ADPATCH ISSUES

1. A patch consists of c,d,g drivers, C driver performs the following activitie

s.
*1. copies the files to the product tops
*2. validates the file version before copying.
*3. use snapshots to validate the file versions.
*4. it relink the files using adrelink .
*5. generate jar files using adrelink.
*6. compiles the jsp files.

1.unable to copy the files: adpatch fails when it does not find space to copy th
e files in product_top.
resolution: Add space to product tops and restart the patch.
2.adpatch is failing during pre-req checks.
resolution: This will happen because adsnapshot has been not properly upgraded.
In this case we have two options.
a) stop the Adpatch
resol: once the utility completes restart the adpatch.
b) go to adadmin and run adsnapshot utility
resol: apply the patch with no prereq option
3.Relinking of executable files is failed
resol: go to $ORACLE_HOME/LIB/stubs in this location you will find a file called
libc.so. this file should always point to current instance. if it is pointing t
owards wrong instance. once these are changed to current instance relinking take
s place.
4.Issue with adjava
resolution: whenever adjava is failing a)you need to ensure that the classpath e
nvironment varialble is properly set.
b) adsign.txt ($APPL_TOP/admin) should have correct digital signature.if the si
gnature is not correct you need to recreate identitydb.obj
5.compilation of jsp files is failing.
a) manually compile the jsp files using ojspcompile.pl
b) noautoconfig,nocompilejsp,hidepassword only these are used to run adpatch.
6.adpatch is erroring out stating missing product.
a) Applprod.txt will have all the information of product tops.
b) although apps password is correctly given adpatch fails.this happens because
applsys account got locked..,so you need to unlock the applsys account.

D driver:
whenever you apply a d driver it runs the following files.
1. .odf files stands for (object definition files)
This object definition file creates the new objects (Tables,indexes,nested tab
les,varrays etc) if any of the odf files fails which means it is unable to creat
e the object. possible reasons are :
a)Existing object may be present (table,index,nested table, varrays) etc ..,

b) patch worker fails stating that unable to run the sql statement
sol: go to log file copy the location of the sql file and run the sql file manua
lly.
if the sql file successfully executes go to adctrl and skip the worker.
if it is still throughing error we need to troubleshoot further based on the err
or.
2. failure of .pls file
sol: Execute it manually otherwise troubleshoot based on error.
reasons: a) lack of permissions
b) additional procedures
3. failure of .ldt files (brings concurrent programs)
sol : if an .ldt file gets executed using the utility FNDLOAD .
or run the .ldt file manually using FNDLOAD if the problem still exists yo
u need to troubleshoot it further.
4..wft files failure(workflow files)
sol: during the d driver .wft files gets executed as there are workflow files .t
hey get executed using WFLOAD. if any of the workflow is failing run manually us
ing the WFLOAD. the syntax to run this WFLOAD will be available in log file.
G driver:
g driver is used to generate forms ,reports,graphic files and message files;
issues
1) .fmx is fails to regenerate
sol see the .fmb code to see which procedure is being coded in the form .go and
compile the porcedure manually (this will fix the issue)
2) This issue might occur if you apply patch with nocopy portion
sol:Apply the c driver and compile the forms again
Try to compile the form with the f60gen manually if the problem is still existin
g.
.rdf file
see the .rdf code to see which procedure is being called in the form go
and compile the procedure manually

same for the graphic files

Ignorable errors
If Jsp files are failing you can ignore the error and continue the process becau
se can call the Jsps and run time

d driver works
(odf,pls,pkg,wft) etc..
They are not licenced
You cannot install NLS language patches without installing base US language;
NLS doesn't bring the .odf files you cannot merge an NLS language

you cannot merge AD and FND patches

you are merge two patches one has c,g and d drivers and another has only u drive
r
you can merge NLS language patches of same languages
whenever you apply a patch using merge patch option the patch numbers will not g
et reflected in AD_APPLIED_PATCHES but reflected in AD_BUGS.
whenever you merge a patch the size of the merged patch will be less than or eq
ual to the size of all individual patches but is never grater than the all file
s;
Never bundle ad patch because new versions may came with the adpatch whe(if)we a
pply a patch it
when you are applying a patch on non-shared APPL_TOP following things should be
taken care
Admin node should be e nabled on all tops (stier =enable)
c,g,d should rnu in database node)
always run autoconfig on icm node
diagnostic patches are the patches which don't bring any functionality
ihelp patches
these patches can be apploied when the application maintance is

During maintainance mode concurrent manager stops processing including the reque
sts following the workflow requests are kept on hold and seeded data should not
be distrubed.