Analyzing partitioned table(URGENT)

Hi,

While inserting in a table (having 182 partitions),I came up with ORA-00600: internal error code,
arguments:[4512],[ ],.....[ ].The tablespace containing that table have 4 datafiles,I have already run dbv(DBVERIFY) but did not find any block corruption in the datafiles.The other thing in my mind is to
ANALYZE the table,can any one help me to tell the easiest way to analyze a partitioned table having 182
partitions or any other way to get rid of this error.

your quick response will be highly appreciated as it is an production env.

Thanks

Hi, We understood the urgency of your problem. But the manual says as follows:

This is the generic internal error number for Oracle program exceptions. It indicates that a process has encountered a low-level, unexpected condition. Causes of this message include:

timeouts
file corruption
failed data checks in memory
hardware, memory, or I/O errors
incorrectly restored files

I think, you may have to check-up your system completely to identify any of the above incidents happened in your database. Please check all the alert log files. This is the better time to contact for ORACLE WORLD-WIDE CUSTOMER SUPPORT or any of your senior experts. We don't know the all the details of your database. But you can check for all the possibilities.

Regards,
A.P.BALASUBRAMANIAN

..mmm...ora-600 (The DBA-INCUB).
I don't think that dbv can help you (in this case). This kind of error means a structure damege, may bee table structure...may bee internal structure (rollback..tablespaces...etc..)
I will try this first:
analyze table xxx validate structure;

try to produce trace :
1. using alter session set sql_tarce=true or setting 10046 events with level 10
2. dumping process state, etc
Then look into trace files, especialy into data dictionary queries as error can be in system tablespace.

if nothing helps and this is not a big deal, try to recreate the table.

Urgent

Hi All,

Thanks for the replies,but the problem still persists,Ihave done
Analyze table ..... validate structure cascade; but I din't helped no trace file was generated and the statment was processed. Please have a look at Alert.log and trace file.

Thanks

