About Oracle Applications DBA Minipack 11i.AD.I [ID 233044.1]

  Modified 13-JAN-2011     Type README     Status PUBLISHED

 

About Oracle Applications DBA Minipack 11i.AD.I

Last revised: July 29, 2009

See Change Record

This About document provides a complete, up-to-date description of Oracle Applications DBA minipack 11i.AD.I. The most current version of this minipack is 11i.AD.I.7 (7429271). It replaces Oracle Applications DBA minipack 11i.AD.I.6, and contains 11i.AD.I.2 and all patches applied to this minipack since its initial release. The information contained in this document, including the instructions for applying this minipack to 11i systems and as a part of a pre-11i upgrade, pertain to any version of 11i.AD.I.x, (11i.AD.I.2 through 11i.AD.I.7).

You should read and understand all tasks described here before you begin your installation. The most current version of this document (Doc ID: 233044.1) can be found on OracleMetaLink. Be sure that you have the most current version before you begin.

Note:

Oracle Applications DBA minipack 11i.AD.I.7 (7429271) replaces Oracle Applications DBA minipack 11i.AD.I.6 (6502082). Minipack 11i.AD.I.7 contains 11i.AD.I.2 and patches 4502904, 4605654, 5161680, 6502079 and 7429248. If you have already applied 11i.AD.I.2, then, you need only apply patch 7429248 to update your system.

You can safely move from 11i.AD.I.2 to 11i.AD.I.7.

Attention:

Oracle Applications DBA minipack 11i.AD.I.x can be applied only to an existing Oracle Applications Release 11i system. If you are not already running Release 11i, you must first install the Oracle E-Business Suite. See Installing Oracle Applications, Release 11 i (11.5.10) or Upgrading Oracle Applications, Release 11 i (11.5.10) , and Oracle Applications Release Notes, Release 11 i (11.5.10) .

How to Use this Document

This About Document contains the following information about Oracle Applications DBA minipack 11i.AD.I.x.

1. New and Changed Features 2. New and Changed Components

3. New and Changed Setup Steps

4. Major Release Enhancements for AD.I

5. Known Issues

6. Instructions for Applying DBA minipack 11 i .AD.I.7 (11 i systems only)

7. Instructions for Applying DBA minipack 11 i .AD.I.7 (as part of a pre-11 i upgrade)

8. Implementation and User Documentation

9. Software Updates

10. Change Record

Target Audience

The Database Administrator: Installs and configures the Oracle database and maintains database access controls.

The System Administrator: Responsible for administering systems.

Prerequisite Patch Application Instructions

You must have already completed an installation of, or upgrade to, Oracle Applications Release 11i before advancing to Oracle Applications DBA minipack 11i.AD.I.x. The patch application instructions in this document are appropriate for starting from any earlier version of Oracle Applications DBA Release 11i.

If you are not already running Release 11i , consult the related installation documentation, located on the Oracle Applications E-Business Documentation Library on OracleMetaLink.

Additional Product Information

After you determine which new and changed features affect your system, refer to the most recent version of the Maintaining Oracle Applications Documentation Set for more information. In addition, this document contains information about DBA enhancements included in this minipack.

1. New and Changed Features

Oracle Applications DBA has added or changed the following features since the release of minipack 11i.AD.H. If you are advancing from a release of Oracle Applications DBA that is earlier than 11i.AD.H,

refer to the About document or readme file for each minipack that you are omitting for descriptions of additional new or changed features.

New Features

AD Secure Software Check

The AD Check Digest utility checks the integrity of files downloaded from Oracle. Oracle provides MD5 and SHA-1 checksums for each Oracle Applications patch. The AD Check Digest can compute the checksums for the downloaded patch and also compare a given checksum with that of the downloaded patch. See Oracle Applications Maintenance Utilities for details.

AD Administration and AD Controller Support for Non-interactive Mode

The non-interactive mode of AD Administration (adadmin) has been expanded to include all tasks. AD Controller (adctrl) has been updated to run in non-interactive mode.

AD Merge Patch Utility - Support for Merging Zip Files

Merging patches used to require unzipping each ARU patch zip file before you could merge the patches. AD Merge Patch can now create a merged patch from a set of ARU zip files. You list the ARU zip files in a manifest file, then point AD Merge Patch to the manifest during the merging process.

AutoConfig Integration with AutoPatch

