When creating multiple TRIRIGA users in a bulk operation, some users do not have their security groups set when logging into TRIRIGA. This requires revising and activating people records again. The following Oracle constraint error shows against the SMART_SECTION_ROWS table:
YYYY-MM-DD HH:MM:DDD,mmm ERROR [STDERR](WFA:221931 - 20500221 CREATE:320792592 IE=320792292) java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (TRIDATA.PK_SMART_SECTION_ROWS) violated all associations appear correct comparing a user record that works and one that doesn't. The following SQL statement helps to identify the bad logins however some accounts work without values in the SMART_SECTION_ROWS table: select username from t_myprofile where spec_id not in (select pass_through_object_id from smart_section_rows where spec_id in( select spec_id from t_group) ) and spec_id not in (select spec_id from ibs_spec where object_state is null)
The issue doesn’t occur with every new record created, but ranges between 20-80% without having the security group assigned.
The platform was processing various batch SQL in an unordered manner.