000035730 - IDC fails at IDC_NORMALIZE and IDC_DATA_COLLECTOR in  RSA Identity Governance and Lifecycle

Document created by RSA Customer Support Employee on Nov 24, 2017
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000035730
Applies ToRSA Product Set: RSA Identity Governance and Lifecycle
RSA Version/Condition: 7.0.2 P01, 7.0.1 P05
 
IssueIdentity Data Collections fail with:
 

ORA-01722: invalid number
ORA-06512: at "AVUSER.IDC_NORMALIZE", line 314
ORA-06512: at "AVUSER.IDC_DATA_COLLECTOR", line 105
ORA-06512: at "AVUSER.IDC_DATA_COLLECTOR", line 195
ORA-06512: at line 1

 
CauseA new table called 'T_RAW_USER_DELETED' defines custom attributes as datatype 'NUMBER' when they should be datatype 'VARCHAR2(256).' 
ResolutionThis is fixed in 7.0.2 P03.  
The fix contains the following modifications:
1. Modifies the datatype of specific columns in T_RAW_USER_DELETED from NUMBER to VARCHAR2(256).
2. Ensures new custom user attribute fields get added to both T_RAW_USER_DELETED and T_RAW_USER as VARCHAR2(256).
WorkaroundTo work around this issue, first, determine which fields in table T_RAW_USER_DELETED have the datatype mismatch and then update the datatypes for those fields as described in the steps below. Any time a new custom user attribute field is added to RSA Identity Governance and Lifecycle, repeat the steps below. Once 7.0.2 P03 is applied, this workaround will no longer be needed.
1. Run the following query to determine what fields in table T_RAW_USER_DELETED have the datatype mismatch:
 

select dl.TABLE_NAME, dl.column_name, dl.data_type, dl.data_length,
rw.TABLE_NAME, rw.column_name, rw.data_type, rw.data_length
from
(select * from user_tab_columns
where table_name = 'T_RAW_USER_DELETED') dl
join
(select * from user_tab_columns
where table_name = 'T_RAW_USER') rw
on (rw.column_name = dl.column_name and rw.data_type <> dl.data_type);

2. If no rows are turned, then you have a different issue. Please contact customer support. If one or more rows are returned, the results will look similar to this:
T_RAW_USER_DELETED     CUS_ATTR_USER_CAS_4     22     NUMBER     T_RAW_USER     CUS_ATTR_USER_CAS_4     VARCHAR2     256
T_RAW_USER_DELETED     CUS_ATTR_USER_CAU_1     22     NUMBER     T_RAW_USER     CUS_ATTR_USER_CAS_4     VARCHAR2     256
3. Every custom attribute column of type 'NUMBER' in T_RAW_USER_DELETED that is of type 'VARCHAR2' in T_RAW_USER needs to be changed to 'VARCHAR2' using the 'ALTER TABLE' command.
In the above example, the fix would be:
 

ALTER TABLE T_RAW_USER_DELETED MODIFY (CUS_ATTR_USER_CAS_4 VARCHAR2(256));
ALTER TABLE T_RAW_USER_DELETED MODIFY (CUS_ATTR_USER_CAU_1 VARCHAR2(256));

4. After applying the workaround, the query in #1 should return no results.
NOTE: If you add a new custom user attribute, run the query again and perform the 'ALTER TABLE'  command on that column.

Attachments

    Outcomes