Professional Documents
Culture Documents
Users Guide
Release 3.6.1.2.0
June 2012
Oracle Change Management Application User's Guide, Release 3.6.1.2.0
The Programs (which include both the software and documentation) contain proprietary information; they
are provided under a license agreement containing restrictions on use and disclosure and are also protected
by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly,
or decompilation of the Programs, except to the extent required to obtain interoperability with other
independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in
the documentation, please report them to us in writing. This document is not warranted to be error-free.
Except as may be expressly permitted in your license agreement for these Programs, no part of these
Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any
purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on
behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data
delivered to U.S. Government customers are "commercial computer software" or "commercial technical data"
pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As
such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation
and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license
agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial
Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA
94065.
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently
dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup,
redundancy and other measures to ensure the safe use of such applications if the Programs are used for such
purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third
parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites.
You bear all risks associated with the use of such content. If you choose to purchase any products or services
from a third party, the relationship is directly between you and the third party. Oracle is not responsible for:
(a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the
third party, including delivery of products or services and warranty obligations related to purchased
products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from
dealing with any third party.
Contents
Preface ................................................................................................................................................................. v
Audience....................................................................................................................................................... v
Typographic Conventions.......................................................................................................................... v
Command Syntax ........................................................................................................................................ v
Documentation Accessibility ..................................................................................................................... vi
1 Prerequisites
iii
4 Initiating a Patching Run
4.1 Patch Type Overview ................................................................................................................. 4-1
4.2 Specify the RFC ID...................................................................................................................... 4-1
4.3 Change Target System Information ......................................................................................... 4-2
4.4 Specify Patch Options................................................................................................................. 4-4
4.4.1 Prerequisite Patches............................................................................................................. 4-5
4.4.2 Patching Procedure Options .............................................................................................. 4-5
4.4.3 AutoPatch Options (Application-Tier Only) ................................................................ 4-11
4.4.4 OPatch Options (Database-Tier Only) ........................................................................... 4-12
4.4.5 AD Administration Options (Application-Tier and CPU Patching Only)............... 4-12
4.4.6 HR Global Options .......................................................................................................... 4-13
4.4.7 Reviewing the Patch List Table....................................................................................... 4-13
4.5 Specifying Hosted Servers Password.................................................................................... 4-15
4.6 Review Patching Run Information ........................................................................................ 4-15
4.6.1 Reviewing the Patch Readme File .................................................................................. 4-15
4.6.2 Changing the Patch Application Order......................................................................... 4-16
4.6.3 Reapplying and Pausing a Previously Applied Patch ................................................ 4-16
4.6.4 Selecting Preinstall Mode ............................................................................................... 4-17
4.6.5 Deleting a Patch ................................................................................................................ 4-17
4.6.6 Recovering a Deleted Patch............................................................................................. 4-17
4.6.7 Specify Operating System Password ............................................................................. 4-17
4.6.8 Change, Cancel, or Submit a Patching Run Request ................................................... 4-18
B Troubleshooting
n Initializing the Enterprise Manager Command Line Interface Client Manually ............. B-1
5. Review Log Files ........................................................................................................................ B-2
5. Create XML Files from Runtime Parameters ......................................................................... B-3
iv
Preface
This guide provides instructions for configuring and using Oracle Enterprise Manager
and the Change Management Application to request patching and refresh runs.
Audience
This guide is intended for Oracle On Demand Operations engineers who maintain On
Demand customer systems.
Typographic Conventions
The following typographic conventions are used in this guide:
Convention Meaning
boldface Boldface type indicates graphical user interface elements associated
with an action, or terms defined in text or the glossary.
italic Italic type indicates book titles, emphasis, or placeholder variables for
which you supply particular values.
monospace Monospace type indicates commands within a paragraph, URLs, code
in examples, text that appears on the screen, or text that you enter.
UPPERCASE Uppercase case letters indicate Structured Query Language (SQL)
reserved words, initialization parameters, and environment variables.
<cr> Indicates a line break.
Command Syntax
UNIX and Linux command syntax appears in monospace font and assumes the use of
the Bourne shell. The "$" character at the beginning of UNIX or Linux command
examples should not be entered at the prompt. Because UNIX and Linux is
case-sensitive, conventions used in this document may differ from those used in other
Oracle documentation.
Convention Meaning
Backslash \ A backslash indicates a command that is too long to fit on a single line.
Enter the line as printed (with a backslash) or enter it as a single line
without a backslash:
dd if=/dev/rdsk/c0t1d0s6 of=/dev/rst0 bs=10b \
count=10000
v
Convention Meaning
Braces {} Braces indicate required items: DEFINE {macro1}
Brackets [] Brackets indicate optional items: cvtcrt termname [outfile]
Note that brackets have a different meaning when used in regular text.
ellipses.... Ellipses indicate an arbitrary number of similar items:
CHKVAL fieldname value1 value2 ... valueN
Italics Italic type indicates a variable. Substitute a value for the variable.
library_name
Vertical line A vertical line indicates a choice within braces or brackets:
SIZE filesize [K|M]
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation
accessible, with good usability, to the disabled community. To that end, our
documentation includes features that make information available to users of assistive
technology. This documentation is available in HTML format, and contains markup to
facilitate access by the disabled community. Accessibility standards will continue to
evolve over time, and Oracle is actively engaged with other market-leading
technology vendors to address technical obstacles so that our documentation can be
accessible to all of our customers. For more information, visit the Oracle Accessibility
Program Web site at
http://www.oracle.com/accessibility/
vi
1
Prerequisites
Ensure that you meet the following prerequisites before using this guide:
You have an Oracle Single Sign-On (SSO) account.
You have a basic understanding of Oracle Enterprise Manager Grid Control 10g
Release 4 (EM Grid Control 10g R4) concepts, including logging in to the console,
basic navigation, and accessing the online help. For information about these
concepts, see the Oracle Enterprise Manager Grid Control Installation and Basic
Configuration guide, available at the following URL:
http://www.oracle.com/technology/products/oem/deployments/b12012_
03.pdf
Prerequisites 1-1
maintenance mode, and AD Merge Patch. These concepts and utilities are
explained in the following documents:
Release 11i:
Oracle Applications Maintenance Procedures, Release 11i (11.5.10.2), available at
the following URL:
http://download.oracle.com/docs/cd/B25516_
18/current/acrobat/11iadproc.pdf
Release 12:
Oracle Applications Patching Procedures, Release 12, available at the following
URL:
http://download.oracle.com/docs/cd/B40089_09/current/acrobat/oa_
patching_r12.pdf
Prerequisites 1-3
1-4 Oracle Change Management Application User's Guide
2
Overview and Setup
Complete the steps in the following sections before using the CMA.
The Confirmation page appears, showing that the request has entered the
approval process.
Your manager receives an automated notification from APS and must then
approve the request.
You can monitor the request in the Recent Requests section of the APS Home
page. When the request has been approved, the status will change to Successfully
Processed.
Complete the steps in the following section to request a role.
Note: You will not be able to request a role until your user account
request is approved, and you will not be able to log in to the CMA
until your role request is approved.
Note: If Cloud Services CMA does not appear in the systems list,
you do not have a Cloud Services CMA account. Follow the
instructions in Requesting a Cloud Services CMA User Account to
create the account, then begin this procedure again.
5. Select the following privileges by moving them from the Available Privileges area
to the Selected Privileges area, then click Next Step:
Change Execution Engineer - This privilege provides access to CMA Patch,
Bounce, and PSFT Refresh on https://cmportal.oracle.com.
Change Execution Planner - This privilege provides access to CMA-PPA on
https://cmportal.oracle.com.
The Justification page appears.
6. On the Justification page, in the Justification field, enter a justification for the
CMA account. Include the group you work for and what you will be using the
CMA for, then click Submit Request.
The Confirmation page appears, showing that the request has entered the
approval process.
Your manager receives an automated notification from APS and must then
approve the request.
You can monitor the request in the Recent Requests section of the APS Home
page. When the request has been approved, the status will change to Successfully
Processed.
Note: Note: You will not be able to request a role until your user
account request is approved, and you will not be able to log in to the
CMA until your role request is approved.
7. Click the Test button on the row of each target for which you entered credentials to
test the login credentials.
Invalid OS Account
If you do not have a valid OS account, you will see the following error when your OS
credentials are validated during the Credentials step:
Error: Invalid Credentials Supplied. Invalid password supplied for user <username>
on Change Management Application Server (<CMA_server_name>). You will not be able
to submit the request until we validate your credentials.
Invalid EM Account
The EMCLI account is created based on the EM account. If you not have a valid EM
account, you will see the following error when attempting to (re)create the EMCLI
account during the Credentials step:
Invalid credential supplied for user <username> on Enterprise Manager Grid Control
(url:<EM_server_name>).You may click the Next button to continue with the
submission of this change execution request, and complete the emcli setup later;
but if you do not complete the emcli setup before the change execution is run by
the CMA, it will fail.
This chapter describes how to log into the Change Management Application (CMA)
and view information on the Dashboard page. It includes the following sections:
Logging In to CMA
Viewing Settings
Switching Between Patch and Refresh Queues
Viewing Details
Working with Scheduled Refreshes
Reviewing Executions that Require Attention
Reviewing Running Change Executions
Reviewing Completed Change Executions
Note: If you have manager privileges, you will see the Dashboard
and Changes Executions tabs.
Note: If you log in to CMA during Stage 1 & 2, you will also see the
outage notifications described here.
Once the outage is complete, the warning messages disappear and restricted actions
are enabled again.
To add an exception, in the Run Exceptions area, click Actions > Add
Exception. Follow the instructions in Viewing, Adding, and Editing
Exceptions.
To stop, suspend, resume, submit, or delete one of the refresh steps, click the
relevant link in the Execution Status Detail area. Only completed refresh steps
are listed.
Note that you can also view details of the EM status of the instance by clicking
the hyperlink in this area.
Parameter Information
To view parameter information, click the plus sign next to Runtime Metadata.
The Execution Status Detail area displays information about the patch or refresh run.
Select an item to view details about that item. Click the arrow next to an item to
expand the tree.
2. Select a communication.
3. Select View Communication from the Actions menu.
The communication appears in a window.
4. Click Back and Next to view other communications.
Communications are listed in chronological order.
5. Click Done to close the window.
Add Communications
To add a communication:
1. Select Add Communication from the Actions menu.
2. Enter a subject and a comment, then click Submit.
RFC created for this issue: If an RFC has been created, check this checkbox.
Bug created for this issue: If a bug has been created, check this checkbox.
To add an exception:
1. Select Add Exception from the Actions menu.
The Add Exception box appears.
2. Enter the exception information, then click Add Exception.
You must complete fields marked with an asterisk.
Step Name: Click the Choose step name icon, then select the step from the list
displayed. Click Select.
Hostname: Enter the hostname of the target instance.
Action: Enter details of the action that resulted in an exception.
Error: Enter details of the error resulting from the exception.
Summary: Select the relevant category from the list.
Problem: Enter a description of the problem.
Solution: Enter a proposed solution for the problem.
RFC created for this issue: If an RFC has been created, check this checkbox.
Bug created for this issue: If a bug has been created, check this checkbox.
Note: You can only retry, update and retry, ignore, or confirm job
steps.
Note: You can only initiate a refresh with the status Awaiting
Implementation.
1. Select the icon in the Initiate column for the refresh that you want to edit.
The Initiate a New Refresh Run wizard starts with the RFC populated.
2. Edit the refresh as required.
See Also: For information about using the Initiate a New Refresh
wizard, see Chapter 5.
Note: By default, the Attention Required area does not list stopped
refresh or patch requests. To include stopped requests, click the Edit
icon, deselect the Exclude Stopped Execution check box, then click
Save. This option is not available on the Dashboard tab for the
manager role.
To refresh the Attention Required area, click Manual Refresh in the upper right corner
of the page.
The Elapsed Time column lists the amount of time that an execution has been running.
This time is also listed on the Details page.
1. Edit the dates in the Completion Date Between boxes or click the calendar icons to
select new date ranges.
2. Click the Search icon.
All refreshes or patches completed between the specified dates appear in the table.
To view execution details, click the icon in the Details column.
To view an RFC, click an RFC in the RFC column.
To refresh the Completed Change Executions table, click Manual Refresh in the upper
right corner of the page.
This chapter describes how to use the CMA to initiate a patching run. It includes the
following sections:
Patch Type Overview
Specify the RFC ID
Change Target System Information
Specify Patch Options
Specifying Hosted Servers Password
Review Patching Run Information
https://cmportal.oracle.com/cmportal/
Note: You cannot created a refresh before the scheduled start time in
the RCF. If you try, an error message appears and you cannot
continue.
4. If the RFC was created with an incorrect subtype, you may override the subtype
by clicking Change, then selecting the appropriate subtype. Doing this enables
CMA to ask the appropriate interview questions for this RFC.
5. Click Next.
The Target System Information page appears.
Note: If you receive an error message on this page, follow the instructions
in the message.
Note: If the Status for Patching is System in Blackout and you click Next,
you will receive the following prompt:
2. For application-tier patch run requests, specify the number of AD workers that
you want AutoPatch and AD Administration to use during the patching run in the
Workers box.
This box cannot be empty and must be set between 1 and 25. By default, this field
is set to twice the number of processors in use by the primary database node of the
customer system, which is the same default number of workers that AutoPatch
and AD Administration normally present to the user.
3. For application-tier patch run requests, in the NLS box, click the short name of
each NLS language for which you want the translated version of each translatable
patch applied.
For application-tier patch run requests, the NLS box contains the short names of
any NLS languages that are installed in the customer system, along with None.
None specifies American English, which is the base language of every On Demand
customer system. If no NLS languages are installed in the customer system, the
NLS box contain only None.
4. For Database upgrade patch types, select the Oracle Database release number that
you want to upgrade to.
If you select 11.1.0.7, you will perform a Database Upgrade. If you select 10.2.0.4,
you will perform a Database Patchset Upgrade.
3. In the Patch Directory Location box, enter the full path of the location of each
patch ZIP file for the patches listed in the Patch Number List box.
The default value for this field is %appl_top%/ patches for an application-tier
patching run request and %oracle_home%/patches for a database-tier patching
run request, but you can use any location that grants read and write permissions
to the owner of the application-tier file system (for an application tier patching run
request) or the owner of the database-tier file system (for a database tier patching
run request) of the customer system to be patched. The variable %appl_top% may
be used with an application-tier patching run request to represent the instantiated
value of the $APPL_TOP environment variable, and the variable %oracle_home%
may be used with a database-tier patching run request to represent the
instantiated value of the $ORACLE_HOME environment variable.
If one or more of the patch ZIP files for the patches listed in the Patch Number
List box are not available in the location entered in the Patch Directory Location
box, and they are available to the general public from OracleMetaLink, the
patching procedure will download them to this location. If the patches have a
distribution status of By MetaLink and are not classified either Internal or
Controlled in ARU, they are available to the general public. If the patches do not
meet these criteria, you must manually copy them to the location specified in the
Patch Directory Location box.
When defining an application-tier patching run request, if you plan to apply
NLS-translated versions in addition to the base language version of any patch
during the patching run, the patch ZIP file for each desired NLS-translated version
of each patch must also be located in the directory listed in the Patch Number List
box.
4. In the Stage Directory Location box, enter the full path of the location of the patch
stage area, which is where each patch ZIP file will be unzipped and from where
each patch will be applied using AutoPatch (by the application tier patching
procedure) or OPatch (by the database tier patching procedure).
The default value for this box is %appl_top%/patch_stage for an
application-tier patching run request and %oracle_home%/patch_stage for a
database-tier patching run request, but you can use any location that grants read
and write permissions to the owner of the application-tier file system (for an
application tier patching run request) or the owner of the database-tier file system
(for a database tier patching run request) of the customer system to be patched.
The variable %appl_top% may be used with an application tier patching run
11. Select desired options from the Patching Procedure Options box, then click Next.
If the patch numbers entered the Patch Number List box are valid patches, the
Patch List page appears.
Note: For CPU patches, select the month and year of the CPU patch.
Select Apply E-Business Suite for applications patching and select
RDBMS for DB patching. To reapply a DB patch, select Force RDBMS
Patch.
If you select a date in the future, you will receive the following
validation error message:
The CPU date should be between Oct 2008 and the
current date.
Confirm link. You will be prompted for your username and password. Click
Submit and the patching procedure will continue.
Create appsutil.zip: The appsutil.zip file is created when the AutoConfig
application is installed or patched. This file contains all of the AutoConfig files
that are needed on the database tier. After AutoConfig is installed or patched, the
appsutil.zip file contains the new or modified AutoConfig files for the database
tier. You can copy this zip file to each database server node and unzips it to install
or modify AutoConfig on the database server node.
Run AutoConfig on the Application Tier: Controls whether the patching
procedure runs AutoConfig on each application tier node after all patches have
been applied and any optional AD Administration tasks have been performed.
When the patching procedure runs AutoConfig, it does so first in test mode, and
then in normal mode immediately afterwards. Test mode generates a
configuration report that shows what configuration changes AutoConfig would
have made, without actually performing any of the changes; normal mode
performs all the changes. By default, this option is disabled, meaning that
AutoConfig will not be run.
Run AutoConfig on the Database Tier: Controls whether the patching procedure
runs AutoConfig on each database-tier node after all patches have been applied
and any optional AD Administration tasks have been performed. When the
patching procedure runs AutoConfig, it does so first in test mode, and then in
normal mode immediately afterwards. Test mode generates a configuration report
that shows what configuration changes AutoConfig would have made, without
actually performing any of the changes; normal mode performs all the changes. By
default, this option is disabled, meaning that AutoConfig will not be run.
Note: You cannot select this option unless you also select Run
AutoConfig on the Database Tier.
accomplished), the patching run can be continued at the point it left off. By
default, this option is neither selectable nor enabled, meaning that if the Run
AutoConfig option is enabled, the patching procedure will not pause between
running AutoConfig in test mode and normal mode.
This is how the pause works: the "Validate AutoConfig Test Mode Output" step of
the patching procedure (which comes just after the "Run AutoConfig in Test
Mode" step) will return an "Action Required" status, and the patching procedure
will pause until action is taken and confirmed. You will see the 'Action Required'
status on the dashboard. Navigate to the Run Detail page. The offending step will
be displayed with the Action Required status in the step tree. Click on the step to
view its information in the detail pane. When you are ready for the patching run to
continue, select the applicable target and click the Confirm link. You will be
prompted for your username and password. Click Submit and the patching
procedure will continue.
detail pane. When you are ready for the patching run to continue, select the
applicable target and click the Confirm link. You will be prompted for your
username and password. Click Submit and the patching procedure will continue.
Pause After OPatch Steps: Controls whether the patching procedure pauses
indefinitely just after it has used OPatch to apply the last patch in the patching
run, but before it performs any post-patching tasks. This can be useful for
performing manual tasks that certain patches require after the patch has been
applied, or for performing maintenance on the customer system that needs to take
place immediately after patches are applied. Once the manual tasks have been
performed (or whatever necessitated the pause has been accomplished), the
patching run can be continued at the point it left off. By default, this option is
disabled, meaning that the patching procedure will not pause after it applies the
last patch in the patching run.
This is how the pause works: the "Post-Database Patch Step" of the patching
procedure (which comes just after the "Relink All RDBMS Binaries" step) will
return an "Action Required" status, and the patching procedure will pause until
action is taken and confirmed. You will see the "Action Required" status of the step
in the Steps tab of the Status Detail page of the EM Grid Control console. You will
see the 'Action Required' status on the dashboard. Navigate to the Run Detail
page. The offending step will be displayed with the Action Required status in the
step tree. Click on the step to view its information in the detail pane. When you are
ready for the patching run to continue, select the applicable target and click the
Confirm link. You will be prompted for your username and password. Click
Submit and the patching procedure will continue.
Relink All Executables After Patching: This option is only selectable if the Relink
Updated Executables option in the OPatch Options section of the accordion
control is disabled. It controls whether the patching procedure attempts to relink
all binary executables in the Oracle home once all patches have been applied. (The
Relink Updated Executables option, which is described later in this section of the
document, controls whether OPatch relinks any binary executables that were
updated by the patching run once all patches have been applied.)
There is no need for OPatch to relink just the binary executables updated by the
patching run if the patching procedure is going to attempt to relink all binary
executables in the Oracle home anyway. Therefore, if one of the Relink All
Executables After Patching or Relink Updated Executables options are selected,
the other one will be grayed out and unselectable; you must unselect one first
before you can select the other one. By default, the Relink All Executables After
Patching option is neither selectable nor enabled, meaning that the patching
procedure will not attempt to relink all binary executables in the Oracle home once
all patches have been applied, but OPatch will relink any binary executables that
were updated by the patching run once all patches have been applied.
that certain patches require after the patch has been applied, or for performing
maintenance on the customer system that needs to take place immediately after
patches are applied. Once the manual tasks have been performed (or whatever
necessitated the pause has been accomplished), the patching run can be continued
at the point it left off. By default, this option is disabled, meaning that the patching
procedure will not pause after it applies the last patch in the patching run.
3. If desired, select Install United States College Data and Install JIT/Geocode
Data.
Patch: Lists each patch number that was entered in the Patch Number List box of
the Patch List Options page.
Product: Displays the Oracle product name to which each patch belongs. If there is
a problem validating the patch with OracleMetaLink, then this column is empty.
Abstract: Displays the abstract of the bug on which each patch is based. If there is
a problem validating the patch with OracleMetaLink, then this column display
NOT FOUND.
Available if the patch is available for download to the general public in that
language
Obsoleted if the patch has been obsoleted and replaced by another patch
Not found if the patch is not available for download to the general public in
that language, is not a valid EBSO application tier product patch, or if there is
a problem validating the patch with MetaLink.
Readme: Click the hyperlinked Readme file name to open the Readme file.
Password: If the patch is password protected and you want CMA to download the
patch, enter the correct password for the product and code version running on the
target instance. You will also see an alert that the patch may be password
protected. Passwords are entered in clear text.
Patch Application Order: You can change the patch application order by entering
the new order in this box. This capability is not available if you have chosen to
merge patches.
Reapply, Pause, or Preinstall Patch: Check the patch checkbox to specify
reapplication of the patch, a pause after the patch, and preinstall mode.
Delete Patch: Click the Delete icon to delete the patch.
Note: If you do not enter the correct password, the patching run will
fail.
2. Click Yes to validate your password or click Skip this Step to continue without
validation.
3. If the validation fails, you click the link to the EM Console to correct your
credentials.
4. For Database upgrade patch types, select the Oracle Database release number that
you want to upgrade to.
If you select 11.1.0.7, you will perform and Database Upgrade. If you select
10.2.0.4, you will perform a Database Patchset Upgrade.
5. Click Next.
The Review page appears.
Note: this column does not appear in the table if the request is for an
application-tier patching run and you enabled the Merge Patches
option on the Patch List Options page.
To change the patch application order, review the following rules then edit the
numbers in the Patch Application Order column:
The field cannot be empty.
Any positive or negative integer, or zero, can be used.
Negative integers take precedence over zero and positive integers, just like the
concept of a number line in mathematics being read from left to right. For
example, -8 takes precedence over -4, which takes precedence over 0, which takes
precedence over 4, which takes precedence over 8, and so on.
The values do not have to be sequential. For example, you could use the values
-14, 0, and 8 to determine the application order of three patches.
Values may be duplicated. When two or more patches share the same Patch
Application Order value, those patches will be applied in a random order relative
to each other.
Duplicated values may be grouped. For example, if there are eight patches to be
applied, and their Patch Application Order values are 1, 2, 2, 2, 3, 3, 4, and 5, then
the patch with the value 1 will be applied first, followed by the three patches with
the value 2 applied in a random order, followed by the two patches with the value
3 applied in a random order, followed by the patch with the value 4, finally
followed by the patch with the value 5.
If you navigate back to the Patch List Options page, change the order in which the
patches are listed in the Patch Number List box, and then navigate to the Patch List
page, the order change will be reflected in the Patch Application Order column.
Select the box in the Okay To Reapply column to apply a patch that has already been
applied to the customer system. Doing this can be useful if you suspect that an applied
patch may not have been completely and successfully applied.
If the box in the Okay to Reapply column is not selected and the patch has already
been applied, the patching procedure will not re-apply the patch and the run will fail.
To pause the patch application after either AutoPatch (Apps run) or OPatch (DB run)
has performed the file copy and database actions of the patch, select the box in the
Pause After Applying column.
Pausing a patch application will enable you to perform manual tasks. These tasks may
be tasks required by the patch after a patch has been applied or system maintenance
tasks required immediately after certain patches are applied.
After the manual tasks have been performed, the patching run can be continued at the
point it left off.
Preinstall Mode is an AdPatch option. Select Preinstall Mode to apply the patch before
running AutoInstall if the patch includes files for AutoInstall or another utility called
by AutoInstall.
Note: Deleting a patch from the patching run does not delete
anything about the patch from the file system, for example, the patch
ZIP file.
Note: If the CMA cannot confirm the host login password, you
cannot submit the patch run. In this case, a red circle appears next to
the Credentials page in the summary on the left of the screen.
This chapter describes how to use the Change Management Application (CMA) to
imitate a refresh run. It includes the following sections:
Specifying the RFC ID or Customer Name
Specifying Refresh Type
Specifying Customer, Target, and Source Instances
Specifying Hosted Servers Password and PowerBroker Role
Specifying Backup Options and Advanced Settings
Changing, Cancelling, or Submitting a Refresh Run
Retrying Failed Steps
Note:
1. Search by Customer Name to display a list of customers that
match your search criteria.
2. Select a customer from the Customer List, then select a target
instance from the Target Instance list.
3. Enter the RFC ID.
A list of previously scheduled change executions for the specified
RFC ID may appear.
4. Click Yes to proceed with the refresh run request.
The CMA validates the RFC ID with the selected customer and target. If
the RFC ID does not pass validation a warning or an error message
appears. Warning messages are red and error messages are blue. If you
receive an error message, you cannot proceed with the selected RFC ID. If
you receive a warning message, you may proceed with the refresh
c. Click Search. All refresh requests meeting these criteria are displayed.
When you search by customer name, a list of matching customer names appears in the
Customer List box:
1. Select a customer name in the Customer List box.
The CMA populates the Target Instances box with the target instances for the
selected customer.
Note: The CMA will not initiate the refresh run request without a
valid RFC ID. If there are issues with the Orion connection, the CMA
will allow the user to proceed if the user has used the customer search.
Note: If this value is incorrect, click Change, then select the correct
value.
Note: If you do not enter the correct password, you will not be able
to submit the refresh run.
2. From the Role list, select one of the following PowerBroker roles to be used during
the refresh run:
OHSDBA
OHSCC
PRODSUPP
Click Next.
3. If the password you entered is valid, you will be prompted to validate your EM
Host Level Credentials. Click Yes.
4. If the following message is selected on the page, click the link displayed in the
message, then enter your EM user name and password to initialize the EMCLI
Client:
Invalid EM Host Level Preferred Credentials...
Note: A standard snapshot contains the creation date in the file name
in the format YYYYMMDD. Snapshots that do contain the creation
date in this format are non-standard snapshots.
Note: The CMA now supports RAC instances. If your RFC ID is for a
RAC instance, the RAC mount points are listed for the Oradata file.
Each mount point can have more than one snapshot. Select the
snapshot that you want to refresh.
Note: This option is only enabled if the Copy files from source
oradata volumes to target oradata option is set to Yes in the Setting
tab.
Specify whether a split should be performed after the target database
volumes are copied from the source system using the NetApp
Flexclone feature. This option applies only if it is possible to perform a
Flexclone copy.
Note: This option is only enabled if the Copy files from source
oradata volumes to target oradata option is set to Yes in the Setting
tab.
Specify whether a split should be performed after the target database
volumes are copied from the source system using the NetApp
Flexclone feature. This option applies only if it is possible to perform a
Flexclone copy.
1. When you have reviewed the refresh information on the Review and Submit page,
click Next.
The Refresh Request page appears.
2. Review the refresh run request information, then do one of the following:
To cancel the refresh run request, click Cancel. The refresh run request is
cancelled and the Dashboard page appears.
To make a change to the refresh run request, click Back.
To submit the refresh run request, click Submit. A list of previously scheduled
change executions for the specified RFC ID appears. To proceed with the
submission, click Yes. If you click No, the refresh is not submitted.
Note: If there are errors in the previous steps, the Submit button is
not available. A list of errors appears on the page as well as the step in
which the error occurred.
3. The Dashboard page appears and a message indicating the status of the refresh
run submission is displayed.
Most of the refresh procedure steps can be retried within the EM 10g Grid Control
console once the problem that caused the failure has been fixed. (Refer to
Appendix A and Appendix B of this document for troubleshooting information.)
The only exceptions are:
All bugs and enhancements related to the CMA and the Oracle Applications Patching
and Refresh Procedures must be logged against product ID 4319, SE EM Initiative.
The Bug/Enhancement Filing FAQ for Change Management's EM Initiative contains
information about the following topics:
Components to be selected
Subcomponents, where applicable, to be selected
Filing and closing templates
Subject formatting
Status handling
Formatted bug reports
This FAQ is available at the following URL:
https://sac.us.oracle.com/change-em/process/bug_enhancement_filing_faq.html
You must complete the remaining steps if the output of this command displays:
Troubleshooting B-1
Review Log Files
Otherwise, the EM CLI Client has already been initialized with the EM Grid
Control console and your credentials, and you can stop here.
5. If the EM CLI has not been initialized, use the EM CLI utility to initialize the EM
CLI Client with the EM Grid Control console location and your EM Grid Control
credentials. The following example shows how to initialize the current EM Grid
Control console, where CONSOLE_URL is either the patching run or refresh runs
EM Grid Control console, username is your EM Grid Control username and
password is your EM Grid Control password:
$ emcli setup -url="CONSOLE_URL" -
username="username" -password="password"
For example:
To run the EM CLI utility for patching runs:
$ emcli setup -url="http://odem1.oracle.com/em/" -
username="jeff.lunn" -password="welcome"
QTESTI_to_TTES_4DED2ABD1AB1354AE040940AE32F20E5.log
QTESTI_to_TTES_4DED2ABD1AC2354AE040940AE32F20E5.log
QTESTI_to_TTES_4DED2ABD1AD3354AE040940AE32F20E5.log
3. Log in to the OMS node as the owner of the OMS file system.
4. Change directories to the OMS home, for example:
$ cd /emsac/EM10203/oms10g
6. Change directories to the directory where you want to create the XML files.
7. Enter the following command to use the EM CLI utility to create a temporary
output text file consisting of a single, huge, unformatted line:
$ emcli get_instance_data_xml -instance="instanceGUID" > "temporary output
file"
For example:
$ emcli get_instance_data_xml -instance="50E9189CB94A2C7EE040940AD32F43A0" >
"QTESTI_to_TTESTI_dump.tmp"
Troubleshooting B-3
Create XML Files from Runtime Parameters
For example:
$ $ORACLE_HOME/refresh/2.8/bin/pafUtil.sh -getRuntimeData emsac.oracle.com 1521
emrep sysman oracle 50E9189CB94A2C7EE040940AD32F43A0
This second XML file is created in the current directory, with the name
RuntimeDatarandom_number.xml. For example:
RuntimeData6747.xml
10. Review the two XML files with a text editor to see all the runtime parameter
values used during the refresh run.
For example:
<scalar value="643D60B75FC6AF9EE040558C0EAD57E0"
classname="oracle.sysman.pp.paf.impl.EncryptedString" name="V_TGT_APPS_DB_
PWD"/>
DECRYPT(ENCRYPTED)
----------------------------------------------------------------------------
apps
For a list of each step in the refresh procedure, including a brief description of the step,
the file names that are relevant to the step, the technical details of what the step does,
and useful troubleshooting information about the step, see the EM Refresh Job Steps
page on the SAC Wiki:
http://sacwiki.us.oracle.com/wiki/index.php/EM_Refresh_Job_
Steps#Initialize_.28Computational_Step.29
and the Elapsed Time field keeps a running count of how long the patching run
has been paused.
3. If desired, enter information about the Cluster Manager shutdown in the Note
field.
4. After you restart the Cluster Manager processes on each database server node and
you have entered any notes that you want recorded, select each applicable target
the click Confirm. The patching procedure continues where it left off, starting up
the database instance and listener.