Migrate the Database

To perform the migration of a single instance Oracle Database Cloud Service server to an Oracle Cloud Infrastructure Virtual Machine database system, you can use Oracle Data Guard. You must configure the database on Oracle Cloud Infrastructure Compute Classic as the primary database (the source database), which you migrate to a standby database (the target database) on Oracle Cloud Infrastructure on Virtual Machine Database systems.

Configure the Primary (Source) Database

To configure the primary database (the source database), you configure Oracle Data Guard and modify the listener.ora and tnsnames.ora files for the standby database (the target database).

Configure the Primary Database for the Standby Database

In this configuration, you configure the primary (source) database to use Oracle Data Guard.

Use SSH to sign in to the primary (source) database server.
```
sudo su
su - oracle
```
Sign in to the database instance as a user who has administrator privileges. For example:
```
sqlplus / as sysoper
```

Ensure that the database is in ARCHIVELOG mode

SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 9
Next log sequence to archive 11
Current log sequence 11
SQL>

In the output above, notice that the value of Database log mode is set to Archive Mode, and the value of Automatic archival is Enabled.

If the output for Database log mode is No Archive Mode and the output for Automatic archival is Disabled, then do the following:
1. Shut down the database.
```
SHUTDOWN IMMEDIATE
```
2. Restart the database in mount mode
```
STARTUP MOUNT
```
3. Enable archive log mode.
```
ALTER DATABASE ARCHIVELOG;
```
4. Ensure that the database is now in archive log mode.
```
ARCHIVE LOG LIST
```
5. The output for the Database log mode should be Archive Mode and the output for Automatic archival is Enabled.
6. Open the database.
```
ALTER DATABASE OPEN;
```
Connect with the SYSDBA administrator privilege.
```
CONNECT / AS SYSDBA
```
For a multitenant environment, do the following:
1. Check the status of the PDBS.
```
SHOW PDBS
```
2. If the PDBS are not open, then open them.
```
ALTER PLUGGABLE DATABASE ALL OPEN;
```
Ensure that the database is in force logging mode. For example:
```
SELECT NAME, OPEN_MODE, FORCE_LOGGING FROM V$DATABASE;
```
If necessary, enable force logging.
```
ALTER DATABASE FORCE LOGGING;
```
Check the configuration.
```
SELECT NAME, CDB, OPEN_MODE, FORCE_LOGGING FROM V$DATABASE;
```
The FORCE_LOGGING column should be YES.
Use the SHOW PARAMETER command to check the following database parameters:
1. DB_NAME : It is recommended to use the same name as the target database.
2. DB_UNIQUE_NAME: Ensure that this name is different from the name used on the target database.
3. REMOTE_LOGIN_PASSWORD_FILE: This parameter must be set to EXCLUSIVE.

Ensure that the Flashback in ON. If its not ON, use sql command ALTER DATABASE FLASHBACK ON;

select flashback_on from v$database;
FLASHBACK_ON
------------------
YES
show parameter flashback_retention_target
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_flashback_retention_target        integer     1440
SQL>

Add Static Services to the Primary Database `listener.ora` File

After you add static services to the primary (source) database listener.ora file, you must restart the listener.

Use SSH to sign in to the primary (source) database server.
At the command line, connect as root.
```
sudo su -
```
Sign in as the database software owner oracle.
```
su - oracle
```

Modify the $ORACLE_HOME/network/admin/listener.ora file to include the static listener. The following example shows the format to use for one static listener:

SID_LIST_LISTENER=
  (SID_LIST=
    (SID_DESC=
    (SDU=65535)
    (GLOBAL_DBNAME = <primary_db_unique_name>.<primary_db_domain>)
    (SID_NAME = <source_db_name>)
    (ORACLE_HOME=<oracle_home_directory>)
    (ENVS="TNS_ADMIN=<oracle_home_directory>/network/admin")
    )
    (SID_DESC=
    (SDU=65535)
    (GLOBAL_DBNAME = <primary_db_unique_name>_DGMGRL.<primary_db_domain>)
    (SID_NAME = <source_db_name>)
    (ORACLE_HOME=<oracle_home_directory>)
    (ENVS="TNS_ADMIN=<oracle_home_directory>/network/admin")
    )
  )

Stop the listener.
```
lsnrctl stop listener
```
Restart the listener.
```
lsnrctl start listener
```
Check the listener status.
```
lsnrctl status
```

Configure the Primary Database Parameters

After you configure the primary (source) database and add static services to the primary database listener.ora file, you can configure the Oracle Data Guard parameters on the primary database.

Note:

Ensure that the source database is in ARCHIVELOG MODE with FLASHBACK enabled by default. It is recommended to have DB_BLOCK_CHECKSUM=FULL. If they are any performance issues then switch to DB_BLOCK_CHECKING=MEDIUM

Use SSH to sign in to the primary database (the source database) server.
Sign in to the database instance as a user who has the SYSDBA administrator privilege.
```
sqlplus / as sysdba
Enter password: password
```

Enable automatic standby file management.

ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=AUTO SID='*' SCOPE=SPFILE;

Set the archive lag target.

ALTER SYSTEM SET ARCHIVE_LAG_TARGET=1800 SID='*' SCOPE=SPFILE;

Identify the Oracle Broker configuration file names and locations. The following statements depend on the type of database storage.

ALTER SYSTEM SET DG_BROKER_CONFIG_FILE1='/u02/app/oracle/oradata/<source_db_name>/dr1<source_db_name>.dat' SCOPE=BOTH;
ALTER SYSTEM SET DG_BROKER_CONFIG_FILE2='/u03/app/oracle/fast_recovery_area/<source_db_name>/dr2<source_db_name>.dat' SCOPE=BOTH;

Enable the Oracle Broker DMON process for the database.
```
ALTER SYSTEM SET DG_BROKER_START=TRUE SCOPE=BOTH;
```

Set the DB_BLOCK_CHECKING and DB_BLOCK_CHECKSUM parameters.

ALTER SYSTEM SET DB_BLOCK_CHECKING=FULL SCOPE=BOTH;
ALTER SYSTEM SET DB_BLOCK_CHECKSUM=FULL SCOPE=BOTH;

Set the log buffer to 256 megabytes.

ALTER SYSTEM SET LOG_BUFFER=268435456 SCOPE=SPFILE;

Set the DB_LOST_WRITE_PROTECT parameter to TYPICAL.

ALTER SYSTEM SET DB_LOST_WRITE_PROTECT=TYPICAL SCOPE=BOTH;

