Sunday, November 9, 2014

ORA-00290 Operating system archival error occurred

Error Code
ORA-00290

Description
Operating system archival error occurred. See error below.

Cause
Possible cause of this error is, while attempting to archive to a redo log file, the server encountered an unexpected operating system error.

Action
To fix this issue, correct the operating system error given in the messages and retry the operation. See also your operating system-specific Oracle documentation.

reference

ORA-00289 Suggestion string

Error Code
ORA-00289

Description
Suggestion : string

Cause
Possible cause of this error is, 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
To fix this issue, consider using this filename for the next log needed for recovery.

reference

ORA-00288 To continue recovery type ALTER DATABASE RECOVER CONTINUE

Error Code
ORA-00288

Description
To continue recovery type ALTER DATABASE RECOVER CONTINUE.

Cause
Possible cause of this error is, during media recovery, a new log is not required but the continuation command is necessary to do a checkpoint and report errors.

Action
To fix this issue, type ALTER DATABASE RECOVER CONTINUE and recovery will resume.

reference

ORA-00287 Specified change number string not found in thread string

Error Code
ORA-00287

Description
Specified change number string not found in thread string.

Cause
Possible cause of this error is, the given change number does not appear in any of the online redo logs for the given thread.

Action
To fix this issue, check the statement to make certain a valid change number is given. Perhaps try to use the NEXT option for archiving logs.

reference

ORA-00286 No members available, or no member contains valid data

Error Code
ORA-00286

Description
No members available, or no member contains valid data.

Cause
Possible cause of this error is, none of the members of a redo log file group are available, or the available members do not contain complete data.

Action
To fix this issue, 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.

reference