Pre-Copy Checks in the Library Manager

Certain checks are performed prior to copying data. The Library Manager invokes any pre-copy checks defined by applications.

To ensure technology database compatibility between source and destination libraries, the following checks are performed:

• Ensure that the names of files to be copied do not have a space in them. Files with names that have spaces does not get copied.
• If the source library contains a local technology database file (tech.db file), then check if the destination library associates with a technology database, either through attachment or by containing a tech.db file in the library. If the destination library associates with a technology database, then the copy command is aborted.

If the above check succeeds, then the following additional checks are performed for compatibility of design data:

1. Compatibility Check: Check for compatibility between the technology databases of the source and destination library and do the following:
   • If the source and destination technology databases are equal, then proceed to the existence check.
   • If the source technology database is a subset of the technology database of the destination library, then proceed to the existence check.
   • If there are any conflicts with a severity level of error between the technology databases, then abort the copy command. The following table lists the checking criteria:
     

     Technology objects	Checking criteria for compatibility
     oaLayers (oaPhysicalLayers / oaDerivedLayers)	Same name then same number, same number then same name
     oaPurposes	Same name then same number, same number then same name
     oaStdViaDefs	Same viaDef name, two compatible layers and a cutLayer in the viaParameter
     oaCustomViaDefs	Same viaDef name and two compatible layers
     oaScalarSiteDefs	Same name, same width, and same height
     oaArraySiteDefs	No compatibility checking; check that there is no siteDef of the same name but a different type
     dbuPerUU (technology attribute) For view types of dbcMaskLayout, dbcSchematic, dbcSchematicSymbol, and dbcNetlist	Same value
     userUnits (technology attribute) For view types of dbcMaskLayout, dbcSchematic, dbcSchematicSymbol, and dbcNetlist	Same unit name

2. Existence Check: If the source technology database and the destination technology database are compatible, then check for the existence of technology objects in the destination technology database. If there are any missing technology objects for a cellview, that cellview is still copied and warning messages are issued.

Information about errors is displayed in the CIW. Modify your source data accordingly and then try to copy it again.

Related Topics

Copy Function in the Library Manager

Return to top