群里有人贴了一个错误：
ora-00600: 内部错误代码, 参数:[dmlsrvcollenchk_2:dty], [2], [0], [16896], [], [], [], [], [], [], [], []
ora-06512: 在 "idbg17_dev.etl_link13_llr_brn", line 44
ORA-06512: 在 line 2
ORA-00600: [dmlsrvColLenChk_2:dty], [2]During Insert [ID 437343.1]
An insert statement fails with thefollowing error and stack trace:
ORA-00600: internal error code, arguments:[dmlsrvColLenChk_2:dty], [2], [], [],[], [], [], []
ksedst ksedmp ksfdmp kgerinv kgeasnmierrdmlsrvColLenChk
insLoadRow qermtRop PGOSF342_qersqRow Procedure qerfiFetch qersqFetch
Bug 5526494.-P Base Bug 6627733
abstract: ora-600 [dmlsrvcollenchk_2:dty], [12] running insert as select
Base Bug 6627733
Abstract: OERI[dmlsrvColLenChk_2:dty] inserting NULLs into CHAR length semanticscolumn
ORA-600 [dmlsrvColLenChk_2:dty] can occur when inserting NULL values into columns with character length semantics along with NULL into DATE or NUMERIC columns in an insert SQL.
eg:
create table bug6627733
(
VAR_CHAR VARCHAR2(3 CHAR),
SOME_DATE DATE
);
INSERT ALL
WHEN 1=1
THEN
INTO bug6627733 ( VAR_CHAR, SOME_DATE )
VALUES ( NULL, NULL )
SELECT NULL FROM dual;
^
ORA-600
Bug 6627733 is fixed inOracle releases 10.2.0.5.0, 11.1.0.7.0 and 12.1.0.0.0.
To implement the solution, please downloadand apply Patch 6627733 if it is available for your platform.
In some cases, a possible workaround is to alter the columns of typeVARCHAR2(nn CHAR) as shown in the example below.
First identify table(s) involved in the failing query and then describe thetable(s). For example:
SQL> descr kf_abschluss_tst
Name Null? Type
-------------------------------- -------- ------------------
C_KONTO_ID NOT NULL VARCHAR2(19 CHAR)<==
C_MANDANT NOT NULL NUMBER(5)
B_ENDE NOT NULL NUMBER(18,3)
F_ZU_KOMPENSIERENDER_ABSCHLUSS NOT NULL NUMBER(1)
C_KONTO_ID_ZINSAUS VARCHAR2(19 CHAR) <==
WORKAROUND:
Modify columns of type VARCHAR2(nn CHAR) and remove maximum length sizecharacters
Example:
alter table kf_abschluss_tst modify (c_konto_id varchar2(19));