When checking the backup output script in the database today, an error occurred in the Rman backup.
This article mainly describes the phenomenon of the problem.
The error message is as follows:
bash-3.00$ More/data/backup/backup_tradedb_090523.out
Script./data/backup/backup_tradedb.sh
= = = started on Sat 23:00:00 CST 2009 = = =
RMAN:/opt/oracle/product/10.2/database/bin/rman
Oracle_sid:tradedb1
Oracle_home:/opt/oracle/product/10.2/database
Recovery manager:release 10.2.0.3.0-production on the Sat May 23 23:00:01 2009
Copyright (c) 1982, +, Oracle. All rights reserved.
Rman-06900:warning:unable to generate V$rman_status or V$rman_output row
rman-06901:warning:disabling update of the V$rman_status and V$rman_output rows
ORACLE error from Target database:
Ora-03113:end-of-file on communication channel
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR message STACK follows ===============
RMAN-00571: ===========================================================
Rman-00554:initialization of internal Recovery manager package failed
Rman-06003:oracle error from Target database:
Ora-03114:not connected to ORACLE
Script./data/backup/backup_tradedb.sh
= = = ended in error on Sat 23:22:34 CST 2009 = = =
This error message has not really encountered before, there have been ORA-3113 errors, there are two alarm information, preliminary suspicion may be related to network instability, try to restart background backup, if you can run smoothly, this problem may be instantaneous network instability caused.
bash-3.00$ More/data/backup/backup_tradedb_090525.out
Script. Bash
= = started on Mon 14:34:14 CST 2009 = = =
RMAN:/opt/oracle/product/10.2/database/bin/rman
Oracle_sid:tradedb1
Oracle_home:/opt/oracle/product/10.2/database
Recovery manager: Release 10.2.0.3.0-production on Mon May 25 14:34:15 2009
Copyright (c) 1982, +, Oracle. All rights reserved.
RMAN-06900: Warning: Unable to generate v$rman_status or v$rman_output rows
RMAN-06901: Warning: Disable update of v$rman_status and V$rman_output rows
Oracle error from Target database:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR message STACK follows ===============
RMAN-00571: ===========================================================
RMAN-00554: Internal Recovery Manager Package initialization failed
RMAN-06003: Oracle Error from Target database:
ORA-03114: Not connected to Oralce
Script. Bash
= = = ended in error on Mon 14:56:54 CST 2009 = = =
After running the backup in the background, the error message is displayed quickly in the output script, which is slightly different from the previous error message, and there is no ORA-3113 error this time. It appears that the problem can be reproduced by attempting a direct Rman connection:
bash-3.00$ Rman Target/
Recovery manager: Release 10.2.0.3.0-production on Mon May 25 15:02:51 2009
Copyright (c) 1982, +, Oracle. All rights reserved.
See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/database/Oracle/
The operation of the Rman connection database is suspended. When the Rman is waiting for the corresponding, query the alert file, check the backup startup time has the corresponding error message, the result has a corresponding error:
Sat May 23 17:16:43 2009
ges:potential blocker (pid=17895) on resource wf-00000046-00000000;
Enqueue info in file/opt/oracle/admin/tradedb/bdump/tradedb1_lmd0_7210.trc and DIAG trace file
Sat May 23 21:28:36 2009
ges:potential blocker (pid=15807) on resource tm-00002391-00000000;
Enqueue info in file/opt/oracle/admin/tradedb/bdump/tradedb1_lmd0_7210.trc and DIAG trace file
Sat May 23 23:15:04 2009
ges:potential blocker (pid=21881) on resource cf-00000000-00000000;
Enqueue info in file/opt/oracle/admin/tradedb/bdump/tradedb1_lmd0_7210.trc and DIAG trace file