Enable the database flashback feature. The minimum recommended value for DB_FLASHBACK_RETENTION_TARGET is 120 minutes.
```
ALTER DATABASE FLASHBACK ON;
ALTER SYSTEM SET DB_FLASHBACK_RETENTION_TARGET=120; 
ALTER SYSTEM ARCHIVE LOG CURRENT;
```
Add the standby redo logs, based on the online redo log. You can use the query below to determine the number and size (in bytes) of the ORLs. The size of the standby redo logs must be the same as the online redo logs, but you must add one or more additional standby redo logs than there are online redo logs. In the following example, four online redo logs exist, so you must add at least five standby redo logs. In other words, you must specify the current redo logs plus at least one, and then use the same size for it as the original redo logs.
1. Execute the following query to determine the number, and size in bytes, of the Oracle redo logs.
```
SELECT GROUP#, BYTES FROM V$LOG;
```
  The output should be similar to the following.
```
GROUP# BYTES
------ ----------
1      1073741824
2      1073741824
3      1073741824
```
2. Specify the current redo logs plus one more, and use the same size as the current redo logs. For example:
```
alter database add standby logfile thread 1
group 4('/u04/app/oracle/redo/stby_redo01.log') size 1073741824,
group 5('/u04/app/oracle/redo/stby_redo02.log') size 1073741824,
group 6('/u04/app/oracle/redo/stby_redo03.log') size 1073741824,
group 7('/u04/app/oracle/redo/stby_redo04.log') size 1073741824;
```
3. Verify that you created the correct number of standby redo logs.
```
SELECT GROUP#, BYTES FROM V$STANDBY_LOG;
```
  Output similar to the following should appear:
```
GROUP#      BYTES
---------- ----------
         4   1073741824
         5   1073741824
         6   1073741824
         7   1073741824
```

Configure the Standby (Target) Database

To configure the standby (target) database, you must modify the oratab,listener.ora, and tnsnames.ora files.

Drop Standby database

This step cleans up the initial database for creating a physical standby on Virtual Machine Database system.

Note:

Capture db_unique_name on standby database. It is mandatory to use same db_unique_name for standby database creation. The db_unique_name is case sensitive.

Use SSH to sign in to the standby database (the target database) server.
At the command line, connect as root.
```
sudo su -
```
Sign in as the database software owner oracle.
```
sudo su - oracle
```

Stop the database

srvctl stop database -d <standby_db_unique_name>

Start the database in mount mode


srvctl start database -d <standby_db_unique_name> -o mount


sqlplus / as sysdba
SQL*Plus: Release 12.1.0.2.0 Production on Sat Feb 17 18:21:20 2018
Copyright (c) 1982, 2014, Oracle.  All rights reserved.
Connected to:
Oracle Database 12c EE Extreme Perf Release 12.1.0.2.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Advanced Analytics and Real Application Testing options

Drop the database

alter system enable restricted session;
System altered.
drop database;

Add Static Services to the Standby Database listener.ora File

After you add static services to the standby database (the target database) listener.ora file, you must restart the listener. .

Use SSH to sign in to the standby (target) database server.
At the command line, connect as root.
```
sudo su 
```
Sign in as the database software owner oracle.
```
su - oracle
```
Execute the oraenv script, which sets the $ORACLE_HOME environment variable.
```
. oraenv
```
Output similar to the following should appear:
```
ORACLE_SID = [oracle] ? db_name
The Oracle base has been set to /u01/app/oracle
```
SSH to the standby database system, log in as the opc or root user, and sudo to the grid user.
```
sudo su - grid
```

Modify the /u01/app/12.2.0.1/grid/network/admin/listener.ora file to include the static listener. The first static listener shown below is required for Oracle Recovery Manager (Oracle RMAN) duplicate.

SID_LIST_LISTENER=
  (SID_LIST=
    (SID_DESC=
    (SDU=65535)
    (GLOBAL_DBNAME = <standby db_unique_name>.<standby db_domain>)
    (SID_NAME = <standby oracle_sid>)
    (ORACLE_HOME=<oracle home directory>)
    (ENVS="TNS_ADMIN=<oracle home directory>/network/admin")
    )
   
  )

Use the srvctl utility to stop the listener.
```
srvctl stop listener -l LISTENER
```
Restart the listener.
```
srvctl start listener -l LISTENER
```

Check the listener status.

lsnrctl status

Sample Output

LSNRCTL for Linux: Version 12.2.0.1.0 - Production on 20-FEB-2018 02:45:31
Copyright (c) 1991, 2016, Oracle.  All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 12.2.0.1.0 - Production
Start Date                19-FEB-2018 12:14:06
Uptime                    0 days 14 hr. 31 min. 24 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /u01/app/12.2.0.1/grid/network/admin/listener.ora
Listener Log File         /u01/app/grid/diag/tnslsnr/migtest/listener/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.0.1.2)(PORT=1521)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=<host name>)(PORT=5500))(Security=(my_wallet_directory=/u01/app/oracle/product/12.1.0.2/dbhome_1/admin/<Standby_db_name>/xdb_wallet))(Presentation=HTTP)(Session=RAW))
Services Summary...
Service "+APX" has 1 instance(s).
  Instance "+APX1", status READY, has 1 handler(s) for this service...
Service "+ASM" has 1 instance(s).
  Instance "+ASM1", status READY, has 1 handler(s) for this service...
Service "+ASM_DATA" has 1 instance(s).
  Instance "+ASM1", status READY, has 1 handler(s) for this service...
Service "+ASM_RECO" has 1 instance(s).
  Instance "+ASM1", status READY, has 1 handler(s) for this service...
Service "<StandbyDB>" has 1 instance(s).
  Instance "<standby_db_name>.<standby_db_domain>", status READY, has 1 handler(s) for this service...
Service "<standby_db_name>" has 1 instance(s).
  Instance "<standby_db_name>.<standby_db_domain>", status READY, has 1 handler(s) for this service...
Service "<standby_db_name>.<standby_db_domain>" has 2 instance(s).
  Instance "MIGTEST", status UNKNOWN, has 1 handler(s) for this service...
  Instance "<StandbyDB>", status READY, has 1 handler(s) for this service...
Service "<StandbyDB>" has 1 instance(s).
  Instance "<StandbyDB>", status READY, has 1 handler(s) for this service...
Service "<StandbyDB>" has 1 instance(s).
    Instance "<StandbyDB>", status READY, has 1 handler(s) for this service...
The command completed successfully

Note:

In the above output, you may see the new listener with status UNKNOWN. This is an expected output.

