View stunning SlideShares in full-screen with the new iOS app!Introducing SlideShare for AndroidExplore all your favorite topics in the SlideShare appGet the SlideShare app to Save for Later — even offline
View stunning SlideShares in full-screen with the new Android app!View stunning SlideShares in full-screen with the new iOS app!
2. Run the environment or command file for the current APPL_TOP and database
3. If you have made any changes to the environment, check that they are correctly set
4. Ensure that there is sufficient temporary disk space
5. Shut down all concurrent managers if you plan to relink Oracle Applications product files or modify Oracle Applications database objects
The AD Utilities Manages parallel workers in AD Administration, and AutoPatch. AD Controller Applies patches and adds new languages and products. AutoPatch Performs maintenance tasks on the Oracle Applications file system and database. AD Administration Description AD Utility
The AD Utilities Registers off-cycle products. AD Splicer Merges multiple patches into a single, integrated patch. AD Merge Patch Relinks Oracle Applications executable programs with the Oracle server product libraries. AD Relink Description AD Utility
The AD Utilities Provides timing summary reports for jobs run by parallel workers. AD Job Timing Report Converts a file from one character set to another. File Character Set Converter Reports standard information about the installed configuration of Oracle Applications. AD Configuration Identifies the version of an Oracle Applications file. AD File Identification Description AD Utility
The Web-based Utilities Licenses products, country-specific functionalities, or languages. License Manager Updates the Applications context with new system configuration and helps manage the system configuration files. AutoConfig Description Utility
The Web-based Utilities Determines patches that have not been applied, but that should be applied to keep the system current. Downloads and merges patches from Oracle MetaLink . Patch Wizard Stores patch history information and allows you to query patch and file history information. Applied Patches Description Utility
Command Line Arguments - abandon n Default y or n Values Example Purpose Used by abandon AD Administration, AutoPatch adpatch interactive=n abandon=y Tells AD utilities to abandon an existing non-interactive session. Can be used only when interactive=n is also specified.
Command Line Arguments - defaultsfile None, meaning that no defaults file is used. Default A fully-qualified filename. Must be under the APPL_TOP/admin/<SID> directory. Values Example Purpose Used by defaultsfile AD Administration, AutoPatch adpatch defaultsfile=/d1/apps/prodappl/admin/prod1/prod_def.txt Specifies the defaults file, which stores answers to interactive AD utility questions. Normally used in non-interactive mode.
Command Line Arguments - help n Default y or n Values Example Purpose Used by help All AD Utilities adpatch help=y Summarizes available command line options.
Command Line Arguments - interactive y, meaning that the utility runs in interactive mode Default y or n Values Example Purpose Used by interactive AD Administration, AutoPatch adpatch interactive=n Tells AD utilities whether to run in interactive mode or non-interactive mode.
Command Line Arguments - localworkers Defaults to the value of the workers argument, which means all workers run on the primary node. Default 1 to the maximum supported by your database, but not more than 999, Inclusive Values Example Purpose Used by localworkers AD Administration, AutoPatch adpatch workers=8 localworkers=3 Specifies the number of workers to run on the primary node in a Distributed AD environment.
Command Line Arguments - logfile None, meaning that the utility will prompt for the log file name. Default A file name (not a fully-qualified path name) Values Example Purpose Used by logfile All AD Utilities adpatch logfile=test.log Tells AD utilities what log file to use. Normally used in non-interactive mode.
Command Line Arguments - menu_option n/a Default Varies. See utility specific section for details Values Example Purpose Used by menu_option AD Administration, AD Controller adctrl interactive=n defaultsfile=$APPL_TOP/admin/prod/defs.txt menu_option=SHOW_STATUS When running one of these utilities non-interactively, used to connect the actions in a defaults file with a specific menu item.
Command Line Arguments - parallel_index_threshold 20000; meaning a threshold of 20,000 blocks. Default 0 to 2147483647; if set to 0, indexes are created with parallel workers and serial DML Values Example Purpose Used by parallel_index_threshold AD Administration, AutoPatch adpatch parallel_index_threshold=15000 Specifies the number of blocks in a table.
Command Line Arguments - printdebug n Default y or n Values Example Purpose Used by printdebug All AD Utilities adpatch printdebug=y Tells AD programs to display extra debugging information. In some cases, the amount of extra debugging information is substantial.
Command Line Arguments - restart n, meaning that the utility run in non-interactive mode will expect to run a completely new session. Default y or n Values Example Purpose Used by restart AD Administration, AutoPatch adpatch interactive=n restart=y Tells AD utilities to restart an existing session in non-interactive mode. Only valid when interactive=n is also specified.
Command Line Arguments - wait_on_failed_job n Default y or n Values Example Purpose Used by wait_on_failed_job AD Administration, AutoPatch adpatch wait_on_failed_job=yes Directs the utilities to wait for user input in a non-interactive session when a job fails.
Command Line Arguments - workers None, meaning that the program will prompt for the number of workers to run. Default 1 to 999, inclusive Values Example Purpose Used by workers AD Administration, AutoPatch adpatch workers=6 Specifies the number of workers to run. Normally used in non-interactive mode.
Command Line Arguments - flags None, meaning that no flags have been passed. Default Information about specific flags are covered on the following pages. Values Example Purpose Used by flags All AD Utilities adpatch flags=hidepw Generic flags passed to AD utilities. Information about specific flags are covered on the following pages.
AD Utilities Flags - hidepw By default, lines in an AD utility log file containing passwords are modified to hide the passwords Comments Default Purpose flags=hidepw Directs the utilities to either hide or show passwords in AD Utility log files. hidepw
AD Utilities Flags - logging Use of NOLOGGING when creating indexes may increase performance. However, it also makes database media recovery incomplete, and does not work with standby databases. Comments Default Purpose flags=logging Tells the AD Utility whether to create indexes using the logging or nologging mode. logging
AD Utilities Flags - trace RDBMS trace files created while running an AD utility may aid debugging. Comments Default Purpose flags=trace Tells the AD Utility whether to log all database operations to a trace file. notrace
AD requires that the files on the file system and the tables in the database match
Each major feature now has both a file system and database version
AD only enables the feature if the file system and database versions match
AD Feature Versions The status of various features in this run of AD Administration is: <-- Feature version in --> Feature Active? APPLTOP Data model ----------------- ------- ------- ------------- CHECKFILE Yes 1 1 PREREQ Yes 6 6 CONCURRENT_SESSIONS No 2 2 PATCH_TIMING Yes 2 2 PATCH_HIST_IN_DB Yes 5 5 SCHEMA_SWAP Yes 1 1
While the utility runs, the manager will display text showing the current status of workers and jobs and the current phase:
There are now 16217 jobs remaining (current phase=con): 4 running, 42 ready to run, and 16171 waiting. Completed: file hrobsakw.sql on worker 2 for product per username HR. Time is: Tue Nov 17 2007 18:24:30 Assigned: file pjmcon1.drv on worker 2 on product pjm username PJM. Time is: Tue Jul 17 2007 18:24:30 This example shows that the AD utility has 16,217 jobs remaining, and that it is in the con phase
Key points to using Distributed AD are as follows:
You can start an AutoPatch or AD Administration session on any shared APPL_TOP node, specifying:
The number of local workers
The total number of workers (local + remote)
You can start an AD Controller session from any shared APPL_TOP node
Both local and non-local workers can be specified
Log Files AD Administration records your AD Administration session in a text file you specify. Enter your AD Administration log file name or press [Return] to accept the default name shown in brackets. Filename [adadmin.log] :
Are used by an AD utility to continue processing at the point where it stopped
Reside in the APPL_TOP/admin/ <SID>/restart directory
Contain information about what processing has already been completed, so that the utility can pick up where it left off
Manager and Worker Log Messages Assigned: file ad_wait1sec.sql on worker 1 for product ad username APPLSYS. FAILED: file ad_wait1sec.sql on worker 1 for product ad username APPLSYS. ATTENTION: All workers either have failed or are waiting: