Unable to populate cache in the server.log
search cancel

Unable to populate cache in the server.log

book

Article ID: 200852

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal CA Identity Suite

Issue/Introduction

In the server.log file from Identity Manager, there is the following error message:

----------------------------

09:03:51,964 DEBUG [ims.jdbc.JDBCManagedObjectProvider] (ServerService Thread Pool -- 121) SELECT "IM_ENVIRONMENT_JDBC"."UNIQUE_NAME", "VERSION", "SMOID", "DIRECTORYDN", "PUBLICALIAS", "ALIAS", "DESCRIPTION", "FRIENDLYNAME" FROM "IM_ENVIRONMENT_JDBC" WHERE "UNIQUE_NAME"=? ORDER BY "UNIQUE_NAME"  DESC (4)
09:03:51,964 DEBUG [ims.jdbc.JDBCManagedObjectProvider] (ServerService Thread Pool -- 121) Is scroll insensitive result set type: true
 Is forward only result set type: false
09:03:51,964 DEBUG [ims.jdbc.JDBCManagedObjectProvider] (ServerService Thread Pool -- 121) No results found from the query: SELECT  FROM  WHERE "UNIQUE_NAME"='14'
09:03:51,964 ERROR [ims.jdbc.JDBCManagedObjectProvider] (ServerService Thread Pool -- 121) Unable to populate cache: No object of type IM ENVIRONMENT JDBC found for identifier '14'

----------------------------

 

Unable to populate cache: No object of type IM ENVIRONMENT JDBC found for identifier '#' may also occur right after Step 4 during startup:

12:36:53,303 INFO  [ims.Main] (ServerService Thread Pool -- 122) ---- CA IAM FW Startup Sequence Initiated. ----
12:36:53,303 INFO  [ims.Main] (ServerService Thread Pool -- 122) * Startup Step 1 : Attempting to start ServiceLocator. 
12:36:54,068 INFO  [ims.Main] (ServerService Thread Pool -- 122) * Startup Step 2 : Attempting to start PolicyServerService
12:36:54,428 INFO  [ims.Main] (ServerService Thread Pool -- 122) * Startup Step 3 : Attempting to start ServerCommandService
12:36:54,568 INFO  [ims.Main] (ServerService Thread Pool -- 122) * Startup Step 4 : Attempting to start EnvironmentService
12:37:02,459 ERROR [ims.jdbc.JDBCManagedObjectProvider] (ServerService Thread Pool -- 122) Unable to populate cache: No object of type IM ENVIRONMENT JDBC found for identifier '14'
    at com.netegrity.llsdk6.imsimpl.jdbcmanagedobject.JDBCManagedObjectProvider.getManagedObject(JDBCManagedObjectProvider.java:403) [imsapi6.jar:]
    at com.netegrity.llsdk6.imsimpl.jdbcmanagedobject.JDBCManagedObjectProvider.getManagedObject(JDBCManagedObjectProvider.java:265) [imsapi6.jar:]

Environment

Identity Manager 14.x

Cause

There is some reference for an old environment ID (OID) in the Identity Manager database.

Resolution

In your Identity Manager database, check if you have the environment ID mentioned in the server.log.

In our case, the error message refers to env_oid = 14

--------

No object of type IM ENVIRONMENT JDBC found for identifier '14'

--------

 

Search in all tables below and check if there is some reference to env_oid or envoid in the tables listed below:


bulk_task
connection
Explore_and_correlate 
FWPASSWORDPOLICY
IM_Admin_policy
IM_certification_policy
IM_member_policy
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_element
PX_condition
PX_data_element
PX_policy
PX_rule
PX_when
AUXdata12
auxdataproviders12
DX_TMP_DATA
SNAPSHOT_TYPE
IM_TAB_DEFINITION
IM_IDENTITY_POLICY_SET
IM_IDENTITY_POLICY
IM_APPROVAL_POLICY
IM_WEBSERVICE_CONFIG
IM_WEBSERVICE_CUSTOM
FWSERVICE
FWSERVICE_PREREQUISITES
FWSERVICE_REQUEST
RPTINSTANCE
WF_ACTIVITY_INSTANCE
WF_PROCESS_INSTANCE
WF_WORK_ITEM
WF_WORK_ITEM_ASSIGNEES
imsAuditTaskSession12
imsAuditEvent12


You can search each table with a simple select statement, for example:

select * from bulk_task where env_oid=14;
select * from connection where env_oid=14;
select * from Explore_and_correlate where env_oid=14;

In the below example 5 entries are found for env_oid=14 in the im_owner_policy table:

 

The DBA performed a backup of the table and delete the row(s) where env_oid=14.   

Once all references to env_oid are cleared from the database, restart Identity Manager. 
The messages should be cleared from the logs. 


Additional Information

Clustered vApp seeing old OID