Installation and Upgrade › Known Issues › Orphan Records in Table CMN_SEC_ASSGND_OBJ_PERM for MSSQL Users

Orphan Records in Table CMN_SEC_ASSGND_OBJ_PERM for MSSQL Users

A recent change prevents the creation of orphan records in the table CMN_SEC_ASSGND_OBJ_PERM. However, for MSSQL users, pre-existing orphan records can sometimes remain. You can search for orphan records and can remove them from the table after the upgrade to Release 13.3 is complete.

To verify that orphan records exist in the table, run the following query:

select COUNT(*)  from (select object_instance_id from cmn_sec_assgnd_obj_perm p
    where p.object_ID = 50680 and object_instance_id not in 
(select ID from BPM_RUN_PROCESSES)) q

The number value that the query returns indicates the number of orphan records.

To clean up orphan records, invoke the following upgrade script from <clarity_install_dir>/bin using dbpatch:

POSTUPGRADE_57954_MSSQL_DEL_PROC_INST_ASSGND_OBJ_PERM.xml

Use the following command:

dbpatch -install -file <CLARITY_INSTALL_DIR>\upgrade\13.3.0\component\postupgrade\POSTUPGRADE_57954_MSSQL_DEL_PROC_INST_ASSGND_OBJ_PERM.xml -apply

Note: The length of time the query runs is dependent on the number of orphan records to be deleted.