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: = 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. After Installation of Media Manager, RMAN Channel Allocation Fails: Scenario
0 kommentar(er)
