2014-06-21 Baoxinjian
Dba_oracle ERP in a form need to upgrade patch detailed (case)
I. Summary
Sometimes when Oracle ERP is maintained, you encounter bugs that are resolved by Oracle and require patches
Before patch, it's a good idea to ask the SR and Oracle Support team to confirm whether or not to recommend a larger patch to do a risk assessment
Second, the case
Case: Upgrade the version of the Supplier Merge form to resolve the Oracle standard Bug
1. Check the current form version
(1). Statement:-A $AU _top/forms/us/glxfcrvl.fmb|grep ' $Header '
(2). By Application Way
2. querying Oracle Support's data
3. Download patches, note the language of choice
4. Copy the patch to the virtual machine and host shared directory
5. Turn on Maintenance mode
6. To change the patch directory permissions to 777 and start the patch
(1). Modify Permissions: Chmod-r 777 Patch
(2). Start patch
7. If you make a patch error, you need to re-hit, two ways
(1). Do not continue pervious autopatch sesion
(2). Adpatch restart=y
8. Turn off maintenance mode after patching
9. See if the patch was successful
(1). View the version of the form
(2). View patch records in the database
SELECT * from Ad_applied_patches
WHERE patch_name = ' 12707227 ';
SELECT * from Ad_bugs
WHERE bug_number = ' 12707227 ';
If a system crash occurs while patching, refer to the practice of step_7
One . if failed occurs during patching, it needs to be started in another session Adctrl
(1). The default password that appears for Failed,applsys is also an apps
(2). Start Adctrl, general select 2 for Restart Job, or select 8 to skip this error
(3). Finally, this failed job is skipped and the job below is
Abalone New ********************
Oracle ERP Patch Upgrade approach