Hi All,

I am trying to create synonymn using JDBC adapter to AWS redshift cloud . The sql passthrough is working but the Synonymn creation fails to identify any tables.

Error as below:
(FOC1568) Datasource {tablename} FOR SYNONYMN not found.

What can be the possible solutions.

Thanks,
Rajna

This message has been edited. Last edited by: FP Mod Chuck,

What exact version of WebFOCUS are you using? I don't remember Redshift in 8.1xx.

If you go to the Redshift connection and open Properties, can you click Test?

Also, have you set a Default Database?

Hi ,

We are using JDBC connection which we used for Netezza and the SQL passthrough is working fine. We are in 8.1.5 version.Yes using Default Database option.

Thanks,
Rajna

Sorry, I'm on 8.206 and there's an ODBC Redshift Adapter listed on my Reporting Server as an option. I never tried JDBC.

There is a manual syntax you could try:

 CREATE SYNONYM baseapp/table FOR schema.table DBMS dbtype AT adaptername
 

quote:

CREATE SYNONYM baseapp/table FOR schema.table DBMS SQLORA AT adaptername

I tried using above syntax but receiving below error.

(FOC1658) DATASOURCE PLAN FOR SYNONYM NOT FOUND

Kindly suggest. We are using 8.1.5.

Rajna

This case on techsupport may help you. https://techsupport.informatio...track/200213048.html Look at the last entry.

Hi Chuck,

I am unable to view that link . Can you please post the content here from the last section.

Thanks,
Rajna

i was able to create synonym via SQL script method and then edited the .acx file to point to needed connection and that worked. The GUI method is still having some issues.

Rajna

I'm glad you were able to get the synonym created. Here is what was in that case just as a reference for others.

It sounds like you may be having to fish for the correct ID/Schema to get a the data. This still looks like an ID security issue. If this was setup by IBI maybe Sal, we'll need to check with him on what ID should be used to get at the data.

Both sets of traces show (as expected), the same ODBC calls to Stored Procedures made to the data source. SQLCoumns, SQLTables etc.. so its not a product issue. Once you the proper ID (for step 3) you should be good to go. Hopefully someone from CalState and provide some guidance. Below is some information I found from the aws documentation on Redshift.

https://docs.aws.amazon.com/re...ibility-of-data.html

Visibility of Data in System Tables and Views

There are two classes of visibility for data in system tables and views: visible to users and visible to superusers.

Only users with superuser privileges can see the data in those tables that are in the superuser-visible category. Regular users can see data in the user-visible tables. To give a regular user access to superuser-visible tables, GRANT SELECT privilege on that table to the regular user.