oracle error -- ORA-00302: limit of string logs exceeded

ORA-00302:	limit of string logs exceeded
Cause:	The maximum number of redo log files has been exceeded.
Action:	Use the CREATE CONTROLFILE command with a larger value for MAXLOGFILES if the compatibility is lower than 10.2.0. Otherwise, allocate more storage space for the control file.

oracle error -- ORA-00301: error in adding log file 'string' - file cannot be created

ORA-00301:	error in adding log file 'string' - file cannot be created
Cause:	The creation of the redo log file failed
Action:	Check: 1) there is enough storage space on the device 2) the name of the file is valid 3) the device is online 4) an IO error occurred Also, it is possible REUSE was specified on the command line and a file of the incorrect size exists. Either do not specify REUSE or use a file of the correct size.

oracle error -- ORA-00300: illegal redo log block size string specified - exceeds limit of string

ORA-00300:	illegal redo log block size string specified - exceeds limit of string
Cause:	The specified block size of the redo log is greater than the maximum block size for the operating system.
Action:	Create the redo log on a device with a smaller block size

oracle error -- ORA-00296: maximum number of files (string) exceeded for RECOVER DATAFILE LIST

ORA-00296:	maximum number of files (string) exceeded for RECOVER DATAFILE LIST
Cause:	The RECOVER DATAFILE LIST command specified more datafiles than are allowed by the DB_FILES initialization parameter. This error occurs when doing recovery with Recovery Manager, and the instance has been started with a DB_FILES parameter specifying fewer datafiles than recovery manager needs to recover to satisfy the user's RECOVER command.
Action:	Re-start the instance with a higher value for DB_FILES.

oracle error -- ORA-00295: datafile/tempfile number string is invalid, must be between 1 and string

ORA-00295:	datafile/tempfile number string is invalid, must be between 1 and string
Cause:	An invalid file number was specified.
Action:	Specify a valid datafile or tempfile number and retry the operation.

oracle error -- ORA-00294: invalid archivelog format specifier 'string'

ORA-00294:	invalid archivelog format specifier 'string'
Cause:	An invalid format specifier was found in the LOG_ARCHIVE_FORMAT initialization parameter. The only characters permitted following the % symbol are s, S, t, and T.
Action:	Correct the initialization file and re-start the instance.

oracle error -- ORA-00293: control file out of sync with redo log

ORA-00293:	control file out of sync with redo log
Cause:	The redo log file and control file are out of sync because a non-current controle file was specified when the instance was started.
Action:	Retry the RECOVER command using the current control file, or retry the RECOVER command using the USING BACKUP CONTROLFILE clause.

oracle error -- ORA-00292: parallel recovery feature not installed

ORA-00292:	parallel recovery feature not installed
Cause:	A parallel recovery was requested when the parallel recovery option is not installed.
Action:	Delete the PARALLEL clause from the RECOVER command. Also, delete the RECOVERY_PARALLELISM parameter in the initialization file.

oracle error -- ORA-00291: numeric value required for PARALLEL option

ORA-00291:	numeric value required for PARALLEL option
Cause:	A recovery command was specified incorrectly. The PARALLEL option must be followed by a numeric argument that specifies the degree of parallelism.
Action:	Re-enter the command with a numeric argument specifying the degree of parallelism desired.

oracle error - ORA-00290: operating system archival error occurred. See error below

ORA-00290:	operating system archival error occurred. See error below
Cause:	While attempting to archive to a redo log file, the server encountered an unexpected operating system error.
Action:	Correct the operating system error given in the messages and retry the operation. See also your operating system-specific Oracle documentation.

oracle error - ORA-00289: suggestion : string

ORA-00289:	suggestion : string
Cause:	This message reports the next redo log filename that is needed, according to the initialization parameters LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT. This message assumes that LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT are the same now as when the required redo log file was archived.
Action:	Consider using this filename for the next log needed for recovery.

oracle error - ORA-00288: to continue recovery type ALTER DATABASE RECOVER CONTINUE

ORA-00288:	to continue recovery type ALTER DATABASE RECOVER CONTINUE
Cause:	During media recovery, a new log is not required but the continuation command is necessary to do a checkpoint and report errors.
Action:	Type ALTER DATABASE RECOVER CONTINUE and recovery will resume.

oracle error - ORA-00287: specified change number string not found in thread string

ORA-00287:	specified change number string not found in thread string
Cause:	The given change number does not appear in any of the online redo logs for the given thread.
Action:	Check the statement to make certain a valid change number is given. Perhaps try to use the NEXT option for archiving logs.

oracle error - ORA-00286: no members available, or no member contains valid data

