Oracle EBS R12 - Use Rman to Clone Oracle EBS R12.1.1 without shutting down source Database and MT-白红宇

Oracle EBS R12 - Use Rman to Clone Oracle EBS R12.1.1 without shutting down source Database and MT

阅读量：4177 次

发布时间：2019-05-26

本文共 9534 字，大约阅读时间需要 31 分钟。

Oracle EBS R12 - Use Rman to Clone Oracle EBS R12.1.1 without shutting down source Database and Middle Tier

This article is based on below Note:

Cloning Oracle Applications Release 12 with Rapid Clone (Doc ID 406982.1)

Tested on r12.1.1 Oracle linux 5.7 x64

===========================================================

Section 1: Prerequisite Tasks

----------------------------------------------------------

Apply the latest AD patch

Table 2.b: Release 12.1 AD patches

Patch Description

9239089 R12.AD.B.DELTA.3

Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release 12 (Doc ID 387859.1)

Patch 8919489 contains the latest TXK product patches for 12.1.X customers).

For Release 12.1:

Apply patches as listed in Table 3.b.

Table 3.b: Release 12.1 Rapid Clone patches

Patch Description

9171651:R12.OAM.B 12.1 RAPIDCLONE CONSOLIDATED FIXES JUL/2010

9833058:R12.OAM.B HOT CLONE FAILS WITH ORA-00201 DURING RECOVERY MANAGER

12404574:R12.OAM.B ORACLE_HOME REGISTRATION DOES NOT HAPPEN WITH CENTRAL INVENTORY ON LOZ

12598630:R12.OAM.B R12.1 ONE-OFF FOR S_DB_LISTENER BUG 12362010

15969020:R12.OAM.B APPSST12C: INCORRECT DIRECTORY WHEN RUNNING ADCFGCLONE.PL

16958896:R12.OAM.B R12.1 FWDPRT BUG16958392 TCH12C: ADCFGCLONE.PL FAILURE DUE TO DEPRECATED PARAM

13942692:R12.OAM.B ADPRECLONE.PL FAILS INTERMITTENTLY ON DB TIER WHILE CHECKING LISTENER STATUS

select bug_number,last_update_date from ad_bugs where bug_number in (9239089,8919489,9171651,9833058,12404574,12598630,15969020,16958896,13942692);

R12.1.1 only installed below patches:
select bug_number,last_update_date from ad_bugs where bug_number='9239089';
select bug_number,last_update_date from ad_bugs where bug_number in (12404574,12598630,13942692,15969020,8919489,9171651,9583541,9833058);

----------------------------------------------------------

Run AutoConfig on the application tiers

On Unix:

sh <INST_TOP>/admin/scripts/adautocfg.sh

Attention:

The database server and the database listener must remain available during the AutoConfig run. Only the application tier servers should be shut down.

Running AutoConfig may change your existing environment files. After running AutoConfig, you should always set the environment before you run any Applications utilities, in order to apply the changed environment variables.

----------------------------------------------------------

Synchronize appsutil on the database tier nodes

Copy AutoConfig to the RDBMS ORACLE_HOME

Update the RDBMS ORACLE_HOME file system with the AutoConfig files by performing the following steps:

On the application tier (as the APPLMGR user):

Create appsutil.zip file

perl <AD_TOP>/bin/admkappsutil.pl

This will create appsutil.zip in <INST_TOP>/admin/out

On the database tier (as the ORACLE user):

Copy or FTP the appsutil.zip file to the <RDBMS ORACLE_HOME>

cd <RDBMS ORACLE_HOME>

unzip -o appsutil.zip

----------------------------------------------------------

Run AutoConfig on the database tier

Running AutoConfig on the database tier is required in the following scenarios:

After migrating a patch to the database tier, the Check Config utility reports any potential changes to the templates.

After customizations on the database tier

After a database or application tier upgrade

After restoration of the database or Oracle Home from a backup tape

After a JDK upgrade on the database tier

After the Net Services Topology Information is manually cleaned up using one of the supported procedures(eg. fnd_conc_clone.setup_clean). Subsequently, AutoConfig must be run on the application tier nodes.

After registration of a RAC node.

After setting up the APPL_TOP on a shared file system.

All other cases where documentation says that AutoConfig should be run on the database tier.

Execute the following command to run AutoConfig on the database tier.

On Unix:

sh <RDBMS_ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>/adautocfg.sh

Attention:

The database server and the database listener must remain available during the AutoConfig run. All the other database tier services should be shut down.

----------------------------------------------------------

Maintain Snapshot Information

