Manju apps DBA
1. After purchasing a license for an Application Product/Module, the first thing is to use license manager to record that the product/module is now licensed. License manager can be run 2 ways:
a. log in through Oracle Application Manager (OAM) and select Site Map -> Administration tab -> License Manager
b. run adlicmgr.sh from AD_TOP/bin
Using both methods you can license by Module or by individual Product. Select the check box for the Module/Product to be licensed and Save/Next
During the form generation process, adadmin reads a file named <prod>file.drv to build a list of objects to generate.
For example if you are looking at the AZ module forms, there will be a file called azfile.drv. This file is located in $PROD_TOP/admin/driver.
In this example this is $AZ_TOP/admin/driver.
Q: Which Concurrent Managers (CCMs) are supported by the Sysadmin team?
- Internal Concurrent Manager (ICM)
- Standard Manager
- Conflict Resolution Manager (CRM)
The setup of product-specific managers related issues should
be directed to the associated product group, i.e. the Inventory manager
Q: Where do the concurrent request output and log files reside?
A: $APPLCSF/out or $Product_Top/out for output files
$APPLCSF/log or $Product_Top/log for log files
Q: Where are temporary files located?
A: Temporary files reside in:
$APPLPTMP$APPLTMP
$REPORTS25_TMP (Release 11.0)
$REPORTS60_TMP (Release 11.5)
Oracle has made the process of upgrading from Oracle8i or Oracle9i databases simple by automating a large portion of the upgrade process.
Here are the upgrade paths that you can take to move up to Oracle Database 10g Release 2 (10.2):
• If you are moving from Oracle 7.3.3 or lower, or Oracle 7.3.4, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.1.5, or 8.1.6, you can’t upgrade directly to Oracle Database 10g.
• If you are using an Oracle 8.1.7, 9.0.1, 9.2, or 10.1 database, you can upgrade directly.
Steps For Upgrading
1.) Install 10g Binaries on a separate ORACLE_HOME
2.) Patch 10g Binaries to the latest Patchset (à 10.2.0.4)
3.) Set env of 9i ORACLE_HOME
4.) Connect to 9i DB
5.) Create a new tablespace called SYSAUX
- Of size 500MB
- Automatic segment space management
- Locally managed
SQL> CREATE TABLESPACE sysaux DATAFILE ‘/oracle/oradata/prod/sysaux01.dbf’
SIZE 500M REUSE
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO;
- OPatch is a java based utility that allow the application and rolling back of interim patches to an Oracle product. The program has sub-commands that may take arguments. The program requires Java(JVM) to be present on the current system.OPatch expects users to have commands such as fuser, jar, ar and make on Unix platforms and jar on Windows platforms to be available in their PATH.
Opatch Details
How to check the Opatch version?
-bash-3.00$ ./opatch version
Invoking OPatch 10.2.0.3.0
Invoking OPatch 10.2.0.3.0
OPatch Version: 10.2.0.3.0
OPatch succeeded.
How to know which version is the correct version of Opatch for your RDBMS home?
You can verify whether the Opatch version for your RDBMS release is correct or not using metalink note ID 357221.1.
This note ID gives the copatibilities between OPatch version and RDBMS version.
How to get the latest version of OPatch?
You can download the latest version of OPatch from metalink using following URL.
http://updates.oracle.com/download/6880880.html
In the release dropdown you can select the OPatch release that you want to download based on your RDBMS version. Please read the README.txt before applying the patch.
What is Oracle Database Inventory and where it is located?
Oracle Inventory is the location or the place where all the information about an Oracle Home is stored and maintained. When ever we install an RDBMS Oracle Home, a new inventory gets created. Applying any new patch to Oracle Home will update the invnrtory for that Oracle Home and record the details for the patch applied. This inventory is in the form of XML files.
The location of inventory is defined in a file called oraInst.loc. The path for this file is provided while installing Oracle Home. If we dont supply any path, the is file will be present at central location /etc/oraInst.loc. Also we can have a central inventory if its not used by any other oracle installation. If the central inventory is used by previous Oracle installation we can create local inventory. The content of oraInst.loc file is as shown below.
-bash-3.00$ cd $ORACLE_HOME
-bash-3.00$ cat oraInst.loc
inventory_loc=/slot/ems2029/appmgr/apps/tech_st/10.1.2/oraInventory
inst_group=ems2029
-bash-3.00$
-bash-3.00$ cat oraInst.loc
inventory_loc=/slot/ems2029/appmgr/apps/tech_st/10.1.2/oraInventory
inst_group=ems2029
-bash-3.00$
Here “inventory_loc” gives the location of Inventory directory where as inst_group gives the name of the group which is the owner of this inventory.
Where are the log files?
The following are referenced in this document:
{MMDDHHMM} : MM (Month) DD (Day) HH (Hour) MM (Minute)
{Timestamp} : {This may include Year, Month, Day, and Time}
{Base Install} : Location chosen during the RapidWiz configuration phase
The following are referenced in this document:
{MMDDHHMM} : MM (Month) DD (Day) HH (Hour) MM (Minute)
{Timestamp} : {This may include Year, Month, Day, and Time}
{Base Install} : Location chosen during the RapidWiz configuration phase
$CONTEXT_NAME : {SID}_{hostname}
RDBMS $ORACLE_HOME} : {Base Install}/db/tech_st/10.2.0
$IAS_ORACLE_HOME : {Base Install}/apps/tech_st/10.1.3
Tools $ORACLE_HOME : {Base Install}/apps/tech_st/10.1.2
$INST_TOP : {Base Install}/inst/apps/$CONTEXT_NAME
$APPL_TOP : {Base Install}/apps/apps_st/appl
RDBMS $ORACLE_HOME} : {Base Install}/db/tech_st/10.2.0
$IAS_ORACLE_HOME : {Base Install}/apps/tech_st/10.1.3
Tools $ORACLE_HOME : {Base Install}/apps/tech_st/10.1.2
$INST_TOP : {Base Install}/inst/apps/$CONTEXT_NAME
$APPL_TOP : {Base Install}/apps/apps_st/appl
Before the installation starts:
$TMP/{MMDDHHMM}/{MMDDHHMM}.log$TMP/{MMDDHHMM}/{hostname}_{SID}.xml
$TMP/{MMDDHHMM}/{hostname}_{SID}_apps.xml
$TMP/{MMDDHHMM}/{MMDDHHMM}.log$TMP/{MMDDHHMM}/{hostname}_{SID}.xml
$TMP/{MMDDHHMM}/{hostname}_{SID}_apps.xml
The Rapidwiz Configuration File is saved in 3 locations:-$TMP/{MMDDHHMM}/conf_{SID}.txt$INST_TOP/conf_{SID}.txt{RDBMS ORACLE_HOME}/appsutil/conf_{SID}.txt
The basics of how this Rapid Wizard installation works are:-
1. RapidWizard collects user information required for configuration of system, and creates a configuration file
2. RapidWizard checks Port availability and file space required
3. Zip files from the “oraDB and oraAppDB” DVD stage area are then uncompressed onto the file system
4. Each Disk directory contains a driver which is read to control the unzip phase
5. The DB Techstack is relinked and reconfigured using an install driver, templates and the configuration file
6. Control files are created
7. The RDBMS ORACLE_HOME is registered into the Global Inventory
8. The DB is started, and further configuration is performed
9. Zip files from the “oraAS” (Developer Tools and As10g” DVD stage area are then uncompressed onto the file system
10. The Apps Techstack is relinked and reconfigured using the install driver, templates and the configuration file
11. The Developer Tools and As10g ORACLE_HOMEs are registered into the Global Inventory
12. Zip files from the “oraApps” (APPL_TOP, COMMON_TOP etc) stage are uncompressed onto the file system
13. APPL_TOP is reconfigured with system using values in the configuration file and services are started
14. Post install checks are performed to check success of the installation.
1. RapidWizard collects user information required for configuration of system, and creates a configuration file
2. RapidWizard checks Port availability and file space required
3. Zip files from the “oraDB and oraAppDB” DVD stage area are then uncompressed onto the file system
4. Each Disk directory contains a driver which is read to control the unzip phase
5. The DB Techstack is relinked and reconfigured using an install driver, templates and the configuration file
6. Control files are created
7. The RDBMS ORACLE_HOME is registered into the Global Inventory
8. The DB is started, and further configuration is performed
9. Zip files from the “oraAS” (Developer Tools and As10g” DVD stage area are then uncompressed onto the file system
10. The Apps Techstack is relinked and reconfigured using the install driver, templates and the configuration file
11. The Developer Tools and As10g ORACLE_HOMEs are registered into the Global Inventory
12. Zip files from the “oraApps” (APPL_TOP, COMMON_TOP etc) stage are uncompressed onto the file system
13. APPL_TOP is reconfigured with system using values in the configuration file and services are started
14. Post install checks are performed to check success of the installation.
Following suggestions can substantially reduce your system downtime during the application of patches:
1.Consolidate Patches
Using AD Merge Patch to merge multiple patches into a single patch eliminates the time it takes to start a new AutoPatch session. It also eliminates generic processes that are common to all patch applications.
Using AD Merge Patch to merge multiple patches into a single patch eliminates the time it takes to start a new AutoPatch session. It also eliminates generic processes that are common to all patch applications.
2.Apply Patches in Non-interactive Mode
You can automate much of the patching process by applying patches in non-interactive mode. This process allows you to store the responses to the patching prompts in a defaults file, and then specify the name of this file when you run AutoPatch. See Oracle Applications Maintenance Procedures (11i) and Oracle Applications Patching Procedures (R12) for more information.
3.Defer Database TasksUse AutoPatch options=nocompiledb,nomaintainmrc to defer system-wide tasks such as “Compile APPS schema” and “Maintain MRC” until all patches have been applied. AutoPatch automatically compiles the APPS schema and maintains the MRC schema during the application of standard patches. Try deferring the compilation of database objects so users can log back in sooner. You should do this with this understanding:
Applying a patch in a test system shows data objects that are invalid because they cannot be compiled (as opposed to being invalid because the definition has changed and the object has not yet been compiled). Problems must be resolved on the production system using workarounds that are similar to those used on the test system.
The database server automatically compiles any uncompiled database objects that are present when the objects are accessed for the first time. This may affect performance as the first user waits for all invalid objects in the dependency chain to be compiled. You can minimize this effect by running “Compile APPS schema” in AD Administration immediately after you return your system to the user community.
The database server automatically compiles any uncompiled database objects that are present when the objects are accessed for the first time. This may affect performance as the first user waits for all invalid objects in the dependency chain to be compiled. You can minimize this effect by running “Compile APPS schema” in AD Administration immediately after you return your system to the user community.
4.Defer Upload of Patch Information
AutoPatch uploads patch history information to the database automatically each time it successfully applies a patch. The time required for the upload may be substantial depending on the size of the patch. You can defer this task during the AutoPatch session and upload the patch history information later, after you have made the system available to users. Use options=phtofile during the downtime patching session to defer the information upload. Then, after your system is up and users have returned, run AutoPatch again with the argument uploadph=y to upload the patch history information from the patch history files to your database. AutoPatch performs the upload and then exits.
AutoPatch uploads patch history information to the database automatically each time it successfully applies a patch. The time required for the upload may be substantial depending on the size of the patch. You can defer this task during the AutoPatch session and upload the patch history information later, after you have made the system available to users. Use options=phtofile during the downtime patching session to defer the information upload. Then, after your system is up and users have returned, run AutoPatch again with the argument uploadph=y to upload the patch history information from the patch history files to your database. AutoPatch performs the upload and then exits.
1. CONCURRENT PROGRAMS
——————————————
two methods to see concurrent program logs :
——————————————
two methods to see concurrent program logs :
a. directly from Oracle Applications :
System Administrator responsability (for own and other users requests) :
Navigator: Concurrent => Requests, button View Log…
System Administrator responsability (for own and other users requests) :
Navigator: Concurrent => Requests, button View Log…
Other responsabilities (for own requests), menus could be different:
Navigator: Requests , button View Log…
Navigator: Other => Requests , button View Log…
Navigator: Other => Requests => View , button View Log…
Navigator: Control => Requests => View , button View Log…
Navigator: Requests , button View Log…
Navigator: Other => Requests , button View Log…
Navigator: Other => Requests => View , button View Log…
Navigator: Control => Requests => View , button View Log…
b. retrieve Concurrent Program log files under :
$/$APPLLOG
or if you have defined common directory :
$APPLCSF/$APPLLOG
or if you have defined common directory :
$APPLCSF/$APPLLOG
File format is :
l.req
l.req
2. CONCURRENT MANAGERS
——————————————
two methods to see concurrent manager logs :
——————————————
two methods to see concurrent manager logs :
a. directly from Oracle Applications :
System Administrator responsability
Navigator: Concurrent => Requests, choose a request …
menu: Special => Manager Log
or
Navigator: Concurrent => Manager => Administer, button Processes (Concurrent Processes window)
=> button Manager Log
Navigator: Concurrent => Requests, choose a request …
menu: Special => Manager Log
or
Navigator: Concurrent => Manager => Administer, button Processes (Concurrent Processes window)
=> button Manager Log
b. retrieve Manager log files under :
$FND_TOP/$APPLLOG
or if you have defined common directory :
$APPLCSF/$APPLLOG
or if you have defined common directory :
$APPLCSF/$APPLLOG
File format is :
w.mgr
The oraInventory is the location for the OUI (Oracle Universal Installer)’s bookkeeping. The inventory stores information about:
- All Oracle software products installed in all ORACLE_HOMES on a machine
- Other non-Oracle products, such as the Java Runtime Environment (JRE)
In a 11i Application system the RDBMS and iAS ORACLE_HOMEs are registered in the oraInventory. The 806 ORACLE_HOME, which is not managed through OUI, is not.
On Unix/Linux, the location of the oraInventory is defined by the content of oraInst.loc, at:
- /var/opt/oracle/oraInst.loc on Solaris, HP-UX and Tru64
- /etc/oraInst.loc on Linux and AIX
On Windows, the location of the oraInventory is defined by the value of the registry key HKEY_LOCAL_MACHINE|Software\Oracle\INST_LOC or if this value is not defined, at C:\Program Files\Oracle\Inventory.
- /var/opt/oracle/oraInst.loc on Solaris, HP-UX and Tru64
- /etc/oraInst.loc on Linux and AIX
On Windows, the location of the oraInventory is defined by the value of the registry key HKEY_LOCAL_MACHINE|Software\Oracle\INST_LOC or if this value is not defined, at C:\Program Files\Oracle\Inventory.
install Oracle Apps 11i (11.5.10.2) on Linux.
Software
1. Software for Oracle 11i can be downloaded from edelivery.oracle.com(46 zip files) or you can order disks via metalink account.
2. Unzip these files and this should create five directory startCD, oraAppDB, oraApps, oraDB, oraiAS
O. S. Requirement
1. Linux Package : make sure you have ar, gcc, g++, ld, ksh, make, X Display Server
2. Disk Space : 26 GB for Application Tier & 65 GB for Vision Database (31 GB for fresh database). Hence total 57 GB for fresh DB & 91 GB for Vision Instance.
3. If you are installing apps 11.5.10.2 from Staging area you need another 24GB (No need if you are doing install from inserting CD’s on prompt)
4. O.S. User : Create two operating system user, avis11i (Application Tier) & ovis11i (Database Tier) both belonging to group DBA. You can use single user as well for both Application Tier & Database Tier
5. JDK : No need to install JDK 1.4.2 on solaris, Linux or windows as 11i Installer will install it. For other operating system you need to install JDK 1.4.2
6. For full list of RPM’s required on Red Hat Enterprise Linux Visit Metalink Note # 303859.1
Things you must do/know before installation
A) set environment variable LD_ASSUME_KERNEL=2.4.19 for root user
B) gcc -v (Should be of version 3.2.x) For any other version
mv /usr/bin/gcc /usr/bin/gcc.orig
mv /usr/bin/g++ /usr/bin/g++.orig
ln -s /usr/bin/i386-redhat-linux-gcc32 /usr/bin/gcc
ln -s /usr/bin/i386-redhat-linux-g++32 /usr/bin/g++
C) If your installation fail some time restart installation by option restart like
“rapidwiz -restart”
D) If you try to access apps from linux machine from browser other than Mozilla (like KDE)you will get error message that “You have insufficient privileges for current operation”
E) Installer should be started from root user
Starting Installation
1. Go to Staging directory /stage_location/startCD/Disk1/rapidwiz/
2. ./rapidwiz
3. Create base directory under which you wish to install database & apps tier with proper permission (owner) (Five main directory - [SID]appl,[SID]comn,[SID]ora owned by application user (avis11i) & [SID]db, [SID]data owned by database o.s. user (ovis11i) )
Post Install
1. Set environment variable in O.S. user profile
/install_base/[sid]appl/APPSORA.env (For Application Tier User, avis11i)
/install_base/[sid]db/SID_hostname.env (For Application Tier User, ovis11i)
2. For start/stop services of Oracle Apps 11i visit
11i Startup/Shutdown Scripts
Error/Issues during 11i Install
Issue : RW-50004: Error code received when running external process. Check log file for details. Running Database Install Drivers for VIS Database
Check Logsat : $install_base/[sid]db/9.2.0/appsutil/log/[SID]_[hostname]/MMDDHHMM.log
Error while running adlnkoh.sh, log for adlnkoh.sh at $install_base/[sid]db /9.2.0/install/make.log
In make.log file libgcc_s.so : undefined reference to mailto:%60dl_iterate_phdr@GLIBC_2.2.4`
Fix : This issue is very well explained in Note : 363600.1 mailto:%27dl_iterate_phdr@GLIBC_2.2.4%27Error on Linux Running Rapidwiz
=--------------------------------------------------------------------------------------------------------
How To License A New Product in Oracle Applications
1. After purchasing a license for an Application Product/Module, the first thing is to use license manager to record that the product/module is now licensed. License manager can be run 2 ways:
a. log in through Oracle Application Manager (OAM) and select Site Map -> Administration tab -> License Manager
b. run adlicmgr.sh from AD_TOP/bin
Using both methods you can license by Module or by individual Product. Select the check box for the Module/Product to be licensed and Save/Next
2. The Products are now licensed but not ready to be used as none of the Forms/Packages etc would have been compiled and loaded into the Database for these new Products. Use adadmin to generate the files for the new Product/s
a. run adadminb. Select Generate Application Files menu
c. Select all of the following Menu options:
- Generate message files
- Generate forms files
- Generate report files
- Generate graphic files
- Generate product JAR files
d. Back to Main Menu
e. Select Compile/Reload Applications Database Entities menu
f. Select all of the following Menu options:
- Compile APPS schema
- Compile menu information
- Compile flexfields
3. Once complete, check that the Forms/JSPs for the new Products licensed now work. The Products are now ready to be configured.
4. Run autoconfig.
During the form generation process, adadmin reads a file named <prod>file.drv to build a list of objects to generate.
For example if you are looking at the AZ module forms, there will be a file called azfile.drv. This file is located in $PROD_TOP/admin/driver.
In this example this is $AZ_TOP/admin/driver.
NOTE – If a product not installed, adpatch does not regenerate forms for that product at all.
You can test this by putting a dummy form name under entries for formsdev and forms. This dummy form will be displayed when prompted to select forms for generation via adadmin.
- Any patches that install a new form or remove an existing form will contain an appropriately updated version of <prod>file.drv.
Possibly related posts: (automatically generated)
Q: Which Concurrent Managers (CCMs) are supported by the Sysadmin team?
- Internal Concurrent Manager (ICM)
- Standard Manager
- Conflict Resolution Manager (CRM)
The setup of product-specific managers related issues should
be directed to the associated product group, i.e. the Inventory manager
Q: Where do the concurrent request output and log files reside?
A: $APPLCSF/out or $Product_Top/out for output files
$APPLCSF/log or $Product_Top/log for log files
Q: Where are temporary files located?
A: Temporary files reside in:
$APPLPTMP$APPLTMP
$REPORTS25_TMP (Release 11.0)
$REPORTS60_TMP (Release 11.5)
Q: How to change PMON method to LOCK.
To check the process monitor (PMON) method status:
Connect as database user “APPS”.
SELECT profile_option_value
FROM fnd_profile_option_values
WHERE level_id = 10001
AND level_value = 0
AND application_id = 0
AND profile_option_id =
(SELECT profile_option_id
FROM fnd_profile_options
WHERE profile_option_name = ‘CONC_PMON_METHOD’);
This should return one row with a value of ‘LOCK’
If the value is ‘RDBMS’ or ‘OS’ run the following script:
$FND_TOP/sql/AFIMPMON.SQL – this will set the PMON method to LOCK instead of RDBMS.
Bounce the database. If running on NT, restart the NT Server completely.
Within 11.5 Applications, the only PMON method is LOCK.
Q: How to start and shutdown the CCM on Unix as APPS
A: To Start:
STARTMGR sysmgr=APPS/passwd
To Shutdown:
concsub apps/<APPS password> sysadmin ‘System Administrator’ SYSADMIN CONCURRENT FND ABORT
11.5 => 11.5.4
adcmctl.sh apps/passwd start/stop prod
11.5.5 =>
adcmctl.sh start/stop apps/passwd prod
Q: How to terminate a concurrent request that cannot be cancelled?
A: Identify the request number to terminate. Shut down the concurrent managers and issue the following sql command as applsys:
update fnd_concurrent_requests
set status_code = ‘E’, phase_code = ‘C’
where Request_id = <reqnum>; (reqnum = request number)
Q: A Manager is not activating.
A: Check the count in sys.dual, system.dual, & apps.fnd_dual. There should only be one (1) row for each. If the count is greater, change to one only. This can be done from sqlplus as follows:
As user apps:
select *
from SYS.DUAL;
Any extra rows should be deleted.
delete rownum
from SYS.DUAL;
(rownum = the row number to delete)
Any extra rows for apps.fnd_dual must be removed by performing the following SQL command:
delete from fnd_dual
where rownum < (select max(rownum) from fnd_dual);
Bounce the Concurrent Managers.
Q: Internal Concurrent Manager.
A: If the ICM should go down, requests will continue to run normally, except for ‘queue control’ requests.
If the ICM should go down, you can restart it with ‘startmgr’. There is no need to shut down the other managers first.
Q: How to purge requests that are in Pending status.
A: The Purge Concurrent Requests program will only purge requests that are in Completed status. Set the status of the Pending requests to Completed
before purging them. The Internal Manager Must be DOWN!
Using sqlplus as APPLSYS perform the following:
UPDATE fnd_concurrent_requests
SET phase_code = ‘C’
WHERE phase_code = ‘P’
Q: Which Concurrent Managers (CCMs) are supported by the Sysadmin team?
- Internal Concurrent Manager (ICM)
- Standard Manager
- Conflict Resolution Manager (CRM)
The setup of product-specific managers related issues should
be directed to the associated product group, i.e. the Inventory manager
Q: Where do the concurrent request output and log files reside?
A: $APPLCSF/out or $Product_Top/out for output files
$APPLCSF/log or $Product_Top/log for log files
Q: Where are temporary files located?
A: Temporary files reside in:
$APPLPTMP$APPLTMP
$REPORTS25_TMP (Release 11.0)
$REPORTS60_TMP (Release 11.5)
Q: How to change PMON method to LOCK.
To check the process monitor (PMON) method status:
Connect as database user “APPS”.
SELECT profile_option_value
FROM fnd_profile_option_values
WHERE level_id = 10001
AND level_value = 0
AND application_id = 0
AND profile_option_id =
(SELECT profile_option_id
FROM fnd_profile_options
WHERE profile_option_name = ‘CONC_PMON_METHOD’);
This should return one row with a value of ‘LOCK’
If the value is ‘RDBMS’ or ‘OS’ run the following script:
$FND_TOP/sql/AFIMPMON.SQL – this will set the PMON method to LOCK instead of RDBMS.
Bounce the database. If running on NT, restart the NT Server completely.
Within 11.5 Applications, the only PMON method is LOCK.
Q: How to start and shutdown the CCM on Unix as APPS
A: To Start:
STARTMGR sysmgr=APPS/passwd
To Shutdown:
concsub apps/<APPS password> sysadmin ‘System Administrator’ SYSADMIN CONCURRENT FND ABORT
11.5 => 11.5.4
adcmctl.sh apps/passwd start/stop prod
11.5.5 =>
adcmctl.sh start/stop apps/passwd prod
Q: How to terminate a concurrent request that cannot be cancelled?
A: Identify the request number to terminate. Shut down the concurrent managers and issue the following sql command as applsys:
update fnd_concurrent_requests
set status_code = ‘E’, phase_code = ‘C’
where Request_id = <reqnum>; (reqnum = request number)
Q: A Manager is not activating.
A: Check the count in sys.dual, system.dual, & apps.fnd_dual. There should only be one (1) row for each. If the count is greater, change to one only. This can be done from sqlplus as follows:
As user apps:
select *
from SYS.DUAL;
Any extra rows should be deleted.
delete rownum
from SYS.DUAL;
(rownum = the row number to delete)
Any extra rows for apps.fnd_dual must be removed by performing the following SQL command:
delete from fnd_dual
where rownum < (select max(rownum) from fnd_dual);
Bounce the Concurrent Managers.
Q: Internal Concurrent Manager.
A: If the ICM should go down, requests will continue to run normally, except for ‘queue control’ requests.
If the ICM should go down, you can restart it with ‘startmgr’. There is no need to shut down the other managers first.
Q: How to purge requests that are in Pending status.
A: The Purge Concurrent Requests program will only purge requests that are in Completed status. Set the status of the Pending requests to Completed
before purging them. The Internal Manager Must be DOWN!
Using sqlplus as APPLSYS perform the following:
UPDATE fnd_concurrent_requests
SET phase_code = ‘C’
WHERE phase_code = ‘P’
Oracle has made the process of upgrading from Oracle8i or Oracle9i databases simple by automating a large portion of the upgrade process.
Here are the upgrade paths that you can take to move up to Oracle Database 10g Release 2 (10.2):
• If you are moving from Oracle 7.3.3 or lower, or Oracle 7.3.4, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.1.5, or 8.1.6, you can’t upgrade directly to Oracle Database 10g.
• If you are using an Oracle 8.1.7, 9.0.1, 9.2, or 10.1 database, you can upgrade directly.
Steps For Upgrading
1.) Install 10g Binaries on a separate ORACLE_HOME
2.) Patch 10g Binaries to the latest Patchset (à 10.2.0.4)
3.) Set env of 9i ORACLE_HOME
4.) Connect to 9i DB
5.) Create a new tablespace called SYSAUX
- Of size 500MB
- Automatic segment space management
- Locally managed
SQL> CREATE TABLESPACE sysaux DATAFILE ‘/oracle/oradata/prod/sysaux01.dbf’
SIZE 500M REUSE
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO;
6.) Increase the size of system tablespace (Min 500MB à 1Gig)
7.) Shutdown DB & lsnr
8.) Take a cold backup of the database
9.) Set env to 10g ORACLE_HOME
- Ensure PATH is pointing to 10g ORACLE_HOME
- Export the SID to the above DB
10.) cp init<SID>.ora or spfile<SID>.ora from 9i ORACLE_HOME to 10g ORACLE_HOME
11.) run pre 10g verification steps
- cd 10g ORACLE_HOME/rdbms/admin
- sqlplus ‘/as sysdba’
- startup migrate
- Pre-Upgrade Information Tool will do a lot of the work for you. Just make sure that you implement the recommended changes and you will be ready to upgrade to Oracle Database 10g.
The Pre-Upgrade Information Tool is actually a SQL script, called utlu102i.sql (in $ORACLE_HOME/rdbms/admin). Here’s how you invoke the Pre-Upgrade Information Tool:
SQL> @ $ORACLE_HOME/rdbms/admin/utlu102i.sql
Oracle Database 10.2 Upgrade Information Tool
02-20-2005 16:45:48
Database:
———
–> name: FINANCE
–> version: 8.1.7.0.0
–> compatibility: 8.1.0
WARNING: Database compatibility must be set to 9.2.0 prior to upgrade.
. . .
PL/SQL procedure successfully completed.
- Shutdown immediate
12.) Partial Output of the Pre-Upgrade Information Tool
*************************************************************************
Database:
–> name: FINANCE
–> version: 8.1.7.0.0
–> compatibility: 8.1.0
WARNING: Database compatibility must be set to 9.2.0 prior to upgrade.
***********************************************************************
Update Parameters: [Update Oracle Database 10.2 init.ora or spfile]
WARNING: –> “shared_pool_size” needs to be increased to at least “150944944″
*************************************************************************
Obsolete Parameters: [Update Oracle Database 10.2 init.ora or spfile]
–> “job_queue_interval”
–> “max_enabled_roles”
*************************************************************************
Components: [The following database components will be upgraded or installed]
–> Oracle Catalog Views [upgrade]
–> Oracle Packages and Types [upgrade]
…
*************************************************************************
SYSAUX Tablespace: [Create tablespace in Oracle Database 10.2 environment]
–> New “SYSAUX” tablespace
…. minimum required size for database upgrade: 500 MB
Please create the new SYSAUX Tablespace AFTER the Oracle Database
10.2 server is started and BEFORE you invoke the upgrade script.
Make all the changes pointed out by the Pre-Upgrade Information Tool before proceeding with
the upgrade.
13.) Verify output and make necessary checks as recommended in the init file and/or tbs file sizes
14.) Perform dbupgrade
Sqlplus ‘/as sysdba’
Startup migrate
Run the upgrade script
SQL> @$ORACLE_HOME/rdbms/admin/catupgrd.sql
Oracle will create, drop, and alter some database objects as the upgrade process progresses, thus invalidating some internal Oracle packages and procedures. After the upgrade script has finished, you need to check for invalid objects:
SQL> SELECT count(*) FROM DBA_OBJECTS
2 WHERE status = ‘INVALID’;
You can recompile all invalidated Oracle database objects using the utlrp.sql script:
SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql
15.) Upgrade java
- Create or replace java system
16.) The upgrade status of each database component by querying the DBA_SERVER_REGISTRY view.
Querying the DBA_SERVER_REGISTRY View for Post-Upgrade Information
SQL> SELECT comp_id, comp_name, version, status
FROM DBA_SERVER_REGISTRY;
COMP_ID COMP_NAME- VERSION STATUS
—————- —————————————————- ————— ————
CATALOG Oracle Database Catalog Views 10.2.0.0.0 VALID
CATPROC Oracle Database Packages and Types 10.2.0.0.0 VALID
JAVAVM JServer JAVA Virtual Machine 10.2.0.0.0 VALID
CATJAVA Oracle Database Java Packages 10.2.0.0.0 VALID
CONTEXT Oracle Text 10.2.0.0.0 VALID
17.) Now shut down and restart the instance so you’re ready for normal database operations.
18.) Create new listener and tns files
19.) Gather schema and dictionary stats
20.) Perform the cold backup of the database
OPATCH Utility
- OPatch is a java based utility that allow the application and rolling back of interim patches to an Oracle product. The program has sub-commands that may take arguments. The program requires Java(JVM) to be present on the current system.OPatch expects users to have commands such as fuser, jar, ar and make on Unix platforms and jar on Windows platforms to be available in their PATH.
Opatch Details
How to check the Opatch version?
-bash-3.00$ ./opatch version
Invoking OPatch 10.2.0.3.0
Invoking OPatch 10.2.0.3.0
OPatch Version: 10.2.0.3.0
OPatch succeeded.
How to know which version is the correct version of Opatch for your RDBMS home?
You can verify whether the Opatch version for your RDBMS release is correct or not using metalink note ID 357221.1.
This note ID gives the copatibilities between OPatch version and RDBMS version.
How to get the latest version of OPatch?
You can download the latest version of OPatch from metalink using following URL.
http://updates.oracle.com/download/6880880.html
In the release dropdown you can select the OPatch release that you want to download based on your RDBMS version. Please read the README.txt before applying the patch.
What is Oracle Database Inventory and where it is located?
Oracle Inventory is the location or the place where all the information about an Oracle Home is stored and maintained. When ever we install an RDBMS Oracle Home, a new inventory gets created. Applying any new patch to Oracle Home will update the invnrtory for that Oracle Home and record the details for the patch applied. This inventory is in the form of XML files.
The location of inventory is defined in a file called oraInst.loc. The path for this file is provided while installing Oracle Home. If we dont supply any path, the is file will be present at central location /etc/oraInst.loc. Also we can have a central inventory if its not used by any other oracle installation. If the central inventory is used by previous Oracle installation we can create local inventory. The content of oraInst.loc file is as shown below.
-bash-3.00$ cd $ORACLE_HOME
-bash-3.00$ cat oraInst.loc
inventory_loc=/slot/ems2029/appmgr/apps/tech_st/10.1.2/oraInventory
inst_group=ems2029
-bash-3.00$
-bash-3.00$ cat oraInst.loc
inventory_loc=/slot/ems2029/appmgr/apps/tech_st/10.1.2/oraInventory
inst_group=ems2029
-bash-3.00$
Here “inventory_loc” gives the location of Inventory directory where as inst_group gives the name of the group which is the owner of this inventory.
How to create Local Inventory?
You can create local inventory at any location while installing Oracle Home. You need to use -invPtrLoc variable along with runInstaller command and give the location of oraInst.loc. Otherwise the default path assumed for oraInst.loc is /etc/oraInst.loc.
./runInstaller -invPtrLoc /slot/ems2029/appmgr/apps/tech_st/10.1.2/oraInst.loc
After the installation starts it will ask for location of oraInventory directory and group which should own it. It will make entry of these into oraInst.loc file.
Having know the above information about opatch, now we will move to details about using opatch and various options available.
Opatch help
You can get all the options using opatch -help
-bash-3.00$ ./opatch -help
Invoking OPatch 11.1.0.6.0
Invoking OPatch 11.1.0.6.0
Oracle Interim Patch Installer version 11.1.0.6.0
Copyright (c) 2007, Oracle Corporation. All rights reserved.
Copyright (c) 2007, Oracle Corporation. All rights reserved.
Usage: opatch [ -help ] [ -r[eport] ] [ command ]
command := apply
lsinventory
prereq
query
rollback
util
version
lsinventory
prereq
query
rollback
util
version
<global_arguments> := -help Displays the help message for the command.
-report Print the actions without executing.
-report Print the actions without executing.
example:
‘opatch -help’
‘opatch apply -help’
‘opatch lsinventory -help’
‘opatch prereq -help’
‘opatch rollback -help’
‘opatch util -help’
‘opatch -help’
‘opatch apply -help’
‘opatch lsinventory -help’
‘opatch prereq -help’
‘opatch rollback -help’
‘opatch util -help’
OPatch succeeded.
You can get specific help for any command of opatch using opatch <command> -help. Example opatch apply -help.
Applying single patch using opatch
1. You MUST read the Readme.txt file included in opatch file, look for any prereq. steps/ post installation steps or and DB related changes. Also, make sure that you have the correct opatch version required by this patch.
2.Make sure you have a good backup of database.
3. Make a note of all Invalid objects in the database prior to the patch.
4. Shutdown All the Oracle Processes running from that Oracle Home , including the Listener and Database instance, Management agent etc.
5. You MUST Backup your oracle Home and Inventory
2.Make sure you have a good backup of database.
3. Make a note of all Invalid objects in the database prior to the patch.
4. Shutdown All the Oracle Processes running from that Oracle Home , including the Listener and Database instance, Management agent etc.
5. You MUST Backup your oracle Home and Inventory
tar cvf – $ORACLE_HOME $ORACLE_HOME/oraInventory | gzip > Backup_Software_Version.tar.gz
6. Unzip the patch in $ORACLE_HOME/patches
If you are applying a single intrim patch to oracle home, then change the location to the directory of that patch and then invoke following command.
Example if I need to apply patch 6972343 to RDBMS Oracle Home
-bash-3.00$ cd 6972343
-bash-3.00$ pwd
/slot/ems2029/oracle/db/tech_st/11.1.0/patches/6972343
-bash-3.00$ ls
etc files README.txt
$ORACLE_HOME/OPatch/opatch apply
-bash-3.00$ pwd
/slot/ems2029/oracle/db/tech_st/11.1.0/patches/6972343
-bash-3.00$ ls
etc files README.txt
$ORACLE_HOME/OPatch/opatch apply
If you have created local inventory then you need to give the correct path for local inventory stored in oraInst.loc. If you have updated /etc/oraInst.loc with correct location of your inventory, then above command will work, If not you can give the correct location by giving local oraInst.loc file.
$ORACLE_HOME/OPatch/opatch apply -invPtrLoc /slot/ems2029/oracle/db/tech_st/11.1.0/oraInst.loc
Remember that when we are applying patch, patch number is NOT provided as an input to opatch command. So we have to to be in the directory of patch since opatch will pick the patch files from current directory.
Rolling back a patch
In case if a patch did not fix the issue or if you has applied wrong patch to oracle home, you can always rollback the patch using following comamnd.
opatch rollback -id <Patch Number>
Applying bundle patches
Some times if you have to apply bundle patch having many patches, example lets say you want to a bundle patch 6778860 ( 11.1.0.6 BUNDLED PATCH FOR EBS 11I)) containing many other patches to RDBMS home, OPatch provides a facility to apply many patches to RDBMS home using a single comamnd. Following command should be used for applying bundle patches.
Download the patch and extract the same. You will see many directories (one for each patch) inside the main patch directory. Execute following command to apply all patches.
$ORACLE_HOME/OPatch/opatch util NApply -invPtrLoc /slot/ems2029/oracle/db/tech_st/11.1.0/oraInst.loc
NApply -> Will apply all patches to RDBMS home.
You can also use -phBaseDir to point to the directory where bundle patch is installed. So you can run opatch command from any location
$ORACLE_HOME/OPatch/opatch util NApply -phBaseDir /slot/ems2029/oracle/db/tech_st/11.1.0/patches/6778860 -invPtrLoc /slot/ems2029/oracle/db/tech_st/11.1.0/oraInst.loc
You can also apply specific patches using NApply
opatch util napply <patch_location> -id 1,2,3 -skip_subset -skip_duplicate
This will apply patches 1, 2, and 3 which are under < the patch_location> directory. OPatch will skip duplicate patches and subset patches (patches under <patch_location> that are subsets of patches installed in the ORACLE_HOME)
You can see all the options for NApply using following help command.
$ORACLE_HOME/OPatch/opatch util NApply -help
Query the inventory for patches applied
We can query the inventory to check various components installed for database as well as to check various patches applied to database. Use following command to get a minimum information from inventory about patches applied and components installed.
$ORACLE_HOME/OPatch/opatch lsinventory -invPtrLoc /slot/ems2029/oracle/db/tech_st/11.1.0/oraInst.loc
Patch 5763576 : applied on Wed May 28 03:20:53 PDT 2008
Created on 6 Feb 2008, 02:26:04 hrs PST8PDT
Bugs fixed:
5763576
Created on 6 Feb 2008, 02:26:04 hrs PST8PDT
Bugs fixed:
5763576
If you are using central inventory then -invPtrLoc variable is not required.
You can also get the detailed view of inventory using following command. In case of detail information it gives which are the files that this patch have touched.
$ORACLE_HOME/OPatch/opatch lsinventory -detail -invPtrLoc /slot/ems2029/oracle/db/tech_st/11.1.0/oraInst.loc
Patch 6318357 : applied on Wed May 28 03:33:27 PDT 2008
Created on 4 Dec 2007, 22:02:16 hrs PST8PDT
Bugs fixed:
6318357
Files Touched:
udjvmrm.sql –> ORACLE_HOME/javavm/install/udjvmrm.sql
Patch Location in Inventory:
/slot/ems2029/oracle/db/tech_st/11.1.0/inventory/oneoffs/6318357
Patch Location in Storage area:
/slot/ems2029/oracle/db/tech_st/11.1.0/.patch_storage/6318357_Dec_4_2007_22_02_16
Created on 4 Dec 2007, 22:02:16 hrs PST8PDT
Bugs fixed:
6318357
Files Touched:
udjvmrm.sql –> ORACLE_HOME/javavm/install/udjvmrm.sql
Patch Location in Inventory:
/slot/ems2029/oracle/db/tech_st/11.1.0/inventory/oneoffs/6318357
Patch Location in Storage area:
/slot/ems2029/oracle/db/tech_st/11.1.0/.patch_storage/6318357_Dec_4_2007_22_02_16
Which options are installed in Oracle Home?
You can check the options installed in RDBMS home using above command. The options installed will be listed at the start of output.
Example: $ORACLE_HOME/OPatch/opatch lsinventory -detail -invPtrLoc /slot/ems2029/oracle/db/tech_st/11.1.0/oraInst.loc
Example: $ORACLE_HOME/OPatch/opatch lsinventory -detail -invPtrLoc /slot/ems2029/oracle/db/tech_st/11.1.0/oraInst.loc
Opatch Log files
Log file for Opatch utility can be found at $ORACLE_HOME/cfgtoollogs/opatch
Advanced Option for OPatch
Here are some of the advanced options of OPatch utility.
UpdateRemoteNodes
It is used to propagate/remove files/directories to/from remote nodes using files under ORACLE_HOME/.patch_storage/<ID>/rac/*.
The directories listed in copy_dirs.txt will be copied to remote nodes.
The files listed in copy_files.txt wil be copied to remote nodes.
The directories listed in remove_dirs.txt will be deleted from remote nodes.
The files listed in remove_files.txt will be deleted from remote nodes.
This is used where RAC setup is present.
The files listed in copy_files.txt wil be copied to remote nodes.
The directories listed in remove_dirs.txt will be deleted from remote nodes.
The files listed in remove_files.txt will be deleted from remote nodes.
This is used where RAC setup is present.
Cleanup
It is used to clean up ‘restore.sh, make.txt’ files and ‘rac, scratch, backup’ directories in the ORACLE_HOME/.patch_storage directory. If -ps option is used, then it cleans the above specified areas only for that patch, else for all patches under ORACLE_HOME/.patch_storage. You will be still able to rollback patches after this cleanup.
Example: opatch util cleanup -ps 6121183_Ju _21_2007_04_19_42
Example: opatch util cleanup -ps 6121183_Ju _21_2007_04_19_42
CopyListedFiles
It is used to copy all files listed in ORACLE_HOME/.patch_storage/<ID>/rac/copy_files.txt to remote nodes. If -fp option is used, then one can specify the path of the file containing the list of files to be copied. The files mentioned in this file will be copied to the remote nodes.
Example: opatch util copylistedfiles -fp a -remote_nodes ceintcb-a5
This is used where RAC setup is present.
Example: opatch util copylistedfiles -fp a -remote_nodes ceintcb-a5
This is used where RAC setup is present.
CopyListedFilesTest
It is used to copy a single file to remote nodes. The usage remains the same as CopyListedFiles.
Example: opatch util copylistedfilestest -fp /home/oracle/a -remote_nodes ceintcb-a5
This is used where RAC setup is present.
Example: opatch util copylistedfilestest -fp /home/oracle/a -remote_nodes ceintcb-a5
This is used where RAC setup is present.
CopyListedDirs
It is used to recursively copy all directories listed in ORACLE_HOME/.patch_storage/<ID>/rac/copy_dirs.txt to remote nodes. If -dp option is used, then one can specify the path of the file containing the list of directories to be copied. The directories mentioned in this file will be copied to the remote nodes.
This is used where RAC setup is present.
This is used where RAC setup is present.
CopyListedDirsTest
It is used to copy a single file to remote nodes. The usage remains the same as CopyListedDirs.
This is used where RAC setup is present.
This is used where RAC setup is present.
RemoveListedFiles
It is used to remove files listed in ORACLE_HOME/.patch_storage/<ID>/rac/remove_files.txt on remote nodes. If -fr option is used, then one can specify the path of the file containing the list of files to be removed. The files mentioned in this file will be removed from the remote nodes.
This is used where RAC setup is present.
This is used where RAC setup is present.
RemoveListedFilesTest
It is used to remove a single file from remote nodes. The usage remains the same as RemoveListedFiles.
This is used where RAC setup is present.
This is used where RAC setup is present.
RemoveListedDirs
It is used to recursively remove directories listed in ORACLE_HOME/.patch_storage/<ID>/rac/remove_dirs.txt from remote nodes. If -dr option is used, then one can specify the path of the file containing the list of directories to be removed. The directories mentioned in this file will be removed from the remote nodes.
This is used where RAC setup is present.
This is used where RAC setup is present.
RemoveListedDirsTest
It is used to remove a single directory from remote nodes. The usage remains the same as RemoveListedDirs.
This is used where RAC setup is present.
This is used where RAC setup is present.
RunLocalMake
It is used to invoke re-link on the local node. The make commands are stored in ORACLE_HOME/.patch_storage/<ID>/make.txt. You need to use the -ps option to specify the Patch ID with timestamp. A directory by this name will be present under ORACLE_HOME/.patch_storage. The make.txt file present under ORACLE_HOME/.patch_storage/<Patch ID with timestamp>/ will be used to perform the local make operation. This command cannot be run if you have already run Cleanup as it would have removed these make.txt files.
Example: opatch util runlocalmake -ps 6121250_ un_21_2007_04_16_11
RunRemoteMake
It is used to invoke re-link on remote nodes. The make commands are stored in
ORACLE_HOME/.patch_storage/<ID>/rac/makes_cmd.txt. The usage remains the same as RunLocalMake.
This is used where RAC setup is present.
ORACLE_HOME/.patch_storage/<ID>/rac/makes_cmd.txt. The usage remains the same as RunLocalMake.
This is used where RAC setup is present.
RunAnyCommand
It is used to run any command on remote nodes. The command should be specified using the -cmd option.
Example: opatch util runanycommand -remote_nodes ceintcb-a5 -cmd ls
This is used where RAC setup is present.
Example: opatch util runanycommand -remote_nodes ceintcb-a5 -cmd ls
This is used where RAC setup is present.
LoadXML
It is used to check the validity of an XML file. The -xmlInput option can be used to specify the path of the xml file.
@ Support can use this utility to verify the integrity of XML files contained in the local and central inventory.
Example: opatch util loadxml -xmlInput $ORACLE_HOME/inventory/ContentsXML/comps.xml
Example: opatch util loadxml -xmlInput $ORACLE_HOME/inventory/ContentsXML/comps.xml
Verify
It is used to run the patch verification process to ensure that the patch was applied to the ORACLE_HOME. It uses the defined ORACLE_HOME and the given patch location via -ph, to run the check.
@ Support can use this utility to re-run the OPatch verification stage, if required for patch diagnosis. The patch staging area has to be present or created.
Example: opatch util verify -ph ~/6646853/6121183
Troubleshooting
Some times the inventory get corrupted because of some issues. In that case you need to repair the inventory. Following are the two methods which I know can be used to repair the inventory.
1) Development has released a utility (checkinv) which can be use to repair the inventory if it becomes corrupted for some reason.
Please note that this version of checkinv works only for 9.2 and 10.1 releases of oracle database. This doesn’t work for 10.2 releases of oracle database.
You can download the checkinv utility from Patch 4121946.
To cleanup the components, you should determine the unwanted or dangling components, then specify those using the option “-remcomp”, to cleanup the component list.
The utility detects and asks user’s permission to repair a bad inventory. In case you want to repair the inventory, the utility will first back up the files before any modification.
However, it is better that you backup the inventory before running the tool.
For more details, check metalink note ID 298906.1
2) Creating a new inventory using Oracle Universal Installer (OUI).
What does Rapidwiz actually do?
The basics of how this Rapid Wizard installation works are:-
1. RapidWizard collects user information required for configuration of system, and creates a configuration file
2. RapidWizard checks Port availability and file space required
3. Zip files from the “oraDB and oraAppDB” DVD stage area are then uncompressed onto the file system
4. Each Disk directory contains a driver which is read to control the unzip phase
5. The DB Techstack is relinked and reconfigured using an install driver, templates and the configuration file
6. Control files are created
7. The RDBMS ORACLE_HOME is registered into the Global Inventory
8. The DB is started, and further configuration is performed
9. Zip files from the “oraAS” (Developer Tools and As10g” DVD stage area are then uncompressed onto the file system
10. The Apps Techstack is relinked and reconfigured using the install driver, templates and the configuration file
11. The Developer Tools and As10g ORACLE_HOMEs are registered into the Global Inventory
12. Zip files from the “oraApps” (APPL_TOP, COMMON_TOP etc) stage are uncompressed onto the file system
13. APPL_TOP is reconfigured with system using values in the configuration file and services are started
14. Post install checks are performed to check success of the installation.
1. RapidWizard collects user information required for configuration of system, and creates a configuration file
2. RapidWizard checks Port availability and file space required
3. Zip files from the “oraDB and oraAppDB” DVD stage area are then uncompressed onto the file system
4. Each Disk directory contains a driver which is read to control the unzip phase
5. The DB Techstack is relinked and reconfigured using an install driver, templates and the configuration file
6. Control files are created
7. The RDBMS ORACLE_HOME is registered into the Global Inventory
8. The DB is started, and further configuration is performed
9. Zip files from the “oraAS” (Developer Tools and As10g” DVD stage area are then uncompressed onto the file system
10. The Apps Techstack is relinked and reconfigured using the install driver, templates and the configuration file
11. The Developer Tools and As10g ORACLE_HOMEs are registered into the Global Inventory
12. Zip files from the “oraApps” (APPL_TOP, COMMON_TOP etc) stage are uncompressed onto the file system
13. APPL_TOP is reconfigured with system using values in the configuration file and services are started
14. Post install checks are performed to check success of the installation.
How To Get Log Files From Various Programs For Oracle Apps
1. CONCURRENT PROGRAMS
——————————————
two methods to see concurrent program logs :
——————————————
two methods to see concurrent program logs :
a. directly from Oracle Applications :
System Administrator responsability (for own and other users requests) :
Navigator: Concurrent => Requests, button View Log…
Other responsabilities (for own requests), menus could be different:System Administrator responsability (for own and other users requests) :
Navigator: Concurrent => Requests, button View Log…
Navigator: Requests , button View Log…
Navigator: Other => Requests , button View Log…
Navigator: Other => Requests => View , button View Log…
Navigator: Control => Requests => View , button View Log…
b. retrieve Concurrent Program log files under :
$/$APPLLOG
or if you have defined common directory :
$APPLCSF/$APPLLOG
File format is :
l.req
2. CONCURRENT MANAGERS
——————————————
two methods to see concurrent manager logs :
a. directly from Oracle Applications :
System Administrator responsability
Navigator: Concurrent => Requests, choose a request …
menu: Special => Manager Log
or
Navigator: Concurrent => Manager => Administer, button Processes (Concurrent Processes window)
=> button Manager Log
b. retrieve Manager log files under :
$FND_TOP/$APPLLOG
or if you have defined common directory :
$APPLCSF/$APPLLOG
File format is :
w.mgr3. INTERNAL MANAGER
————————————-
two methods to see internal manager log :
a. directly from Oracle Applications :
System Administrator responsability
Navigator: Concurrent => Manager => Administer, button Processes (Concurrent Processes window)
=> button Internal Manager Log
b. retrieve Internal Manager log file under :
$FND_TOP/$APPLLOG
or if you have defined common directory :
$APPLCSF/$APPLLOG
File format is :
.mgr
(mgrname which figures in startmgr file is ‘std’ by default)
4. AD, FND AND OTHER UTILITIES
—————————————————-
Some AD utilities like adpatch, adadmin, etc. generate log file under
$APPL_TOP/admin or $APPL_TOP/install/log, file names are :
adunload.log
adrelink.log
adlibout.log
adlibin.log
adfrmgen.log
admrgpch.log
adrepgen.log
adctrl.log
admvcode.log
adaimgr.log
adwork01.log, adwork02.log, adwork03.log, …
Utility adodfcmp generates log file under $/admin/odf/
or $/patch//odf/, file name is:
adodfcmp.log
FND utilities like fdfcmp, FNDFFVGN, FNDMDGEN generate log file under
$APPL_TOP/admin or $APPL_TOP/install/log, file name is :
L.req
5. USER EXITS
———————-
User exits from forms generate log file under directory from where the forms
server is started if variable FDUDEBUG is set to ON. File name is:
userexit.log
6. FORMS SERVER
—————————
When starting forms server you can specify a log file name.
Exemples:
WIN/NT
f60srv32 log=c:\temp\f60srv.log
Unix
f60ctl start log=/temp/f60srv.log
f45ctl start port=9000 log=/temp/forms.log>
7. SQL*NET, NET8 LISTENER
——————————————-
You can specify LOG_DIRECTORY_ and LOG_FILE_ specific values for theses parameters in listener.ora. You can set LOG_FILE and TRACE_FILE variables from a lsnrctl session. There are also LOG_DIRECTORY_SERVER and LOG_FILE_SERVER parameters in sqlnet.ora.
8. APACHE, JSERV
————————–
Logs from Apache server are under $APACHE_TOP/logs, file names are :
error_log, access_log, httpds_access_log, httpds_error_log, sqlnet.log
Logs from Jserv are under $ORACLE_HOME/Apache/Jserv/logs , file names are :
jserv.log, debug.log
Note: it is recommended to clean up these log files, shutdown and restart apache server before trying to reproduce the issue and analyze.
9. SSP5 (iPROCUREMENT)
—————————————
Apache and Jserv logs are useful to check for iProcurement (SSP5), you can also add these lines in ssp_init.txt (should be under $ORACLE_HOME/Apache/Jserv/etc) to generate specific SSP5 log file :
DebugOutput= (preferably under $APACHE_TOP/logs)
DebugLevel=5
DebugSwitch=ON
Note: don’t forget to restart Apache server after editing ssp_init.txt.DebugLevel=5
DebugSwitch=ON
10. DATABASE
———————-
In case of ORA- and other database errors it could be useful to check the
file alert.log.
You should find it under bdump directory (background_dump_dest parameter)
or $ORACLE_HOME/rdbms/log.
or $ORACLE_HOME/rdbms/log.
The oraInventory is the location for the OUI (Oracle Universal Installer)’s bookkeeping. The inventory stores information about:
- All Oracle software products installed in all ORACLE_HOMES on a machine
- Other non-Oracle products, such as the Java Runtime Environment (JRE)
In a 11i Application system the RDBMS and iAS ORACLE_HOMEs are registered in the oraInventory. The 806 ORACLE_HOME, which is not managed through OUI, is not.
On Unix/Linux, the location of the oraInventory is defined by the content of oraInst.loc, at:
- /var/opt/oracle/oraInst.loc on Solaris, HP-UX and Tru64
- /etc/oraInst.loc on Linux and AIX
On Windows, the location of the oraInventory is defined by the value of the registry key HKEY_LOCAL_MACHINE|Software\Oracle\INST_LOC or if this value is not defined, at C:\Program Files\Oracle\Inventory.
- /var/opt/oracle/oraInst.loc on Solaris, HP-UX and Tru64
- /etc/oraInst.loc on Linux and AIX
On Windows, the location of the oraInventory is defined by the value of the registry key HKEY_LOCAL_MACHINE|Software\Oracle\INST_LOC or if this value is not defined, at C:\Program Files\Oracle\Inventory.
=> Before OUI 2.X, the oraInventory was binary.
=> Starting with OUI 2.X and 11.5.8, the information in the inventory is stored in Extensible Markup Language (XML) format. It is called XML oraInventory.
XML inventory is divided into 2 distinct components:
- Global (or Central) Inventory
- Local (or Home) Inventory
How To License A New Product in Oracle Applications
1. After purchasing a license for an Application Product/Module, the first thing is to use license manager to record that the product/module is now licensed. License manager can be run 2 ways:
a. log in through Oracle Application Manager (OAM) and select Site Map -> Administration tab -> License Manager
b. run adlicmgr.sh from AD_TOP/bin
Using both methods you can license by Module or by individual Product. Select the check box for the Module/Product to be licensed and Save/Next
To get everything relinked and to ensure that the adadmin Utility was relinked before it is used, follow these steps :
Release 11i (AutoConfig enabled) :
Technology Stack Binaries inclusive Database :
1.Source the RDBMS ORACLE_HOME Environment
2.Execute the script $ORACLE_HOME/appsutil/install/adlnkoh.sh
3.Source the iAS ORACLE_HOME Envrionment
4.Execute the script $ORACLE_HOME/bin/adlnkiAS.sh
5.Source the APPS Environment
6.Execute the script $ORACLE_HOME/bin/adlnk806.sh
Oracle E-Business-Suite Binaries :
1. Source the APPS Environment
2. Execute following command :
adrelink.sh force=y “ad adadmin”
If you are using the command
adrelink.sh force=y “ad all”
you are relinking all binaries under the $AD_TOP/bin – otherwise the AD Utilities are relinked via the adadmin Utility.
3. Execute adadmin
select –> ’2. Maintain Applications Files menu’
select –> ’1. Relink Applications programs’
–> select all modules to relink
Before starting the Instance, please open a new shell and source the Environment
What is cloning?
Cloning is the process of creating an identical copy of an already existing Oracle Applications system.
What are the differences between the two cloning methods?
- Cloning Oracle Applications Release 11i was originally published in conjunction with Release 11.5.5 and is applicable for all 11i releases up to 11.5.5 that are not AutoConfig enabled.
- Cloning Oracle Applications Release 11i with Rapid Clone is applicable for all 11i systems that have migrated to AutoConfig and enabled Rapid Clone. This method contains steps to install AutoConfig and Rapid Clone.
How do i determine if my system is AutoConfig enabled?
- Open the environment file APPSORA.env in your APPL_TOP. If the top of the file says that it is maintained by AutoConfig, then your system is probably using AutoConfig.
- Check if there is an Applications Context file in the APPL_TOP/admin directory. This file will typically be named <SID>.xml or <SID>_<HOSTNAME>.xml.
Check if there is an Applications Context file in the RDBMS ORACLE_HOME under the appsutil directory. This file will typically be named <SID>.xml or <SID>_<HOSTNAME>.xml.
Pre-cloning Tasks
1. Apply application tier patches using adpatch
Apply patch 4038964
Apply patch 4175764
Apply patch 4175764
Both the above patches are include in the consolidated update 2 or CU2 so in case you are on 11.5.10.2 or later you can ignore this step.
2. Maintain snapshot information
Log in as the applications user on each application tier node and run ‘Maintain Snapshot Information’ by using adadmin.
3. Merge existing APPL_TOPs
Log in to the primary node of your application tier as the application user user and run:
$ cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME]
$ perl adpreclone.pl appsTier merge
$ perl adpreclone.pl appsTier merge
This will prompt you with option to merge secondary nodes
Now log in as the applications user to each of the secondary application tier nodes being merged and run:
$ cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME]
$ perl adpreclone.pl appltop merge
$ perl adpreclone.pl appltop merge
4. Prepare the source system database tier.
Log on to the database tier of the source system as the oracle user and run the following commands:
$ cd [RDBMS ORACLE_HOME]/appsutil/scripts/[CONTEXT_NAME]
$ perl adpreclone.pl dbTier
$ perl adpreclone.pl dbTier
With this all the pre clone tasks on the source system have been completed.
Steps to be performed on target system
1. Create OS user accounts
Create a OS user account for your applications
$ useradd -g dba -d [home_directory] -p password username
Similarly create a OS user account for your database
2. Modify the orainventory to reflect the new location
$ vi /etc/oraInst.loc
3. Copy the following application tier directories
Copy the following application tier directories from the primary node of your source system to the target application tier node, retaining the original directory structure:
– [APPL_TOP]
– [OA_HTML]
– [OA_JAVA]
– [COMMON_TOP/util]
– [COMMON_TOP/clone>
– [806 ORACLE_HOME]
– [iAS ORACLE_HOME]
– [OA_HTML]
– [OA_JAVA]
– [COMMON_TOP/util]
– [COMMON_TOP/clone>
– [806 ORACLE_HOME]
– [iAS ORACLE_HOME]
After installing the Rapid Clone and AutoConfig patches, you are ready to clone an instance. There are ten basic steps involved. I have outlined them below:
1. Run system configuration on the Application tier:
/admin/scripts//adautocfg.sh
Use the APPS password when prompted.
2. Run system configuration on the database tier:
/appsutil//scripts/adautocfg.sh
Use the APPS password when prompted.
3. Copy AutoConfig to the RDBMS ORACLE_HOME:
Apply patch 2952369 to acquire adchkcfg utility.
Create appsutil.zip file by: perl /bin/admkappsutil.pl.
Copy appsutil.zip file to the
unzip -o appsutil.zip
4. Generate the database context file:
cd /appsutil/bin
adbldxml.sh tier=database appsuser= appspasswd=
Output log is written to: $ORACLE_HOME/appsuti/out//cfgcheck.
Use the APPS password when prompted.
2. Run system configuration on the database tier:
/appsutil//scripts/adautocfg.sh
Use the APPS password when prompted.
3. Copy AutoConfig to the RDBMS ORACLE_HOME:
Apply patch 2952369 to acquire adchkcfg utility.
Create appsutil.zip file by: perl /bin/admkappsutil.pl.
Copy appsutil.zip file to the
unzip -o appsutil.zip
4. Generate the database context file:
cd /appsutil/bin
adbldxml.sh tier=database appsuser= appspasswd=
Output log is written to: $ORACLE_HOME/appsuti/out//cfgcheck.
Steps for Manual Cloning
1) Restored the backup from the tape to the source destination.
2) Changed the ownership of all the directories.
chown -R appltest:dba *
chown -R oratest:dba * — Incase its multi-user.
3) Created a control file in the name of control.sql
In the source database … issue conmmand … alter database backup control file to trace;
We would find the trace file in udump.
Modify he contents of the control.sql to match the structure in the destination.
4) Changed the environment file to have the necessary settings and set the environment. Once you source the .env … it would give you the errors where it does not match and you may make the changes accordingly in various files.
.env file … please make sure that we change all the .env files. Even the ones in 8.0.6 and iAS Oracle Home along with the Appl_Top.
Also make the changes in the listener.ora, tnsnames.ora and sqlnet.ora.
Rename the folders too.
Make the changes in the .xml file.
Changes required would be in the hostname, Location, DB name, OS owners of Application and Database.
1. CONCURRENT PROGRAMS
——————————————
two methods to see concurrent program logs :
——————————————
two methods to see concurrent program logs :
a. directly from Oracle Applications :
System Administrator responsability (for own and other users requests) :
Navigator: Concurrent => Requests, button View Log…
System Administrator responsability (for own and other users requests) :
Navigator: Concurrent => Requests, button View Log…
Other responsabilities (for own requests), menus could be different:
Navigator: Requests , button View Log…
Navigator: Other => Requests , button View Log…
Navigator: Other => Requests => View , button View Log…
Navigator: Control => Requests => View , button View Log…
Navigator: Requests , button View Log…
Navigator: Other => Requests , button View Log…
Navigator: Other => Requests => View , button View Log…
Navigator: Control => Requests => View , button View Log…
b. retrieve Concurrent Program log files under :
$/$APPLLOG
or if you have defined common directory :
$APPLCSF/$APPLLOG
or if you have defined common directory :
$APPLCSF/$APPLLOG
File format is :
l.req
l.req
2. CONCURRENT MANAGERS
——————————————
two methods to see concurrent manager logs :
——————————————
two methods to see concurrent manager logs :
a. directly from Oracle Applications :
System Administrator responsability
Navigator: Concurrent => Requests, choose a request …
menu: Special => Manager Log
or
Navigator: Concurrent => Manager => Administer, button Processes (Concurrent Processes window)
=> button Manager Log
Navigator: Concurrent => Requests, choose a request …
menu: Special => Manager Log
or
Navigator: Concurrent => Manager => Administer, button Processes (Concurrent Processes window)
=> button Manager Log
b. retrieve Manager log files under :
$FND_TOP/$APPLLOG
or if you have defined common directory :
$APPLCSF/$APPLLOG
or if you have defined common directory :
$APPLCSF/$APPLLOG
File format is :
w.mgr
The oraInventory is the location for the OUI (Oracle Universal Installer)’s bookkeeping. The inventory stores information about:
- All Oracle software products installed in all ORACLE_HOMES on a machine
- Other non-Oracle products, such as the Java Runtime Environment (JRE)
In a 11i Application system the RDBMS and iAS ORACLE_HOMEs are registered in the oraInventory. The 806 ORACLE_HOME, which is not managed through OUI, is not.
On Unix/Linux, the location of the oraInventory is defined by the content of oraInst.loc, at:
- /var/opt/oracle/oraInst.loc on Solaris, HP-UX and Tru64
- /etc/oraInst.loc on Linux and AIX
On Windows, the location of the oraInventory is defined by the value of the registry key HKEY_LOCAL_MACHINE|Software\Oracle\INST_LOC or if this value is not defined, at C:\Program Files\Oracle\Inventory.
- /var/opt/oracle/oraInst.loc on Solaris, HP-UX and Tru64
- /etc/oraInst.loc on Linux and AIX
On Windows, the location of the oraInventory is defined by the value of the registry key HKEY_LOCAL_MACHINE|Software\Oracle\INST_LOC or if this value is not defined, at C:\Program Files\Oracle\Inventory.
In order to make better use of system resources, and to reduce the time it takes to complete certain maintenance tasks, AD utilities are designed to process jobs concurrently. This parallel processing makes use of managers, which direct the actions of worker processes. The manager assigns each worker a processing job and monitors its progress. When a worker completes a job, the manager assigns it another until all jobs are complete.
AD Administration and AutoPatch can be directed to distribute processing tasks across multiple remote machines in a multi-node system. This type of parallel processing operation is called Distributed AD. It further reduces the time to complete a maintenance task by utilizing the processing capabilities of all of the nodes in the system.
Because the AD workers create and update file system objects as well as database objects, Distributed AD can only be used on systems that are using a Shared Application Tier File System to ensure that files are maintained in a single, centralized location.
Using Distributed AD
- Start AutoPatch or AD Controller with Distributed AD worker options
On one of your shared application tier file system nodes, start your AutoPatch or AD Administration session with the following command line options:
localworkers= workers=
For example, to run an AutoPatch session with a total of eight workers (three workers on the local node and five workers on a remote node):
$ adpatch workers=8 localworkers=3
Shared APPL_TOP is a traditional multi-node installation requires the Applications file system on each node in the system.
In a Shared APPL_TOP installation, the APPL_TOP and the COMMON_TOP file systems are installed on a shared disk resource mounted to each node in the system. These nodes can be used to provide standard application tier services, such as Forms, Web, and Concurrent processing. Any changes made in the shared APPL_TOP file system are immediately visible on all nodes.
Note that each node continues to have a separate Applications techstack installation.
Find component Version in Apps 11i/R12/12i
Q. How to find Apps Version (11i/R12/12i).
A. Connect to database as user apps
SQL> select release_name from apps.fnd_product_groups;
Output like 12.0.4 or 11.5.10.2
A. Connect to database as user apps
SQL> select release_name from apps.fnd_product_groups;
Output like 12.0.4 or 11.5.10.2
Q. Web Server/Apache or Application Server in Apps 11i/R12
A. Log in as Application user, set environment variable and run below query $IAS_ORACLE_HOME/Apache/Apache/bin/httpd -versionOutput for 11i should be like
Server version: Oracle HTTP Server Powered by Apache/1.3.19 (Unix)
Server built: Jan 26 2005 11:06:44 (iAS 1.0.2.2.2 rollup 5)
Output for R12 should be like
Server version: Oracle-Application-Server-10g/10.1.3.0.0Oracle-HTTP-Server
Server built: Dec 4 2006 14:44:38
A. Log in as Application user, set environment variable and run below query $IAS_ORACLE_HOME/Apache/Apache/bin/httpd -versionOutput for 11i should be like
Server version: Oracle HTTP Server Powered by Apache/1.3.19 (Unix)
Server built: Jan 26 2005 11:06:44 (iAS 1.0.2.2.2 rollup 5)
Output for R12 should be like
Server version: Oracle-Application-Server-10g/10.1.3.0.0Oracle-HTTP-Server
Server built: Dec 4 2006 14:44:38
Q. Forms & Report version (aka developer 6i) in 11i
A. Log in as Application user, set environment variable and run below query
$ORACLE_HOME/bin/f60run | grep Version | grep Forms
output like
Forms 6.0 (Forms Runtime) Version 6.0.8.25.2 (Production)
Check fourth character in version 25 which means Forms 6i patchset 16 (25-9)
.
Q. Forms & Report version in R12/12i
A. Log in as Application user, set environment variable and run below query
$ORACLE_HOME/bin/rwrun | grep Release
Output should be like
Report Builder: Release 10.1.2.2.0You can safely ignore warnings.
A. Log in as Application user, set environment variable and run below query
$ORACLE_HOME/bin/f60run | grep Version | grep Forms
output like
Forms 6.0 (Forms Runtime) Version 6.0.8.25.2 (Production)
Check fourth character in version 25 which means Forms 6i patchset 16 (25-9)
.
Q. Forms & Report version in R12/12i
A. Log in as Application user, set environment variable and run below query
$ORACLE_HOME/bin/rwrun | grep Release
Output should be like
Report Builder: Release 10.1.2.2.0You can safely ignore warnings.
Q. Database Version in 11i/R12/12i
A. Go to database section below.
A. Go to database section below.
Q. Oracle Jinitiator in 11i/R12/12i
A. Log in as Application user, set environment variable and run below query
grep jinit_ver_comma $CONTEXT_FILE
A. Log in as Application user, set environment variable and run below query
grep jinit_ver_comma $CONTEXT_FILE
(Default is Java Plug-In for R12/12i )
Q. Oracle Java Plug-in in 11i/R12/12i
A. Log in as Application user, set environment variable and run below query
grep plugin $CONTEXT_FILE.
Q. Oracle Java Plug-in in 11i/R12/12i
A. Log in as Application user, set environment variable and run below query
grep plugin $CONTEXT_FILE.
Q. File Version on file systemadident Header
or
strings | grep Header
Here adident is AD Utility (Oracle Apps) and strings is Unix utility.
or
strings | grep Header
Here adident is AD Utility (Oracle Apps) and strings is Unix utility.
Q. Version of pld file*.pld are source code of *.pll which are inturn source of *.plx. *.pll is in $AU_TOP/resource and to find its version check
adident Header $AU_TOP/resource/.pll
IGSAU012.pll:
$Header IGSAU012.pld 115.1.115100.1 2004/04/01 05:40:18 appldev ship $
or
strings $AU_TOP/resource/.pll | grep -i header
FDRCSID(’$Header: IGSAU012.pld 115.1.115100.1 2004/04/01 05:40:18 appldev ship $’);
adident Header $AU_TOP/resource/.pll
IGSAU012.pll:
$Header IGSAU012.pld 115.1.115100.1 2004/04/01 05:40:18 appldev ship $
or
strings $AU_TOP/resource/.pll | grep -i header
FDRCSID(’$Header: IGSAU012.pld 115.1.115100.1 2004/04/01 05:40:18 appldev ship $’);
Q. OA Framework Version
A.http:// hostname.domainName:port/OA_HTML/OAInfo.jsp (Only for 11i)
A. Log in as Application user, set environment variable and run below query
adident Header $FND_TOP/html/OA.jsp
adident Header $OA_HTML/OA.jsp
output for both should look like
$Header OA.jsp 115.60 2006/03/31 00:47:28 atgops1 noship $
120.21 means OA Framework Version (coming soon..)
115.60 means OA Framework Version (coming soon..)
115.56 means OA Framework Version (coming soon..)
115.36 means OA Framework Version 5.7
115.27 means OA Framework Version 5.6E
115.26 means OA Framework Version 5.5.2E
A.http:// hostname.domainName:port/OA_HTML/OAInfo.jsp (Only for 11i)
A. Log in as Application user, set environment variable and run below query
adident Header $FND_TOP/html/OA.jsp
adident Header $OA_HTML/OA.jsp
output for both should look like
$Header OA.jsp 115.60 2006/03/31 00:47:28 atgops1 noship $
120.21 means OA Framework Version (coming soon..)
115.60 means OA Framework Version (coming soon..)
115.56 means OA Framework Version (coming soon..)
115.36 means OA Framework Version 5.7
115.27 means OA Framework Version 5.6E
115.26 means OA Framework Version 5.5.2E
Q. Discoverer Version for 11i (3i or 4i)
A. Log in as Application user, set environment variable and run below query
$ORACLE_HOME/bin/disc4ws | grep -i Version
A. Log in as Application user, set environment variable and run below query
$ORACLE_HOME/bin/disc4ws | grep -i Version
Q. Discoverer Version for 11i or R12 (10g AS)Check under Application Server Section as 10g AS Discoverer is on standalone
Q. Workflow Version with Apps
A. Connect to Database as apps user
SQL> select TEXT Version from WF_RESOURCES where NAME = ‘WF_VERSION’;
Output like 2.6.0 means workflow version 2.6.0
A. Connect to Database as apps user
SQL> select TEXT Version from WF_RESOURCES where NAME = ‘WF_VERSION’;
Output like 2.6.0 means workflow version 2.6.0
In Oracle Applications 11i & R12 (12i) all the configuration parameters are captured in two context files:
Application context file called the .xml contains the configuration information for the application tier & is located in $APPl_TOP/admin for each node of application tier.
Database context file called the .xml contains the configuration information for the database tier & is located in $ORACLE_HOME/appsutil/.
Details stored in the context file contains host names,domain name , directory structure, port numbers used ……
The AutoConfig feature of Oracle application manager(OAM) is used to update & manage context files.
Updating Context file
Suppose we want to update the active port from to 80 , for this we will edit the application context file as follows:
Step 1 :Start all services
$ $COMMON_TOP/admin/scripts//adstrtal.sh APPS/
Step 2 :log on to OAM & click site map.
Step 3:Click AutoConfig from the list of System Configuration features in the Administration tab.
Step 4 : Click the Edit Parameter button for the application tier context file to access the Context File Parameters page & then click the system tab.
Step 5 : Click the Focus icon (blue triangle) for oa_web_server. This expands oa_web_server and shows the web server related parameters.
Step 6:Update the Web Port (s_active_webport) parameter from < Original port number> to 80.
Step 2 :log on to OAM & click site map.
Step 3:Click AutoConfig from the list of System Configuration features in the Administration tab.
Step 4 : Click the Edit Parameter button for the application tier context file to access the Context File Parameters page & then click the system tab.
Step 5 : Click the Focus icon (blue triangle) for oa_web_server. This expands oa_web_server and shows the web server related parameters.
Step 6:Update the Web Port (s_active_webport) parameter from < Original port number> to 80.
Step 7 : Save it & answer the tab.Then logout of OAM. Read more »
March 12, 2010 Posted by Shreyas Desai | General | 11i, APPL_TOP, AutoConfig, COMMON_TOP, ORACLE_HOME, R12 | 1 Comment
FNDREVIVER, also recognized as reviver.sh, is used for momentary gliches in the system where the forms server and concurrent go down and forms is reconnected, but concurrent is not. The reviver revives the Internal Concurrent Manager (ICM) when it fails.
When ICM can no longer get a database connection, it kills itself and spawns the reviver. Reviver just loops every 30 seconds trying to see if it can logon to the database as apps user. When it does, it starts
up the ICM again.
up the ICM again.
If the failure is due to a brief network outage, or database issue, the managers are restarted avoiding the necessity of the client having to restart the managers manually.
Reviver is recovery mechanism that is delivered with ATG RUP4, patch 4676589, and is running in the background. In a Real Applications Cluster (RAC) environment, when the primary node goes down and ICM is set to migrate to the secondary node, the reviver parameter will be passed to the secondary node.
The easiest way to determine see if reviver.sh exists is by checking the $FND_TOP/bin directory
Where are the log files?
The following are referenced in this document:
{MMDDHHMM} : MM (Month) DD (Day) HH (Hour) MM (Minute)
{Timestamp} : {This may include Year, Month, Day, and Time}
{Base Install} : Location chosen during the RapidWiz configuration phase
The following are referenced in this document:
{MMDDHHMM} : MM (Month) DD (Day) HH (Hour) MM (Minute)
{Timestamp} : {This may include Year, Month, Day, and Time}
{Base Install} : Location chosen during the RapidWiz configuration phase
$CONTEXT_NAME : {SID}_{hostname}
RDBMS $ORACLE_HOME} : {Base Install}/db/tech_st/10.2.0
$IAS_ORACLE_HOME : {Base Install}/apps/tech_st/10.1.3
Tools $ORACLE_HOME : {Base Install}/apps/tech_st/10.1.2
$INST_TOP : {Base Install}/inst/apps/$CONTEXT_NAME
$APPL_TOP : {Base Install}/apps/apps_st/appl
RDBMS $ORACLE_HOME} : {Base Install}/db/tech_st/10.2.0
$IAS_ORACLE_HOME : {Base Install}/apps/tech_st/10.1.3
Tools $ORACLE_HOME : {Base Install}/apps/tech_st/10.1.2
$INST_TOP : {Base Install}/inst/apps/$CONTEXT_NAME
$APPL_TOP : {Base Install}/apps/apps_st/appl
Before the installation starts:
$TMP/{MMDDHHMM}/{MMDDHHMM}.log$TMP/{MMDDHHMM}/{hostname}_{SID}.xml
$TMP/{MMDDHHMM}/{hostname}_{SID}_apps.xml
$TMP/{MMDDHHMM}/{MMDDHHMM}.log$TMP/{MMDDHHMM}/{hostname}_{SID}.xml
$TMP/{MMDDHHMM}/{hostname}_{SID}_apps.xml
The Rapidwiz Configuration File is saved in 3 locations:-$TMP/{MMDDHHMM}/conf_{SID}.txt$INST_TOP/conf_{SID}.txt{RDBMS ORACLE_HOME}/appsutil/conf_{SID}.txt
March 12, 2010 Posted by Shreyas Desai | R12 | Installation, log files, R12 | 1 Comment
File
|
Oracle Applications 11i
|
Oracle Applications R12
|
Environment Source file
|
APPSORA.env
|
APPS<SID>_<hostname>.env
|
Context File (middle tier)
|
$APPL_TOP/admin/$TWO_TASK.xml
|
$INST_TOP/appl/admin/$TWO_TASK_<hostname>.xml
|
tnsnames.ora (OH)
|
$ORACLE_HOME/network/admin/<CONTEXT>
|
$INST_TOP/ora/10.1.2/network/admin
|
listener.ora
|
$ORACLE_HOME/network/admin/<CONTEXT>
|
$INST_TOP/ora/10.1.2/network/admin
|
appsweb.cfg
|
$OA_HTML/bin
|
$INST_TOP/ora/10.1.2/forms/server
|
tnsnames.ora (Apache)
|
$IAS_ORACLE_HOME/network/admin/<CONTEXT>
|
$INST_TOP/ora/10.1.3/network/admin
|
zone.properties
|
$IAS_ORACLE_HOME/Apache/Jserv/etc
|
$ORA_CONFIG_HOME/10.1.3/j2ee/oacore/application-deployments/oacore/oa_servlets/orion-web.xml and …/oacore/html/orion-web.xml
(Same file located in both directories) |
jsev.properties
|
$IAS_ORACLE_HOME/Apache/Jserv/etc
|
$INST_TOP/ora/10.1.3/opmn/conf/opmn.xml
|
httpd.conf
|
$IAS_ORACLE_HOME/Apache/Apache/conf
|
$ORA_CONFIG_HOME/10.1.3/Apache/Apache/conf
|
apps.conf
|
$IAS_ORACLE_HOME/Apache/Apache/conf
|
$ORA_CONFIG_HOME/10.1.3/Apache/Apache/conf
|
formservlet.ini
|
$IAS_ORACLE_HOME/Apache/Jserv/etc
|
$ORACLE_HOME/forms/server/default.env
|
topfile.txt
|
$APPL_TOP/admin
|
$APPL_CONFIG_HOME/admin
|
adovars.env
|
$APPL_TOP/admin
|
$APPL_CONFIG_HOME/admin
|
adjborg2.txt
|
$APPL_TOP/admin
|
$APPL_CONFIG_HOME/admin
|
SSL Certificates
|
$COMMON_TOP/admin/certs
|
$INST_TOP/certs
|
AD scripts logs
|
$COMMON_TOP/admin/log/<SID_hostname>
|
$LOG_HOME/appl/admin/log
|
Concurrent Request logs
|
$APPLCSF
|
$APPLCSF
|
Apache logs
|
$IAS_ORACLE_HOME/Apache/Apache/logs
|
$LOG_HOME/ora/10.1.3/Apache
|
Jserv logs
|
$IAS_ORACLE_HOME/Apache/Jserv/logs
|
$LOG_HOME/ora/10.1.3/j2ee
|
javacache.log
|
$COMMON_TOP/rgf/<SID_Hostname>
|
$LOG_HOME/appl/rgf
|
In Release 11i deployment of a (custom) JSP was done as follows:
- Copy the file (for example: custom.jsp) to the server in the $OA_HTML directory
- Request it in the browser like URL> http://<myhost.mydomain>:<port>/OA_HTML/custom.jsp
This makes that on the MT server:
- The custom.jsp was compiled
- Output files of the compilation _custom.class (and _custom.java) are saved under the _pages directory
- The custom.jsp page is shown in the browser
Performing the same steps in Release 12 environment just shows a blank screen and no compilation of the custom.jsp is done. The steps in this Note explain how the same behavior as in Release 11i can be achieved in Release 12.
In Release 12 the (automatic) compilation of JSP is disabled and on runtime only the pre-compiled JSP’s are picked up. Since this requires less checks to be done the performance is improved. Therefor is this the recommended setting for a Production environment where JSP’s will only be replaced occasionally.
In cases where development activities are done and JSP pages are changing often this default setting makes things more complicated. Each time a JSP is deployed a manual compilation using the ojspCompile.pl is needed and the OC4J running the oacore needs a restart to pick up the changes. This will also affect other people working on the same environment.
Unified APPL_TOP is different from separate APPL_TOP in Oracle Applications 11i. Unified APPL_TOP make more sense if you are using multi node Oracle Applications R12.
In Oracle Applications 11i , in multi node installation each APPL_TOP have its different name and files in each APPL_TOP will depend on type of Node (i.e. Forms Node will have fmx or forms related files where as APPL_TOP belonging to CM only node will have rdf or files required to run CM node)
Starting from R12, it will use Unified APPL_TOP which means all files required for all middle tier services are included in all nodes of Multi Node installation (irrespective of services running on that node)
What are few changes because of Unified APPL_TOP ?
– During Cloning of multi node Oracle Application install, only one copy (any one appl_top) of Application Node files need to copied to target instance.
– During Cloning of Multi Node to Single Node you don’t have to merge APPL_TOP’s in R12 as required in 11i .
–Services start/stop If you are using adstrtall.sh to start services on a node then it will start services which were configured to start during install on that node (You can still start a specific service even though it was not suppose to configure/start by calling startup script of that specific services).
To explain this better, lets assume you installed multi node R12 instance with Node 1 as Forms & Web Server where as Node 2 was installed with Concurrent Manager. Now on Node1 when you use adstrtall.sh script to start services as expected it will start Forms and Web services but unlike 11i, You can still start Concurrent Manager on Node1 by running adcmctl.sh
–FND_NODES From R12 all nodes will have Y against all services (For multi-node) in FND_NODES table.
– During Cloning of Multi Node to Single Node you don’t have to merge APPL_TOP’s in R12 as required in 11i .
–Services start/stop If you are using adstrtall.sh to start services on a node then it will start services which were configured to start during install on that node (You can still start a specific service even though it was not suppose to configure/start by calling startup script of that specific services).
To explain this better, lets assume you installed multi node R12 instance with Node 1 as Forms & Web Server where as Node 2 was installed with Concurrent Manager. Now on Node1 when you use adstrtall.sh script to start services as expected it will start Forms and Web services but unlike 11i, You can still start Concurrent Manager on Node1 by running adcmctl.sh
–FND_NODES From R12 all nodes will have Y against all services (For multi-node) in FND_NODES table.
Log files are useful in troubleshooting issues in Oracle Applications. Here is the list of Log file location in Oracle Applications for Startup/Shutdown, Cloning, Patching, DB & Apps Listener and various components in Apps R12/12i:
A. Startup/Shutdown Log files for Application Tier in R12
Instance Top is new TOP added in R12
–Startup/Shutdown error message text files like adapcctl.txt, adcmctl.txt…
$INST_TOP/apps/$CONTEXT_NAME/logs/appl/admin/log
–Startup/Shutdown error message related to tech stack (10.1.2, 10.1.3 forms/reports/web)
$INST_TOP/apps/$CONTEXT_NAME/logs/ora/ (10.1.2 & 10.1.3)
$INST_TOP/apps/$CONTEXT_NAME/logs/ora/10.1.3/Apache/error_log[timestamp]
$INST_TOP/apps/$CONTEXT_NAME/logs/ora/10.1.3/opmn/ (OC4J~…, oa*, opmn.log)
$INST_TOP/apps/$CONTEXT_NAME/logs/ora/10.1.2/network/ (listener log)
$INST_TOP/apps/$CONTEXT_NAME/logs/appl/conc/log (CM log files)
B. Log files related to cloning in R12
Preclone log files in source instance
Database Tier – $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/(StageDBTier_MMDDHHMM.log)
Application Tier -
$INST_TOP/apps/$CONTEXT_NAME/admin/log/(StageAppsTier_MMDDHHMM.log)
Clone log files in target instance
Database Tier – $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDBTier_.log
Apps Tier – $INST_TOP/apps/$CONTEXT_NAME/admin/log/ApplyAppsTier_.log
If your clone on DB Tier fails while running txkConfigDBOcm.pl (Check metalink note – 415020.1)
During clone step on DB Tier it prompts for “Target System base directory for source homes” and during this you have to give like /base_install_dir like ../../r12 and not oracle home like ../../r12/db/tech_st_10.2.0
C. Patching related log files in R12
i) Application Tier adpatch log – $APPL_TOP/admin/$SID/log/
ii) Developer (Developer/Forms & Reports 10.1.2) Patch – $ORACLE_HOME/.patch_storage
iii) Web Server (Apache) patch – $IAS_ORACLE_HOME/.patch_storage
iv) Database Tier opatch log – $ORACLE_HOME/.patch_storage
D. Autoconfig related log files in R12
i) Database Tier Autoconfig log :
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/MMDDHHMM/adconfig.log
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/MMDDHHMM/NetServiceHandler.log
ii) Application Tier Autoconfig log : $INST_TOP/apps/$CONTEXT_NAME/admin/log/$MMDDHHMM/adconfig.log
Autoconfig context file location in R12 – $INST_TOP/apps/$CONTEXT_NAME/appl/admin/$CONTEXT_NAME.xml
During the form generation process, adadmin reads a file named <prod>file.drv to build a list of objects to generate.
For example if you are looking at the AZ module forms, there will be a file called azfile.drv. This file is located in $PROD_TOP/admin/driver.
In this example this is $AZ_TOP/admin/driver.
Q: Which Concurrent Managers (CCMs) are supported by the Sysadmin team?
- Internal Concurrent Manager (ICM)
- Standard Manager
- Conflict Resolution Manager (CRM)
The setup of product-specific managers related issues should
be directed to the associated product group, i.e. the Inventory manager
Q: Where do the concurrent request output and log files reside?
A: $APPLCSF/out or $Product_Top/out for output files
$APPLCSF/log or $Product_Top/log for log files
Q: Where are temporary files located?
A: Temporary files reside in:
$APPLPTMP$APPLTMP
$REPORTS25_TMP (Release 11.0)
$REPORTS60_TMP (Release 11.5)
Concurrent Manager as name suggest is Manager, which manages your concurrent requests in Oracle Apps 11i. You can assign single request or batch job & let concurrent manager manage these request.
The Master Concurrent Managers
There is a lot of talk about “the” concurrent manager in Oracle Applications. Actually, there are many Concurrent Managers, each governing flow within each Oracle Apps areas. In addition there are “super” Concurrent Managers whose job is to govern the behavior of the slave Concurrent Managers. The Oracle e-Business suite has three important master Concurrent Managers:
- Internal Concurrent Manager — The master manager is called the Internal Concurrent Manager (ICM) because it controls the behavior of all of the other managers, and because the ICM is the boss, it must be running before any other managers can be activated. The main functions of the ICM are to start up and shutdown the individual concurrent managers, and reset the other managers after one them has a failure.
- Standard Manager — Another important master Concurrent Manager is called the Standard Manager (SM). The SM functions to run any reports and batch jobs that have not been defined to run in any specific product manager. Examples of specific concurrent managers include the Inventory Manager, CRP Inquiry Manager, and the Receivables Tax Manager.
- Conflict Resolution Manager — The Conflict Resolution Manager (CRM) functions to check concurrent program definitions for incompatibility rules.
However, the ICM can be configured to take over the CRM’s job to resolve incompatibilities.
How to Start/Stop Concurrent Manager – In Oracle Applications 11i as you might already be aware that all startup shutdown scripts in 11i(11.5.10) are in $OAD_TOP/admin/script/$CONTEXT_NAME where $OAD_TOP is also called as $COMMON_TOP and $CONTEXT_NAME is your SID_hostname, adcmctl.sh where ad (In my view) is application dba, cm is concurrent manager & ctl means control. When you run adcmctl.sh it records execution of this command in text file with name adcmctl.txt at directory $COMMON_TOP/admin/log/$CONTEXT_NAME. adcmctl.sh called another script startmgr which in turn calls batchmgr in $FND_TOP/bin and this is actual file which fire up Internal Concurrent Manager Process. Read more »
1. Keep all services running.
2. Login via the OS level by way of the applmgr user.
3. Run your environment scripts
a. cd $APPL_TOP
b. run APPSORA.env
c. the above should also run _.env, but you can verify by running it.
d. cd admin
e. run adovars.env
4. cd $FND_TOP/bin
5. Run FNDCPASS to change the SYSADMIN password (IMPORTANT: Change ONLY the SYSADMIN password)
FNDCPASS apps/apps 0 Y system/manager USER SYSADMIN
6. Restart the Apache, Forms, Reports, 8.0.6 listener and concurrent manager services.
7. To test, login into the applications as the SYSADMIN user and the new password.
8. Verify that a concurrent program such as Active Users runs.
2. Login via the OS level by way of the applmgr user.
3. Run your environment scripts
a. cd $APPL_TOP
b. run APPSORA.env
c. the above should also run _.env, but you can verify by running it.
d. cd admin
e. run adovars.env
4. cd $FND_TOP/bin
5. Run FNDCPASS to change the SYSADMIN password (IMPORTANT: Change ONLY the SYSADMIN password)
FNDCPASS apps/apps 0 Y system/manager USER SYSADMIN
6. Restart the Apache, Forms, Reports, 8.0.6 listener and concurrent manager services.
7. To test, login into the applications as the SYSADMIN user and the new password.
8. Verify that a concurrent program such as Active Users runs.
March 12, 2010 Posted by Shreyas Desai | Sysadmin | 11.5.10.2, 11i, APPL_TOP, How To Change The Password, Password, Sysadmin, user | Leave a Comment
Debugging tool for HTTP, OC4J and OPMN in E-Business Suite R12
How To Enable and Collect Debug for HTTP, OC4J and OPMN
Shutdown the http server, oc4j and opmn services
adapcctl.sh stop
adoacorectl.sh stop
adformsctl.sh stop
adoafmctl.sh stop
adopmnctl.sh stop
adoacorectl.sh stop
adformsctl.sh stop
adoafmctl.sh stop
adopmnctl.sh stop
Enable http ODL logging
———————–
$ORA_CONFIG_HOME/10.1.3/Apache/Apache/conf/httpd.conf
OraLogMode oracleOraLogSeverity TRACE:32OraLogDir $LOG_HOME/ora/10.1.3/Apache/oracle
———————–
$ORA_CONFIG_HOME/10.1.3/Apache/Apache/conf/httpd.conf
OraLogMode oracleOraLogSeverity TRACE:32OraLogDir $LOG_HOME/ora/10.1.3/Apache/oracle
Please use the full path to $LOG_HOME e.g. OraLogDir /u01/inst/apps/JCB_atg/logs/ora/10.1.3/Apache/oracle
mkdir $LOG_HOME/ora/10.1.3/Apache/oracle