ORA-00286:	no members available, or no member contains valid data
Cause:	None of the members of a redo log file group are available, or the available members do not contain complete data.
Action:	If a member is temporarily offline, attempt to make it available. Make sure that the correct filenames are being used, especially if the redo log file is being accessed from a remote location.

oracle error - ORA-00285: TIME not given as a string constant

ORA-00285:	TIME not given as a string constant
Cause:	UNTIL TIME was not followed by a string constant for the time.
Action:	Enter the time enclosed in single quotation marks.

oracle error - ORA-00284: recovery session still in progress

ORA-00284:	recovery session still in progress
Cause:	An error during recovery was determined to be minor enough to allow the current recovery session to continue.
Action:	More specific messages will accompany this message. Refer to the other messages for the appropriate action.

oracle error - ORA-00283: recovery session canceled due to errors

ORA-00283:	recovery session canceled due to errors
Cause:	An error during recovery was determined to be fatal enough to end the current recovery session.
Action:	More specific messages will accompany this message. Refer to the other messages for the appropriate action.

oracle error - ORA-00282: UPI string call not supported, use ALTER DATABASE RECOVER

ORA-00282:	UPI string call not supported, use ALTER DATABASE RECOVER
Cause:	The given UPI call is no longer supported.
Action:	Use the ALTER DATABASE RECOVER command for all recovery actions.

oracle error - ORA-00281: media recovery may not be performed using dispatcher

ORA-00281:	media recovery may not be performed using dispatcher
Cause:	An attempt was made to use a dispatcher process for media recovery. Memory requirements disallow this recovery method.
Action:	Connect to the instance via a dedicated server process to perform media recovery.

oracle error - ORA-00280: change string for thread string is in sequence #string

ORA-00280:	change string for thread string is in sequence #string
Cause:	This message helps to locate the redo log file with the specified change number requested by other messages.
Action:	Use the information provided in this message to specify the required archived redo log files for other errors.

oracle error - ORA-00279: change string generated at string needed for thread string

ORA-00279:	change string generated at string needed for thread string
Cause:	The requested log is required to proceed with recovery.
Action:	Please supply the requested log with "ALTER DATABASE RECOVER LOGFILE <file_name>" or cancel recovery with "ALTER DATABASE RECOVER CANCEL".

oracle error - ORA-00278: log file 'string' no longer needed for this recovery

ORA-00278:	log file 'string' no longer needed for this recovery
Cause:	The specified redo log file is no longer needed for the current recovery.
Action:	No action required. The archived redo log file may be removed from its current location to conserve disk space, if needed. However, the redo log file may still be required for another recovery session in the future.

oracle error - ORA-00277: illegal option to the UNTIL recovery flag string

ORA-00277:	illegal option to the UNTIL recovery flag string
Cause:	Only CANCEL, CHANGE and TIME can be used with the UNTIL keyword.
Action:	Correct the syntax.

oracle error - ORA-00276: CHANGE keyword specified but no change number given

ORA-00276:	CHANGE keyword specified but no change number given
Cause:	The CHANGE keyword was specified on the command line, but no change number was given.
Action:	Retry the command using a valid change number after the CHANGE keyword.

oracle error -- ORA-00275: media recovery has already been started

ORA-00275:	media recovery has already been started
Cause:	An attempt was made to start a second media recovery operation in the same session.
Action:	Complete or cancel the first media recovery session or start another session to perform media recovery.

oracle error -- ORA-00274: illegal recovery option string

ORA-00274:	illegal recovery option string
Cause:	An illegal option was specified for a recovery command.
Action:	Correct the syntax and retry the command.

oracle error - ORA-00273: media recovery of direct load data that was not logged

ORA-00273:	media recovery of direct load data that was not logged
Cause:	A media recovery session encountered a table that was loaded by the direct loader without logging any redo information. Some or all of the blocks in this table are now marked as corrupt.
Action:	The table must be dropped or truncated so that the corrupted blocks can be reused. If a more recent backup of the file is available, try to recover this file to eliminate this error.

oracle error - ORA-00272: error writing archive log string

ORA-00272:	error writing archive log string
Cause:	An I/O error occurred while archiving a redo log file.
Action:	Check that the output device is still available and correct any device errors that may have occurred. Also, make certain that sufficient space for archiving is available on the output device.

oracle error - ORA-00271: there are no logs that need archiving

ORA-00271:	there are no logs that need archiving
Cause:	An attempt was made to archive the unarchived redo log files manually, but there are no files that need to be archived.
Action:	No action required.

oracle error - ORA-00270: error creating archive log string

ORA-00270:	error creating archive log string
Cause:	An error was encountered when either creating or opening the destination file for archiving.
Action:	Check that the archive destination is valid and that there is sufficient space on the destination device.

