RMAN issue on backup
Date: Fri, 26 Jun 2009 15:22:10 +0100
Red Hat Enterprise AS Release 3 (Taroon Update 4)
Backups have been working fine for months, when this morning on the daily archive log backup I saw the following.
Starting Control File Autobackup at 26.06.09
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-00601: fatal error in recovery managerRMAN-03004: fatal error during execution of command RMAN-10039: error encountered while polling for RPC completion on channel ORA_DISK_2
RMAN-10006: error running SQL statement: select act from x$ksusex where sid=:1 and serial=:2
RMAN-10002: ORACLE error: ORA-03113: end-of-file on communication channel
*** ERROR: Errors in backup! ***
Checked in the catalog and the relevant backups are AVAILABLE inc. the controlfile one. DB was up with no issues and the archivelogs backed up had been deleted as expected.
This was in the alert log....
Fri Jun 26 12:00:57 2009
skgpspawn failed:category = 27142, depinfo = 11, op = fork, loc = skgpspawn5
Fri Jun 26 12:01:46 2009
Control autobackup written to DISK device
And this is what was in the trace file produced.
- 2009-06-26 12:01:46.277
- ACTION NAME:(0000053 STARTED111) 2009-06-26 12:01:45.719
- MODULE NAME:(backup archivelog: ORA_DISK_2) 2009-06-26 12:01:45.719
- SERVICE NAME:(derb) 2009-06-26 12:01:45.719
- SESSION ID:(413.2905) 2009-06-26 12:01:45.686 kgxgncin: CLSS init failed with status 21
Anyone seen this before. Had a bit of a google and been in Metalink but couldn't see anything exactly the same as this.
Regards & TIA
The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged.
If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.
If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system.
Received on Fri Jun 26 2009 - 09:22:10 CDT