- #WAITING FOR SNAPSHOT CONTROL FILE ENQUEUE INSTALL#
- #WAITING FOR SNAPSHOT CONTROL FILE ENQUEUE FULL#
If the channel allocation with SBT_LIBRARY succeeds, but an ordinary sbt channel allocation fails, then the database is probably trying to load a library other than the one you installed. If the channel allocation fails, then check the trace file again to see whether you can learn anything new. 'ENV=(NSR_SERVER=tape_svr,NSR_CLIENT=oracleclnt,NSR_GROUP=oracle_tapes)' PARMS='SBT_LIBRARY=/vendor/lib/some_mm_lib.so', For example, if your library is called /vendor/lib/some_mm_lib.so, then run a command such as the following, making sure to specify whatever PARMS settings are required by your media manager: RUN To test the loading of the media management library, try allocating a channel by using the PARMS parameter SBT_LIBRARY to force the loading of the media management library. Contact the media management vendor for details about the trace messages written to sbtio.log. The media management vendor may not have implemented the writing of trace messages in a particular situation. Note, however, that writing SBT trace messages is the responsibility of the media management software, not the Oracle database or RMAN. You may find more detailed information in the file sbtio.log, as described in the error message. The last line of this output indicates that Oracle is loading the default static library instead of the media management library that you installed. SKGFQ OSD: Look for SBT Trace messages in file /oracle/rdbms/log/sbtio.log SKGFQ OSD: Error in function sbtinit on line 2396 For example, the trace file on UNIX may be called something like /oracle/rdbms/log/prod1_ora_c, and may contain information such as the following: *** 17:16:54.385 The trace file should have the complete path name of the media management library loaded by the database as well as any other media manager errors or operating system errors. If the channel allocation fails, then the database generates a trace file in the USER_DUMP_DEST location that contains the error that caused the channel allocation to fail. The ORA-27211 error indicates that the channel allocation is failing because the database is not loading the media management library. Typically, there is no need to refer to the trace file or sbtio.log in such a case.Īfter Installation of Media Manager, RMAN Channel Allocation Fails: Diagnosis It indicates the basic problem, that the media management library could not be loaded. The most important line of the error output is the ORA-27211 error. ORA-27211: Failed to load Media Management Library
ORA-19554: error allocating device, device type: SBT_TAPE, device name: RMAN-03009: failure of allocate command on c1 channel at 17:16:54 RMAN-00569: = ERROR MESSAGE STACK FOLLOWS = For example, after allocating the sbt channel, you receive an error stack similar to the following: RMAN-00571: =
#WAITING FOR SNAPSHOT CONTROL FILE ENQUEUE INSTALL#
In this scenario, you install and test the media manager as explained in "Configuring RMAN to Make Backups to a Media Manager", but you still cannot make RMAN back up to tape. For more information about Oracle (NYSE:ORCL), visit Installation of Media Manager, RMAN Channel Allocation Fails: Scenario Oracle offers a comprehensive and fully integrated stack of cloud applications and platform services. My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.
#WAITING FOR SNAPSHOT CONTROL FILE ENQUEUE FULL#
To view full details, sign in with your My Oracle Support account.ĭon't have a My Oracle Support account? Click to get started! + Database was hung with no redo log file switches until the database was bounced. + Alert log reported "ORA-00239: timeout waiting for control file enqueue". Information in this document applies to any platform. Oracle Cloud Infrastructure - Database Service - Version N/A and later Oracle Database Exadata Cloud Machine - Version N/A and later Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.1.0.2 Oracle Database - Enterprise Edition - Version 11.1.0.7 to 11.2.0.2 Database Hung With ORA-00239: Timeout Waiting For Control File Enqueue
0 kommentar(er)
