Welcome Guest! Log in
×

Notice

The forum is in read only mode.
Due to some maintenance operations, stambia.org will be switched to read-only mode during the 13th November. It will be possible to read and download, but impossible to post on the forums or create new accounts. For any question please contact the support team.

Topic-icon Question Table or view does not exiat

More
16 Feb 2018 09:34 #1 by jerryjosejames1
jerryjosejames1 created the topic: Table or view does not exiat
I am getting the below error from stambia.
SQL Exception Error: ORA-00942: Table or nonexistent view
ORA-06512: to line 2.
We have a few database connections available.How to find out which to which region Stambia points to?
More
16 Feb 2018 17:22 - 16 Feb 2018 17:23 #2 by Adrian MATYSIAK
Adrian MATYSIAK replied the topic: Table or view does not exiat
Hi,

Is it an error during execution of a mapping?
On which action do you have this error ?
First thing to do is to consult the generated and executed code of the action.
Here is a link that explains how to do it.
stambia.org/stambia_internal/di/stambia-...ringthegeneratedcode
This will tell you which schemas and tables were used in the SQL command that caused the error and should help you to understand where the error comes from.

Kind regards,
Adrian
Last Edit: 16 Feb 2018 17:23 by Adrian MATYSIAK.
More
19 Feb 2018 07:20 #3 by jerryjosejames1
jerryjosejames1 replied the topic: Table or view does not exiat
I am getting this error for a process.Its a simple process with 3 SQL operations.Its giving error on the second process
More
19 Feb 2018 07:31 #4 by jerryjosejames1
jerryjosejames1 replied the topic: Table or view does not exiat
Attachments:
More
20 Feb 2018 11:37 #5 by Adrian MATYSIAK
Adrian MATYSIAK replied the topic: Table or view does not exiat
Hi,

can you let us know what code is generated by the action that is showing the error?
Once you know the code a simple test is to right click on the table Action>SQL Editor and try to execute the generated code in SQL Editor.
You should of course get the same error and you can then try to adjust the code to solve it and finally make appropriate changes in the action code.
Perhaps you are missing a schema name in front of the table name in the sql code ?