Oracle ORA-00600: [dmlsrvcollenchk_2: DTY] Error description

 

Someone posted an error in the group:

ORA-00600: Internal error code, parameter: [dmlsrvcollenchk_2: DTY], [2], [0], [16896], [], [], [], [], [], [], [], []

ORA-06512: In "idbg17_dev.etl_link13_llr_brn", line 44

ORA-06512: In line 2

 

I searched the mos and wrote an article to explain:

ORA-00600: [dmlsrvcollenchk_2: DTY], [2] During insert [ID 437343.1]

 

An Insert statement fails with thefollowing error and stack trace:
-- The insert operation fails and the following error is reported.

ORA-00600: Internal error code, arguments: [dmlsrvcollenchk_2: DTY], [2], [], [], [], [], [], []

Stack trace:

Ksedst ksedmp ksfdmp kgerinv kgeasnmierrdmlsrvcollenchk
Insloadrow qermtrop pgosf342_qersqrow procedure qerstmetch qersqfetch

 

I. Cause of this error:

This is a bug 5526494 whichis closed duplicate of base bug 6627733:

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

 

This problem is introduced by the fix for Bug 3447792.

-- This problem was introduced by bug3447792.

 

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.

-- A ORA-600 [dmlsrvcollenchk_2: DTY] error occurs when null is inserted into a character type field or a date, numberic type field is inserted into null.

 

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

Ii. solution:

Bug 6627733 is fixed inoracle releases 10.2.0.5.0, 11.1.0.7.0 and 12.1.0.0.0.

-- Bug 6627733 has been fixed after 10.2.0.5 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.

-- To solve this problem, you can also apply patch 6627733.

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 ));

 

 

 

 

 

Bytes -------------------------------------------------------------------------------------------------------

All rights reserved. reprinted articles are allowed, but source addresses must be indicated by links. Otherwise, the documents will be held legally responsible!

Skype: tianlesoftware

Email: tianlesoftware@gmail.com

Blog: http://www.tianlesoftware.com

WEAVER: http://weibo.com/tianlesoftware

Twitter: http://twitter.com/tianlesoftware

Facebook: http://www.facebook.com/tianlesoftware

LinkedIn: http://cn.linkedin.com/in/tianlesoftware

 

------- Add a group to describe the relationship between Oracle tablespace and data files in the remarks section. Otherwise, reject the application ----

Dba1 group: 62697716 (full); dba2 group: 62697977 (full) dba3 group: 62697850 (full)

Super DBA group: 63306533 (full); dba4 group: 83829929 dba5 group: 142216823

Dba6 group: 158654907 dba7 group: 172855474 DBA group: 104207940