Problem Details
Problem Statement
Probable Oracle bug with 19.17 impacts operations of the Dbvisit Standby database
This Problem occurs from 19.17 onwards: i.e. 19.18, 19.19 etc ...
Applicable Error Code
RMAN-03002: failure of show command at 10/31/2022 12:35:12
ORA-01507: database not mounted
Affected Versions
Dbvisit Standby 9,10 & 11
Affected Platforms
All Platforms
Description
Normal operations like sending and applying logs can continue without issues, and this does not impact database activation during DR scenarios. This does not affect the production database.
The issue has been fixed with Standby MP 11.2.1 and Dbvisit Standby Version 10.2.1.
Dbvisit Standby works well with the supported database version (10g to 21c) without issues. Still, when you upgrade to 19.17 from earlier releases of 19c or earlier versions, you encounter an issue when running operations like below as the standby database is put in nomount state:
- Create Standby Database
- Switchover
- SYNC
Dbvisit runs the below RMAN command show all; in nomount for the standby database to check the current configuration parameters of RMAN before doing the above operations. The output of the command is usually like the one below.
rman target /
Recovery Manager: Release 19.0.0.0.0 - Production on Sat Oct 29 09:19:31 2022
Version 19.16.0.0.0
Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.
connected to target database: DEV (DBID=2472969873)
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name OMKSP are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/19.0.0/dbhome_1/dbs/snapcf_DEV.f'; # default
But, After upgrading to 19.17, there is an error with the above command when the show all; is run with the standby database in nomount.
oracle@localhost[/home/oracle]: rman target =/ Recovery Manager: Release 19.0.0.0.0 - Production on Wed Nov 9 16:03:58 2022 Version 19.17.0.0.0 Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved. connected to target database: SRC (DBID=1086252808)
using target database control file instead of recovery catalog RMAN configuration parameters for database with db_unique_name SRC are: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE CONTROLFILE AUTOBACKUP ON; # default CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE MAXSETSIZE TO UNLIMITED; # default CONFIGURE ENCRYPTION FOR DATABASE OFF; # default CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default CONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of show command at 11/09/2022 15:53:12 ORA-01507: database not mounted
There is currently no workaround for this issue. We urge customers not to upgrade to Oracle 19.17 for the time being. We are also actively working with Oracle support to confirm the issue as a bug.
This has been fixed with Standby MP 11.2.1 and also with Dbvisit Standby 10.2.1. We recommend customers planning to upgrade to Oracle 19.17 to upgrade to the latest releases of Standby MP 11.2.1 and Dbvisit standby 10.2.1.
Comments