Tag Archives: APPSORA

ERROR – RDA execution failed (9009)

Problem:

When running RDA from Application Diagnostics, the following error appears in the output report:

ERROR - RDA execution failed (9009)
ACTION - Review the output of the RDA command (shown below) to determine the cause 
of this error

Solution:

In APPL_TOP, create APPSORA.cmd from APPSSID_hostname.cmd.

Read more »

Checking for Prerequisite Patches and Patch Levels

In a patch’s README file, the prerequisite patches and patch levels that must be in place before that patch is applied are listed. Patches are indicated by a patch number (usually seven digits long), for example, 4712852. Patch levels  are usually of the form 11i.<PRODUCT CODE>.<LETTER>, for example, 11i.GL.H.

To determine if a particular prerequisite patch has already been applied to the system, query the AD_BUGS table.

Step 1:        Source the environment to load SQL*Plus. Either the applications tier environment or database tier environment can be sourced.

[applmgr@appslinux /]$ cd /u2/oracle/vis2appl/
[applmgr@appslinux vis2appl]$ . APPSORA.env

Step 2:        Load SQL*Plus:

[applmgr@appslinux vis2appl]$ sqlplus apps/apps

Step 3:        To determine whether a particular patch has been applied, query the BUG_NUMBER column of the AD_BUGS table for the patch number. For example, to determine if the patch 4712852 has been applied to the system, issue this SQL query:

SQL> select bug_number, creation_date from ad_bugs where bug_number = '4712852';
BUG_NUMBER                     CREATION_DATE
------------------------------ -------------
4712852                        16-MAR-07

If the query returns a row, the patch has been applied, whereas if the query does not return any rows, then the patch has not been applied.

Step 4:        To determine the patch level of a product, query the PATCH_LEVEL columns of the FND_PRODUCT_INSTALLATIONS table. For example, to determine the patch level for the GL product, issue this SQL query:

SQL> select patch_level, status from fnd_product_installations where patch_level like '%GL%';
PATCH_LEVEL                    S
------------------------------ -
11i.GL.H                       I

Changing Domain Name in Oracle Applications 11i

This documentation shows how to change the network domain name of the server that houses an Oracle Applications 11i instance (ebusiness).

  1. Log on to the ebusiness server (either on the console or using VNC or PuTTY). Run the network system settings tool (Red Hat menu > System Settings > Network).

Change the server name from ebusiness.support.com to ebusiness. illuminatnm.com. Save the settings. Do not attempt to restart the network services using this tool, since it will disconnect the remote connection tool.

  1. Edit the context file $APPL_TOP/admin/TEST_ebusiness.xml and replace ‘support.com’ with ‘illuminatnm.com’. With vi, use this command:
:%s/support.com/illuminatnm.com/g

Save the context file and exit the text editor.

  1. Stop the application tier services and then run AutoConfig on the database and application tiers:
cd /u0/oracle/testcomn/admin/scripts/TEST_ebusiness
./adstpall.sh

On the database tier:

cd /u0/oracle/testdb/9.2.0
. TEST_ebusiness.env
cd /u0/oracle/testdb/9.2.0/appsutil/scripts/TEST_ebusiness
./adautocfg.sh

On the application tier:

cd /u0/oracle/testappl
. APPSORA.env
cd /u0/oracle/testcomn/admin/scripts/TEST_ebusiness
./adautocfg.sh

Run the database tier and application tier AutoConfig processes in separate sessions (terminal windows).

  1. As the root user, update the hosts file on the server (/etc/hosts) to reflect the new host name:
x.x.x.x   ebusiness.illuminatnm.com   ebusiness
  1. As the root user, restart network services:
service network restart
  1. As the applmgr user, bounce the application tier services.
cd /u0/oracle/testcomn/admin/scripts/TEST_ebusiness
./adstpall.sh
(wait five minutes)
./adstrtal.sh
  1. Log on to the E-Business TEST application on the client machine using the new URL:
http://ebusiness.illuminatnm.com:8001

If E-Business Suite does not launch properly, reboot the server. After booting, start the application tier services. Then log on to the TEST instance.

Metalink References:

Note: 177311.1 – How to Change Domain Name in Oracle Applications 11i