AutoPatch automatically calls AutoConfig to instantiate and run new templates contained in a patch. When AutoPatch is run in test mode, AutoConfig also runs in test mode. AutoConfig test mode identifies the configuration files that would have been updated had the patch been applied in normal mode. Minipack AD.I.7 contains ADX.E.[1], which includes the latest enhancements to AutoConfig.

Creation of Large Indexes Using Parallel Slaves

To help reduce downtime, large indexes can now be automatically created using parallel slaves if the table is larger than a specified threshold.

Distributed AD

Patch downtimes can be significantly reduced by better increasing the number of workers utilized during an AutoPatch session. Distributed AD allows you to start AD workers on any node of a Shared APPL_TOP system. For more information, see OracleMetaLink Document 236469.1.

Eliminate MRC Maintenance Overhead (11.5.10)

The APPS_MRC Multiple Reporting Currencies schema is obsolete. MRC-related functionalities are maintained in the product base schemas.

Maintenance Mode

Maintenance mode provides a clear separation between normal runtime operation of Oracle Applications and system downtime for maintenance. Enabling the maintenance mode feature shuts down the Workflow Business Events System and sets up function security so that no Oracle Applications functions are available to users. Used only during AutoPatch sessions, maintenance mode ensures optimal

performance and reduces downtime when applying a patch. For more information, refer to Preparing your System for Patching in Oracle Applications Maintenance Utilities.

Patch and File History XML Reports

SQL report files that generate XML reports of patch and file histories of an Oracle Applications system are now available. These reports can be used to view patch history information for different systems in your environment.

Changed Features

AD Merge Patch Updates

AD Merge Patch has been enhanced to perform merges based on meta-data when merging patches that contain only unified drivers. This type of merge removes duplicate database driver lines when creating merged patches.

AutoPatch Prerequisite Patch Check

The default functionality of checking for prerequisite patches has changed so that AutoPatch no longer checks for patch prerequisites. You can turn on prerequisite checking by adding options=prereq to the AutoPatch start command.

Defer AutoPatch Patch History Upload

To reduce downtime for patching, you can use two new command-line options to defer patch history upload: during downtime, use the first command to run AutoPatch without uploading patch history information, then during uptime, use the other command to run AutoPatch so that it performs only the patch history information upload.

AD Utility Timing Information in OAM

The In Progress or Completed status of an AutoPatch or an AD Administration session is accessible from the Oracle Applications Manager (OAM), where information such as how many jobs have been completed or are remaining can be monitored. The OAM Timing Reports also capture job timing information and total times for AutoPatch and AD Administration sessions. Previously, timing information was stored in the AD Timing Report, a file in the file system. The OAM Timing Reports feature moves the contents of this file to database tables. This feature is available in OAM.H.

AutoPatch Writes Copy Action Details to the Informational Log File (.lgi)

As AutoPatch backs up files from the file system or copies files to the file system, it writes detailed information about these actions to the .lgi file, instead of to the .log file as in prior versions of AD.

Improved adalldefaults.txt Support

All menu options in AutoPatch and AD Administration offer defaults file support. All options have been integrated into one adalldefaultsfile.txt, which also contains an improved explanation as to what menu options the Name/Value pairs map to. The adalldefaultsfile.txt is now created and maintained by AutoConfig.

Improved Java Servlet Page Compilation

To reduce unnecessary downtime, AutoPatch compiles Java Server Pages (JSP) only if the APPL_TOP on which it is run is implemented as a Web server type.

Improved Patch History for Partially Applied Patches

While applying the copy portion of a patch, a mismatch between the file version on the file system and the database may occur if the patch process does not run to completion and is abandoned. To ensure that the correct version is recorded, patch history information is now recorded immediately following the copying of new files.

More Help Options for all AD Utilities

Command line Help content for all AD utilities displays all options and usages for the utility. To use help, type the help option on the command line after the program name. For example, for help information about AutoPatch, type adpatch help=y.

ODF Support Locally Managed Tablespaces - Sequence Caching

Support for all locally managed tablespace extent allocation types is now provided for objects managed through Object Description Files (ODFs). In addition, sequence cache values that have a value greater in the database than contained in the ODF remain unmodified.

2. New and Changed Components

This section lists the components that were added or changed for Oracle Applications DBA minipack 11i.AD.I.x. The components detailed here may have significant impact on existing customizations and/or extensions currently implemented on the system. You should review and understand the implications of these updates. For additional information, see the Oracle Electronic Technical Reference Manuals ( e TRM) on OracleMetaLink.

