Symantec Identity Manager - Exception during attribute map init
Article ID: 121396
Updated On:
Products
Issue/Introduction
We rebuilt node 2 on a clustered vApp and now both nodes will not start and pointing to the old OID (env_oid).
2018-11-20 14:02:12,583 ERROR [ims.LLSDK.baseobject] (Thread-12 (HornetQ-client-global-threads-1387617167)) Exception during attribute map init
2018-11-20 14:02:12,583 ERROR [ims.LLSDK.baseobject] (Thread-12 (HornetQ-client-global-threads-1387617167)) No object of type IM ENVIRONMENT JDBC found for identifier '62'
at com.netegrity.llsdk6.imsimpl.jdbcmanagedobject.JDBCManagedObjectProvider.getManagedObject(JDBCManagedObjectProvider.java:401)
at com.netegrity.llsdk6.imsimpl.jdbcmanagedobject.JDBCManagedObjectProvider.getManagedObject(JDBCManagedObjectProvider.java:264)
at com.netegrity.llsdk6.imsimpl.utility.DirAndEnvCache._getImsEnvironment(DirAndEnvCache.java:366)
at com.netegrity.llsdk6.imsimpl.utility.DirAndEnvCache.fetchEnvironment(DirAndEnvCache.java:120)
at com.netegrity.llsdk6.imsimpl.utility.DirAndEnvCache._getImsDirectory(DirAndEnvCache.java:314)
at com.netegrity.llsdk6.imsimpl.utility.DirAndEnvCache.fetchDirectory(DirAndEnvCache.java:90)
In this case the old OID is 62. The new one that should be used is 84.
Environment
Release:
Component: IDMGR
Resolution
The solution: Task persistent data just sits there. The JMS queue is what gives reference to give work. There must have been something in the JMS queue giving the old reference to OID 62. Make running deleteJMSqueue Part of normal maintenance. Consider running this alias again once a month or quarter to keep things cleaned. Alias
run alias:
deleteJMSqueue
Restart nodes once complete.
If that does not resolve issue it is possible reference in the database. look for column env_oid
In Database trying to find the old env_oid=62
Selected Bulk_task
Select * from bulk_task;
No results
Connection table
Select * from connection;
No results
Explore_and_correlate table
Select * from Explore_and_correlate;
2 results but correct OID (results of 84)
FWPASSWORDPOLICY table
Select * from FWPASSWORDPOLICY where env_oid=62;
No results
IM_Admin_policy table
Select * from IM_Admin_policy where env_oid=62;
Many results but sorted by OID and see the new 84. Looking for 62.
No results for OID 62.
IM_certification_policy
Select * from IM_certification_policy where env_oid=62;
no results
IM_Identity_policy_set table
select * from IM_Identity_policy_set where env_oid=62;
no results
IM_member_policy
Select * from IM_member_policy where env_oid=62;
Same steps but for the all the other tables below. Looking for old 62 OID in env_oid. Add where env_oid=62 to every select statement:
IM_owner_policy
IM_role_task
IM_role
IM_screen_definition
IM_screen_field
IM_screen
IM_Tab
IM_Admin_policy
IM_task_handler
IM_task
PX_action_elements
PX_condition
PX_data_element
PX_policy
PX_rule
PX_when
AUXdata12 (envoid with NO SPACE for this table…)
auxdataproviders12 (envoid with NO SPACE for this table…)
If you find the env_oid as the old one, modify this to be your new OID and restart once completed. Once completed run deleteJMSqueue again and restart.
Feedback
