Skip to main content

Step by Step How to Clone Oracle RAC Database to Single Instance Database

 <<Back to Oracle RAC Main Page


Cloning Oracle RAC Database to Single Instance Database

Existing DB ORCL with 2 node (ORCL11 and ORCL12)
Closed DB: ORCLN

Step1: Add Static Listener Entry
Add Static Listener Entry in GRID_HOME/network/admin/listener.ora and reload the listener 

SID_LIST_LISTENER = 
 (SID_LIST = 
  (SID_DESC = 
    (GLOBAL_DBNAME = ORCLN) 
    (ORACLE_HOME = /ora_app/product/19c/dbd1) 
    (SID_NAME = ORCLN) 
   ) 
 ) 

lsnrctl reload LISTENER

LSNRCTL for Linux: Version 19.0.0.0.0 - Production on 03-FEB-2026 09:14:16

Copyright (c) 1991, 2023, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))
The command completed successfully

[+ASM1] lsnrctl status |grep -i ORCLN
Service "ORCLN" has 1 instance(s).
  Instance "ORCLN", status UNKNOWN, has 1 handler(s) for this service...

Step2:Add TNS entry for ORCLN

add  TNS entry for "ORCLN" in Oracle RDBMS Home $ORACLE_HOME/network/admin/tnsnames.ora

ORCLN =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = node1)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = ORCLN)
    )
  )

Step3: Create Password File
NOTE: Clone database password shoud be same as source database for rman duplicate to work

[ORCL11] orapwd file=orapwORCLN

Enter password for SYS:*******

[ORCL11] ls -lrt *ORCLN*
-rw-r----- 1 oracle oinstall 6144 Feb  3 09:20 orapwORCLN


Step4:Verify TNS Connectivity for ORCLN database

[ORCL11] sqlplus sys@ORCLN as sysdba

SQL*Plus: Release 19.0.0.0.0 - Production on Tue Feb 3 09:23:42 2026
Version 19.20.0.0.0

Copyright (c) 1982, 2022, Oracle.  All rights reserved.

Enter password:
Connected to an idle instance.

Step5: Create Directory Structures for ORCLN

mkdir -p /ora_log/diag/rdbms/ORCLN/adump/

Step6: Create parameter file for ORCLN database

You need to carefully review the parameters of Source database and pre-create the directory structures for ORCLN as needed.

cat initORCLN.ora
 
*.audit_file_dest='/ora_log/diag/rdbms/ORCLN/adump/'
*.cluster_database=false
*.control_files='+DATA/ORCLN/cntrlORCLN.dbf','+ARCH/ORCLN/cntrlORCLN.dbf','+RECO/ORCLN/cntrlORCLN.dbf'
*.db_name='ORCLN'
*.memory_max_target=10G
*.memory_target=8G
*.db_file_name_convert='+DATA/orcl/datafile','+DATA/ORCLN','+DATA/orcl/DATAFILE','+DATA/ORCLN','+DATA/orcl/tempfile','+DATA/ORCLN'
*.log_file_name_convert='+DATA/orcl/onlinelog','+DATA/ORCLN/onlinelog','+RECO/orcl/onlinelog','+RECO/ORCLN/onlinelog'
*.db_file_create='+DATA'

Step7: Start ORCLN (auxiliary) instance in NOMOUNT mode

export ORACLE_SID=ORCLN
export ORACLE_HOME=/ora_app/product/19c/dbd1
export PATH=$PATH:$ORACLE_HOME/bin

[ORCLN] sqlplus "/as sysdba"

SQL*Plus: Release 19.0.0.0.0 - Production on Tue Feb 3 09:48:25 2026
Version 19.20.0.0.0

Copyright (c) 1982, 2022, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup nomount;
ORACLE instance started.

Total System Global Area 1.0737E+10 bytes
Fixed Size                 13670496 bytes
Variable Size            6593445888 bytes
Database Buffers         4110417920 bytes
Redo Buffers               19881984 bytes
SQL>

SQL> show parameter convert

NAME                                 TYPE
------------------------------------ ---------------------------------
VALUE
------------------------------
db_file_name_convert                 string
+DATA/orcl/datafile, +DATA/ORCLN,
 +DATA/orcl/DATAFILE, +DATA/ORCLN
log_file_name_convert                string
+DATA/orcl/onlinelog, +DATA/ORCLN
/onlinelog, +RECO/orcl/onlinelo
g, +RECO/ORCLN/onlinelog
pdb_file_name_convert                string


Step8:connect with target and auxiliary database using rman