New User Interfaces Changed User Interfaces

New Reports

Changed Reports

New User Interfaces

None

Changed User Interfaces

AD Administration - AD Administration menus have been slighlty remodeled to improve usability.

New Reports

Sql files have been introduced to generate Patch History XML reports.

Changed Reports

None

3. New and Changed Setup Steps

There are no setup steps as a result of apply this patch. About Documents for previous Oracle Applications DBA releases are available on OracleMetaLink.

4. Major Release Enhancements for AD.I

Major enhancement for AD.I.2

Changed adncnv utility to take file list before doing the character set conversion instead of taking one file at a time. Added -logfile option to adncnv by redirecting the stdout and stderr to the log file. admerge.pl utility is also enhanced to call the modified adncnv.

Major enhancement for AD.I.3

This patch contains only bug fixes

Major enhancement for AD.I.4

This patch contains only bug fixes

Major enhancement for AD.I.5

Implemented the feature to hide the system password when running AutoPatch utilities.

Major enhancement for AD.I.6

Modified adpchlst.sql script, so that the is_patch_applied function is called to determine if the patch has been applied on the APPL_TOP. The script is also modified to list patches that have been applied between specified start_date and end_date for each and every appltop. Provided a new command line option to AutoPatch, backup=pathname. With this option, backup will be taken at this location instead of the patchtop, provided the location exists and is writable. If this command line option is not given, the default is patchtop. Enforced a restriction when merging patches, so that the merged file name is not longer than 30 characters. Allowing customers to merge patches with a much longer name will result in patch application error. When merging NLS patches with the same file version, different level, admrgpch utility takes the highest level information.

Major enhancement for AD.I.7

AutoPatch will no longer spawn the FNDLOAD process, instead FNDLOAD will be called from an API, saving significant performance time. AD Merge Patch should always merge using the higher version of the file. To get the higher version, all segments of the version numbers will now be compared. AD Merge Patch crashed when merging big patches on AIX. This has been resolved by resetting the data segment size to the correct value. When running AD in non-interactive mode, changes were made to prompt a user to enter the password value as standard input. The command line option used for prompting a user to input a password is stdyn=yes/no. AD can now support up to 7 characters for product abbreviation, instead of 4 characters.

5. Known Issues

Oracle Applications DBA minipack 11i.AD.I.x contains the following known issues:

Troubleshooting

1. Failures while applying the copy driver in normal mode

If you have implemented multiple APPL_TOPs and do not follow the instructions in the Section 5 section, you may encounter errors when writing patch history information to your database at the end of an AutoPatch session.

AutoPatch may report an error, then write the patch history information to files on the file system instead. In this case, the information saved to the file system can be uploaded to the patch history tables by using the "adpatch uploadph=y" command.

AutoPatch could also fail, depending on your AD code level at the time you apply this minipack. If this happens, apply (7429271) in pre-install mode:

$ adpatch preinstall=y

Then, re-apply (7429271) in normal mode.

The errors described in this section may also occur if your AD executables and database objects were out of synch before you started to apply this minipack. The workarounds previously described may enable you to successfully apply this minipack even if your AD executables and database objects were originally out of synch.

2. Failures while applying the copy portion in pre-install mode

If this minipack is being applied in pre-install mode, it may fail with the following message:

"adsetenv.sh" not found in "admin" directory under your APPL_TO

As a workaround, create the file $APPL_TOP/admin/adsetenv.sh. The contents of the file are not relevant. AutoPatch only checks to see if the file is present.

Acceptable Error and Warning Messages

1. Non-fatal error uploading the list of modified Java classes to the database

Depending on your AD version when applying this minipack, you may encounter the following error in the AutoPatch log file when applying the copy portion:

Unknown Database Error :ORA-01403: no data foundError: Getting bug_run_id for the bug_number:one AutoPatch error:Unable to upload Java Classes to Database

You can safely ignore this error as long as AutoPatch continues after the error occurs.

2. Non-fatal error updating the current-view snapshot

Depending on your AD version when applying this minipack, you may encounter the following error in the AutoPatch log file when applying the copy portion of this patch:

Updating the current-view snapshot... ORA-06502: PL/SQL: numeric or value error: character to number conversion errorORA-06512: at line 2

You can safely ignore this error as long as AutoPatch continues after the error occurs.

3. Warnings about removing resource units that don't exist

