Oracle application 11i upgrade to R12.0.4 - coming soon

I will start writing this post soon which includes Oracle Application 11.5.9CU2 upgrade to Oracle application R12.0.4. This upgrade includes upgrade from Portal 3.0.9 , Portal Login server/SSL to Portal 10g/SSO/SSL. Also database upgrade from 9.2.0.7 to 10.2.0.4 patchset. Also I am going to discuss about various paths to upgrade to R12..

Step by Step Information on R12 - How to Validate APPS Schema

In day to day activity DBA's encounter issues related to invalid objects. Common solution to the problem is running adadmin utility and utlrp script. In this post we are going to discuss invalid APPS schema not objects.

Now the question must be in your mind in what situations you really needs to validate the APPS Schema.

Here we go....

If face any problem with AD_DDL package at runtime

When patch is applied. You can run this only once even you apply more then one patches at a time.

If you upgraded Oracle applications or applied Maintenance pack

After migration using export/import

After Custom development of APPS Schema

Methods to validate APPS Schema

On Unix:
1. Run system/passowrd @$AD_TOP/admin/sql/advrfapp.sql
2. Using adadmin utility and opt for "1. Validate APPS Schema" under "Maintain Applications Database Entities".

Steps to Validate APPS Schema


1.Run adadmin utility. Select the option "Maintain Applications Database Entities" from main menu of AD Administration.

2.Select "Validate APPS Schema" from sub-menu of "Maintain Applications Database Entities".

3. Now review the output file located at $APPL_TOP/admin/SID/out. The report name will be .lst. Look for any missing or invalid pacakges , synonyms or invalid objects in APPS schema. Also check and verify for table or sequences in APPS and base schema. Follow the instruction in the file to resolve any issues.

Hope this helps.

Step by Step Information on Oracle Applications R12 Control Scripts

In this post you will come to know about Oracle Applications Control Scripts. It is very important for an APPS DBA to know the location and its usage while handling APPS DBA duties.

The application Tier server process control scripts are used to start and stop server processes on the applications tier like adcmctl.sh (Concurrent manager start/stop control script) and adapcctl.sh (HTTP Server start/stop control script).

The following question can be arise in your mind regarding control scripts on Application Tier.

Now you will think where this control scripts are located in Application Tier

How these control scripts are created.

Is it possible to recreate these control scripts.

Here you go...The answer to the above queries are...

Control scripts are located in the $ADMIN_SCRIPTS_HOME (i.e, $INST_TOP/admin/scripts) directory. It is created by Rapid Install during the installation and you can recreate using AutoConfig (i.e,adautocfg.sh control script) as and when required.

The syntax of the control scripts is [stop or start]

$./adalnctl.sh stop (To stop the Apps Listener)
$./adalnctl.sh start (To start the Apps Listener)

You can use other Application Tier server process control scripts for all server processes to stop and start at the same time.

$./adstrtal.sh (Apps username/password)
$./adstpall.sh (Apps username/password)

To stop or start Forms server in socket mode.

$./adfrmsrvctl.sh

To stop or start Forms OC4J instance in servlet mode.

$./adfrmctl.sh

To stop or start Application Listener.

$./adalnctl.sh

To stop or start concurrent managers.
(This control script required the APPS username and password).

$./adcmctl.sh

To stop or start the HTTP server.

$./adapcctl.sh

Hope you like this post. Please let me know what Topic you would like to see on my blog. Based on request I will start including other stuff too. I am taking my family time to write these articles so I will be on / off from the blogs. You inputs are highly appreciated to improve my blog.