V$SESSION_LONGOPS.TOTALWORK shows incorrect value during RMAN backup on standby database.
(Doc ID 1638684.1)
Last updated on MARCH 14, 2019
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 to 22.214.171.124 [Release 11.2 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
You can see the progress of RMAN backup by the following query "V$SESSION_LONGOPS" .
However,on Physical Standby database,%_COMPLETE shows incorrect value.
The entry was removed when %_COMPLETE reached to 50!
SELECT sysdate,SID, SERIAL#, CONTEXT, SOFAR, TOTALWORK,
WHERE OPNAME LIKE 'RMAN%'
AND OPNAME NOT LIKE '%aggregate%'
AND TOTALWORK != 0
AND SOFAR <> TOTALWORK
RMAN backup fails with the following message.
RMAN-3009: failure of backup command on XXXX channel at 12/18/2013 00:43:32
ORA-19502: write error on file "XXXX_1_1", block number 385 (blocksize=8192)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
ANS1311E (RC11) Server out of data storage space
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document