Roll Forward Physical Standby Database Using Service

<<Back to Oracle DataGuard Main Page

How to Synchronize Physical Standby Database Using Service

Primary DB Unique Name: ORCL1PP

Standby DB Unique Name: ORCL1PS

Step1: Place the physical standby database in MOUNT mode

If Active Dataguard is Used

SQL> SHUTDOWN IMMEDIATE;
SQL> STARTUP MOUNT;

Step2: Stop Managed Recovery Process

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

Or if Broker is configured

DGMGRL> edit database 'ORCL1PS' set STATE='APPLY-OFF' ;

Step3: Connect to Standby database over Service

rman target SYS/<password>@ORCL1PS
connected to target database: ORCL1PS (DBID=4165840403, not open)

Step4: Recover From Primary Database Service

RMAN> recover database from service "ORCL1PP" noredo using compressed backupset;

Starting recover at 06-JUL-20
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=318 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=630 device type=DISK
channel ORA_DISK_1: starting incremental datafile backup set restore
channel ORA_DISK_1: using compressed network backup set from service ORCL1PP
destination for restore of datafile 00001: /u01/oradata/ORCL1P/DBFILE/SYSTEM_01.DBF
channel ORA_DISK_2: starting incremental datafile backup set restore
channel ORA_DISK_2: using compressed network backup set from service ORCL1PP
destination for restore of datafile 00002: /u01/oradata/ORCL1P/DBFILE/PDBSEED/SYSTEM_01.DBF
channel ORA_DISK_2: restore complete, elapsed time: 00:00:08
.....................
.....................
.....................
channel ORA_DISK_1: using compressed network backup set from service ORCL1PP
destination for restore of datafile 00012: /u01/oradata/ORCL1P/DBFILE/PDB01/TOOLS_01.DBF
channel ORA_DISK_1: restore complete, elapsed time: 00:00:04
channel ORA_DISK_2: restore complete, elapsed time: 00:03:17
Finished recover at 06-JUL-20

Step5: Compare Primary and Standby datafile SCN for each datafile

Execute below command on Primary as well as on standby and compare the SCN for each datafile.

SQL>set line 200
SQL>col SUBSTR(HXFNM,1,40) for a50
SQL>select HXFIL File_num,substr(HXFNM,1,40),fhscn from x$kcvfh;

At this point the datafiles are synchronized and as we know standby control file still do not have this information and therefore it also has to be synchronized.

Step6: Refresh standby controlfile from the primary

rman target SYS/<password>@ORCL1PS

RMAN> shutdown immediate;

database dismounted
Oracle instance shut down

RMAN> startup nomount;

connected to target database (not started)
Oracle instance started

Total System Global Area 3221225472 bytes

Fixed Size                     3078416 bytes
Variable Size                654313200 bytes
Database Buffers            2558525440 bytes
Redo Buffers                   5308416 bytes

RMAN> restore standby controlfile from service "ORCL1PP" ;

Starting restore at 06-JUL-20
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=312 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=619 device type=DISK
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: using network backup set from service ORCL1PP
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:08
output file name=/u01/oradata/ORCL1P/CONTROL/CONTROL_01.CTL
output file name=/u01/oradata/ORCL1P/CONTROL/CONTROL_02.CTL
output file name=/u01/oradata/ORCL1P/CONTROL/CONTROL_03.CTL
Finished restore at 06-JUL-20

RMAN> alter database mount;
Statement processed
released channel: ORA_DISK_1
released channel: ORA_DISK_2

Step7: Validate Datafile name

Since we have restored the controlfile from primary database, it got the datafile name from Primary only and if the directory structure between Primary and standby is different between the standby and primary databases or if you are using Oracle managed file names OMF, you need to rename it accordingly.

catalog the STANDBY datafiles with RMAN to execute the rename operation.

NOTE: If the primary and standby have identical structure and datafile names, this step can be skipped.

RMAN> report schema;

To keep the blog cleaner and readable I have omitted the output of the command

........

RMAN> catalog start with '/u01/oradata/ORCL1P';

Switch Datafile to Copy

Switch to the cataloged datafile copy.

RMAN> SWITCH DATABASE TO COPY;

Step8: Start Recovery

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

Only If Oracle Active Data Guard in Use

SQL> ALTER DATABASE OPEN READ ONLY;

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

Optionally

On the primary database, switch the archived redo log files using the following command:

SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;

Comments

How to Power On/off Oracle Exadata Machine

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using button on front of the server The power on sequence is as follows. 1. Start Rack, including switches Note:- Ensure the switches have had power applied for a few minutes to complete power on configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers Note:- Ensure all Exadata Storage Servers complete the boot process before starting the database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the serve...

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco...

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1 node1-vip node2 node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:

ORA-46630: keystore cannot be created at the specified location

