Office365 Collector fails to process 'Is Disabled' and 'Is Locked' flags and Admin Error 'ORA-01722: invalid number' in RSA Identity Governance & Lifecycle
Originally Published: 2020-07-28
Last Modified: 2023-10-06
Article Number
000044923
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.x
 
Issue
When running an Office365 collection that collects the Is Disabled and Is Locked flags, the values of the flags are not processed in RSA Identity Governance & Lifecycle. The raw data shows the collected value but the user interface does not.

The following Admin Error is reported in the user interface:
 
ORA-01722: invalid number
 
User-added image

The same error is logged to the aveksaServer.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log) :
  
com.aveksa.server.db.PersistenceException: java.sql.SQLSyntaxErrorException: 
ORA-01722: invalid number
ORA-06512: at "AVUSER.ADC_NORMALIZE", line 148
ORA-06512: at "AVUSER.ADC_NORMALIZE", line 1451
ORA-06512: at "AVUSER.ADC_DATA_COLLECTOR", line 218
ORA-06512: at "AVUSER.ADC_DATA_COLLECTOR", line 481
ORA-06512: at line 1

Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log file for your specific deployment, if you are on a WildFly cluster or a non-WildFly platform. The aveksaServer.log may also be downloaded from the RSA Identity Governance & Lifecycle user interface (Admin > System > Server Nodes tab > under Logs.)
 
Cause
The values being passed for the Is Disabled and/or Is Locked attributes are T or F. Supported values are null/1/0.
 
Resolution
Only pass null/1/0 values in the Is Disabled and Is Locked fields when collecting from an Office365 data source. For example, collect 1 instead of T and 0 instead of F.
 

Related Articles

Trending Articles

Don't see what you're looking for?