You are on page 1of 4

cd $IAS_ORACLE_HOME/Apache/Apache/bin

httpd -v

perl adbldxml.pl tier=apps appsuser=<APPSuser> appspasswd=<APPSpwd>


for generation of xml file

Advantages and importance of maintenance mode


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

There is a separate logon page for Restricted Mode access while the system is in
Maintenance Mode.
Restricted Mode allows administrators access to specific privileged functionality
in OAM,
for example to view the timing report that shows the progress of a patching
session.
For more Information on Restricted Mode Access please consult Metalink Note:
364236.1
or the OAM Online Help (OAM->Patches and Utilities -> Managing Downtime Schedules
-> Restricted Mode)

1.Minimizes the downtime


2.When the System has been scheduled for 'Downtime',
Apache should be re-started on Restricted Mode by using the Script (adaprstctl.sh).

Site Map --> Maintenance --> Manage Downtime Schedules

When adsetmmd.sql runs, it sets the Profile Option 'Applications Maintenance Mode'
(APPS_MAINTENANCE_MODE) to 'MAINT' to Enable 'Maintenance Mode' and to 'NORMAL' to
Disable it.

2. Advantages

There are several practical points relating to the use of Maintenance Mode:

You can toggle Maintenance Mode between Enabled and Disabled using the new Change
Maintenance Mode menu in AD Administration, or the equivalent function in Oracle
Applications Manager.

Although you can run AutoPatch with Maintenance Mode disabled, there will be a
significant degradation in performance.

There is a separate logon page for Restricted Mode access while the system is in
Maintenance Mode. Restricted Mode allows administrators access to specific
privileged functionality in OAM, for example to view the timing report that shows
the progress of a patching session.
For more Information on Restricted Mode Access please consult Metalink Note:
364236.1
or the OAM Online Help (OAM->Patches and Utilities -> Managing Downtime Schedules
-> Restricted Mode)
Note: Maintenance Mode is only needed for AutoPatch Sessions. Other AD utilities
do not require Maintenance Mode to be enabled. Maintenance Mode must be 'Enabled'
before running AutoPatch and 'Disabled' after the patch application was completed.

When Maintenance Mode is disabled, you can still run Autopatch by using
options=hotpatch on the command line, if necessary. However, doing so can cause a
significant degradation of performance.

IMP: The concurrent processing can run and only the apache and forms services can
be taken down and restarted when main mode is disabled

Step by Step Process

1. Schedule the 'System Downtime' from OAM

OAM: Site Map --> Maintenance --> Manage Downtime Schedules

At the moment of the downtime, do the following:

2. Shutdown Apache (on Normal Mode):

adapcctl.sh stop
or
adstpall.sh <apps_user>/<apps_pwd>

3. Enable 'Maintenance Mode' from adadmin

Important points:

Every patch should have c driver.

adadmin: Options 5, 1

4. Start Apache (on Restricted Mode)

adaprstctl.sh start

5. Apply the Patch with adpatch

6. Stop Apache (on Restricted Mode)

adaprstctl.sh stop
7. Disable 'Maintenance Mode' from adadmin

adadmin: Options 5, 2

8. Start Apache (on Normal Mode):

adapcctl.sh start
or
adstrtal.sh <apps_user>/<apps_pwd>

with hotpatch option.

$AU_TOP/java is the location for apps.zip file.


In java patches the class files are updated.

jcopy is used to copy the java files.

A.Copy driver, cXXXXXX.drv

The copy driver is the first driver, which must be run using adpatch.
This driver will do the following functions.

a)copy the files from the patch to the appropriate directory

b)relink executables

c)regenerate jar files

<command> <product> <subdirectory> <file> <other arguments�>

start and stop scripts use env file to get the node information and the necessary
details.

krishprasad1@yahoo.com

Steps Used for Implementing Parallel Concurrent Processing:


================================================

1. On Node 1, log in as applmgr (owner of the application files) Unix user and
Source all your environment files to fully set your environment.

At the prompt type:


$ id

This should return output that looks similar to:


uid=1003(applmgr) gid=102(ad)

You need this information when you are creating the applmgr user on Node 2.
If the applmgr user on Node 2 does not have the same exact uid and gid
Then this will cause errors later when one of the nodes tries to login and
Start processes on the other node.

9885693291