Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
elie_issa
Creator II
Creator II

Incremental load issue

Hi all,

I am running the below script

Sales:

LOAD business_date,

     bc_id,

     business_unit,

     rvc_num,

     rvc_name,

     chk_num,

     chk_seq,

     r_type,

     mi_obj_num,

     mi_name,

     majgrp_name,

     famgrp_name,

     migrp_name,

     record_name,

     record_type,

     ord_type,

     chk_open_date,

     chk_open_time,

     chk_close_date,

     chk_close_time,

     chk_open_hour,

     chk_close_hour,

     waiter_name,

     table_no,

     cust_cnt,

     quantity,

     d_chk_ttl,

     sub_ttl,

     tax_ttl,

     pymnt_ttl,

     tips_ttl,

     cost,

     chk,

     H_Flag

FROM $(vSalesQvdName) (qvd)

where business_date < $(v45days);

concatenate(Sales)

Load business_date,

     bc_id,

     business_unit,

     rvc_num,

     rvc_name,

     chk_num,

     chk_seq,

     r_type,

     mi_obj_num,

     mi_name,

     majgrp_name,

     famgrp_name,

     migrp_name,

     record_name,

     record_type,

     ord_type,

     chk_open_date,

     chk_open_time,

     chk_close_date,

     chk_close_time,

     chk_open_hour,

     chk_close_hour,

     waiter_name,

     table_no,

     cust_cnt,

     quantity,

     d_chk_ttl,

     sub_ttl,

     tax_ttl,

     pymnt_ttl,

     tips_ttl,

     cost,

     chk,

     H_Flag;

SQL

set transaction isolation level read uncommitted

select * from Fandb.[dbo].[BI_MicrosSalesData] where [business_date] >= '$(v45dayDate)';

After running the above script , sometimes we are getting OLE DB connection failure. In this case i need to make a rollback or if possible retry to reconnect.

if the connection error persist, i need to get the qvd as it is.

Please advise what function should i use to catch the connection error.

Thanks.

1 Solution

Accepted Solutions
swuehl
MVP
MVP

Look into the Error variables in the HELP file.

You can set the ErrorMode to 0 before the SQL statement, then check the ScriptErrorCount and ScriptError vairables after the call and apply appropriate actions.

View solution in original post

1 Reply
swuehl
MVP
MVP

Look into the Error variables in the HELP file.

You can set the ErrorMode to 0 before the SQL statement, then check the ScriptErrorCount and ScriptError vairables after the call and apply appropriate actions.