My Oracle Support Banner

ORA-00600 [17114] When Exporting a Table with VARCHAR2(4000) Field (Doc ID 1300799.1)

Last updated on FEBRUARY 07, 2014

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Information in this document applies to any platform.

Symptoms

Exporting a table with VARCHAR2(4000) Field fails with following errors:

. . exporting table ...
EXP-00056: ORACLE error 39 encountered
ORA-00039: error during periodic action
ORA-00600: internal error code, arguments: [17114], [0xFFFFFFFF7AEE7E80], [], [], [], [], [], []
EXP-00008: ORACLE error 3113 encountered

Call stack trace is similar to:

kgesic1 <- kghrcdepth <- kghrcappl <- kghfrempty_ex <- qesmmIPgaFreeCb <- ksu_dispatch_tac
...
ksu_register_tac <- kccocx <- kcradx1 <- kcbdnbRedo <- kcbdnb <- ksedmp
<- kgesic1 <- kghrcdepth <- kghrcappl <- kghfrempty_ex <- qesmmIPgaFreeCb <- ksu_dispatch_tac <- 984


- Connected session fails with ORA-03113 error.

- Using Data Pump to export and import data in the table with VARCHAR2(4000) Field.
Data Pump import fails with following errors:

KUP-11007: conversion error loading table ...
ORA-26093: input data column size (4233) exceeds the maximum input size (4000)
KUP-11009: data for row: ...


Changes

In this case, a third party tool inserts data from physical files, flat files, to the table with varchar2(4000) field in the database.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.