Get Data Moving 1
Results 1 to 6 of 6

Thread: Terdata ODBC driver Error

  1. #1
    chetan86 is offline Junior Member
    Join Date
    Nov 2016
    Posts
    19
    Rep Power
    0

    Terdata ODBC driver Error

    Hi All,
    We are getting following error when executing job with Teradata (ODBC connection) as source in Attunity Replicate.

    00006120: 2016-12-22T14:13:37 [SOURCE_UNLOAD ]E: Failed to execute statement: 'SELECT "GPS_ID","EQP_ID","EQP_EVNT_STRT_TS","CAL_DT","EQP _EVNT_STRT_TM","EVNT_OCUR_CT","EVNT_SRC_TYP_CD","E VNT_SRC_NM","EVNT_SRC_TYP_DESC","MID_IND","EVNT_SR C_CD","EVNT_STAT_CD","SVRTY_LVL_CD","EVNT_STAT_DES C","ECM_SFTWE_SN","SVC_TL_CHG_LVL","ECM_SN","SFTWE _RLSE_LVL_NUM","MOD_SFTWE_VERS_NUM","SFTWE_SVC_TL_ VERS_NUM","ELECTR_SN","HC11_SFTWE_PTNO","MODEM_SFT WE_PTNO","HDWE_SN","OCUR_CT","EVNT_OCUR_CUM_CT","C RTE_JOB_ID","UPDT_JOB_ID","DTA_SRC_ID","SER_NUM"," MFR_NM","TOTAL_FUEL_USED","REPORTED_HOURS","TOTAL_ IDLE_HOURS","TOTAL_IDLE_FUEL_USED","EQP_GPS_SPEC_L AT_CORD","EQP_GPS_SPEC_LONG_CORD","PRIM_EVNT_CD"," FMI","DIAG_TYP_CD","CID","EID","SPN","DIAG_TYP_DES C" FROM "EDW_BI_SL_M1"."EQP_EVNT"' [1022502] (ar_odbc_stmt.c:2240)
    00006120: 2016-12-22T14:13:37 [SOURCE_UNLOAD ]E: RetCode: SQL_ERROR SqlState: HYT00 NativeError: 0 Message: [Teradata][ODBC Teradata Driver] Query timeout expired [1022502] (ar_odbc_stmt.c:2246)


    Please help.Thanks in Advance

    Regards
    Priyanka

  2. #2
    stevenguyen is offline Senior Member
    Join Date
    May 2014
    Posts
    221
    Rep Power
    3
    Quote Originally Posted by chetan86 View Post
    Hi All,
    We are getting following error when executing job with Teradata (ODBC connection) as source in Attunity Replicate.

    00006120: 2016-12-22T14:13:37 [SOURCE_UNLOAD ]E: Failed to execute statement: 'SELECT "GPS_ID","EQP_ID","EQP_EVNT_STRT_TS","CAL_DT","EQP _EVNT_STRT_TM","EVNT_OCUR_CT","EVNT_SRC_TYP_CD","E VNT_SRC_NM","EVNT_SRC_TYP_DESC","MID_IND","EVNT_SR C_CD","EVNT_STAT_CD","SVRTY_LVL_CD","EVNT_STAT_DES C","ECM_SFTWE_SN","SVC_TL_CHG_LVL","ECM_SN","SFTWE _RLSE_LVL_NUM","MOD_SFTWE_VERS_NUM","SFTWE_SVC_TL_ VERS_NUM","ELECTR_SN","HC11_SFTWE_PTNO","MODEM_SFT WE_PTNO","HDWE_SN","OCUR_CT","EVNT_OCUR_CUM_CT","C RTE_JOB_ID","UPDT_JOB_ID","DTA_SRC_ID","SER_NUM"," MFR_NM","TOTAL_FUEL_USED","REPORTED_HOURS","TOTAL_ IDLE_HOURS","TOTAL_IDLE_FUEL_USED","EQP_GPS_SPEC_L AT_CORD","EQP_GPS_SPEC_LONG_CORD","PRIM_EVNT_CD"," FMI","DIAG_TYP_CD","CID","EID","SPN","DIAG_TYP_DES C" FROM "EDW_BI_SL_M1"."EQP_EVNT"' [1022502] (ar_odbc_stmt.c:2240)
    00006120: 2016-12-22T14:13:37 [SOURCE_UNLOAD ]E: RetCode: SQL_ERROR SqlState: HYT00 NativeError: 0 Message: [Teradata][ODBC Teradata Driver] Query timeout expired [1022502] (ar_odbc_stmt.c:2246)


    Please help.Thanks in Advance

    Regards
    Priyanka

    Can you run the selects outside of Replicate using the same ODBCDNS source and what happens?

    Are these wide tables with LOB fields?


    How many tables are on this task?


    If you setup just one table does it works?

  3. #3
    Hein is offline Senior Member
    Join Date
    Dec 2007
    Location
    Nashua, NH - USA.
    Posts
    109
    Rep Power
    10
    Quote Originally Posted by chetan86 View Post
    Hi All,
    We are getting following error when executing job with Teradata (ODBC connection) as source in Attunity Replicate.

    00006120: 2016-12-22T14:13:37 [SOURCE_UNLOAD ]E: Failed to execute statement: 'SELECT "GPS_ID","EQP_ID",.... "SPN","DIAG_TYP_DESC" FROM "EDW_BI_SL_M1"."EQP_EVNT"' [1022502] (ar_odbc_stmt.c:2240)
    00006120: 2016-12-22T14:13:37 [SOURCE_UNLOAD ]E: RetCode: SQL_ERROR SqlState: HYT00 NativeError: 0 Message: [Teradata][ODBC Teradata Driver] Query timeout expired [1022502] (ar_odbc_stmt.c:2246)
    The most common reason for this error is simple a LOCK on the source table.
    The typical timeout value is 20 minutes, which you can verify by looking at the lines in the log just before the error.

    fwiw,
    Hein

  4. #4
    chetan86 is offline Junior Member
    Join Date
    Nov 2016
    Posts
    19
    Rep Power
    0
    Quote Originally Posted by stevenguyen View Post
    Can you run the selects outside of Replicate using the same ODBCDNS source and what happens?

    Are these wide tables with LOB fields?


    How many tables are on this task?


    If you setup just one table does it works?



    There are 3 views in task we are getting same error even if executing one table at a time.

  5. #5
    chetan86 is offline Junior Member
    Join Date
    Nov 2016
    Posts
    19
    Rep Power
    0
    Quote Originally Posted by Hein View Post
    The most common reason for this error is simple a LOCK on the source table.
    The typical timeout value is 20 minutes, which you can verify by looking at the lines in the log just before the error.

    fwiw,
    Hein


    Hi Hein,

    I am not able to see timeout value in log .Attaching log for reference.What could be the solution for this problem.Data volume is large in source tables.

    Regards
    Priyanka
    Attached Files Attached Files

  6. #6
    Hein is offline Senior Member
    Join Date
    Dec 2007
    Location
    Nashua, NH - USA.
    Posts
    109
    Rep Power
    10
    Quote Originally Posted by chetan86 View Post
    Hi Hein,

    I am not able to see timeout value in log .Attaching log for reference.What could be the solution for this problem.Data volume is large in source tables.

    Regards
    Priyanka
    Thanks for the log.

    Code:
    >> 00004556: 2017-01-02T01:10:33 [SOURCE_UNLOAD   ]I:  Source endpoint 'ODBC' is using provider syntax 
    :
    >> 00006420: 2017-01-02T01:10:39 [TARGET_LOAD     ]I:  Full load Max file size: 1048576 bytes
    >> 00004556: 2017-01-02T01:11:42 [SOURCE_UNLOAD   ]E:  Failed to execute statement: 'SELECT "GPS_ID"
    >> 00004556: 2017-01-02T01:11:42 [SOURCE_UNLOAD   ]E:  RetCode: SQL_ERROR  SqlState: HYT00 NativeError: 0 Message: [Teradata][ODBC Teradata Driver] Query timeout expired [1022502]  (ar_odbc_stmt.c:2246)
    Hmmm, that's just over 60 seconds. That could be the default ODBC driver time-out, lock or otherwise, I don't know.

    Really the best thing to do in these circumstances is to lift the SQL from the reptask log, and execute it in a generic ODBC based query tool, or maybe TeradataStudioExpress
    Does it run fine, or give a similar error perhaps with more details?
    (Note, you may want to put a 'limit' on the query)

    Btw... a Max full-load file size of 1MB may be fine for DEV testing, but seems small for high volume production.
    I would sooner expect 100 MB or 1GB

    Hope this helps,
    Hein

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •