Adjava Error

Got following error while patch application :

 

    AD Run Java Command is complete.

 

                         Copyright (c) 2002 Oracle Corporation

                            Redwood Shores, California, USA

 

                                        AD Java

 

                                     Version 11.5.0

 

    NOTE: You may not use this utility for custom development

          unless you have written permission from Oracle Corporation.

 

    Failed to generate product JAR files in JAVA_TOP -

       /instance/applmgr/common/java.

 

 

 

    ***

    Do you wish to continue ?

    ***

 

    AutoPatch could not find a response to the above prompt

    or found an incorrect response in the defaults file.

 

    You must run AutoPatch in an interactive session

    and provide a correct value.

 

 

    You should check the file

    /instance/applmgr/11510/admin/INSTANCE/log/adpatch_3032057.log

 

    for errors.





Issue is with Java:

    JarSigner error output:

    Exception in thread "main" java.lang.NoClassDefFoundError: sun/security/tools/JarSigner

 

 

    WARNING: The following path(s), defined in /instance/applmgr/11510/fnd/11.5.0/java/make/fndjar.dep

    as elements of the output file fndaol.jar, could not be found in any area:

      oracle/apps/media/ieu_moveleft

      oracle/apps/media/ieu_moveright

      oracle/apps/media/mscrsbti

      oracle/apps/media/msctile

 

 

      About to Analyze fndutil.jar : Tue Sep 22 2009 23:50:38

 

    Up-to-date : fndutil.jar

 

      Done Analyzing fndutil.jar : Tue Sep 22 2009 23:50:38

 

 

      About to Analyze fndctx.jar : Tue Sep 22 2009 23:50:38

 

 

        About to Generate fndctx.jar : Tue Sep 22 2009 23:50:38

 

 

        Done Generating fndctx.jar : Tue Sep 22 2009 23:50:38

 

 

        About to Sign fndctx.jar : Tue Sep 22 2009 23:50:38

 

    ERROR: JarSigner subcommand exited with status 1

 

    No standard output from jarsigner

 

 

      Done Analyzing fndlist.jar : Tue Sep 22 2009 23:46:02

 

 

    ERROR: The following jars failed to get generated properly.

 

    ----------------------------------------------------------------------------

    /instance/applmgr/common/java/oracle/apps/fnd/jar/fndaol.jar

    /instance/applmgr/common/java/oracle/apps/fnd/jar/fndctx.jar

    /instance/applmgr/common/java/oracle/apps/fnd/jar/wfmon.jar

    /instance/applmgr/common/java/oracle/apps/fnd/jar/wfapi.jar

    /instance/applmgr/common/java/oracle/apps/fnd/jar/fndaolj.jar

    /instance/applmgr/common/java/oracle/apps/fnd/jar/fndcct.jar

    /instance/applmgr/common/java/oracle/apps/fnd/jar/fndlist.jar

    ----------------------------------------------------------------------------

 

 

    Done Analyzing/Generating jar files : Tue Sep 22 2009 23:46:02

 

 

 

 

    -----------

    verifying files:  adcert.txt and indentitydb.obj; these files are used for signing JAR files

 

    ----

    can't find file indentitydb.obj

    Regenerating missing files .....




 bash-2.05b$  adjkey -initialize

 

                         Copyright (c) 2002 Oracle Corporation

                            Redwood Shores, California, USA

 

                                 AD Java Key Generation

 

                                     Version 11.5.0

 

    NOTE: You may not use this utility for custom development

          unless you have written permission from Oracle Corporation.

 

    Reading product information from file...

 

    Reading language and territory information from file...

 

    Reading language information from applUS.txt ...

 

    Successfully created javaVersionFile.

 

    adjkey will now create a signing entity for you.

 

    Please specify a common name to be assigned to certificate [CUSTOMER] :CUSTOMER

 

    Please specify an organization unit to be assigned to certificate [ORGANIZATION UNIT] : DEF_UNIT

 

    Please specify an organization name to be assigned to certificate [ORGANIZATION NAME] :  DEF_NAME

 

    Please specify a country name to be assigned to certificate [COUNTRY] : DEF_COUNTRY

    Your digital signature has been created successfully and

    imported into the keystore database. This signature

    will now be used to sign Applications JAR files whenever

    they are patched.

 

      IMPORTANT: If you have multiple web servers, you must copy

      files to each of the remaining web servers on your site.

      See the documentation reference for more information.

 

 

    adjkey is complete.

    bash-2





 Regeneratin jar files manually failed:

 

    Up-to-date : fndpromise.jar

 

      Done Analyzing fndpromise.jar : Wed Sep 23 2009 00:20:02

 

 

      About to Analyze fndforms.jar : Wed Sep 23 2009 00:20:02

 

    Up-to-date : fndforms.jar

    WARNING: The following path(s), defined in /instance/applmgr/11510/fnd/11.5.0/java/make/fndjar.dep

    as elements of the output file fndforms.jar, could not be found in any area:

      oracle/forms/engine/KeyMapTable

      oracle/forms/engine/MainHTTP

      oracle/forms/engine/MainJNI

      oracle/forms/engine/MessageHandler2

      oracle/forms/handler/SearchDialog

      oracle/forms/ui/ListValuesNavigator

 

 

      Done Analyzing fndforms.jar : Wed Sep 23 2009 00:20:05

 

 

      About to Analyze fndewt.jar : Wed Sep 23 2009 00:20:05

 

    Up-to-date : fndewt.jar

 

      Done Analyzing fndewt.jar : Wed Sep 23 2009 00:20:07

 

 

      About to Analyze fndewtpv.jar : Wed Sep 23 2009 00:20:07

 

    Up-to-date : fndewtpv.jar

 

      Done Analyzing fndewtpv.jar : Wed Sep 23 2009 00:20:07

 

 

      About to Analyze fndaol.jar : Wed Sep 23 2009 00:20:07

 

 

        About to Generate fndaol.jar : Wed Sep 23 2009 00:20:07

 

 

        Done Generating fndaol.jar : Wed Sep 23 2009 00:20:09

 

 

        About to Sign fndaol.jar : Wed Sep 23 2009 00:20:09

 

    ERROR: JarSigner subcommand exited with status 1

 

    No standard output from jarsigner

 

    JarSigner error output:

    Exception in thread "main" java.lang.NoClassDefFoundError: sun/security/tools/JarSigner

 

    WARNING: The following path(s), defined in /instance/applmgr/11510/fnd/11.5.0/java/make/fndjar.dep

    as elements of the output file fndaol.jar, could not be found in any area:

      oracle/apps/media/ieu_moveleft

      oracle/apps/media/ieu_moveright

      oracle/apps/media/mscrsbti

      oracle/apps/media/msctile

 

 

      About to Analyze fndutil.jar : Wed Sep 23 2009 00:20:09

 

    Up-to-date : fndutil.jar

 

 

 

    Investigating ....

 

    Verifying

 

    bash-2.05b$ cd $OA_JRE_TOP/lib

    bash-2.05b$ ls -al tools.jar

    -rw-r--r--    1 apinstance aainstance  5093683 May 14  2007 tools.jar

 

    bash-2.05b$ jar tvf  tools.jar | grep sun/security/tools/JarSigner

 

    bash-2.05b$ jar tvf tools.jar | grep JarSigner

     21085 Tue Jan 01 00:00:00 GMT 1980 sun/security/tools/JarSigner.class

      4043 Tue Jan 01 00:00:00 GMT 1980 sun/security/tools/JarSignerResources.class

      6503 Tue Jan 01 00:00:00 GMT 1980 sun/security/tools/JarSignerResources_ja.class

    bash-2.05b$

 

 

    $ echo $CLASSPATH

    /instance/applmgr/common/util/java/1.4/j2sdk1.4.2_04/lib/tools.jar:/instance/applmgr/common/util/java/1.

    4/j2sdk1.4.2_04/lib/dt.jar:/instance/applmgr/common/util/java/1.4/j2sdk1.4.2_04/jre/lib/charsets.jar:/

    instance/applmgr/common/util/java/1.4/j2sdk1.4.2_04/jre/lib/rt.jar:/instance/applmgr/common/java/appsbor

    g2.zip:/instance/product/806/forms60/java:/instance/applmgr/common/java

    $ echo $AF_CLASSPATH

    /instance/applmgr/common/util/java/1.4/j2sdk1.4.2_04/lib/tools.jar:/instance/applmgr/common/util/java/1.

    4/j2sdk1.4.2_04/lib/dt.jar:/instance/applmgr/common/util/java/1.4/j2sdk1.4.2_04/jre/lib/charsets.jar:/

    instance/applmgr/common/util/java/1.4/j2sdk1.4.2_04/jre/lib/rt.jar:/instance/applmgr/common/java/appsbor

    g2.zip:/instance/product/806/forms60/java:/instance/applmgr/common/java

    $

 

 

    Same issue ...

    ERROR: JarSigner subcommand exited with status 1

 

    No standard output from jarsigner

 

    JarSigner error output:

    Exception in thread "main" java.lang.NoClassDefFoundError: sun/security/tools/JarSigner

 

 

      Done Analyzing fndlist.jar : Wed Sep 23 2009 00:51:49

 

 

    ERROR: The following jars failed to get generated properly.

 

    ----------------------------------------------------------------------------

    /instance/applmgr/common/java/oracle/apps/fnd/jar/fndaol.jar

    /instance/applmgr/common/java/oracle/apps/fnd/jar/fndctx.jar

    /instance/applmgr/common/java/oracle/apps/fnd/jar/wfmon.jar

    /instance/applmgr/common/java/oracle/apps/fnd/jar/wfapi.jar

    /instance/applmgr/common/java/oracle/apps/fnd/jar/fndaolj.jar

    /instance/applmgr/common/java/oracle/apps/fnd/jar/fndcct.jar

    /instance/applmgr/common/java/oracle/apps/fnd/jar/fndlist.jar

    ----------------------------------------------------------------------------

 

 

    Done Analyzing/Generating jar files : Wed Sep 23 2009 00:51:49

 

 

                         Copyright (c) 2002 Oracle Corporation

                            Redwood Shores, California, USA

 

                                        AD Java

 

                                     Version 11.5.0

 

    NOTE: You may not use this utility for custom development

          unless you have written permission from Oracle Corporation.

 



  Solution:

    ========

 

    $ ls /instance/applmgr/common/util/java/1.4/j2sdk1.4.2_04/lib/tools.jar

    ls: /instance/applmgr/common/util/java/1.4/j2sdk1.4.2_04/lib/tools.jar: No such file or directory

    $ cd /instance/applmgr/common/util/java/1.4/j2sdk1.4.2_04/lib

    ksh: cd: /instance/applmgr/common/util/java/1.4/j2sdk1.4.2_04/lib - No such file or directory

    $ cd

    $ pwd

    /instance/product

    $

 

 

    $ pwd

    /instance/applmgr/common/util/java/1.4

    $ env | grep j2sdk1.4.2_04

    AF_CLASSPATH=/instance/applmgr/common/util/java/1.4/j2sdk1.4.2_04/lib/tools.jar:/instance/applmgr/common

    /util/java/1.4/j2sdk1.4.2_04/lib/dt.jar:/instance/applmgr/common/util/java/1.4/j2sdk1.4.2_04/jre/lib/c

    harsets.jar:/instance/applmgr/common/util/java/1.4/j2sdk1.4.2_04/jre/lib/rt.jar:/instance/applmgr/common

    /java/appsborg2.zip:/instance/product/806/forms60/java:/instance/applmgr/common/java

    CLASSPATH=/instance/applmgr/common/util/java/1.4/j2sdk1.4.2_04/lib/tools.jar:/instance/applmgr/common/ut

    il/java/1.4/j2sdk1.4.2_04/lib/dt.jar:/instance/applmgr/common/util/java/1.4/j2sdk1.4.2_04/jre/lib/char

    sets.jar:/instance/applmgr/common/util/java/1.4/j2sdk1.4.2_04/jre/lib/rt.jar:/instance/applmgr/common/ja

    va/appsborg2.zip:/instance/product/806/forms60/java:/instance/applmgr/common/java

    $

 

 

    edited $APPL_TOP/admin/adovars.env

 

    and replaced /instance/applmgr/common/util/java/1.4/j2sdk1.4.2_04 with

    /instance/applmgr/common/util/java/1.4 and logoff and login and reran adadmin and regenerated jar

    files manually and it works fine.