Copy TDE Wallets from the Primary Database to the Standby Database

You can manually copy the TDE wallet files from the primary database (the source database) system to the standby database (the target database) system by using Secure Copy Protocol (SCP).

Compress the TDE Wallet

You must perform this operation in the primary database (the source database).

Use SSH to sign in to the primary database (the source database) server.
At the command line, connect as root.
```
sudo su -
```
Sign in as the database software owner oracle.
```
su - oracle
```
To find the wallet location, sign in to the primary database (the source database) instance with the SYSDBA administrator privilege.
```
sqlplus / as sysdba
```
Query the WRL_PARAMETER column of the V$ENCRYPTION_WALLET dynamic view to find the directory where the wallet is located.
```
SELECT * FROM V$ENCRYPTION_WALLET;
```
Exit SQL*Plus.
```
exit
```
Go to the directory where the wallet files are located.For example:
```
cd /u01/app/oracle/admin/source_db_unique_name
```

Use the tar command to compress the TDE wallet.For example:

tar cvf tde_wallet.tar ./tde_wallet

Output similar to the following appears:

./tde_wallet/
./tde_wallet/ewallet.p12
./tde_wallet/cwallet.sso
./tde_wallet/ewallet_2018021607225910.p12

Copy the TDE Wallet and Set Permissions on the Wallet Directory

After you back up the TDE wallet file, you must create a directory for the wallet and set permissions on this directory.

Copy the wallet tar file to a temp directory. For example:
```
cp tde_wallet.tar /tmp/
```
Exit twice to become the OCP user.
```
$ exit
# exit
```
Use SCP to copy the wallet files from the primary database (the source database) to the standby database (the target database), in the/opt/oracle/dcs/commonstore/wallets/tde/$ORACLE_UNQNAME directory.For example:
```
scp -i /home/opc/.ssh/privateKey /tmp/tde_wallet.tar opc@<Standby DB IP>:/tmp/
```
Output similar to the following appears:
```
tde_wallet.tar
100% 20KB 20.0KB/s 00:00
```
Use SSH to sign in to the target database server and then sign in as database software owner oracle.
Go to the target wallet directory.For example:
```
cd /opt/oracle/dcs/commonstore/wallets/tde
```
Check that the correct wallet is in this directory.
```
ls <Standby DB Unique Name>
```

Back up the wallet file.For example:

mv standby_db_unique_name standby_db_unique_name.old

Create a directory in which to store the wallet.For example:
```
mkdir standby_db_unique_name
```
Check the permissions on the wallet directory.
```
ls -ld standby_db_unique_name
```
If necessary, give the database software owner oracle read, write, and execute permissions.
```
chmod 700 standby_db_unique_name
```
Check the permissions again.
```
ls -ld standby_db_unique_name
```
Copy the wallet tar file to the current directory.
```
cp /tmp/tde_wallet.tar .
```

Check the permissions.

ls -rlt

Output similar to the following appears:

total 124
drwx------ 2 oracle oinstall 20480 Feb 16 09:25 standby_db_unique_name.old
drwx------ 2 oracle oinstall 20480 Feb 16 10:16 standby_db_unique_name
-rw-r--r-- 1 oracle oinstall 20480 Feb 16 10:17 tde_wallet.tar

Complete the TDE Wallet Process

You must extract the TDE wallet file tar and then move its contents to the wallet directory on the standby database (the target database).

On the primary database (the source database), ensure that you are in the correct wallet directory. For example:
```
pwd
 
# Output similar to the following should appear:
/opt/oracle/dcs/commonstore/wallets/tde
```

Extract the tar file.

tar xvf tde_wallet.tar

Output similar to the following should appear:

./tde_wallet/ewallet.p12
./tde_wallet/ewallet_2018050819024979.p12
./tde_wallet/cwallet.sso

Move the tde_wallet contents to the wallet directory on the standby database (the target database).
```
mv ./tde_wallet/* ./target_db_unique_name
```
Remove the tde_wallet contents from the primary database (the source database).
```
rm -rf ./tde_wallet
```

Configure the Standby Initialization Parameter File and Start the Instance in NOMOUNT Mode

After you configure the standby initialization file, then you can restart the database in NOMOUNT mode.

Use SSH to sign in to the standby database (the target database) server.
Sign in as the database software owner oracle.
```
su - oracle
```
Execute the oraenv script, which sets the $ORACLE_HOME environment variable.
```
. oraenv
```
Go to the dbs directory.
```
cd $ORACLE_HOME/dbs
```

Create a temporary initialization parameter file, named


                        init<Standby>.ora

. For example:

echo "*.db_name='standby_db_name'" > $ORACLE_HOME/dbs/initstandby_db_name.ora
echo "*.db_unique_name='standby_db_unique_name'" >> $ORACLE_HOME/dbs/initStandby_db_name.ora
echo "*.db_domain='standby_db_domain'" >> $ORACLE_HOME/dbs/initStandby_db_name.ora

Back up the existing password file, if one exists. For example:

mv $ORACLE_HOME/dbs/orapwtarget $ORACLE_HOME/dbs/orapwtarget.old

Create a new password file. For example:

orapwd file=$ORACLE_HOME/dbs/orapwtarget password=admin_password_for_primary entries=5

Connect to the standby database (the target database) instance as a user who has the SYSOPER administrator privilege. For example:
```
sqlplus / as sysoper
```

Shut down the database. For example:

shutdown immediate [ If the Database is already stopped, this may throw error]

Restart the database in NOMOUNT mode using the init_target.ora initialization parameter file.
```
startup force nomount PFILE=?/dbs/initStandby_db_name.ora
```

Duplicate the Target Database for the Standby from the Active Database

You can execute a script to duplicate the standby database (the target database). If the primary database (the source database) is large, then you can allocate additional channels to improve its performance. For a newly installed database, one channel typically runs the database duplication in a couple of minutes. Ensure that no errors occur after you run the Oracle Recovery Manager (Oracle RMAN) duplication operation. If errors occur, then restart the database by using the initialization parameter file (not spfile), in case it is generated under the $ORACLE_HOME/dbs directory as part of the Oracle RMAN duplication process.

Connect to the standby database (the target database) as the database software owner oracle.
```
su - oracle
```

Create a script file dup.rcv, where you will copy the commands and fill in the environment specific variables specified in the later step.

