Skip to main content

How to Create Physical Standby database using RMAN restore from service


<<Back to Oracle DataGuard Main Page

Creating a Physical Standby database using RMAN restore from service

Assumption:
It is assumed that you already have single instance database installed and configured and you want to setup physical standby database for this primary database to protect you data from disaster recovery etc.
Installation and configuration of a single instance database using ASM is explained in following posts
Here is the details of my Primary database for which I want to configure the Physical Standby database
Hosts and Databases Used in this Example
DB_ROLE
PRIMARY
STANDBY
HOST_NAME
test1
test2
DB_UNIQUE_NAME
TST1TP
TST1TS
DB_NAME
TST1T
TST1T
That's said lets start .....
Step1> Prepare your primary database to support physical standby database
  • Put the database in Archivelog mode
If the primary database is not already in archivelog mode, put it in archive log mode
SQL> alter system set log_archive_dest_1='location=/u01/dbatst1/stage/archive/';
System altered.
For ASM
SQL> alter system set log_archive_dest_1='location=+DATA';
System altered.
SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 2147483648 bytes
Fixed Size                  8794848 bytes
Variable Size            1912605984 bytes
Database Buffers          218103808 bytes
Redo Buffers                7979008 bytes
Database mounted.
SQL> alter database archivelog;
Database altered.
SQL> alter database open;
Database altered.
SQL> archive log list;
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            +DATA
Oldest online log sequence     198
Next log sequence to archive   200
Current log sequence           200
  • Disabling Active Data Guard
    NOTE: This step is optional and only needed if you don't want to use Oracle Active Dataguard Option or You don't have Licence for it. Since this is an static parameter it requires downtime.
    SQL> alter system set "_query_on_physical"=FALSE scope=spfile;
    System altered.
    SQL> startup force;
    ORACLE instance started.
    Total System Global Area 2147483648 bytes
    Fixed Size                  8794848 bytes
    Variable Size            1912605984 bytes
    Database Buffers          218103808 bytes
    Redo Buffers                7979008 bytes
    Database mounted.
    Database opened.
    SQL> show parameter "_query_on_physical"
    NAME                                 TYPE        VALUE
    ------------------------------------ ----------- ------------------------------
    _query_on_physical                   boolean     FALSE
    • Activating Standby File Management
    SQL> alter system set standby_file_management=AUTO scope=both;
    System altered.
    SQL> show parameter standby_file_management
    NAME                                 TYPE        VALUE
    ------------------------------------ ----------- ------------------------------
    standby_file_management              string      AUTO
    • Enable forced logging
    SQL> alter database force logging;
    Database altered.
    SQL> select force_logging from v$database;
    FORCE_LOGGING
    ---------------------------------------
    YES
    Want to read more about force logging Check out Oracle Database Logging Mode and Enhancements in 18c
    • Enable Flashback
    SQL> alter database flashback on;
    Database altered.
    SQL> select flashback_on from v$database;
    FLASHBACK_ON
    ------------------
    YES
    • Add Standby Logfile
    The count of standby logfile group is always online logfile group +1
    The Size of the standby logfile must be same as online logfile
    Use below query to find the online lofile details 
    SQL> select GROUP#,BYTES/1024/1024 "Online Loggroup Size in MB" from v$log;
        GROUP# Online Loggroup Size in MB
    ---------- --------------------------
             1                       2048
             2                       2048
    Since I have 2 Online Log Group 2GB in size I must add 3 Standby logfile Group each 2GB.
    SQL> alter database add standby logfile group 11 '+DG_TST_FRA' size 2048M;
    Database altered.
    SQL> alter database add standby logfile group 12 '+DG_TST_FRA' size 2048M;
    Database altered.
    SQL> alter database add standby logfile group 13 '+DG_TST_FRA' size 2048M;
    Database altered.
    • Configure DG Broker Parameter
    SQL> alter system set dg_broker_config_file1='+DG_TST_DATA/TST1T/drc1.dat';
    System altered.
    SQL> alter system set dg_broker_config_file1='+DG_TST_DATA/TST1T/drc2.dat';
    System altered.
    SQL> alter system set dg_broker_start=true;
    System altered.
    • Setting Unique name
    DB_UNIQUE_NAME parameter of primary and standby database must be unique. As mentioned in the beginning itself I am using TST1TP as DB_UNIQUE_NAME  for Primary database
    SQL> alter system set db_unique_name='TST1TP' scope=spfile;
    System altered.
    SQL> startup force;
    ORACLE instance started.
    Total System Global Area 2147483648 bytes
    Fixed Size                  8794848 bytes
    Variable Size            1912605984 bytes
    Database Buffers          218103808 bytes
    Redo Buffers                7979008 bytes
    Database mounted.
    Database opened.
    SQL> show parameter unique
    NAME                                 TYPE        VALUE
    ------------------------------------ ----------- ------------------------------
    db_unique_name                       string      TST1TP
    Step2> On Standby Database Server (test2) Install oracle database Binaries - same Oracle version as Primary Database
    For Step by step instruction navigate to Oracle 12c Database Software Only Installation in Silent Mode
    Step3> Optionally if using ASM
    Install and configure ASM and ASM Diskgroups. Steps are provided at Installing and Configuring Oracle Grid Infrastructure for Standalone Server in Silent Mode
    Step4> Configure Oracle Network Files
    • Configuring TNSNAMES.ORA file
    Configuring tnsnames.ora file
    Prepare the tns entry for both primary as well as Stanby and enter in $ORACLE_HOME/network/admin/tnsnames.ora file in both primary and physical stanby database servers
    TST1TP =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP) (HOST = test1.oracle.com)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = TST1TP)
          (UR = A)
        )
      )
    TST1TS =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP) (HOST = test2.oracle.com) (PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = TST1TS)
          (UR = A)
        )
      )
    • Configure Static Entries in Listener.ora file
    Note1:  Static entries are only used by the Broker itself via the Broker defined StaticConnectIdentifier property.  They are NEVER to be used for any other purpose by the user.  This includes using it for the normal DGConnectIdentifier, RMAN connections or anything else.  Also note that you must never define a static entry for the Broker 'DGB' service.  That service is for the Broker exclusive use.  Also note that using the "_DGMGRL" or "_DGB" in your TNSNAMES definition is expressly forbidden.
    Note2: Static "_DGMGRL" entries are no longer needed as of Oracle Database 12.1.0.2 in Oracle Data Guard Broker configurations that are managed by Oracle Restart, RAC On Node or RAC as the Broker will use the clusterware to restart an instance.
    Example:
    SID_LIST_LISTENER=
      (SID_LIST=
        (SID_DESC=
         (GLOBAL_DBNAME=db_unique_name_DGMGRL.db_domain)
         (ORACLE_HOME=oracle_home)
         (SID_NAME=sid_name)
        )
      )
    On Primary: Enter the following Value in Listener.ora
    SID_LIST_LISTENER=
      (SID_LIST=
        (SID_DESC=
         (GLOBAL_DBNAME=TST1TP_DGMGRL)
         (ORACLE_HOME=/u01/dbatst1/12.2.0.1/dbp1)
         (SID_NAME=TST1T)
        )
      )
    On Standby: Enter the following Value in Listener.ora
    SID_LIST_LISTENER=
      (SID_LIST=
        (SID_DESC=
         (GLOBAL_DBNAME=TST1TS_DGMGRL)
         (ORACLE_HOME=/u01/app/oracle/12.2.0.1/dbp1)
         (SID_NAME=TST1T)
        )
      )
    Step 5: Transfer Primary database password file to standby database

    $ scp $ORACLE_HOME/dbs/orapwTST1T oracle@test2:$ORACLE_HOME/dbs/

    Rename the password file to the standby database name.
    NOTE: The password file name must match the instance name/SID used at the standby site, not the DB_NAME.

    Step6> Prepare the Listener and TNS Entry for RMAN Duplicate

    • Statically register the Standby instance to the listener

    Enter the following the entry in the listener.ora of Standby database and reload the listener
    SID_LIST_LISTENER =
      (SID_LIST =
        (SID_DESC =
         (ORACLE_HOME = /u01/app/oracle/12.2.0.1/dbp1)
         (SID_NAME = TST1T)
        )
       )

    • Prepare the TNS entry for RMAN duplicate
    Prepare the TNS entry of Standby database for RMAN restore from service and enter it in tnsnames.ora file of both Primary and standby database.
    TST1T_DUP =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP) (HOST = test2) (PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = TST1T)
          (UR = A)
        )
      )
    • Verify the TNS Entry using tnsping
    test1$ tnsping TST1T_DUP
    test2$ tnsping TST1T_DUP
    • Verify if the connection 'AS SYSDBA' is working
    Verify from both Primary as well as from standby. You should be able to connect to the standby instance from primary even if it is not started.
    sqlplus /nolog
    SQL> connect sys/<passwd>@Primary AS SYSDBA
    From Primary:
    $ sqlplus /nolog
    SQL> connect sys@TST1T_DUP as sysdba
    Enter password:
    Connected to an idle instance.
    SQL> connect sys@TST1TP  as sysdba
    Enter password:
    Connected.
    From Standby:
    $ sqlplus /nolog
    SQL> connect sys@TST1T_DUP as sysdba
    Enter password:
    Connected to an idle instance.
    SQL> connect sys@TST1TP  as sysdba
    Enter password:
    Connected.
    Step7> Create pfile from Primary for standby
    SQL> create pfile='/u01/dbatst1/stage/backup/initTST1T.ora' from spfile;
    File created.
    Step8> Transfer the PFILE on Standby Server at $ORACLE_HOME/dbs
    $ scp /u01/dbatst1/stage/backup/initTST1T.ora oracle@test2:/u01/app/oracle/12.2.0.1/dbp1/dbs/
    Step9> modify the Pfile on Standby Server as shown below
    *.db_unique_name='TST1TS'
    Optionally
    NOTE1:-If you have different file system/ASM DISK GROUP structure between Primary and standby then modify the following parameter accordingly
    db_create_file_dest='ASM_DISKGROUP OR FILESYSTEM'
    db_create_online_log_dest_1='ASM_DISKGROUP OR FILESYSTEM'
    db_create_online_log_dest_2='ASM_DISKGROUP OR FILESYSTEM'
    NOTE2:- If you are not willing to use OMF and you have different file system/ASM DISK GROUP structure between Primary and standby then include below Parameter in you init file of Standby.
    db_file_name_convert = 'DB_FILE_LOCATION_ON_PRIMARY','DB_FILE_LOCATION_ON_STANDBY'
    log_file_name_convert= 'ONLINELOG_FILE_LOCATION_ON_PRIMARY','ONLINELOG_FILE_LOCATION_ON_STANDBY'
    Step10> Create Required directories on Standby Server
    $ mkdir -p /u01/app/admin/TST1T/adump
    Step11> On Standby Server: Set the Environment variables and start the Database Instance in NOMOUNT mode
    $export ORACLE_HOME=/u01/app/oracle/12.2.0.1/dbp1
    $export ORACLE_SID=TST1T
    $export PATH=$ORACLE_HOME/bin:$PATH
    $ sqlplus "/as sysdba"
    Connected to an idle instance.
    SQL> create spfile from pfile;
    File created.
    SQL> startup nomount;
    ORACLE instance started.
    Total System Global Area 2147483648 bytes
    Fixed Size                  8794848 bytes
    Variable Size            1912605984 bytes
    Database Buffers          218103808 bytes
    Redo Buffers                7979008 bytes
    Step12> Create the Standby Using RMAN Restore from Service
    • Restore Controlfile 
    $ rman target /
    Recovery Manager: Release 18.0.0.0.0 - Production on Fri Feb 22 13:55:43 2019
    Version 18.3.0.0.0
    Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: TST1T (not mounted)
    RMAN> restore standby controlfile from service TST1TP;
    Starting restore at 22-FEB-19
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=783 device type=DISK
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: using network backup set from service TST1TP
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:05
    output file name=+DATA/TST1TS/CONTROLFILE/current.257.1000907771
    output file name=+DATA/TST1TS/CONTROLFILE/current.258.1000907771
    Finished restore at 22-FEB-19
    • Mount the Standby database

    RMAN> sql 'alter database mount';
    sql statement: alter database mount
    released channel: ORA_DISK_1
    • Restore Standby database from service
    RMAN> restore database from service TST1TP;
    Starting restore at 22-FEB-19
    Starting implicit crosscheck backup at 22-FEB-19
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=784 device type=DISK
    Crosschecked 4 objects
    Finished implicit crosscheck backup at 22-FEB-19
    Starting implicit crosscheck copy at 22-FEB-19
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 22-FEB-19
    searching for all files in the recovery area
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: +DATA/TST1TS/CONTROLFILE/current.257.1000907771
    File Name: +DATA/TST1TS/CONTROLFILE/current.258.1000907771
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: using network backup set from service TST1TP
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00001 to +DATA/TST1T/DATAFILE/system.265.1000551777
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:16
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: using network backup set from service TST1TP
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00002 to +DATA/TST1T/82293A8712975890E0530601A8C0295F/DATAFILE/system.266.1000551783
    ....................................
    ....................................
    channel ORA_DISK_1: restoring datafile 00016 to +DATA/TST1T/8251E43D73226C5FE0530601A8C0FEC7/DATAFILE/undotbs1.383.1000726461
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:04
    Finished restore at 22-FEB-19

    • Backup Spfile
    RMAN> backup spfile;
    Starting backup at 22-FEB-19
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current SPFILE in backup set
    channel ORA_DISK_1: starting piece 1 at 22-FEB-19
    channel ORA_DISK_1: finished piece 1 at 22-FEB-19
    piece handle=+DATA/TST1TS/BACKUPSET/2019_02_22/nnsnf0_tag20190222t140402_0.277.1000908243 tag=TAG20190222T140402 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    Finished backup at 22-FEB-19
    Starting Control File and SPFILE Autobackup at 22-FEB-19
    piece handle=+DATA/TST1TS/AUTOBACKUP/2019_02_22/s_1000907961.278.1000908245 comment=NONE
    Finished Control File and SPFILE Autobackup at 22-FEB-19
    • Create Broker Configuration
    $ dgmgrl /
    Welcome to DGMGRL, type "help" for information.
    Connected to "TST1TP"
    Connected as SYSDG.
    DGMGRL> CREATE CONFIGURATION DG_TST1T AS PRIMARY DATABASE IS TST1TP CONNECT IDENTIFIER IS TST1TP;
    Configuration "dg_tst1t" created with primary database "tst1tp"
    DGMGRL> ADD DATABASE TST1TS AS CONNECT IDENTIFIER IS TST1TS;
    Database "tst1ts" added
    DGMGRL> show configuration;
    Configuration - dg_tst1t
      Protection Mode: MaxPerformance
      Members:
      tst1tp - Primary database
        tst1ts - Physical standby database
    Fast-Start Failover: DISABLED
    Configuration Status:
    DISABLED
    Step6> Enable Configuration
    DGMGRL> enable configuration;
    Enabled.
    DGMGRL> show configuration;
    Configuration - dg_tst1t
      Protection Mode: MaxPerformance
      Members:
      tst1tp - Primary database
        tst1ts - Physical standby database
    Fast-Start Failover: DISABLED
    Configuration Status:
    SUCCESS   (status updated 59 seconds ago)

    ==========================================================
    If you notice below error in Standby database alert log, Just drop and recreate the online and standby logfile and everything will be fine

    ORA-00312: online log 3 thread 1: '+DATA/TST1T/ONLINELOG/group_3.263.1000551717'
    ORA-17503: ksfdopn:2 Failed to open file +DATA/TST1T/ONLINELOG/group_3.263.1000551717
    ORA-15012: ASM file '+DATA/TST1T/ONLINELOG/group_3.263.1000551717' does not exist
    2019-02-22T15:07:36.144621+01:00


    SQL> recover managed standby database cancel;
    Media recovery complete.
    SQL> select GROUP#,MEMBERS,STATUS from v$log;
        GROUP#    MEMBERS STATUS
    ---------- ---------- ----------------
             1          2 INACTIVE
             3          2 CURRENT
             2          2 INACTIVE
    SQL> alter database drop logfile group 1;
    Database altered.
    SQL>  alter database drop logfile group 2;
    Database altered.
    SQL> alter database clear logfile group 3;
    Database altered.
    SQL>  alter database add logfile group 1 '+DATA' size 2048M;
    Database altered.
    SQL> alter database add logfile group 2 '+DATA' size 2048M;
    Database altered.
    SQL>  alter database drop logfile group 3;
    Database altered.
    SQL> alter database add logfile group 3 '+DATA' size 2048M;
    Database altered.
      
    SQL> alter database drop logfile group 11;
    Database altered.
    SQL>  alter database drop logfile group 12;
    Database altered.
    SQL> alter database drop logfile group 13;
    Database altered.
    SQL> alter database drop logfile group 14;
    Database altered.
    SQL>  alter database add standby logfile group 11 '+DATA' size 2048M;
    Database altered.
    SQL> alter database add standby logfile group 12  '+DATA' size 2048M    ;
    Database altered.
    SQL> alter database add standby logfile group 13  '+DATA' size 2048M;
    Database altered.
    SQL> alter database add standby logfile group 14 '+DATA' size 2048M;
    Database altered.
    SQL> recover managed standby database using currecnt logfile disconnect from session;
    Media recovery complete.

    Comments

    Post a Comment

    Popular posts from this blog

    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...
    Post a Comment
    Read more

    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...
    7 comments
    Read more

    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:
    1 comment
    Read more

    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.
    Post a Comment
    Read more

    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
    Post a Comment
    Read more

    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)
    Post a Comment
    Read more

    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.
    Post a Comment
    Read more

    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...
    Post a Comment
    Read more

    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          ...
    7 comments
    Read more

    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...
    Post a Comment
    Read more