Account collection failing with ORA-12899: value too large for column "AVUSER"."STX_ACC_122_266"."CAS17" in RSA Via Lifecycle and Governance
Originally Published: 2016-04-20
Article Number
Applies To
RSA Product/Service Type: All
Issue
Cause
CAS1 or CAS2 with 2048 bytes are the only custom attributes currently in our system to support greater lengths. Any other attribute do not support to collect large values.
Resolution
To swap the attributes Just hover to Admin > Attributes > Affected object say for example Account -> Edit
You will see that Attribute Name are editable. For example in below screenshot Notes attribute with Database ID CAS6 will not collect data with more that 256 characters.
Just swap the names of CAS1 and Notes attribute .
Then edit your collector and map the correct attribute.
Related Articles
Migration from 7.0.1 to 7.0.2 fails with error PLS-00323: subprogram or cursor 'PROCESS_ACTIVE_USER_ACC_MAPS' is declared … 18Number of Views RSA Identity Governance and Lifecycle - 702 Migration fails with 'ORA-02260: table can have only one primary key' 44Number of Views RSA Via Lifecycle and Governance Aveksa Data Collector (ADC) becomes stuck for hours on "Inserting account mappings into s… 155Number of Views RSA Identity Governance and Lifecycle - Can you map an account to a specific user through Web Services 38Number of Views Accounts created from an RSA Via Lifecycle and Governance account template are not removed from UI when request item is re… 241Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide How to Download OTP Token Seed Files from myRSA RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide
Don't see what you're looking for?