ORA:00600: after export - Page 2
DBAsupport.com Forums - Powered by vBulletin
Page 2 of 2 FirstFirst 12
Results 11 to 20 of 20

Thread: ORA:00600: after export

  1. #11
    Join Date
    Oct 2006
    Location
    Mumbai
    Posts
    184
    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
    Share on Google+

  2. #12
    Join Date
    Mar 2007
    Location
    Ft. Lauderdale, FL
    Posts
    3,554
    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?
    Pablo (Paul) Berzukov

    Author of Understanding Database Administration available at amazon and other bookstores.

    Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
    Share on Google+

  3. #13
    Join Date
    Aug 2007
    Location
    Cyberjaya,kuala lumpur
    Posts
    339
    Quote Originally Posted by PAVB
    poster doesn't even know what pga_aggregate_target is

    Solution ??

    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
    Last edited by gopu_g; 09-30-2008 at 05:24 AM.
    Thanks/Gopu
    Share on Google+

  4. #14
    Join Date
    Oct 2006
    Location
    Mumbai
    Posts
    184
    Quote Originally Posted by gopu_g
    Solution ??
    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
    Share on Google+

  5. #15
    Join Date
    Oct 2006
    Location
    Mumbai
    Posts
    184
    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?
    Share on Google+

  6. #16
    Join Date
    Aug 2007
    Location
    Cyberjaya,kuala lumpur
    Posts
    339
    Paresh,

    yes i am using...pga_aggregate_target

    SQL> show parameter work_

    NAME TYPE VALUE
    ------------------------------------ -----------
    workarea_size_policy string AUTO
    SQL>
    Thanks/Gopu
    Share on Google+

  7. #17
    Join Date
    Oct 2006
    Location
    Mumbai
    Posts
    184
    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
    Share on Google+

  8. #18
    Join Date
    Aug 2007
    Location
    Cyberjaya,kuala lumpur
    Posts
    339
    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;
    Thanks/Gopu
    Share on Google+

  9. #19
    Join Date
    Oct 2006
    Location
    Mumbai
    Posts
    184
    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
    Share on Google+

  10. #20
    Join Date
    Aug 2007
    Location
    Cyberjaya,kuala lumpur
    Posts
    339
    Thanks , i will check it
    Share on Google+

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width