What is wrong with these data jobs ?

Some ideas

• first error, it seems you have some LIMIT or OFFSET clause in some place in the script. Although in the Vertica SQL documentation can be allowed, not all the features have been ported to Celonis, so maybe that's the problem
• Second error... not sure but, AFAIK, the aliases (AS xxxx) only work inside the same SQL operation (that's, until next ";") ... so maybe those 2 lines belong to different SQL operations... no idea.

HTH

"first error, it seems you have some LIMIT or OFFSET clause in some place in the script. Although in the Vertica SQL documentation can be allowed, not all the features have been ported to Celonis, so maybe that's the problem"

But the problem is I do not (:

"Second error... not sure but, AFAIK, the aliases (AS xxxx) only work inside the same SQL operation (that's, until next ";") ... so maybe those 2 lines belong to different SQL operations... no idea"

But it was working 2 minutes ago and I did not changed anything (:

Witchcraft, then? :D

In that case, my guesses will be (no necessary in order):

• data in the tables has changed
• some typo added to the SQL text inadvertently
• some odd glitch in the browser side --> reload or close and log in again

Sorry can't help you much more :(

Hi Omer - Would you be able to share the SQL snippet to debug?

Probably 3rd one my friend. I think there is a bug. I tried to add a field to a table and reversed it (UNION BSEG one ). but it is stuck in this error. can not clear cash or something. Vertica seems have some problems.

sure. Here you go.

the problem was ALTER statement and I commented it and worked then started "SELECT ANALYZE_STATISTICS ('BSEG');" line get error. but these are standard connector codes.

DROP VIEW IF EXISTS "BSEG_UNION";

--Start of customization section

--If you extract new records though Replication Cockpit, leave this CREATE VIEW BSEG_UNION statement and delete/comment out the second one.

CREATE VIEW "BSEG_UNION" AS (

SELECT * FROM "BSID"

UNION ALL

SELECT * FROM "BSAD"

);

--If you extract new records through Data Jobs, leave this CREATE VIEW BSEG_UNION statement and delete/comment out the first one.

/*

CREATE VIEW "BSEG_UNION" AS (

SELECT

MANDT,BUKRS,KUNNR,UMSKS,UMSKZ,AUGDT, AUGBL,ZUONR,GJAHR,BELNR,BUZEI, BUDAT,CPUDT,BSCHL,SHKZG,DMBTR,WRBTR,SGTXT,ZFBDT,ZTERM,ZBD1T,ZBD2T,ZBD3T,ZBD1P,ZBD2P,SKFBT,SKNTO,WSKTO,REBZG,REBZJ,REBZZ,MANSP,MSCHL,MANST,REBZT,AUGGJ,NULL AS AUGCP,_CELONIS_CHANGE_DATE

FROM "BSID"

UNION ALL

SELECT

MANDT,BUKRS,KUNNR,UMSKS,UMSKZ,AUGDT,AUGBL,ZUONR,GJAHR,BELNR,BUZEI, NULL AS BUDAT,NULL AS CPUDT,BSCHL,SHKZG,DMBTR,WRBTR,SGTXT,ZFBDT,ZTERM,ZBD1T,ZBD2T,ZBD3T,ZBD1P,ZBD2P,SKFBT,SKNTO,WSKTO,REBZG,REBZJ,REBZZ,MANSP,MSCHL,MANST,REBZT,AUGGJ,AUGCP,_CELONIS_CHANGE_DATE

 FROM "BSEG_CL"

);

*/

--End of customization section

--THIS SECTION IS COMMON FOR RC AND NON-RC SETUP

DROP TABLE IF EXISTS "BSEG" ;

CREATE TABLE "BSEG" AS(

SELECT

    ROW_NUMBER()

        OVER(PARTITION BY "BSEG"."MANDT", "BSEG"."BUKRS", "BSEG"."BELNR", "BSEG"."GJAHR", "BSEG"."BUZEI"

            ORDER BY "BSEG"."AUGBL","BSEG"."MANDT", "BSEG"."BUKRS", "BSEG"."BELNR", "BSEG"."GJAHR", "BSEG"."BUZEI" ) AS NUM

    ,"BSEG".*

FROM

    "BSEG_UNION" AS BSEG

);

DELETE FROM "BSEG" WHERE NUM > 1;

ALTER TABLE "BSEG" DROP COLUMN NUM CASCADE;

DROP VIEW IF EXISTS "BSEG_UNION";

SELECT ANALYZE_STATISTICS ('BSEG');

how can you debug it ? data job interface also needs debugger and more features !