V$SESSION_LONGOPS.TOTALWORK shows incorrect value during RMAN backup on standby database.
Last updated on MARCH 27, 2014
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 11.2 to 12.1]
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
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms