DATABASE LINKAGE ERRORS REMOVAL IN ISOMETRIC

EXTRACTION

Self Study Presentation by Ganesh Radhakrishnan

Introduction

Typical errors encountered in Batch or Isometric extraction are as follows

Multiple Disconnected segments
Data Overflow error
Internal error generating Material Pointer
Database Occurrence Linkage errors
Most of the above errors involve extensive rework in the model in which the error
originated. This self-study focuses on solving the Database Occurrence Linkage
errors using a novel way rather than using time-consuming conventional
methods.

Database Linkage Errors

Database error Linkages occur because of the following

Type I Graphic elements exist in Piping Model but no corresponding entry

exist in RIS Tables
Type II Database entry exists in RIS Tables but no corresponding Graphic
Element exists for that entry
Type III Piping Component loses associativity with Piping Segment

This documentation covers procedure for solving Database linkage errors of the
first type ie when Graphic elements exist in Piping Model but no
corresponding entry exist in RIS Tables. Such type of errors results in
display of error reading database data when Component having the
database linkage problem is selected in the model.

Batch or Interactive Isometric Extraction always generates an error file in ASCII

format if errors of the type as listed above are encountered. Error file generated
for Database linkage error of Type I is as follows.

The clue to solving the above error lies in interpreting the numbers listed below
the error and relate them to the affected component in the Piping model.
Before this it is essential to understand the concept of Partition because it forms
a part of the numbers to be interpreted.

Partitioning

Partitioning addresses the problem of supporting very large tables by

decomposing them into smaller pieces called partitions and still contain the same
logical attributes as of the parent Table.

Once Partitions are defined SQL statements can access the partitions rather than
the entire tables or indexes thus making data access much faster.

Significance of Partitions in PDS

In PDS partitions are automatically created when a Piping model is created

The Partition number information for the piping model can be obtained from
PDTABLE_113 of Project Database Schema.

The Design Database tables corresponding to this Piping model have the
Partition number built as part of their Table name itself.
For eg. if partition number is 551 for a piping model then corresponding segment
data table for the model will be PDTABLE_12_551 where 12 signifies segment
data table and 551 signifies the partition number.

Table 3 as mentioned in the error file indicates that the type of object, which is in
suspect, is a Piping Component. Similarly Table 1 is equivalent to 12 which is
Piping Segment Data, Table5 is equivalent to50 which in PDS terms indicates
Piping data etc.

Partition number 551 gives information about the Piping model in which the
Component lies.

Only number left to be interpreted is the Database Occurrence Number.

Procedure for Interpreting Database Occurrence Number and Solving

Database Occurrence Linkage errors

Convert Database Occurrence Number to binary digits .The total binary digits
will have to be 32. So if the Calculator shows digits less than 32 then the
difference should be substituted with zeroes and added to the digits from the
extreme left. In this case the number 288882708 is equivalent to
0001 0001 0011 1000 0000 0000 0001 0100.
The Calculator shows 1 0001 0011 1000 0000 0000 0001 0100.
Therefore 3 zeroes have been added to the left of the digits.
 The first 13 digits of this number when converted back to decimal equivalent
represents Partition Number and the remaining digits correspond to the Row
number of the Component. i.e.

0001 0001 0011 1 000 0000 0000 0001 0100

partition no Row no

In this case 1000100111 will give 551 as the decimal equivalent

And 10100 will give 20 which corresponds to the Row number of the Piping
Component in the model.

Partition number gives model number details from pdtable_113 of project

schema. Enter into the Piping model based on information obtained from the
above table.
Using Piping Diagnostics option select Find Segment or Component by
Linkage and key in the Row number as identified from the binary digits.
The Piping Component under suspect is shown highlighted. Then using
Repair Graphics linkage to Database tool from Piping Diagnostics delete the
dumb graphics of the Piping component and replace it by a suitable Piping
component as decided by the spec.

Scope of Topic

Scope of the Topic is to introduce the user to the concept of Partitioning and use
it effectively in solving Database Occurrence Linkage errors. The Scope is thus
limited to interpreting the numbers generated in the specific error file generated
for Database Occurrence linkage problems. It is assumed that the user is well
familiar with Batch and Interactive Isometric extraction and typical techniques of
remodeling in Piping Designer.

Conclusion

The above technique was used very effectively in solving Database Occurrence
Linkage errors encountered in Technip Project. Freezing on the Row numbers of
affected Components could be done without even entering the Piping model.
Once row numbers are available for the affected components repairing them
does not take much time.