When you start ADPATCH, you name the log file. The file is located in $APPL_TOP / install / log and the DEFAULT name is adpatc h.log. Some patches may spawn workers which each have an associated log file. These log files should be checked for errors when a new patch I s installed.
When you start ADPATCH, you name the log file. The file is located in $APPL_TOP / install / log and the DEFAULT name is adpatc h.log. Some patches may spawn workers which each have an associated log file. These log files should be checked for errors when a new patch I s installed.
When you start ADPATCH, you name the log file. The file is located in $APPL_TOP / install / log and the DEFAULT name is adpatc h.log. Some patches may spawn workers which each have an associated log file. These log files should be checked for errors when a new patch I s installed.
7) A patch fails on a column with one of the following errors:
ORA-00904 invalid column name
or ORA-00942 table or view does not exist
Review the manual steps in the README file distributed with the patch. This problem can usually be corrected by following the steps in this file. 8) What log files are generated by ADPATCH?
When you start ADPATCH, you name the log file. If you do not give it a uniq ue name each time, the log information is appended to the end of the existing fi le. The file is located in $APPL_TOP/install/log and the DEFAULT name is adpatc h.log. The ADPATCH log file could contain references to many patches.
Some patches may spawn workers which each have an associated log file. Worke r. These log files are named adwork01.log, adwork02.log, etc., and are located in $APPL_TOP/install/log. They should be checked for errors when a new patch i s installed.
9) What happens when a patch is applied whose version is lower than the current installed version of the patch? Higher versions contained within the patch are copied; the lower versions ar e ignored.