oracle error -ORA-00269: specified log file is part of thread string not string

ORA-00269:	specified log file is part of thread string not string
Cause:	The given redo log file is not part of the given thread
Action:	Check that the thread of the redo log file matches the thread on the command line. If not, use a redo log file from the appropriate thread. Retry the command after correcting the error

oracle error - ORA-00268: specified log file does not exist 'string'

ORA-00268:	specified log file does not exist 'string'
Cause:	The given redo log file does not exist.
Action:	Check the spelling and capitalization of the filename and retry the command.

oracle error - ORA-00267: name of archived log file not needed

ORA-00267:	name of archived log file not needed
Cause:	During media recovery, the name of an archived redo log file was entered, but no name was requested.
Action:	Continue media recovery, but do not enter a new log name.

oracle error - ORA-00266: name of archived log file needed- o melhor conteúdo oracle

ORA-00266:	name of archived log file needed
Cause:	During media recovery, the name of an archived redo log file was requested, but no name was entered.
Action:	Mount the correct redo log file and enter its name when it is requested.

oracle error - ORA-00265: instance recovery required, cannot set ARCHIVELOG mode

ORA-00265:	instance recovery required, cannot set ARCHIVELOG mode
Cause:	The database either crashed or was shutdown with the ABORT option. Media recovery cannot be enabled because the online logs may not be sufficient to recover the current datafiles.
Action:	Open the database and then enter the SHUTDOWN command with the NORMAL or IMMEDIATE option.

oracle error -- ORA-00264: no recovery required

ORA-00264:	no recovery required
Cause:	An attempt was made to perform media recovery on files that do not // need any type of recovery.
Action:	Do not attempt to perform media recovery on the selected files. Check to see that the filenames were entered properly. If not, retry the command with the proper filenames.

Positivo drivers- Download dos drivers da positivo informatica

A positivo é uma empresa brasileira especializada em computadores e notebooks.
Estimativas informam que a positivo informatica possui em de 16.1% do market share das vendas de computadores no brasil.

E para fazer o download dos drivers é muito simples, basta acessar a pagina do fabricante no link abaixo e informar o numero de serie do seu produto.

http://www.positivoinformatica.com.br/www/suporte/drivers

Fica a dica.

oracle error - ORA-00262: current log string of closed thread string cannot switch

ORA-00262:	current log string of closed thread string cannot switch
Cause:	The log cannot be cleared or manually archived because it is the current log of a closed thread, and it is not possible to switch logs so another log is current. All other logs for the thread need to be archived, or cleared, and cannot be reused.
Action:	Archive another log in the same thread first, or complete the clearing. See attached errors for the reason the switch cannot be completed.

oracle error - ORA-00261: log string of thread string is being archived or modified

ORA-00261: log string of thread string is being archived or modified Cause: The log is either being archived by another process or an administrative command is modifying the log. Operations that modify the log include clearing, adding a member, dropping a member, renaming a member, and dropping the log. Action: Wait for the current operation to complete and try again.

oracle error - ORA-00260: cannot find online log sequence string for thread string

ORA-00260:	cannot find online log sequence string for thread string
Cause:	The log sequence number supplied to the archival command does not match any of the online logs for the thread. The log might have been reused for another sequence number, it might have been dropped, the sequence number might be greater than the current log sequence number, or the thread might not have any logs.
Action:	Check the ARCHIVE statement, then specify a valid log sequence number. Specify a valid log sequence number.

oracle error - ORA-00257: archiver error. Connect internal only, until freed.

ORA-00257:	archiver error. Connect internal only, until freed.
Cause:	The archiver process received an error while trying to archive a redo log. If the problem is not resolved soon, the database will stop executing transactions. The most likely cause of this message is the destination device is out of space to store the redo log file.
Action:	Check archiver trace file for a detailed description of the problem. Also verify that the device specified in the initialization parameter ARCHIVE_LOG_DEST is set up properly for archiving.

oracle error - ORA-00256: cannot translate archive destination string string

ORA-00256:	cannot translate archive destination string string
Cause:	The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command could not be translated.
Action:	Check the accompanying message stack for more detailed information. Then, retry the ALTER SYSTEM command using a different string.

oracle error - ORA-00255: error archiving log string of thread string, sequence # string

ORA-00255:	error archiving log string of thread string, sequence # string
Cause:	An error occurred during archiving.
Action:	Check the accompanying message stack for more detailed information. If the online log is corrupted, then the log can be cleared using the UNARCHIVED option. This will make any existing backups useless for recovery to any time after the log was created, but will allow the database to generate redo.

oracle error - ORA-00259: log string of open instance string (thread string) is the current log, cannot archive

