spfile

Oracle 11.1.0:

Oracle 10.2.0:

Oracle 10.1.0:

Oracle 9.2.0:

Oracle 8.1.7:

Oracle 8.0.6:

Oracle 7.3.4:

Related Error Messages:

Cause: The SPFILE is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of the SPFILE.

Action: No action required - the conversation is still active, and more files can be specified.

ORA-19598: can not backup SPFILE because the instance was not started with SPFILE

Cause: A backup command requested a backup of the SPFILE, but no SPFILE was used to startup the instance.

Action: Create an SPFILE and re-start the instance using the SPFILE.

ORA-19685: SPFILE could not be verified

Cause: Some data blocks for the SPFILE were corrupt in the backup set.

Action: Unless the damage to the backup set can be repaired, the SPFILE cannot be restored from this backup set.

ORA-19686: SPFILE not restored due to %s

Cause: The indicated file could not be restored, because some of its data blocks were not found in the backup piece.

Action: Unless the damage to the backup set can be repaired, the SPFILE cannot be restored from this backup set.

ORA-19687: SPFILE not found in backup set

Cause: The SPFILE could not be restored, because it is not in this backup set.

Action: This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found in the piece. You must supply the first backup piece of a backup set that contains the requested file.

ORA-32001: write to SPFILE requested but no SPFILE specified at startup

Cause: An alter system command or an internal self tuning mechanism requested a write to the SPFILE but no SPFILE was used to startup the instance

Action: Create an SPFILE and re-start the instance using the SPFILE.

ORA-32002: cannot create SPFILE already being used by the instance

Cause: A create spfile command is trying to write to an SPFILE that was used to startup the instance.

Action: Specify a different SPFILE name

ORA-32004: obsolete and/or deprecated parameter(s) specified

Cause: One or more obsolete and/or parameters were specified in the SPFILE or the PFILE on the server side.

Action: See alert log for a list of parameters that are obsolete. or deprecated. Remove them from the SPFILE or the server side PFILE.

ORA-32010: cannot find entry to delete in SPFILE

Cause: The SPFILE did not contain the sid.parameter entry.

Action: Change the sid and/or the parameter.

ORA-32011: cannot restore SPFILE to location already being used by the instance

Cause: A restore operation trying to write to an SPFILE that was used to startup the instance.

Action: Specify a different SPFILE name

ORA-32013: failure in verifying parameters from the restored SPFILE

Cause: Failure during processing of parameters from restored SPFILE. It could be that restore image of the SPFILE is corrupted.

Action: Further diagnostic information should be in the error stack.

ORA-32014: error processing parameter \"%s\" from the SPFILE restore image

Cause: Failure during processing of parameters from restored SPFILE. It could be that restore image of the SPFILE is corrupted.

Action: Further diagnostic information should be in the error stack.

ORA-32015: unable to restore SPFILE

Cause: Failure during SPFILE restore. It could be that the restore destination is not valid.

Action: Further diagnostic information should be in the error stack.

ORA-32016: parameter \"%s\" cannot be updated in SPFILE

Cause: Database is mounted.

Action: Unmount the database to update the parameter in the SPFILE

ORA-32019: The parameter SPFILE cannot be updated in the server parameter file.

Cause: An attempt was made to update the parameter SPFILE in the server parameter file.

Action: Convert the server parameter file into a parameter file and then add the parameters needed and recreate the server parameter file.

This parameter is documented in the Oracle Server Reference Guide. Search for more info about [ spfile ] on the Oracle FAQ.