Log in to each application tier node as the APPLMGR user, and run "Maintain Snapshot Information" in AD Administration. To update the snapshot, please select the following options "Update Current View Snapshot" and "Update Complete APPL_TOP".

===========================================================

Section 2: Cloning Tasks

----------------------------------------------------------

Prepare the source system database tier for cloning

Log on to the source system as the ORACLE user, and run the following commands:

$ cd [RDBMS ORACLE_HOME]/appsutil/scripts/[CONTEXT_NAME]

$ perl adpreclone.pl dbTier

----------------------------------------------------------

Prepare the source system application tier for cloning

Log on to the source system as the APPLMGR user, and run the following commands on each node that contains an APPL_TOP:

$ cd [INST_TOP]/admin/scripts

$ perl adpreclone.pl appsTier

----------------------------------------------------------

Copy the source system to the target system

----------------------------------------------------------

Copy the database node file system

Copy the source database ORACLE_HOME to the target system

----------------------------------------------------------

Configure the target system database server

Option 6: Cloning the Database Separately

Log on to the target system as the ORACLE user

Configure the [RDBMS ORACLE_HOME]

$ cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
$ perl adcfgclone.pl dbTechStack #does not require datafiles or control files, neither require database started.

Create the target database control files manually

#dbTechStack will configure the target database ORACLE_HOME but it will not create controlfiles or open the database.

#You need to use dbTechStack when you clone the database using hotbackup as you will need to create/open the database manually (not by Rapid Clone).

https://community.oracle.com/thread/856080

In this step, you copy and recreate the database using your preferred method, such as RMAN restore, Flash Copy, Snap View, or Mirror View.

db_name='DEV'
control_files='/u04/xxx/xx.cntl','/u04/xxx/xx.cntl','/u04/xxx/xx.cntl'

db_file_name_convert =('/u01/finsys/db/apps_st/data', '/u01/finsys/db/apps_st/data1') #not necessary

log_file_name_convert =('/u01/finsys/db/apps_st/data', '/u01/finsys/db/apps_st/data1') #not necessary

orapwd file=$ORACLE_HOME/orapwPROD password=oracle entries=5

orapwd file=$ORACLE_HOME/orapwDEV password=oracle entries=5

add tns entry to $TNS_ADMIN/tnsnames.ora

rman target sys/sys@TEST auxiliary /

rman target sys/oracle@prod auxiliary sys/oracle@DEV

duplicate target database to DEV from active database;

duplicate target database to DEV from active database nofilenamecheck;

select sid,serial#,sofar,totalwork,TIME_REMAINING,ELAPSED_SECONDS,MESSAGE from v$session_longops where opname like 'RMAN:%' and TIME_REMAINING >0;

select sid,username,client_info from v$session where client_info is not null;

SELECT SID, SERIAL#, CONTEXT, SOFAR, TOTALWORK,

ROUND(SOFAR/TOTALWORK*100,2) "%_COMPLETE"

FROM V$SESSION_LONGOPS

WHERE OPNAME LIKE 'RMAN%'

AND OPNAME NOT LIKE '%aggregate%'

AND TOTALWORK != 0

AND SOFAR <> TOTALWORK

;

https://www.stanford.edu/dept/itss/docs/oracle/10gR2/backup.102/b14191/advmaint006.htm

Start the target database in open mode

Run the library update script against the database

$ cd [RDBMS ORACLE_HOME]/appsutil/install/[CONTEXT NAME]

$ sqlplus "/ as sysdba" @adupdlib.sql [libext]

Where [libext] should be set to 'sl' for HP-UX, 'so' for any other UNIX platform, or 'dll' for Windows.

Configure the target database

The database must be running and open before performing this step.

$ cd [RDBMS ORACLE_HOME]/appsutil/clone/bin

$ perl adcfgclone.pl dbconfig [Database target context file]

Where Database target context file is: [RDBMS ORACLE_HOME]/appsutil/[Target CONTEXT_NAME].xml.

Note: The dbconfig option will configure the database with the required settings for the new target, but it will not recreate the control files.

----------------------------------------------------------

Copy the application tier file system

Log on to the source system application tier nodes as the APPLMGR user and shut down the application tier server processes. Copy the following application tier directories from the source node to the target application tier node:

[APPL_TOP]

[COMMON_TOP]

Applications Technology Stack:

[OracleAS Tools ORACLE_HOME]

[OracleAS Web IAS_ORACLE_HOME]

----------------------------------------------------------

Configure the target system application tier server nodes

Log on to the target system as the APPLMGR user and enter the following commands:

$ cd [COMMON_TOP]/clone/bin

$ perl adcfgclone.pl appsTier

===========================================================

Section 3: Finishing Tasks