APPSINFODB – Information Technology Group

Finding Solutions for DBA's to smile…….!!!!!!! DBA its just not Administration, its core of customer’s data integrity

  • Blog Stats

    • 38,065 hits
  • Visitors

    free counters
  • Vistors Access

  • Calendar

    November 2017
    M T W T F S S
    « Dec    
     12345
    6789101112
    13141516171819
    20212223242526
    27282930  
  • Archives

  • Authors

Archive for the ‘Cloning’ Category

Not able to cancel concurrent request & Unable to activate CM after cloning

Posted by appsinfo on August 20, 2012

Below are the two issues that I have faced after cloning from production

Q: How to terminate a concurrent request that cannot be cancelled

1.  Identify the request number to terminate.

2.  Shut down the concurrent managers and issue the following sql command as applsys:

            update fnd_concurrent_requests  set status_code = ‘E’, phase_code = ‘C’  where Request_id = <reqnum>; (reqnum = request number)

Q: A Manager is not activating.         

Check the count in sys.dual, system.dual, & apps.fnd_dual. There should only be one (1) row for each. 
If the count is greater, change to one only. This can be done from sqlplus as  follows:

    As user apps:
                   select * from SYS.DUAL;

    Any extra rows should be deleted.

                   delete rownum from SYS.DUAL; (rownum = the row number to delete)

    Any extra rows for apps.fnd_dual must be removed by performing the following SQL command:

                 delete from fnd_dual where rownum < (select max(rownum) from fnd_dual);

**For more on concurrent managers you can refer to FAQ (Concurrent Manager Unix specific Note ID: 105101.1)**

Advertisements

Posted in Cloning, E-Business Suite 11i, E-Business Suite R12, Troubleshooting | Tagged: | Leave a Comment »

Single Node Cloning 11.5.10.2 on Win03 Enviornment

Posted by appsinfo on March 2, 2009

Single Node Cloning

In the last post we have discussed about what cloning is, now we will learn how to clone an ERP instance in a single node enviornment ie single node to single node cloning.

Operating Sytem Pre-Requsites:

  1.  VC++ 6.0
  2.  VC ++ Service Pack 5 or higher
  3.  MKS 8.0.
  4. GNU Make 3.77
  5. Zip utility 3.0.

Application Pre-Requisites

Single Node cloning is simple, how ever you need to install Rapid Clone and AutoConfig patches, then you are ready to clone an instance. 

 5414396 -11i RAPIDCLONE CONSOLIDATED FIXES JUL/2008

Developer 6i Patch

6372396–Latest TXK Autoconfig and Template Patch

Following are the basic steps in cloning the ERP 11.5.10.2 application in windows enviornment:

Before going to the below steps you need to run the enviornment file on database tier and application tier accordingly.

Apply the above patches follow the readme document carefully.

Step 1: Prepare for source database clone:

cd E:\oracle\devdb\10.2.0\appsutil\scripts\dev_mydomain

perl adpreclone.pl dbTier

Step 2:  Prepare for source application clone:

cd %COMMON_TOP%/admin/scripts/<SID>

perl adpreclone.pl appsTier

Step 3:  Copy the application tier file system and Data files:

Logon to the source system as APPLMGR and shut down the server processes.

Copy the following application directories from the source to the target node/file system or you can copy all the tops

  • DATA_TOP
  • RDBMS_TOP
  • %APPL_TOP%
  • %OA_HTML%
  • %OA_JAVA%
  • %COMMON_TOP%/util
  • %COMMON_TOP%/clone
  • %806 ORACLE_HOME%
  • %iAS ORACLE_HOME%

Shut down the source database and copy it to the target node/file system.

Restart the source database and source application server processes.

Step 4:  Configure the target system database sever:

cd %ORACLE_HOME%/appsutil/clon/bin

perl adcfgclone.pl dbTier

Step 5:  Configure the target system application tier:

cd %COMMON_TOP%/clone/bin

perl adcfgclone.pl appsTier

Note: If you are using Oracle Workflow, you must update wf_notification_attributes and wf_item_attribute_values.

Posted in Cloning | Leave a Comment »

Clone Oracle Applications

Posted by appsinfo on November 17, 2008

Clone Oracle Applications

 

There are three sections to this phase of the cloning process:

 

• Prepare the source system

• Copy the source system to the target system

• Configure the target system

 

Clone Oracle Applications

 

• Use Rapid Clone to create template files for cloning on the source system.

• After the source system is copied to the target system, Rapid Clone updates these templates to

contain the new target system configuration settings.

• Rapid Clone will not change the source system configuration.

 

Prepare the Source System

 

1. Prepare the source system database tier for cloning.

2. Prepare the source system application tier for cloning.

 

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 <COMMON_TOP>/admin/scripts/<CONTEXT_NAME>

perl adpreclone.pl appsTier

 

Copy the Source System to the Target System

 

• Copy the application tier file system from the source Applications system to the target node.

• Ensure the application tier files copied to the target system are owned by the target applmgr

    user, and that the database tier files are owned by the oracle user.

 

Copy the Application Tier File System

 

• Log on to the source system application tier nodes as the applmgr user.

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

         <OA_HTML>

         <OA_JAVA>

         <COMMON_TOP/util>

         – <COMMON_TOP/clone>

         <806 ORACLE_HOME>

         <iAS ORACLE_HOME>

 

Copy the Database Tier File System

 

• Log on to the source system database node as the oracle user.

• Perform a normal shutdown of the source system database.

• Copy the database (DBF) files from the source to the target system.

• Copy the source database ORACLE_HOME to the target system.

• Start up the source Applications system database and application tier processes.

 

Configure the Target System

 

1. Configure the target system database server.

2. Configure the target system application tier server

nodes.

 

Configure the Target System Database Server

 

Log on to the target system as the oracle user and type the following commands to configure and start the database:

 

cd <RDBMS ORACLE_HOME>/appsutil/clone/bin

perl adcfgclone.pl dbTier

 

 Configure the Target System Application Server Nodes

 

Log on to the target system as the applmgr user and type the following commands:

cd <COMMON_TOP>/clone/bin

perl adcfgclone.pl appsTier

 

Finishing Tasks

 

1. Update profile options

Rapid Clone updates only site level profile options. If any other profile options are set to instance

specific values, you must update them manually.

 

2. Update printer settings

If the new cloned system needs to utilize different printers, update the target system with the new printer settings.

 

3. Update Workflow and other configuration settings Cloning an Oracle Applications instance will not update the host and instance specific information used by Oracle Workflow and other components

Posted in Cloning | Leave a Comment »

Rapid Cloning FAQ’s

Posted by appsinfo on November 17, 2008

What is Cloning?

 

Cloning is the act of creating an identical copy of an already existing Oracle Applications system. The new system and the existing system must be initially identical in these aspects:

 

  • Component versions
  • Platform type

 Why Cloning?

 

Situations that may require cloning include:

 

• Creating a copy of the production system for testing updates.

• Migrating an existing system to new hardware.

• Creating a stage area to reduce patching downtime.

 

 What is Rapid Clone?

 

The Rapid Clone utility:

 

• Preserves Oracle Applications configuration information specific to the target system.

• Removes components of the file system.

• Re-implements the saved configuration on the target system.

• Is applied in pre-install mode to all APPL_TOPs on the source system.

 

 How many cloning phases are there?

 

The main phases of cloning are:

 

• Prerequisite steps

• Clone Oracle Applications

– Prepare the source system

– Copy the source system to the target system

– Configure target system

• Perform finishing tasks

• Test the target system

Posted in Cloning, FAQ Cloning | Leave a Comment »