In tRedshiftOutput, Action on table --> Create table is not working

[Anonymous]

Hi,
Below is my job flow in which i am exracting a data from mysql, transforming it twice using tmap and creating a csv file. Now i want this csv file to be inserted in my Redshift. I do not have that table in Redshift. So i selected Action on table --> Create table in tRedshiftOutput component. But it keeps on failing stating
Exception in component tRedshiftOutput_2
org.postgresql.util.PSQLException: ERROR: relation "my_csv_table" does not exist

[Anonymous]

Thanks for helping me.
I am sorry i did not get you. We always need to specify table name inside double quotes, which i have done. Check screenshot in my above post where i gave basic settings details.

[Anonymous]

Hi,
Could you please have a try to use "ELOQUA.SG_COUNT" as your table name to see  if it is working?
Best regards
Sabrina

[Anonymous]

Does not work. Still same error.
Eloqua is the name of schema. I also tried removing that from the table name. But that also didn't work.

[Anonymous]

Its strange. But when I changed tRedshiftOutput component to use public schema, it worked and created table in public schema. But, when I use any other schema, it doesn't work.
Do not think there would be permission issue as I am able to create table in Redshift manually in any other schema.

[Anonymous]

Hi,
Could you use your schema (not the public one) to make Redshift DB connection successfully in DB metadata?
Best regards
Sabrina

[Anonymous]

Yes. I can.

[Anonymous]

Has this been solved? I am experiencing the same problem.
What I think the problem is here, is that the schema name is missing from the table when checking.
SELECT = exists in a different schema!
INSERT . = going wrong
I think this needs a (quick) fix in the tRedshift components.

[_AnonymousUser]

Hi,
Even i face a similar problem. The tredshiftoutput works fine in update configuration when the job has its own redshift connection. But throws error with "tablename" relation does not exist when using a shared connection of parent job. Although the tredshiftoutput component which are configured for inserts work fine in both scenarios, so i am certain that the Connection is not a problem and Also the "schema.table" relation actually exists in the database.
Is there a resolution to this or has this been resolved in any on the release. I am trying to establish a SCD2 process with redhshift being the target.
I am using Version - 5.5.1 Buid - r118616

[Anonymous]

Hi, we were having the same problem in the tRedshiftOutput component, and found that when we unticked the 'extend insert' option under its advanced setting, and added a row -> main after the tRedshiftOutput to a tRedshiftCommit (untick the auto close connection), then the job ran without any issues.

[Anonymous]

the same problem happened with me, thanks Lourens for the solution, that works

Hi, we were having the same problem in the tRedshiftOutput component, and found that when we unticked the 'extend insert' option under its advanced setting, and added a row -> main after the tRedshiftOutput to a tRedshiftCommit (untick the auto close connection), then the job ran without any issues.