vi dup.rcv
run {
allocate channel prmy1 type disk;
allocate channel prmy2 type disk;
allocate channel prmy3 type disk;
allocate channel prmy4 type disk;
allocate auxiliary channel stby1 type disk;
allocate auxiliary channel stby2 type disk;
allocate auxiliary channel stby type disk;
duplicate target database for standby from active database dorecover
spfile
parameter_value_convert '/u02/app/oracle/oradata/<source_db_name>','+DATA'
set db_unique_name='<target_db_unique_name>'
set db_create_file_dest='+DATA'
set db_create_online_log_dest_1='+RECO'
set db_recovery_file_dest='+RECO'
set audit_file_dest='/u01/app/oracle/admin/db_name/adump'
set control_files='+DATA','+RECO'
set dg_broker_config_file1='+DATA/<target_db_unique_name>/dr1<target_db_unique_name>.dat'
set dg_broker_config_file2='+RECO/<target_db_unique_name>/dr2<target_db_unique_name>.dat'
set dispatchers='(PROTOCOL=TCP) (SERVICE=<target_db_name>XDB)'
set instance_name='<target_db_name>'
set db_domain='<target_db_domain>'
set db_recovery_file_dest='+RECO'
;
}

With the standby database (the target database) in NOMOUNT mode, connect to Oracle RMAN.

rman
RMAN> connect target sys@<primary_db_tnsnames_name>
target database Password: password
RMAN> connect auxiliary sys@<standby_db_tnsnames_name>
auxiliary database Password: password

Execute the following script to duplicate the target database for a standby database from an active database. The following example shows the dup.rcv script, which must be user-created, and is based on the My Oracle Support note 2369137. In this example, the dup.rcv script has been customized to push duplication (image copies) from the file system to Oracle Automatic Storage Management (Oracle ASM). Other options such as from the file system to Oracle Automatic Storage Management Cluster File System, or Oracle ASM to Oracle ASM, would require changes to the file destination parameters and the file name conversion parameters.

Modify the dup.rcv file with environment specific parameters.

@dup.rcv
RMAN> run {
2> allocate channel prmy1 type disk;
3> allocate channel prmy2 type disk;
4> allocate channel prmy3 type disk;
5> allocate channel prmy4 type disk;
6> allocate auxiliary channel stby1 type disk;
7> allocate auxiliary channel stby2 type disk;
8> allocate auxiliary channel stby type disk;
9> duplicate target database for standby from active database dorecover
10> spfile
11> parameter_value_convert '/u02/app/oracle/oradata/<source_db_name>','+DATA'
12> set db_unique_name='<target_db_unique_name>'
13> set db_create_file_dest='+DATA'
14> set db_create_online_log_dest_1='+RECO'
15> set db_recovery_file_dest='+RECO'
16> set audit_file_dest='/u01/app/oracle/admin/db_name/adump'
17> set control_files='+DATA','+RECO'
18> set dg_broker_config_file1='+DATA/<target_db_unique_name>/dr1<target_db_unique_name>.dat'
19> set dg_broker_config_file2='+RECO/<target_db_unique_name>/dr2<target_db_unique_name>.dat'
20> set dispatchers='(PROTOCOL=TCP) (SERVICE=<target_db_name>XDB)'
21> set instance_name='<target_db_name>'
22> set db_domain='<target_db_domain>'
23> set db_recovery_file_dest='+RECO'
24> ;
25> }

Post Oracle Recovery Manager Duplication Steps

After you complete the Oracle Recovery Manager (Oracle RMAN) duplication operation, you should perform clean-up tasks.

Enable Oracle Flashback

You should enable Oracle Flashback.

Use SSH to sign in to the standby database (the target database) server.
Sign in to the database instance as a user who has the SYSOPER administrator privilege. For example:
```
sqlplus / as sysoper
Enter password: password
```
Enable Oracle Flashback.
```
ALTER DATABASE FLASHBACK ON;
```
Connect as a user with the SYSDBA administrator privilege.
```
CONNECT / AS SYSDBA
```

Set the flashback retention target.

ALTER SYSTEM SET DB_FLASHBACK_RETENTION_TARGET=120;

Move the `spfile` File to Oracle Automatic Storage Management

You should move the spfile file to Oracle Automatic Storage Management.

Use SSH to connect to the standby database (the target database) server.
Sign in to the database instance as a user who has the SYSOPER administrator privilege.
Create and move the spfile file to Oracle Automatic Storage Management.
1. Create the pfile.
```
create pfile='/tmp/init<target_db_name>.ora' from spfile;
```
2. Shut down the database
```
shutdown immediate
```
3. Restart the database in MOUNT mode by using the initdb_name.ora file that you just created.
```
startup mount pfile='/tmp/init<target_db_name>.ora';
```
4. Create the spfile file.
```
create spfile='+DATA' from pfile='/tmp/init<target_db_name>.ora';
```
Exit SQL*Plus.
As the grid user, find the spfile file on Oracle Automatic Storage Management by using the asmcmd command.
```
asmcmd
ASMCMD> cd +DATA/<target_db_unique_name>/PARAMETERFILE/
ASMCMD> ls -lt
```
Output similar to the following appears:
```
Type           Redund  Striped  Time             Sys  Name
PARAMETERFILE  UNPROT  COARSE   APR 09 16:00:00  Y    spfile.262.973010033
```
Make a note of the ASM name (spfile.262.973010033), which you will need in the next task.

Change the init<target_db_name>.ora File to Reference the spfile File

You can modify the init<target_db_name>.ora file to reference the spfile file.

Use SSH to connect to the standby database (the target database) server.
Sign in as the database software owner oracle.
```
su - oracle
```
Execute the oraenv script to set the $ORACLE_HOME environment variable.
```
. oraenv
```
Go to the $ORACLE_HOME/dbs directory.
```
cd $ORACLE_HOME/dbs
```
Ensure that the init<target_db_name>.ora file is in this directory.
```
ls *.ora
```

Change the init<target_db_name>.ora file to refer to the spfile file.For example:

mv spfile<target_db_name>.ora spfile<target_db_name>.ora.stby
mv init<target_db_name>.ora init<target_db_name>.ora.stby
echo "SPFILE='+DATA/target_db_unique_name/PARAMETERFILE/spfile.262.973010033'" > init<target_db_name>.ora
cat init<target_db_name>.ora --To check the file

In this output, spfile.262.973010033 is the name of the file that you generated when you moved the spfile file to Oracle Automatic Storage Management in the previous task.

Output similar to the following appears:

SPFILE='+DATA/<target_db_unique_name>/PARAMETERFILE/spfile.262.973010033'

Modify and Start the Standby Database in MOUNT Mode

You can use the srvctl to modify and start the standby database (the target database).

