@lopespetro based on the stack trace, it looks like this originates from a package C_MOBILE_NAO_CONFORM_EVU which looks like a customization. Is this indeed a customization and have you looked at the logic there? It looks like you’re trying to read Signature into a VARCHAR2 that’s too small.

Hope this helps!

Rukmal

Hi @Rukmal Fernando , tks for the info. This is the trigger created by IFS and do you have any ideia how to fix this error?

it’s strange because the SGNATURE is not inside it. Just in the code.

  BEGIN
    IF ('&NEW:ANSWER' = 'SIGNATURE' AND '&OLD:ROWVERSION' IS NOT NULL AND '&NEW:ROWVERSION' IS NOT NULL) THEN
      survey_rec_ := Get_Surveys;

CREATE OR REPLACE TRIGGER IFSPET.C_MOBILE_NAO_CONFORM_EVU
   AFTER UPDATE ON JT_TASK_SURVEY_ANSWERS_TAB
   FOR EACH ROW 
BEGIN 
   
   DECLARE
      msg_  VARCHAR2(32767);
   BEGIN 
      IF (Event_SYS.Event_Enabled('JtTaskSurveyAnswers', 'C_MOBILE_NAO_CONFORM')) THEN 
         msg_ := Message_SYS.Construct('C_MOBILE_NAO_CONFORM');
         Message_SYS.Add_Attribute(msg_, 'LU', 'JtTaskSurveyAnswers');
         Message_SYS.Add_Attribute(msg_, 'ROWKEY', :NEW.ROWKEY);
         Message_SYS.Add_Attribute(msg_, 'NEW:ALTERNATIVE_ID', :NEW.ALTERNATIVE_ID);
         Message_SYS.Add_Attribute(msg_, 'NEW:ANSWER', :NEW.ANSWER);
         Message_SYS.Add_Attribute(msg_, 'NEW:ANSWER_ID', :NEW.ANSWER_ID);
         Message_SYS.Add_Attribute(msg_, 'NEW:ANSWER_SET', :NEW.ANSWER_SET);
         Message_SYS.Add_Attribute(msg_, 'NEW:COMPANY_ID', :NEW.COMPANY_ID);
         Message_SYS.Add_Attribute(msg_, 'NEW:DATE_CREATED', to_char(:NEW.DATE_CREATED, 'YYYY-MM-DD'));
         Message_SYS.Add_Attribute(msg_, 'NEW:EMP_NO', :NEW.EMP_NO);
         Message_SYS.Add_Attribute(msg_, 'NEW:ITEM_NO', :NEW.ITEM_NO);
         Message_SYS.Add_Attribute(msg_, 'NEW:MCH_CODE', :NEW.MCH_CODE);
         Message_SYS.Add_Attribute(msg_, 'NEW:MCH_CODE_CONTRACT', :NEW.MCH_CODE_CONTRACT);
         Message_SYS.Add_Attribute(msg_, 'NEW:QUESTION', :NEW.QUESTION);
         Message_SYS.Add_Attribute(msg_, 'OLD:QUESTION_ID', :OLD.QUESTION_ID);
         Message_SYS.Add_Attribute(msg_, 'NEW:QUESTION_ID', :NEW.QUESTION_ID);
         Message_SYS.Add_Attribute(msg_, 'OLD:ROWKEY', :OLD.ROWKEY);
         Message_SYS.Add_Attribute(msg_, 'NEW:ROWKEY', :NEW.ROWKEY);
         Message_SYS.Add_Attribute(msg_, 'OLD:ROWVERSION', to_char(:OLD.ROWVERSION, 'YYYY-MM-DD'));
         Message_SYS.Add_Attribute(msg_, 'NEW:ROWVERSION', to_char(:NEW.ROWVERSION, 'YYYY-MM-DD'));
         Message_SYS.Add_Attribute(msg_, 'NEW:SURVEY_ID', :NEW.SURVEY_ID);
         Event_SYS.Event_Execute('JtTaskSurveyAnswers', 'C_MOBILE_NAO_CONFORM', msg_);
      END IF; 
   END; 
   
END;

Hi, maybe you can check the underlying table where the signature will be saved in the database.

This error indicates to me that the underlying table or column for the signature may be to small

ORA-06502: PL/SQL: numeric or value error: character string buffer too small 

ORA-06512: at "IFSPET.JT_TASK_SURVEY_ANSWERS_API", line 1221
ORA-06512: at "IFSPET.JT_TASK_SURVEY_ANSWERS_API", line 1231

Hi, I took a look but I could not find anything related. Cloud you guys help me see the logs and check if there is something wrong?

It’s strange that I tested with another IOS phone and the same version 17.4.1 and worked. The user already cleaned data and cache but still getting this problem.

@Rukmal Fernando , @Bjornar Brekka 

Logs in attach.

A good example is april 12, the server synced all the answers except the signature.