This Client Server article is republished in its entirety from 2008 for reference purposes. By Shawn Denton, Bentley Plant Support 31 March 2008 Modified: 15 July 2008 Product: AutoPLANT 2004 Edition (does not apply to AutoPLANT XM or V8i) Overview AutoPLANT 3D is very data-centric, and a drawing file can sometimes get out of sync with its database. The cause can be database failure/crashes, poor document management, and/or file system failures (requiring files to be recovered from whatever form of backup is used). When the file and the database get out of sync, many difficult-to-diagnose issues can arise. However, there are commands that can be used to repair damaged data in many instances. This does assume: You have an uncorrupted document file that can be opened in AutoCAD You can load Piping (or another AutoPLANT 3D application) You have a stable, running database for the project The workstation can perform a successful test connection to the database In order to demonstrate the problem and the steps to correct it: I created a MSDE, AutoPLANT 3D project called CS_Article. I created a Piping document called CS_Article_1.dwg. I added a number of Piping components to the document. I opened the database and deleted all records in the Piping table. I deleted all records in the RelationshipInstance table as well. I opened the document in AutoCAD. I loaded Piping. Now, when I use the command Edit Component, I see a screen similar to this. Empty Edit Component Dialog As you see, there is no component data. This can cause many issues going forward. What to do? The first thing to do is recreate the components in the project database, to take all the components from the file and create then in the Piping table. To do this, use the command: AT_DBPIPE_RECOVERDATA When the Piping table has been populated, a dialog like the following one appears Database Information The next step is to repair all the relationships. These include the relationships between documents and components, components and each other and the project objects, along with many others. The next command will cause AutoPLANT to attempt to recreate these relationships from the drawing. It may take several passes, depending on the state of the file and the database. It provides feedback in the command line. You may have to take certain steps and run it again. AT_DBPIPE_REPAIRRELATIONSHIPS Specifically, since AutoPLANT cannot determine the correct project objects to use for the components in this example, it will use the defaults. For example, since we removed all relationships and components, there is no way for AutoPLANT to have the correct project objects. As a result, it will inform you that there is no Service called S100 (the default).This is the error message displayed: Repair Relationship Error This is text from the command line: Processing component: AT_F5WHI1AU_10 Error: ATDB0719: Relationship Manager error code reported -213131 modPreference.GetPrefernceValue : Service instance doesn't exist.S100 You will have to create a service called S100 and then run the command again. The next time you run it, you will see: Processing component: AT_F5WHI1AU_Z Error: ATDB0719: Relationship Manager error code reported -213131 modPreference.GetPrefernceValue : Unit instance doesn't exist.U100 So you now have to add the unit U100 and whatever else is missing until the system returns this message: Command: AT_DBPIPE_REPAIRRELATIONSHIPS Repairing relationships in the current drawing...39/39 Components scanned, 37 repaired 2 were correct, 100 percent complete So now if you run an Edit Component command, you get: Edit Component w/ data You can now see the component data from the recreated components. Many times this step will get you back up and running. However, you may see issues with components not being associated with a valid spec record. In this case, the next step is to run the following command: Piping --> Database Tools --> Update From Spec Choose All from the component selection dialog and the system displays this dialog: Spec Update Dialog In this example, you want as much information as possible, so choose the first item. AutoPLANT will begin to check the components against the spec. If it finds matching records for all components, you will be finished. The system returns this message: Scanning component: 1 / 39 C:\Bentley Plant Projects\MSDE\CS_Article\Drawings\CS_Article_1.dwg AT_F5WHI1AU_1: Component contains an unknown spec reference and cannot be updated. Scanning component: 39 / 39 So one of the components could not be matched correctly to a spec. The next step is to enter this command AT_SPEC_SCAN An attempt is made to process each component to fix its spec reference by matching its SYS_IDs in the spec. Since there is a component with a bad reference, this dialog is displayed: Spec Fix Scan Notice that the comp_id shown is the one in the message returned by running Update from Spec. The Go To button takes you to the component. The Update lets you update the spec record. After clicking Update, you see the same spec selection dialog as you do when placing a component that has multiple components matching the where clause. Select the correct one to update the component record correctly. Finally, to clean up the document, run the AutoCAD PURGE and AUDIT commands, as well as the AutoPLANT command AT_DBPIPE_CLEAN to clean the database. This should return your AutoPLANT drawing to a stable format that you can save. At this point you might say, "Great! But aren't my components associated with the wrong project objects?" You'd be right. Unfortunately, since AutoPLANT didn't know what Areas, Services, and so on to use, it defaulted to U100, S100, and A100. To correct this, you have to move them to their right associations using the Update Component command in the Piping menu. Using the advanced selection dialog, it isn't very difficult. See Also Client Server Archive Plant TechNotes And FAQs Comments or Corrections? Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!
↧