Posts for all those DBAs out there, who are more fond of google than metalink :)

Tuesday, August 25, 2009

‘View Log’ generates 'Internal Server Error'



Issue:

On clicking on ‘View Log’ for any concurrent request, we hit ‘Internal Server Error’

Analysis:

The Apache error_log shows:

[Fri Dec 5 14:29:34 2008] [error] [client x.x.x.x] client denied by server configuration: /mnt/comn/java/oracle/dms
ld.so.1: FNDWRR.exe: fatal: libm.so.2: open failed: No such file or directory
[Fri Dec 5 14:29:41 2008] [error] [client x.x.x.x] Premature end of script headers: /mnt/comn/html/bin/FNDWRR.exe

The last run of autoconfig had apparently resulted in error, as the adconfig log shows:

Uploading Metadata file /mnt/appl/ad/11.5.0/admin/template/adctxinf.tmp
Metadata file /mnt/appl/ad/11.5.0/admin/template/adctxinf.tmp upload failed.
Check log file created by FNDCPUCF program.
ERRORCODE = 137 ERRORCODE_END
.end std out.
ld.so.1: FNDCPUCF: fatal: libm.so.2: open failed: No such file or directory
Killed

ld.so.1: FNDCPUCF: fatal: libm.so.2: open failed: No such file or directory
Killed

Solution:

Created a soft link linking libm.so.2 to ld.so.1 but still got the error in Adconfig Log

Uploading Metadata file /t5/oracle/eexitdevappl/ad/11.5.0/admin/template/adctxinf.tmp
Metadata file /t5/oracle/eexitdevappl/ad/11.5.0/admin/template/adctxinf.tmp upload failed.
Check log file created by FNDCPUCF program.
ERRORCODE = 137 ERRORCODE_END
.end std out.
ld.so.1: FNDCPUCF: fatal: libm.so.2: version `SUNW_1.1' not found (required by file /t5/oracle/eexitdevappl/fnd/11.5.0/bin/FNDCPUCF)
ld.so.1: FNDCPUCF: fatal: libm.so.2: open failed: No such file or directory
Killed
ld.so.1: FNDCPUCF: fatal: libm.so.2: version `SUNW_1.1' not found (required by file /t5/oracle/eexitdevappl/fnd/11.5.0/bin/FNDCPUCF)
ld.so.1: FNDCPUCF: fatal: libm.so.2: open failed: No such file or directory
Killed

Then created soft link linking libm.so.2 to libm.so.1

ln -s libm.so.1 libm.so.2

And finally through the maze of dreaded lib files, we managed to resolve the issue.


No comments:

Post a Comment