Forgot to mention in my last mail that if you can identify the offending attribute which breaks convention (The one with '-' in the name), you could try the following...
Go to the OBJSTR:AttributeDefinition form. Locate the offending Attribute by searching for it based upon the field name. Hopefully, you'll only get one entry returned which is in the "Change Pending" status. Delete this one entry only. Then try the procedure I described in detail in my last mail to flush the rest of your changes through. This should hopefully save you having to type all of those attributes in again. As Robert suggested, don't go too delete happy in the OBSTR forms as this could do more harm than good. There are limited specific cases where it's relatively "safe" to do this. In the case you are currently experiencing, as long as the field was not created in any of the CMDB forms (you should check this first by looking in the AR System Data Dictionary for all occurrences of the field you tried to create, either by name or ID) and the attribute is still showing "Change Pending" and there's only one instance of it in the metadata, then you *should* be OK. Never delete an attribute which is currently "Active". Regarding the Max Filters error, I have seen this before due to 2 things... Firstly, make sure you've set a high enough number for Max Filters in your AR Config file. I think the documentation recommends 100,000. (You can always reduce this again after making your Data Model changes). Secondly, there was a known defect identified in the Filters which push information from the OBJSTR forms to the SHR:SchemaNames. From memory, a bad push fields action caused too many records to be modified, thus causing Filters to run for each of those SHR:SchemaNames entries to push to each other!...Hence you breach the max filters limit. There used to be a KB about this, though I can't find it now...I think it was a Filter with a name like "SHR:Objstr_Menu_Push" that modified all matching entries instead of the first matching entry. This *might* have been fixed in Patch 003 for CMDB 1.1, but I'm not sure. HTH 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"
