My Oracle Support Banner

OID 11g Bulkload of Large Amount (Several Millions) of Entries Fails Initially with ORA-12592, Later with ORA-39776 and ORA-00600: internal error code, arguments: [klaprs_<##>], Finally with ORA-03135 and ORA-03114 (Doc ID 2091301.1)

Last updated on MAY 24, 2021

Applies to:

Oracle Internet Directory - Version 11.1.1 and later
Information in this document applies to any platform.


Oracle Internet Directory (OID) 11g, e.g.,

OID bulk load of millions of entries using Document 579529.1 fails:

*Error in loading data for "attr_store001"
For more details, refer bulkload.log*

As indicated above, there were errors during the load of data. This will leave the OID directory content in inconsistent state.
Hence, it is highly recommended that you use the bulkload -recover option to restore the OID directory content to the pre-bulkload state.
If you choose not to use the recover option of bulkload now, then you must restore the OID Database from a backup taken prior to this bulkload invocation so that the Directory content is restored to the pre-bulkload state.

Similar bulkload worked several times in previous environments configured the same way.

Initially there were no errors in the bulkload logs or files (other than a typical "Attribute pwdchangedtime is single valued", but can be skipped/ignored and do not cause problems and worked in previous successful bulkloads.)

Later on bulkload fails for a few different entries, for example, in bsl_attr_store<number>.log bulkload logs:

Record 12954614: Rejected - Error on table DS_ATTRSTORE.
ORA-12592: TNS:bad packet
SQL*Loader-926: OCI error while uldlfca: last loaded row is bigger than the column array size for table DS_ATTRSTORE
SQL*Loader-2026: the load was aborted because SQL Loader cannot continue.

After identifying and removing the few problem entries from the ldif file and retrying, bulkload now returns a different error, for example:

bsl_attr_store001.log:         ORA-39776: fatal Direct Path API error loading table ODS.DS_ATTRSTORE
bsl_attr_store001.log:         ORA-00600: internal error code, arguments: [klaprs_11], [60], [115], [45030627], [], [], [], [], [], [], [], []
bsl_attr_store006.log:         ORA-39776: fatal Direct Path API error loading table ODS.DS_ATTRSTORE
bsl_attr_store006.log:         ORA-00600: internal error code, arguments: [klaprs_11], [60], [36], [14538110], [], [], [], [], [], [], [], []
bsl_orclsecondaryuid.log:   ORA-39776: fatal Direct Path API error loading table ODS.CT_ORCLSECONDARYUID
bsl_orclsecondaryuid.log:   ORA-00600: internal error code, arguments: [klaprs_12], [110], [60], [15979905], [], [], [], [], [], [], [], []

As the bulkload.log also shows the following message:

[BULKLOAD] [host: <OID_HOSTNAME>] [pid: xxxx] [tid:xx] gsltltwWriter: Two realms cannot reference the same DN in orclcommonusersearchbase.

Searching the root oraclecontext shows the default attributes, as after the initial install, as follows:




Tried modifying root oraclecontext base attribute values to match ldif file to be bulkloaded, which resolved the ORA-600 but results in new error ORA-03114 and unusable data and OID server.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.