Skip to main content

In IFS Cloud, PL/SQL event actions ("Execute Online PLSQL Block") have a character limit. While the system allows up to 4000 characters (and this limit can be bypassed via direct edit), the effective limit for exporting Application Configuration Packages (ACPs) containing these actions is approximately 3980 characters. Exceeding this limit during ACP export results in the following error:

 

JSON

{
    "error": {
        "code": "DATABASE_ERROR",
        "message": "Database error occurred. Contact administrator.",
        "details":  
            {
                "code": 19202,
                "message": "ORA-19202: Error occurred in XML processing"
            }
        ]
    }
}

 

This issue is specific to ACP exports. If the event action logic is not delivered via ACPs, this character limit does not apply, as the underlying database column is a CLOB, which can handle significantly larger text blocks. Therefore, the problem only arises when exporting ACPs containing PL/SQL event actions that approach or exceed the ~3980-character limit.

Hi ​@nithbtns111 ,

 

We found this issue even when trying to import the event action as a single item from the ACP.

I don’t see any other option to export only the event action from event action details page. When exporting the event as an .ins that doesn't seem to contain the event action contain. Do you have any idea to get only exported event action to avoid this error? This is 24R2

 

 

 

 

Best Regards,

Methshika

Hi ​@SYBMETHSHIKA 

Try reducing event action characters below 3988 limit and see.
That is the only way to avoid this error.

Simple software like NotePad ++ shows the character count for your reference.
 

​@nithbtns111  how could still export then custom actions which are higher then 4000 chars? or is it really a hard limit to only use 4000 chars? and then you change it in the exported xml? 

Can you then also import it again using the ACP?

 

​@kvbe we could not resolve this issue and what we did was remove the event action from the ACP and deliver only the event actions with less than 3988 characters via ACPs. Then deliver the event actions with higher characters manually by saving the PLSQL logic to a file. 

​@nithbtns111  and how did you manually deliver them? I mean how can you go over the 4000 char limit? as the input box limits you on 4000? but the db column is a clob just was wondering how you can go over the 4000 limit then? Thank you!

 

​@kvbe by creating event action manually and to bypass the check try with a dummy value like ‘1’ for the PLSQL logic. After the event action is created edit and add the full PLSQL logic saved from the development environment.  

​@nithbtns111


Thanks! I was not aware that AFTER you save, there is indeed no check anymore :-)
You got to love the IFS tricks!
 

 

 

​@kvbe no problem, yes 😁

Reply


Terms & ConditionsCookie settings