How to apply a Patch in Apps

Patching is the most basic thing that an Oracle Apps Dba is expected to know.A patch is applied either to fix a bug or to add some new functionality.
Here are the steps for patching in Apps 11i
1 First check that the patch is already not applied.
select * from ad_bugs where bug_number='patchnumber';
Now if the patch is not applied then go through the read me of the patch on Metalink. Check for pre-reqs and download the patch.
1 Stop the apps services
./adstpall.sh apps/password
2 Bounce the database(This is not mandatory but it kills any hanging process)
./addbctl.sh stop immediate
./addlnctl.sh stop listnername
./addlnctl.sh start listnername
./addbctl.sh start
3 Put the system in Maintenance mode
Run adadmin--Goto step 5-Change Maintenance mode-step 1 Enable Maintenance mode
4 Goto the patch directory where you downloaded the patch.Unzip the patch as applmgr user(application owner).It will create a directory with the patch number.
5 Goto the directory with the patch number and run
adpatch
It will ask for patch log file,apps,system password,driver name(c,d,g,u),number of workers.
6 go through the patch log file and check that there is no error
7 Disable maintenance mode
Run adadmin--Goto step 5-Change Maintenance mode-step 2 Dis-able Maintenance mode
8 Bounce the database again
9 Start the apps services
./adstartal.sh apps/password

Custom objects in Apps

Creating custom object causes major confusion as we need to know whether the object should be create in custom schema or apps schema. The following needs to be followed for this->
All the custom table, index and sequence should be created in custom schema.
grants should be given on that object from custom schema to apps schema
synonym should be created for those object in apps schema
All the other database objects->views,packages,etc should be created in apps schema.

Bouncing the Apps & Db services

Stop the services
If you have implemented SSL then Stop Apache from "root" otherwise skip this step->
./adapcctl.sh stop

then after waiting for a minute stop all the services with "applmgr" user
./adstpall.sh apps/password


then stop the database with "oracle" user
./addbctl.sh stop immediate

and finally stop the db listener with "oracle" user
./addlnctl.sh stop listenername

Start the services
First start the db listener with "oracle" user
./addlnctl.sh start listenername

then start the database
./addbctl.sh start

Next start the application services
Start Apache from "root" is you have implemented SSL otherwise skip this step
./adapcctl.sh start

Next start the remaining application services after waiting for about a minute
./adstrtal.sh apps/password

Purging in Oracle Apps

Purging is very important activity in Oracle Apps. As a dba one needs to purge the obsolete data so that only usable data is there in system,backups and restore are faster,space is recovered and finally it makes the system faster as well. Following are some of the concurrent requests which should be scheduled for purging-
Purge Concurrent request and/or manager data--Here we specify mode=x so that it purges all the concurrent request log files,concurrent request output files and manager data which are more than 'x' days old i.e. we just keep 'x' days data.

Purge Obsolete Workflow Runtime data-Here we specify type of workflow -'Temperorary/Permanent, "Age"-which determines how old notification one wants to keep. We can also specify the 'Item Type' and 'Item key' to restrict it to purge just a particular type of workflow notifications.Note that only the closed notifications are purged.

Purge Signon Audit Data-Here we need to specify the timestamp before which the Audit data will be deleted

These are just some of the requests.There are many more!

Delete Apache log files

Stop the Apache.
delete all the log files from
$IAS_ORACLE_HOME/Apache/Apache/logs
$IAS_ORACLE_HOME/Apache/Jserv/logs/jvm
$IAS_ORACLE_HOME/Apache/Jserv/logs
Start the Apache

Concurrent Request for tablespace issue

This summary is not available. Please click here to view the post.