Home » RDBMS Server » Server Administration » Unable to analyze table(IOT_TYPE = IOT ) (Oracle 9.2.0.8.0 (RAC ) o/s:HP-UX 11.23)
Unable to analyze table(IOT_TYPE = IOT ) [message #378114] Mon, 29 December 2008 00:22 Go to next message
kesavansundaram
Messages: 181
Registered: October 2007
Location: MUMBAI
Senior Member

Dear sir,

We are analyzing one table with following command:

ANALYZE TABLE ACC_VOU_GEN_TXN_DTL estimate statistics 15 percent for table for all indexes for all indexed columns;

we are getting following error:

SQL> analyze table ACC_VOU_GEN_TXN_DTL estimate statistics sample 10 percent for table for all indexes for all indexed columns;
analyze table ACC_VOU_GEN_TXN_DTL estimate statistics sample 10 percent for table for all indexes for all indexed columns
*
ERROR at line 1:
ORA-03113: end-of-file on communication channel


When we check dba_tables, we found IOT_TYPE is IOT.

Further, after checking alert log file, we are pasting alert log content and corresponding trace file content:

the following content is alert log file:
----------------------------------------

Sun Dec 28 09:39:48 2008
Errors in file /dump_dest/sbiwill/udump/sbiwill1_ora_3369.trc:
ORA-07445: exception encountered: core dump [kdgistp()+2528] [SIGFPE] [HP Conditional trap] [0x4000000001166ED3] [] []



trace file content:
-------------------
*** 2008-12-28 09:39:48.840
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [kdgistp()+2528] [SIGFPE] [HP Conditional trap] [0x4000000001166ED3] [] []
Current SQL statement for this session:
analyze table ACC_VOU_GEN_TXN_DTL estimate statistics sample 15 percent for table for all indexes for all indexed columns
----- Call Stack Trace -----
calling              call     entry                argument values in hex      
location             type     point                (? means dubious value)     
-------------------- -------- -------------------- ----------------------------
ksedmp()+184         ?        ksedst()             800003FFC001EAB0 ?
                                                   800003FFC0030310 ?
                                                   52456DB36EFC3 ?
                                                   800000010013CFA8 ?
ssexhd()+636         ?        ksedmp()             800000010013CFA8 ?

..
..
..
..
13690736:00324512    19   156 10429   9 IPC MSGC: OUTQ first msg c000000250543f20, type 65521, dest 1, receiver 1
14DE5A93:00324513    19   156 10429   9 IPC MSGC: OUTQ first msg c0000002505eedc0, type 65521, dest 1, receiver 1
14E0AC58:00324514    19   156 10429   9 IPC MSGC: OUTQ first msg c0000002507e3d50, type 65521, dest 1, receiver 1
KSTDUMP: End of in-memory trace dump
ssexhd: crashing the process...
Shadow_Core_Dump = partial


=========================================================================================================================

And this table is getting analyzed (by removing sample option ) with following command:

ANALYZE TABLE ACC_VOU_GEN_TXN_DTL estimate statistics for table for all indexes for all indexed columns;

p.s: the total record count is: 4 rows

Thank you,
kesavan.
Re: Unable to analyze table(IOT_TYPE = IOT ) [message #378125 is a reply to message #378114] Mon, 29 December 2008 01:11 Go to previous messageGo to next message
Michel Cadot
Messages: 64122
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
ORA-00600/ORA-07445/ORA-03113 = Oracle bug => search on Metalink and/or call Oracle support

By the way, you should use dbms_stats and not analyze to gather statistics.

Regards
Michel

[Updated on: Mon, 29 December 2008 01:12]

Report message to a moderator

Re: Unable to analyze table(IOT_TYPE = IOT ) [message #378129 is a reply to message #378125] Mon, 29 December 2008 01:27 Go to previous messageGo to next message
kesavansundaram
Messages: 181
Registered: October 2007
Location: MUMBAI
Senior Member


Thank you for your prompt reply.

Kindly note, since we are using oracle 9i version , as per my understanding we should use ANALYZE instead of DBMS_STATS pkg.

Please correct me if we are wrong.

Thank you,
Kesavan
Re: Unable to analyze table(IOT_TYPE = IOT ) [message #378131 is a reply to message #378129] Mon, 29 December 2008 01:28 Go to previous message
Michel Cadot
Messages: 64122
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
You should use dbms_stats even in 9.2.

Regards
Michel
Previous Topic: setting the environment problem
Next Topic: OEM problem with wrong date_time
Goto Forum:
  


Current Time: Wed Dec 07 05:06:06 CST 2016

Total time taken to generate the page: 0.05534 seconds