Token Verification fields, but custom query works

replied on February 6, 2014

Is this a table in another schema that you're accessing through a synonim?

0 0

View 4 previous replies

replied on February 6, 2014

Thanks Miruna, the answer is, I don't know, but I'll ask the question of the folks who "own" the database. I know that when I set up the connection, I'm able to both see the view and see the columns within the view, but when I try to validation, I get the error, which I don't get by using the custom query.

I hope to have an answer to your reply shortly. Thank you.

0 0

replied on February 13, 2014

The table is not being accessed through a synonym. Is there a way we could use a custom query for token verification?

0 0

replied on February 13, 2014

The custom query workings using the construct fc.name. I wanted to clarify that this is not a table but a view. The custom query works by using the construct fc.view_name. However, the token verification doesn't work, and I'm wondering if it is dependent on a table or if it should also work against a view.

0 0

replied on February 13, 2014

Is "fc" the schema specified for your connection?

0 0

replied on February 13, 2014

I'm asking the DB folks, but I know our SELECT statement is:

SELECT * FROM fc.scan_rscne WHERE MPI = ?

I also know that when I try to configure the token verification, I configure the source. I then add the token, which presents me with Name, Table, Column, and Input Value.

When I choose the "table," (which is a view, in my case), I'm able to select from a list of tables/views, and I select SCAN_RSCNE. For the column, I can then select any of the columns from within the "table"--let's say it's DOB--

and I can then assign an input value, which is my compare value.

However, when it runs, the result is table does not exist.

0 0

replied on February 24, 2014

Hi Miruna, we're still working on this.

fc. is the schema owner of the tables involved. However, we don't know if the schema owner is specified in the connection or specified in the specific sqls used through the connection.

Our DB folks are asking, "Is it possible to use the Oracle client directly?"

Thanks, Adam

0 0

replied on March 24, 2014

Hi folks, we're still working on this.

Does anyone know why the custom query would work but the token verfication would fail? Would both use the same ODBC CONNECTION? If so, why would one method work and the other fail?

0 0

Question

Question

Token Verification fields, but custom query works

Replies

Sign in to reply to this post.