This is a good one:
-
How about this error showing up in 64-bit 8.1.6.2.0 on HP-UX v11i?? Any ideas??
Printable View
This is a good one:
-
How about this error showing up in 64-bit 8.1.6.2.0 on HP-UX v11i?? Any ideas??
ORA 600 ( As I Know ) indicates that the database needs recovery
Not neccessarily.....
It depends on the argument which is followed after the ora-600 error.
If the args[17000......more] and args[7445] you are right it may need recovery ...It may
corrupt index (I have faced)....
I feel arg[6033] is because of the core dump?.If so just bounce the db once.It will work.
What corresponding trace file says?.can you post that.
Thanks.
Thanigaivasan
/dss_816/app/oracle/admin/dss/udump/ora_26371_dss.trc
Oracle8i Enterprise Edition Release 8.1.6.2.0, 64 bit - Production
With the Partitioning option
JServer Release 8.1.6.2.0 - Production
ORACLE_HOME = /dss_816/app/oracle/product/8.1.6
System name: HP-UX
Node name: hpn2
Release: B.11.00
Version: U
Machine: 9000/800
Instance name: dss
Redo thread mounted by this instance: 1
Oracle process number: 75
Unix process pid: 26371, image: oracle@hpn2 (TNS V1-V3)
*** SESSION ID:(36.4406) 2001-03-29 12:31:20.876
*** 2001-03-29 12:31:20.876
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [6033], [], [], [], [], [], [], []
Current SQL statement for this session:
SELECT * FROM CM_CHECK_CLAIM_LOG WHERE CHECK_ID = :b1 AND CHECK_DATE = :b2 FOR UPDATE
----- PL/SQL Call Stack -----
object line object
handle number name
c00000014d112bd8 48 procedure CM_LIVE.CM_VOID_CHK
c00000014b435290 1 anonymous block
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
Cannot find symbol for address: 00000000009b4f97 (631)
ksedst + 399 ???? skdstinit 8000000100063754 ?
00000002C ?
80000001FFFFFFFF ?
8000000100063790 ?
ksedmp + 247 ???? ksedst 8000000100063650 ?
4000000000219650 ?
5555555555555555 ?
40000000002C81A0 ?
ksfdmp + 35 ???? ksedmp 80000001000048B8 ?
C00000014C202640 ?
8000000100001791 ?
000000002 ?
kgeriv + 159 ???? ksfdmp 8000000100001791 ?
000000002 ? 04E53DB70 ?
000000007 ?
kgeasi + 211 ???? kgeriv 000000007 ?
8000000100063790 ?
8000000100098AF0 ?
0000AB138 ?
kdifxs + 4391 ???? kgeasi 8000000100098AF0 ?
40000000003F7678 ?
-
-
and so on. It's a huge trace file.
Hi friend,
I have gone thru the file and I could not guess the exact error because the line which shows the error is missing in the trace file..
I know it is difficult to post all the trace file..
okay you do this...
is there any smon trace file created....if yes good it will specify clearly which is giving problem...
try for file id /mostly it will be there after PROXY in trace file check for that.query the db using the file id../tablespace...
I am also doing reseach on that I will get back shortly.
Thanks.
Thanigaivasan
apart from recovery:
on 816,parch 3 the
declare
a boolean;
begin
a:=DBMS_SESSION.IS_SESSION_ALIVE(null);
end;
gives ORA-00600: internal error code, arguments: [15498], [0], [], [], [], [], [], []
Reason: null in proc. call.
Could it be similar issue?
I'll have to check up on that. This happened on a db that I am not administering. This was reported by another DBA on site.
I have encountered "ORA-00600: internal error code, arguments: [6033], [], [], [], [], [], [], []" when executing a cursor loop. The error message was caused probably by an update statement inside the cursor. My Oracle is Oracle9i 9.0.1.4.0 on Linux.
In your honor I hearby do invent the following new acronymQuote:
Originally posted by vbrover
I have encountered "ORA-00600: internal error code, arguments: [6033], [], [], [], [], [], [], []" when executing a cursor loop. The error message was caused probably by an update statement inside the cursor. My Oracle is Oracle9i 9.0.1.4.0 on Linux.
OAFT! open a friendly tar!
ORA-600, drop the database immediately, it is corrupt!
yet another acronym for Mt Hanky => lmfao...laughing my friendly ass off!!!Quote:
Originally posted by Mr.Hanky
ORA-600, drop the database immediately, it is corrupt!
that's friendly great!, just friendly fine!!
Maybe I'll change my title to Self Appointed Court Jester?
.. Or may be OS is corrupt, format your disks !Quote:
Originally posted by Mr.Hanky
ORA-600, drop the database immediately, it is corrupt!
;)
or maybe just do this
pleeaaaazzzzeeee. that's hardly any fun ;-)Quote: