Internal error code, arguments : [17182], [185212224], [], [], [], [], [],
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 6 of 6

Thread: Internal error code, arguments : [17182], [185212224], [], [], [], [], [],

  1. #1
    Join Date
    Dec 2006
    Posts
    2

    Internal error code, arguments : [17182], [185212224], [], [], [], [], [],

    Hello,
    My oracle server has an internal error code , arguments : [17182], [185212224], [], [], [], [], [], [] when i run a decode function from an oracle client. I use an Oracle 8.1.7.0 on Windows 2000 server. I searched solutions in the net but nothing. Does anybody could help me to solve this problem.

    Need your help,

    Below the output of my oracle trace

    Many thanks.

    ksedmp: internal or fatal error
    ORA-00600: code erreur interne, arguments : [17182], [185212224], [], [], [], [], [], []
    Current SQL statement for this session:
    SELECT ALL decode(FSQ_FORMATIONS.FRMT_TYPE,:"SYS_B_00",:"SYS_B_01",:"SYS_B_02",:"SYS_B_03",:"SYS_B_04",:"SYS_B_05",:"SYS_B_06",:"SYS_B_07",:"SYS_B_08",:"SYS_B_09",:"SYS_B_10",:"SYS_B_11",:"SYS_B_12",:"SYS_B_13",:"SYS_B_14",:"SYS_B_15" ,
    :"SYS_B_16",:"SYS_B_17",:"SYS_B_18",:"SYS_B_19"),
    decode (FSQ_FORMATIONS.FRMT_TYPE,:"SYS_B_20",:"SYS_B_21" ,:"SYS_B_22",:"SYS_B_23",:"SYS_B_24",:"SYS_B_25",:"SYS_B_26",:"SYS_B_27",:"SYS_B_28",:"SYS_B_29",:"SYS_B_30",:"SYS_B_31",:"SYS_B_32",:"SYS_B_33",:"SYS_B_34",:"SYS_B_35",:"SYS_B_36",:"SYS_B_37",:"SYS_B_38",:"SYS_B_39") type,
    decode (FSQ_FORMATIONS.FRMT_TYPE,:"SYS_B_40",:"SYS_B_41" ,:"SYS_B_42") type_long,
    FSQ_DOCUMENTS.DOC_REF,
    FSQ_DOCUMENTS.DOC_INTITULE,
    FSQ_FORMATIONS.SERVICE_CODE,
    VFSQ_QRH_ORG_SERVICES.SERVICE_LIBELLE,
    FSQ_FORMATIONS.AGENT_MATRICULE,
    VFSQ_QRH_FIP_AGENTS.AGENT_NOM,
    VFSQ_QRH_FIP_AGENTS.AGENT_PRENOM,
    FSQ_AGENT_POSTES.POSTE_CODE,
    FSQ_POSTES.POSTE_LIBELLE,
    FSQ_FORMATIONS.FRMT_REELLE_DATE_DEBUT,
    FSQ_ANIMATEURS.ANIM_NOM||:"SYS_B_43"|| FSQ_ANIMATEURS.ANIM_PRENOMS,
    fsq_doc_indices.doc_indice doc_indice_actuel,
    fsq_doc_indices.doc_indice_date doc_indice_date_actuel
    FROM FSQ_DOCUMENTS,
    FSQ_FORMATIONS,
    VFSQ_QRH_FIP_AGENTS,
    VFSQ_QRH_ORG_SERVICES,
    FSQ_AGENT_POSTES,
    FSQ_POSTES,FSQ_ANIMATEURS,
    fsq_doc_indices
    WHERE ( ( FSQ_FORMATIONS.DOC_REF = FSQ_DOCUMENTS.DOC_REF ) AND ( FSQ_FORMATIONS.SERVICE_CODE = VFSQ_QRH_ORG_SERVICES.SERVICE_CODE ) AND ( FSQ_FORMATIONS.AGENT_MATRICULE = VFSQ_QRH_FIP_AGENTS.AGENT_MATRICULE ) AND ( FSQ_FORMATIONS.AGENT_MATRICULE = FSQ_AGENT_POSTES.AGENT_MATRICULE AND FSQ_FORMATIONS.SITE_CODE = FSQ_AGENT_POSTES.SITE_CODE AND FSQ_FORMATIONS.STE_CODE = FSQ_AGENT_POSTES.STE_CODE ) AND ( FSQ_AGENT_POSTES.POSTE_CODE = FSQ_POSTES.POSTE_CODE ) ) AND FSQ_FORMATIONS.DOC_REF <> :"SYS_B_44" AND FSQ_FORMATIONS.ANIM_ID = FSQ_ANIMATEURS.ANIM_ID (+) AND FSQ_FORMATIONS.FRMT_AGENT_CONCERNE = :"SYS_B_45" AND FSQ_FORMATIONS.DOC_REF = : p_doc AND FSQ_FORMATIONS.DOC_INDICE = : p_indice AND FSQ_FORMATIONS.FRMT_REALISEE like decode ( : p_realisee , :"SYS_B_46" , :"SYS_B_47" , :"SYS_B_48" , :"SYS_B_49" , :"SYS_B_50" , :"SYS_B_51" ) and FSQ_FORMATIONS.service_code = substr ( : p_service , :"SYS_B_52" , instr ( : p_service , :"SYS_B_53" ) - :"SYS_B_54" ) and fsq_documents.doc_ref = fsq_doc_indices.doc_ref and fsq_formations.doc_ref = fsq_documents.doc_ref and fsq_doc_indices.DOC_INDICE = : p_indice GROUP BY fsq_doc_indices.doc_indice , fsq_doc_indices.doc_indice_date , FSQ_FORMATIONS.FRMT_TYPE , FSQ_FORMATIONS.SERVICE_CODE , VFSQ_QRH_ORG_SERVICES.SERVICE_LIBELLE , FSQ_FORMATIONS.AGENT_MATRICULE , VFSQ_QRH_FIP_AGENTS.AGENT_NOM , VFSQ_QRH_FIP_AGENTS.AGENT_PRENOM , FSQ_AGENT_POSTES.POSTE_CODE , FSQ_POSTES.POSTE_LIBELLE , FSQ_FORMATIONS.FRMT_REELLE_DATE_DEBUT , FSQ_ANIMATEURS.ANIM_NOM , FSQ_ANIMATEURS.ANIM_PRENOMS , FSQ_DOCUMENTS.DOC_REF , FSQ_DOCUMENTS.DOC_INTITULE ORDER BY :"SYS_B_55" ASC,:"SYS_B_56" ASC,:"SYS_B_57" ASC,:"SYS_B_58" ASC,:"SYS_B_59" ASC,:"SYS_B_60" ASC , VFSQ_QRH_ORG_SERVICES.SERVICE_LIBELLE ASC
    ----- Call Stack Trace -----

  2. #2
    Join Date
    Apr 2003
    Location
    Gourock, Scotland
    Posts
    102
    ORA-00600: code erreur interne - an internal error. These should usually be reported to Oracle for advice as it's difficult for the average DBA to delve so deeply into the possible causes. Of course, there are many above average DBAs here who may be able to help, but you should report it to Oracle anyway.
    If I have to choose between two evils, I always like to choose the one I haven't tried yet.

  3. #3
    Join Date
    Nov 2004
    Location
    Mumbai, India
    Posts
    452
    Internal errors should always reported to Oracle support in form of an SR, even if there is a document with the same arguments. They will analyze the stack trace and advise whether or not to follow those documents.
    There are three kinds of lies: Lies, damned lies, and benchmarks...

    Unix is user friendly. It's just very particular about who it's friends are.

    Oracle DBA

  4. #4
    Join Date
    May 2000
    Location
    ATLANTA, GA, USA
    Posts
    3,135
    It seems to be that a bug in cursor_sharing = force.

    Set cursor_sharing=exact, and rerun the SQL. If you still get an error, contact oracle support.

    Do not set "force" value for the cursor_sharing parameter instance wide. It has a lot of side effects.

    Tamil

  5. #5
    Join Date
    Dec 2006
    Posts
    2
    You are right Tamil,
    My cursor_sharing value was force and i've changed it to exact and the problem is solved.
    Thanks for your help

    regards
    Raitsarevo

  6. #6
    Join Date
    May 2000
    Location
    ATLANTA, GA, USA
    Posts
    3,135
    In the past, I refused to support a database, where the previous DBA set CURSOR_SHARING=FORCE in the init.ora file.

    Tamil

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