Note: 342332.1 – Troubleshooting Login Problems in Oracle Applications 11i (11.5.2 – 11.5.10+)

adogjf() Unable to generate jar files under JAVA_TOP

Problem:

While applying patch 6502082, the patch completes in error with the following message:

ERROR: Javakey subcommand exited with status 1
Javakey standard output:
Adding entry: META-INF/MANIFEST.MF
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.
Javakey error output:
Reading product information from file...
Reading language and territory information from file...
Reading language information from applUS.txt ...
Reading language information from applUS.txt ...
Successfully created javaVersionFile.
TEST_hrms not found in database.
java key error:
adjava -ms128m -mx256m sun.security.provider.Main -gs /u0/oracle/prodcomn/java/oracle/apps/pon/jar/ponam.jar.tmp /u0/oracle/prodcomn/java/oracle/apps/pon/jar/ponam.jar.uns
The above Java program failed with error code 1.
Assigned: file adpcpset.pls on worker  1 for product ad  username APPLSYS.

Solution:

  1. Source the apps tier environment (APPSORA.env) and run adjkey –l
[applmgr@ebusiness 6502082]$ adjkey -l
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.
Scope: sun.security.provider.IdentityDatabase, source file: /home/applmgr/identitydb.obj
[Signer]Customer[identitydb.obj][trusted]
[Signer]DEMO_ebusiness[identitydb.obj][trusted]
java key is complete.
  1. Rename the identitydb.obj file in /home/applmgr
  2. Run: adjkey –initialize to create a new certificate
[applmgr@ebusiness 6502082]$ mv /home/applmgr/identitydb.obj /home/applmgr/identitydb.obj.20080909a
[applmgr@ebusiness 6502082]$ 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.
AD Java Key will now create a signing entity for you.
Please enter the name of the entity you wish to create [Customer] :
After creating the signing entity, a certificate will
be created for signing jar files locally.  You can specify an
organization to be used in identifying the certificate.
Please specify an organization to be assigned to the certificate [DEFAULT_ORG] :
Created identity [Signer]Customer[identitydb.obj][trusted]
Generated DSA keys for Customer (strength: 512).
Generated certificate from directive file /u0/oracle/prodappl/admin/out/adcert.txt.
Your digital signature has been created successfully and
imported into the javakey identity 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.
java key is complete.

References:

Note 141692.1 – How to Install a Digital Certificate in Oracle Applications Release 11i

Note 365735.1 – How to use, create and/or update Digital Certificates for 11i Applications

Answering adadmin Prompts

This section shows the typical responses for an adadmin session. Note that in this example, the VIS2 instance is used. The directories shown may differ for another instance. Note that pressing Enter for the responses uses the default answer, shown in brackets ([]).

[applmgr@appslinux ~]$ cd /u2/oracle/vis2appl/
[applmgr@appslinux vis2appl]$ . APPSORA.env
[applmgr@appslinux vis2appl]$ adadmin logfile=adadmin_20080516a.log
                     Copyright (c) 2002 Oracle Corporation
                        Redwood Shores, California, USA
                     Oracle Applications AD Administration
                                 Version 11.5.0
NOTE: You may not use this utility for custom development
      unless you have written permission from Oracle Corporation.
