After Upgrade to 220.127.116.11.0 Receiving "Code cannot be bllank" Error in OFSAA PLC Screen
(Doc ID 2738910.1)
Last updated on DECEMBER 22, 2020
Applies to:Oracle Financial Services Analytical Applications Infrastructure - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Analytical Applications Infrastructure (OFSAAI)
Post Load Change (PLC)
Data Management Tools (DMT)
After OFSAA to 22.214.171.124.0 upgrade receiving error in Post Load Change Screen, currently UNABLE to modify an existing Post load change and receive error "Code cannot be blank".
 Code cannot be blank
The following additional error is found in the nohup.out of Tomcat:
com.fasterxml.jackson.core.JsonParseException: Illegal unquoted character ((CTRL-CHAR, code 9)): has to be escaped using backslash to be included in string value
The same Post load change can be modified in 8.0.7 OFSAA environment.
It seems there may be some new limitations around length of code as well as length of name, but neither of these are the issue with this specific Post load change.
The length is nowhere near the new 5000 char limit.
SQL> select length(v_sqlblock)
where v_obj_id = '32c194ae-37ff-40d4-b345-91057ea9d41e'
No issue with new PLC that is 5-10 chars.
The issue can be reproduced at will with the following steps:
1. Common Object Maintenance -> Data Management Tools -> Post Load Changes
2. Attempt to edit or copy any existing PLC and Save
3. Find error message appears
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document