Scribd Logo
Upload

Welcome to Scribd!

  • 115 views

    EBS R12 Error Soutions

    Uploaded by

    Daniel Craig
    This document discusses solutions to common errors when starting up Oracle Applications components. It addresses errors such as adopmnctl.sh exiting with status 206 or 2, adstrtal.sh exiting with status 4, and post-installation errors. The solutions involve removing lock files, validating IP addresses, setting the environment, and ensuring required shared libraries are present. Starting individual components like the web server and checking logs is recommended to diagnose the root cause.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    EBS R12 Error Soutions

    Uploaded by

    Daniel Craig
    115 views5 pages
    This document discusses solutions to common errors when starting up Oracle Applications components. It addresses errors such as adopmnctl.sh exiting with status 206 or 2, adstrtal.sh exiting with status 4, and post-installation errors. The solutions involve removing lock files, validating IP addresses, setting the environment, and ensuring required shared libraries are present. Starting individual components like the web server and checking logs is recommended to diagnose the root cause.

    Original Description:

    EBS R12 Error Soutions

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document discusses solutions to common errors when starting up Oracle Applications components. It addresses errors such as adopmnctl.sh exiting with status 206 or 2, adstrtal.sh exiting with status 4, and post-installation errors. The solutions involve removing lock files, validating IP addresses, setting the environment, and ensuring required shared libraries are present. Starting individual components like the web server and checking logs is recommended to diagnose the root cause.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    115 views5 pages

    EBS R12 Error Soutions

    Uploaded by

    Daniel Craig
    This document discusses solutions to common errors when starting up Oracle Applications components. It addresses errors such as adopmnctl.sh exiting with status 206 or 2, adstrtal.sh exiting with status 4, and post-installation errors. The solutions involve removing lock files, validating IP addresses, setting the environment, and ensuring required shared libraries are present. Starting individual components like the web server and checking logs is recommended to diagnose the root cause.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 5

    Author A.

    Kishore/Sachin
    http://appsdba.info
    1

    Solutions to Oracle Apps Errors

    adopmnctl.sh: exiting with status 206

    We may face this issue while starting up the oacore component in our R12 environment. There
    might not errors logged in any of the log files except the error status code of 206 returned by
    opmnctl.sh .

    Error Details :

    ias-component/process-type/process-set:
    OC4J/oacore/default_group/
    Error
    --> Process (index=1,uid=32979870,pid=13697)
    failed to start a managed process after the maximum retry limit
    Log:
    /d01/oracle/PROD/INSTANCE_NAME/inst/apps/INSTANCE_NAME_SERVER_NAME/logs/ora/10.1.
    3/opmn/OC4J~oacore~default_group~1

    ias-component/process-type/process-set:
    OC4J/oafm/default_group/

    Error
    --> Process (index=1,uid=32979871,pid=13716)
    failed to start a managed process after the maximum retry limit
    Log:
    /d01/oracle/PROD/INSTANCE_NAME/inst/apps/instance_name_server_name/logs/ora/10.1.3/
    opmn/OC4J~oafm~default_group~1

    03/31/11-07:12:49 :: adopmnctl.sh: exiting with status 206

    Expected Solution:

    cd $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/persistence/
    rm -rf *
    cd $ORA_CONFIG_HOME/10.1.3/j2ee/oafm/persistence/
    rm -rf *



    Author A.Kishore/Sachin
    http://appsdba.info
    2

    adstrtal.sh: Exiting with status 4

    We may face this issue while starting up the application services using adstrtal.sh.

    Error Details:
    adstrtal.sh: Exiting with status 4

    adstrtal.sh: check the logfile
    /d01/oracle/PROD/inst/apps/PROD_erp/logs/appl/admin/log/adstrtal.log for more information

    Expected Solution :

    We need to go to each of the following location, and move or delete files with extension .lock

    $cd $INST_TOP/ora/10.1.3/j2ee/forms/persistence/forms_default_group_1/
    $cd $INST_TOP/ora/10.1.3/j2ee/oafm/persistence/oafm_default_group_1/
    $cd $INST_TOP/ora/10.1.3/j2ee/oacore/persistence/oacore_default_group_1/

    adopmnctl.sh: exiting with status 2

    We may get this error ,we try to start the application or OPMN (adstrtal.sh apps/<apps_pwd>
    or adopmnctl.sh start).

    Error Details:
    adopmnctl.sh: exiting with status 2

    Expected Solution :
    Normally, this error occurs when opmn associate with wrong ip address.
    So, we need to validate the ip address with correct one.

    Oracle R12 Post Installation Error

    We may face this error after finishing the Oracle R12 installation and when post installation
    checks begin.







    Author A.Kishore/Sachin
    http://appsdba.info
    3
    Error Details:
    From below screenshot,we are getting that some services are not available.



    Expected Solution:

    Login in to apps tier as applmgr and set the environment.
    [root@ebs ~]# su - applmgr
    [applvis@ebs ~]$ . /d01/oracle/PROD/apps/apps_st/appl/PROD_erp.env
    Check the status of opmn by issuing the following :
    [applmgr@ebs ~]$ $ADMIN_SCRIPTS_HOME/adopmnctl.sh status


    We found that the web server is the only component that's currently failing, and the other app
    server components of the system are started as expected.

    Start web server as shown below.
    [applmgr@ebs ~]$ $ADMIN_SCRIPTS_HOME/adapcctl.sh start



    Author A.Kishore/Sachin
    http://appsdba.info
    4

    We will get the following error.

    ias-component/process-type/process-set:
    HTTP_Server/HTTP_Server/HTTP_Server/
    Error--> Process (index=1,uid=1625958549,pid=26727)
    failed to start a managed process after the maximum retry limit Log:
    /d01/oacle/PROD/inst/apps/PROD_erp/logs/ora/10.1.3/opmn/HTTP_Server~1.log
    adapcctl.sh: exiting with status 0
    adapcctl.sh: check the logfile
    /d01/oracle/PROD/inst/apps/PROD_erp/logs/appl/admin/log/adapcctl.txt for more
    information ...
    Check the log file for more information, as shown below.
    [applmgr@ebs ~]$ tail /d01/oacle/PROD/inst/apps/PROD_erp/logs/ora/10.1.3/opmn/HTTP_Server~1.log
    We will find the below information:


    So, this missing shared object library file is the most likely the cause of the error, we got.
    We need to create one symlink later, as shown below.
    Switch to root user and do the following.
    [root@ebs ~]# ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2
    Now start the web server again.
    [applmgr@ebs ~]$ $ADMIN_SCRIPTS_HOME/adapcctl.sh start
    Now check the status of opmn.
    [applmgr@ebs ~]$ $ADMIN_SCRIPTS_HOME/adopmnctl.sh status


    After that post installation checks will look like below screenshot.








    Author A.Kishore/Sachin
    http://appsdba.info
    5



    Now we can access Oracle Apps without any problem.

    You might also like