|
Auto Patch made easy
For Minimized downtime and optimized performance for an auto patch session, Use Maintenance mode with Oracle E-Business suite Release 11.5.10 .
Maintenance Mode is a new mode of operation introduced with Release 11.5.10, in which the Oracle Applications system is made accessible only for patching activities. The users are not allowed to login any responsibility. This provides optimal performance for auto patch sessions, and minimizes downtime .
You can enable or disable the maintenance mode by using either Ad utility (adadmin) or OAM(oracle applications Manager)
Steps to enable and disable maintenance mode (adadmin)
Run the consolidated contextname.env file which is available in $APPL_TOP/ usually
file name is like APPS.env Context name= SID_
start adadmin answer the subsequent prompts you can get the main menu of the adadmin utility select 5) change maintenance mode afterthat you will get another menu select 1)enable maintenance mode
When you Enable or Disable 'Maintenance Mode',adadmin will execute the script:$AD_TOP/patch/115/sql/ adsetmmd.sql, sending the parameter 'ENABLE' or 'DISABLE' :
You can also enable the maintenance mode by calling the scripts in sql prompt sqlplus /@adsetmmd.sql ENABLE | DISABLE
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.
After the auto patch process, you have to disable the maintenance mode by using adadmin
How do we know that maintenance mode is enabled ?
You can find out whether maintenance mode is enabled or not by executing the simple query in
sqlplus apps/apps
SQL> select fnd_profile.value('APPS_MAINTENANCE_MODE') from dual;
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.
If you directly login through the forms when maintenance mode is enabled
http://FQDN:portno/dev60cgi/f60cgi
You will get the following error
- No valid navigations for this responsibility
Cause: The menu compilation has failed.
Cause: There is no valid menu defined for this responsibility.
Cause: There are no navigable forms associated with this responsibility.
Action: Contact your system administrator. Ensure that a valid menu,
containing navigable forms, is defined for the responsibility.
Ensure that the menu is correctly compiled.
If you login through the PHP page you may get this type of errors. On clicking the Responsibility from the PHP .
|