Your default directory is '/u2/oracle/vis2appl'.
Is this the correct APPL_TOP [Yes] ? <Press Enter> 
************* Start of AD Administration session *************
AD Administration version: 11.5.0
AD Administration started at: Fri May 16 2008 13:30:01
APPL_TOP is set to /u2/oracle/vis2appl
You can be notified by email if a failure occurs.
Do you wish to activate this feature [No] ? <Press Enter>
Please enter the batchsize [1000] : <Press Enter>
Please enter the name of the Oracle Applications System that this
APPL_TOP belongs to.
The Applications System name must be unique across all Oracle
Applications Systems at your site, must be from 1 to 30 characters
long, may only contain alphanumeric and underscore characters,
and must start with a letter.
Sample Applications System names are: "prod", "test", "demo" and
"Development_2".
Applications System Name [VIS2] : VIS2 *
NOTE: If you do not currently have certain types of files installed
in this APPL_TOP, you may not be able to perform certain tasks.
Example 1: If you don't have files used for installing or upgrading
the database installed in this area, you cannot install or upgrade
the database from this APPL_TOP.
Example 2: If you don't have forms files installed in this area, you cannot
generate them or run them from this APPL_TOP.
Example 3: If you don't have concurrent program files installed in this area,
you cannot relink concurrent programs or generate reports from this APPL_TOP.
Do you currently have files used for installing or upgrading the database
installed in this APPL_TOP [YES] ? YES *
Do you currently have Java and HTML files for HTML-based functionality
installed in this APPL_TOP [YES] ? YES *
Do you currently have Oracle Applications forms files installed
in this APPL_TOP [YES] ? YES *
Do you currently have concurrent program files installed
in this APPL_TOP [YES] ? YES *
Please enter the name Oracle Applications will use to identify this APPL_TOP.
The APPL_TOP name you select must be unique within an Oracle Applications
System, must be from 1 to 30 characters long, may only contain
alphanumeric and underscore characters, and must start with a letter.
Sample APPL_TOP Names are: "prod_all", "demo3_forms2", and "forms1".
APPL_TOP Name [appslinux] : appslinux *
You are about to use or modify Oracle Applications product tables
in your ORACLE database 'VIS2'
using ORACLE executables in '/u2/oracle/vis2ora/8.0.6'.
Is this the correct database [Yes] ? <Press Enter>
AD Administration needs the password for your 'SYSTEM' ORACLE schema
in order to determine your installation configuration.
Enter the password for your 'SYSTEM' ORACLE schema: manager
The ORACLE username specified below for Application Object Library
uniquely identifies your existing product group: APPLSYS
Enter the ORACLE password of Application Object Library [APPS] : <Press Enter>
AD Administration is verifying your username/password.
The status of various features in this run of AD Administration is:
                                           <-Feature version in->
Feature                          Active?   APPLTOP    Data model    Flags
------------------------------   -------   --------   -----------   -----------
CHECKFILE                        Yes       1          1             Y N N Y N Y
PREREQ                           Yes       6          6             Y N N Y N Y
CONCURRENT_SESSIONS              No        2          2             Y Y N Y Y N
PATCH_TIMING                     Yes       2          2             Y N N Y N Y
PATCH_HIST_IN_DB                 Yes       6          6             Y N N Y N Y
SCHEMA_SWAP                      Yes       1          1             Y N N Y Y Y
Identifier for the current session is 33937
Reading product information from file...
Reading language and territory information from file...
Reading language information from applUS.txt ...
Reading database to see what industry is currently installed.
Reading FND_LANGUAGES to see what is currently installed.
Currently, the following language is installed:
Code   Language                                Status
----   --------------------------------------- ---------
US     American English                        Base
Your base language will be AMERICAN.
Setting up module information.
Reading database for information about the modules.
Saving module information.
Reading database for information about the products.
Reading database for information about how products depend on each other.
Reading topfile.txt ...
Saving product information.
AD code level : [11i.AD.I.6]

EBS Cloning Environment Variables

Problem: What environment variables must be set before cloning, assuming no prior EBS environment file is present?

Solution:

Here is a sample script to source before running post-clone steps. It sets up the location to the PERL and Java executables. Note the directories must be changed to reflect your environment.

export PERL5LIB=/u01/deltaora/iAS/Apache/perl/lib/5.00503:
/u01/deltaora/iAS/Apache/perl/lib/site_perl/5.005:/u01/deltaappl/au/11.5.0/perl
export PATH=.:/u01/deltaora/iAS/Apache/perl/bin:/u01/deltacomn/util/jre/1.1.8/bin:$PATH
export LD_ASSUME_KERNEL=2.4.19

Enabling Maintenance Mode in SQL

Problem: Show how to enable or disable maintenance mode from SQL.

Solution: Run adsetmmd.sql

Step 1: Set up the environment by running APPSORA.env:

. ./$APPL_TOP/APPSORA.env

Step 2: Change directory to $AD_TOP/patch/115/sql/:

cd $AD_TOP/patch/115/sql/

Step 3: Run the SQL script:

sqlplus apps/apps @adsetmmd.sql ENABLE | DISABLE

Step 4: Bounce the Apache Web listener. (adapcctl.sh)

See Metalink Note: 291901.1 (Subject:  Maintenance Mode – A New Feature in 11.5.10)