How do I recover the Applications context file if it is lost or deleted accidentally?

A gem is not polished without rubbing, nor a man perfected without trials.

Chinese Proverb

The Applications context file can be retrieved by running the adclonectx.pl script.

To retrieve the Applications tier context file,

• perl /clone/bin/adclonectx.pl retrieve
• On being prompted for the context file to be retrieved, select the option of retrieving the Applications tier context file that has been lost and retrieve it to the default location specified by the script.

The above command can be used only when INST_TOP the is still intact. In case the has also been lost accidentally, the Applications tier context file may be retrieved as follows:

• Execute the following command on the Database tier:
  perl /appsutil/clone/bin/adclonectx.pl retrieve
• On being prompted for the context file to be retrieved, select the option of retrieving the Applications tier context file that has been lost.
• While confirming the location for the context file, set it to any existing directory with write permission.
• Once the context file has been generated in the specified location, move it to the location specified for the context file in the context variable ‘s_contextfile’.

To retrieve the Database tier context file,

• Execute the following command on the Database tier:
  perl /appsutil/clone/bin/adclonectx.pl retrieve
• On being prompted for the context file to be retrieved, select the Database tier context file and retrieve it to the default location specified by the script.

Best Practice
Retrieve the context file from database tier . It will be very easy and only few steps needs to be answered

Autoconfig

Great starts make great finishes

Today i am going to discuss about Autoconfig
AC–Autoconfig

What is Autoconfig?
Autoconfig is a tool for configuring application instance.

What are the programs and program name involved in AC?
You can see perl,shell,cmd and java programs.

1.adconfig.pl- Its a main program which inturn call Java APIs for configuring appl instance.
args-appl context file location

2.adautocfg.sh/adautocfg.cmd-This program inturn calls adconfig.pl
args-apps password

3.adconfig.sh-This program again calls adconfig.pl

These three programs i used for running AC.

4. adchgatname.pl – This program will validating the APPL_TOP name in context file .If the APPL_Top name is changed, then this utility will take care of storing the old APPL_TOP name in APPL_TOP/admin/ATName.txt.Adconfig.pl calls this program .

Issue with Concurrent Manager

Be not afraid of growing slowly, be afraid only of standing still.

Chinese Proverb

CM– Concurrent Manager

Most of the DBA face the problem with CM.
CM is heart of Oracle APPS

Procedure to start CM:

1. Start the Database.
2. Start the Apps Tier

• Unix user – apstartal.sh apps/apps
• Windows user – use SCM to start the service or adstrtal.cmd apps/apps
• Script is located under $COMMON_TOP/admin/scripts for 11i and $INST_TOP/admin/scripts for R12
• Log file location : $APPLCSF/$APPLLOG

Steps to debug the CM :

1. Check the log file CM . CM will not start if unable to write the information in log file.
2. Tnsping $TWO_TASK . Two task is nothing but a sid name . Check its executing successfully.
3. Check for the process FNDLIBR. Unclean shutdown will create a problem.
4. Check for the FND invalids in database
5. Keep an eye on alert logs of database . It will cause an core dump issue

How the CM works :

1. First it will start the ICM(Internal concurrent manager) and ICM will start remaining managers like standard managers..etc
2. FNDSM is a process is responsible for starting other managers.

Features involved in CM:

1. You can create any number of managers and assign a workshift to the managers.
2. CM can handle any number of request depends on the server configuration.
3. If CM wants to handle more process(FNDLIBR). Increase the count of FNDLIBR process as a system administrator and bounce the CM

Real time example:

1. CM will connect to database by resolving tnsnames.ora . After changing the ip of the server(multi node installation) i cannot able to up the CM . Problem because /etc/hosts entry still pointing to the old ip after changing the /etc/host file CM is up successfully .It sounds simple but tricky to debug . Finally tnsping utility helped me to analyse the problem

Related Terms:
Fndsm,fndlibr,concsub,palibr,adcmctl,cpmgr