ORA:00600: after export

hi
i fot this error after export, database is in 9i

. exporting synonyms
. exporting views
. exporting referential integrity constraints
. exporting stored procedures
EXP-00008: ORACLE error 600 encountered
ORA-00600: internal error code, arguments: [17112], [0x41F8E010], [], [], [], [], [], []
EXP-00000: Export terminated unsuccessfully

Is it Reported as a Bug?
what is the reason for this error?

Are you using PGA_AGGREGATE_TARGET?

Check Metalink Note:463747.1

What is the exact oracle version?

Quote:

---

Originally Posted by pareshjavkar

What is the exact oracle version?

---

Oracle9i Enterprise Edition Release 9.2.0.4.0

Quote:

---

Originally Posted by PAVB

Are you using PGA_AGGREGATE_TARGET?

---

Sorry PAVB, i did,t get what you mean :)

Quote:

---

Check Metalink Note:463747.1

---

i will check it

I checked the note.....

but i got only this error when exporting... ORA:600....


i did't get the below error...

ORA-29516: Aurora assertion failure: Assertion failure at eoamig.c:699
EOA runtime assertion failure:
eoamig.c:699
Current SQL statement for this session:
BEGIN :STATUS := DBMS_JAVA.EXPORT_TEXT_CHUNK(:CHUNK, :LENGTH); END;

Upgrade to 9.2.0.5.0 or higher and check if the error persists ...

Regards,
Paresh

Check Metalink doc id 153788.1 (ORA-600 Troubleshooter) this will help you what exactly the ORA - 600 arguments are?

Select the version and enter the arguments listed in your ORA- 600.

Quote:

---

Originally Posted by pareshjavkar

Upgrade to 9.2.0.5.0 or higher and check if the error persists ...

---

I see, you are ready to work for Oracle tier 1 support.

You cannot be serious, nobody is upgrading to the next patchset every time you get an error; have you ever heard about "troubleshooting"?

Quote:

---

Originally Posted by PAVB

I see, you are ready to work for Oracle tier 1 support.

You cannot be serious, nobody is upgrading to the next patchset every time you get an error; have you ever heard about "troubleshooting"?

---

Dear PAVB,

FIX

The issue is fixed since RDBMS release 9.2.0.5.0.
WORKAROUND

None.



The above excerpt is taken from the Metalink ID (463747.1) which you have provided, which i agree to might be in the right direction, which i think is written in English and not French ...

Anyways different ways to look at it, if you are hitting a bug the parent itself i.e. Oracle Corporation (just in case) advises to go on a higher release which has the bug fixed.

But, I appreciate your skills at English grammar, .. you seem to be very good JUST AT IT.

I would request the moderators, i think i am here to learn somethings and help people solving their problems which doesn't seem to be the case with few around ... Can't we just help people "TROUBLESHOOTING" or whatever they call and put it across in a better way if somebody goes off track in answering a question.

Regards,
Paresh

Dear Paresh --

You are not stopping to read and put all pieces togheter then you are jumping into conclussions.

Metalink Note #463747.1 only applies when you have set pga_aggregate_target in your offending instance; if you read the chain you are going to find poster doesn't even know what pga_aggregate_target is therefore we could infer pga_aggregate_target is not set in the affected instance then Metalink Note #463747.1 doesn't apply.

You consider an upgrade only when you are 100% positive it applies to the issue but in this case evidence suggests this is not the case.

By the way, you come out as somebody good at what you do but you have to learn to stop for a second, breath ... and take a second look at it.

Note: Did you know we also have access to Metalink in French?

Quote:

---

Originally Posted by PAVB

poster doesn't even know what pga_aggregate_target is

---

Solution ?? :D

Quote:

---

Originally Posted by PAVB

You cannot be serious, nobody is upgrading to the next patchset every time you get an error; have you ever heard about "troubleshooting"?

---

I think You know only this :D

Quote:

---

Originally Posted by gopu_g

Solution ?? :D

---

Dear Gopu,

He has asked you whether you are using pga_aggregate_target?

Please let us know whether you are using pga_aggregate_target or you using sort_area_size?

Regards,
Paresh

Quote:

---

Originally Posted by pareshjavkar

Dear Gopu,

He has asked you whether you are using pga_aggregate_target?

Please let us know whether you are using pga_aggregate_target or you using sort_area_size?

Regards,
Paresh

---

Sorry missed out on one more thing, workarea_size_policy is it AUTO or MANUAL?

Paresh,

yes i am using...pga_aggregate_target

SQL> show parameter work_

NAME TYPE VALUE
------------------------------------ -----------
workarea_size_policy string AUTO
SQL>

Dear Gopu,

Does it create any trace file in udump when this error occurs?

Check alert.log .... Paste output of the trace file if any ...

Regards,
Paresh

yes it created one trace file...
and it is having this error..in it..

ORA-00600: internal error code, arguments: [17112], [0x41F8E010], [], [], [], [], [], []
Current SQL statement for this session:
BEGIN :STATUS := DBMS_JAVA.EXPORT_RAW_CHUNK(:CHUNK, :LENGTH); END;

Quote:

---

Originally Posted by gopu_g

yes it created one trace file...
and it is having this error..in it..

ORA-00600: internal error code, arguments: [17112], [0x41F8E010], [], [], [], [], [], []
Current SQL statement for this session:
BEGIN :STATUS := DBMS_JAVA.EXPORT_RAW_CHUNK(:CHUNK, :LENGTH); END;

---

I guess PAVB has answered your question then: Metalink ID: 463747.1 ... Upgrade to 9.2.0.5.0 or higher and check if the error persists.

Regards,
Paresh

Thanks , i will check it :)