You will likely see warnings like the following in the AutoPatch log file when AutoPatch is processing adrmoad.txt as part of updating Oracle Applications Java classes. This is most likely to occur when applying the database portion of this minipack, but could also occur when applying the copy portion.

Warning: oracle/apps/fnd/3rdparty/stdalone/OracleApplications2 -Invalid entry. No resource unit matching this pattern found.

You can safely ignore these warnings. They occur because the file to remove has already been removed.

4. Warning about not being able to find apps.zip

You may also see a warning like the following in the AutoPatch log file when AutoPatch updates Oracle Applications Java classes:

adearea(); Warning=> unable to locate /d7/autodriver/apps/pseudo25comn/java/apps.zip file.

You can safely ignore this warning. It is caused by the change in the architecture for maintaining Oracle Applications Java files in this minipack. (Java files were formerly maintained inside the apps.zip file. They are now maintained under JAVA_TOP.)

5. Warnings about unrecognized products

Applying this minipack on a database where some Release 11.5.10 products are not registered may produce warnings in the AutoPatch log file or AutoPatch informational messages file. If you see warnings like the following in either log file, you can safely ignore them.

WARNING: 'okr' is not a recognized product.The following entry is now disabled:

6. Warnings about JAVA_TOP being a duplicate area when generating JAR files

You may see a warning like the following in your AutoPatch log file when generating JAR files:

WARNING: Duplicate area : /u02/appljeff/p1152comn/java/JAVA_TOP

You can safely ignore this warning. It is caused by the change in the architecture for maintaining Oracle Applications Java files.

7. Warning about unimplemented/unrecognized extension command in the patch driver file

You may see a warning like the following in the AutoPatch log file when applying the copy portion of this minipack:

'extension patch_type software' is not currently implemented.

You can safely ignore this warning. This minipack introduces code changes that recognize this extension command, but the copy portion of the minipack is applied using your existing AutoPatch executable, which is not likely to recognize this extension command.

8. Warning about FNDSCMOU.fmx form generation failure

AutoPatch does not use any forms. You can safely ignore this warning.

Runtime Impact

This minipack has little to no impact on the functional runtime behavior of non-AD Oracle Applications products. It does contain files for products other than AD. However, these files should have no impact on the functional behavior of the non-AD products. You should not need to re-run functional tests for these non-AD products after applying this minipack. This does not preclude the need to perform system configuration validation. Examples of configuration validation include, but are not limited to, verifying all services are working, navigating through forms as the system administrator responsibility, and validating connectivity.

References

Refer to the latest 11 i Applications Recommended Patch List (OracleMetaLink Document 123456.1) to see if you should apply any additional Oracle Applications DBA patches on top of Oracle Applications DBA minipack 11i.AD.I.7.

6. Applying DBA Minipack 11i.AD.I.x (11i systems only)

This section contains instructions for updating an earlier version of Oracle Applications DBA to minipack 11i.AD.I.x. The steps are cumulative and apply to all versions since the base release of 11i (11.5.1).

Note:

Do not use the information in this section if you are updating your OA DBA version to 11i.AD.I.x during an upgrade from Release 10.7 or 11.0 (pre-11i) to Release 11.5.10 or 11.5.9 of Oracle Applications. Instead, follow the steps in Section 6.

In general, applying this minipack requires three actions:

Apply prerequisite patches (if any) Apply Minipack 11i.AD.I.x

Perform post-minipack application steps

Additional Information:

Tasks included in these instructions require use of AutoPatch, AD Administration, and other AD utilities. For information about how to use these utilities, see Oracle Applications Maintenance Utilities, Release 11 i .

If you have languages other than American English licensed in your installation, apply the translated versions (if they exist) of each Oracle Applications patch referenced in these instructions immediately after applying the American English version, unless the instructions state otherwise.

There may be both technical and functional steps required to apply this minipack. Functional steps may require assistance from someone who is familiar with Applications setup and use, and with business processes at your enterprise.

Note:

This minipack contains updated versions of many system files. Applying it updates any file whose version is older than the version included in this minipack. (AutoPatch skips any file that is already current on your system.) To identify the files that will be updated on your system, see "Determing the Impact of a Patch" in Oracle Applications Maintenance Procedures.

System Requirements

Make sure your system meets the following requirements before you begin the process of applying this minipack.

Perl executable

You must have the Perl executable (5.004 minimum; 5.005 perferred) in your PATH before you apply this minipack. You should have already installed Perl as part of your iAS ORACLE_HOME. See http://www.cpan.org for information on obtaining Perl.

