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

  • Most likely the issue is caused due to a special char in one of the collected
    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

    ![BorisLekumovich_0-1642593572657.png](
    https://community.rsa.com/t5/image/serverpage/image-
    id/412385iC4BB45EC3CC89A9D/image-size/large?v=v2&px=999)



    * 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

    ![BorisLekumovich_1-1642594136548.png](
    https://community.rsa.com/t5/image/serverpage/image-
    id/412386i91F828468205E26C/image-size/medium?v=v2&px=400)

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

    ![BorisLekumovich_2-1642594324687.png](
    https://community.rsa.com/t5/image/serverpage/image-
    id/412387i18E6FE653E2F7659/image-size/medium?v=v2&px=400)

    If that the case, please reach out to support and they will guide you on how
    to change the delimiter.
    Expand Post
    Selected as Best
  • Most likely the issue is caused due to a special char in one of the collected
    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

    ![BorisLekumovich_0-1642593572657.png](
    https://community.rsa.com/t5/image/serverpage/image-
    id/412385iC4BB45EC3CC89A9D/image-size/large?v=v2&px=999)



    * 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

    ![BorisLekumovich_1-1642594136548.png](
    https://community.rsa.com/t5/image/serverpage/image-
    id/412386i91F828468205E26C/image-size/medium?v=v2&px=400)

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

    ![BorisLekumovich_2-1642594324687.png](
    https://community.rsa.com/t5/image/serverpage/image-
    id/412387i18E6FE653E2F7659/image-size/medium?v=v2&px=400)

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