Oracle E - Business suite : R12.1.3 on Linux 64 bits and Oracle Database 11.2.0.3 on same plateform.

I have upgraded E-business suite application from R12.1.1 to R12.1.3. all steps were completed successfully except autoconfig. I faced following error during autoconfig.

Error:

Autoconfig completed with errors.

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

DECLARE
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-20000: Oracle Text error:
DRG-11422: linguistic initialization failed
DRG-11446: supplied knowledge base file
/u01/app/orar12/db/tech_st/11.2.0/ctx/data/enlx/droldUS.dat not installed
ORA-06512: at "CTXSYS.DRUE", line 160
ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 366
ORA-06512: at "SYS.DBMS_SQL", line 1199
ORA-06512: at line 37

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

Cause:

An Issue is the CTXSTS.DEFAULT_LEXER. INDEX_THEMES attribute was made to YES.

 
Solutions:

  1.  Shut down the database and applications.

  2.  Make sure ORA_NLS10 is unset on dbTier

        $ unset ORA_NLS10

  3.  Startup the database.

  4.  Drop index jtf.JTF_AMV_ITEMS_URL_CTX

                        SQL> drop index jtf.JTF_AMV_ITEMS_URL_CTX FORCE;

                        Index dropped.

  5.  Re-run  jtfictx.sh again

                        cd $COMMON_TOP/admin/install/CONTEXT_NAME

                        $ . ./jtfictx.sh

                        bash started at Wed Oct 30 10:40:35 PDT 2013

                        Enter the APPS username: apps

                        Enter the APPS password:

                        SQL*Plus: Release 8.0.6.0.0 - Production on Wed Oct 30 10:40:40 2013

                        (c) Copyright 1999 Oracle Corporation.  All rights reserved.

                        Enter value for 1: Enter value for 2: Enter value for 3: Connected.

                        PL/SQL procedure successfully completed.

                        Commit complete.

adgentns.pl exiting with status 2 after Clone/Refresh

Autoconfig Error: adgentns.pl exiting with status 2 after Clone/Refresh

Error:

[CVM Error Report]

            The following report lists errors encountered during CVM Phase

           /u01/oracle/DEVDB1/apps/apps_st/appl/ad/12.0.0/bin/adgentns.pl  2

No of scripts failed in CVM phase: 1

            AutoConfig is exiting with status 1

Solution:

1.     Open a new shell and source the APPS Environment. ($APPL_TOP/APPS_.env)
2.     sqlplus apps/apps 
• SQL> exec fnd_conc_clone.setup_clean
3.     Open a new terminal or shell and source the DB-Tier Environment.
4.     Execute Autoconfig on the DB Tier. ($ORACLE_HOME/appsutil/bin/adconfig.sh)
5.     Switch back to the APPS environment or start a new shell and source the APPS environment.
6.     Execute Autoconfig at the Apps Tier. ($AD_TOP/bin/adconfig.sh)
7.     Check the Autoconfig log for any errors and ensure that the services start correctly.

AutoPatch error: Missing file format id in file: adpinit.rf9

AutoPatch error: Missing file format id in file: adpinit.rf9

Error:

 

AutoPatch error:

Missing file format id in file:

/e01/EBSPTR1/ebsptr1app/apps/apps_st/appl/admin/EBSPTR1/restart/adpinit.rf9

This version of AutoPatch requires a file format id

on the first line of the file.

 

Cause: 

 

adpatch has run multiple times

 

Solution:

 

Goto /e01/EBSPTR1/ebsptr1app/apps/apps_st/appl/admin/EBSPTR1/restart/ and

Rename adpinit.rf9 and reapply the patch. One should not manually edit the *.rt9 files

Oracle error &ERRNO: &REASON has been detected in &ROUTINE.

Error:

Oracle error &ERRNO: &REASON has been detected in &ROUTINE.

Solution:

1. select trigger_name,status from dba_triggers where trigger_name like ‘ALR_FND%UAR%';
2. Disable the trigger ‘ALR_FND_USER_UAR’ using sqlplus 

           SQL> alter trigger ALR_FND_USER_UAR disable;

FRM-92101 There was a failure in the Forms server during startup.

When i try to open any forms in EBS R12 with the new Linux machine, getting below error, 

 

Error: 

 

FRM-92101 There was a failure in the Forms server during startup.

        This could happen due to an invalid configuration.

        Please look into the web server log for the details.

        Details...

        Java Exception:

        oracle.forms.net.ConnectionException...

 

Solution:

 

Create directory and copy paste the contents of /usr/X11R6/lib from another server that exists libXm.so.2 or download it from the internet for your specific Linux version.

        Or if you are missing the prerequisite rpms, install the following RPM packages:

 

Workaround:

 

Create directory and copy paste the contents of /usr/X11R6/lib from another server that exists libXm.so.2 or download it from the internet for your specific Linux version.

        Or if you are missing the prerequisite rpms, install the following RPM packages:

        xorg-x11-libs-compat-6.8.2-1.EL.33.0.1

        libXp-1.0.0-8.1.el5

        openmotif21-2.1.30-11.EL6.i686 rpm

Forms session <1> aborted: runtime process failed during startup with errors /u04/EXTRNAPP2/apps/tech_st/10.1.2/bin/frmweb: error while loading shared libraries:

         libXm.so.2: cannot open shared object file: No such file or directory

         rpm -Uvh openmotif21-2.1.30-11.EL6.i686.rpm

adformsctl.sh: exiting with status 150

If adoacorectl.sh,adformsctl.sh,adoafmctl.sh not coming up after start the application services

Error:

adoacorectl.sh: exiting with status 150
adformsctl.sh: exiting with status 150
adoafmctl.sh: exiting with status 150

Check the log file for these three processes:
$LOG_HOME/appl/admin/log/adoacorectl.txt
$LOG_HOME/appl/admin/log/adoafmctl.txt
$LOG_HOME/appl/admin/log/adoaformsctl.txt
If you see error like below

"opmn id=app01.rajeev01.com:6200
    no processes or applications matched this request

06/20/12-02:50:27 :: adoafmctl.sh: exiting with status 150"

Solution:

 

1. Stop all three services.
2. Clean the directory, under  persistence from below directory and restart all three
   services
   $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/persistence
   $ORA_CONFIG_HOME/10.1.3/j2ee/oafm/persistence
   $ORA_CONFIG_HOME/10.1.3/j2ee/forms/persistence
3. Start the EBS services.
4. Retest the issue.
5. Migrate the solution as appropriate to other environments.