Use SSH to sign in to the standby database (the target database) server.
Sign in as the database software owner oracle.
```
su - oracle
```

Use srvctl to modify and start the standby database (the target database) in MOUNT mode. For example:

srvctl modify database -db <target_db_unique_name> -role PHYSICAL_STANDBY -s "READ ONLY"  -spfile +DATA/target_db_unique_name/PARAMETERFILE/spfile.262.973010033 

srvctl config database -db <target_db_unique_name>

Sign in to the database instance as a user who has the SYSOPER administrator privilege.
```
sqlplus / as sysoper
```
Shut down the database, and then exit SQL*Plus.
```
SHUTDOWN IMMEDIATE
EXIT
```

Start the database in MOUNT mode by using srvctl.

srvctl start database -db <target_db_unique_name> -o mount

Query the V$DATABASE dynamic view to ensure that the database is in MOUNT mode.

SELECT NAME, OPEN_MODE FROM V$DATABASE;
 
#Output similar to the following appears: 
 
NAME              OPEN_MODE
--------------    ---------
source_db_name    MOUNTED

Set the Database and Log File Name Conversion Parameters on the Primary Database

You must set the conversion parameters for the database and the log file name on the primary database (the source database).

Use SSH to sign in to the primary database (the source database) server.
Sign in as the database software owner oracle.
```
sudo su - oracle
```
Sign in to the database instance as a user who has the SYSDBA administrator privilege. For example:
```
sqlplus / as sysdba
Enter password: password
```

Check the CONVERT parameter.

SHOW PARAMETER CONVERT#Output similar to the following appears:NAME                                 TYPE        VALUE
------------------------------------ ----------- ------
db_file_name_convert                 string
log_file_name_convert                string
pdb_file_name_convert                string

The VALUE column should be empty (null). If there is a value, then make a note of this value for after the migration is complete. After the migration is complete, these values are set to null.

Check the names of the data files.

SELECT NAME FROM V$DATAFILE;

Output similar to the following appears:

NAME
-----------------------------------------------------------------------
/u02/app/oracle/oradata/SOURCE_DB_NAME/system01.dbf
/u02/app/oracle/oradata/SOURCE_DB_NAME/sysaux01.dbf
/u02/app/oracle/oradata/SOURCE_DB_NAME/undotbs01.dbf
/u02/app/oracle/oradata/SOURCE_DB_NAME/pdbseed/system01.dbf
/u02/app/oracle/oradata/SOURCE_DB_NAME/users01.dbf
/u02/app/oracle/oradata/SOURCE_DB_NAME/pdbseed/sysaux01.dbf
/u02/app/oracle/oradata/SOURCE_DB_NAME/pdb1/system01.dbf
/u02/app/oracle/oradata/SOURCE_DB_NAME/pdb1/sysaux01.dbf
/u02/app/oracle/oradata/SOURCE_DB_NAME/pdb1/SAMPLE_SCHEMA_users01.dbf
/u02/app/oracle/oradata/SOURCE_DB_NAME/pdb1/example01.dbf

Note down the path in the output above.

Check the V$LOGFILE dynamic view.

SELECT MEMBER FROM V$LOGFILE;Output similar to the following appears:MEMBER
-------------------------------------------------------------------
/u04/app/oracle/oradata/redo/redo03.log
/u04/app/oracle/oradata/redo/redo02.log
/u04/app/oracle/oradata/redo/redo01.log
/u03/app/oracle/fast_recovery_area/SOURCE_DB_NAME/onlinelog/o1_mf_4_fddlmffq_.log
/u03/app/oracle/fast_recovery_area/SOURCE_DB_NAME/onlinelog/o1_mf_5_fddlvjo1_.log
/u03/app/oracle/fast_recovery_area/SOURCE_DB_NAME/onlinelog/o1_mf_6_fddlvjs4_.log
/u03/app/oracle/fast_recovery_area/SOURCE_DB_NAME/onlinelog/o1_mf_7_fddlvjys_.log
/u03/app/oracle/fast_recovery_area/SOURCE_DB_NAME/onlinelog/o1_mf_8_fddlvk7x_.log
/u03/app/oracle/fast_recovery_area/SOURCE_DB_NAME/onlinelog/o1_mf_9_fddlvkfj_.log

Note down the path in the output above.

Use the information from this output to set the DB_FILE_NAME_CONVERT parameter.
Note:
Note that the name of the source database in this output is case sensitive.
```
ALTER SYSTEM SET DB_FILE_NAME_CONVERT='+DATA',
'/u02/app/oracle/oradata/SOURCE_DB_NAME/' SID='*' SCOPE=SPFILE;
```

Set the LOG_FILE_NAME_CONVERT parameter. For example:

ALTER SYSTEM SET LOG_FILE_NAME_CONVERT='+RECO','/u04/app/oracle/redo/','+RECO',
'/u03/app/oracle/fast_recovery_area/SOURCE_DB_NAME/onlinelog/' SID='*' SCOPE=SPFILE;

Restart the database.
```
SHUTDOWN IMMEDIATE,
STARTUP
```

Set the Database and Log File Name Conversion Parameters on the Standby Database

You must set the conversion parameters for the database and the log file name on the standby database (the target database).

Use SSH to sign in to the standby database (the target database) server.
Sign in to the database instance as a user who has the SYSDBA administrator privilege. For example:
```
sqlplus / as sysdba
```

Check the CONVERT parameter.

SHOW PARAMETER CONVERTOutput similar to the following appears:NAME                                 TYPE        VALUE
------------------------------------ ----------- ------
db_file_name_convert                 string
log_file_name_convert                string
pdb_file_name_convert                string

The VALUE column should be empty (null). If there is a value, then make a note of this value for after the migration is complete. After the migration is complete, these values are set to null.

Check the names of the data files.

SELECT NAME FROM V$DATAFILE;Output similar to the following appears:NAME
------------------------------------------------
+DATA/target_db_unique_name/DATAFILE/system.273.972998889
+DATA/target_db_unique_name/DATAFILE/sysaux.272.972998889
+DATA/target__unique_name/DATAFILE/undotbs1.270.972998945
+DATA/target_db_unique_name/690A484F7D3F1B6EE05332C6120A3C84/DATAFILE/system.266.972998961
+DATA/target_db_unique_name/DATAFILE/users.263.972998969
+DATA/target_db_unique_name/690A484F7D3F1B6EE05332C6120A3C84/DATAFILE/sysaux.269.972998945
+DATA/target_db_unique_name/690A76A8ED011E29E05332C6120AD40F/DATAFILE/system.265.972998945
+DATA/target_db_unique_name/690A76A8ED011E29E05332C6120AD40F/DATAFILE/sysaux.264.972998889
+DATA/target_db_unique_name/690A76A8ED011E29E05332C6120AD40F/DATAFILE/users.261.972998971
+DATA/target_db_unique_name/690A76A8ED011E29E05332C6120AD40F/DATAFILE/example.267.972998887

