My Oracle Support Banner

Big Data SQL Queries from Exadata to BDA Hive Tables Fail with "ORA-20000: KUP-11523:" with Exadata Logs Showing BDA Host Access Via the Public Not Private IP Address (Doc ID 2341295.1)

Last updated on FEBRUARY 06, 2020

Applies to:

Oracle Big Data SQL - Version 3.2.0 to 3.2.0 [Release 3.2]
Linux x86-64


NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner. 

In an environment where Big Data SQL (BDS) 3.2 is being used between a BDA cluster and Exadata, SQL queries on the Exadata may fail as below.  In the example here "<HIVE_TABLE>" is the name of a Hive table on the BDA cluster.  Note that the same Hive table can be accessed successfully from Hive.

1. From SQLPLUS on the Exadata the query fails. For example:


Note: The most important symptom for identifying the issue: :<BDA_HOSTNAME1>.<DOMAIN>/<PRIVATE_IP_HOST1>:8020.

Here see the IP address is the public IP address, not the private IP address as expected.



 Upgraded to BDS 3.2


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.