Test type xml is not available at the expected location. Please refer log for more details.

In R12 after upgrade from 11i, none of the diagnostic tests are available under Diagnostic tab. To test this we submitted concurrent request "Diagnostics Patching CP" which is available from 12.1.1. This request completes normally and in the log file following errors are records,

[main][20:23:22:457, 9/4/11] Running oracle.apps.fnd.oam.diagnostics.cp.MigrateCustomizationData
[main][20:23:22:458, 9/4/11] $Header: MigrateCustomizationData.java 120.0.12010000.4 2009/06/30 11:40:28 sramados noship $
[20:23:23:532, 9/4/11] Test type xml file location = /oraprod/oracle/finprdcomn/java/oracle/apps/fnd/oam/diagnostics/config/fnddiagTestTypes.xml
[main][20:23:23:560, 9/4/11] INV:Onhand Material Status:INV_DIAG_OH_PLAIN_NO_STATUS  Test type xml is not available at the expected location. Please refer log for more details.
[20:23:23:645, 9/4/11] Test type xml file location = /oraprod/oracle/finprdcomn/java/oracle/apps/fnd/oam/diagnostics/config/fnddiagTestTypes.xml
[main][20:23:23:645, 9/4/11] INV:Onhand Material Status:INV_DIAG_OH_SERIAL_STATUS Test type xml is not available at the expected location. Please refer log for more details.
[20:23:23:697, 9/4/11] Test type xml file location = /oraprod/oracle/finprdcomn/java/oracle/apps/fnd/oam/diagnostics/config/fnddiagTestTypes.xml
[main][20:23:23:697, 9/4/11] INV:Onhand Material Status:INV_DIAG_OH_STATUS_CONTROL Test type xml is not available at the expected location. Please refer log for more details.
[20:23:23:743, 9/4/11] Test type xml file location = /oraprod/oracle/finprdcomn/java/oracle/apps/fnd/oam/diagnostics/config/fnddiagTestTypes.xml



To getover this problem, refer to metalink document 235307.1, under "I am missing diagnostic tests after upgrading my EBS Release to 12"

To resolve this issue run the following sql,


select STATUS, EXTRACTVALUE(XMLType(text),'//JAVA_TOP') , name, node_name from fnd_oam_context_files where name not in ('TEMPLATE','METADATA') and (status is null or status != 'H') and CTX_TYPE = 'A' order by LAST_SYNCHRONIZED DESC;

If 11i path and information is displayed and if the status is not 'H' then update table  fnd_oam_context_files and set status to 'H' for 11i path/node.

In our case we executed the following statement,

SQL> update fnd_oam_context_files set status='H' where name='orauat_XXXXX';
1 row updated.
SQL> commit;

Rerun the concurrent request "Diagnostics Patching CP" and the error should have gone.

Now go back to Diagnostic page and you should be able to see all the diagnostic tests.