Check the V$LOGFILE dynamic view.

SELECT MEMBER FROM V$LOGFILE;Output similar to the following appears:MEMBER
-------------------------------------------------------------------
+RECO/target_db_unique_name/ONLINELOG/group_3.264.972998987
+RECO/target_db_unique_name/ONLINELOG/group_2.263.972998987
+RECO/target_db_unique_name/ONLINELOG/group_1.257.972998985
+RECO/target_db_unique_name/ONLINELOG/group_4.265.972998987
+RECO/target_db_unique_name/ONLINELOG/group_5.266.972998987
+RECO/target_db_unique_name/ONLINELOG/group_6.267.972998989
+RECO/target_db_unique_name/ONLINELOG/group_7.268.972998989
+RECO/target_db_unique_name/ONLINELOG/group_8.269.972998989
+RECO/target_db_unique_name/ONLINELOG/group_9.270.972998989

Use the information from this output to set the

DB_FILE_NAME_CONVERT

parameter.For example:

ALTER SYSTEM SET DB_FILE_NAME_CONVERT='/u01/app/oracle/oradata/source_db_name/','+DATA' SID='*' SCOPE=SPFILE;

Set the LOG_FILE_NAME_CONVERT parameter. For example:

ALTER SYSTEM SET LOG_FILE_NAME_CONVERT='/u01/app/oracle/oradata/source_db_name/',
'+RECO','/u01/app/oracle/fast_recovery_area/SOURCE_DB_NAME/onlinelog/','+RECO'
SID='*' SCOPE=SPFILE;

Restart the database.

srvctl stop database -db target_db_unique_name
srvctl startup database -db target_db_unique_name -o mount

Configure the Database with Oracle Data Guard Broker

You can use the dbmgrl utility to configure either the primary database (the source database) or the standby database (the target database) with Oracle Data Guard Broker..

Use SSH to sign in to the primary database (the source database) or the standby database (the target database) server.
Start the dgmgrl command line utility as user SYS from either the primary or the standby database system. For example, to log in to a primary database whose TNS name is OCIC-ORCL:
```
dgmgrl sys@ocic-orcl
Enter password: password
```

Using the dbmgrl utility, create the Oracle Data Guard configuration and identity for the primary and standby databases. For example:

create configuration configuration_name as primary database is source_db_unique_name connect identifier is OCIC-ORCL; -- Uses the source TNS name
 
add database target_db_unique_name as connect identifier is OCI-ORCL; --Uses the target TNS name

Enable the configuration.
```
enable configuration
```

Show the Oracle Data Guard configuration on the standby database.

show configurationORA-16792 configuration property value is inconsistent with database setting>> As a workaround enable property <<dg_broker> on Primary database.#Output similar to the following appears:Configuration - configuration_name
  Protection Mode: MaxPerformance
  Members:
  source_db_unique_name           - Primary database
    target_db_unique_name         - Physical standby database
 
Fast-Start Failover: DISABLED
 
Configuration Status:
SUCCESS   (status updated 12 seconds ago)

Validate Oracle Data Guard Broker on the Primary Database and the Standby Database

You can use SQL*Plus to validate Oracle Data Guard Broker on the primary database (the source database) and the standby database (the target database).

Validate Oracle Data Guard Broker on the Primary Database

You can use SQL*Plus to validate Oracle Data Guard Broker on the primary database (the source database).

Use SSH to sign in to the primary database (the source database) server.
Connect as a user who has the SYSDBA administrator privilege. For example, for a primary database whose TNS name is OCIC-ORCL:
```
connect sys@ocic-orcl as sysdba
Enter password: password
```

Query the V$DATABASE dynamic view.

SELECT FORCE_LOGGING, FLASHBACK_ON, OPEN_MODE, DATABASE_ROLE, SWITCHOVER_STATUS, DATAGUARD_BROKER, PROTECTION_MODE FROM V$DATABASE;Output similar to the following appears:FORCE_LOGGING                           FLASHBACK_ON       OPEN_MODE
--------------------------------------- ------------------ -----------
DATABASE_ROLE    SWITCHOVER_STATUS    DATAGUAR PROTECTION_MODE
---------------- -------------------- -------- --------------------
YES                                     YES                READ WRITE
PRIMARY          TO STANDBY           ENABLED  MAXIMUM PERFORMANCE

In the output, the DATABASE_ROLE should be PRIMARY and OPEN_MODE should be READ WRITE.

Validate Oracle Data Guard Broker on the Standby Database

You can use SQL*Plus to validate Oracle Data Guard Broker on the standby database (the target database).

Use SSH to sign in to the standby database (the target database) server.
Connect as a user who has the SYSDBA administrator privilege.

Query the V$DATABASE dynamic view.

SELECT FORCE_LOGGING, FLASHBACK_ON,
OPEN_MODE, DATABASE_ROLE, SWITCHOVER_STATUS,
DATAGUARD_BROKER, PROTECTION_MODE
FROM V$DATABASE;

Output similar to the following appears:

FORCE_LOGGING                           FLASHBACK_ON       OPEN_MODE
--------------------------------------- ------------------ -----------
DATABASE_ROLE    SWITCHOVER_STATUS    DATAGUAR PROTECTION_MODE
---------------- -------------------- -------- --------------------
YES                                     YES                MOUNTED
PHYSICAL STANDBY NOT ALLOWED          ENABLED  MAXIMUM PERFORMANCE

The output should show DATABASE_ROLE as PHYSICAL STANDBYand OPEN_MODE as MOUNTED.

Verify that the Oracle Data Guard processes are initiated in the standby database.

SELECT PROCESS,PID,DELAY_MINS FROM V$MANAGED_STANDBY;

Output similar to the following appears:

PROCESS   PID                      DELAY_MINS
--------- ------------------------ ----------
ARCH      9207                              0
ARCH      9212                              0
ARCH      9216                              0
ARCH      9220                              0
RFS       1065                              0
RFS       1148                              0
RFS       1092                              0
MRP0      972                               0
RFS       1208                              0

