Oracle Applications, Oracle Database, D49656, Oracle Applications DBA

1. Other Patching Topics Patching Topics

14. Using AutoPatch in Non-Interactive Mode Command to run AutoPatch in non-interactive mode: $ adpatch defaultsfile=$APPL_TOP/admin/testdb1/def.txt logfile=c123456.log patchtop=$APPL_TOP/patch/123456 workers=3 interactive=no

17. AutoPatch Command Line Arguments - apply Tells AutoPatch whether to run in test mode. Purpose Example Default Values apply y, meaning that AutoPatch does not run in test mode. n, meaning that AutoPatch does run in test mode. adpatch apply=n y

18. AutoPatch Command Line Arguments - driver Tells AutoPatch the name of the patch driver file. This is usually used in non-interactive mode. It is only valid when the AutoPatch patchtop option is also used. Purpose Example Default Values driver A driver file name, or comma-separated list of patch driver file names. adpatch patchtop=/d01/apps/patches/2344175 driver=u2344175.drv None, meaning that AutoPatch prompts for the patch driver file name.

19. AutoPatch Command Line Arguments - patchtop Tells AutoPatch the top-level directory for the current patch. This is normally used in non-interactive mode. Purpose Example Default Values patchtop A fully-qualified directory name. adpatch patchtop=/d01/apps/patches/2344175 None, meaning that AutoPatch prompts for the patch directory.

20. AutoPatch Command Line Arguments - preinstall Tells AutoPatch whether to run in pre-install mode. Pre-install mode is used to update AD utilities before an upgrade, and to apply family consolidated upgrade patches. Purpose Example Default Values preinstall y, meaning that AutoPatch runs in pre-install mode. n, meaning that AutoPatch does not run in pre-install mode. adpatch preinstall=y n

21. AutoPatch Command Line Arguments - uploadph Tells AutoPatch to upload patch history information from the patch information files to the database, and then exit. Purpose Example Default Values uploadph y, meaning that AutoPatch uploads patch history information; n, meaning that AutoPatch does not upload patch history information. adpatch uploadph=y None.

22. AutoPatch Command Line Arguments - options Pass generic options to AutoPatch. See the following slides for more information on available options. Purpose Example Default Values options A comma-separated list of options. adpatch options=autoconfig None, meaning that no generic options are passed.

23. AutoPatch Options - autoconfig Tells AutoPatch to run AutoConfig automatically. Purpose Comments Default options=noautoconfig autoconfig Use options=noautoconfig if you are applying a number of patches in sequence and want to run AutoConfig once, after applying the last patch of the sequence. A more common strategy is to merge the patches first using AD Merge Patch.

24. AutoPatch Options - checkfile Tells AutoPatch to either skip running SQL and EXEC commands if they are recorded as already run and to record them as having run after running them. Use nocheckfile to turn off the checkfile feature. Purpose Comments Default options=nocheckfile checkfile Using checkfile provides significant performance benefits.

25. AutoPatch Options - compiledb Tells AutoPatch to automatically compile invalid objects in the database after running actions normally found in the database driver. Purpose Comments Default options=nocompiledb compiledb for standard patches; nocompiledb for standard patch translations, documentation patches, and documentation patch translations. In cases where multiple non-merged patches are applied in a maintenance window, you can use nocompiledb to save time. However, merging multiple patches and applying a single merged patch is usually a better strategy.

26. AutoPatch Options - compilejsp Tells AutoPatch whether to automatically compile out-of-date JSP files. Purpose Comments Default options=nocompilejsp compilejsp for standard patches; nocompilejsp for standard patch translations, documentation patches, and documentation patch translations. JSP files are only compiled if the patch contains copy actions for at least one JSP file.

27. AutoPatch Options - copyportion Tells AutoPatch whether to run commands normally found in the copy portion of the driver. Purpose Comments Default options=nocopyportion copyportion Use nocopyportion to tell AutoPatch not to perform copy actions of the driver.

28. AutoPatch Options - databaseportion Tells AutoPatch whether to run commands normally found in the database portion of the driver. Purpose Comments Default options=nodatabaseportion databaseportion Use nodatabaseportion to tell AutoPatch not to perform database actions of the driver.

29. AutoPatch Options - generateportion Tells AutoPatch whether to run commands normally found in the generate portion of the driver. Purpose Comments Default options=nogenerateportion generateportion Use nogenerateportion to tell AutoPatch not to perform generate actions of the driver.

30. AutoPatch Options - hotpatch Tells AutoPatch to apply a patch regardless of whether the Oracle Applications system is in Maintenance Mode. Purpose Comments Default options=hotpatch nohotpatch AutoPatch aborts the patching session if Maintenance Mode is disabled and the options=hotpatch command is not used.

31. AutoPatch Options - integrity Tells AutoPatch whether to perform patch integrity checking, which verifies that the version of each file referenced in a copy action matches the version present in the patch. Purpose Comments Default options=integrity nointegrity As the integrity of Oracle Applications patches is checked before they are released, the default of nointegrity is safe and avoids some AutoPatch overhead.

32. AutoPatch Options - parallel Tells AutoPatch whether to run actions that update the database (such as) and actions that generate files (such as genform) in parallel. Use noparallel to tell AutoPatch to run actions serially. Purpose Comments Default options=noparallel parallel Oracle does not recommend using the noparallel option. Oracle Applications patches are tested on systems using parallel processing.

33. AutoPatch Options - phtofile Tells AutoPatch whether to upload patch history information to the database after applying the patch, or to write it to the patch information files in the file system. Purpose Comments Default options=phtofile nophtofile Using phtofile allows you to defer uploading of patch history information to the database until after the system downtime. Use adpatch uploadph=y to upload patch history information from the patch information files to the database during uptime.

34. AutoPatch Options - validate Tells AutoPatch whether to connect to all registered Oracle Applications schemas at the start of the patch. Purpose Comments Default options=validate novalidate Useful for finding problems with incorrectly-registered Oracle Applications schemas or schemas with invalid passwords.

38. Using Test and Production Systems Oracle Applications Test Database Oracle Applications Test File System Oracle Applications Production Database Oracle Applications Production File System AutoPatch 1. Apply to Test 2. Apply to Production

40. Merging Patches Umerged.drv Source Destination U<Patch2>.drv U<Patch1>.drv

43. Source and Destination Directories 2345671 destination <TOP> source 2345672 2345673 2345674