Error Handling

[myself]

Hi,

I am doing error handling for two tables. In the process I have intentionally created an error in the sql script of one of the loads, but for my surprise error is thrown in that query that i have created an error and all subsequent sql queries for other loads . I have used Error mode=0 after every load. 
I want other sql queries to successfully complete even if there is an error in the previous sql query.

I am using oracle db.

[BenjaminT]

Could you share some sample script? You mention using set ErrorMode = 0 after every load but you should set it before.

[JonnyPoole]

I haven't had experience with this issue.  Could you share the script clearly showing the errormode setting, the faulty SQL and the working SQL?  

I *wonder* if you have to reissue another CONNECT statement prior to retrying the SQL?  You can test this theory by loading a generic inline table after the failed SQL? If you add the following does this work and still fail at the next SQL? If yes then try adding another CONNECT. Just guessing.. 

Delete:

LOAD * INLINE [Delete];

DROP TABLE Delete;

[MatheusC]

See also the solution in the post below:

https://community.qlik.com/t5/New-to-Qlik-Analytics/Can-a-file-be-ignored-in-a-load-and-not-fail-the...

Regarts, Matheus

[myself]

Test field is not there in the database, I have added it to create an error in the above load. But second query is also showing an error.

After adding the test field, the error was as shown below

[JonnyPoole · Accepted solution]

After the first SQL statement, try adding a duplicate 'LIB CONNECT' statement.  Maybe it will reset the database cursor and not get stuck on the old error. 

[myself · Accepted solution]

Thanks @JonnyPoole might be a simple thing but helped me a lot. Working good.