
NicolasLebris (Customer) to rsaSFDCadmin (RSA): asked a question.
Account Active Directory Collection failed : Ora-12899
Hello,
We have a failed collection of Active Directory groups which stops at the Pre-
processing step with the oracle error 12899
01/19/2022 10:59:30.297 ERROR (Exec Task Consumer#0 - Accounts Sequence)
[com.aveksa.server.db.FileToTable]
java.sql.BatchUpdateException: ORA-12899: value too large for column
"AVUSER"."STX_G_M_1063_2166858"."MEMBER_TYPE" (actual: 98, maximum: 10)
Could you help me on this subject?
Regards
Nicolas
We have a failed collection of Active Directory groups which stops at the Pre-
processing step with the oracle error 12899
01/19/2022 10:59:30.297 ERROR (Exec Task Consumer#0 - Accounts Sequence)
[com.aveksa.server.db.FileToTable]
java.sql.BatchUpdateException: ORA-12899: value too large for column
"AVUSER"."STX_G_M_1063_2166858"."MEMBER_TYPE" (actual: 98, maximum: 10)
Could you help me on this subject?
Regards
Nicolas
records.
If the special char is the same as the delimiter which is being used by the
system, it can cause a confusion in the parsing process
To confirm this is indeed the root cause, follow these steps:
* Disable **Remove Internal Data Files After Upload** config

* Run the collector
* It will generate some files in AveksaDataDir directory (search under /home/oracle or under the install folder)
* Copy the generated files
* Restore **Remove Internal Data Files After Upload** config
* Open the files and identify the delimiter. This might be the one - ª
* Use **Text to Columns** functionality in excel with your delimiter

* You should be able to identify if some record/s span across more columns than all other records.

If that the case, please reach out to support and they will guide you on how
to change the delimiter.