Thursday, September 29, 2011

Issue : Statistics locked when running GSS

Issue: statistics locked error when running GSS

Gathering statistics using concurrent jobs "Gather Schema Statistics / Gather Table Statistics" or running FND_STATS fails with "ORA-20005: object statistics are locked".

First identify the object
select owner, table_name, stattype_locked
from dba_tab_statistics
where stattype_locked is not null;

and then unlock the stats

nlock statistics gathering on those queues running:

exec dbms_stats.unlock_schema_stats('schema_owner');
exec dbms_stats.unlock_table_stats('table_owner','table_name');


Example:

SQL> exec dbms_stats.unlock_schema_stats ('AR');
SQL> exec dbms_stats.unlock_table_stats('AR', 'AR_REV_REC_QT');

to reset the sequences for creation of temp files

Issue: to reset the sequences for creation of temp files
Solutions:
you please shutdown the managers and reset the sequence to a smaller value, 1000 or so.
To do this you will need to drop and recreate the sequence.

The create statement for fnd_temp_files_s is:
create sequence fnd_temp_files_s
increment by 1
start with 1
maxvalue 9999999
minvalue 0
cache 20
cycle;

Pls check if there are any invalid object which are not getting compiled and hanging for example due to db links.

Use the ojspcmpile.pl perl script to perform a manual pre-compilation of the JSP pages. The following command will compile all the JSP

Unix: # $FND_TOP/patch/115/bin/perl ojspCompile.pl --compile --flush -p 2

Issue:utlprp.sql gets hung

Pls check if there are any invalid object which are not getting compiled and hanging for example due to db links which are in the code But not working.

Issue:/var getting full in any location on middle tier

Issue : /var getting full in any location on middle tier
Solutions:
1.Check for file with name of application unix user in location /var/mail/
e.g. applmgr
check the size of this file and make the size to null by command “ > applmgr”

Issue:VIP down so listener not starting.

Issue:VIP down so listener not starting.
Solution:
To confirm the following :
Comment the vip entry from listener.ora from $ORACLE_HOME of database and start the listener,If the listener starts then we can confirm that it’s the vip which is down and hence the listener is not starting.
Contact the unix team to start th vip properly

Issue:vip's getting failed over abruptly

look at the racgvip file? the parameter CHECK_TIMES must be 10..
if its too less like 2, this issue can occur.