oracle@node1:~/ [ORCL11] rman target sys/*********@ORCL11 auxiliary sys/**************@ORCLN

Recovery Manager: Release 19.0.0.0.0 - Production on Tue Feb 3 10:00:53 2026
Version 19.20.0.0.0

Copyright (c) 1982, 2019, Oracle and/or its affiliates.  All rights reserved.

connected to target database: orcl (DBID=3798554321)
connected to auxiliary database: ORCLN (not mounted)

Step9: Duplicate database 

RMAN>
run
{
allocate channel tgt1 device type disk ;
allocate channel tgt2 device type disk ;
allocate auxiliary channel aux1 device type disk ;
duplicate target database to ORCLN from active database;
}



Successful completion message 

contents of Memory Script:
{
   Alter clone database open resetlogs;
}
executing Memory Script

database opened
Finished Duplicate Db at 03-FEB-26

ep How to Install Oracle RAC Database Software 12c Release2

Comments

Post a Comment

Popular posts from this blog

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-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-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

How to Export and Import TDE Master Encryption Key

<<Back to Oracle DB Security Main Page In many cases you need to export the TDE Master Encryption Key and Import it in same or different database. For Example: If you want to migrate a PDB (Using Encryption) from one CDB to another, you must export the TDE Keys from source CDB and import it in Target CDB. How To Export TDE Master Encryption Key SQL> ADMINISTER KEY MANAGEMENT EXPORT ENCRYPTION KEYS WITH SECRET "any password to protect export file" TO 'file_path' IDENTIFIED BY keystore_password If you run the above statement in PDB it will export the keys for that PDB only SQL> alter session set container=PDB01 ; Session altered. SQL> ADMINISTER KEY MANAGEMENT EXPORT ENCRYPTION KEYS WITH SECRET "mysecret" TO '/home/dbatst1/Wallet/PDB01_TDE.KEY' IDENTIFIED BY keystore_password; keystore altered. NOTE : You can only export the keys if the password based wallet is open in case AUTOLOGIN wallet is open you can export the keys eit...
1 comment
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

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

Error: ORA-16883: unable to translate DGConnectIdentifier property

<<Back to Oracle DataGuard Main Page Error: ORA-16883: unable to translate DGConnectIdentifier property DGMGRL> show configuration; Configuration - dg_tst1t   Protection Mode: MaxPerformance   Members:   tst1tp - Primary database     Error: ORA-16778: redo transport error for one or more members     tst1ts - Physical standby database       Error: ORA-16883: unable to translate DGConnectIdentifier property DGMGRL> show database tst1ts Database - tst1ts   Role:               PHYSICAL STANDBY   Intended State:     APPLY-ON   Transport Lag:      (unknown)   Apply Lag:          (unknown)   Average Apply Rate: (unknown)   Real Time Query:    OFF   Instance(s):     TST1T Database S...
Post a Comment
Read more

How to Install JAVA JVM Component into an Existing Oracle Database

<<Back to DB Administration Main Page How to Add the JVM Component to an Existing Oracle Database Followed oracle Doc ID 1461562.1 and installed oracle JVM component in multitenant database, the script installed JVM component in CDB$ROOT container only and the component was still missing in PDB$SEED and all pluggable database. Since the script and steps mentioned in Doc ID 1461562.1 did not install the component in PDB$SEED , all future PDBs create in the container also inherited the issue and eventually JVM  component was not installed in any of the PDBs. Scroll down to see how to install JVM component in a Multitenant Database environment using catcon.pl How to Verify if JVM component is installed or not select comp_name, version, status from dba_registry where comp_name like '%JAVA%' ; COMP_NAME                           ...
Post a Comment
Read more

How to Modify Database Startup Mode (Startoption) in Clusterware Registry

<<Back to Oracle RAC Main Page How to Modify Database Startup Option Using srvctl In this post I will show you, how you can modify the database startup option / Database startup mode in clusterware registry using srvctl. There are some time requirement to change the startup option (from default  OPEN ) to  MOUNT, or "READ ONLY" eg if in case of Physical Standby Configuration Let us Check the Current Configuration $ srvctl config database -d ORCL Database unique name: ORCL Database name: Oracle home: /u01/app/oracle/product/12.1.0.2/dbhome_2 Oracle user: oracle Spfile: +DATA/ORCL/PARAMETERFILE/spfileORCL.ora Password file: +DATA/ORCL/PASSWORD/pwORCL Domain: Start options: open Stop options: immediate Database role: PHYSICAL_STANDBY Management policy: AUTOMATIC Server pools: Disk Groups: DATA,RECO Mount point paths: Services: Type: RAC Start concurrency: Stop concurrency: OSDBA group: oinstall OSOPER group: oinstall Database instances: ORCL1,...
Post a Comment
Read more