Provides options for creating a new catalog database and schema. You access this dialog by clicking Database > New > Catalog.
In a Global Workshare configuration, Database > New > Catalog is available at the host location, but not at satellite locations. You cannot create
or modify reference data at satellite locations. In addition, Smart 3D does not support Linux for Global Workshare. You must run Oracle on a Windows-based
server if you intend to use Global Workshare.
Catalog information
Catalog database server
Specifies the name of the server on which to create the catalog database. This option is only available when the database type is MS SQL Server.
Oracle service
Specifies the name of the Oracle net service to use to create the catalog database. This option is only available when the database type is Oracle.
Catalog database name
Specifies the name of the new catalog database. You can type a new name or select an existing catalog database from the list. If you select an existing database, the software replaces the existing catalog database with a new catalog database.
Schema information
Catalog schema server
Displays the name of the server where the software creates the catalog schema database. This is the same server you specified for Catalog database server. This option is only available when the database type is MS SQL Server.
Oracle service
Displays the name of the Oracle net service for the catalog schema database connection. This option is only available when the database type is Oracle.
Catalog schema name
Displays the name that the software assigns to the catalog schema database. This name is the same string you specified for the catalog database name with _SCHEMA appended.
Template options
Create an empty catalog
Indicates creation of a new, empty catalog. An empty catalog contains all schema, such as tables, procedures, and views, but does not contain any data, such as part data or specifications. When you select this option, the Template file to be used to create catalog schema field is available.
Template file to be used to create catalog schema
Specifies the path and name of the .dat file (such as apprepos.dat or sm_emptyshipcatalogdb.dat, delivered with the software) to use to create the catalog schema. You can type the full path and file name or click the ellipsis button to select the file from the Browse dialog.
Create a new catalog from a template
Indicates that a new catalog database and schema is to be created from an existing template. You can use this option to begin work from a seed catalog containing data. When you select this option, the Template file to be used to create catalog database and schema field is available.
Template file to be used to create catalog database and schema
Specifies the path and name of the file to use to create the catalog database and schema. You can type the full path and file name or click the ellipsis button to select the file from the Browse dialog. You will typically select a .dat file certified for use by your company.
Smart 3D reference data includes sample template files containing example data. This data
is not certified for production use by Hexagon Asset Lifecycle Intelligence.
Paths for catalog database files
Physical database
Specifies the location for the catalog database file. Click the ellipsis button to select the file from the Browse dialog. This option is only available when the database type is MS SQL Server.
Log file
Specifies the location for the catalog database log file. Click the ellipsis button to select the file from the Browse dialog. This option is only available when the database type is MS SQL Server.
Database tablespace file name
Specifies the location of the catalog database table space. This option is only available when the database type is Oracle. By default, the text in this field is Oracle Managed File. This means that the tablespace file name is placed into a predefined Oracle location. You can edit this field to use an unmanaged file for the tablespace. If ASM is enabled in Oracle, the text in this field is the disk group name, such as +Data1, instead of a tablespace file name.
Index tablespace file name
Specifies the location of the catalog index table space. This option is only available when the database type is Oracle. By default, the text in this field is Oracle Managed File. This means that the tablespace file name is placed into a predefined Oracle location. You can edit this field to use an unmanaged file for the tablespace. If ASM is enabled in Oracle, the text in this field is the disk group name, such as +Data1, instead of a tablespace file name.
Symbol and custom program file location
Specifies where the catalog symbol files are located. Click the ellipsis button to select the file from the Browse dialog.
You must have full control on the catalog root to change the location in the Project
Management task on the Properties dialog. The catalog root is the highest allowable level in the hierarchy for a discipline.
-
Smart 3D does not delete a partially created catalog after displaying an error message. You must manually delete the database from the database server before trying again.
-
If you are running Oracle on Linux, then the database templates must be on the Linux computer on which the Oracle service is running.
-
Linux is a case-sensitive environment. Make sure that you use the correct case when typing the database template names (catalogdb.dmp and apprepos.dmp) and the folder when creating the database.