JDBC producer complains ${record:attribute('tablename')} does not exist or PDB is incorrect, but will not allow literal

asked 2018-03-20 17:41:34 -0500

lampshadesdrifter gravatar image

updated 2018-03-20 19:26:09 -0500

Attempting to use streamsets to copy a single oracle DB table to a MS SQL Server table, but am getting error

JDBC_16 - Table '' does not exist or PDB is incorrect. Make sure the correct PDB was specified

from the JDBC Producer destination.

I have installed both JDBC drivers for the respective DBs, connection strings throw no error on validation, and can successfully Preview the pipeline (when using the default JDBC Producer/JDBC/Table Name field value ${record:attribute('tablename')}). The problem is that when running the pipeline "for real", every record sent to the producer throws the error

JDBC_16 - Table '' does not exist or PDB is incorrect. Make sure the correct PDB was specified

Looking on the streamsets google group (https://groups.google.com/a/streamset...) and further examining the data in the pipeline Preview shows that there is in fact no ${record:attribute('tablename')}in the oracle JDBC Consumer data (only the data map-list itself). From that same google groups discussion thread, there is the advice (https://groups.google.com/a/streamset...) to explicitly name the table (in my case, say, PAT_ENC). Yet, when doing this, the pipeline does not pass validation to even let me try to use that explicit naming, eg.

JDBC_16 - Table 'PAT_ENC' does not exist or PDB is incorrect. Make sure the correct PDB was specified

Does anyone know what to do at this point? Thanks.

Extra info:

oracle consumer connection string format:

jdbc:oracle:thin:myname/mypass@dbserver:dbport/db

ms sql server producer connection string format:

jdbc:sqlserver://someserver:someport;database=somedb;user=someuser;password=somepass

streamsets version:

StreamSets Data Collector 3.0.1.0 ( built by root on 2017-12-27T02:21Z git: af72012507f63eccc75cd6a8659cfb2c9c1fecce)

edit retag flag offensive close merge delete

Comments

Did you ever figure out the answer here? Looking at it now, perhaps case sensitivity was to blame - did you try 'pat_enc'?

metadaddy gravatar imagemetadaddy ( 2018-06-07 09:58:28 -0500 )edit