Post Clone Checks,Procedures for 11i / R12

Post Clone Checks,Procedures for 11i / R12

Clone Procedures are outlined in :
Clone-ie-Refresh-Oracle-Applications-11i-R12
Cloning-from-Multinode-to-Single-Node-Merge-APPL_TOP

Post Clone checks and steps can differ .
Listed are some of the common Post clone activities :

(Here DEV is the target and PROD is the source)

CHECKS
===========

THE CHECKS/STEPS LISTED HERE SHOULD BE PERFORMED AFTER DATABASE CLONE BEFORE APPLICATIONS CLONE

1 Check the Target - If its in ARCHIVELOG / NOARCHIVELOG MODE as desired.

2 Create the Temp datafiles , using the commands taken from the control file , if the temporary tablespace tempfiles is not existing.

ALTER TABLESPACE TEMP ADD TEMPFILE __________

Verify dba_temp_files, for all the temp file entries added to TEMP

SQL> select file_name from dba_temp_files;

Check for the Default Temporary file –
===========================
select * from database_properties where property_name = 'DEFAULT_TEMP_TABLESPACE';

Confirm that this TEMP.
If the default is not TEMP,

SQL>alter database default temporary tablespace TEMP

3 Update global_name if it contains source

select * from global_name;
update global_name set global_name='<global db name>';
commit;

SQL> select * from global_name;

GLOBAL_NAME
--------------------------------------------------------------------------------
DEV

4 Restoration of files backed up on Target Instance prior to the clone.

- You may need to restore the tnsnames.ora , listener.ora (which was backed up for the target instance prior to clone)
- You may need to restore the spfile/init file , so that the target instance takes the original init parameters (memory/performance parameters) and restart the database.

5 Change the directories – if any need to be changed

set heading off
set pages 1000
set linesize 100
select 'CREATE OR REPLACE DIRECTORY '||DIRECTORY_NAME||' AS '||''''||DIRECTORY_PATH||''''||';'
from all_directories;
spool off

- Edit the commands by replacing PROD with DEV ie source with target and Execute.

- You would also be required to check and recreate the DB links as per tns entries and requirements in the Target Instance.


6 Update apps.wf_systems
(This should show the target Instance and not the source Instance)

SQL>select name,display_name from apps.wf_systems;
SQL>update apps.wf_systems set name=’<SID>’,display_name=’ <SID>.<hostname.domainname>’;
SQL>COMMIT;

Example after change
SQL> select name,display_name from apps.wf_systems;

NAME DISPLAY_NAME
------------------------------ --------------------------------------------------------------------------------
DEV DEV.DBALOUNGE.COM


7 Update Notification status
(This needs to be bone before running adcfgclone on the apps tier , to avoid any Notifications to be sent from the Target Instance)

UPDATE wf_notifications SET status ='CLOSED', mail_status ='SENT', end_date ='01-JAN-01' WHERE mail_status in ('MAIL','INVALID','OPEN') ;

Commit;

update wf_agents set address = replace ( address,'PROD','DEV' ) ;
select name ,display_name from wf_systems;

update wf_systems set
DISPLAY_NAME = replace ( DISPLAY_NAME, 'PROD.DBALOUNGE.COM','DEV.DBALOUNGE.COM');

Commit;


8 Update the target node in CM fnd_concurrent_queues table :

update fnd_concurrent_queues set node_name='<target_conc_node>' where node_name='<source_conc_node>';

commit;

THE CHECKS/STEPS LISTED HERE SHOULD BE PERFORMED AFTER APPLICATIONS CLONE BUT with APPS SERVICES DOWN

9 You may want to Restore the backed up target xml file (DEV xml) file to its proper location.
We may want to use the same xml file which was in place prior to the clone so that the same ports / configuration is in use.

10 remove the log files from APPLCSF/APPLLOG:

Make sure Dir are existing ; Use command to confirm
cd $APPLCSF/$APPLLOG

Delete all files under $APPLCSF/$APPLLOG


11 You can set the logfile to NULL

update fnd_concurrent_requests set logfile_name = null, logfile_node_name = null,
outfile_name = null, outfile_node_name = null;

commit;

12 You may need to run

exec FND_CONC_CLONE.SETUP_CLEAN;
commit;

to clear FND_NODES entries and rerun autoconfig (on all application tiers) as per step given below

For Details , Refer to : How-to-cleanup-FND_NODES-table-to-clear-corrupted-setup

13 Run Autoconfig

14. Change apps , system and sysadmin and a module specific passwords.
Change apps password in wdbsvr.app and CGIcmd.dat files

Refer to :
FNDCPASS-to-Change-Passwords

15 Log in to the target system application tier node as the applications User

Run the following tasks in adadmin for all products:
- generate JAR files
- generate message files
- relink executables


16 Run cmclean.sql
(This may be required to clean Concurrent Queue Status and Request Status)


THE CHECKS/STEPS LISTED HERE SHOULD BE PERFORMED AFTER APPLICATIONS CLONE with APPS SERVICES UP and RUNNING

17 Bring up all services

18 Set the Site Name Profile Option

19 Set the Java Color profile option
Changing-Look-and-feel-of-Oracle-Application&highlight=java+color

20 Configure Workflow Mailer

Login to OAM. Click on
Notification Mailer => Edit Button => Advanced.
Make sure to type in the Target instance password.

PROCESS and DISCARD should exist on the Server for wf<sid> user.
The name of the Process and the Discard directory can be got from the workflow configuration

21 Check and Schedule the Concurrent Requests - these would include Gather Statistics , Purge old data and Workflow related Concurrent Requests.
You can submit these Conc. Requests using forms or use CONCSUB as described in Concsub-to-Quickly-submit-Concurrent-Requests

Purge-concurrent-request-and-or-manager-data
Purge-Obsolete-Workflow-Runtime-Data-Concurrent-Program
Purge-Obsolete-Workflow-Runtime-Data-Concurrent-Program

22 Do a comprehensive Status check

23 Release the Instance to Users .

If you like this post please comment ......