1 Reply Latest reply on Jan 24, 2003 9:56 PM by 4174

    ORA-00600: internal error code, arguments: [12333], [0], [0], [0], [], [],

    230345
      ORA-00600: Occurred in production database. I did not contact oracle support yet, because I know they will ask to upgrade or apply a patch. I want do that as a last resort. Do you see any other reason for this ORA-600 error or solution?
      Thanks.

      part of trace file:
      -------------------
      Dump file /tmp/rmsdv84_ora_11548.trc
      Oracle8i Enterprise Edition Release 8.1.7.2.0 - Production
      With the Partitioning option
      JServer Release 8.1.7.2.0 - Production
      ORACLE_HOME = /usr/oracle/product/8.1.7
      System name:     SunOS
      Node name:     fcdb239
      Release:     5.8
      Version:     Generic_108528-12
      Machine:     sun4u
      Instance name: RMSDV84
      Redo thread mounted by this instance: 1
      Oracle process number: 32
      Unix process pid: 11548, image: oracle@fcdb239 (TNS V1-V3)

      *** SESSION ID:(34.1296) 2003-01-23 16:46:43.524
      *** 2003-01-23 16:46:43.524
      ksedmp: internal or fatal error
      ORA-00600: internal error code, arguments: [12333], [0], [0], [0], [], [], [], []
      Current SQL statement for this session:
      SELECT OWNERID FROM PS.PSDBOWNER WHERE DBNAME=:1
      ----- Call Stack Trace -----
      calling call entry argument values in hex
      location type point (? means dubious value)
      -------------------- -------- -------------------- ----------------------------
      ksedmp()+168 CALL ksedst()+0 230 ? 1 ? FFBED080 ?
      FFBECB24 ? FFBECB08 ? 0 ?
      kgeriv()+196 PTR_CALL 00000000 3 ? 0 ? 0 ? 258 ? 1 ? 302D ?
        • 1. Re: ORA-00600: internal error code, arguments: [12333], [0], [0], [0], [], [],
          4174
          ORA-00600 12333 usually means there was a communications error between the client and server. If you kill a session or perform a shutdown while a users connected you could potentially get this error. There's other reasons too. I think you're probably right that Oracle support will tell you to upgrade if you file a TAR with them.

          Did this error crash your database or does it happen frequently? If the answer is no then I wouldn't worry about it unless the end user has said something about it. If this is a problem then I'd contact Oracle support.

          I'm also running 8.1.7.2 and get maybe 1-2 of these errors a month from the same PC. In our case this error didn't correspond with a database shutdown or a killed session. We also tried reinstalling the client software and this didn't fix it either. I think our error may be because of this one PC being on a very old part of our network that probably needs upgrading.