ORA-00259:	log string of open instance string (thread string) is the current log, cannot archive
Cause:	An attempt was made to archive the current log of an open thread. This is not allowed because the redo log file may still be in use for the generation of redo entries.
Action:	Force a log switch in the instance where the thread is open. If no instances are open, open the database so that instance recovery can recover the thread.

oracle error - ORA-00258: manual archiving in NOARCHIVELOG mode must identify log

ORA-00258:	manual archiving in NOARCHIVELOG mode must identify log
Cause:	The database is in NOARCHIVELOG mode and a command to manually archive a log did not specify the log explicitly by sequence number, group number or filename.
Action:	Specify log by filename, by group number or by thread and sequence number.

oracle error - ORA-00254: error in archive control string 'string'

ORA-00254:	error in archive control string 'string'
Cause:	The specified archive log location is invalid in the archive command or the LOG_ARCHIVE_DEST initialization parameter.
Action:	Check the archive string used to make sure it refers to a valid online device.

oracle error - ORA-00253: character limit string exceeded by archive destination string string

ORA-00253:	character limit string exceeded by archive destination string string
Cause:	The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command was too long.
Action:	Retry the ALTER SYSTEM command using a string shorter than the limit specified in the error message.

oracle error - ORA-00252: log string of thread string is empty, cannot archive

ORA-00252:	log string of thread string is empty, cannot archive
Cause:	A log must be used for redo generation before it can be archived. The specified redo log was not been used since it was introduced to the database. However it is possible that instance death during a log switch left the log empty.
Action:	Empty logs do not need to be archived. Do not attempt to archive the redo log file.

oracle error - ORA-00251: LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as string string

ORA-00251:	LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as string string
Cause:	The destination specified by the LOG_ARCHIVE_DUPLEX_DEST parameter is the same as the destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command.
Action:	Specify a different destination for parameter LOG_ARCHIVE_DUPLEX_DEST, or specify a different destination with the ALTER SYSTEM command.

oracle error - ORA-00250: archiver not started

ORA-00250:	archiver not started
Cause:	An attempt was made to stop automatic archiving, but the archiver process was not running.
Action:	No action required.

oracle error - ORA-00238: operation would reuse a filename that is part of the database

ORA-00238:	operation would reuse a filename that is part of the database
Cause:	The filename supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of a file that is currently part of the database.
Action:	Retry the operation with a different filename.

oracle error - ORA-00237: snapshot operation disallowed: control file newly created

ORA-00237:	snapshot operation disallowed: control file newly created
Cause:	An attempt to invoke cfileMakeAndUseSnapshot with a currently mounted control file that was newly created with CREATE CONTROLFILE was made.
Action:	Mount a current control file and retry the operation.

oracle error -- ORA-00299: must use file-level media recovery on data file string

ORA-00299:	must use file-level media recovery on data file string
Cause:	The control file does not contain an entry for this file, so block media recovery cannot be done.
Action:	Restore the data file and perform file-level media recovery.

oracle error - ORA-00237: snapshot operation disallowed: control file newly created

ORA-00237:	snapshot operation disallowed: control file newly created
Cause:	An attempt to invoke cfileMakeAndUseSnapshot with a currently mounted control file that was newly created with CREATE CONTROLFILE was made.
Action:	Mount a current control file and retry the operation.

oracle error - ORA-00236: snapshot operation disallowed: mounted control file is a backup

ORA-00236:	snapshot operation disallowed: mounted control file is a backup
Cause:	Attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot, or cfileUseSnapshot when the currently mounted control file is a backup control file.
Action:	Mount a current control file and retry the operation.

oracle error - ORA-00235: control file fixed table inconsistent due to concurrent update

ORA-00235:	control file fixed table inconsistent due to concurrent update
Cause:	Concurrent update activity on a control file caused a query on a control file fixed table to read inconsistent information.
Action:	Retry the operation.

oracle error - ORA-00234: error in identifying or opening snapshot or copy control file

ORA-00234:	error in identifying or opening snapshot or copy control file
Cause:	A snapshot or copy control file of the specified name could not be found or opened during an invocation of cfileUseSnapshot, cfileMakeAndUseSnapshot, or cfileUseCopy.
Action:	Re-create the snapshot or copy control file using cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE, respectively.

oracle error - ORA-00233: copy control file is corrupt or unreadable

ORA-00233:	copy control file is corrupt or unreadable
Cause:	The specified copy control file was found to be corrupt or unreadable during an invocation of cfileUseCopy.
Action:	Before retrying cfileUseCopy, use the ALTER DATABASE BACKUP CONTROLFILE command and specify the same filename that was specified for cfileUseCopy.