In case anybody else runs into this. I added the schema to the DB Catalog instead of the DB Schema Pattern. This resolved the issue I was having.
On Sep 12, 2019, at 12:30 PM, Support support@arrahtech.com wrote:
https://sourceforge.net/p/dataquality/discussion/602692/thread/5b1857a3/?limit=25#dec3
https://sourceforge.net/p/dataquality/discussion/602692/thread/bea09f66/
Hope it works for you.
Hi, I’ve got the profiler tool and was attempting to use it on a postgres system.
The postgres is in AWS. I’ve got three schemas in the database, production, data, and extract.
When I connect I setup the connection and add extract as the schema to use. Everything seems to connect correctly.
Connection screen:
<1.png>
However, when I click on a table name it gives me a error:
<2.png>
I’m not sure what else I can do.
Any suggestions?
Log in to post a comment.
In case anybody else runs into this. I added the schema to the DB Catalog instead of the DB Schema Pattern. This resolved the issue I was having.
On Sep 12, 2019, at 12:30 PM, Support support@arrahtech.com wrote:
https://sourceforge.net/p/dataquality/discussion/602692/thread/5b1857a3/?limit=25#dec3
https://sourceforge.net/p/dataquality/discussion/602692/thread/bea09f66/
Hope it works for you.
Hi, I’ve got the profiler tool and was attempting to use it on a postgres system.
The postgres is in AWS. I’ve got three schemas in the database, production, data, and extract.
When I connect I setup the connection and add extract as the schema to use. Everything seems to connect correctly.
Connection screen:
<1.png>
However, when I click on a table name it gives me a error:
<2.png>
I’m not sure what else I can do.
Any suggestions?