Taggato: ORA-600

ORA-600 Lookup Error Categories (part 1c)

Internal Errors Categorised by mnemonic kpor  progint/opi support for streaming protocol used by replication kposc  progint/kpo support for scrollable cursors kpotc  progint/opi oracle side support functions for setting up trusted external procedure callbacks kpotx kpov  progint/kpo support for managing local and distributed transaction coordination. kpp2 kpp3  sqllang/parse kpp2 – parse routines for dimensions; kpp3 – parse support for create/alter/drop summary  statements kprb kprc  progint/rpi support for executing sql efficiently on the Oracle server side as well as for copying data types during rpi operations kptsc  progint/twotask callback functions provided to all streaming operation as part of replication functionality kpu kpuc...

ORA-600 Lookup Error Categories (part 1b)

ORA-600 Lookup Error Categories   In the Oracle Server source, there are two types of ora-600 error : à the first parameter is a number which reflects the source component or layer the error is connected with; or at the first parameter is a mnemonic which indicates the source module where the error originated. This type of internal error is now used in preference to an internal error number.   Both types of error may be possible in the Oracle server. Internal Errors Categorised by number range The following table provides an indication of internal error codes used in the...

ORA-600 Lookup Error Categories (part 1)

What causes this error? ORA-600 is an internal error generated by the generic kernel code of the Oracle RDBMS software. It is different from other Oracle errors in many ways. The following is a list of these differences: 1. An ORA-600 error may or may not be displayed on the screen. Therefore, screen output should not be relied on for capturing information on this error. Information on ORA-600 errors are found in the database alert and trace files. We recommend that you check these files frequently for database errors. (See the Alert and Trace Files section for more information.) 2....