FNDLOAD executable

Ensure all application tier server nodes contain the FNDLOAD executable in the $FND_TOP/bin directory. If the executable is not present, apply patch 2684116 on all nodes. When applying this AD minipack, apply it on all forms/web server nodes first, and then on the administration server node.

Perform Pre-minipack Steps

Complete the following steps before you apply the minipack. If you have already completed any of these steps during a previous 11i patch application, you do not need to repeat the step, unless the instructions in this section specify otherwise.

Step 1: Apply prerequisites patches (required)

If your system release level is 11.5.7 or higher, apply the following prerequisite patches before you apply this minipack. The patches must be applied in order.If you have a windows platform, apply patch 6773659 before applying 11i.AD.I.6. This issue is fixed in 11i.AD.I.7 or later versions.

If you have already applied this minipack... Apply this patch...

AD minipack H (included in Release 11.5.9) or higher 3464936 (Windows only)

AD minipack G (included in Release 11.5.8) or higher 3464936 (Windows only)

AD minipack F (included in Release 11.5.7) or higher 3464936 (Windows only)

If you have not already applied Minipack F (or higher), locate the release level that applies to your system and apply the appropriate patches before you apply this minipack.

If your system release level is... Apply this patch...

11.5.3, 11.5.4, 11.5.5, or 11.5.6

2408149 (all platforms)*2237858 (Windows only)2985592 (Windows only)3464936 (Windows only)2648711 (Windows only)3150374 (all platforms)**

11.5.2 2408149 (all platforms)*2237858 (Windows only)1874355 (Windows only)2985592 (Windows only)3464936 (Windows only)

If your system release level is... Apply this patch...

2648711 (Windows only)3150374 (all platforms)**

11.5.1 2408149 (all platforms)*2237858 (Windows only)1363919 (all platforms)1981720 (all platforms)1874355 (all platforms)2985592 (Windows only)3464936 (Windows only)1363909 (Windows only)2648711 (Windows only)3150374 (all platforms)**

*For multi-node systems, apply the copy driver of this patch on all nodes, followed by the database driver on the administration node.**Apply only the copy driver

Step 2: Verify that you have implemented the apps.zip architectural change (conditionally required)

Unzip apps.zip under $JAVA_TOP on all application tier nodes, if you have not done so already.

Step 3: Convert to Multiple Organizations (Recommended)

Oracle Applications strongly recommends that you convert to Multi-Org as soon as possible so that you will be prepared for improvements to performance across the E-Business Suite as well as support for Multi-Org Access Control.

For more information, see Release 11 i Use of Multiple Organizations in Oracle Applications (OracleMetaLink Document 210193.1).

Apply the Minipack

This minipack contains a unified patch driver and may contain additional driver files to be applied with AutoPatch. Apply the unified driver file on all application tier server nodes.

Post-minipack Steps

Once you have successfully applied this minipack, you must complete some additional steps. If you have completed any of these steps during a previous 11i patch application, you do not need to repeat the step, unless the instructions in this section specify otherwise.

Step 1: Grant privileges and create PL/SQL profiler objects

If this is not already done as a pre-step, run the adgrants.sql script as a user that can connect as SYSDBA to grant privileges to selected SYS objects and create PL/SQL profiler objects.

1. Create $ORACLE_HOME/appsutil/admin on the database server.

2. Copy adgrants.sql (UNIX) from $APPL_TOP/admin to $ORACLE_HOME/appsutil/admin. Or, copy adgrants_nt.sql (Windows) from %APPL_TOP%\admin to %ORACLE_HOME%\appsutil\admin.

3. Set the environment to point to ORACLE_HOME on the database server.

4. Use SQL*Plus to run the script:

UNIX:

$ sqlplus /nologSQL> @$ORACLE_HOME/appsutil/admin/adgrants.sql APPS

Windows:

C:\> sqlplus /nologSQL> @%ORACLE_HOME%\appsutil\admin\adgrants_nt.sql APPS

Step 2: Unzip apps.zip under $JAVA_TOP (conditionally required)

If you have already unzipped apps.zip, go on to Step 3.

Verify whether apps.zip has been unzipped. If the file exists in your $JAVA_TOP directory, it has not been unzipped. If it doesn't exist in $JAVA_TOP, it has already been unzipped.

