Find Oracle Error Code Ora- and Pl/SQL Tips and Tricks

Cause : Oracle detected that the initialization parameter COMPATIBLE was not explicitly specified, and the compatibility of the database is lower than the default value of the COMPATIBLE parameter. In order to use the new compatible setting, the intialization parameter must be explicitly set by the user.
Action : Explicitly set the value of COMPATIBLE parameter either in PFILE or SPFILE, whichever is used.

Popularity: 6% [?]

Share This

Cause : The COMPATIBLE initialization parameter is not high enough to allow the operation. Allowing the command would make the database incompatible with the release specified by the current COMPATIBLE parameter.
Action : Shutdown and startup with a higher compatibility setting.

Popularity: 12% [?]

Share This

Cause : A clone database open forces log file renaming to avoid overwriting the primary log files.
Action : Rename the log files manually or using the LOG_FILE_NAME_CONVERT initialization parameter.

Popularity: 11% [?]

Share This

Cause : An instance tried to start by using a value of the initialization parameter INSTANCE_NUMBER that is already in use.
Action : Either:
- Specify another INSTANCE_NUMBER,
- Shut down the running instance with this number, or
- Wait for instance recovery to complete on the instance with this number.

Popularity: 8% [?]

Share This

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 : Restart the instance with a higher value for DB_FILES.

Popularity: 10% [?]

Share This

Cause : An invalid format specifier was found in the LOG_ARCHIVE_FORMAT initialization parameter. The only characters permitted for string are s,S, t, and T.
Action : Correct the initialization file and restart the instance.

Popularity: 9% [?]

Share This

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.

Popularity: 8% [?]

Share This

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.

Popularity: 8% [?]

Share This

Cause : The block size as stored in the control file header is different from the value of the initialization parameter DB_BLOCK_SIZE. This might be due to an incorrect setting of DB_BLOCK_SIZE, or else might indicate that the control file
has either been corrupted or belongs to a different database.
Action : Restore a good copy of the control file.

Popularity: 12% [?]

Share This

Cause : The service name specified in the MTS_SERVICE initialization parameter is too long.
Action : Use a shorter name for the MTS_SERVICE value (less than or equal to 255 characters).

Popularity: 7% [?]

Share This