Ref : User Guide Oracle® E-Business Suite Patching Procedures Release 12.1 Part No. E12148-04
Checking the server details :
**********************
select NODE_NAME, SUPPORT_CP, SUPPORT_FORMS, SUPPORT_WEB, SUPPORT_ADMIN from fnd_nodes;
Running a Unified Driver on Multiple Nodes:
**********************************
Requirement: How do I run a unified driver patch on a multi-node system?
Apply the unified driver to all APPL_TOPs. AutoPatch determines which actions in the
unified driver are required for the current APPL_TOP.
To apply a unified driver on multiple nodes
1. Complete Steps 1 through to 9 in Applying a Patch Interactively, page 5-7.
2. Apply the unified driver on the node where the administration server is located.
3. Apply the unified driver on the node where the concurrent processing server is
located.
4. Start the concurrent managers.
5. Apply the unified driver on the remaining nodes in the application tier.
6. Disable Maintenance mode.
Use the Change Maintenance Mode menu of AD Administration to disable
Maintenance mode. See: Changing Maintenance Mode, Oracle E-Business Suite
Maintenance Utilities.
7. Start other services and restart the Web services, if necessary.
To apply a patch in common
**********************
This procedure describes the typical steps for applying a patch. Subsequent procedures
describe command line options that change the default behavior of AutoPatch.
1. Log in as applmgr (Applications file system owner) and set the environment:
UNIX:
The environment file is typically APPS<CONTEXT_NAME>.env, and is located
under the APPL_TOP. From a Bourne, Korn, or Bash shell, enter the following:5-8 Oracle E-Business Suite Patching Procedures
$ . APPS<CONTEXT_NAME>.env
Windows:
Run %APPL_TOP%\envshell.cmd using either Windows Explorer or the Run
command from the Start menu. This creates a Command Prompt window that
contains the required environment settings for Oracle E-Business Suite. Run all
subsequent commands in this Command Prompt window.
If you are running on a Windows platform, ensure that all necessary tools are
installed properly. In addition, all %JAVA_TOP% and %JAVA_TOP%\loadjava.zip
files are included in the set CLASSPATH statement
of %APPL_TOP%\admin\adovars.cmd.
2. Create a patch top directory, if it does not already exist. Download the patch into a
staging directory and unzip the patch into the patch top directory. Do not use the
patch subdirectory under the <PROD>_TOP directories as your patch top directory.
3. Change directory to the patch top directory where you unzipped the patch.
4. Review the readme file in the patch top directory.
Review the readme file (README.txt or README.html). It contains an abstract of
the patch. If the patch contains manual steps, the readme file will contain
instructions for running Oracle Patch Application Assistant (PAA) to generate
customized manual steps for your system.
5. If indicated in the patch readme, run PAA to generate customized instructions for
applying the patch. You will need to provide the location of your patch top
directory and the applmgr password.
$ admsi.pl
Perform the manual steps contained in the customized instructions generated by
PAA. Additional steps may also be detailed depending on the patch, the state of
your system, and the products you have installed.
Perform the following steps, in addition to the steps detailed in the customized
instructions, to apply the patch.
6. Shut down services.
Run the adstpall.sh script to shut down the services appropriate to your system.
You will need to provide the applmgr user name and password.
Note: For more information on patching a multi-node system, see:
Applying Patches to a Multi-Node System,
UNIX:
$ adstpall.shPatching Procedures
Windows:
C:\> adstpall.cmd
Note: You must complete all tasks associated with applying a patch
before you access Oracle E-Business Suite.
7. Enable Maintenance Mode.
Use the Change Maintenance Mode menu (Option 1) of AD Administration to
enable Maintenance mode. See: Enable Maintenance Mode, page 2-3.
8. Start AutoPatch.
Use the adpatch command to start AutoPatch from the patch top directory (the
directory where you downloaded the patch files). You can customize the way
AutoPatch runs by adding arguments to the command line. See Command Line
Arguments, page 2-12.
9. Respond to the AutoPatch prompts. You are prompted for the following
information required to apply the patch:
• Name of the APPL_TOP where you want to apply the patch
• Log file name: Select a name for the log file, for example, u<patchnum>.log
• Email where you want to receive notifications
• Batch size (default is 1000)
• Database name
• Patch top directory where you unzipped the patch
• Driver file name: Provide the name of the driver file located in the patch top
directory, for example, u<patchnum>.drv
10. Apply the driver.
At the AutoPatch prompt for the driver name, specify the name of the driver.
11. Review customizations.
Customized files are registered on the OAM Register Flagged Files page. If
AutoPatch displays a message indicating that previously registered, customized
files will be replaced by the patch, review those files in the Register Flagged Files
page to determine if the customizations need to be reregistered or removed. See:
Register Flagged Files, page 1-8.5-10 Oracle E-Business Suite Patching Procedures
12. After AutoPatch exits, review the log files.
Review the AutoPatch log file after the application of each driver file for warnings
or errors. The log file (named u<patchnum>.log in step 9 is located in
<APPL_TOP>/admin/<SID>/log. In addition, some patch tasks may create separate
log files in the same directory. If the patching process used multiple workers, each
worker creates its own log file. You can also use the View Log Files feature in
Timing Reports to view the files. See: Log Files, page 2-3 and View Log Files, page
4-28.
13. Preallocate space for packages, functions, and sequences (optional).
If AutoPatch has modified Oracle E-Business Suite database objects, you may want
to run ADXGNPIN.sql and ADXGNPNS.sql to allocate space ("pin") for new
packages and sequences in the Oracle System Global Area. These scripts are located
in AD_TOP/sql.
See: Pre-allocating Space for Packages and Functions, Oracle E-Business Suite
Maintenance Procedures.
14. Disable Maintenance Mode.
Use the Change Maintenance Mode menu (Option 2) of AD Administration to
disable Maintenance mode.
15. Restart server processes.
After verifying that the patch was applied successfully, start all services. Once the
services are running, you can allow users to access the system again.
UNIX:
$ adstrtal.sh
Windows:
C:\> adstrtal.cmd
See: Stopping or Starting Application Tier Services, Oracle E-Business Suite
Maintenance Procedures.
16. Delete or archive AutoPatch backup files (optional).
After you have tested the patched system, you can delete the backup copies of files
from the patch top directories to recover disk space, as necessary. Oracle
recommends archiving these files if you have space available.
Checking the server details :
**********************
select NODE_NAME, SUPPORT_CP, SUPPORT_FORMS, SUPPORT_WEB, SUPPORT_ADMIN from fnd_nodes;
Running a Unified Driver on Multiple Nodes:
**********************************
Requirement: How do I run a unified driver patch on a multi-node system?
Apply the unified driver to all APPL_TOPs. AutoPatch determines which actions in the
unified driver are required for the current APPL_TOP.
To apply a unified driver on multiple nodes
1. Complete Steps 1 through to 9 in Applying a Patch Interactively, page 5-7.
2. Apply the unified driver on the node where the administration server is located.
3. Apply the unified driver on the node where the concurrent processing server is
located.
4. Start the concurrent managers.
5. Apply the unified driver on the remaining nodes in the application tier.
6. Disable Maintenance mode.
Use the Change Maintenance Mode menu of AD Administration to disable
Maintenance mode. See: Changing Maintenance Mode, Oracle E-Business Suite
Maintenance Utilities.
7. Start other services and restart the Web services, if necessary.
To apply a patch in common
**********************
This procedure describes the typical steps for applying a patch. Subsequent procedures
describe command line options that change the default behavior of AutoPatch.
1. Log in as applmgr (Applications file system owner) and set the environment:
UNIX:
The environment file is typically APPS<CONTEXT_NAME>.env, and is located
under the APPL_TOP. From a Bourne, Korn, or Bash shell, enter the following:5-8 Oracle E-Business Suite Patching Procedures
$ . APPS<CONTEXT_NAME>.env
Windows:
Run %APPL_TOP%\envshell.cmd using either Windows Explorer or the Run
command from the Start menu. This creates a Command Prompt window that
contains the required environment settings for Oracle E-Business Suite. Run all
subsequent commands in this Command Prompt window.
If you are running on a Windows platform, ensure that all necessary tools are
installed properly. In addition, all %JAVA_TOP% and %JAVA_TOP%\loadjava.zip
files are included in the set CLASSPATH statement
of %APPL_TOP%\admin\adovars.cmd.
2. Create a patch top directory, if it does not already exist. Download the patch into a
staging directory and unzip the patch into the patch top directory. Do not use the
patch subdirectory under the <PROD>_TOP directories as your patch top directory.
3. Change directory to the patch top directory where you unzipped the patch.
4. Review the readme file in the patch top directory.
Review the readme file (README.txt or README.html). It contains an abstract of
the patch. If the patch contains manual steps, the readme file will contain
instructions for running Oracle Patch Application Assistant (PAA) to generate
customized manual steps for your system.
5. If indicated in the patch readme, run PAA to generate customized instructions for
applying the patch. You will need to provide the location of your patch top
directory and the applmgr password.
$ admsi.pl
Perform the manual steps contained in the customized instructions generated by
PAA. Additional steps may also be detailed depending on the patch, the state of
your system, and the products you have installed.
Perform the following steps, in addition to the steps detailed in the customized
instructions, to apply the patch.
6. Shut down services.
Run the adstpall.sh script to shut down the services appropriate to your system.
You will need to provide the applmgr user name and password.
Note: For more information on patching a multi-node system, see:
Applying Patches to a Multi-Node System,
UNIX:
$ adstpall.shPatching Procedures
Windows:
C:\> adstpall.cmd
Note: You must complete all tasks associated with applying a patch
before you access Oracle E-Business Suite.
7. Enable Maintenance Mode.
Use the Change Maintenance Mode menu (Option 1) of AD Administration to
enable Maintenance mode. See: Enable Maintenance Mode, page 2-3.
8. Start AutoPatch.
Use the adpatch command to start AutoPatch from the patch top directory (the
directory where you downloaded the patch files). You can customize the way
AutoPatch runs by adding arguments to the command line. See Command Line
Arguments, page 2-12.
9. Respond to the AutoPatch prompts. You are prompted for the following
information required to apply the patch:
• Name of the APPL_TOP where you want to apply the patch
• Log file name: Select a name for the log file, for example, u<patchnum>.log
• Email where you want to receive notifications
• Batch size (default is 1000)
• Database name
• Patch top directory where you unzipped the patch
• Driver file name: Provide the name of the driver file located in the patch top
directory, for example, u<patchnum>.drv
10. Apply the driver.
At the AutoPatch prompt for the driver name, specify the name of the driver.
11. Review customizations.
Customized files are registered on the OAM Register Flagged Files page. If
AutoPatch displays a message indicating that previously registered, customized
files will be replaced by the patch, review those files in the Register Flagged Files
page to determine if the customizations need to be reregistered or removed. See:
Register Flagged Files, page 1-8.5-10 Oracle E-Business Suite Patching Procedures
12. After AutoPatch exits, review the log files.
Review the AutoPatch log file after the application of each driver file for warnings
or errors. The log file (named u<patchnum>.log in step 9 is located in
<APPL_TOP>/admin/<SID>/log. In addition, some patch tasks may create separate
log files in the same directory. If the patching process used multiple workers, each
worker creates its own log file. You can also use the View Log Files feature in
Timing Reports to view the files. See: Log Files, page 2-3 and View Log Files, page
4-28.
13. Preallocate space for packages, functions, and sequences (optional).
If AutoPatch has modified Oracle E-Business Suite database objects, you may want
to run ADXGNPIN.sql and ADXGNPNS.sql to allocate space ("pin") for new
packages and sequences in the Oracle System Global Area. These scripts are located
in AD_TOP/sql.
See: Pre-allocating Space for Packages and Functions, Oracle E-Business Suite
Maintenance Procedures.
14. Disable Maintenance Mode.
Use the Change Maintenance Mode menu (Option 2) of AD Administration to
disable Maintenance mode.
15. Restart server processes.
After verifying that the patch was applied successfully, start all services. Once the
services are running, you can allow users to access the system again.
UNIX:
$ adstrtal.sh
Windows:
C:\> adstrtal.cmd
See: Stopping or Starting Application Tier Services, Oracle E-Business Suite
Maintenance Procedures.
16. Delete or archive AutoPatch backup files (optional).
After you have tested the patched system, you can delete the backup copies of files
from the patch top directories to recover disk space, as necessary. Oracle
recommends archiving these files if you have space available.
No comments:
Post a Comment