Oracle Corporation

Maintenance Wizard User Guide Release 2

Creation Date: Last Updated: Version:

March 1, 2008 Monday, April 04, 2011 2.18

Contents

Preface ...................................................................................................................................... 1 Maintenance Wizard Overview ............................................................................................ 2 Features of the Maintenance Wizard ............................................................................ 2 Architecture Components .............................................................................................. 2 About Maintenance Wizard Products .......................................................................... 3 About Maintenance Wizard Users ................................................................................ 4 About Categories, Product Families, Tasks, and Steps .............................................. 4 Before You Begin ..................................................................................................................... 6 Note On Browser Usage: Do Not Reload or Refresh Your Browser! ........................ 6 Verify That Your Browser is Configured Correctly .................................................... 6 Set Up Tasks for Maintenance Wizard ................................................................................. 7 Step 1: Logging In ............................................................................................................ 7 Step 2: Creating New Customers ................................................................................... 7 Step 3: Creating a Project ................................................................................................ 8 Step 4: Creating New Users ............................................................................................ 9 Step 5: Assigning a Project Administrator ................................................................. 11 Step 6: Registering Nodes for the Project ................................................................... 12
Specify Node Attributes Manually ............................................................................. 13 Copy From Existing Project ......................................................................................... 14 Read From AutoConfig ................................................................................................ 15

Step 7: Assigning Responsibilities to Users ................................................................ 16 Customizing Maintenance Wizard ..................................................................................... 18 Adding Additional Categories, Product Families, Tasks and Steps ....................... 18
Add Categories ............................................................................................................. 18 Add Product Families .................................................................................................. 19 Add Tasks ...................................................................................................................... 20 Add Steps ....................................................................................................................... 21

Running Steps in Maintenance Wizard ............................................................................. 24 Accessing Maintenance Wizard Steps ........................................................................ 24 About the Maintenance Wizard Interface .................................................................. 24 Actions for Each Step in the Project ............................................................................ 25 Executing a Step Automatically or Manually ............................................................ 26 Marking the Success or Redo of Each Step ................................................................. 27 Maintenance Wizard Online Help............................................................................... 28 Viewing Log Files .......................................................................................................... 29 About Utilities ....................................................................................................................... 31 Troubleshooting Maintenance Wizard ....................................................................... 31
Check Your Installation................................................................................................ 31 Use the Collector Script to Gather Debug Information for Installation Issues ..... 31

Page ii

Check Your Project Configuration .............................................................................. 33 Use the Collector Script to Gather Debug Information for Project Configuration Issues .............................................................................................................................. 33

Using the OS and SQL Utilities .................................................................................... 35

Run OS Commands ...................................................................................................... 35 Run SQL Queries .......................................................................................................... 36

About Reporting ................................................................................................................... 37 Run System or Project Administration Reports ........................................................ 37 Run Engineer Reports ................................................................................................... 37 Running Live Patch and Live Update ................................................................................ 39 Download and Run Live Patch .................................................................................... 39 Update Existing Projects Using LiveUpdate .............................................................. 40 What to Do if the Live Update or Live Patch Fails .................................................... 40 Administering Maintenance Wizard .................................................................................. 41 Appendix A: Maintenance Wizard Common Tools......................................................... 42 Traditional Approach to the Upgrade for UNIX ....................................................... 42 New Approach to the Upgrade for UNIX .................................................................. 42 Improve System Performance During the Upgrade ................................................. 42 System Preparation........................................................................................................ 42 Merge and Apply Patches ............................................................................................ 42 Merge Patches ................................................................................................................ 44 About the Utilities Category ........................................................................................ 44 About Patching Tasks ................................................................................................... 44 About Administer Services .......................................................................................... 46 About View Information .............................................................................................. 49 About MW Tool ............................................................................................................. 50 Appendix B: Product Specific Information for Maintenance Wizard ............................ 52 Note to 10.7 Customers ................................................................................................. 52 Variables to Use for Customization ............................................................................ 52 Appendix C: Examples for Using the OS Command and SQL Query Utility .............. 60 Worker Log Files ............................................................................................................ 61

Page iii

Preface
This document describes how to use Maintenance Wizard, version 2. Maintenance Wizard includes the following features: Supports upgrade to release 12 from releases 11.5.9 and later Includes many post-upgrade bug fixes. The R12 post upgrade patch list now includes the contents of the Recommended Patch List (RPL), which starts the instance out on the latest code. Enables you to maintain multiple tiers across different platforms including HP Tru64 UNIX, HP-UX PA-RISC, IBM AIX based Systems, Linux x86, and Solaris Operating System (SPARC). Enables you to use secured remote access (SSH) or remote shell (RSH) communications between nodes. Enables you to view logs for each step performed, as well as live progress reports, historical data, and timing reports. Enables you to customize projects by adding categories, product families, tasks, and steps. Enables you to use My Oracle Support to download live updates, required upgrade patches, and any other required patches. Provides Web-based access to run UNIX commands and to run SQL Query commands to check and view the Oracle E-Business Suite database settings.

Note: The screenshots displayed in this document are only examples; the exact screens that you see vary based upon your installation and operating system.

Page 1

Maintenance Wizard Overview

Features of the Maintenance Wizard
Maintenance Wizard: Presents a consolidated, personalized set of instructions in a step-by-step format Enables validation of important activities to prevent downstream issues Maintains log and status information for all tasks Enables Project Administrators to assign different groups of upgrade tasks to different users Downloads, merges, and installs many required patches automatically Provides access for Web-based operating system (OS) commands to check the upgrade processes, logs, and OS status during patch upgrades. Provides project management utilities to record the time taken for each task and its completion status Enables maintenance of multiple customer systems Enables maintenance of multiple projects such as Development Maintenance, Production Upgrade, and Test Upgrade. Provides different user types, each with its own responsibilities and permissions. Enables the creation of customized steps to accommodate specific project requirements. Documents and displays additional information linked to each step via a user notepad. Provides setup substeps that can be executed to determine whether a step is ready to be run, and if it is relevant for the current upgrade. Provides validatation substeps that can be executed to determine whether a step executed successfully before continuing with the upgrade. Executes each step either manually or automatically. Provides status tracking of the setup, execute and validate steps.

