BDS V2.0 Query Raises "ORA-29913: error in executing ODCIEXTTABLEOPEN callout"
(Doc ID 2122653.1)
Last updated on SEPTEMBER 30, 2018
Applies to:Oracle Big Data SQL - Version 2.0 and later
On BDS 2.0/BDA 4.3/Exadata 22.214.171.124 with Bundle Patch 10 it is possible to create an external table, but querying data from the external table raises:
ORA-29913: error in executing ODCIEXTTABLEOPEN callout
ORA-29400: data cartridge error
ORA-28575: unable to open RPC connection to external procedure agent
Troubleshooting ORA-29913: error in executing ODCIEXTTABLEOPEN callout
1. Since ODCIEXTTABLEOPEN can indicate that extproc is not being started or the listener not being configured:
a) Check if the extproc is started:
To do so run:
You should see a process running. If you do not, use crsctl to restart the process.
oracle 3251 0.0 0.0 103300 812 pts/0 S+ 17:25 0:00 grep bds
oracle 6835 0.1 0.7 36170352 463528 ? Ssl 14:06 0:16 extprocbds_orcl_democluster -mt
b) Check the listener:
Run "lsnrctl status | grep bds"
Service "bds_orcl_democluster" has 1 instance(s).
Instance "bds_orcl_democluster", status READY, has 30 handler(s) for this service...
You should see 10-30 handlers for the extproc. If not, restart the listener for the extproc.
2. Check the logs from the bds-ex-install.sh script.
In this case the logs from bds-ex-install.sh show there is no bds resource on Exadata. They show:
bds-exa-install: mta shutdown : bds_wecdb1pf_s1_*
ORA-28593: agent control utility: command terminated with error
bds-exa-install: registering crs resource : bds_wecdb1pf_s1_*
bds-exa-install: skipping crs registration on this instance
No real error is reported by the above, rather the command terminates with an error message which is the result of trying to stop the service just in case it was running.
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
|Troubleshooting ORA-29913: error in executing ODCIEXTTABLEOPEN callout|