The output should indicate that the processes are running with little or no delay. If the DELAY_MINS for MRP0, the databases are synchronized.

Check theLOG_ARCHIVE_DEST parameter.

SHOW PARAMETER LOG_ARCHIVE_DEST_

Output similar to the following appears:

NAME                         TYPE      VALUE
---------------------------- --------- -----------------------------
log_archive_dest_1           string       
                                       location=USE_DB_RECOVERY_FILE_
                                       DEST, valid_for=(ALL_LOGFILES,
                                       ALL_ROLES)
log_archive_dest_10          string
log_archive_dest_11          string
log_archive_dest_12          string
log_archive_dest_13          string
log_archive_dest_14          string
log_archive_dest_15          string
...
log_archive_dest_2           string    service="oci-orcl", ASYNC
                                       NOAF FIRM delay=0 optional
                                       compression=disable
                                       max_failure=0 max_connections
                                       =1 reopen=300 db_unique_name=
                                       "source_db_unique_name"
                                       net_timeout=30, valid_for=
                                       (online_logfile,all_roles)
...

The output should be similar to the output for log_archive_dest_2, with the service pointing to the standby database (the target database), which in this example is oci-orcl.

Check the LOG_ARCHIVE_CONFIG parameter.

SHOW PARAMETER LOG_ARCHIVE_CONFIG#

Output similar to the following appears:


NAME                         TYPE      VALUE
---------------------------- --------- -----------------------------------------------------------
log_archive_config           string    dg_config=(source_db_unique_name,target_db_unique_name)

Check the FAL_SERVER parameter.

SHOW PARAMETER FAL_SERVER

Output similar to the following appears:


NAME                        TYPE      VALUE
--------------------------- --------- ----------
fal_server                  string    <tns_entry_of_primary>

Check the LOG_ARCHIVE_FORMAT parameter.

SHOW PARAMETER LOG_ARCHIVE_FORMAT

Output similar to the following appears:


NAME                        TYPE      VALUE
--------------------------- --------- --------------
log_archive_format          string    %t_%s_%r.dbf

Complete the Validation on the Primary Database

You can use dgmrgl to complete the Oracle Data Guard Broker validation on the primary database (the source database).

Use SSH to sign in to the primary database (the source database) server.
Repeat steps 5 through 8 in the topic Validate Oracle Data Guard Broker on the Standby Database on the primary database (the source database).
Start the dgmgrl command line utility:
```
dgmgrl
```
Connect as user SYS from either the primary or the standby database system. For example, to log in to a primary database whose TNS name is OCIC-ORCL:
```
connect sys@primary_db_tnsnames_name
Enter password: password
```

Check the Oracle Data Guard configuration.

show configuration verbose

Output similar to the following appears:

Configuration - configuration_name
 
  Protection Mode: MaxPerformance
  Members:
  source_db_unique_name           - Primary database
    target_db_unique_name         - Physical standby database
 
  Properties:
    FastStartFailoverThreshold      = '30'
    OperationTimeout                = '30'
    TraceLevel                      = 'USER'
    FastStartFailoverLagLimit       = '30'
    CommunicationTimeout            = '180'
    ObserverReconnect               = '0'
    FastStartFailoverAutoReinstate  = 'TRUE'
    FastStartFailoverPmyShutdown    = 'TRUE'
    BystandersFollowRoleChange      = 'ALL'
    ObserverOverride                = 'FALSE'
    ExternalDestination1            = ''
    ExternalDestination2            = ''
    PrimaryLostWriteAction          = 'CONTINUE'
 
Fast-Start Failover: DISABLED

Check the status on the standby database (the target database). For example:
```
show database verbose target_db_unique_name
```
After you complete these steps, you must test that the Oracle Data Guard configuration is functioning as expected by performing switchover operations in both directions.

Perform the Migration

To complete the migration, you must perform a switchover operation from the primary database (the source database) to the standby database (the target database).

Use SSH to sign in to the primary database (the source database) server.
Start the dgmgrl utility. For example, for a source database whose TNS name is OCIC-ORCL:
```
dgmgrl sys@ocic-orcl
Enter password: password
```
Check the configuration.
```
show configuration verbose
```
In the configuration verbose output, check the StaticConnectIdentifier setting.
This setting should point to the standby database (the target database) connection ID. The Database Status setting should say SUCCESS.

If necessary, use dgmgrl to change the StaticConnectIdentifier setting to point to the correct TNS net services name. For example:

edit database source_db_unique_name set property staticConnectidentifier='source_TNS_name';
edit database target_db_unique_name set property staticConnectidentifier='target_TNS_name';

Check the configuration for the primary database (the source database).
```
show database verbose source_db_unique_name
```
The database verbose output should show that the role is primary and the setting for StaticConnectIdentifier is the same as DGConnectIdentifier.
Perform a switchover operation to the standby database (the target database).
```
switchover to target_db_unique_name
```
The output should indicate that the switchover operation is occurring between the two databases.

Post-Migration Steps

After you complete the migration of an Oracle database from an Oracle Cloud Infrastructure Compute Classic server to an Oracle Cloud Infrastructure server that uses a Virtual Machine Database system, you should validate the migration, and then remove the configuration from the primary database (the source database).

Test the Oracle Data Guard Configuration on the Standby Database

At this stage, the target database is now the primary database. The source database is now the standby database.

You can test the Oracle Data Guard connection on the target database, by performing a switchover operation with the source database. This switchover operation will make the target database take the standby role again. The purpose of this test is to prove that you can return to the original configuration in case the target database is not functional.

Use SSH to sign in to the standby database (the target database) server.

Start the dgmgrl utility. For example:

dgmgrl sys@target_db
Enter password: password

Perform a switchover operation to the source database, which will make the target database take the standby role.
```
switchover to source_db_unique_name;
```
The output should indicate that the switchover operation is occurring between the two databases.
(Optional) To prevent changes to the new standby database until the new primary database is determined to be fully functional, temporarily disable the Redo Apply feature.
```
edit database source_db_unique_name set state = 'APPLY-OFF';
```
If you perform another switchover operation so that the target database is now the standby database, you can perform an APPLY-OFF operation to prevent the source database from being updated. This enables the target database to be put in service, and keeps the source database as a point-in-time backup in case of a logical failure in the new configuration.

(Optional) To restart the apply feature:

edit database source_db_unique_name set state = 'APPLY-ON';

