All posts by mpbod

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

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.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

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

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.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00256: cannot translate archive destination string string

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.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

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

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.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00254: error in archive control string ‘string’

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.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

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

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.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

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

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.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

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

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.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

ORA-00250: archiver not started

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.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/

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

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.

Back to previous menu

https://support.oracle.com/

http://www.oracle.com/