ADJAVA

---

ADJAVA restores several zip files if a patch contains Java files. Usually, you will see messages during the running of a C driver that show that this utility is running. However, you occasionally will have to manually run it if something happens that you cannot explain or as a manual step during a patch. While ADPATCH and ADADMIN usually put any and all error messages into the log file, occasionally a utility (ADJAVA is a good example) will sit for hours apparently doing nothing. It can take a while to run an ADJAVA statement; it is not unusual for one statement to run from 30 minutes to over an hour, especially if the patch you are applying is doing considerable Java related work. If one statement, however, runs for several hours, it could indicate a problem. If you stop whatever is running, copy the statement to the command line, and run it, you can often see what was going on behind the scenes and get a better idea of exactly what part of the statement was causing problems. This is often information that Oracle Support will ask for in an iTAR and being able to provide that information when you open the TAR can expedite the process considerably.

One interesting note to remember is that ADJAVA is a resource hog (either because it is called from ADPATCH or ADADMIN or running directly from the command line). It will consume considerable resources on your box, so when running this utility for extended periods of time, you may see other things waiting or running slowly. It is nothing to become unduly alarmed about.

---