|Applies To||RSA Product Set: RSA Identity Governance & Lifecycle |
RSA Version/Condition: 6.x, 7.0.x, 7.1.0
|Issue||New user provisioning fails and the following error is seen in the Account Changes section of the change request:|
ORA-22835: Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: 4210, maximum: 4000)
22835. 00000 - "Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: %s, maximum: %s)"
*Cause: An attempt was made to convert CLOB to CHAR or BLOB to RAW, where
the LOB size was bigger than the buffer limit for CHAR and RAW
The aveksaServer.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log) reports errors similar to the following:
The following exception is subsequently thrown in the aveksaServer.log:
followed by the Caused by message:
|Cause||The ORA-22835 exception occurs when a SQL TO_CHAR statement attempts to convert a CLOB object to a CHAR object and the CLOB object exceeds 4000 bytes. The 4000 byte limit is a hard limit and is not configurable. ORA-22835 is a new exception; in older (Oracle 10.x and earlier) versions of Oracle SQL, if the BLOB object was too large, the object would be truncated without any error message.|
When this error occurs during an AFX provisioning event, it is caused by an attempt to convert the SQL statement used to define the attributes to be added to the user. This can occur if the Account Template used to define the user contains a very large number of user attributes.
Note that the number of attributes you can add before encountering this error depends on the size of the SQL used to define them so there is no hard limit.
This is a known issue reported in engineering ticket ACM-56836.
|Resolution||This issue is resolved in RSA Identity Governance & Lifecycle 7.1.1.|
|Workaround||Reduce the number of user attributes and/or the length of the attribute names defined in the Account Template (Requests > Configuration > Account Templates tab) associated with the Account until the error no longer occurs.|