> ============== alert_GPB.log ============================
>
> Sun Apr 1 01:22:56 2001
> Errors in file /oracle/GPB/saptrace/usertrace/ora_27747_gpb.trc:
> ORA-00600: internal error code, arguments: [4512], [], [], [], [], [], [],
> []
> Sun Apr 1 04:07:09 2001
>
> 164412 Mon Apr 2 01:23:15 2001
> 164413 Errors in file /oracle/GPB/saptrace/usertrace/ora_27747_gpb.trc:
> 164414 ORA-00600: internal error code, arguments: [4512], [], [], [], [],
> [], [], []
> 164415 Mon Apr 2 04:14:24 2001
> 164416 ALTER TABLESPACE PSAPBTABD END BACKUP
> 164417 Mon Apr 2 04:14:24 2001
> 164418 Completed: ALTER TABLESPACE PSAPBTABD END BACKUP
> 164419 Mon Apr 2 04:14:24 2001
> 164420 ALTER TABLESPACE PSAPBTABI END BACKUP
>
> 164806 Tue Apr 3 01:30:26 2001
> 164807 Errors in file /oracle/GPB/saptrace/usertrace/ora_27787_gpb.trc:
> 164808 ORA-00600: internal error code, arguments: [4512], [], [], [], [],
> [], [], []
> 164809 Tue Apr 3 05:18:04 2001
> 164810 Completed checkpoint up to RBA [0x4bf.2.10], SCN: 0x0000.00661301
> 164811 Tue Apr 3 05:18:05 2001
>
> ============== ora_27787_gpb.trc ============================
> 1 Dump file /oracle/GPB/saptrace/usertrace/ora_27787_gpb.trc
> 2 Oracle8i Enterprise Edition Release 8.1.6.3.0, 64 bit - Production
> 3 With the Partitioning option
> 4 JServer Release 8.1.6.3.0 - Production
> 5 ORACLE_HOME = /oracle/GPB/816_64
> 6 System name: HP-UX
> 7 Node name: atdhp21
> 8 Release: B.11.00
> 9 Version: U
> 10 Machine: 9000/800
> 11 Instance name: GPB
> 12 Redo thread mounted by this instance: 1
> 13 Oracle process number: 18
> 14 Unix process pid: 27787, image: oracle@atdhp21 (TNS V1-V3)
> 15
> 16 *** SESSION ID:(19.1) 2001-04-03 01:30:26.111
> 17 *** 2001-04-03 01:30:26.111
> 18 ksedmp: internal or fatal error
> 19 ORA-00600: internal error code, arguments: [4512], [], [], [], [],
> [], [], []
> 20 Current SQL statement for this session:
> 21 INSERT INTO "/BIC/FS908_SUP" ( "KEY_S908_SUPP" , "KEY_S908_SUPT" ,
> "KEY_S908_SUPU" , "KEY_S908_SUP1" , "KEY_S908_SUP2" , "KE
> Y_S908_SUP3" , "KEY_S908_SUP4" , "ACT_DL_QTY" , "/BIC/ZDELFRCST" ,
> "/BIC/ZDELORDER" , "/BIC/ZDELPAST" , "/BIC/ZDELSHIP" , "/BIC/ZFOR
> ECAST" , "/BIC/ZNETPRICE" , "/BIC/ZNETVAL" , "/BIC/ZORDERQTY" ,
> "/BIC/ZPASTDUEO" , "/BIC/ZTARGTQTY" ) VALUES( :A0 , :A1 , :A2 , :A3
> , :A4 , :A5 , :A6 , :A7 , :A8 , :A9 , :A10 , :A11 , :A12 , :A13 , :A14 ,
> :A15 , :A16 , :A17 )
> 22 ----- Call Stack Trace -----
> 23 calling call entry argument values
> in hex
> 24 location type point (? means dubious
> value)
> 25 -------------------- -------- --------------------
> ----------------------------
> 26 Cannot read string table section header:
> 27 ksedst + 399 ???? skdstinit C000000000154177
> ?
> 28 000000001 ?
> 29 8000000100076118
> ?
> 30 000000028 ?
> 31 ksedmp + 247 ???? ksedst 000000003 ?
> 32 4000000000219840
> ?
> 33 C00000000AFD9014
> ?
> 34 000000001 ?
> 35 ksfdmp + 35 ???? ksedmp 80000001000666C0
> ?
> 36 800003FFFF7FA128
> ?
> 37 8000000100004D58
> ?
> 38 8000000100063798
> ?
> 39 kgeriv + 159 ???? ksfdmp 8000000100004D58
> ?
> 40 8000000100063798
> ?
> 41 01EDFB698 ?
> 42 FFFFFFFFFFFFFFFF
> ?
> 43 kgeasi + 211 ???? kgeriv FFFFFFFFFFFFFFFF
> ?
> 44 8000000100063570
> ?
> 45 8200FFFF00FF ?
> 000000000 ?
> 46 ktbgtl + 331 ???? kgeasi 100000002 ?
> 47 800003FFFF7F8CC8
> ?
> 48 80000001000048E0
> ?
> 49 000000012 ?
> 50 kdiins0 + 3995 ???? ktbgtl 3FFFF7F9DE8 ?
> 51 1700000000000000
> ?
> 52 8000000100063798
> ?
> 53 00000000D ?
> 54 kdiins + 95 ???? kdiins0 000000000 ?
> 55 40000000010E7B23
> ?
> 56 2000400000053D8 ?
> 57 40000000009883BF
> ?
> 58 kdibldwrt + 583 ???? kdiins 8000000100722208
> ?
> 59 000000000 ?
> 100000000 ?
> 60 000001FA6 ?
> 61 kdiblread + 903 ???? kdibldwrt 000000000 ?
> 100000000 ?
> 62 004000000 ?
> 63 8000000100000000
> ?
> 64 kdiblcfls + 219 ???? kdiblread 000000000 ?
> 000003843 ?
> 65 8000000100062BA0
> ?
> 66 8000000100063780
> ?
> 67 kdiblfls + 615 ???? kdiblcfls 80000001002F6A00
> ?
> 68 800003FF0002DB21
> ?
> 69 80000001000629A0
> ?
> 70 5555555555555555
> ?
> 71 kaudfb + 203 ???? kdiblfls 5555555555555555
> ?
> 72 4000000000279B18
> ?
> 73 000000000 ?
> 000000000 ?
> 74 insexe + 3503 ???? kaudfb 5555555555555555
> ?
> 75 4000000000000005
> ?
> 76 100004D58 ?
> 77 800000010000B880
> ?
> 78 opiexe + 12131 ???? insexe 80000001002B0878
> ?
> 79 000000018 ?
> 000005CED ?
> 80 400000000111B957
> ?
> 81 opiodr + 1419 ???? opiexe 000000000 ?
>

The problem seems to be at ORacle Service layer,
Verify there are no tablespace still in backup mode
I feel they still are and checkpoint cannot occur since the
tablespace is not back in normal mode and hence no new data is being entered.
Also Verify your Redologfiles are not corrupt, checkpoint process advances based on Redo block Address in Redolog files and updates controlfile.

Dump you control file header and verify the above tablespace mode and checkpoint SCN.

Take Care
GP

No file is in the backup mode, I checked from v$backup

Problem still not solved.

does it run on test database?
if do not know then try to create a copy of that table somewhere else(at least indifferent tablespace) and try to insert: this at least will show that it is a storage problem, but not SQL bug.