on 10-01-2012 1:06 PM
Hi everyone,
when i'm doing with SUM an update of my ECC 6.0 SAP system to install EHP 6 I receive this error in the TABIM_UPG Phase:
2EETW125 SQL error "600" during "DSYS_PHHEAD_ECI2" access: "ORA-00600: internal error code, arguments: [kdimod0: key order], [9], [9], [], [], [], [], [], [], [], [], []"
4 ETW000 fld:#=0, alias:p=(nil), fupd:#=0, tab:#=1, where:#=3,
4 ETW000 groupby:#=0, having:#=0, order:#=0, primary=0, hint:#=0}
4 ETW000 CRSR: {tab='', id=0, hold=0, prop=0, max.in@0=3, fae:blk=0,
4 ETW000 con:id=0, con:vndr=5, val=2,
4 ETW000 key:#=0, xfer=0, xin:#=0, row:#=0, upto=0, wa:p=(nil)}
2EETW125 SQL error "600" during "DSYS_PHHEAD_ECI2" access: "ORA-00600: internal error code, arguments: [kdimod0: key order], [169], [169], [], [], [], [], [], [], [], [], []"
4 ETW000 fld:#=0, alias:p=(nil), fupd:#=0, tab:#=1, where:#=3,
4 ETW000 groupby:#=0, having:#=0, order:#=0, primary=0, hint:#=0}
4 ETW000 CRSR: {tab='', id=0, hold=0, prop=0, max.in@0=3, fae:blk=0,
4 ETW000 con:id=0, con:vndr=5, val=2,
4 ETW000 key:#=0, xfer=0, xin:#=0, row:#=0, upto=0, wa:p=(nil)}
2EETW125 SQL error "600" during "DSYS_PHHEAD_ECI2" access: "ORA-00600: internal error code, arguments: [kdimod0: key order], [54], [54], [], [], [], [], [], [], [], [], []"
1 ETP111 exit code : "12"
SAP procedure tries to execute a "delete" SQL statement of the table DSYS_PHHEAD_ECI2 and stops with this error....
I'm in a downtime phase, so I can't logon to SAP System.
Could you help me?
Thanks to all!
Fabrizio
Hi Fabrizio,
Check SAP note
#376755 - ORA-00600 - what to do?
Please run this command to see any error occurred.
analyze table DSYS_PHHEAD_ECI2 validate structure cascade;
Please also run a consistency check on entire database.
#23345 Consistency check of ORACLE database
There may be some corruption on this table.
let us know the results of the checks.
Regards,
Paul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi guys,
I solved the problem in this way:
- I read Note 23237 - duplicate keys, duplicate rows, duplicate records
The SQL statement doesn't show any duplicates,so I tried to use the SQL statement showed by
"Note 1742979 - ORA-00001: unique constraint violated encountered in DBCLONE phase during upgrade".
This SQL statement (obviously adapted for my case) reported 190 duplicates.
- I deleted the duplicate records, but many deletion failed because the statement tried to use the index, but the index is corrupted
- I drop the index
- I deleted the remaining duplicates
- in order to check the table I executed a REORG for the table using brtools
- I started SUM again and after a while the TABIM_UPG Phase successfully ended
Thanks all guys!
Fabrizio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello guys,
I read #376755 - ORA-00600 - what to do? and I executed the suggested statement
The result is the following:
ERROR at line 1:
ORA-01499: table/index cross reference failure - see trace file
TABIMUPG.ELG file shows this error:
4 ETW000 fld:#=0, alias:p=(nil), fupd:#=0, tab:#=1, where:#=3,
4 ETW000 groupby:#=0, having:#=0, order:#=0, primary=0, hint:#=0}
4 ETW000 CRSR: {tab='', id=0, hold=0, prop=0, max.in@0=3, fae:blk=0,
4 ETW000 con:id=0, con:vndr=5, val=2,
4 ETW000 key:#=0, xfer=0, xin:#=0, row:#=0, upto=0, wa:p=(nil)}
2EETW125 SQL error "600" during "DSYS_PHHEAD_ECI2" access: "ORA-00600: internal error code, arguments: [kdimod0: key order], [54], [54], [], [], [], [], [], [], [], [], []"
Any idea?
Thanks!
Fabrizio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Fabrizio,
It seems that there is a corruption in the index or table DSYS_PHHEAD_ECI2.
To determine the details what precisely is wrong, you need to follow the
steps in note 765613.
Secondly since database corruptions are generally occuring due to hardwa
re problems, schedule a full database consistency check per note 23345
using the analyze method.
We generally recommend that you import a non-corrupt backup and recovery
to eliminate corruptions. However, in the case of ora-01499, you may
have to examine the mismatched rows in greater detail to reduce downtime
or if you do not have a corruption-free backup.
Before you restore, check one last thing. first we have to identify
the if table or index, which one have the issue:
for e.g. if the issue with the index we can just rebuild the index.
For further analisys we will need to get the trace file generated by the
check where the ORA-01499 occured.
analyze table DSYS_PHHEAD_ECI2 validate structure cascade;
Please check the trace files and the alert.log to see if its just an index or really the table which is affected.
Regards,
Paul
Hi,
Recently i resolve the same issue in my landscape. It is not a simple matter to do. I provided the analysis method which was i did.
1. open the oracle trace file and it have the file and block which is corrupted in your database. Mostly it would be data block corruption and you can find after running the db check in DB13.
2. once you confirmed that also check in SM21 and if it shows some index problem ??. It shows any index problem you need to rebuild the same by using the command in oracle.
Let me know if you need any details or have any queries.
Thanks
Simbhu
Hello,
Can you please provide the TABIMUPG.ELG file.
Also can you please provide me the output of the following :
analyse table <owner>.DSYS_PHHEAD_ECI2 validate structure cascade;
Thank you.
Regards,
Gaurav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.