Adrelink Fails

Error message :


gcc -s -L/instance/product/806/lib -L/instance/product/806/lib/stubs -ldl  -o
    /instance/applmgr/11510/ad/11.5.0/bin/adpchnew
    /instance/applmgr/11510/ad/11.5.0/lib/adpmain.o \
    /instance/applmgr/11510/ad/11.5.0/lib/libad.a
    /instance/applmgr/11510/fnd/11.5.0/lib/libfnd.a -lsql
    /instance/product/806/lib/nautab.o /instance/product/806/lib/naeet.o
    /instance/product/806/lib/naect.o /instance/product/806/lib/naedhs.o `cat
    /instance/product/806/lib/naldflgs` -lnetv2 -lnttcp -lnetwork -lncr  -lclient
    -lvsn -lcommon -lgeneric -lmm -lnlsrtl3  -lcore4 -lnlsrtl3 -lcore4 -lnlsrtl3
    -lnetv2 -lnttcp -lnetwork -lncr  -lclient -lvsn -lcommon -lgeneric  -lepc
    -lnlsrtl3  -lcore4 -lnlsrtl3 -lcore4 -lnlsrtl3 -lclient -lvsn -lcommon
    -lgeneric -lnlsrtl3  -lcore4 -lnlsrtl3 -lcore4 -lnlsrtl3   `cat
    /instance/product/806/lib/sysliblist` -ldl -lpthread -lm
    /instance/product/806/rdbms/lib/defopt.o
    /instance/product/806/rdbms/lib/ssbbded.o
    /usr/lib/gcc/i386-redhat-linux/3.4.6/libgcc_s.so: undefined reference to
    `dl_iterate_phdr@GLIBC_2.2.4'
    collect2: ld returned 1 exit status
    make: *** [/instance/applmgr/11510/ad/11.5.0/bin/adpchnew] Error 1
    Done with link of ad executable 'adpchnew' on Sat Sep 26 23:58:01 BOT 2009
   
    Relink of module "adpchnew" failed.
    See error messages above (also recorded in log file) for possible
    reasons for the failure.  Also, please check that the Unix userid
    running adrelink has read, write, and execute permissions
    on the directory /instance/applmgr/11510/ad/11.5.0/bin,
    and that there is sufficient space remaining on the disk partition
    containing your Oracle Applications installation.
   
   


 $ gcc -v
    Reading specs from /usr/lib/gcc/i386-redhat-linux/3.4.6/specs
    Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info
    --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit
    --disable-libunwind-exceptions --enable-java-awt=gtk --host=i386-redhat-linux
    Thread model: posix
    gcc version 3.4.6 20060404 (Red Hat 3.4.6-10.0.1)




  gcc version is 3.4.6 20060404.
  
    Action Plan
    ------------------
    1. Uninstall Patch 4198954.
    ( You have to uninstall first before installing again .
    You can also use force install , if any issues )
  
    2.. Reapply the Patch 4198954 on all the node

Expired and Locked DB account

SQL> select username,ACCOUNT_STATUS from dba_users where USERNAME='ABCD';
    
    USERNAME                       ACCOUNT_STATUS
    ------------------------------ --------------------------------
    ABCD                          EXPIRED & LOCKED
    

To resolve i gave following command

1. Check the current password :

SQL>  select username,password from dba_users where username='ABCD';

USERNAME                       PASSWORD
------------------------------ ------------------------------
ABCD                          8B0354E43FEE9F31




2. alter user  abcd account unlock;
3. alter user identified by user abcd ;


4. Reverted the password :

SQL> alter user ABCD identified by values '8B0354E43FEE9F31';

SQL> select username,ACCOUNT_STATUS from dba_users where USERNAME='ABCD';
    
    USERNAME                       ACCOUNT_STATUS
    ------------------------------ --------------------------------
    ABCD                            OPEN
    
    

Concurrent Manager Processes Architechture

The current Concurrent Processing architecture with Global Service Management
consists of the following processes and communication model, where each process
is responsible for performing a specific set of routines and communicating with
parent and dependent processes.

Internal Concurrent Manager (FNDLIBR process) - Communicates with the Service
Manager.

The Internal Concurrent Manager (ICM)  starts, sets the number of active processes,
monitors, and terminates all other concurrent processes through requests made to
the Service Manager, including restarting any failed processes.  The ICM also
starts and stops, and restarts the Service Manager for each node.  The ICM will
perform process migration during an instance or node failure.  The ICM will be
active on a single node.  This is also true in a PCP environment, where the ICM
will be active on at least one node at all times.

Service Manager (FNDSM process) - Communicates with the Internal Concurrent Manager,
Concurrent Manager, and non-Manager Service processes.

The Service Manager (SM) spawns, and terminates manager and service processes (these
could be Forms, or Apache Listeners, Metrics or Reports Server, and any other process
controlled through Generic Service Management).  When the ICM terminates the SM that
resides on the same node with the ICM will also terminate.  The SM is ‘chained’ to
the ICM.  The SM will only reinitialize after termination when there is a function it
needs to perform (start, or stop a process), so there may be periods of time when the
SM is not active, and this would be normal.  All processes initialized by the SM
inherit the same environment as the SM.  The SM’s environment is set by APPSORA.env
file, and the gsmstart.sh script.  The TWO_TASK used by the SM to connect to a RAC
instance must match the instance_name from GV$INSTANCE.  The apps_ listener must
be active on each CP node to support the SM connection to the local instance.  There
should be a Service Manager active on each node where a Concurrent or non-Manager
service process will reside.

Internal Monitor (FNDIMON process) - Communicates with the Internal Concurrent
Manager.

The Internal Monitor (IM)  monitors the Internal Concurrent Manager, and restarts any
failed ICM on the local node.  During a node failure in a PCP environment the IM will
restart the ICM on a surviving node (multiple ICM's may be started on multiple nodes,
but only the first ICM started will eventually remain active, all others will
gracefully terminate).  There should be an Internal Monitor defined on each node
where the ICM may migrate.

Standard Manager (FNDLIBR process) - Communicates with the Service Manager and any
client application process.

The Standard Manager is a worker process, that initiates, and executes client requests
on behalf of Applications batch, and OLTP clients.

Transaction Manager - Communicates with the Service Manager, and any user process
initiated on behalf of a Forms, or Standard Manager request.  See Note 240818.1
regarding Transaction Manager communication and setup requirements for RAC.

Steps To Recreate Central Inventory(oraInventory) In RDBMS

Opatch error
==========

Stderr output:
    /instance/oracle/product/102/lib//libcore10.a(lcd.o)(.text+0xb71): In function `lcdprm':
    : warning: the `gets' function is dangerous and should not be used.
    
    
         Make Action done
    OPatch was able to restore your system. Look at log file and timestamp of each file to make sure
    your system is in the state prior to applying the patch.
    --------------------------------------------------------------------------------
    The following warnings have occurred during OPatch execution:
    1) OUI-67124:Inventory check failed: Patch ID 6258480 is NOT registered in Oracle Home inventory.
    --------------------------------------------------------------------------------
    
    OPatch failed with error code 73
    

In cases where the OraInventory is missing or otherwise corrupt, recreate the oraInventory directory on UNIX systems using the following steps. In a normal installation, there is a Global Inventory ($ORACLE_BASE/OraInventory) and a Local Inventory ($ORACLE_HOME/inventory).

   1. Locate the oraInst.loc file, which may be in different locations, depending on your system:

            /var/opt/oracle/oraInst.loc file
            or
            /etc/oraInst.loc


   2. Modify the file oraInst.loc file:

            cp /var/opt/oracle/oraInst.loc /var/opt/oracle/oraInst.loc.bak
            mkdir /u01/oracle/oraInventory

            ---file contents---
            inventory_loc=/u01/oracle/oraInventory
            inst_group=oinstall
            ---file contents---


        
   3. Change the permissions to be appropriate, (using your directory location):

            chmod 644 /var/opt/oracle/oraInst.loc


   4. For consistency, copy the file to Oracle home directory, (using your directory location):

      cp $ORACLE_HOME/oraInst.loc $ORACLE_HOME/oraInst.loc.bak
      cp /var/opt/oracle/oraInst.loc $ORACLE_HOME/oraInst.loc


   5. Run Oracle Universal Installer from your Oracle home as below:

      cd $ORACLE_HOME/oui/bin
      ./runInstaller -silent -attachHome ORACLE_HOME="/u01/oracle/product/10.1.2" ORACLE_HOME_NAME="Ora10gHome"

     
   6. Check the inventory output is correct for your Oracle home:

            $ORACLE_HOME/OPatch/opatch lsinventory -detail

   7. If the table at the beginning of the output is showing the proper directories, and the Oracle home components are properly reflected in the details, then the Global Inventory (in $ORACLE_BASE) has been successfully created from the Local Inventory, (in $ORACLE_HOME). At this time, you may patch and maintain your Oracle home, as normal.

RRA/FNDFS

Report Review Agent(RRA) also referred by executable FNDFS is default text viewer in Oracle Applications 11i for viewing output files and log files. 



FNDFS executable uses the Report Review Agent Listener in the 8.0.6 Oracle Home installed on the application tier.

The report review agent uses two major configuration files :

1) listener.ora

2) tnsnames.ora

Location of these files -- $ORACLE_HOME/network/admin

FNDFS listener is automatically configured by the system.

When a user makes a request to view a report, FNDFS program is launched.

FNDFS connectivity can be configured by configuring the tnsnames.ora file.

Location of tnsnames.ora file -- $TNS_ADMIN/tnsnames.ora

An alias is created for FNDFS_nodename.

The tnsnames.ora file defines connections to the FNDFS listener adn it contains the address list of all the services that we can connect to from the client.

FNDFS_nodename=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=TCP)
(HOST=hostname)
(PORT=portnumber))
(CONNECT_DATA=(SID=FNDFS))
)

GSM

GSM stands for Generic Service Management Framework. Oracle E-Business Suite consist of various compoennts like Forms, Reports, Web Server, Workflow, Concurrent Manager ..

Earlier each service used to start at their own but managing these services (given that) they can be on various machines distributed across network. So Generic Service Management is extension of Concurrent Processing which manages all your services , provide fault tolerance (If some service is down ICM through FNDSM and other processes will try to start it even on remote server) With GSM all services are centrally managed via this Framework.

Adsplice

Copy These files at the $APPL_TOP/admin

izuprod.txt  izuterr.txt  newprods.txt


$ cp izuprod.txt /instance/applmgr/11510/admin
$ cp /instance/applmgr/11510/patches/3636980/izu/admin/izuprod.txt /instance/applmgr/11510/admin
$ cp /instance/applmgr/11510/patches/3636980/izu/admin/izuterr.txt /instance/applmgr/11510/admin
$ cp /instance/applmgr/11510/patches/3636980/izu/admin/newprods.txt /instance/applmgr/11510/admin
$ cd  $APPL_TOP/admin





+++++++++++++++++++++
Before running Adsplice create tablespace

create tablespace IZUD datafile '/instance/oradata/data01/izud01.dbf' size 1000M autoextend on next 25M maxsize 1800M ;

create tablespace IZUX datafile '/instance/oradata/data01/izux01.dbf' size 100M autoextend on;

create tablespace IZUX datafile '/instance/oradata/data01/izux01.dbf' size 1000M autoextend on next 25M maxsize 1800M ;

Sometime Tablespace can be default

SQL> select username , default_tablespace from dba_users where username='IZU';

USERNAME                       DEFAULT_TABLESPACE
------------------------------ ------------------------------
IZU                            APPS_TS_TX_DATA
+++++++++++++++++++++


SQL> create tablespace user_data datafile '/instance/oradata/data01/user_data01.dbf' size 200M;

Tablespace created.

SQL> create tablespace user_idx datafile '/instance/oradata/data01/user_idx01.dbf' size 200M;



SQL> create user izu identified by izu default tablespace izud;

User created.

SQL> grant connect,resource to izu;

Grant succeeded.

select tablespace_name,status from dba_tablespaces where tablespace_name like '%IZU%';

+++++++++
changing newprod.txt file replace the names by userdata to IZUD
product=izu
base_product_top=*APPL_TOP*
oracle_schema=izu
sizing_factor=100
main_tspace=IZUD
index_tspace=IZUX
temp_tspace=TEMP
default_tspace=IZUD





- run adsplice



use option no for regeneration for environment file : NO


Saving product actions...done.

Making product top directory for product "izu"...
Directory will be /instance/applmgr/11510/izu/11.5.0
...............................................
Creating stub file "admin/driver/izudfr.drv" for product "izu"...
Creating stub file "admin/driver/izuen.drv" for product "izu"...
Creating stub file "admin/driver/izudep.drv" for product "izu"...


Do you wish to regenerate your environment file [Yes] ? No

AD Splicer is complete.

Errors and warnings are listed in the log file
/instance/applmgr/11510/admin/INSTANCE/log/adsplice.log

and in other log files in the same directory.


Set this Path on all nodes.

/instance/applmgr/11510/ar/11.5.0

/instance/applmgr/11510//izu/11.5.0

/instance/applmgr/11510/izu/11.5.0
++++++++++come out from box and login again and check it


$ echo $IZU_TOP
/instance/applmgr/11510/izu/11.5.0


select APPLICATION_ID        from fnd_application        where APPLICATION_SHORT_NAME = 'EGO';


This statement should return one row:    APPLICATION_ID    --------------               278     From within SQL*Plus, logged in as APPS, run the following:        

select STATUS         from fnd_product_installations         where APPLICATION_ID = 431;

This statement should return one row:    S    -    I


SQL> select APPLICATION_ID from fnd_application where APPLICATION_SHORT_NAME = 'IZU';

APPLICATION_ID
--------------
278

SQL> select STATUS from fnd_product_installations where APPLICATION_ID = 278;

S
-
I


Then RUN Patch 3636980 after completion of all these activities.

If Issue Came
=============
- If product is not showing Installed in u can license it through OAM
- Login in sysadmin and check Oracle Diaganostic Tool responsibility is available.
- Oracle Diaganoitic is installed properly.

Setting events in the database

Correct way of setting the event dynamically ( only after confirmation from support)

alter system set events ''event name

---- if using spfile ( show parameter pfile)

1) set the event dynamically as mentioned above
2) change the spfile

a) show parameter event
if there is no event set currectly

alter system set event=''event name" scope=spfile

if there is some event already set, we need to include that also

alter system set event=''event name1","event name2'' scope=spfile

confirm the setting in spfile

string -a | grep -i event

---- if using pfile


1) set the event dynamically as mentioned above
2) change the init ora file manually

Tracing web session in eBS

1. Log onto the Applications Forms with the Application Developer Responsibility
2. Navigate to the Profile menu
3. Query up the profile name "FND_INIT_SQL"
4. In the bottom block of the form, make sure that ALL checkboxes are checked Typically, you will have to enable the checkboxes under "User Access" to make it "Visible" and "Updatable".

b. Now switch to the System Administrator Responsibility
1. Navigate to - Profile - System
2. On the "Find System Profile Values" form, make sure the checkboxes for "User" and "Profiles with no Values" are checked
3. Beside the "User" checkbox, use the LOV to select the user who's activity you need to trace
4. In the "Profile" field, enter the following profile and click the button: 'Initialization SQL Statement - Custom'
5. In the "System Profile Values" form, enter the following in the User Field: (This is one line and all single quotes)

begin fnd_ctl.fnd_sess_ctl('','','TRUE','TRUE','LOG','ALTER SESSION SET EVENTS=''10046 TRACE NAME CONTEXT FOREVER, LEVEL 12'' tracefile_identifier=''HARMEET'' max_dump_file_size=''unlimited'''); end;

6. SAVE THE PROFILE

7. In another browser window, login as the user you are going to trace and prepare to reproduce the problem
8. Reproduce the problem
9. Back in the Applications form, set profile to null so it does not trace anymore and Save the change
10. The trace will be located in the user_dump_dest. To find location run the following in SQL*Plus: select value from v$parameter where name = 'user_dump_dest';
11. The trace file will have current date/time and can be identified with the word HARMEET in it.


Note : for an example with screenshots of eBS follow this link :)
http://oracle-apps-dba.blogspot.com/2009/01/how-to-enable-trace-for-crm-session.html

Release 12 Applications

r12apps.blogspot.com

Version Checks

Version of objects is often needed by support.


CONTENTS
--------

1. Oracle Applications
2. Forms
3. Reports
4. SQL or PL/SQL Scripts
5. Executables
6. Other Files
7. RDMBS
8. Database Objects
9. Operating System


1. ORACLE APPLICATIONS

a. To obtain version of form from any applications form, navigate to the form.
Then in the Menu toolbar select Help => About Oracle Applications.

NOTE:  A pop-up window will open indicating the version of:

 Oracle Applications version
 Current used module
 Oracle Forms version
 RDBMS
 Current open form

b. Also run the following command:

 sqlplus applsys/
 select release_name from fnd_product_group;


2. FORMS

a. If the form is displayed, review #1 above to get current open form version.
b. In the event the form doesn't appear then:

  (1).  Retreive the form name from another environment which has the same form.
        (i.d. NLS, test or production, etc.) or from Metalink.

  (2).  Navigate to /forms (/ eventually) directory.  The 
        corresponding file with the .fmx extension should be located here.

  (3).  See #6 below to obtain the file version.


3. REPORTS

a.  First check the report name on located at the top of the log file.
b.  Navigate to /reports(/ eventually) directory.  The
    corresponding file with the .rdf extension should be located here.
c.  See #6 below to obtain the file version.


4. SQL OR PL/SQL SCRIPTS

a.  Navigate to /admin/sql or /patch/110/sql to obtain the last version.
    The corresponding file with .sql, .pls, .pkh, or .pkb extension should be located
    here.
b.  See #6 below to get the file version.


5. EXECUTABLES

a.  Binary or executable names often do not have extensions on unix systems.
    In MS-Windows environments the extensions are usually .exe or .dll.
b.  Most of the executables are located under the

/bin

    directory.
c.  There are many methods for obtaining the version of an executable.  These methods
    are listed below:

   (1).  If an interface is displayed, go to the Menu => Help => About.
         e.g. Oracle Applications, internet browsers, tools (Oracle Forms,
         Oracle Reports, Enterprise Manager, SQL*Plus)
         'Help => About Plug-ins' will provide the Jinitiator version.

   (2).  Run the file without parameter.
         e.g. f45gen, f60gen (for Oracle Forms)
         r25convm, rwcon60 (for Oracle Reports)
         sqlplus (for SQL*Plus)
         tnsping (TNS Ping Utility)
         jre (Java Runtime Loader)
            
  
   (3).  To see properties of the file with MS-Windows Explorer.
         e.g. *.exe, *.dll files


   (4).  To find the 'Header' string, see #6 to proceed.
         e.g. ad utilities (adpatch, adrelink, etc.), fnd executables,
         binaries under /bin directories

   (5).  Run a specific command
         e.g. Appletviewer:
             java -version

         Oracle Workflow in Oracle Applications:
           sqlplus apps/ 
           @$FND_TOP/sql/wfver.sql
           or
           select TEXT from WF_RESOURCES where NAME='WF_VERSION';

   (6).  Launch Oracle Installer
  
      Several Oracle products (like RDBMS and Tools) require ORAINST to be installed.
      Below is the method to launch ORAINST and obtain the version of various products:

      (a).  Login with Oracle account
      (b).  Run Oracle Installer using:
            $ORACLE_HOME/orainst/orainst

          or

            Under MS-Windows:
            $ORACLE_HOME\bin\orainst.exe

      (c).  Answer by taking defaults to reach 'Software Asset Manager' screen.

      (d).  Right column will display installed products and versions.

            NOTE: Same information is found in the files below:
            $ORACLE_HOME/orainst/unix.rgs (Unix)
            $ORACLE_HOME\orainst\nt.rgs, windows.rgs (Win NT, MS-Windows)



6. OTHER FILES

A.  Other files on the file system may be:
 
 driver files (*.drv)
 object description files (*.odf)
 data files (*.dat)
 library and object files (*.a, *.o)
 Oracle Forms libraries (*.pll, *.plx)
 Oracle Forms menu files (*.mmb, *.mmx)
 form source files (*.fmb)
 jar file (*.jar)
 java class file (*.class)
 html, xlm files (*.htm, *.xlm)

b.  Navigate to the corresponding directory.
c.  Execute one of the following commands to obtain the version of the file
    on all platforms (beginning with Oracle Applications v. 11.x):
     adident Header

    On Unix:
     strings -a | grep Header

    On Windows (DOS box):
     find "Header"


7. RDMBS

a. See #1.a to obtain the version of the Oracle Server installed in the environment.
b. Another method for obtaining the version is by executing sqlplus.
   It displays SQL*Plus and RDBMS version.

   e.g. Oracle8 Enterprise Edition Release 8.0.6.1.

c. If the preference is to use Oracle Installer, then review #5c(6) to also obtain the
   version of several installed products.


8. DATABASE OBJECTS

a. Run the following sql statement to obtain the package version:

   select text from user_source where name='&package_name'
   and text like '%$Header%';

NOTE:  The prompt requests the package name. By providing the package name it will
       return two lines corresponding to specifications and body creation files.

       You can also obtain the pls version on the database by running:

       select name, text
       from dba_source
       where text like '%.pls%'
       and line < 10;


b. To obtain the version information in the view definition run the sql below:

   col TEXT for a40 head "TEXT"
   select VIEW_NAME, TEXT
   from USER_VIEWS
   where VIEW_NAME = '&VIEW_NAME';

c. To obtain the workflow related objects run the wfver.sql script. Review #5c(5) above
   to obtain the version of workflow packages and views.


9. OPERATING SYSTEM

a. For most Unix platforms run command:
 
   uname -a

b. For MS-WINDOWS 95/98/2000

   Start => Parameters => Control Panel => System

c. For WIN/NT, execute command:

   winver

   or

   Menu: Start => Programs => Admin Tools => WIN NT Diagnostic



RELATED DOCUMENTS
-----------------

Note 106767.1 How To Determine The Version Of An Applications Form In
Release 11?


        

Debug Apache

Debug Apache


I . Please perform the following steps:

        - Clear the Apache cache

        in $OA_HTML/_pages ( 11.5.9)

                    in $COMMON_TOP/_pages ( 11.5.10 and above

    

        - Delete or rename the existing logfiles. You may or may not have all of these.

               a. From "$IAS_TOP/Apache/Apache/logs" delete the error_log and the access_log

               b. From "$IAS_TOP/Apache/JServ/logs" delete the mod_jserv.log an the jserv.log

        - Please have the apache debug turned on like in Note 230688.1

        - Start the apache server.

        - Reproduce the Hang/Issue

II  have the apache debug turned on like in Note 230688.1

1.  Shutdown the apache web server. 

2.  Delete or rename the existing logfiles. 

a. from ".../iAS/Apache/Apache/logs" delete everything in this directory

b. from ".../iAS/Apache/Jserv/logs" delete everything in this directory, including the underlying jvm directory 

3. Edit the file .../iAS/Apache/Apache/conf/httpd.conf to enable debug for apache.

ErrorLog /dwwt1i/product/iAS/Apache/Apache/logs/error_log

LogLevel debug

4.  Edit the /dwwt1i/product/iAS/Apache/Jserv/etc/jserv.conf to enable debug for the JServ module. 

ApJServLogLevel debug

5. Edit the file .../iAS/Apache/Jserv/etc/jserv.properties to enable debug for the JVM.

 log=true 

 log.file=/dwwt1i/product/iAS/Apache/Jserv/logs/jserv.log

log.timestamp=true

log.channel=true

log.channel.info=true 

log.channel.servletException=true 

log.channel.jservException=true 

log.channel.warning=true 

log.channel.servletLog=true

log.channel.critical=true 

log.channel.debug=true

6.  Start the apache server. 

7. Pause for a minute

8.  Do the test and capture it in the logfiles

 - Reproduce the Hang/Issue ( Customer will have to reproduce the issue )

  

9. Upload a new set of config files..

        Run the following Unix command as the Apache/Jserv owner ( whoever started up Apache/Jserv ):

              zip -r /tmp/`uname -n`_`date +%m%d%y.%H%M`current_config_iAS.zip \

                     $IAS_ORACLE_HOME/Apache/Apache/conf/* \

                     $IAS_ORACLE_HOME/Apache/Jserv/etc/*

     

10. Upload a fresh set of log files..  Run the following Unix command as the Apache/Jserv owner

            zip -r /tmp/`uname -n`_`date +%m%d%y.%H%M`current_log.zip \

                  $IAS_ORACLE_HOME/Apache/Apache/logs/* \

                  $IAS_ORACLE_HOME/Apache/Jserv/logs/*

Metalink note:230688.1

OPATCH ERROR

While appling patch i got following error :

--------------------------------------------------------------------------------
The following warnings have occurred during OPatch execution:
1) OUI-67124:Inventory check failed: Patch ID 7445168 is NOT registered in Oracle Home inventory.
--------------------------------------------------------------------------------
sol
====
Please delete the /oracle/product/10.2.0.4/OCDEV/oraInventory/Contents directory to avoid inventory update failures


The above solution worked .:)

Scripts

http://harmeetdbascripts.blogspot.com/