Hi Claire & Robert, Don't forget, that if your changes to the Data Model didn't fully synchronise, there may be another way of forcing them through without having to recreate them or "hack" any of the meta data records in the OBJSTR prefixed forms...
This method should work as long as the changes you made are legal. As Robert suggested, if you've broken the laws of the CMDB and used invalid characters, bad attribute name or field Id's, then you're still stuck and that requires a more drastic cleanup....but it's not impossible. In CMDB 1.1, there should be a utility called cmdbdriver (or possibly called osdriver. Osdriver was the name used in CMDB 1.0 and wasn't changed until a specific patch release of the 1.1 version, from memory). If you've ever used driver for the AR System (the command line API interface), then you should see that cmdbdriver is relatively similar to use. Cmdbdriver is the command line API interface to the CMDB. Once you've found the cmdbdriver executable, you'll need to follow these steps carefully: Backup your entire DB before doing anything...just in case. I'd recommend only doing the following when nobody else is on the environment, as it may chew up your resources and hog the AR Server admin thread for several hours. >From a command prompt, run the cmdbdriver executable. A screen full of commands should appear. Type "init" to intialise the API session. Type "log" to log into your AR Server. You'll need specify the Admiin Login details you are using and the server name. Leave all other options blank by pressing return. If you have allocated port numbers for your server type "ssp" (in some older versions of CMDB this was buggy and you might need to set the port as a windows environmental variable before running cmdbdriver). Type "sync". You will be prompted for a pending ID. Now switch back to your User tool and open up form OBJSTR:Pending (I'm documenting this from memory, so if this is not the exact name, forgive me, but you should see which form I mean). Search for all entries in the form. Hopefully there will only be 1, but it's no big deal if there are more. Each entry represents an attempted (and potentially failed) synchronisation of the CMDB Meta Data. There should be a field on the form called 'Pending ID'. Copy the GUID value in this field (you may need to export the records to a csv file to be able to copy this value easily). Switch back to the cmdbdriver window and paste the first GUID value exactly as it is. Don't use double quotes, but do copy and paste any and all special characters in the Pending ID GUID. As long as no other synchronisation is currently running and the arcmdbd is quietly waiting for it's next command, you can hit the return key. This will immediately start the synchronisation process for the record in the OBJSTR:Pending form which represents a failed synchronisation session. Wait till the cmdbdriver window comes back to you to confirm that the operation was successful. (This is effectively the same thing that happens when you press the "Save" button in the CMDB Class Manager after you've made some changes.) Repeat the steps above for each record in the OBJSTR:Pending form until they are all gone. Once finished, type "term" to end the API session. Then type "e" to quit cmdbdriver. NB: During this rescue operation, it is important that you do NOT attempt to make any further changes to the data model. The version of CMDB you are using is a little notorious for being somewhat delicate when you come to make changes to it's data model. CMDB 2.0.x is a bit more robust, and is worth considering in the future....there's some nice new features in there which help make the CMDB more powerful as well as performing faster than before. I hope all of this helps. If you need any further advice or run into problems, please let me know and I'll see if I can help. Cheers Chris. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Robert Molenda Sent: Tuesday, February 13, 2007 8:51 PM To: [email protected] Subject: Re: CMDB 1.1 Change Pending Ah' that wonderful "explode after error and now you are stuck" condition. I know this because "been there and done that" has applied. At this point you must manually cleanup the Meta Data, and add the field(s) back again. Unfortunately the UI/Workflow does not check for "bad things" but when you try to update, then it goes BOOM. (You had the '-' character in the field..) Before you go in and get "deletion happy" in the OBJSTR: forms, remember to always CYI and export to arx ALL ENTIRES IN ALL TABLES of OBJSTR:.. One of our contractors went 'delete happy' and then nothing all worked, and it was restore DB time into a spare DB and recover the entries :( Q(s)>> Is this the first MetaUpdate that has run on the system, or have other custom fields been added. A good test is to go in and simply view some fields, and the UI thinks you updated and will update it again. This MUST GO OK before going any further!! Ensure (by scanning) that you don't duplicate ID/Field Name/name restrictions, and you should be fine. Also, we could not add more than 6 or 7 fields at one attempt or would get the same error. HTH Thanks-n-advance; HDT Platform Incident / Problem Manager & Architect Robert Molenda IT OS PA Tel: +1 408 503 2701 Fax: +1 408 503 2912 Mobile: +1 408 472 8097 [EMAIL PROTECTED] Quality begins with your actions. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Sanford, Claire Sent: Tuesday, February 13, 2007 11:03 AM To: [email protected] Subject: CMDB 1.1 Change Pending I added several fields via the class manager. When I clicked "Save" I received an error: ARERR [298] Too many filters processed during this operation OBJSTR:AttributeDefinition The preceding message occurred during the execution of active link OBJSTR:ClassDef_SaveChanges -- action 2. (ARNOTE 1101) This was in my arerror.log Mon Feb 12 17:32:40 2007 390620 : Too many filters processed during this operation (ARERR 298) Mon Feb 12 17:32:40 2007 OBJSTR:AttributeDefinition So I go to the admin tool and increase the filter value and then hit save again and everything looked ok. All of my fields are still showing "Change Pending" and when I look at the task manager, the arcmdbd server process is running, and the dispatcher (arsvcdsp) server process is running on the server. The only thing in the view log is: 2/12/2007 5:40:48 PM Remedy Application Service Sync Class: BMC:BMC_AssetBase 2/12/2007 5:40:49 PM Remedy Application Service ERROR: 120078 The supplied character is not allowed in the name. W-Parts: '-' Do I have to recreate all of the fields? ARS 6.3 Patch 18 HD 6.0 CMDB 1.1 Oracle 10 w/9 libraries Oracle lives on a remote server Windows 2003 4 gig on app server and 8 gig on DB server Claire Sanford Information Systems Division Memorial Hermann Healthcare System Phone: 713 448 6035 [EMAIL PROTECTED] ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