If you are unzipping apps.zip as a post-minipack step, you must apply patch (5161676). This patch includes a driver file (explode.drv) that unzips apps.zip. If you do not apply this patch, the Maintain Snapshot functionality will not work correctly.

Note:

You must enable maintenance mode before applying this driver file. For more information, see Preparing your System for Patching in Oracle Applications Maintenance Utilities, Release 11 i .

Change directories to $AD_TOP/patch/115/driver and run AutoPatch again. Answer explode.drv when prompted for the driver file:

Enter the name of your AutoPatch driver file: explode.drv

This driver will first remove unwanted entries from apps.zip, then unzip the file under $JAVA_TOP. For more information on the apps.zip rearchitecture, see OracleMetaLink Document 220188.1.

Step 3: Run AutoConfig

If you have not already implemented AutoConfig, you must do so now using the procedure in Using AutoConfig to Manage System Configurations with Oracle Applications (Oracle MetaLink Document 165195.1)

If your system is enabled to use AutoConfig, run AutoConfig to instantiate the templates used by the AD utilities. After you apply this minipack, AutoPatch automatically runs AutoConfig during each patch session. For more information, see Oracle Applications Maintenance Utilities, Release 11 i .

7. Applying DBA Minipack 11i.AD.I.x (as part of a pre-11i upgrade)

If you are applying this Oracle Applications DBA minipack while performing an upgrade from a pre-11i release (10.7 or 11.0) to Release 11.5.10 or 11.5.9, follow the steps in Upgrading Oracle Applications. When instructed to apply the AD minipack, refer to the steps in this section for the latest instructions.

Upgrading to Release 11.5.10

After you run AutoUpgrade, cimplete these steps in the order listed.

5. In Category 4, apply this minipack when instructed to do so. Use the following command:

adpatch options=nogenerateportion,hotpatch6. Continue with your upgrade process as described in Upgrading Oracle Applications.

Upgrading to Release 11.5.9

Apply the minipack and complete the sections in this section in the order listed.

7. In Category 2, when instructed to apply the AD minipack, apply on the copy portion of this minipack using the following command:

adpatch preinstall=y8. Perform the following manual step:

$ cp $AD_TOP/bin/adupdeul.sh $AU_TOP/discover/9. In Category 3, run AutoUpgrade using the following command:

adaimgr consolidated_tablespace=n

Note:

Converting to the new Oracle Applications Tablespace Model (OATM) during the upgrade to 11.5.9 is not supported. If you plan to convert to OATM, you can do so after the upgrade. For more information, see the Oracle Applications Tablespace Model (OATM) FAQ.

10. In Category 4, when instructed to apply the AD minipack, re-apply the Oracle Applications DBA minipack (7429271) using the following command:

adpatch options=nogenerateportion,hotpatch

11. Continue with the upgrade process as described in Upgrading Oracle Applications.

8.Implementation and User Documentation

The latest Oracle Applications E-Business Suite Documentation Library is available on the Oracle Technology Network (OTN). This "virtual" DVD contains the most current documentation, including all interim changes made to documentation since the initial release of Oracle Applications 11.5.10. It is updated once a quarter, unless you are notified otherwise.

There is no documentation patch for 11i.AD.I.x

9. Software Updates

See the readme file for ARU 7429271 for the bug list associated with this minipack.

10. Change Record

Date Description of Change

July 20, 2009 Completed update for 11i.AD.I.7

Mar 03, 2009 Added a reference to window fix 6773659. Implemented additional remarks.

Feb 23, 2008 Revised instructions to indicate that all information applies to any version of 11i.AD.I

Jan 18, 2008 Completed update for 11i.AD.I.6

May 10, 2007 Completed update for 11i.AD.I.5

April 18, 2006 Corrected AD.I.2 patch number

March 29, 2006 Completed the following changes:

o Updated for 11i.AD.I.4. o Moved instructions for applying

minipack during 10.7 or 11.0 upgrade from Section 5 to a new Section 6.

o General copy edit

July 27, 2005 Initial Release

Oracle Corporation

Copyright Information Copyright 1994-2010, Oracle Corporation. All rights reserved.

Trademark Information Oracle is a registered trademark of Oracle Corporation.

Related

Products

Oracle E-Business Suite > Applications Technology > Lifecycle Management > Oracle Application Install

Keywords

APPLY PATCH; 11I.AD.I; ADPATCH; E-BUSINESSErrors

ORA-6502; ORA-6512; ORA-1403