My Oracle Support Banner

Failure To Convert To Physical Standby (Doc ID 2085432.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.4 and later
Information in this document applies to any platform.

Symptoms

 Standby database was converted to Snapshot database for testing using  11g Using Snapshot Standby Database. <Document 443720.1>

 Rman backup validate check logical database was run on the database after converting it to Snapshot database which populated v$database_block_corruption

 Converting the standby database back to Physical standby failed with Below error

 

RMAN> sql 'alter database convert to physical standby';
sql statement : alter databaes convert to physical standby
RMAN-00571===================================
RMAN-00569=======ERROR MESSAGE STACK FOLLOWS
RMAN-00571===================================
RMAN-03009: failure of sql command on default channel at 10/27/2015 17:37:29
RMAN-11003: failure during parse/execution of SQL statement: alter database convert to physical standby
ORA-38769: FLASHBACK DATABASE failed after modifying data.
ORA-38746: error occured while restoring data block (file# 12, block# 274273676)
ORA-10564: tablespace AA_BBBB
ORA-01110: data file 12: '+DATA/xxxx/datafile/xx_xxx.xxx.xxxxx'
ORA-10561: block type 'TRANSACTION MANAGED INDEX BLOCK', data object# 913146
ORA-38747: corrupt before image (file# 12, block# 274273676)

 

Select database_role from v$database shows

SNAPSHOT STANDBY

Indicating the convert to physical standby was not successful.

Changes

 Corruption in the Datafile block and flashback log after the database was converted to Snapshot standby

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.