We figured this one out. We originally went through the class manager in the user tool to do this. Cleared out the pending changes and made the change through the mid-tier and it took. That's what we get for trying to use the user tool that BMC is desperately trying to get rid of. We actually had a similar issue with rebuilding service targets. It wouldn't do a full rebuild from the user tool, but went through fine from the mid-tier.
-----Original Message----- From: Brian Pancia [mailto:panc...@finityit.com] Sent: Thursday, February 28, 2013 1:20 AM To: arslist@ARSLIST.ORG Subject: RE: Adding Attributes to CMDB Class Tim, Thanks for the input. The only thing I did not do yet is run cmdbdriver. All the error logs check out. I was looking for a quick check xyz is set right. Brian -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Hulmes, Timothy CTR MDA/ICTO Sent: Thursday, February 28, 2013 12:02 AM To: arslist@ARSLIST.ORG Subject: Re: Adding Attributes to CMDB Class It should not take that long. You might have to do a CMDB health check to see where the problem lies. Below is information from an old KB article that has the steps. It is recommended that your CMDB meta data be correct prior to upgrading the CMDB or making class changes when a superclass is in Change Pending. A quick test of the health of the CMDB is to open the Class Manager, scroll through the list of CI classes to make sure they all have a status of "Active", toggle the 'Class Type' to "Relationship", and scroll through the list of relationship classes to verify they all have a status of "Active". However, this check will not capture all kinds of incomplete or incorrect meta data. Below are steps to verify the CMDB meta data is correct. 1. Check the arerror.log for errors starting the CMDB Engine. Search for the string "cmdbEngine" to find relevant errors. Validation of the metadata occurs on startup. Below is an example error message. Mon Dec 11 16:10:18 2006 390600 : Error encountered while initializing(Initialization routine) the shared library (ARERR 9755) Mon Dec 11 16:10:18 2006 bmc.cmdb.cmdbEngine Mon Dec 11 16:10:18 2006 390600 : The specified super class with given classId is not found. : Class ID: OB005056C00008PlV3RQU3oZAAHO8C, Super Class ID: OB005056C00008F1V3RQd#IYAAD90C (ARERR 120132) 2. Query on the Class form to verify all classes are Active - Launch and login to Remedy User as an administrator user. - Choose File --> Open Object List, and open the Class form ( OBJSTR:Class ) in a Search window - Choose View --> Advanced Search Bar - In the Advanced Search Bar at the bottom of the Window, specify the query: 'OSStatus' != "Active" OR 'Pending ID' != "0" OR 'System Status*' != "Active" If this query returns any rows, then these should be investigated as classes which have not built or deleted properly. Please click the link below to see a demonstration of the process of querying on the class and attribute forms: /KMSAttachments/KM-000010004041/km10004041_viewlet_swf.html 3. Query on the Class form to determine the number of classes - Assuming the above test finds no records, perform an Advanced Search on the Class form where: 'Namespace*' = "BMC.CORE" should return 92 rows. Querying where: 'Namespace*' = "BMC.CORE.CONFIG" should return 10 rows. Note: Using a QBE search on Namespace = BMC.CORE will return the sum of the above - 102 rows. Additional classes can be added via the Class Manager, so this is not an absolute confirmation of the correct number of classes, but the result of the query is expected to be as listed above. 4. Query on the Attribute Definition form to verify all attributes are Active - Launch and login to Remedy User as an administrator user. - Choose File --> Open Object List, and open the Attribute Definition form ( OBJSTR:AttributeDefinition ) in a Search window - Choose View --> Advanced Search Bar - In the Advanced Search Bar at the bottom of the Window, specify the query: 'OSStatus' != "Active" OR 'Pending ID' != "0" If this query returns any rows, then these should be investigated as attributes which have not built or deleted properly. Export the value of the 'ForeignKeyID (Class ID)' field to determine the class and check whether it must be rebuilt to update the attribute definition. 5, Run cmdbdriver from the server, and issue the glc command to get the list of classes. - Navigate to the CMDB/bin directory on the server - Run the cmdbdriver program. (On UNIX, you must first set the library path to include the directory, see KM-000000024454) - At the command prompt, issue the log command, and respond to the prompts to login. - At the command prompt, issue the ssp command if necessary to set the specific port (if ARServer is not running on portmapper) - At the command prompt, issue the init command to initialize the connection - At the command prompt, issue the glc command to get a list of classes. Hit Return at all of the prompts to accept the defaults The desired output is a list of classes. If cmdbdriver gives an AR 91 RPC call failed message - as in the example below - this indicates the CMDB Engine is not loaded or running. In the particular case, the reason it was not loaded was that validation of the CMDB meta data failed, so use the steps above to find the meta data that is incorrect. Command: init INITIALIZATION CMDBInitialization results ReturnCode: OK Status List : 0 items Command: log Control record: Authentication string () : User name () : Demo Password () : Locale[.charSet] () : TimeZone () : Server () : ltangha-ple-13 Command: ssp SET SERVER PORT The TCP port number of the server (0): 7011 The RPC port number of the server (0): CMDBSetServerPort results ReturnCode: OK Status List : 0 items Command: glc GET LIST CLASS Namespace (): Class Relationship Name Namespace (): Class name (): Super Class Name Namespace (): Class name (): Getting querying Characteristics for this class Number of Characteristics (0): Retrieve hidden classes? (F): CMDBGetListClass results ReturnCode: ERROR Status List : 1 items Status Struct : Message type : ERROR Message number : 91 Message: RPC call failed Appended: RPC: Procedure unavailable Tim -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Brian Pancia Sent: Wednesday, February 27, 2013 9:33 PM To: arslist@ARSLIST.ORG Subject: Adding Attributes to CMDB Class ** I'm a little rusty on this one. We have a ITSM 7.6.04 environment we added a new attribute to the BMC:BusinessService class. The Class Manager shows the class as pending change. This has been sitting there for about an hour. I thought it usually goes through quicker than that. Any help would be appreciated. _ARSlist: "Where the Answers Are" and have been for 20 years_ ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