<<Back to DB Administration Main Page ORA-46630: keystore cannot be created at the specified location CDB011> ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "xxxxxxx"; ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "EncTest123" * ERROR at line 1: ORA-46630: keystore cannot be created at the specified location Cause Creating a keystore at a location where there is already a keystore exists Solution To solve the problem, use a different location to create a keystore (use ENCRYPTION_WALLET_LOCATION in sqlnet.ora file to specify the keystore location), or move this ewallet.p12 file to some other location. Note: Oracle does not recommend deleting keystore file (ewallet.p12) that belongs to a database. If you have multiple keystores, you can choose to merge them rather than deleting either of them.

ORA-65104: operation not allowed on an inactive pluggable database alter pluggable database open

<<Back to DB Administration Main Page ORA-65104: operation not allowed on an inactive pluggable database SQL> alter pluggable database TEST_CLON open; alter pluggable database TEST_CLON open * ERROR at line 1: ORA-65104: operation not allowed on an inactive pluggable database Cause The pluggable database status was UNUSABLE. It was still being created or there was an error during the create operation. A PDB can only be opened if it is successfully created and its status is marked as NEW in cdb_pdbs.status column SQL> select PDB_NAME,STATUS from cdb_pdbs; PDB_NAME STATUS -------------------- --------------------------- PDB$SEED NORMAL TEST_CLON UNUSABLE Solution: Drop the PDB and create it again. Related Posts How to Clone Oracle PDB (Pluggable Database) with in the Same Container

ORA-16905: The member was not enabled yet

<<Back to Oracle DataGuard Main Page ORA-16905 Physical Standby Database is disabled DGMGRL> show configuration; Configuration - DG_ORCL1P Protection Mode: MaxPerformance Members: ORCL1PP - Primary database ORCL1PS - Physical standby database (disabled) ORA-16905: The member was not enabled yet. Fast-Start Failover: Disabled Configuration Status: SUCCESS (status updated 58 seconds ago) DGMGRL> DGMGRL> enable database 'ORCL1PS'; Enabled. DGMGRL> show configuration; Configuration - DG_ORCL1P Protection Mode: MaxPerformance Members: ORCL1PP - Primary database ORCL1PS - Physical standby database Fast-Start Failover: Disabled Configuration Status: SUCCESS (status updated 38 seconds ago)

How to Switch Log File from All Instances in RAC

<<Back to Oracle RAC Main Page Switch The Log File of All Instances in Oracle RAC. In many cases you need to switch the logfile of the database. You can switch logfile using alter system switch logfile command but if you want to switch the logfile from all the instances you need to execute the command on all the instances individually and therefore you must login on all the instances. You can avoid this and switch logfile of all instances by just running the below command from any of the instance in RAC database SQL> ALTER SYSTEM SWITCH ALL LOGFILE; System altered.

Starting RMAN and connecting to Database

<<Back to Oracle Backup & Recovery Main Page Starting RMAN and connecting to Database Starting RMAN and connecting to Database To start RMAN you need to set the environment and type rman and press enter. You can connect to database either using connect command or using command line option. using command line option localhost:$ export ORACLE_HOME=/ora_app/product/18c/dbd2 localhost:$ export PATH=$ORACLE_HOME/bin:$PATH localhost:$ export ORACLE_SID=ORCL1P localhost:$ rman target / Recovery Manager: Release 18.0.0.0.0 - Production on Sun Apr 4 08:11:01 2021 Version 18.11.0.0.0 Copyright (c) 1982, 2018, Oracle and/or its affiliates. All rights reserved. connected to target database: ORCL1P (DBID=4215484517) RMAN> using connect option localhost:$ rman RMAN> connect target sys@ORCL1P target database Password:******** connected to target database: ORCL1P (DBID=4215484517) NOTE: To use connect command you need to ensure that you have proper TNS sentry...

How to Attach to a Datapump Job and Check Status of Export or Import

<<Back to Oracle DATAPUMP Main Page How to check the progress of export or import Jobs You can attach to the export/import job using ATTACH parameter of oracle datapump utility. Once you are attached to the job you check its status by typing STATUS command. Let us see how Step1> Find the Export/Import Job Name You can find the datapump job information from DBA_DATAPUMP_JOBS or USER_DATAPUMP_JOBS view. SQL> SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME OPERATION JOB_MODE STATE ---------- ------------------------------ -------------------- ---------- ---------- SYSTEM SYS_EXPORT_FULL_02 ...

ORA-46655: no valid keys in the file from which keys are to be imported

<<Back to DB Administration Main Page SQL> administer key management import encryption keys with secret "xxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxx" with backup; administer key management import encryption keys with secret "xxxxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxxxx" with backup * ERROR at line 1: ORA-46655: no valid keys in the file from which keys are to be imported Cause: Either the keys to be imported already present in the target database or correct container (PDB) is not set. Solution: In my case I got the error because I attempted to import the keys for newly plugged database PDB02 from CDB$ROOT container. To Solve the issue just switched to the correct container and re run the import. SQL> show con_name CON_NAME ------------------------------ CDB$ROOT <===Wrong Container selected SQL> alter session set container=PDB02; Session alt...

Online DBA

Search This Blog