| Oracle® Fusion Applications Patching Guide 11g Release 1 (11.1.4) Part Number E16602-15 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Applications Patching Guide 11g Release 1 (11.1.4) Part Number E16602-15 |
|
|
PDF · Mobi · ePub |
This chapter describes the process of running Oracle Fusion Applications utilities to perform routine system maintenance tasks.
This chapter contains the following topics:
AD Administration is a standalone utility that performs administration maintenance tasks for the products in your Oracle Fusion Applications Oracle home and your Applications Core Oracle home. The general purpose of the maintenance tasks is to keep your Oracle Fusion Applications files and database objects up-to-date. Some maintenance tasks should be performed systemwide on a regular basis, while others are required infrequently.
Run AD Administration by using the command-line utility, adadmin. This utility has a wrapper script that sets the environment and calls the utility. For UNIX, the wrapper is adadmin.sh and for Windows it is adadmin.cmd. This brings you to the AD Administration main menu, where you select from a list of submenus that contain these task groups:
Maintain Snapshot Information
Maintain Applications Database Entities
After the utility starts, it requires that you enter system information by responding to a series of prompts.
The AD Administration main menu is the gateway to submenus, where you select the individual maintenance tasks. For example, selecting Maintain Snapshot Information takes you to the Maintain Snapshot Information submenu, where you can run tasks related to snapshots of the application-related files of a given Oracle home.
To select a submenu, enter the number of the submenu at the prompt.
You may want to add arguments to the adadmin command to customize its operations. For example, you can add defaultsfile=defaultsfile_location to indicate that you want to create a defaults file for use in running maintenance tasks noninteractively, without the need to respond to prompts. For more information, see Section 10.4, "Running Maintenance Tasks Noninteractively".
When you run AD Administration, it prompts for information about your system. Prompts typically include a description of the information needed, and usually, a default answer is enclosed in brackets. Enter a response to the prompt, or press Enter to accept the default. AD Administration prompts include:
Confirmation of your Oracle home location
Log file name
Batch size
Confirmation of the correct database
Some submenu options may trigger additional system prompts associated with that task.
For increased security, the adadmin command does not prompt for passwords, nor does the program store passwords in clear text or obfuscated format in the restart or defaults file. Instead, it uses the Credential Store Framework (CSF) to store and retrieve passwords from the CSF wallet. For more information, see Section 2.4, "Oracle Fusion Applications Patching and the Security Model".
Follow these steps to start the AD Administration utility:
From any directory, start AD Administration with this command, adding any arguments that apply to this session:
(UNIX) FA_ORACLE_HOME/lcm/ad/bin/adadmin.sh [argument]
(Windows) FA_ORACLE_HOME\lcm\ad\bin\adadmin.cmd [argument]
AD Administration starts and displays the first prompt.
Respond to each prompt by either entering a value or pressing Enter to accept the default value. When you have responded to all of the prompts, the AD Administration main menu appears.
Select a menu or submenu option by entering its number in the brackets at the bottom of the screen.
From the next menu, select any task by entering its number.
You can exit AD Administration from any submenu screen by entering the option number for Exit AD Administration.
A snapshot represents each unique combination of Oracle home, product, and version at any given point of time. It includes information on each file maintained by Oracle Fusion Applications AutoPatch and a summary of database patches that have been applied to that Oracle home. The information maintained for each file includes the subdirectory where it is located, the name of the file and its version, and the file metadata. The files tracked in the snapshot are those files located in the following product family subdirectories: components, db, and patch. Because snapshots track only files for which there can be different versions as shipped by Oracle, they do not track C executable files or log files.
Each time you run Oracle Fusion Applications Patch Manager or Oracle Fusion Applications AutoPatch, the snapshot is updated to include any new file copied to the Oracle home. When you apply a patch, Oracle Fusion Applications Patch Manager performs version-checking against the file to determine which files must be replaced.
The snapshot can be either a current view or a named view.
Current View Snapshot
A current view snapshot is a copy of the current file system of the Oracle home. Oracle Fusion Applications Patch Manager creates the current view. The current view is then updated every time a patch is applied and every time the Update Current View Snapshot process runs to maintain a consistent view. Oracle Fusion Applications Patch Manager uses the current view snapshot to determine if all prerequisite patches have been applied to the Oracle home.
For more information, see Section 10.2.1.2, "Update Current View Snapshot".
Named View Snapshot
A named view snapshot is a copy of the current view snapshot that you create at a particular time and it is never updated. You can compare one or more named view snapshots to the current view snapshot or refer to previous states of your Oracle home, as needed. Complete file, file version information, and patch history is stored in a named view snapshot.
Properly maintained snapshots allow you to:
Compare two different Oracle homes
Compare the same Oracle home at different times
Track the current status of an Oracle home
Snapshot Tables
Snapshot information is stored in several tables. They contain details such as:
The name, type, and other attributes of each snapshot
The list of files, file versions, and other attributes of each file recorded by the snapshot
The list of patches and bug fixes recorded by the snapshot
Table 10-1 describes the tables related to snapshots.
Table 10-1 Snapshot Tables
| Table Name | Description |
|---|---|
|
|
Records one entry for each snapshot. |
|
|
Records all patches ever applied at the moment of snapshot creation for a specific snapshot. |
|
|
Records all files associated with a particular snapshot. |
|
|
Records all files associated with every snapshot in the system. Contains one entry for each file, regardless of how many snapshots and snapshot versions exist. This table may contain files that are no longer in the system to save files for past snapshots. |
|
|
Records all versions for each file that are present in any snapshot. |
|
|
Records all patches that have been applied to the Oracle home. |
You can select a task from the Maintain Snapshot Information submenu. Select the last option in the list to return to the AD Administration main menu.
This action queries the database and lists all snapshots. It displays the name, type, and comments for each snapshot stored in the AD_SNAPSHOTS table.
If your current view snapshot is not up-to-date, you can update it. An example of when you may need to run this task is when a snapshot may not have been updated as the result of an interruption during a patching session. All of the other snapshot maintenance tasks are based on the results of this task. You can choose to scan the entire Oracle Fusion Applications Oracle home for all installed product families to determine which component directories should be examined or you can choose a specific product family. For each of those components, it scans these product family subdirectories: components, db, and patch. It then updates the database as follows:
Inserts and updates the current view snapshot whenever the Update Current View Snapshot runs.
Modifies the file and file version information for the current view snapshot.
Sets the RAN_SNAPSHOT_FLAG column in the AD_SNAPSHOTS table to Y to indicate that the Update Current View Snapshot ran.
This action lists the current view snapshot and prompts you to provide a name. It then performs the following actions:
Creates the named view snapshot.
Creates a file information list for this snapshot by copying from the current view snapshot.
Copies the bug fix list from the current view snapshot.
This action lists the snapshots available for export. Then it copies the snapshot file details and snapshot bug fix information to an output file that you specify at the prompt.
This action prompts you for the full path and name of the file you want to import. It then updates the snapshot tables with the imported snapshot details.
Database entities are objects or data related to Oracle Fusion Applications. During standard system use, some database entities may become invalid, for example, through user error or after you apply a large patch. Oracle recommends that you verify the integrity of database entities as a regular maintenance procedure, or whenever the activity of your system indicates that database entities may need revalidation.
AD Administration contains several tasks designed to manage database entities. You access them from the Maintain Applications Database Entities submenu. Some tasks in this menu report on issues, or potential issues, and others actually resolve the issues.
As you apply patches and make manual changes to the database, the number of invalid objects can increase. This process compiles invalid database objects in all schemas in the database. As soon as the compile process is complete, AD Administration generates an HTML report that contains information about any objects that remain invalid.
The health check process is a centralized set of validity checks that you can perform to ensure that the database is compatible with Oracle Fusion Applications. It validates the schemas and the database objects they contain to verify that they are valid.
The checks performed are as follows:
Confirms the presence and validity of ADM_DDL in the FUSION_RUNTIME schema
Identifies grants given to Oracle Fusion Applications and grants given by way of roles. Ensures that no grant is given with the admin option set to Yes. This task grants privileges to roles used by the FUSION_RUNTIME schema.
Performs various checks on Oracle Fusion Application such as ensuring that synonyms point to valid, existing tables.
Verifies that privileges are given to roles used by the FUSION_RUNTIME schema.
Generates a list of invalid objects, compiles the invalid objects, and issues a report that includes the commands to recompile the objects that remain invalid.
The health check process produces a report with its findings, named ad_health_check_report.html. It also creates two scripts that contain a set of corrective actions that you can take to fix the issues found by the analysis. The scripts may contain steps for you to follow to resolve an issue and they may also contain SQL actions that are executed when you run the script. The HTML file and both scripts are located in the FA_ORACLE_HOME /admin/SID/log directory.
The following scripts are created:
ad_health_fix_sys.sql: Run this script as sysdba.
ad_health_fix_fus.sql: Run this script as fusion.
This task grants privileges to roles used by the FUSION_RUNTIME schema.
The standard Oracle Fusion Applications Multilingual Support (MLS) table architecture requires that the multilingual tables (those ending with _TL) be fully populated for all active languages. For each row in the base table, there must be a corresponding row in the MLS table for each active language. The Maintain Multilingual Tables utility standardizes and centralizes the synchronization logic for all tables in Oracle Fusion Applications. It relies on the Application/XDF dictionary data to know which tables to synchronize and inserts records only when they are missing for a given language. When you install a language, this task automatically runs. You can also run it from the AD Administration menu when you have reason to believe that the data in the _TL table is not synchronized. For more information, see Section 6.4, "Install a Language Pack".
The previous sections have so far described how to run AD Administration interactively - you start the adadmin utility and respond to system prompts, select a submenu from the main menu, and then select the task you want to run from that submenu. You can also run AD Administration noninteractively by specifying a defaults file that contains the information necessary to run one of the maintenance tasks. The first time you create the defaults file, you run the adadmin command interactively, and then you can reuse the defaults file for the task that you performed.
This section describes the steps necessary to create a defaults file and save it for when you want to run one of the AD Administration tasks without user intervention. You may want to use the noninteractive functionality for long-running tasks, such as compiling the schema.
To create a defaults file, you add the option defaultsfile= defaults file location to your adadmin command. The following example syntax shows how to create a defaults file for compiling the schemas:
(UNIX) FA_ORACLE_HOME/lcm/ad/bin/adadmin.sh defaultsfile=FA_ORACLE_HOME/admin/$TWO_TASK/default_compile.txt (Windows) FA_ORACLE_HOME\lcm\ad\bin\adadmin.cmd defaultsfile=FA_ORACLE_HOME\admin\%LOCAL%\default_compile.txt
The next time you want to perform this same task noninteractively, call the adadmin command in noninteractive mode and specify the defaults file. Then run the adadmin command interactively to record the history of the session in the specified defaults file.
The following example specifies the defaults file:
(UNIX) FA_ORACLE_HOME/lcm/ad/bin/adadmin.sh defaultsfile=FA_ORACLE_HOME/admin/$TWO_TASK/default_compile.txt interactive=no (Windows) FA_ORACLE_HOME\lcm\ad\bin\adadmin.cmd defaultsfile=FA_ORACLE_HOME\admin\%LOCAL%\default_compile.txt interactive=no
When you use the defaults file in noninteractive mode, your adadmin session reads the contents of the defaults file to respond to the prompts.
You can select a specific AD Administration menu option by specifying the menu name when you call the adadmin command. This functionality allows you to perform specific tasks somewhat noninteractively without using a defaults file. You must respond to the initial adadmin prompts. The following example shows how to run adadmin to compile the schemas:
(UNIX) FA_ORACLE_HOME/lcm/ad/bin/adadmin.sh menu_option=CMP_INVALID (Windows) FA_ORACLE_HOME\lcm\ad\bin\adadmin.cmd menu_option=CMP_INVALID
If you select a menu option that contains additional prompts, such as List Snapshots, then you must respond to those prompts interactively. Table 10-2 provides a list of menu names that you can specify with menu_option when running the adadmin command.
Table 10-2 AD Administration Menu Options
| Menu Name | Description |
|---|---|
|
|
Lists snapshots |
|
|
Updates the current view snapshot |
|
|
Updates the current view snapshot for a product |
|
|
Creates a named view snapshot |
|
|
Exports a snapshot to a file |
|
|
Imports a snapshot from a file |
|
|
Deletes a named view snapshot |
|
|
Compiles schemas |
|
|
Performs the health check analysis |
|
|
Re-creates grants and synonyms for the |
|
|
Maintains multi-lingual tables |
You can combine the functionality provided by adding menu_option to the adadmin command along with specifying a defaults file. This allows you to bypass responding to prompts interactively. However, if you add the menu_option selection to the adadmin command while referencing an existing defaults file, your session executes only that menu choice from the defaults file. For example, if your defaults file was created to compile schemas and update the current view snapshot, the following command would update only the current view snapshot:
(UNIX) FA_ORACLE_HOME/lcm/ad/bin/adadmin.sh menu_option=update_current_view defaultsfile=FA_ORACLE_HOME/admin/$TWO_TASK/mydefaults.txt (Windows) FA_ORACLE_HOME\lcm\ad\bin\adadmin.cmd menu_option=update_current_view defaultsfile=FA_ORACLE_HOME\admin\%LOCAL%\mydefaults.txt
The HomeChecker utility verifies the correctness of any Oracle Fusion Applications Oracle home directory. It verifies that the duplicated Oracle Applications Development Framework (Oracle ADF) libraries within Oracle Fusion Applications are synchronized with each other. While separate copies of the libraries are maintained, they are treated logically as a unit and this utility verifies that the libraries are still consistent with each other. HomeChecker also ensures that the artifacts within the Oracle home match the central Oracle Inventory, to confirm that the artifacts were laid down either as part of the initial installation or by a subsequent patch. For more information, see Section 2.1.5, "Oracle Universal Installer (OUI) Inventory".
The HomeChecker output displays the following information:
Libraries that are not synchronized
Oracle Fusion Applications artifacts that are not synchronized
Libraries that are synchronized
Oracle Fusion Applications artifacts that are synchronized
You would most likely run the HomeChecker utility when you are working with Oracle Support Services to diagnose issues with your environment.
To run the HomeChecker utility
Run the following command:
(UNIX) FA_ORACLE_HOME/lcm/ad/bin/homechecker.sh -validate FA_ORACLE_HOME path [-logfile log file name] [-prodfamily comma-separated list of product families] [-reportfile report file path] [-loglevel log level] (Windows) FA_ORACLE_HOME\lcm\ad\bin\homechecker.cmd -validate FA_ORACLE_HOME path [-logfile log file name] [-prodfamily comma-separated list of product families] [-reportfile report file path] [-loglevel log level]
Table 10-3 HomeChecker utility parameters
| Parameter | Description | Mandatory |
|---|---|---|
|
validate |
Specify the path to |
Yes |
|
logfile |
Overrides the default log file name and sends the processing information to the file you specify, under the |
No |
|
prodfamily |
Supply a comma-separated list of product families you want to see on the report |
No |
|
reportfile |
Supply the directory path and file name for report output |
No, the default is the current directory |
|
loglevel |
Records messages in the log file at the level you specify. Enter a value to override the default log level of |
No |
|
 Copyright © 2011, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
