Posts Tagged ‘fix’

How to debug CMDB 7.5 Change Pending Issues

June 21st, 2010

How to debug CMDB 7.5 Change Pending Issues

OVERVIEW:  CLASS Manager Activity. If a particular activity stays in Change Pending state for a long time you can investigate the root cause by following the steps mentioned in the document.

To resolve this problem you need to validate  CMDB metadata problems. We need to check some of the forms which may have pending entries for classes, attributes for which class manager do not show pending entries.

LOGIN with Administrator previlege:

This is a brief descriptions of the points to check:

– WUT: Login as Demo and check the CMDB metadata. Check each record is active, unique and it’s correct.

STEPS:

The forms to check and fix are:

Step1: Class (OBJSTR:Class)  -> Check there is NOT pending entries (No entries where ‘System Status*’ !=  “Active” )

Fix: If there are not active entries, you need to backup those entries on arx format and delete them.

1.a Check Class (OBJSTR:Class)  again where ‘Pending ID’ != “0” OR ‘OSStatus’ != “Active”

Fix: If there are entries with Pending ID != 0, you have to investigate this problem carefully.

Step 2: Attribute Definitions (OBJSTR:AttributeDefinition) -> Check there is NOT pending entries (No entries where ‘Record Status’ != “Active”)

Fix: If there are not active entries, you need to backup those entries on arx format and delete them.

**

Step 3: OBJSTR:Index (OBJSTR:Index) -> Check there is NOT pending entries (No entries where ‘Record Status’ != “Active”)

Fix: If there are NOT active entries, you need to backup those entries on arx format and delete them.

Step 4: OBJSTR:IndexAttrib (OBJSTR:IndexAttrib) -> Check there is NOT pending entries (No entries where ‘Record Status’ != “Active”)

Fix: If there are not active entries, you need to backup those entries on arx format and delete them.

***

Step 5: OBJSTR:Pending -> Check there are not errors here.

Fix: If there are errors, please read them and fix the problem. Otherwise, you need to backup those entries on arx format and delete them.

Step 6: Application Pending -> Check there are not entries waiting processing here.

Fix: Wait until all the entries are deleted. If they are not deleted, to fix the problem, you need to backup those entries on arx format and delete them manually.

Credits-Vishal V. Dhainje

Overview console issue and fix

June 15th, 2010

Overview Console Debug – ARERR 8939 :

Overview:

Typical scenario and fix is mentioned in the below document. Accessing Overview Console gives error ARERR 8939.

Solution:

1.Check Plugin Logs. If GLEWF incompletes with ARDBCRollbackTransaction (“Entering ARDBCGetListEntryWithFields”).  This indicates that while quering SHR:ARDBC_OverviewConsoleTemplate form, ARS is not able to find records in it.

2. When you search on this form , if no records exists then; Export the data from a working server  and Import onto non-working server’s SHR:ARDBC_OverviewConsoleTemplate form that should resolve the problem.

3. Expected behavior after fix – If you look at the plugin logs,you would notice that, quering ( GLEWF ) to the SHR:ARDBC_OverviewConsoleTemplate form results are returned, you can also see GLEWF OK with ARDBCCommitTransaction.
 
Credits-Vishal V. Dhainje
%d bloggers like this: