BDS V2.0 Query on an External Table Raises "ORA-29913: error in executing ODCIEXTTABLEOPEN callout"/KUP-11503: cannot access cluster (Doc ID 2122654.1)

Last updated on SEPTEMBER 05, 2017

Applies to:

Oracle Big Data SQL - Version 2.0 and later
Linux x86-64

Symptoms

1. With BDS V2.0 running a select query on an external table raises:

ORA-29913: error in executing ODCIEXTTABLEOPEN callout
ORA-29400: data cartridge error
KUP-11503: cannot access cluster

2. The associated log4j shows:

[# JNIAGE] 16/03/22 12:01:40 DEBUG sql.JXADProvider: process pid=<pid>
[# JNIAGT] 16/03/22 12:01:40 DEBUG sql.JXADProvider: cluster link=BDSQL$_*
[# JNIAGT] 16/03/22 12:01:40 DEBUG sql.JXADProvider: created agent handle=3
[# JNIAGT] 16/03/22 12:01:40 DEBUG sql.JXADProvider: created agent context=0x*
[# JNIAGT] 16/03/22 12:01:40 DEBUG sql.JXADProvider: using jvm pointer=0x*
[# JNIAGT] 16/03/22 12:01:40 DEBUG sql.JXADProvider: using jni handle=0x*
[# JNIAGT] 16/03/22 12:01:40 DEBUG sql.JXADProvider: ...access denied
[# JNIAGT] 16/03/22 12:01:40 DEBUG sql.JXADProvider: using agent handle=3
[# JNIAGT] 16/03/22 12:01:40 DEBUG sql.JXADProvider: using agent context=0x*
[# JNIAGT] 16/03/22 12:01:40 DEBUG sql.JXADProvider: using agent jvm pointer=0x*
[# JNIAGT] 16/03/22 12:01:40 DEBUG sql.JXADProvider: using agent jni handle=0x*
[# JNIAGT] 16/03/22 12:01:40 DEBUG sql.JXADProvider: using agent pro handle=0x*
[# JNIAGT] 16/03/22 12:01:40 DEBUG sql.JXADProvider: process pid=<pid>
[# JNIAGT] 16/03/22 12:01:40 DEBUG sql.JXADProvider: cluster link=BDSQL$_*
[# JNIAGT] 16/03/22 12:01:40 DEBUG sql.JXADProvider: freeing agent context=0x7*...

This shows directory permission error.

3. The DB on Exadata is configured as CDB and a select query from a PDB is being run.

4. The same test made directly from a CDB works.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms