As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at email@example.com and provide your corporate email address, company, and name.
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.
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.
Thank you for using Focal Point!
Chuck Wolff - Focal Point Moderator WebFOCUS 7x and 8x, Windows, Linux All output Formats
Posts: 2128 | Location: Customer Support | Registered: April 12, 2005