Skip to main content

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.


Comments

Popular posts from this blog

SQL Interview Questions on Subqueries

SUB Queries:
1. List the employees working in research department 2. List employees who are located in New York and Chicago
3. Display the department name in which ANALYSTS are working
4. Display employees who are reporting to JONES
5. Display all the employees who are reporting to Jones Manager
6. Display all the managers in SALES and ACCOUNTING department
7. Display all the employee names in Research and Sales Department who are having at least 1 person reporting to them
8. Display all employees who do not have any reportees
9. List employees who are having at least 2 reporting
10. List the department names which are having more than 5 employees
11. List department name having at-least 3 salesman
12. List employees from research and accounting having at-least 2 reporting
13. Display second max salary
14. Display 4th max salary
15. Display 5th max salary  -- Answer for nth Max Salary
Co-Related Subqueries:
16. Write a query to get 4th max salary from EMP table
17. Write a query to get 2nd…

Answers for SUB Queries

1. SQL> select empno, ename from emp where deptno=(select deptno from dept where dname='RESEARCH');


2. SQL> select empno, ename from emp where deptno in (select deptno from dept where loc in ('NEW YORK','CHICAGO'));

3. SQL> select dname from dept where deptno in ( select deptno from emp where job ='ANALYST');

4. SQL> select empno, ename, mgr from emp where mgr = (select empno from emp where ename='JONES');

5. SQL> select empno, ename, mgr from emp where mgr = (select mgr from emp where ename='JONES')

6. SQL> select empno, ename, job from emp where deptno in ( select deptno from dept where dname in ('SALES','ACCOUNTING'))

7. SQL> select empno, ename, job from emp where deptno in ( select deptno from dept where dname in ('SALES','RESEARCH')) and empno in (select mgr from emp)

8. SQL> select empno, ename from emp where empno not in ( select mgr from emp where mgr is not null)

9. select…

'Linux-x86_64 Error: 28: No space left on device' While trying to start the database -- Error

SQL> startup mount pfile='/tmp/initdlfasp12.ora'
ORA-27102: out of memory
Linux-x86_64 Error: 28: No space left on device


This as you can see is on Linux x86 with 64 bit processor. We got this error after we changed SGA on 10gR2 database. So was sure that this is something to do with the OS.

Parameters to check for this are shmall.

shmall is the total amount of shared memory, in pages, that the system can use at one time.

$cat /proc/sys/kernel/shmmax
53687091200

$ getconf PAGE_SIZE
4096

As per Oracle SHMALL should be set to the total amount of physical RAM divided by page size.

Our system has 64GB memory, so change kernel.shmall = 1024 * 1024 * 1024 * 64 / 4096 = 16777216


Once this value is calculated you can modify Linux system configuration file directly.

$ su - root
vi /etc/sysctl.conf file:
kernel.shmall=16777216

and

# sysctl -p

Once this is done the database was started without any problem.