Exit dgmgrl.
```
exit
```
Perform a switchover operation to the target database, which will make the source database the standby role.
```
switchover to target_db_unique_name;
```
The output should indicate that the switchover operation is occurring between the two databases.
Test the connection to the new primary database. For example, after exporting the target unique name, connect as user SYS and select from an encrypted table space. In this example, the HR.EMPLOYEES table is encrypted.
```
exit
```
Test the connection to the new primary database. For example, after exporting the target unique name, connect as user SYS and select from an encrypted table space. In this example, the HR.EMPLOYEES table is encrypted.
```
export ORACLE_UNQNAME=target_db_unique_name
 
sqlplus sys@target_TNS_name
Password: password
 
SQL> ALTER SESSION SET CONTAINER = PDB1;
SQL> SELECT * FROM HR.EMPLOYEES;
 
SQL> EXIT
```

Clean Up the Standby Database

After you complete and test the migration, you can remove the Oracle Data Guard configuration from the standby database (the target database). You do not need to remove the original source database. At this stage, the standby database is the new source database.

Use SSH to sign in to the standby database (the target database) server and sign in to the Oracle Data Guard dgmgrl utility.
Check the configuration.
```
show configuration
```
If the configuration does not show Protection Mode: MaxPerformance, then set Oracle Data Guard to use the MaxPerformance protection mode.
```
edit configuration set protection mode as maxperformance
```

Disable and then remove the configuration.

edit database source_db_unique_name set state = 'APPLY-OFF';
 
disable configuration;
 
remove configuration;
 
exit

Connect to the database instance as a user who has the SYSDBA administrator privilege.For example:
```
sqlplus / as sysdba
```
Check the DG_BROKER_CONFIG_FILE parameters.
```
SHOW PARAMETER DB_BROKER_CONFIG_FILE
```
The output should list the associated data and recovery files for this configuration, typically named dg_broker_config_file1 and dg_broker_config_file2.
Start another terminal window, and sign in to asmcmd as the grid user.
Remove the Oracle Data Guard configuration files that were listed when you checked the DG_BROKER_CONFIG_FILE parameters.
Return to the window that is running SQL*Plus.

Execute the following ALTER SYSTEM statements:

ALTER SYSTEM SET DG_BROKER_START=FALSE SID='*' SCOPE=BOTH;
ALTER SYSTEM SET DG_BROKER_CONFIG_FILE1='' SID='*' SCOPE=SPFILE;
ALTER SYSTEM SET DG_BROKER_CONFIG_FILE2='' SID='*' SCOPE=SPFILE;
ALTER SYSTEM RESET LOG_ARCHIVE_CONFIG SID='*' SCOPE=SPFILE;

Check the following parameters:

SHOW PARAMETER DB_FILE_NAME_CONVERT
SHOW PARAMETER LOG_FILE_NAME_CONVERT
SHOW PARAMETER LOG_ARCHIVE_DEST
SHOW PARAMETER LOG_ARCHIVE_DEST_STATE
SHOW PARAMETER STANDBY_ARCHIVE_DEST
SHOW PARAMETER FAL

If any of the preceding parameters is set, then reset the parameters to use blank values. For example, for STANDBY_ARCHIVE_DEST:
```
ALTER SYSTEM SET STANDBY_ARCHIVE_DEST='' SID='*' SCOPE=SPFILE;
```
Restart the database.
```
SHUTDOWN IMMEDIATE
STARTUP
```

Drop the standby logs from the primary database (the source database).

Find the group numbers for the standby database redo logs that are on the new primary database (which was formerly the target database).
```
SELECT GROUP# FROM V$STANDBY_LOG;Output similar to the following appears:    GROUP#
----------
         5
         6
         7
         8
         9
```

Remove the standby logs. For example:

ALTER DATABASE DROP STANDBY LOGFILE GROUP 5;
ALTER DATABASE DROP STANDBY LOGFILE GROUP 6;
ALTER DATABASE DROP STANDBY LOGFILE GROUP 7;
ALTER DATABASE DROP STANDBY LOGFILE GROUP 8;
ALTER DATABASE DROP STANDBY LOGFILE GROUP 9;

(Optional) Change the DB_BLOCK_CHECKSUM and DB_BLOCK_CHECKING parameters.
The default values are DB_BLOCK_CHECKSUM=TYPICAL and DB_BLOCK_CHECKING=FALSE.
Exit SQL*Plus.
```
EXIT
```

Reapply Rolled Back Patches (if any) on Primary

After you complete the migration, you should reapply the patches(if any) that you had rolled back as part of the Prepare section. This step should be performed on primary database.

Note:

This step is applicable ONLY if you had applied patch for bug 18633374 in the Prepare step, and have rolled back any patches as part of that procedure.

Login to the primary database as oracle
Roll back patch 18633374.
```
$ORACLE_HOME/OPatch/opatch rollback -id 18633374
```
Wait for the roll back to complete.
Go to My Oracle Support (MOS) page. Use the Search box to find the MOS note for the patch number that was rolled back as part of Prepare step .
Follow the instructions in the ReadMe file to reapply the patch.
Repeat the steps 2 and 3 for all the patches that were rolled back.

Configure the Primary (Source) Database

Configure the Primary Database for the Standby Database

Add Static Services to the Primary Database listener.ora File

Configure the Primary Database Parameters

Configure the Standby (Target) Database

Drop Standby database

Add Static Services to the Standby Database listener.ora File

Copy TDE Wallets from the Primary Database to the Standby Database

Compress the TDE Wallet

Copy the TDE Wallet and Set Permissions on the Wallet Directory

Complete the TDE Wallet Process

Configure the Standby Initialization Parameter File and Start the Instance in NOMOUNT Mode

Duplicate the Target Database for the Standby from the Active Database

Post Oracle Recovery Manager Duplication Steps

Enable Oracle Flashback

Move the spfile File to Oracle Automatic Storage Management

Change the init<target_db_name>.ora File to Reference the spfile File

Modify and Start the Standby Database in MOUNT Mode

Set the Database and Log File Name Conversion Parameters on the Primary Database

Set the Database and Log File Name Conversion Parameters on the Standby Database

Configure the Database with Oracle Data Guard Broker

Validate Oracle Data Guard Broker on the Primary Database and the Standby Database

Validate Oracle Data Guard Broker on the Primary Database

Validate Oracle Data Guard Broker on the Standby Database

Complete the Validation on the Primary Database

Perform the Migration

Post-Migration Steps

Test the Oracle Data Guard Configuration on the Standby Database

Clean Up the Standby Database

Reapply Rolled Back Patches (if any) on Primary

Add Static Services to the Primary Database `listener.ora` File

Move the `spfile` File to Oracle Automatic Storage Management