Sven, This is a recently discovered bug, I am still working on characterizing the issue before writing a Jira to describe it. NIFI-9169 [1] has the same cause but is a slightly different issue. So far the issue seems to be with using update key(s) with "Quote Identifiers" set to true. Setting it to false (if possible for your flow) should allow it to work.
Regards, Matt [1] https://issues.apache.org/jira/browse/NIFI-9169 On Thu, Jan 20, 2022 at 11:15 AM Sven Ritter <sven.rit...@sedapta.com> wrote: > > Hi Mark, > > > > Thanks for the hint with the PutDatabaseRecord processor. > > I tried it. For INSERTS it works fine, but the UPDATE is failing with: > “Routing to failure.: ORA-00936: missing expression”. > > When I enable DEBUG and force the processor to write out the SQL query (by > setting Maximum Batch Size = 1), I get the following: > > > > PutDatabaseRecord[id=cc8716d2-3adc-1ca6-e173-69c231e48341] Executing query > UPDATE "FIRST_LEVEL" SET "S_START_TIME" = ?, "S_ID_KEY" = ?, > "S_STATUS_MESSAGE" = ?, "S_STATUS" = ? WHERE because batch reached max size > for > StandardFlowFileRecord[uuid=e4389b22-b9a6-4632-9321-96e56285f1d7,claim=StandardContentClaim > [resourceClaim=StandardResourceClaim[id=1642609386401-6, container=default, > section=6], offset=77170, > length=105],offset=0,name=dd5e6bae-9a5f-40e6-826d-d8d205a3154b,size=105]; > fieldIndexes: [0, 1, 2, 3]; batch index: 1; batch size: 1 > > > > It seems that “Update Keys” (S_ID_KEY) is not recognized by the processor, > because S_ID_KEY is in the UPDATE itself and the WHERE condition is empty. > > What did I do wrong? > > > > Best Regards > > Sven > >
