waiting for snapshot control file enqueue

#Waiting for snapshot control file enqueue software#

ORA-00206: error in writing (block string, # blocks string) of control fileĬause: A disk I/O failure was detected on writing the control file.Īction: Check if the disk is online, if it is not, bring it online and try a warm start again. ORA-00205: error in identifying control file, check alert log for more infoĬause: The system could not find a control file of the specified name and size.Īction: Check that ALL control files are online and that they are the same files that the system created at cold start time.

If it is online, then you need to recover the disk.

ORA-00204: error in reading (block string, # blocks string) of control fileĬause: A disk I/O failure was detected on reading the control file.Īction: Check if the disk is online, if it is not, bring it online and try a warm start again. Most likely one instance is using a backup control file.Īction: Check that the correct control files were specified. The control files are for the same database but they are not the same files. ORA-00203: using the wrong control filesĬause: The mount ID in the control file is not the same as the mount ID in the control file used by the first instance to mount this database. ORA-00202: control file: ‘ string‘Ĭause: This message reports the name file involved in other messages.Īction: See associated error messages for a description of the problem.

#Waiting for snapshot control file enqueue software#

ORA-00201: control file version string incompatible with ORACLE version stringĬause: The control file was created by incompatible software.Īction: Either restart with a compatible software release or use CREATE CONTROLFILE to create a new control file that is compatible with this release. The conflict is usually caused when two jobs are both backing up the control file, and the job that first starts backing up the control file waits for service from the media manager.ORA-00200: control file could not be createdĬause: It was not possible to create the control file.Īction: Check that there is sufficient disk space and no conflicts in filenames and try to create the control file again. Recovery Manager makes up to five attempts to get the enqueue and then fails the job. Under normal circumstances, a job that must wait for the control file enqueue waits for a brief interval and then successfully retrieves the enqueue. If one RMAN job is already backing up the control file while another needs to create a new snapshot control file, you may see the following message: waiting for snapshot control file enqueue You can also set the snapshot control file name to a raw device: CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/dev/vgd_1_0/rlvt5' Subsequent snapshot control files that RMAN creates use the specified filename.įor example, start RMAN and then enter: CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/oradata/trgt/snap_trgt.ctl' Use the CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' filename ' command to change the name of the snapshot control file. Setting the Location of the Snapshot Control File In these earlier releases, the default location for the snapshot control file was not dependent on the Oracle home, whereas in the current release the default location is dependent on the Oracle home. In general, you should only need to set the snapshot control file location when you are upgrading to the current release from a release earlier than 8.1.7. For example, the default filename on some UNIX platforms in Oracle Database 10 g is Note that if you have a flash recovery area configured, the default location for the snapshot control file is not the flash recovery area. The default value for the snapshot control file is platform-specific and depends on the Oracle home. RMAN needs a snapshot control file only when resynchronizing with the recovery catalog or when making a backup of the current control file. When RMAN needs to resynchronize from a read-consistent version of the control file, it creates a temporary snapshot control file. Setting the Snapshot Control File Location