Oracle® Applications: Maintenance Utilities Release 12
Oracle® Applications: Maintenance Utilities Release 12
Oracle® Applications: Maintenance Utilities Release 12
Maintenance Utilities
Release 12
Part No. B31568-01
January 2007
Oracle Applications Maintenance Utilities, Release 12
The Programs (which include both the software and documentation) contain proprietary information; they
are provided under a license agreement containing restrictions on use and disclosure and are also protected
by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly,
or decompilation of the Programs, except to the extent required to obtain interoperability with other
independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in
the documentation, please report them to us in writing. This document is not warranted to be error-free.
Except as may be expressly permitted in your license agreement for these Programs, no part of these
Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any
purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs
on behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data
delivered to U.S. Government customers are "commercial computer software" or "commercial technical
data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental
regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including
documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable
Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19,
Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway,
Redwood City, CA 94065.
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently
dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup,
redundancy and other measures to ensure the safe use of such applications if the Programs are used for such
purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third
parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites.
You bear all risks associated with the use of such content. If you choose to purchase any products or services
from a third party, the relationship is directly between you and the third party. Oracle is not responsible for:
(a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the
third party, including delivery of products or services and warranty obligations related to purchased
products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from
dealing with any third party.
Contents
1 Getting Started
Oracle Applications Maintenance Utilities......................................................................................... 1-1
Command Line Utilities .................................................................................................................... 1-1
Web-based Utilities ............................................................................................................................ 1-2
Online Help......................................................................................................................................... 1-3
AD Command Line Utilities .................................................................................................................. 1-5
Common AD Operations .................................................................................................................. 1-5
The AD Interface ................................................................................................................................ 1-8
Command Line Arguments.............................................................................................................. 1-9
Running AD Utilities ...................................................................................................................... 1-13
Using Parallel Processing .................................................................................................................... 1-16
Processing Tasks in Parallel........................................................................................................... 1-16
Monitoring and Controlling Parallel Processes .......................................................................... 1-18
Distributing Processing Tasks Across Nodes ............................................................................. 1-20
OAM Web-based Utilities ................................................................................................................... 1-20
Common OAM Operations ........................................................................................................... 1-21
OAM Interface ................................................................................................................................. 1-21
Accessing OAM ............................................................................................................................... 1-23
iii
AutoPatch................................................................................................................................................... 2-7
The AutoPatch Interface.................................................................................................................... 2-8
Running AutoPatch ........................................................................................................................... 2-8
Other Patching Tools ......................................................................................................................... 2-9
3 Configuration
About System Configurations ............................................................................................................... 3-1
Web-based Configuration Utilities .................................................................................................. 3-1
Command Line Configuration Utilities .......................................................................................... 3-2
AD Splicer.................................................................................................................................................. 3-2
Control Files ........................................................................................................................................ 3-2
The AD Splicer Interface ................................................................................................................... 3-3
Running AD Splicer........................................................................................................................... 3-3
File Character Set Converter .................................................................................................................. 3-4
Required Parameters ......................................................................................................................... 3-4
The File Character Set Converter Interface .................................................................................... 3-4
Running the File Character Set Converter...................................................................................... 3-4
4 Maintenance
About System Maintenance ................................................................................................................... 4-1
AD Administration Overview ............................................................................................................... 4-1
Prompts................................................................................................................................................ 4-2
Preparing for Non-interactive Processing ...................................................................................... 4-2
The AD Administration Interface .................................................................................................... 4-3
Running AD Administration Interactively .................................................................................... 4-4
Generating Applications Files ............................................................................................................... 4-5
Generate Message Files ..................................................................................................................... 4-5
Generate Form and Report Files ...................................................................................................... 4-5
Generate Product JAR Files .............................................................................................................. 4-6
Maintaining Applications Files............................................................................................................. 4-7
Relink Applications Programs ........................................................................................................ 4-7
Create Applications Environment File [Subkey in Registry]....................................................... 4-7
Copy Files to Destinations ................................................................................................................ 4-8
Convert Character Set........................................................................................................................ 4-8
Maintain Snapshot Information ....................................................................................................... 4-9
Check for Missing Files .................................................................................................................. 4-11
Managing Database Entities ............................................................................................................... 4-11
Compiling or Reloading Database Entities ................................................................................. 4-11
Maintaining Applications Database Entities............................................................................... 4-12
Changing Maintenance Mode ............................................................................................................ 4-14
AD Relink ............................................................................................................................................... 4-14
Log Files............................................................................................................................................ 4-15
Command Line Arguments........................................................................................................... 4-15
The AD Relink Interface................................................................................................................. 4-15
Running AD Relink......................................................................................................................... 4-16
iv
5 Reporting
About Oracle Applications Reporting Tools ...................................................................................... 5-1
Reporting Tools .................................................................................................................................. 5-1
AD Job Timing Report ............................................................................................................................ 5-2
The AD Job Timing Report Interface............................................................................................... 5-2
Running AD Job Timing Report ...................................................................................................... 5-2
AD Configuration Report ....................................................................................................................... 5-3
The AD Configuration Report Interface ......................................................................................... 5-3
Running AD Configuration .............................................................................................................. 5-3
AD File Identification Report ................................................................................................................ 5-4
Command Line Arguments.............................................................................................................. 5-4
The AD File Identification Report Interface ................................................................................... 5-4
Running AD File Identification........................................................................................................ 5-4
AD Check Digest...................................................................................................................................... 5-5
The AD Check Digest Interface........................................................................................................ 5-5
Parameters........................................................................................................................................... 5-5
Running AD Check Digest................................................................................................................ 5-5
Index
v
vi
Preface
This document, along with Oracle Applications Maintenance Procedures and Oracle
Applications Patching Procedures make up the Maintaining Oracle Applications
documentation set, which describes Oracle Applications utilities and associated
procedures for maintaining the application file system and database. Oracle
Applications Maintenance Utilities provides a general description of the utilities.
Audience
This book is intended for database administrators and system administrators who are
responsible for performing the tasks associated with maintaining an Oracle
Applications system.
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation
accessible, with good usability, to the disabled community. To that end, our
documentation includes features that make information available to users of assistive
technology. This documentation is available in HTML format, and contains markup to
facilitate access by the disabled community. Accessibility standards will continue to
evolve over time, and Oracle is actively engaged with other market-leading
technology vendors to address technical obstacles so that our documentation can be
accessible to all of our customers. For more information, visit the Oracle Accessibility
Program Web site at
http://www.oracle.com/accessibility/
vii
TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services
within the United States of America 24 hours a day, seven days a week. For TTY
support, call 800.446.2398. Outside the United States, call +1.407.458.2479.
Related Documents
This book was current as of the time it was initially published. It is included in the
Oracle Applications Document Library, which is supplied in the Release 12 software
bundle. Later versions of this and other documents that have changed sufficiently
between releases to warrant re-publishing are made available at the following URL:
http://www.oracle.com/technology/documentation/applications.html
A full list of documentation resources is also published on OracleMetaLink. See Oracle
Applications Documentation Resources, Release 12 (Doc ID: 394692.1). You can also
purchase hard-copy documentation from the Oracle Store at:
http://oraclestore.oracle.com.
The following references are specifically related to maintenance tasks:
■ Oracle Applications Maintenance Procedures
■ Oracle Applications Maintenance Utilities
■ Oracle Applications Patching Procedures
■ Oracle Applications System Administrator’s Guide — Configuration
■ Oracle Applications System Administrator’s Guide — Maintenance
■ Oracle Applications System ADministrator’s Guide — Security
Conventions
The following conventions are used in this book:
Convention Meaning
UNIX: Indicates platform-specific information. This guide contains
Windows: information for both UNIX and Windows platforms. All
instructions for UNIX platforms also apply to Linux platforms,
unless otherwise noted.
$ or C:\> Represents the platform-specific command prompt. Your
prompt may differ.
Monospace text Represents command line text. Type this text exactly as shown.
<> Text enclosed in angle brackets represents a variable. Substitute
a value for the variable text. Do not type the brackets
[] Encloses optional items or indicate a function key. Do not type
the brackets.
| Represents an OR option among several options. You must enter
only one of the options. Do not type the vertical bar.
\ In examples of commands you type online, a backslash at the
end of a line signifies that you must type the entire command on
one line. Do not type the backslash.
Special notes Additional Information, Note, and Caution boxes alert you to
particular information within the body of the book.
viii
1
Getting Started
Web-based Utilities
Oracle Applications Manager (OAM) provides a web-based interface where system
administrators can monitor system status, administer services, examine system
configuration, manage Oracle Workflow, view applied patches, and measure system
usage. It provides a concise overview of the state of your Oracle Applications system,
and serves as a gateway to utilities for tasks such as managing system configuration,
reviewing patch history, determining which patches will bring your system up to date,
registering additional products and languages, and other maintenance activities.
The web-based maintenance utilities are listed in the following table. Their operation
is described fully in Oracle Applications Patching Procedures or the Oracle Applications
System Administrator’s Guide – Configuration.
Online Help
Both the AD utilities and the OAM utilities provide a help function.
The arguments and options that you can use to refine the operation of a utility are
listed, along with a brief description of how they work. Here’s an excerpt from the
command line help for AutoPatch.
usage: adpatch [help=y]
adpatch Pre-Install Mode
[preinstall=y|n]
adpatch Test Mode
[apply=y|n]
adpatch Non-Interactive mode
[defaultsfile=<$APPL_TOP/admin/SID/defaultsfile>]
[logfile=<logfile>][interactive=y|n][workers=<workers>]
[patchtop=<patchtop>][driver=<driver_file>][restart=y|n]
[abandon=y|n][wait_on_failed_job=y|n]
adpatch
[localworkers=<localworkers>][workers=<workers>]
[printdebug=y|n][parallel_index_threshold=<threshold_value>]
[order=<order>] [flags=<flags>][options=<options>]
where
* help=y - Prints help information about adpatch options.
* preinstall - To run adpatch in Pre-Install Mode.
Default - No.
* apply - To run adpatch in Test Mode.
Default - Yes.
* interactive - Invokes adpatch in Non-Interactive mode when
"interactive=no" is specified.
Default - Yes.
OAM Help
OAM Help is in the form of a web-based directory tree that lists overview information
and specific features available from the Site Map or the Applications Dashboard. You
access the menu by clicking the Help icon from any page in the Oracle Applications
Manager. For example, from the Site Map Administration tab, click the Help icon.
The OAM help directory appears in a separate window. Click either the Contents tab
or Index tab to expand the branches and view the entire tree.
Click a plus sign to see more topics, and click any individual link to access information
on that topic.
Individual topics may include topical essays, procedures, and page descriptions. The
help associated with the utilities and features discussed in this book provides
navigation paths, field definitions, and general information about using the page.
Common AD Operations
Many AD utilities employ similar features and operations as they perform processing
tasks. For example, most rely on prompts to gather values for system-specific
processes, and all automatically create log files to record processing actions. This
section describes some of these common operations.
Prompts
Many AD utilities prompt for information necessary for completing a task. Prompts
typically include a description of the information needed, and may include a default
answer (in square brackets). For example:
The ORACLE username specified below for Application Object Library uniquely
identifies your existing product group: APPLSYS
Press [Return] to accept the default value, or type a new value after the colon and
press [Return]. Read the prompts carefully to make sure you supply the correct
information.
Log Files
All AD utilities record their processing actions and any errors that they encounter in
log files. Many utilities prompt you for the name of the log file that will record the
processing session.
<utility name> records your <utility name> session in a text file you specify.
Enter your <utility name> log file name or press [Return] to accept the default
name shown in brackets.
The default file name is <utility name>.log. For example, for AD Administration, the
default log file is adadmin.log, and for AutoPatch, it is adpatch.log.
AD Administration (and AutoPatch) place the log file in the following directory,
$APPL_TOP/admin/<SID>/log, where <SID> is the value of the ORACLE_SID or
TWO_TASK variable (UNIX), or in %APPL_TOP%\admin\<SID>\log, where <SID>
is the value of the LOCAL variable (Windows). Log files created by Rapid Install and
AutoConfig are located in the $APPL_TOP/admin/<CONTEXT_NAME>/log
directory.
Other utilities may not prompt you for a log file name. Typically, they write the log
file in the directory from which the utility was run.
Restart Files
Restart files contain information about what processing has already been completed.
They are located in $APPL_TOP/admin/<SID>/restart (UNIX) or in %APPL_
TOP%\admin\<SID>\restart (Windows).
If a utility stops during processing due to an error, or you use AD Controller (in the
case of parallel processing) to shut down workers while they are performing
processing tasks, you can restart the utility. If you do, it looks for restart files to
determine if there was a previous session. If the files exist, the utility prompts you to
continue where the processing left off, or to start a new process. If you choose to
continue, it reads the restart files to see where the process left off, and continues the
process from that point.
By default, AD utilities delete their restart files when processing is complete, but leave
backup versions with the extensions .bak, .bk2, or .bk3.
The following table lists configuration and environment files commonly used by the
AD command line utilities, and in some cases, by the OAM web-based utilities. Note
that <CONTEXT_NAME> defaults to <SID>_<hostname>.
The following configuration and environment files are also used by most AD utilities,
but are not created by AutoConfig. Do not update these files manually.
Feature Versions
In order to use some AD Administration and AutoPatch features, the version number
of the feature must be the same in both the file system and the database. There may be
times when these feature versions do not match. For example, if a patch did not run
successfully to completion, it may have updated the file system, but not the database.
In this case, the file system version and the database version could be different.
When you start AD Administration or AutoPatch, an information matrix scrolls on the
screen. It indicates the status (Active=<Yes or No>) and version numbers of the
following features: CHECKFILE, PREREQ, CONCURRENT_SESSIONS, PATCH_
HIST_IN_DB, PATCH_TIMING, and SCHEMA_SWAP.
The matrix is for information only. No action is required unless the feature versions do
not match. If they do not, you can use the OAM Applied Patches utility to determine
which patches were applied successfully and verify the version level.
The AD Interface
Some AD utilities are designed to perform a single function. For example, you run AD
Relink only to relink executables programs with the server product libraries. These
utilities do not use menus or input screens. All user interaction is from the command
line in the form of prompts.
However, other utilities have multiple functions, which are presented on menus or
input screens. For example, when you run AD Administration, the first screen you see
is the main menu.
From this screen, choose one of the submenus, and then from there, choose the process
you want to run.
The token ("LOGFILE") will be converted to lowercase, but the value (TEST.LOG) is
not recognized by the utility. The correct way to enter this command is:
$ adadmin logfile=test.log
You can enter more than one token=value argument on a single command line by
separating them with one blank space as in the following AutoPatch command.
$ adadmin printdebug=y flags=hidepw
In some cases, you can include more than one value for a token. In this case, separate
the values with commas. For example:
$ adadmin flags=nohidepw,trace
Comma-separated lists must not contain blank spaces. For example, this command is
not valid:
$ adadmin flags=nohidepw, trace
Some command line arguments are used by several utilities and are listed in the
following table. Other arguments are used only for a specific utility. For example,
AutoPatch makes extensive use of command line arguments and options that are
unique to that utility. They are listed and discussed Oracle Applications Patching
Procedures.
abandon Description
Used by AD Administration, AutoPatch
Purpose Tells AD utilities to abandon an existing non-interactive
session. Can be used only when interactive=n is also specified.
Values y or n
Default n, meaning that the last utility run non-interactively did not
successfully complete the processing.
Example adadmin interactive=n abandon=y
defaultsfile Description
Used by AD Administration, AutoPatch, AD Controller
Purpose Specifies the defaults file which stores answers to interactive AD
utility questions. Normally used non-interactively.
Values A fully-qualified filename. Must be under the $APPL_
TOP/admin/<SID> directory.
defaultsfile Description
Default None, meaning that no defaults file is used.
Example adctrl defaultsfile=/d1/apps/prodappl/admin/prod1/prod_
def.txt
help Description
Used by All AD utilities
Purpose Summarizes available command line options.
Values y or n
Default n
Example adadmin help=y
interactive Description
Used by AD Administration, AutoPatch, AD Controller
Purpose Tells AD utilities whether to run either interactively or
non-interactively.
Values y or n
Default y, meaning that the utility runs interactively.
Example adadmin interactive=n
localworkers Description
Used by AD Administration, AutoPatch
Purpose Specifies the number of workers to run on the primary node in a
Distributed AD environment.
Values 1 to the maximum supported by your database, but not more
than 999, inclusive
Default Defaults to the value of the workers argument, which means all
workers run on the primary node.
Example adadmin workers=8 localworkers=3
logfile Description
Used by All AD Utilities
Purpose Tells AD utilities what log file to use. Normally used when
running a utility non-interactively.
Values A file name (not a fully-qualified path name)
Default None, meaning that the utility will prompt for the log file name.
Example adctrl logfile=test.log
menu_option Description
Used by AD Administration, AD Controller
menu_option Description
Purpose When running one of these utilities non-interactively, used to
connect the actions in a defaults file with a specific menu item.
Values See list of menu options in the description of these utilities.
Must be used with interactive=n and defaultsfile=<name of
defaults file>.
Default N/A
Example adctrl interactive=n defaultsfile=$APPL_
TOP/admin/prod/ctrldefs.txt menu_option=SHOW_STATUS
parallel_index_threshold Description
Used by AD Administration, AutoPatch
Purpose Specifies the number blocks in a table. If a table contains fewer
blocks than the threshold setting, indexes are created with
parallel workers and serial DML. If the table contains more
blocks than the threshold setting, indexes are created with one
worker and parallel DML.
Values 0 to 2147483647; if set to 0, indexes are created with parallel
workers and serial DML
Default 20000; meaning a threshold of 20,000 blocks.
Example adadmin parallel_index_threshold=15000
printdebug Description
Used by All AD Utilities
Purpose Tells AD programs to display extra debugging information. In
some cases, the amount of extra debugging information is
substantial.
Values y or n
Default n
Example adadmin printdebug=y
restart Description
Used by AD Administration, AutoPatch, AD Controller
Purpose Tells AD utilities running non-interactively to restart an existing
session. Only valid when interactive=n is also specified.
Values y or n
Default n, meaning that the utility running non-interactively will expect
to run a completely new session.
Example adadmin interactive=n restart=y
wait_on_failed_job Description
Used by AD Administration, AutoPatch
Purpose Directs the utilities to wait for user input in a non-interactive
session when a job fails.
wait_on_failed_job Description
Values y or n
Default n
Example adadmin wait_on_failed_job=yes
workers Description
Used by AD Administration, AutoPatch
Purpose Specifies the number of workers to run. Normally used when
running the utility non-interactively.
Values 1 to the maximum supported by your database, but not more
than 999
Default No, meaning that the program prompts for the number of
workers to run.
Example adadmin workers=8
AD Flags
The flags= argument is used by all AD utilities. It passes one of several generic flags to
the utility. Enter one flag or a comma-separated list of flags. The default is None.
hidepw Description
Default hidepw
Purpose Directs the utilities to either hide or show passwords in AD Utility
log files.
Comments By default, lines in an AD utility log file containing passwords are
modified to hide the passwords.
When nohidepw is specified, each line containing hidden
passwords is followed by a corresponding line prefixed with
HIDEPW:, showing the original line with passwords.
Example adadmin flags=nohidepw
logging Description
Default logging
Purpose Tells the AD utility whether to create indexes using logging or
nologging.
Comments Using flags=nologging when creating indexes may increase
performance. However, flags=nologging makes database media
recovery incomplete and does not work with standby databases.
Logging is the default in AutoPatch to support database media
recovery and standby databases. We do not recommend using
flags=nologging for production systems unless you make a
complete backup both before and after running AutoPatch.
flags=nologging affects indexes created through ODF only, not SQL
scripts. The XDF utility always creates indexes with logging.
Example adpatch flags=logging
trace Description
Default notrace
Purpose Tells the AD utility whether to log all database operations to a trace
file.
Comments RDBMS trace files created while running an AD utility may aid
debugging. The flags=trace option creates multiple trace files for
the AD utility and the AD workers. A new trace file is created each
time the AD utility or a worker reconnects to the database.
Note that flags=trace only traces database operations internal to the
AD utility itself. Database operations in SQL scripts or external
programs run by the AD utility are not recorded by flags=trace.
Example adadmin flags=trace
AD utilities accept other arguments. However, they should be used only when
instructed to do so by Oracle Support Services.
Running AD Utilities
To run AD utilities, set the environment to define the system configuration
parameters. For example, a utility may require the directory path to the Applications
ORACLE_HOME. This parameter, and others, make up your system environment.
Once you have pointed the utility to the correct environment, you start it by entering
the executable (start command).
Windows:
Run %APPL_TOP%\envshell.cmd using either Windows Explorer or the Run
command from the Start menu. This creates a Command Prompt window that
contains the required environment settings for Oracle Applications. Run all
subsequent commands in this Command Prompt window.
3. If you have made any changes to the environment, check that it is correctly set by
typing the following commands:
UNIX:
$ echo $TWO_TASK
$ echo $ORACLE_HOME
$ echo $PATH
Windows:
C:\> echo %LOCAL%
C:\> echo %ORACLE_HOME%
C:\> echo %PATH%
C:\> echo %APPL_CONFIG%
For UNIX, the ORACLE_HOME must be set to the proper database directory, and
TWO_TASK or LOCAL must identify the correct database. For Windows, APPL_
CONFIG must be set to <CONTEXT_NAME>.
4. Ensure that there is sufficient temporary disk space.
You should have at least 50 MB in the temporary directories denoted by
$APPLTMP, $APPLPTMP, and $REPORTS60_TMP (UNIX) or %APPLTMP%,
%APPLPTMP%, and %REPORTS60_TMP% (Windows). You should also have
space in the operating system’s default temporary directory, which is usually
/tmp or /usr/tmp (UNIX) or C:\temp (Windows).
5. If you are running an AD utility to relink or update Oracle Applications product
files or modify Oracle Applications database objects, shut down the concurrent
manager, Web server listeners, forms server listeners if the files are on a node that
contains the associated servers. For example, if the files are on the node that
contains the concurrent processing server, shut down the concurrent managers.
Starting a Utility
To start an AD utility, type the utility’s executable name (start command) on the
command line. For example, to start AD Administration, you would type:
$ adadmin
Restarting a Utility
You can restart a utility by entering the executable on the command line. When you
restart, the utility prompts you to enter a new log file, or to specify the log file from the
interrupted session. When you reuse the log file from a previous session, the utility
adds the message “Start of <utility name> session” to the end of the file and appends
messages from the continued session as it generates them.
The utility prompts you to do one of the following:
■ Continue Session (the default)
The utility checks the progress of the previous session in the restart files, and
begins processing at the point where your last session stopped.
Note: You must have a shared application tier file system to use
Distributed AD. See Distributing Processing Tasks in Oracle
Applications Maintenance Procedures.
Managers
The manager assigns each worker a unique ID and inserts a row for each worker in the
FND_INSTALL_PROCESSES table. It 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 its assignment, the manager updates each row with the next task in the list,
and leaves another message for the worker.
Once all jobs are complete, the manager tells the workers to shut down, and then
drops the FND_INSTALL_PROCESSES table (after it is sure all workers have actually
shut down).
Workers
Each worker updates the STATUS column, giving the manager a report on its
progress. As the jobs are completed, the manager updates the table with the next job in
the queue, and updates the CONTROL_CODE and STATUS columns telling the
worker to start processing. If there is a failure, the worker reports a failed status.
For certain tasks, some worker processes spawn other child processes that do the actual
work. The spawned child process returns a status code to the worker that spawned it.
The worker interprets the code to determine if the job has been completed
successfully. Examples of child processes are SQL*Plus and FNDLOAD.
Deferred Jobs
The first time a job fails, the manager automatically defers the job and assigns a new
one to the worker. If the deferred job fails the second time it is run, the manager defers
it again only if the total runtime of the job is less than ten minutes. If the deferred job
fails a third time (or if the job’s total runtime is not less than ten minutes the second
time it is run) the job stays at failed status and the worker waits. At this point, you
must address the cause of the failure, and then restart the job.
The deferred job feature uses the AD_DEFERRED_JOBS table. This table is created
when the FND_INSTALL_PROCESSES table is created, and is dropped when the
FND_INSTALL_PROCESSES table is dropped.
\restart (Windows). The worker creates the restart file when the manager assigns it a
job, and deletes the restart file when it finishes the job.
You choose options that display worker status, restart workers, or issue commands to
the manager from the AD Controller main menu.
Note: Run this utility in its own window, not in the same window
as AD Administration or AutoPatch.
Type a number to select an option. Press [Return] at any time to return to the AD
Controller main menu.
Like AD Administration, the same defaults file can be used to run different AD
Controller commands — a single file can contain all your choices for the different
menu options. In order to choose which task the defaults file will run, you add menu_
option= <menu choice> to the utility start command. This overrides any menu-specific
key stroke information stored in the defaults file initially, and allows you to use the
defaults file for any of the AD Controller menu items. It also ensures that the menu
option you intended for the defaults file is always valid, even it the menu items are
renumbered or relocated in subsequent releases
The available options are listed in the following table.
Note: Using any menu option on the command line, except for
SHOW_STATUS, requires that you also use the worker_
range=<range> option. See the AD Controller command line help
for details.
Page Navigation
On individual pages, you have navigation options, and, where appropriate, there are
drop-down lists that provide links to related features. On pages with lengthy lists of
items, OAM displays a subset of the items for easy access.
OAM Interface
The Oracle Applications Manager Dashboard presents a quick overview of the general
status of your system. The Site Map provides access to the utilities and features within
the OAM framework.
Open the list, make a selection, and click Go. For a more complete list of all the utilities
and features included in OAM, click the Site Map tab.
The Site Map page displays tabs for Administration, Monitoring, Maintenance, and
Diagnostics and Repair. On individual tabs, there are links to utilities or functions
under general groups. For example, on this page there are headings for System
Configuration, Application Services, Workflow, and so on. Under the Maintenance
tab, there are headings for Patching Utilities and Critical Activities.
To open the main page for a utility, find it under one of the headings and click the
link. For example, to view information about patches that have already been applied
to your system, click Applied Patches under the Patching and Utilities heading on the
Maintenance tab.
Click any of the other tabs to access other functions. In this guide, all instructions for
accessing OAM web-based utilities start from the Site Map.
Accessing OAM
You access OAM using the following URL:
http:.// <HTTP hostname>.<domain>:<HTTP port>OA_HTML/AppsLogin
Enter your user name and password, and click Login. The OAM Applications
Dashboard appears. From the Dashboard, you can jump quickly to one of the utilities
listed in the Navigate to: menu, or you can move to the Site Map page to see a
complete list of utilities.
This chapter describes the utilities you use to install a new Oracle Applications system
and to upgrade an existing system to a new release version. It contains these sections:
■ About Installations and Upgrades
■ Rapid Install
■ AutoPatch
Installations
You install Oracle Applications systems using Rapid Install. It installs a new, fully
configured system, including a complete set of Oracle Applications products, a
certified database tier and application tier technology stack, all patches, minipacks,
family packs, and other updates that are available at the time of the software release.
The technology stack consists of the components that are required to run the new
system — those specific to both the database tier and the application tier. For example,
a new installation includes a fresh database (and the associated Oracle homes)
certified for a specific Oracle Applications version, as well as the latest application tier
components.
All products, regardless of their licensed status, are installed. During the installation,
you have an opportunity to flag the products you have licensed to register them as
active in your system. This action marks them for inclusion in patching and other tasks
required to update and maintain your system after the initial installation.
Upgrades
As a part of an upgrade, you enter configuration parameters in the Rapid Install
wizard and run Rapid Install as one of the pre-upgrade preparatory steps. Rapid
Install uses the parameters to lay down the file system and install the new database
tier and application tier technology stack. You migrate or upgrade your existing
database to Oracle 10g as one of the pre-upgrade tasks.
In addition, you use AutoPatch at various times during the upgrade process to apply
upgrade-related patches and to run the upgrade driver that brings your Oracle
Applications system up to the full release level.
Rapid Install
With Rapid Install, you can perform the following tasks:
■ Install a new, fully configured Oracle Applications system, including the latest
certified Oracle Applications technology stack and all patches, minipacks, family
packs, and other updates available at the time of this release.
■ Lay down the file system and configure server processes for an upgraded system.
■ Install a new database tier or application tier technology stack.
Rapid Install employs a wizard that guides you through the screens used to carry out
each selected task. On the wizard screens, you enter configuration values for your
system. They are typically saved in the Applications database for later use.
If you run Rapid Install again, you typically point it to the stored information, so that
it can use those details in operations such as creating the Oracle Applications file
system, installing a fresh database, registering products, managing NLS requirements,
configuring port connections, and creating and running the start and stop scripts for
the database and listeners.
Storing the configuration enables you to perform a distributed install (repeat the process
across multiple machines) without having to re-enter the system configuration
information each time — for every run of the Rapid Install wizard. Storing the
configuration details allows you to enter the information only once, and then use the
same system configuration to run the install on all required machines.
The main configuration engine used by Rapid Install is called AutoConfig. Rapid Install
supplies the configuration information to AutoConfig, which stores it for each node in
a node-specific configuration file called a context file.
AutoConfig also simplifies and standardizes the management of your system
configuration. At any time after the initial installation, you can use the Configuration
Editor in Oracle Applications Manager (OAM) to update various system settings, and
then run an AutoConfig script to populate the system configuration files with the new
values.
Distributed Installations
An installation of a distributed (multi-node) system by Rapid Install includes the setup
of a shared application node file system and associated provision for load balancing.
As the default for nodes running the same operating system, Rapid Install creates a
system that shares not only the APPL_TOP and COMMON_TOP file systems, but the
application node technology stack as well. All application node files are installed on a
single shared disk resource that is mounted from each application node machine,
making it possible for any application node to be used to provide standard services,
■ Replace an option in a drop-down list. Combo boxes give you the ability to replace
an option on the list by typing a valid option in the box. Whenever this type of
input is allowed, it is noted in the text.
Help
Most screens offer mouse-over help for individual fields by providing a description of
the information that goes in the field in a small text box when you move the mouse
over the field. In addition most screens display a Help button. Click it to see
screen-level help — a general description of the screen, and a summary of the input
fields that it displays. Here is an example of screen-level help:
Applications Installation and Upgrade Notes (for your platform) for any additional
requirements.
3. Set up the stage area.
As preparation for running Rapid Install, you must run a Perl script that creates
the install directory and copies the contents of the software bundle to the
appropriate location in the file system.
4. Start Rapid Install, using the following commands:
UNIX:
$ cd /u01/Stage12/startCD/Disk1/rapidwiz
$ ./rapidwiz
Windows:
C:\>f:
F:\>cd Stage12\startCD\Disk1\rapidwiz
F:\Stage12\startCD\Disk1\rapidwiz> rapidwiz.cmd
Click Next. The wizard continues with the appropriate screen flow.
7. Complete the wizard screens.
The remaining wizard screens prompt for the parameters necessary to complete
the installation or upgrade. Once you complete the wizard, Rapid Install verifies
that all parameters necessary to create working environment are present, and
begins to set up your system.
AutoPatch
You use AutoPatch to apply patches to the Oracle Applications file system or
database. It gathers necessary information about your system through a series of
prompts Once you have completed the prompts, AutoPatch performs all the tasks
required to apply the patch, including the following:
Running AutoPatch
Before you run AutoPatch, you must perform some preparatory tasks, including
setting the environment, shutting down services, and enabling maintenance mode.
You start AutoPatch with this command:
$ adpatch
You can direct the way AutoPatch operates by adding modifiers to its start command.
These modifiers may be in the form of arguments or options. They refine the actions
that AutoPatch performs. For example, you can add the driver=<driver file name>
option to indicate to AutoPatch the name of the driver file.
In addition, you can add an options= argument to pass generic options to AutoPatch.
For example, options=nocopyportion tells AutoPatch not to run the copy portion of a
driver. Separate each argument or option with a comma.
During an installation or upgrade, your system is set up and configured based on the
values you specify as a part of those processes. At various times after an installation or
upgrade, you may need to reconfigure your system. Oracle Applications employs
several utilities to aid you with this task. This chapter contains the following
information about configuration utilities:
■ About System Configurations
■ AD Splicer
■ File Character Set Converter
AutoConfig
System configuration parameters are stored and managed by AutoConfig. It is the
main configuration engine used by Rapid Install, which supplies configuration
information to AutoConfig, which, in turn, stores the configuration for each system
node in a node-specific configuration file call a context file.
You can also use AutoConfig independently of a Rapid Install operation to view and
edit the individual configuration parameters that define your system. At any time after
the initial installation, you use the Configuration Editor in Oracle Applications
Manager to update various system settings.
Configuration 3-1
AD Splicer
License Manager
Products, country-specific functionalities (localized products), and languages that you
license or begin to use after the initial installation must be registered as active in order
to be included in various system maintenance tasks. Using License Manager, you can
create reports about currently registered products and register additional products,
country-specific functionalities (localized products).
AD Splicer
Splicing refers to the process of adding a product that was not included in a base
release to the products in an existing system. AD Splicer modifies the APPL_TOP and
database so that AutoPatch and AD Administration recognize the product as valid.
AD Splicer
AD Splicer performs the same product registration function as License Manager.
However, it registers off-cycle products — those that are released between maintenance
packs — as active in your system. This process of "splicing" modifies the APPL_TOP
and database so that AutoPatch and AD Administration recognize the off-cycle
product as a valid product for a specific release.
Patches that contain off-cycle products also contain the control files that AD Splicer
needs to register the product. The patch also contains a readme file that describes how
to install the new product(s).
Control Files
There are two kinds of AD Splicer control files: product definition and product
configuration. You must customize the product configuration file, then copy it and the
product definition file to APPL_TOP/admin before you run AD Splicer.
and must not be edited. For example, the product definition files for Oracle Sales
Analyzer (zsa) are zsaprod.txt and zsaterr.txt.
Product Configuration
The newprods.txt file acts as a template to define necessary parameters for a spliced
product. Here is an example of the product configuration file for Oracle Sales Analyzer
(zsa):
product=zsa
base_product_top=*APPL_TOP*
oracle_schema=zsa
sizing_factor=100
main_tspace=*Product_Name*D
index_tspace=*Product_Name*X
temp_tspace=*Temporary_Tablespace*
default_tspace=*Product_Name*D
You may need to edit some of the values for the parameters in this file. Refer to the
following table for more information. Do not change the order of the entries in the
product configuration file — they must appear exactly as shown in the example.
Parameter Description
product= Do not edit this entry. The product abbreviation <prod> is already set, and must
match the <prod>prod.txt and <prod>terr.txt control files for this product. Most
internal references use <prod>.
base_product_top= Identifies the base directory that contains the product's files. The default value,
*APPL_TOP*, means the product's files are written in the directory your APPL_TOP
environment is set to. If you want to write the product files to another directory,
replace the *APPL_TOP* value with the full directory path.
oracle_schema= Identifies the Oracle schema where database objects for the product are created. The
default Oracle schema is the same as the product abbreviation. You can change this
if you want to put the product's database objects in a different schema. Moving a
product's objects from one schema to another involves export/import and updates
to internal Oracle Applications tables, so choose your initial schema carefully.
sizing_factor= Identifies the sizing factor Oracle Applications uses when creating tables and
indexes for this product. The default value of 100 means 100%.The product's tables
and indexes are created with the default sizes determined by Oracle. We
recommend you accept the default sizing factor.
Tablespaces
Release 12 uses the Oracle Applications Tablespace Model (OATM), so you do not
need to supply AD Splicer with parameters for identifying tablespaces.
Running AD Splicer
All the steps necessary to prepare for using this utility are described in Adding
Off-cycle Products in Oracle Applications Maintenance Procedures. When instructed to do
so, run AD Splicer as follows:
Configuration 3-3
File Character Set Converter
Windows:
C:\> cd %APPL_TOP%\admin
C:\> adsplice
You must run AD Splicer for each APPL_TOP and database combination so that the
Applications utilities recognize the product as being spliced properly into the
database.
Required Parameters
The following parameters are required for running the converter.
Parameter Definition
source_file Path and file name for the (source) file to be converted.
source_char_set Character set for the file to be converted (source).
destination_file Path and file name for the (destination) file after it is converted.
dest_char_set Character set for the converted (destination) file.
The path and file name for the source and the destination files can be the same if the
source file’s directory and the APPLTMP directory are on the same file system. In
general, it is simpler and safer to use different source and destination file names.
For example, to convert the file afdict.ldt from the we8iso8859p1 character set to the
utf8 character set, you would type:
UNIX:
$ cd $FND_TOP/patch/115/import/<language>
$ cp afdict.ldt afdict.old
$ adncnv afdict.old we8iso8859p1 afdict.ldt utf8
Windows:
C:\> cd %FND_TOP%\patch\115\import\<language>
C:\> copy afdict.ldt afdict.old
C:\> adncnv afdict.old we8iso8859p1 afdict.ldt utf8
Configuration 3-5
File Character Set Converter
In order to ensure that your Oracle Applications system runs smoothly, you must
perform routine maintenance tasks. This chapter discusses the AD utilities designed to
help you perform those tasks. It contains these sections:
■ About System Maintenance
■ AD Administration Overview
■ Generating Applications Files
■ Maintaining Applications Files
■ Managing Database Entities
■ Changing Maintenance Mode
■ AD Relink
AD Administration Overview
AD Administration manages most of the maintenance tasks required for your Oracle
Applications system. Currently, these maintenance tasks are grouped by types on the
AD Administration main menu.
When you start AD Administration from the command line, it prompts you for the
basic system-specific information it needs. For example, you need to supply a name
for the log file where processing actions and error messages will be recorded.
Maintenance 4-1
AD Administration Overview
Once you respond to these prompts, AD Administration displays the main menu,
which serves as the gateway to various submenus where you select the individual
maintenance tasks. For example, on the Generating Applications Files menu, you can
run tasks that generate message files, forms files, report files, message files, or product
JAR files. These submenu tasks may also require you to respond to prompts to collect
task-specific information. For example, some tasks require you to enter the number of
workers you want to employ to process the jobs associated with the task.
When you respond to AD Administration prompts, you are running the utility
interactively. However, like AutoPatch and AD Controller, you can also run AD
Administration non-interactively — specifying a previously created defaults file that
contains the information necessary to run a specific maintenance task without user
intervention.
Prompts
In addition to the basic prompts described in Chapter 1, AD Administration may
require additional information that is specific to one of the submenu tasks. If so, it
displays additional prompts. For example, when running the Generate Product JAR
files task from the Generate Applications Files menu, AD Administration prompts you
as follows:
Do you wish to force generation of all jar files? [No]:
The task-specific prompts are described more fully in the discussion of each task.
The following table lists the menu options and the corresponding menu tasks:
Main Menu
After you start AD Administration and respond to the prompts, the AD
Administration Main Menu appears.
Maintenance 4-3
AD Administration Overview
This menu displays the submenus where the individual maintenance tasks are
grouped. To choose a submenu, type the number of the menu at the prompt. To exit
AD Administration, press [Return].
Option Numbers
The submenus for AD Administration may display slightly different option names
and numbers from the ones shown here based on your system configuration.
If system users are having difficulty accessing messages, forms, or reports, you may be
able to resolve the issue by generating the associated files. Or, when you apply a patch
that adds or changes product functionality, you may want to generate the associated
files after you apply the patch, instead of running the generate driver during the
patching downtime. The generate files tasks may be performed on any server, as
required.
Note: You do not have to shut down your system to generate files.
However, users that access the files being generated (for example,
for Human Resources forms) must log off.
Maintenance 4-5
Generating Applications Files
If you choose No, it generates only JAR files that are missing or out-of-date. If you
choose Yes, all JAR files are generated.
Some of these tasks are performed for you without having to run AD Administration.
For example, each time you run AutoConfig, it creates the environment file. However,
when required, you can run any of these tasks by choosing it from this menu. They
may be performed on any server, as required.
Maintenance 4-7
Maintaining Applications Files
The environment file is placed directly under the APPL_TOP (UNIX) or under the
\\HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\APPLICATIONS\12.0.0
subkey (Windows registry).
If you need to customize this file, you can do so using AutoConfig in the Oracle
Applications Manager.
The file types and their respective destinations are shown in the following table:
The directories for the variables are specified in the adovars.env file (UNIX) or the
adovars.cmd file (Windows).
When you choose this option, AD Administration presents another submenu, which
contains options for scanning your files in preparation for the conversion. The scan
searches for exceptions — files that will have incomplete (lossy) conversions — so that
you can fix potential problems before you actually convert the character set. Choose
one of the following scan options.
File Contents
admanifest_excp.lst Lists files that will not be converted because of lossy conversion.
admanifest.lst Lists files that can be converted.
admanifest_lossy.lst Lists files with lossy conversions, including line by line detail.
Review the files listed in admanifest_excp.lst. Fix files that report lossy conversion
before you convert the character set. Repeat this task until there are no entries in
admanifest_excp.lst. If you need to see more detail, review admanifest_lossy.lst.
2. Scan a CUSTOM directory for exceptions.
Collects the same information as the first task, but scans custom Applications
directories rather than the APPL_TOP directory.
3. Convert character set.
Run this task only if admanifest_excp.lst has no entries. It prompts you for the
manifest file (admanifest.lst) created when you ran the scan option(s).
The utility backs up the product source files and the APPL_TOP/admin source
files. It saves product files in the <PROD>_TOP directories in the format <prod>_
s_<char_set>.zip. It saves admin source files in the APPL_TOP/admin directory in
the format admin_s_<char_set>.zip
Maintenance 4-9
Maintaining Applications Files
2. Choose an option.
From this menu, you can:
■ List snapshots (stored in the system)
■ Update current view snapshot (full or partial APPL_TOP and global)
■ Create named snapshot (select a current view snapshot to copy and name)
■ Export snapshot to file (select one to export to a text file)
■ Import snapshot from (a text) file
■ Delete named snapshot (select a snapshot for deletion)
2. From the Maintain Current View Snapshot Information menu, select one of the
following options:
■ Update Complete APPL_TOP
This is the original functionality of the Update Current View Snapshot option.
It synchronizes all the files in your APPL_TOP.
■ Update JAVA_TOP only
Synchronizes only the files in the JAVA_TOP. At the prompt, enter the path to
the JAVA_TOP subdirectory where the files were copied. If the files were
copied to more than one directory, press Enter. AD Administration scans the
entire JAVA_TOP and updates the information in both the current view and
the global view snapshots.
■ Update a <PRODUCT>_TOP
Synchronizes only the files in a specific <PRODUCT>_TOP. Enter the product
abbreviation, then provide the subdirectory information at the prompt.
Enter the path to a single subdirectory in the <PRODUCT>_TOP. If the files
were copied to more than one directory in the <PRODUCT>_TOP, press
Enter. AD Administration scans the entire <PRODUCT>_TOP and updates
the information in both the current and the global view snapshots.
Maintenance 4-11
Managing Database Entities
You run the tasks on this menu any time you need to compile or reload database
objects. For example, after you upload new menu entries or apply a patch that changes
the setup of flexfields. Run these tasks only on the node where the core AD technology
directories (the administration server) are located.
Note: The need for a separate MRC schema has been removed in
this release, as has the associated prompt to run Invoker Rights.
Compile flexfields
Compiles flexfield data structures in Oracle Application Object Library (FND) tables.
Choose this task after you apply a patch that changes the setup of flexfields. Patches
usually indicate when you should perform this step.
Flexfields automatically compile data when you use them for the first time, so running
this task is not required. However, compiling flexfield data at a specific time (for
example, when system use is low), rather than automatically at first use, can alleviate
potential runtime performance issues.
Some tasks on this menu report on issues, or potential issues, with database entities,
and others actually remedy the issues. Run these tasks only on the node where the core
AD technology directories (the administration server) are located.
Maintenance 4-13
Changing Maintenance Mode
Caution: If the DUAL table does not exist, or if it does not contain
only one row, the Applications products that access it will fail.
Choose Change Maintenance Mode from the AD Administration Main Menu. The
menu appears, displaying the current maintenance mode status at the top of the
screen.
AD Relink
You use AD Relink to relink AD executables with the Oracle server product libraries
to keep them functioning properly with the Oracle database. While you link product
executables using the Relink Applications Executables task on the AD Administration
Maintain Applications Files submenu, you cannot use it to relink an AD executable.
So, you must relink AD executables manually using AD Relink. You can relink
multiple AD executables simultaneously.
Log Files
As you run AD Relink, it creates a log file (adrelink.log) where it records errors and
messages. AD Relink appends information about the latest relink action to the end of
the file. This file is located in APPL_TOP/admin/log. If an error occurs while you are
using AD Relink, or if you are not sure that the relinking was successful, review this
file to see what issues should be fixed.
To recover disk space, you can delete the adrelink.log file if you do not need the
information. A new log file is created each time AD Relink runs.
force Description
Purpose indicates which executable programs to relink. This argument
is required.
Values n, meaning relink only if the libraries or object files are more
recent that the current executable program.
y, meaning relink regardless of the status of the libraries or
object files.
Default none (you must enter either y or n)
Example adrelink force=n
backup_mode Description
Purpose indicates whether you want to back up executables
Values none, meaning do not back up any executables
all, meaning back up all executables
file, meaning back up files according to instructions in
adlinkbk.txt
Default backup_mode=file
Example adrelink force=n backup_mode=all
Files that are critical to running Oracle Applications are listed in the adlinkbk.txt file,
which is located in APPL_TOP/admin. Using the backup_mode=file argument directs
AD Relink to back up only these files.
Maintenance 4-15
AD Relink
Running AD Relink
Run AD Relink as follows.
1. Set the environment.
You must set the environment to indicate the location of the configuration
parameters that define your system. This task is common to many AD utilities. See
Setting the Environment in Chapter 1.
2. Relink files.
Run AD Relink with the following command:
UNIX:
S adrelink.sh force=n "ad <executable name>"
Windows:
C:\> sh adrelink.sh force=n "ad <executable name>"
This chapter describes various reports and views of your system, including
information about patches you have applied to your system, statistics for maintenance
sessions and the time it takes to run them, and other important system information. It
contains the following sections:
■ About Oracle Applications Reporting Tools
■ AD Job Timing Report
■ AD Configuration Report
■ AD File Identification Report
■ AD Check Digest
Reporting Tools
These AD utilities are run from the command line.
AD Configuration Report
This report contains information about the installed configuration of Oracle
Applications, including product group information, whether Multi-Org or MRC
functionality is installed, base language and other installed languages, and so on.
Reporting 5-1
AD Job Timing Report
Windows:
C:\> cd %APPL_TOP%\admin\<SID>\out
C:\> sqlplus <APPS username>/<APPS password> @%AD_TOP%\admin\sql\adtimrpt.sql \
<session id> <output file>
AD Configuration Report
The AD Configuration utility is a SQL script that reports standard information about
the installed configuration of Oracle Applications. Run this task in order to debug or
document the status of your installation. Running AD Configuration generates a
report file (adutconf.lst) that contains the following:
■ SQL*Plus PAUSE and NEWPAGE settings
■ Rollback segment information
■ Information about the product group
■ Whether Multi-Org is installed and list of operating units
■ Whether Multiple Reporting Currencies (MRC) functionality is installed
■ List of registered products
■ Information on all registered schemas
■ Information about all installed products, including shared and dependent
products
■ Status of localization modules
■ The base language and other installed languages
■ NLS init.ora settings
Running AD Configuration
Run this utility as follows:
Windows:
C:\> cd %APPL_TOP%\admin\<SID>\out
C:\> sqlplus <APPS schema username>/<APPS schema password> \
@%AD_TOP%\sql\adutconf.sql
Reporting 5-3
AD File Identification Report
wfload.o:
wfload.oc 115.5.1100.3
libfnd.a:
fdacon.lc 115.0
fdatat.lc 115.0
fdastr.lc 115.0
fdaupd.lc 115.0.1100.2
fdahmi.lc 115.0.1100.2
fdacv.lc 115.0
fdfutl.lc 115.4
....
Windows:
C:\> adident Header %FND_TOP%\lib\wfload.obj %FND_TOP%\lib\fndst.lib
wfload.obj:
wfload.oc 115.5.1100.3
fndst.lib:
fdacon.lc 115.0
fdatat.lc 115.0
fdastr.lc 115.0
fdaupd.lc 115.0.1100.2
fdahmi.lc 115.0.1100.2
fdacv.lc 115.0
fdfutl.lc 115.4
....
You can also use an asterisk (*) to identify all files in a directory (For example, *.sql to
identify all SQL scripts).
Windows:
C:\> adident Header <file 1> [ <file 2> <file 3> ... ]
AD Check Digest
The AD Check Digest utility checks the integrity of downloaded patches. Oracle
provides MD5 and SHA-1 digests for each Oracle Applications patch. The MD5 digest
is a 128-bit string output that uniquely identifies the patch and the SHA-1 is a 160-bit
string output. The patch digests are viewable from the OracleMetaLink download page
for a particular patch. Use AD Check Digest to verify whether the computed digests
for the downloaded patch match the digests published on OracleMetaLink.
Parameters
The following parameters are used for running AD Check Digest.
Parameter Definition
-file Path and file name for the patch. This parameter is required. When
the -file parameter is used without the -md5 and -sha1 parameters,
AD Check Digest will compute the MD5 and SHA-1 digests for the
patch.
-md5 The MD5 output from the OracleMetaLink patch download page.
When you use the -md5 parameter, AD Check Digest compares the
MD5 value you provide with the MD5 digest computed for the
patch file.
-sha1 The SHA-1 output from the OracleMetaLink patch download page.
When you use the -sha1 parameter, AD Check Digest compares the
SHA-1 value you provide with SHA-1 digest computed for the
patch file.
Reporting 5-5
AD Check Digest
Windows:
C:\> adchkdig -file <File> [ -md5 <MD5_digest> -sha1 <SHA-1_digest> ]
A AD utilities
AD Administration, 4-1
AD Administration AD Check Digest, 5-5
about, 4-1 AD Configuration, 5-3
adadmin, 4-4 AD Controller, 1-18
Change Maintenance Mode menu, 4-14 AD File Identification, 5-4
Compile/Reload Applications Database Entities AD Splicer, 3-2
menu, 4-11 AutoPatch, 2-7
Generate Applications Files menu, 4-5 Character Set Converter, 3-4
Main Menu, 4-3 command line arguments, 1-9
Maintain Applications Database Entities common operations, 1-5
menu, 4-12 configuration files, 1-7
Maintain Applications Files submenu, 4-7 environment files, 1-7
maintain snapshot, 4-9 feature versions, 1-8
Maintain Snapshot Information menu, 4-10 flags, 1-12
menu options for non-interactive operation, 4-3 interactive processing, 1-5
prompts, 4-2 log files, 1-6
running non-interactively, 4-2 non-interactive processing, 1-5
starting, 4-4 parallel processing, 1-16
AD Check Digest, 5-5 prompts, 1-5
AD Configuration restart files, 1-6
about, 5-3 restarting, 1-15
adutconf.sql, 5-3 running, 1-13
AD Controller starting, 1-15
about, 1-18 stopping, 1-15
running non-interactively, 1-19 temporary disk space, 1-14
starting, 1-18 adadmin, 1-2, 4-4
AD File Identification, 5-4 adaimgr, 1-2
AD Job Timing report
adchkdig, 1-2, 5-5
about, 5-2 adconfig.txt, 1-7
adtimrpt.sql, 5-2 adctrl, 1-2, 1-18
running, 5-2 adident, 1-2, 5-4
AD Relink admrgpch, 1-2
about, 4-14 adncnv, 1-2, 3-4
adrelink.sh, 4-16 adovars.cmd, 1-7
command line arguments adovars.env, 1-7
backup_mode, 4-15 adpatch, 1-2
force, 4-15 adrelink.sh, 1-2, 4-16
log file, 4-15 adsplice, 1-2, 3-4
running, 4-16 adtimrpt.sql, 1-2, 5-2
AD Splicer, 3-2 adutconf.sql, 1-2, 5-3
adsplice, 3-4 APPL_TOP
control files, 3-2 missing files, 4-10, 4-11
newprods.txt, 3-3 snapshots, 4-9
product definition files, 3-2 application tier file system
running, 3-3 shared, 1-16
Index-1
Applications files executable programs
generating, 4-5 relinking, 4-7
maintaining, 4-7
applora.txt, 1-7
F
applorau.txt, 1-7
applprod.txt, 1-8 File Character Set Converter
applterr.txt, 1-8 about, 3-4
APPS schema adncnv, 3-4
compiling with AD Administration, 4-12 running, 3-4
validating with AD Administration, 4-13 files
AutoPatch copying (to destinations), 4-8
about, 2-7 generating JAR files, 4-6
generating message files, 4-5
flexfield data
C compiling, 4-12
character set FND_INSTALL_PROCESSES table, 1-15
converting, 3-4, 4-8 FND_MENU_ENTRIES table, 4-12
command line arguments fndenv.env, 1-8
AD Utilities
abandon, 1-9
G
defaultsfile, 1-9
flags=logging, 1-12 grants and synonyms
flags=nohidepw, 1-12 recreating, 4-13
flags=trace, 1-13
help, 1-10 J
interactive, 1-10
logfile, 1-10 JAR files
printdebug, 1-11 generating, 4-6
restart, 1-11 reloading, 4-12
wait_on_failed_job, 1-11
configuration files, 1-7 L
adconfig.txt, 1-7
log files
applora.txt, 1-7
about, 1-6
applorau.txt, 1-7
applprod.txt, 1-8
applterr.txt, 1-8 M
CONTEXT_NAME, 1-7
maintenance mode
disabling, 4-14
D enabling, 4-14
menu data structures
database entities
compiling, 4-12
compiling, 4-11
menu information
maintaining, 4-12
compiling, 4-12
reloading, 4-11
message files
Distributed AD, 1-16
generating, 4-5
documentation library
multi-lingual tables
contents, viii
maintaining, 4-13
DUAL table
verifying, 4-14
N
E newprods.txt, 3-3
environment
setting, 1-13 O
environment file
OAM see Oracle Applications Manager
creating, 4-7
online help
environment files, 1-7
command line, 1-3
adovars.cmd, 1-7
OAM Help, 1-4
adovars.env, 1-7
Oracle Application Object Library (AOL)
fndenv.env, 1-8
compiling flexfields in tables, 4-12
envshell.cmd, 1-13
Index-2
Oracle Applications
maintaining, 4-1
Oracle Applications Manager (OAM)
about, 1-2
accessing maintenance utilities, 1-22
Applications Dashboard, 1-21
common operations, 1-21
help, 1-4
Site Map, 1-4
Oracle Store
URL, viii
P
parallel processing
about, 1-16
distributing across nodes, 1-20
preface
PT PrefaceTitle, vii
products
off-cycle
about, 3-2
registering, 3-2
splicing, 3-2
PT PrefaceTitle, vii
R
Rapid Install
running, 2-5
restart files, 1-6
S
server libraries
relinking with executables, 4-7
snapshots
creating, 4-9
current view, 4-9
global, 4-9
maintaining, 4-9
named view, 4-9
synonyms
recreating with AD Administration, 4-13
system maintenance, 4-1
U
utilities
AD, 1-1
command line, 1-1
web-based, 1-2
W
Web-based utilities, 1-20
Windows services
configuring, 1-14
worker
child processes, 1-17
log files, 1-17
Index-3
Index-4