Architecture Components
Maintenance Wizard requires the following: A system running a UNIX or Linux operating system with Oracle Database 10g installed Remote or Secure Shell to be configured (For information about how to set up a remote or secure shell, see Installing Maintenance Wizard: A Step-by-Step Guide (My Oracle Support Note 329476.1) Internet Explorer 6 or later or Firefox 3 or later for all end users of the tool

Page 2

About Maintenance Wizard Products

Maintenance Wizard uses one of following products to assist you in your upgrade procedure: Maintenance Pack Assistant for 11.5.10 Use this product to upgrade Oracle E-Business Suite 11i to the latest available 11i version. It contains all of the steps from the 11.5.10.2 Maintenance Pack readme file. The possible upgrade path is as follows: o 11.5.3 or later --> 11.5.10.2

Upgrade Assistant for 11.5.10 Use this product to upgrade Oracle Applications version 10.7 or 11, to the latest available 11i version. It contains all of the steps from the Oracle Applications Upgrading Oracle Applications Release 11i (11.5.10.2) manual as well as the release notes. The possible upgrade paths are as follows: o o o o 10.7 SmartClient --> 11.5.10.2 10.7 Character --> 11.5.10.2 10.7 NCA --> 11.5.10.2 11.0.3 --> 11.5.10.2

Applications Database Upgrade Assistant 10g Use this product to upgrade Oracle E-Business Suite to Oracle Database 10g. It contains all of the steps from the Oracle 10gR2 Database Preparation Guidelines for an Oracle E-Business Suite Release 12 Upgrade note and the Oracle Applications Release 11i with Oracle Database 10g Release 2 (10.2.0) note. The possible upgrade paths are as follows: o o o 8i -> 10.2.0.3 9i -> 10.2.0.3 10.1 -> 10.2.0.3

Release Update Pack Assistant 12 Use this product to apply a Release Update Pack for Release 12 to the Oracle E-Business Suite. It contains all of the steps from the Release Update Pack readme as well as the release notes. The possible upgrade path is as follows: o 12.1.1 --> 12.1.2

Upgrade Assistant for Release 12 Use this product to upgrade Oracle E-Business Suite to the Release 12 version of the software. It contains all of the steps from the Oracle Applications Upgrade Guide: Release 11i to Release 12 manual as well as the release notes. The possible upgrade path is as follows: o 11.5.9 or later --> 12.1.1

Applications Database Upgrade Assistant 11g Use this product to upgrade Oracle E-Business Suite to Oracle Database 11g. It contains all of the steps from the Oracle 11g Database Preparation Guidelines for an Oracle E-Business Suite Release 12 Upgrade note and the Oracle Applications Release 11i with Oracle Database 11g note. The possible upgrade paths are as follows:

Page 3

o o

9i -> 11.1 10g -> 11.1

Maintenance Pack Assistant for 12 Use this product to upgrade Oracle E-Business Suite version 12.0 or later . It contains all of the steps from the 12.1.1 Maintenance Pack readme file. The possible upgrade path is as follows: o 12.0.0 or later --> 12.1.1

About Maintenance Wizard Users

Maintenance Wizard has three types of users: System Administrators System Administrators are responsible for maintaining users, customers, and projects. In addition, the System Administrator performs Live Patches to ensure that Maintenance Wizard is updated with the latest code. Maintenance Wizard provides one default sysadmin user. You can define additional System Administrators. Project Administrators Project Administrators configure projects, create user accounts, and assign tasks to the Upgrade Engineers. Each project can have one or more Project Administrators. Note: You are not required to create a Project Administrator because a System Administrator can perform all project administration tasks. Upgrade Engineers Upgrade Engineers complete the actions that are a part of the upgrade. An individual engineer might be responsible for performing all the steps of the upgrade or just some selected steps. Usually, each project has multiple Upgrade Engineers.

About Categories, Product Families, Tasks, and Steps

All maintenance procedures are organized into a hierarchy of categories, product families, tasks, steps, and substeps: Categories Categories represent major groupings of tasks and steps that must be completed during the project. These categories often correspond to chapters in the source documentation. Product Families Product Families are broad groupings of tasks and steps related to a particular category of the project. Typically, Product Families relate to groups of related products or aspects of the project such as Database Upgrade steps. Tasks Tasks are specific groupings of related activities, often associated to a specific Applications module. Steps

Page 4

Steps are the actions that must be completed during the project. Each step includes one or more of the following substeps: 1. 2. 3. Setup Execute (always present) Validate

Every step must include an Execute substep. Setup and Validate substeps are not required but can be used to prepare the environment (Setup) and verify the results (Validate) for the Execute substep.

Page 5

Before You Begin

Read this section carefully; it contains important information about Maintenance Wizard.

Note On Browser Usage: Do Not Reload or Refresh Your Browser!

When using Maintenance Wizard, do not use the Reload or Refresh feature of your Web browser in the EOF Script Executer window. Clicking Reload or Refresh causes Maintenance Wizard to execute the current step again. If you click Reload or Refresh a number of times, you can potentially have dozens of processes running, with each process trying to accomplish the same task. This is a common mistake when running a long-running step. To refresh a long-running step: 1. 2. Close the Script Executer window by clicking X in the upper right corner. Right-click the Step Action Run window and select Refresh periodically until the step has completed.

Verify That Your Browser is Configured Correctly

Before you install Maintenance Wizard, you must configure your browser settings. There are no required settings for using Mozilla Firefox. However, for Microsoft Internet Explorer: 1. 2. 3. 4. From the Microsoft Internet Explorer menu, select Tools, then Internet Options. In the Temporary Internet Files area, click on Settings. The Settings window appears. Select Every visit to the page. Click OK twice.

Page 6

Set Up Tasks for Maintenance Wizard

Before running Maintenance Wizard, you must perform some set up tasks, such as associating customers with projects, and assigning responsibilities to users. Maintenance Wizard comes with one default System Administrator user (sysadmin). When you create a new project, you base it on Maintenance Wizard products.

Step 1: Logging In
Figure 1 displays the Maintenance Wizard Login page. Maintenance Wizard is delivered with one default user account with System Administrator responsibility. Note: Click additional setup for IE to view the required browser settings Figure 1 Login Page

To log in to Maintenance Wizard as System Administrator: 1. 2. In the User ID field, enter sysadmin. In the Password field, enter sysadmin. Note: Change this password before giving other users access to Maintenance Wizard. Click Login. The Customer Maintenance page appears, similar to Figure 2.

3.

Step 2: Creating New Customers

When you log in to Maintenance Wizard as sysadmin, Maintenance Wizard displays the Customer page from the Configuration tab. The Customer list is empty until you add a customer. In Figure 2, some customers are added already.

Page 7

Figure 2 Customer Page

To add a customer: 1. 2. 3. 4. Log in to Maintenance Wizard as sysadmin. Click Configuration, then click the Customer subtab. Maintenance Wizard displays the Customer page, similar to Figure 2. In the Add Customer table, in the Customer Name field, enter the name of the new customer. Click Add. The customer is added to the Customer list.

To change the status of an existing customer: 1. In the Modify Customer table, select one of the following for the appropriate customer: 2. Open Access Enables full access to the customer Access Locked Prevents all access to the customer Click Modify.

Step 3: Creating a Project

To perform the upgrade, you must create a project. A project is used for a single iteration of the upgrade process. As you progress through the various test upgrades, you will create new projects each time. Maintenance Wizard provides a Master project. The Master project populates each new project with data. You can also copy data from a previous project if you have customized it. To view existing projects, click the Configuration tab, then click the Projects subtab. The Project Maintenance page appears similar to Figure 3.

Page 8

Figure 3 Projects Page

To create a new project: 1. 2. 3. 4. Click the Configuration tab, then click the Projects subtab. The Project Maintenance page appears similar to Figure 3. In the Add Project table, from the Customer Name list, select the customer for whom you are creating the project. In the Project Name field, assign the project a brief but concise name. Each Customer-Project name pair must be unique. From the Product list, select the product that corresponds to the type of upgrade you are performing. Note: It is very important that you choose the correct product because you cannot change it later. For more information about these products, see About Maintenance Wizard Products. Click More Details. Depending on the selected product, the Add Project table displays additional options. From the Source Version list, select the version from which you are upgrading. From the Destination Version list, select the version to which you are upgrading. In the Remote EOF_HOME field, enter the name of the directory where the EOF_HOME directory is stored on each tier. This is a directory name and not a directory path. Maintenance Wizard creates a directory with the same name on each remote tier. Note: This value must be unique. From the Copy Steps from list, select the existing project from which you want to populate the new project. Select the Master project to populate a new project with data. If you added steps to a previous project or you want to copy notes from a previous project, then you can select that previous project.

5. 6. 7. 8.

9.

10. Click Add to save the new project.

Step 4: Creating New Users

To add a new user: 1. 2. Log in to Maintenance Wizard as a System Administrator or a Project Administrator. Click the Admin tab, and then click the Add User subtab. The Add User page appears, similar to Figure 4.

Page 9

3. Figure 4 Add a New User

Figure 4.

4. 5. 6. 7. 8. 9.

In the User Name field, enter a user name for the new user. For example, jsmith. In the Full name field, enter the full name of the user. For example, John Smith. In the Email Address field, enter an e-mail address for the user. For example, john.smith@acme.com In the Password field, enter a password for the user. In the Re-enter Password field, enter the password again. In the Description field, enter a description for the user. For example, Financials System Analyst.

10. In the Phone Number field, enter a phone number for the user. 11. Click Add.

Page 10

Step 5: Assigning a Project Administrator

The first type of user is a Project Administrator. The Project Administrator is responsible for assigning specific tasks to Upgrade Engineers. The creator of the project is automatically assigned as a Project Administrator. To assign Project Administrator privileges to a user: 1. 2. Log in to Maintenance Wizard as a System Administrator. Click the Admin tab, then click the Assign Proj Admins subtab. The Assign Proj Admin page appears, similar to Figure 5.

Figure 5 Assign Project Administrator

3. 4. 5.

In the Assign Project Administrator Role table, from the Customer/Project list, select the project to which you want to assign a Project Administrator. From the Select user to assign list, select the user that you require for Project Administrator. Click Assign. A message appears stating that the user was successfully assigned.

Note: From the List Administrators for Selected Project table, select a project to view the Project Administrators assigned to that project. Click Remove to delete a Project Administrator from a project.

Page 11

Step 6: Registering Nodes for the Project

A Project Administrator must register nodes for the project before performing any other tasks. To register nodes for a project: 1. 2. Figure 6 Role Page Log in to Maintenance Wizard. Click Roles. The Role page appears similar to Figure 6.

3.

From the Project Administrator list, select the project name. The Project Maintenance page appears similar to Figure 7.

Figure 7 Project Maintenance Page

4. 5.

Check that the initial project setup is correct. Click Edit to make any changes. Click the Define Nodes subtab. The Define Nodes page appears similar to Figure 8.

Page 12

Figure 8 Define Nodes

6.

From the Node Source Type list, select a method: Manually specify node attributes Copy from existing customer/project Read from AutoConfig

Note: In general, you can use any combination of the three methods to define the nodes in your project. However, some node types cannot use all three methods. For example, some node types cannot be defined by the AutoConfig file. The following sections describe each of these methods. Specify Node Attributes Manually To manually specify node attributes: 1. Figure 9 Manually Enter Node From Node Source Type list, select Manually specify node attributes. The Manually Enter Node(s) page appears, similar to Figure 9.

2. 3.

In the Fully Qualified Hostname field, enter the name of the host on which the nodes will reside. Ensure that you include the domain name of the host. In the Username field, enter the operating system (OS) user name for the host specified in step 2. Note: If you have multiple OS users (for example one user owns the database and another user owns the Applications), you must specify those nodes separately. From the Platform list, select the required platform. From the Remote Access Type list, select whether you want to use remote

4. 5.

Page 13

shell or secure shell for remote execution. 6. Select the type of node that you are defining. Ensure that the selected node is owned by the OS user specified in step 3. Note: To select multiple for the same host, use SHIFT+select or CTRL+select. Click Save. The Attributes page appears similar to Figure 10.

7. Figure 10 Attributes Page

8. 9.

In the Attributes table, enter a value for each of the attributes. The displayed attributes depend on the nodes that you selected in step 6. Click Save. The Registered Nodes table appears.

10. Click Configure to define the nodes when you have registered all the node types using any combination of the methods as described in step 6 on page 13. Note: You must define data for all node types before you can continue. If the Configure button is not available, then you have not defined all the required node types completely. Copy From Existing Project To copy from an existing project: 1. 2. 3. From the Node Source Type list, select Copy from existing customer/project. The Copy Node(s) page appears. From the Copy Node Attributes from customer/project list, select the project from which you want to copy the node attributes. From the Node TYPE(s) list, select the type of node that you are defining. Note: To select multiple nodes for the same host, use SHIFT+select or CTRL+select. Click Copy. The Registered Nodes table appears Click Configure to define the nodes when you have registered all the node types using any combination of the methods as described in step 6 on page 13

4. 5.

Note: You must define data for all node types before you can continue. If the Configure button is not available, then you have not defined all the required node types completely.

Page 14

Read From AutoConfig To define the nodes automatically by reading the AutoConfig file: 1. 2. 3. From the Node Source Type list, select Read from AutoConfig. The Administration Node Autoconfig Setup page appears. In the Fully Qualified Hostname field, enter the name of the host on which the nodes will reside. Ensure that you include the domain name of the host. In the Username field, enter the operating system (OS) user name for the host specified in step 2. Note: If you have multiple OS users (for example, a user that owns the database and another user that owns the Applications), you must specify those nodes separately. In the Autoconfig Path field, enter the full path of the AutoConfig utility. Note: Do not use any environment variables. Ensure that you enter the full path such as /u01/foo/applmgr/apps/apps_st/appl/admin/PROD1.xml. From the Platform list, select the required platform. From the Remote Access Type list, select either remote shell or secure shell From the Node Type(s) list, select the type of node that you are defining. Some node types that are not registered yet may not appear in this list because they cannot be configured using this method. Ensure that the selected node is owned by the OS user specified in step 3. Note: To select multiple nodes for the same host, use SHIFT+select or CTRL+select Click Next. The nodes appear in the Registered Node(s) table. A window may appear to indicate that Maintenance Wizard could not retrieve some values from AutoConfig file. If this occurs, you must edit the attributes for the nodes displayed in the window and correct the values assigned to those attributes before proceeding. Click Configure to define the nodes when you have registered all the node types using any combination of the methods as described in step 6 on page 13.

4.

5. 6. 7.

8.

9.

Note: You must define data for all node types before you can continue. If the Configure button is not available, then you have not defined all the required node types completely.

Page 15

Step 7: Assigning Responsibilities to Users

The Project Administrator must assign responsibilities to engineers. To assign responsibilities: 1. 2. 3. Log in to Maintenance Wizard as a Project Administrator. Note: If you are logged in as a System Administrator, proceed to step 2. Click the Admin tab, then click the Assign Engineers subtab. The Responsibilities page appears. You may enter a search value in the Search User box and then click Search. A list of possible matches will be shown below the Search User box. Select the name of the required engineer by clicking on it. Note: If the required engineer does not appear in the list, see Step 4: Creating New Users. The Responsibilities page appears similar to Figure 11

Figure 11 Responsibilities

4. 5.

For each Category on the page, click the plus sign (+) to expand the list and view the product families and tasks associated with that category. Click the check box beside an entry to assign it to the selected engineer. You can assign any combination of the Category, Product Family, or Task levels. If you assign a higher-level entry to a user, then Maintenance Wizard includes all entries below that level in the hierarchy.

Page 16

Note: To assign all tasks to the selected engineer, click Assign All button at the bottom of the page. This option ignores any previous selections and forces a save. The Assign All option does not include Development Responsibility, OS Command Access, SQL Query Access, or Patching Access. a. b. To enable the engineer to customize the project content, check the Development Responsibility box. To enable the engineer to access the OS Command Access feature for this project, check the OS Command Access box. Ensure that the option is only granted to users with operating system access to the Applications system. To enable the engineer to access the SQL Query feature for this project, check the SQL Query Access box. Ensure that the option is only granted to users with database query access to the Applications data.

c.

d. To enable the engineer to access the Patching Access feature for this project, check the Patch Access box. 6. In the Save Responsibilities row, click Save.

Page 17

Customizing Maintenance Wizard

Adding Additional Categories, Product Families, Tasks and Steps
After installing Maintenance Wizard as described in Installing the Maintenance Wizard: A Step-by-Step Guide (My Oracle Support Note 329476.1), determine if you need additional categories, product families, tasks or steps to accommodate customizations, interfaces, and other organization-specific steps. Check the current project and investigate each customization to determine how it should be resolved. You must have a thorough understanding of the current installation and how it works for all products installed. Omitting information at this stage may return unexpected results. Note: Skip this section if you do not require additional categories, product families, tasks or steps. Add new categories, product families, tasks, or steps in the following order: 1. 2. 3. 4. Add Categories Note: You must have development responsibility for the current project to add categories. For more information about granting development responsibility, see step 5 of Step 7: Assigning Responsibilities to Users. You can insert new categories or update existing categories that you created. Note: You cannot update or delete predefined categories that come seeded in Maintenance Wizard. To add a category: 1. 2. Log in as the Upgrade Engineer. The Roles page appears From the Engineer list, select the required project. The Process page appears, similar to Figure 12. Categories Product Families Tasks Steps

Page 18

Figure 12 Process Steps

3. Figure 13 Category Page

Click the Customize tab, then from the Select Action list, select Category. The Category table appears similar to Figure 13.

Note: You may not see all of the categories displayed in Figure 13 because the categories depend on your configuration. The Action column is not available for Oracle seeded categories because you cannot modify these categories. 4. 5. Scroll down to the empty row in the Category table, then enter the new category name. The category name is limited to 20 characters. In the Order By field, specify where to insert the new category. Note: This category only appears in the drop-down list of the Process page after you add Product Families, Tasks, and Steps. Click Insert to save your changes.

6. Add Product Families

Note: You must have development responsibility for the current project to add Product Families. For more information about granting development responsibility,

Page 19

see step 5 of Step 7: Assigning Responsibilities to Users. You can insert new product families or update existing product families. Note: You cannot update or delete predefined product families that come with Maintenance Wizard. To add a product family: 1. 2. 3. 4. 5. Log in as the Upgrade Engineer. The Roles page appears. From the Engineer list, select the required project. The Process page appears, similar to Figure 12. Click the Customize tab. From the Select Action list, select Product Family. Select the category to which the new Product Family belongs. The Category Configuration portlet appears similar to Figure 14. Note: You may not see all of the product families because the product families depend on your configuration. The Action column is not available for Oracle seeded entries because you cannot modify these entries.

Figure 14 Adding a Product Family

6. 7. 8. Add Tasks

In the Product Family field, enter the name in the empty row. In the Order By field, specify where to place the new product family. Click Insert to save your changes.

Note: You must have development responsibility for the current project to add tasks. For more information about granting development responsibility, see step 5 of Step 7: Assigning Responsibilities to Users. To add tasks: 1. 2. 3. 4. 5. 6. Log in as the Upgrade Engineer. The Roles page appears. From the Engineer list, select the required project. The Process page appears, similar to Figure 12. Click the Customize tab. From the Select Action list, select Task. Select the category to which the new task belongs. Select the product family to which the new task belongs: The Category: Configuration table appears similar to Figure 15.
Page 20

Note: You may not see all of the tasks because the tasks depend on your configuration. The Action column is not available for Oracle seeded entries because you cannot modify these entries. Figure 15 Add a Task

7. 8. 9.

In the empty field in the Task column, enter a name of the new task. In the Order By column, enter the position as an integer where the new task appears in the list of steps. In the Documentation Link column, enter the URL for associated documentation if it is available. This URL appears as a link on the Task name when viewed in the Process tab.

10. Click Insert. Add Steps Note: You must have development responsibility for the current project to add steps. For more information about granting development responsibility, see step 5 of Step 7: Assigning Responsibilities to Users. For additional information about writing scripts to use with Maintenance Wizard, see Maintenance Wizard Scripting Language (My Oracle Support Note: 291888.1). To add steps 1. 2. 3. 4. 5. 6. 7. 8. Log in as the Upgrade Engineer. The Roles page appears. From the Engineer list, select the required project. The Process page appears, similar to Figure 12. From the Select Category list, select the Configuration category. Click the Customize tab. From the Select Action list, select Step. Select the category to which the new step belongs. Select the product family to which the new step belongs. Select the task to which the new step belongs. The Category: Configuration table appears, similar to Figure 16. Note: You may not see all of the steps because the steps depend on your configuration. The Action column is not available for Oracle seeded entries because you cannot modify these entries.

Page 21

Figure 16 Add a step

9.

Enter values in the following fields:

Field Order By Step Num Description Enter the position as an integer where the new task appears in the list of steps. Provide a number for the new step. This number must be unique within the particular task and indicate the sequence of the steps. For example, the first step has a value of 1 and the third step has a value of 3; the new step to appear between these steps is given the value of 2. If you want to insert a step between 2 existing steps, you must renumber the current step and all subsequent steps, then insert the new one. For example:

Original Step 1: Do A Step 2: Do B Step 3: Do C

Renumber Existing Steps Step 1: Do A Step 3: Do B Step 4: Do C

Insert New Step Step 1: Do A Step 2: Do D Step 3: Do B Step 4: Do C

Step Condition Source Documentation ID Apps Short Name Install Status

Click the Notebook icon to specify whether the step is required, optional, recommended, or conditionally required. Click the Notebook icon to select C for custom.

Version Filter:From Version Filter:To

Secondary Version Filter From Secondary Version Filter To

Platform Specification

Click the Notebook icon to select the Application short name. Only Applications that are installed in your Applications environment appear in the list. Click the Notebook icon to select the install status. The step is displayed if you select one of the following: I Product is installed S Shared only IS Product is installed or shared Note: You must specify this value by selecting the Notebook icon or by using uppercase. If you specify the value in lowercase, Maintenance Wizard displays an error message. Specify the version from which you are upgrading. You must enclose the version number in colons. For example: :11.5.8: Specify the version to which you are upgrading. You must enclose the version number in colons. For example: :12: For certain upgrades, specify the version of the secondary product from which you are upgrading. You must enclose the version number in colons. For example: :10.2.0.4: For certain upgrades, specify the version of the secondary product to which you are upgrading. You must enclose the version number in colons. For example: :10.2.0.4: Click the Notebook icon to select the platform to which the step applies. If it is not specific to any platform, select All.

Page 22

Field Step Script ID TUM's Step Key

Description Enter a name to describe the new step. This field is an internal identifier and is automatically populated by Maintenance Wizard. This field is an internal identifier and must remain blank.

10. Click Insert. The new categories, product families, tasks, and steps are available within Maintenance Wizard. Verify that each new element appears as intended.

Page 23

Running Steps in Maintenance Wizard

Note: Before you begin a project, refer to the Before You Begin section of this guide. When running steps, perform all steps in the order in which they are specified. If you do not complete steps in the required order, the success of the project could be compromised.

Accessing Maintenance Wizard Steps

To access the maintenance wizard steps: 1. 2. 3. Log in as the Upgrade Engineer. The Roles page appears. From the Engineer list, select the required project. The Process page appears, similar to Figure 12. From the Select Category list, select a category from the list. The Configuration category prepares your system to run Maintenance Wizard. The other available categories depend on your set up and configuration.

Important Notes: To view the full list of categories applicable to your installation, you must complete all of the steps in the Configuration category. When you complete these steps, you must refresh the lower left pane of your Web browser by right clicking in the lower left pane and choosing Reload or Refresh from the drop down menu. The entire list of categories appears. If, after completing the configuration tasks, you still do not see the entire expected list, please refer to the Maintenance Wizard FAQ (My Oracle Support Note: 407085). This list of categories is subject to change.

About the Maintenance Wizard Interface

The following table provides a list of the icons that enable you to scan the list of tasks and steps for each category and product family to determine the status of each step.
Icon Icon Name Green Check Mark in Circle (Complete) Description Indicates that the step has been automatically executed and the user indicated that the step finished successfully Indicates that the step has never been completed or has been reported as a step requiring execution again. Indicates that the step was executed automatically but the user did not indicate the success or redo of the step. The window was closed without clicking Success or Redo. Steps that take a long time to run often display this icon. Indicates a step that was manually completed by the user. Indicates that Maintenance Wizard automatically skipped the step. The tool determined that the user does not have to perform this portion of the step. Usually the Note field

Blue Box in Circle (Incomplete)

Red X in Circle (Under Execution)

Blue Man with Check (Manually Complete) Red Circle with Slash (Auto Skipped)

Page 24

Icon

Icon Name

Description contains the reason for skipping the step. Indicates a step that is new or updated since the previous application of LivePatch.

Blue Star (New or Updated)

Actions for Each Step in the Project

Each step has a minimum of one and a maximum of three required substeps. These substeps are called Setup, Execute, and Validate. For manual steps, the text should indicate the commands that you are required to perform. However, many actions include scripts that automate the process.
Action Setup (This substep is optional) Description The Setup substep runs a process that verifies the following: If execution of that step is required If the data is ready for the Execute substep to process Specifically, it details the Oracle Applications navigation steps, additional details, objects to be checked, and criteria for checking them. The Execute substep either runs the script provided with Maintenance Wizard or it displays the navigation required to perform the step manually. Specifically, it details the action for the actual work that is required. Note: Every step must have an Execute substep. The Validate substep verifies that the step is complete and it is OK to continue with the next step. Specifically, it attempts to determine whether the Execute substep was successful and details specific objects to be checked and the criteria for checking them.

Execute (This substep is mandatory) Validate (This substep is optional)

Page 25

Executing a Step Automatically or Manually

You have the option to perform any step manually as displayed in Figure 18. Manual: Manual step execution requires you to perform the work manually. You must record the success or redo of the step upon completion. Enter the hours and minutes required to complete the step, then click Manual. The step window appears similar to Figure 17.

Figure 17 Executing a Step Manually

Page 26

Automatic: Click Run to run a provided script automatically. You must select the success or redo button for that step upon completion. Maintenance Wizard records the execution time taken for the step. In addition, each automated sub step prompts the user for an optional "additional think time" both before and after the actual step execution. This field can be used to store time for tasks such as research, data correction, and customization handling. It also appears on the Management Report. If an automatic step has already been run, the most recent log file is displayed. Note: You can always run an automatic step manually by clicking Manual.

Figure 18 Executing a Step Automatically

Note: If you want to include multiple sets of parameters, you can run the automated steps multiple times. To do this, select Redo even if it runs successfully, then run the step again with the next set of parameters. Keep selecting Redo and re-running it with the new set of parameters until each set has been included. Mark the step a success after you have run the last set of parameters. The log file for each execution is saved and available through the Audit window.

Marking the Success or Redo of Each Step

Upon the completion of each substep (Setup, Execute or Validate), you must click either Success or Redo as shown in Figure 19.

Page 27

Figure 19 Completing a Step

Depending on the choice you make, the status of the step is marked either Complete or Not Run. Success: Record the step as a success when it completes as expected. Redo: Record the step as Not Run if it does not complete at all, or if it completes with problems.

Sometimes a step takes longer to execute than the framework can wait; this is called "timing out". To refresh a step, close the Script Executer window using the X in the upper right corner, then right-click and select Refresh on the Step Action Run window periodically until the step is complete.

Maintenance Wizard Online Help

Figure 20 shows an example of the online documentation that is available within the tool:

Page 28

Figure 20 Online Help

Links to Documentation or My Oracle Support Notes: Many steps contain links to additional information in My Oracle Support. User Note: The Edit User Note button and the Notepad icon beside each step enable you to record information for each step. Use this feature to facilitate the next test or go-live project. Add your notes in the text box and click Save to exit. Click the link again to add more information. As each test is performed, this becomes another part of the documentation that customizes your project. Online Documentation: There are several links to product documentation on the left of the main screen on the Process page similar to Figure 12. Click the links to view various types of product documentation, including My Oracle Support notes and documents. Task Help: For some tasks, you can click the task name and context-sensitive information is displayed.

Viewing Log Files

Maintenance Wizard captures log files for all substeps that have been automatically executed. To view the most recent log file for a particular substep, click the status icon for that step. If the step has been run, the log file is displayed in the step status window. To view all log files for a particular substep, click the Audit icon beside that step, and then click Notebook icon in the Log column. The Audit window appears similar to Figure 21 and Figure 22 shows the contents of a log file.

Page 29

Figure 21 Audit Window

Figure 22 Log File Contents

Page 30

About Utilities

Troubleshooting Maintenance Wizard

Check Your Installation To verify your new Maintenance Wizard installation: 1. Check that the listener is running all the services by running: lsnrctl status LISTENER_yourSIDname You should see services running for XDB and XPT in addition to the regular listener as shown in Figure 23. Figure 23 Listener services

2.

If all the proper listener services are running, then you may log into the Maintenance Wizard. Enter the following URL in the Web browser: http://yourhost.yourdomain:yourport The Web browser redirects to a URL similar to the following: http://yourhost.yourdomain:yourport/pls/EOF/Eof_Http.html_frames?p_fram e_set_id=LOGIN

The Maintenance Wizard Login page appears. If the Login page does not appear, then you do not have a successful installation. To troubleshoot this issue, use the Maintenance Wizard collector script as described in the next section. Use the Collector Script to Gather Debug Information for Installation Issues The Maintenance Wizard Collector script gathers information that Oracle Support requires for debugging your installation issue. The collector script produces a ZIP file that you can upload with your TAR. To run the cant_login.sh collector script:

Page 31

Log in to the operating system of the Maintenance Wizard node as the Maintenance Wizard owner. Change directory to the $EOF_HOME/scripts/COMMON directory. Note: $EOF_HOME is set to the directory where you unzipped Maintenance Wizard.

Run the collector script (cant_login.sh) as follows: $ ./cant_login.sh The script prompts you for the following information as illustrated in Figure 24:

Figure 24 Running the Collector Script

Enter the full path to the EOF_HOME directory. Enter the user name for the Maintenance Wizard schema. Enter the password for the Maintenance Wizard schema. The collector script produces output similar to Figure 25.

Page 32

Figure 25 Collector Output

Check Your Project Configuration If you defined a project in Maintenance Wizard and cannot achieve the Configuration Complete status for a specific project, use the Maintenance Wizard Collector script to gather information about the installation and the project configuration as described in the following section. Use the Collector Script to Gather Debug Information for Project Configuration Issues The Maintenance Wizard Collector script gathers information that Oracle Support requires for debugging your project configuration issue. The collector script produces a ZIP file that you can upload with your TAR. To run the cant_config.sh collector script: Log in to the operating system of the Maintenance Wizard node as the Maintenance Wizard owner. Change directory to the $EOF_HOME/scripts/COMMON directory. Note: $EOF_HOME is set to the directory where you unzipped Maintenance Wizard. Run the collector script (cant_config.sh) as follows: $ ./cant_config.sh The script prompts you for the following information as illustrated in Figure 26.

Page 33

Figure 26 Running the Collector Script

Figure 27 Collector Output

Enter the full path to the EOF_HOME directory. Enter the user name to the Maintenance Wizard schema. Enter the password to the Maintenance Wizard schema. Enter the Instance ID for the project with which you are having issues. The collector script produces output similar to Figure 27.

Page 34

Using the OS and SQL Utilities

You can use the OS and SQL utilities integrated in Maintenance Wizard to perform various remote commands in a simple and convenient way. This saves time and effort because you do not have to open a separate tool, log in, source the correct environment files, and enter the relevant command to view a specific file or to check the results of a query. To run the OS Commands utility or SQL Query utility: 1. Log in as the Upgrade Engineer. Note: You must have the appropriate responsibility for the current project to run these utilities. For more information about granting OS Command Access and SQL Query Access, see step 5 of Step 7: Assigning Responsibilities to Users. From the Process tab, select Utilities. The Utilities page appears, similar to Figure 28. Depending on the utility that you want to use, select one of the following: Run OS Commands To run OS commands: 1. Figure 28 Run OS Commands From the Ebiz Support list, click Run OS Commands. The OS Commands utility page appears similar to Figure 36. Run OS Commands Run SQL

2.

2. 3.

In the Command field, enter the OS command that you want to run. From the Host list, select the node on which you want to run the OS command, then click Submit. The OS Command page appears similar to Figure 29.

Page 35

Figure 29 OS Commands Results

Run SQL Queries To run SQL queries: 1. From the Ebiz Support list, click Run SQLs. The SQL Query utility page appears similar to Figure 30.

Figure 30 Run SQL Query

2. 3.

In the Run SQL text field, enter the SQL query that you want to perform. For information about SQL Queries, see the example following this section. From the Flip columns list, select the format in which to view the results, then click Submit. You may also export the data to Word or Excel.

Note: For examples of how to use SQL Query, see Appendix C: Examples for Using the OS Command and SQL Query Utility.

Page 36

About Reporting
Run System or Project Administration Reports
Use the Configuration page to create system and project administration reports. To run reports: 1. 2. Figure 31 Reports Page Log in as the System or Project Administrator. The Customer Configuration page appears. Click Configuration, then click the Reports subtab. The Reports page appears, similar to Figure 31.

3.

From the Select Report list, select the report that you want to view: Note: The reports available to you depend on your role. Customer Projects: Displays the status of each project for each customer. Projects Assigned: Displays the projects assigned to the selected Upgrade Engineer. Node Configuration Details: Displays the node information and runtime configuration information for the selected project. Project Configuration Details: Displays the project level configuration information for the selected project. Responsibility Assignments: Displays the tasks assigned to each Upgrade Engineer for the selected project. Audit Trail: Displays the main events that occurred for the sleeted project. Assigned Engineers: Displays the Upgrade Engineers assigned to the selected project. Monitor Logins: Displays the number of logins to the selected project for the duration of 1 day, 2 days, a week, or the lifetime of the project. Select the duration from the No of Days list. Monitor Upgrades: Displays the progress of the upgrade for the selected project

Run Engineer Reports

Upgrade Engineers can view a List of Assigned Steps report, which displays all of the steps that are currently assigned to the engineer. Steps that appear in red indicate that the step was not marked as Success or Redo and must be addressed. To view a List of Assigned Steps report: 1. Log in as the Upgrade Engineer.
Page 37

The Roles page appears. 2. 3. 4. Figure 32 List of Assigned Steps From the Engineer list, select the required project. The Process page appears, similar to Figure 12. From the Process page, click the Reports subtab. From the Select Report list, select List of Assigned Steps. The report appears similar to Figure 32.

Page 38

Running Live Patch and Live Update

You can use Live Patch and Live Update to maintain the latest version of Maintenance Wizard as follows: Download and Run Live Patch Update Existing Projects Using LiveUpdate What to Do if the Live Update or Live Patch Fails

Download and Run Live Patch

The Maintenance Wizard Live Patch enables you to upgrade the current version of Maintenance Wizard without overwriting any configuration information previously gathered. To view LivePatch: 1. 2. Log in as the System Administrator. The Customer Configuration page appears. From the Configuration tab, click LivePatch. The LivePatch page appears. If the installation is already up-to-date, then it will appear similar to Figure 33.

Figure 33 LivePatch Page with no action required

3.

Otherwise, if a later version of LivePatch for Maintenance Wizard is available, it will automatically run the first phase of the LivePatch and download the new code. The screen will appear similar to Figure 34. If it completes successfully click Run Phase 2 of Automatic LivePatch now. For more information about LivePatch, see How to Perform a LivePatch (My Oracle Support Note 291887.1).

Note: You must run Live Update after a LivePatch to view the effects in your projects. For information about LiveUpdate, see Update Existing Projects Using LiveUpdate.

Page 39

Update Existing Projects Using LiveUpdate

Only System Administrators can update existing projects with Live Update. To update an existing project: 1. 2. Figure 34 Liveupdate Page Log in as the System Administrator. The Customer page appears. From the Configuration tab, click the LiveUpdate secondary tab. The LiveUpdate page appears similar to Figure 34.

3.

From the Project to Liveupdate list, select the project that you wish to update, then click OK. Select the source project from which you wish to update. Select the Master project unless you have a customized project that you want to replicate. Then click Liveupdate. Alternatively, click Liveupdate All to update all projects at one time.

Figure 35 LivePatch phase 2

What to Do if the Live Update or Live Patch Fails

If a Live Update or Live Patch fails, you must restore your project from the back up that you created. Contact Oracle Support for assistance when performing the restore.
Page 40

Administering Maintenance Wizard

Note: When you update an administration option, it affects all users and projects, unless overridden at a lower level. There are a number of administration tasks available to the System Administrator: Displaying icons for completed steps From the Icon for Automatically Completed Steps list, select Show symbols to enable Maintenance Wizard to display the Red Circle with Slash icon described in About the Maintenance Wizard Interface. If you do not select this option, there will be no icons under the Setup, Execute, and Validate columns on the Process tab for Automatically Completed steps. Click Save to save your options. Setting Debug From the System level DEBUG option list, select Show debugging to display debug information for all projects. Otherwise, select Hide debugging to hide the debug information. Click Save to save your options. Note: You can override this setting at the Project level. For more information, see Debug Task on page 50. Hiding Passwords in Maintenance Wizard Output From the Mask passwords in output list, select Mask passwords to hide or obfuscate passwords in the Maintenance Wizard output. Otherwise, select Show passwords to display passwords in the Maintenance Wizard output. Click Save to save your options. Note: When Maintenance Wizard hides your password, it hides all occurrences of that word. If your password is a common word, then Maintenance Wizard hides all occurrences of that word in the Maintenance Wizard output. Deleting customers from Maintenance Wizard From the Delete Customer table, beside the customer that you want to delete, click Delete. Click OK to confirm your action. Deleting projects from Maintenance Wizard From the Delete Project table, beside the project that you want to delete, click Delete. Click OK to confirm your action.

Page 41

Appendix A: Maintenance Wizard Common Tools

Traditional Approach to the Upgrade for UNIX
The traditional approach for upgrading on UNIX is to perform all upgrade steps manually using information from the Upgrading Oracle Applications Manual, Release Notes and the Upgrade Assist Worksheet. The person performing the upgrade must do the following: Browse through all applicable information manually Keep a manual log of all steps and their success or failure Perform data validation manually (without documentation assistance) Manually gather and submit all applicable log files with SRs (if necessary)

New Approach to the Upgrade for UNIX

Maintenance Wizard guides you through the Oracle Application Upgrade process. The tool presents the upgrade as a step-by-step process by consolidating all upgrade references together. It enables the validation of each step, tracks the completion of the step, and maintains a log and status. It is a multi-user tool that enables the System Administrator to give different users upgrade assignments based on any combination of category, product family, or task level. It also provides upgrade project management utilities to record the time taken for each task, completion status, and project reporting. The tool does not replace any code in the current or future Oracle code.

Improve System Performance During the Upgrade

The upgrade may require more database server resources than normal runtime usage. You can improve performance by installing the administration server on a different machine than the database server, thus allowing more CPU to participate in the upgrade.

System Preparation
Clone your system. Create an identical copy of an existing Oracle Applications system to use in the upgrade. Refer to Cloning Your System in the Oracle Applications AD Procedures Guide for details.

Merge and Apply Patches

This version of Maintenance Wizard includes a patch application tool that can download and apply patches on both the source and target project. If a step requires you to apply a patch, the tool is used in the Setup-Execute-Validate framework to perform the following: Setup The patch tool checks to see if the patch has already been applied. If the patch is already applied, then no further action is necessary. You can mark the Setup, Execute and Validate portions of this step as successfully completed. If the patch has not yet been applied, then this step downloads

Page 42

the patch and copies it to all relevant nodes for installation. It then unzips the patch and displays the readme.txt file. Read readme.txt carefully to determine if there are any manual actions that you need to perform. Maintenance Wizard checks these manual actions by running admsi.pl and then displays the results in a newly-generated readme file based on the existing system. Note: Patches are loaded in order, so all prerequisites for a patch are applied in previous steps. Errors encountered during the Setup phase are usually due to one of the following: o o An invalid My Oracle Support User ID or Password in the configuration of Maintenance Wizard. An obsolete or deleted patch number

If this occurs, log in to My Oracle Support and download the patch manually. Execute The patch tool applies the patch to all appropriate nodes. Review the log file for this step carefully to ensure that the patch applied without errors. If there are errors in the log file and the cause of the errors can be corrected, restart the patch application as follows: 1. From the Process tab, click the Utilities subtab. The Utilities page appears similar to Figure 36.

Figure 36 Utilities Page

2. 3.

Select Step 2-Apply a patch. When prompted, select YES to Restart a failed patch application?

Note: You can also choose to have the DBA manually reapply the patch using the adpatch utility. When this is complete, mark the Execute step as manually completed, and proceed to the Validate step. Validate The patch tool verifies that the patch was successfully applied. If the log file shows the patch was not successfully applied, then have the DBA manually reapply this patch using the adpatch utility. When this is complete, repeat this Validate step. Do not proceed to the next step until the script shows that the patch has been successfully applied.

Page 43

Merge Patches
The tools also include a patch merge utility. Merging makes it easier to apply the large number of patches required by Maintenance Wizard, because it considers prerequisites and applies the patches in the correct order. It also saves time by eliminating duplicate jobs that would normally run once per individual patch, but now run only once per merged patch. Often, multiple patches required for the upgrade are dynamically grouped into merged patches, then each merged patch is applied. This capability reduces the time required to apply the patches.

About the Utilities Category

The Utilities Category contains a collection of steps that you can use to perform activities such as applying a patch, recompiling invalid objects, and starting or stopping a service. You are not required to use this category to perform the upgrade. However, these steps are provided to assist you in special cases where you need to perform a general command that is not specifically listed in the Upgrade manual. The Utilities Category steps are divided into four types: Patching Administer Services View Information MW Tool

About Patching Tasks

The Patching Steps are divided between two tasks: Patching for all Releases Task Additional Utilities for Rel 11i and 12 Only Task.

Patching for all Releases Task Use the steps under this task to download, apply, and verify a patch on either the source or target project. These steps prompt you for necessary parameters and then perform the patch function. There is also a step to recompile invalid objects. The individual steps are as follows: STEP 1 - Download a patch This step performs one of the following: o Verifies that the patch has been downloaded to the Maintenance Wizard Main node and has been copied to the specified target node(s), Downloads the patch to the Maintenance Wizard node and copies it to the specified target node(s). If successful, it displays the readme.txt file. Then Maintenance Wizard runs the Manual Step Infrastructure script (admsi.pl) to generate the final readme after checking for any completed manual steps. Parameters are: Release to apply patch to? (10.7, 11, 11i, 12) Patch Number Force the patch to download even if it is already applied?

Page 44

(Yes/No) For 10.7 patches only, is this an NCA patch? (Yes/No/Not Applicable) Note: You must choose Not Applicable if the patch is not for release 10.7. Debug

STEP 2 - Apply a patch This step applies a patch that has already been downloaded. It includes a Parameter to restart a failed patch. Parameters are as follows: Release to apply patch to? (10.7, 11, 11i. 12) Patch Number Force the patch to install? (Yes/No) For 10.7 patches only, is this an NCA patch? (Yes/No/Not Applicable) Note: You must choose Not Applicable if the patch is not for release 10.7. Restart a failed patch application? (Yes/No) Number of workers? (default is 3) Apply in preinstall mode? (Yes/No) Enter driver filename or all. (default is all) Turn debug mode on? (Yes/No)

STEP 3 - Verify patch application This step verifies the application of a patch. Parameters are as follows: Release to apply patch to? (10.7, 11, 11i, 12) Patch Number On which node would you like to check for application? (Applications node, Forms node, Concurrent manager node, Web node) Turn debug mode on? (Yes/No)

Additional Utilities for Rel 11i and 12 Only Task The step under this task enables you to merge and apply more than one patch. This utility is used in the Post-MP Patching to apply all the patches needed to the 11i or 12 project after the data has been migrated. It is available from the Utilities Category if you need to apply multiple patches to the 11i and 12 projects. STEP 1 - AD Merge Patch and Apply

This step applies a merged patch, which was downloaded and unzipped on the remote tiers through the setup step. Parameter is: What release are the patches for? (11i/12)

STEP 2 Alter Maintenance Mode

This step alters the maintenance mode setting. You must provide the required parameters to indicate the version of the Applications and to enable or disable the maintenance mode setting. Parameters are: For which release do you wish to change Maintenance Mode? (11i, 12) Turn Maintenance Mode on or off (On, Off)

Page 45

STEP 3 Reset incomplete patching attempt

This step resets an incomplete or failed patching attempt. Parameter is: For which release do you wish to reset an incomplete patching attempt? (11i, 12)

STEP 4 Control adworker

This step performs a single action using adctrl. Parameters are as follows: For what release do you wish to control the adworker? (11i, 12) Which action do you wish to perform? (Show worker status, Tell worker to restart a failed job, Tell worker to quit, Tell manager that a worker failed its job, Tell manager that a worker acknowledges quit, Restart a worker on the current machine, Tell worker to skip the current job (only with Support approval) Which worker do you wish to perform the action on? (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, all)

STEP 5 Perform adadmin action

This step performs a single action using adadmin. Parameters are as follows: For which release do you want to run adadmin? (11i, 12) Which action do you wish to perform? (Relink Applications programs, Generate message files, and so on) How many workers do you wish to use?

About Administer Services

The group of steps under the task Administer services for Rel 11i and Rel 12 enables you to perform basic service functions. Administer Services for Rel 11i This group of steps allows you to perform basic operations on the services. STEP 1 - Administer the Apache listener for Rel 11i This step either stops or starts the Apache service automatically. You must provide one parameter that starts, stops, bounces (stops and restarts), or gets the status of the service. If you choose either the start or bounce option, it also clears the cache before starting Apache. Parameter is as follows: What action do you want to do to Apache? (Show Status, Start, Bounce, Stop)

STEP 2 - Administer the forms listener for Rel 11i This step administers the forms listener automatically. You must provide one parameter, which starts, stops or shows the status of the service. Parameter is: What action do you want to do to the forms listener? (Show Status, Start, Stop)

STEP 3 - Administer the reports listener for Rel 11i This step administers the reports listener automatically. You must provide one parameter, which starts, stops or shows the status of the services. Parameter is:

Page 46

What action do you want to do to the reports listener? (Show Status, Start, Stop)

STEP 4 - Administer the concurrent manager for Rel 11i This step administers the concurrent manager automatically. You must provide one parameter, which starts, stops or shows the status of the service. Parameter is: What action do you want to do to the concurrent manager? (Show Status, Start, Stop)

STEP 5 - Administer the applications listener for Rel 11i This step administers the applications listener automatically. You must provide one parameter, which starts, stops, or shows the status of the service. Parameter is: What action do you want to do to the concurrent manager? (Show Status, Start, Stop)

STEP 6 - Administer all applications services for Rel 11i This step stops or starts all of the Release 11i services automatically. You must provide one start or stop parameter. Parameter is as follows: What action do you want to do to all of the applications services? (Start, Stop)

STEP 7 - Administer the database for Rel 11i This step either stops or starts the database automatically. You must provide two parameters. The first tells it whether to start or stop the service. If you choose to stop the database, then you must also specify whether to shutdown in normal, immediate or abort mode. If you do not specify a shutdown mode, it uses normal mode. Parameters are: What action do you want to do to the database? (Start, Stop) If shutting down, which mode do you want to use? (Normal, Immediate, Abort)

STEP 8 - Administer the database listener for Rel 11i This step stops or starts the database listener automatically. You must provide one parameter to start, stop, or show the status of the service. Parameter is: What action do you want to do to the database listener? (Show status, Start, Stop)

Administer Services for Rel 12 This group of steps allows you to perform basic operations on the services. STEP 1 - Administer the Oracle HTTP Server (OHS) for Rel 12 This step either stops or starts the Apache service automatically. You must provide a parameter to start, stop, bounce, or get the status of the Apache service. Parameter is as follows: What action do you want to do to Apache (Show status, Start, Bounce, Stop)

STEP 2 Administer the forms listener for Rel 12 This step administers the forms listener automatically. You must provide

Page 47

one parameter that starts, stops, or gets the status of the service. Parameter is as follows: What action do you want to do to the forms listener? (Show status, Start, Stop)

STEP 3- Administer the OACORE OC4J for Rel 12 This step administers the OACORE OC4J automatically. You must provide one parameter that starts, stops, or gets the status of the service. Parameter is as follows: What action do you want to do to the OACORE OC4J? (Show status, Start, Stop)

STEP 4 Administer the OAFM OC4J for Rel 12 This step administers the OAFM OC4J automatically. You must provide one parameter that starts, stops, or gets the status of the service. Parameter is as follows: What action do you want to do to the OAFM OC4J? (Show status, Start, Stop)

STEP 5 Administer the Fulfillment Server for Rel 12 This step administers the Fulfillment server automatically. You must provide one parameter that starts or stops the service. Parameter is as follows: What action do you want to do to the Fulfillment server? (Start, Stop)

STEP 6 Administer the concurrent manager for Rel 12 This step administers the concurrent manager automatically. You must provide one parameter, which starts, stops or shows the status of the service. Parameter is as follows: What action do you want to do to the concurrent manager? (Show Status, Start, Stop, Abort)

STEP 7 Administer the applications listener Rel 12 This step administers the applications listener automatically. You must provide one parameter, which starts, stops, or shows the status of the service. Parameter is as follows: What action do you want to do to the applications listener? (Show status, Start, Stop)

STEP 8 Administer all applications services for Rel 12 This step stops or starts all of the Release 12 Applications services automatically. You must provide one start or stop parameter. Parameter is as follows: What action do you want to do to all of the applications services? (Start, Stop)

STEP 9 Administer the database for Rel 12 This step either stops or starts the database automatically. You must provide two parameters. The first determines whether to start or stop the service. If you choose to stop the database, then you must also specify whether to shutdown in normal, immediate, or abort mode. If you do not specify a shutdown mode, Maintenance Wizard uses normal mode. Parameters are as follows:

Page 48

What action do you want to do to the database? (Start, Stop) If shutting down, which mode do you want to use? (Normal, Immediate, Abort)

STEP 10 Administer the database listener for Rel 12 This step stops or starts the database listener automatically. You must provide one parameter to start, stop, or show the status of the service. Parameter is as follows: What action do you want to do to the database listener? (Show status, Start, Stop)

About View Information

This group of steps enables you to view concurrent request and logs files. Concurrent Request These steps enable you to view the concurrent request output and logs: STEP 1 - View concurrent request output file This utility shows you the concurrent request output file for a concurrent job. You must enter the concurrent request ID as a parameter, as well as the version of the Applications to which the job was submitted Note: If a concurrent request was submitted before running Auto Upgrade, you should choose the release from which you are upgrading. If a concurrent request was submitted after running Auto Upgrade, then you should choose 12 as your release. Parameters are as follows: What release is the concurrent request for? (10.7, 11, 11i, 12) Concurrent Request ID?

STEP 2 - View concurrent request log file This utility shows you the concurrent request log file for a concurrent job. You must enter the concurrent request ID as a parameter, as well as the version of the Applications to which the job was submitted. Note: If a concurrent request was submitted before running Auto Upgrade, you should choose the release from which you are upgrading. If a concurrent request was submitted after running Auto Upgrade, then you should choose 12 as your release. Parameters are as follows: What release is the concurrent request for? (10.7, 11, 11i, 12). Concurrent Request ID?

Log Files These steps enable you to view the patch and worker logs: STEP 1 - View patch application log file This utility displays a patch application log file. It requires two parameters: the patch number and the node location of the log file. This utility does not work for 10.7 Smart Client patches. Parameters are as follows:

Page 49

What release is this patch for? (10.7, 11.0, 11i, 12) Enter the patch number Node to view the log for? (Applications node, Forms node, Concurrent Manager node, Apache node)

STEP 2 - View a worker log file This utility displays a worker log file. It requires four parameters: the worker number, the node on which you were running the AD utility, the amount of the file you wish to have displayed, and whether the worker is a pre-upgrade or post-upgrade worker. Parameters are as follows: What release is the patch for? (10.7, 11.0, 11i, 12) Enter the worker number Which node was running the AD utility? (Applications node, Forms node, Concurrent Manager node, Apache node) How much of the file do you wish to see? (50 lines, 100 lines, 500 lines, 1000 lines, Entire file not recommended)

Database Queries This step enables you to view database parameter values: STEP 1 - View database parameter value (Optional)

About MW Tool
Debug Task This step assists with debugging: STEP 1: Alter debug mode in MW This step toggles the debug flag for the current project only. This setting overrides the system level debug setting. When set to Yes, additional diagnostic messages are recorded in the log during execution. Parameter is as follows: Use debugging? (No, Yes)

Page 50

MW Setup Task These steps assist with setting up Maintenance Wizard: STEP 1: Change password for EOFUSER This step changes the password for the database user EOFUSER and for all the associated configuration files that require updating. It restarts Oracle Process Management and Notification (OPMN) for the new data to take effect. Parameters are as follows: Provide the current password for the EOFUSER Provide the new desired password for EOFUSER

Note: Maintenance Wizard does not display the password when you enter it on the page. STEP 2: Change number of workers for AD utilities This step changes the default number of workers used when AD utilities are called. Any value provided at the step execution time will override this value. Parameters are as follows: Shows you the current value for this option Provide how many workers you wish to use

STEP 3: Change the HTTP Proxy server information This step changes the hostname and/or port number used for your HTTP Proxy Server. Parameters are as follows: Shows you the current value for the host Shows you the current value for the port number Provide the new value for the host Provide the new value for the port number

STEP 4: Change My Oracle Support password This step changes the password used when connecting to My Oracle Support. Parameters are as follows: Provide the previously stored MOS password Provide the new MOS password

Page 51

Appendix B: Product Specific Information for Maintenance Wizard

Note to 10.7 Customers
When you create your upgrade project, you specify that your source version is 10.7. However, the tool does not ask at that point whether you are using Network Computing Architecture (NCA), SmartClient (SC) or character. You are not prompted for this information until after you have completed project definition and are actually in the Configuration category of the tool. As a result, when you begin node definition, you are prompted for the following values, which are only applicable to NCA customers: Release 10.7 NCA $APPL_TOP path Release 10.7 NCA patch directory path Release 10.7 NCA ORAWEB_HOME path Release 10.7 NCA forms port number Release 10.7 NCA (OWS) listener name

If you are an NCA customer, fill in the appropriate values. If you are not an NCA customer, you may enter any non-null value (such as X) into these fields, because they will not be used once you specify your 10.7 type.

Variables to Use for Customization

#Start of a Local Instance File PRODUCT_ID INSTANCE_ID REMOTE_EOF_HOME EOF_SCRIPTS EOF_HTML EOF_LOG EOF_CONFIG EOF_CUSTOM EOFUSER EOFPASSWORD TNS_ADMIN HOME LD_LIBRARY_PATH APPLSYSUSER APPLSYSPASSWORD APPSUSER APPSPASSWORD SYSTEMUSER SYSTEMPASSWORD
Page 52

#Product ID #Project ID #Directory created under remote Hosts #Directory where scripts are located #Directory containing Product specific HTML file #Log Directory for the project #Config Directory for the project #Directory for customized scripts #User on the local Maintenance Wizard database #Password for the EOF_USER

#$EOF_HOME/config #The LD_LIBRARY_PATH on the remote node

# 11i Admin Node Remote Node environment variables REMOTE115_APP_PATCH_TOP REMOTE115_APP_HOME REMOTE115_APP_DB_HOME REMOTE115_APP_NODE REMOTE115_APP_USER REMOTE115_APP_PLATFORM REMOTE115_APP_ENV_FILE REMOTE115_APP_CONTEXT REMOTE115_APP REMOTE115_APP_SHELL_TYPE #Directory to download patches #APPL_TOP #Apps Tools ORACLE_HOME #Machine #User #Platform #Applications environment filename #AutoConfig context name #Remote Agent #Either RSH or SSH

REMOTE115_APP_CONTEXT_LOC #Location of AutoConfig file REMOTE115_APP_FTPEXE REMOTE115_APP_CPEXE REMOTE115_APP_SHEXE REMOTE115_CM_PATCH_TOP REMOTE115_CM_HOME REMOTE115_CM_DB_HOME REMOTE115_CM_NODE REMOTE115_CM_USER REMOTE115_CM_PLATFORM REMOTE115_CM_ENV_FILE REMOTE115_CM_CONTEXT REMOTE115_CM REMOTE115_CM_SHELL_TYPE REMOTE115_CM_FTPEXE REMOTE115_CM_CPEXE REMOTE115_CM_SHEXE REMOTE115_FRM_PATCH_TOP REMOTE115_FRM_HOME REMOTE115_FRM_DB_HOME REMOTE115_FRM_NODE REMOTE115_FRM_USER #User REMOTE115_FRM_PLATFORM REMOTE115_FRM_ENV_FILE #Platform #Applications environment filename #Either ftp or sftp #Either rcp or scp #Either rsh, remsh, or ssh #Directory to download patches #APPL_TOP #Apps Tools ORACLE_HOME #Machine #User #Platform #Applications environment filename #AutoConfig context name #Remote Agent #Either RSH or SSH #Either ftp or sftp #Either rcp or scp #Either rsh, remsh, or ssh #Directory to download patches #APPL_TOP #Apps Tools ORACLE_HOME #Machine

# 11i Concurrent Manager Node Remote Node environment variables

REMOTE115_CM_CONTEXT_LOC #Location of AutoConfig file

# 11i Forms Node Remote Node environment variables

Page 53

REMOTE115_FRM_CONTEXT REMOTE115_FRM REMOTE115_FRM_SHELL_TYPE REMOTE115_FRM_FTPEXE REMOTE115_FRM_CPEXE REMOTE115_FRM_SHEXE REMOTE115_WEB_PATCH_TOP REMOTE115_WEB_HOME REMOTE115_WEB_NODE REMOTE115_WEB_USER REMOTE115_WEB_PASSWORD REMOTE115_WEB_PLATFORM REMOTE115_WEB_ENV_FILE REMOTE115_WEB_IAS_HOME REMOTE115_WEB_CONTEXT REMOTE115_WEB REMOTE115_WEB_SHELL_TYPE REMOTE115_WEB_FTPEXE REMOTE115_WEB_CPEXE REMOTE115_WEB_SHEXE

#AutoConfig context name #Remote Agent #Either RSH or SSH #Either ftp or sftp #Either rcp or scp #Either rsh, remsh, or ssh #Directory to download patches #APPL_TOP #Machine #User #Password #Platform #Applications environment filename #WEB iAS Home #AutoConfig context name #Remote Agent #Either RSH or SSH #Either ftp or sftp #Either rcp or scp #Either rsh, remsh, or ssh

REMOTE115_FRM_CONTEXT_LOC #Location of AutoConfig file

# 11i Web Node Remote Node environment variables

REMOTE115_WEB_CONTEXT_LOC #Location of AutoConfig file

# DB Remote Node variables for Upgrade Assistant and Maintenance Pack Assistant products REMOTE115_DB_VERSION REMOTE115_DB_ENV_FILE REMOTE115_DB_USER REMOTE115_DB_HOME REMOTE115_DB_SID REMOTE115_DB_PATCH_TOP REMOTE115_DB_PORT_NUM REMOTE115_DB_NODE REMOTE115_DB_PLATFORM REMOTE115_DB_CONTEXT REMOTE115_DB REMOTE115_DB_SHELL_TYPE #Database Version #Database environment filename #User #RDBMS ORACLE_HOME #Database SID name #Directory to download patches #Database port number #Machine #Platform #AutoConfig context name #Remote Agent #Either RSH or SSH

REMOTE115_DB_CONTEXT_LOC #Location of AutoConfig file

Page 54

REMOTE115_DB_FTPEXE REMOTE115_DB_CPEXE REMOTE115_DB_SHEXE REMOTEPOST_DB_USER REMOTEPOST_DB_HOME REMOTEPOST_DB_SID REMOTEPOST_DB_PATCH_TOP REMOTEPOST_DB_PORT_NUM REMOTEPOST_DB_LISTENER REMOTEPOST_DB_NODE REMOTEPOST_DB_PLATFORM REMOTEPOST_DB_ENV_FILE REMOTEPOST_DB_CONTEXT REMOTEPOST_DB_SHELL_TYPE REMOTEPOST_DB REMOTEPOST_DB_SHEXE REMOTEPOST_DB_FTPEXE REMOTEPOST_DB_CPEXE REMOTEPRE_DB_CONTEXT REMOTEPRE_DB_ENV_FILE REMOTEPRE_DB_USER REMOTEPRE_DB_HOME REMOTEPRE_DB_SID REMOTEPRE_DB_PORT_NUM REMOTEPRE_DB_LISTENER REMOTEPRE_DB_NODE #Machine REMOTEPRE_DB_PLATFORM REMOTEPRE_DB_SHELL_TYPE REMOTEPRE_DB REMOTEPRE_DB_SHELL_EXE REMOTEPRE_DB_SHEXE REMOTEPRE_DB_FTPEXE REMOTEPRE_DB_CPEXE REMOTE12_APP REMOTE12_APP_CONTEXT REMOTE12_APP_CPEXE

#Either ftp or sftp #Either rcp or scp #Either rsh, remsh, or ssh #User #RDBMS ORACLE_HOME #Database SID name #Directory to download patches #Database port number #Database listener name #Machine #Platform #Database environment file #AutoConfig context name #SSH or RSH #Remote agent #rsh, remsh, or ssh #ftp or sftp #rcp or scp #AutoConfig context name #Database environment file #User #RDBMS ORACLE_HOME #Database SID name #Database port number #Database listener name #Platform #RSH or SSH #Remote agent #rsh, remsh, or ssh #rsh, remsh, or ssh #ftp or sftp #rcp or scp #Remote Agent #AutoConfig context name #rcp or scp

# DB Node variables for Database Upgrade Assistant products

# 12 Admin Node Remote Node environment variables

Page 55

REMOTE12_APP_DB_HOME REMOTE12_APP_FTPEXE REMOTE12_APP_HOME REMOTE12_APP_NODE REMOTE12_APP_PATCH_TOP REMOTE12_APP_PLATFORM REMOTE12_APP_SHELL_TYPE REMOTE12_APP_SHEXE REMOTE12_APP_USER REMOTE12_APP_ENV_FILE

#Apps Tools ORACLE_HOME #ftp or sftp #APPL_TOP #Machine #Directory to download patches #Platform #SSH or RSH #rsh or ssh #User #Applications environment file

REMOTE12_APP_CONTEXT_LOC #Location of AutoConfig file # 12 Concurrent Manager Node Remote Node environment variables REMOTE12_CM REMOTE12_CM_CONTEXT REMOTE12_CM_CPEXE REMOTE12_CM_DB_HOME REMOTE12_CM_FTPEXE REMOTE12_CM_HOME REMOTE12_CM_NODE REMOTE12_CM_PATCH_TOP REMOTE12_CM_PLATFORM REMOTE12_CM_SHELL_TYPE REMOTE12_CM_SHEXE REMOTE12_CM_USER REMOTE12_CM_ENV_FILE REMOTE12_CM_CONTEXT_LOC REMOTE12_FRM REMOTE12_FRM_CONTEXT REMOTE12_FRM_CPEXE REMOTE12_FRM_DB_HOME REMOTE12_FRM_FTPEXE REMOTE12_FRM_HOME REMOTE12_FRM_NODE REMOTE12_FRM_PATCH_TOP REMOTE12_FRM_PLATFORM REMOTE12_FRM_SHELL_TYPE REMOTE12_FRM_SHEXE #Remote agent #AutoConfig context name #rcp or scp #Apps Tools ORACLE_HOME #ftp or sftp #CM_HOME #Machine #Directory to download patches #Platform #SSH or RSH #rsh or ssh #User #Applications environment file #Location of AutoConfig file # Remote agent #AutoConfig context name #rcp or scp #Apps Tools ORACLE_HOME # ftp or sftp #APPL_TOP #Machine #Directory to download patches #Platform #SSH or RSH #rsh or ssh

# 12 Forms Node Remote Node environment variables

Page 56

REMOTE12_FRM_USER REMOTE12_FRM_ENV_FILE

#User #Applications environment file

REMOTE12_FRM_CONTEXT_LOC #Location of AutoConfig file # 12 Web Node Remote Node environment variables REMOTE12_WEB REMOTE12_WEB_CONTEXT REMOTE12_WEB_CPEXE REMOTE12_WEB_FTPEXE REMOTE12_WEB_HOME REMOTE12_WEB_IAS_HOME REMOTE12_WEB_NODE REMOTE12_WEB_PATCH_TOP REMOTE12_WEB_PLATFORM REMOTE12_WEB_SHELL_TYPE REMOTE12_WEB_SHEXE REMOTE12_WEB_USER REMOTE12_WEB_ENV_FILE #Remote agent #AutoConfig context name #rcp or scp #ftp or sftp #APPL_TOP #WEB iAS Home #Machine #Directory to download patches #Platform #SSH or RSH #rsh or ssh #User #Applications environment file

REMOTE12_WEB_CONTEXT_LOC #Location of AutoConfig file # Pre-upgrade variables for 10.7 Administration nodes REMOTE_APP_PATCH_TOP REMOTE_APP_HOME REMOTE_APP_DB_HOME REMOTE_APP_NODE REMOTE_APP_USER REMOTE_APP_PLATFORM REMOTE_APP_ENV_FILE REMOTE_APP_SHELL_TYPE REMOTE_APP REMOTE_APP_SHEXE REMOTE_APP_FTPEXE REMOTE_APP_CPEXE REMOTE_FRM_PATCH_TOP REMOTE_FRM_HOME REMOTE_FRM_DB_HOME REMOTE_FRM_NODE REMOTE_FRM_USER REMOTE_FRM_PLATFORM #Directory to download patches #APPL_TOP #Applications Tools ORACLE_HOME #Machine #User #Platform #Applications environment filename #SSH or RSH #Remote Agent #rsh, remsh or ssh #ftp or sftp #rcp or scp #Directory to download patches #APPL_TOP #Applications Tools ORACLE_HOME #Machine #User #Platform

# Pre-upgrade variables for 10.7 Forms nodes

Page 57

REMOTE_FRM_ENV_FILE REMOTE_FRM_SHELL_TYPE REMOTE_FRM REMOTE_FRM_SHEXE REMOTE_FRM_FTPEXE REMOTE_FRM_CPEXE REMOTE_FRM_ORAWEB_SITE REMOTE_FRM_FORMS_PORT REMOTE_CM_PATCH_TOP REMOTE_CM_HOME REMOTE_CM_DB_HOME REMOTE_CM_NODE REMOTE_CM_USER REMOTE_CM_PLATFORM REMOTE_CM_ENV_FILE REMOTE_CM_SHELL_TYPE REMOTE_CM REMOTE_CM_SHEXE REMOTE_CM_FTPEXE REMOTE_CM_CPEXE REMOTE_WEB_PATCH_TOP REMOTE_WEB_HOME REMOTE_WEB_DB_HOME REMOTE_WEB_NODE REMOTE_WEB_USER REMOTE_WEB_PLATFORM REMOTE_WEB_ENV_FILE REMOTE_WEB_SHELL_TYPE REMOTE_WEB REMOTE_WEB_SHEXE REMOTE_WEB_FTPEXE REMOTE_WEB_CPEXE REMOTE_WEB_ORAWEB_SITE

#Applications environment filename #SSH or RSH #Remote Agent #rsh, remsh or ssh #ftp or sftp #rcp or scp #OWS listener name #Forms port #Directory to download patches #APPL_TOP #Applications Tools ORACLE_HOME #Machine #User #Platform #Applications environment filename #SSH or RSH #Remote Agent #rsh, remsh or ssh #ftp or sftp #rcp or scp #Directory to download patches #APPL_TOP #Applications Tools ORACLE_HOME #Machine #User #Platform #Applications environment filename #SSH or RSH #Remote Agent #rsh, remsh or ssh #ftp or sftp #rcp or scp #OWS listener name

REMOTE_FRM_ORAWEB_HOME #OWS $ORAWEB_HOME path

# Pre-upgrade variables for 10.7 Concurrent Manager nodes

# Pre-upgrade variables for 11.03 WEB nodes

REMOTE_WEB_ORAWEB_HOME #OWS $ORAWEB_HOME path # Pre-upgrade variables for 11.03 Forms nodes

Page 58

REMOTE_FRM_PATCH_TOP REMOTE_FRM_HOME REMOTE_FRM_DB_HOME REMOTE_FRM_NODE REMOTE_FRM_USER REMOTE_FRM_PLATFORM REMOTE_FRM_ENV_FILE REMOTE_FRM_SHELL_TYPE REMOTE_FRM REMOTE_FRM_SHEXE REMOTE_FRM_FTPEXE REMOTE_FRM_CPEXE REMOTE_FRM_FORMS_PORT REMOTE_CM_PATCH_TOP REMOTE_CM_HOME REMOTE_CM_DB_HOME REMOTE_CM_NODE REMOTE_CM_USER REMOTE_CM_PLATFORM REMOTE_CM_ENV_FILE REMOTE_CM_SHELL_TYPE REMOTE_CM REMOTE_CM_SHEXE REMOTE_CM_FTPEXE REMOTE_CM_CPEXE

#Directory to download patches #APPL_TOP #Applications Tools ORACLE_HOME #Machine #User #Platform #Applications environment filename #SSH or RSH #Remote Agent #rsh, remsh or ssh #ftp or sftp #rcp or scp #forms port #Directory to download patches #APPL_TOP #Applications Tools ORACLE_HOME #Machine #User #Platform #Applications environment filename #SSH or RSH #Remote Agent #rsh, remsh or ssh #ftp or sftp #rcp or scp

# Pre-upgrade variables for 11.03 Concurrent Manager nodes

Page 59

Appendix C: Examples for Using the OS Command and SQL Query Utility
Applications patching provides an example of when and how to use the OS and SQL utilities. This appendix provides these examples as a guide to patching. For a detailed tutorial on patching see Oracle Applications Maintenance Utilities Release 12(Part No. B31568-01) and Oracle Applications Patching Procedures Release 12 (Part No. B31567-01) from the Oracle Applications Documentation Web site. A manager assigns each worker a unique ID and inserts a row for each worker in the FND_INSTALL_PROCESSES table. The manager creates this table to serve as a staging area for job information, and as a way to communicate with the worker. Communication is accomplished using two columns: CONTROL_CODE and STATUS. The manager updates the table with a subset of the list of jobs, one job per worker. For example, if there are five workers, then the table holds five jobs (even though there may be 100 or more jobs involved in the complete action). The manager starts the workers and uses the CONTROL_CODE and STATUS columns to assign tasks. It polls these two columns continuously, looking for updates from the workers. As a worker finishes their assignment, the manager updates each row with the next task in the list, and leaves another message for the worker. The above information can be helpful during the execution of a long patch or in trying to diagnose a patch that has failed or is stuck. The following are a number of useful SQL examples for the above example:
select CONTROL_CODE, STATUS from fnd_install_processes@REMOTE

select patch_name, patch_type, creation_date from ad_applied_patches@REMOTE order by creation_date desc

select fa.application_short_name, fpi.STATUS, fpi.PATCH_LEVEL from fnd_product_installations@REMOTE fpi, fnd_application@REMOTE fa

where fpi.application_id = fa.application_id order by 1

Page 60

Worker Log Files

In addition to the information recorded in the utility name.log file, utilities that process jobs in parallel write details about errors to worker log files. The adworknumber.log files (adwork001.log, adwork002.log, and so on) reside in the $APPL_ TOP/admin/SID/log directory, where SID is the value of the ORACLE_SID or TWO_TASK variable (UNIX). Typical useful OS examples are as follows:
tail -100 $APPL_TOP/admin/$TWO_TASK/log/adwork001.log ls lrt $APPL_TOP/admin/$TWO_TASK/log/ tail -100 $APPL_TOP/admin/$TWO_TASK/log/adwork001.log adrelink.log grep i error $APPL_TOP/admin/$TWO_TASK/log/adwork001.log $ORACLE_HOME/bin/tnsping $TWO_TASK

By default, adpatch names the log files adpatch.log but the Maintenance Wizard standard is to have one log file for each patch and indicate that it was a patch executed by Maintenance Wizard. Maintenance Wizard uses the following format to names log files:
$APPL_TOP/admin/$TWO_TASK/{BugNumber_adpatch.log}

or
$APPL_TOP/admin/R12_DIAG/log/5362928_patchit12.log

Maintenance Wizard runs the patches in non-interactive mode. For this to work, the defaults file must be setup in the $APPL_TOP/admin/$TWO_TASK/ directory. The defaults file is named adalldefaults.txt by default. If it is not present, Maintenance Wizard creates the file automatically by running autoconfig or by running adpatch to recreate it. For more information, see Oracle Applications Patching Procedures Release 12 (Part No. B31567-01) from the Oracle Applications Documentation Web site. The following non-patching related commands may also be useful:
ps ef | grep pmon ps ef |grep lsnr tnsping $TWO_TASK ls l $APPL_TOP/admin

Page 61