Академический Документы
Профессиональный Документы
Культура Документы
EBS-1
EBS-2
EBS-3
EBS-4
Client: The requirements and processes on the user workstation Web Node: Web Server processes that run on the Web Node Forms Node: Forms Server processes that run on the Forms Node Concurrent Processing Node: Concurrent Manager processes running on the Concurrent Processing Node Admin Node: Administrative tasks executed on the Admin Node Database Node: Database services that run on the Database Node
EBS-6 2009 Cristian Stanca S.C. RomSoft S.R.L.
EBS-7
EBS-8
EBS-10
EBS-12
EBS-13
EBS-14
EBS-15
EBS-17
EBS-19
EBS-20
EBS-21
EBS-24
EBS-26
EBS-28
EBS-29
EBS-30
EBS-31
EBS-32
EBS-33
EBS-34
EBS-35
EBS-39
Most issues can be fixed by either compiling invalid database objects or recreating grants and synonyms.
EBS-40
EBS-42
EBS-43
EBS-45
EBS-46
Procedures available for gathering statistics with fnd_stats: fnd_stats.gather_schema_statistics: Gather statistics for schemas fnd_stats.gather_tables_stats: Gather table-level statistics fnd_stats.gather_column_stats: Gather column-level statistics fnd_stats.gather_index_stats: Gather index statistics
EBS-48 2009 Cristian Stanca S.C. RomSoft S.R.L.
EBS-49
EBS-50
One-off patch: This is the simplest type of patch. It is created to resolve a specific bug. Minipack patch: This is a collection of one-off patches and enhancements related to a particular module. Alphabetic characters denote the Minipack version for the module; for example, the product code for the Application DBA utilities is AD, and version Minipack I of this product would be called AD.I.
EBS-52 2009 Cristian Stanca S.C. RomSoft S.R.L.
EBS-53
Consolidated patch: This is a collection of one-off fixes for a Family Pack or Maintenance Pack; Oracle Applications 11.5.10 Consolidated Update 2 (CU2) is an example of a consolidated patch. Interoperability patch: This is a patch that is required for Oracle Applications to function with a newer version of a technology stack component; for example, you would apply an interoperability patch when upgrading the database to version 10g. NLS patch: This is a patch that updates languagespecific information for multi-language installations.
EBS-54 2009 Cristian Stanca S.C. RomSoft S.R.L.
Legislative patch: This is a special patch for HR Payroll customers; it contains legislative data for multiple countries.
EBS-55
EBS-56
EBS-59
EBS-60
EBS-62
EBS-63
EBS-64
Patching problems manifest themselves in many different ways. Typically the adpatch session will display an error or will appear to be hung on one task for a long period of time. The first step in resolving the issue is to review the adpatch log file and associated worker log file. Next, the reason the worker failed must be determined and resolved. After resolution has been obtained, adctrl can be used to continue the patching process.
EBS-65
Reviewing Log Files During and after the application of patches, it is helpful to review log files of the adpatch session and its workers. These files are found in the $APPL_TOP/ admin/$CONTEXT_NAME/log directory. The adpatch log filename is specified during the patch process. In order to monitor the patch from a telnet session other than the one where the patch was started, a simple UNIX command such as tail f u[patch#].log will display information as it is written to the log file. The log files for the workers will be named adwork[xxx].log, where [xxx] is the number of the patch worker process. If a particular worker has failed, examine the related log file for detailed information.
EBS-66 2009 Cristian Stanca S.C. RomSoft S.R.L.
Using AD Control The administrative tool used to manage patch workers is AD Control, or adctrl. Frequently workers will fail or hang, which will require the Oracle Applications DBA to interface with adctrl. To execute an adctrl menu option, simply type the menu option and press Enter. If options 26 are chosen, either specify the number of the worker that requires action, or press Enter for the action to be executed for all workers. The Skip Worker menu option is a hidden adctrl menu option. If a worker needs to be skipped, start adctrl, enter 8, and then enter the worker number. Only use this option if advised by Oracle Support.
EBS-67 2009 Cristian Stanca S.C. RomSoft S.R.L.
EBS-68
Resolving AD Patch Worker Failure If a worker has failed, the adpatch session will normally display a failedworker message. The status of the worker may also be determined using adctrl. If a worker has failed, the worker error can be obtained by viewing the worker log file. Once the worker issue has been resolved, use adctrl to restart the worker. If a worker has failed, and it is determined that the step the worker was trying to execute may be skipped, the hidden option 8 of the adctrl menu, Skip Worker, may be used to skip the worker. It is only advisable to do this if the step is not critical to the environment being patched.
EBS-69 2009 Cristian Stanca S.C. RomSoft S.R.L.
Additional Tips for Resolving Patching Issues If a patch has hung or workers have failed, and the reason for this failure cannot be determined, it is advisable to check the number of invalid objects in the database. If the number of invalid objects is high, recompile the invalid objects in parallel and restart the patching session. If the adpatch session is hung, and all other methods for resolution have been executed, it may be necessary to bounce the database and restart the patch session. This method for resolving patching issues is sometimes necessary, especially when applying large patches, such as Maintenance Packs.
EBS-70 2009 Cristian Stanca S.C. RomSoft S.R.L.
Additional Tips for Resolving Patching Issues If a failure occurs during the application of a patch, it may be necessary to apply another patch to resolve the issue. If this type of issue occurs during the application of a large patch, you may want to be able to restart the original patch from the point of failure. MetaLink Note 175485.1 provides details for applying a patch with adpatch already running.
EBS-71
EBS-74
EBS-76
EBS-77
EBS-78
EBS-79
EBS-80
EBS-81
EBS-82
EBS-83
EBS-85
EBS-87
EBS-88
EBS-89
EBS-91
EBS-92