In addition to the site and site schema database, you also need a catalog database in order to use the software to create a model. Using the Database Wizard, you can restore the sample catalog that is delivered with the software, or you can use a catalog database that already exists on the server.
Restore catalog from backup
Creates a new catalog database by restoring a backup of the .DAT file for SQL, or .DMP for Oracle, specified in the Template file to be used to create the Catalog database and schema field.
Use existing catalog already on server
Specifies that you want to create a custom catalog using the Bulkload utility delivered with the software. For more information about using the Bulkload utility, see the Smart 3D Reference Data Guide available from Help > Printable Guides. Choosing this option disables all the text boxes and option buttons on the Catalog Database and Schema page.
Database type
Specifies the type of database.
Catalog database server
Sets the server on which the catalog database will reside. Only registered SQL Servers appear in the list. After you select a server for the catalog database, the Catalog schema server field defaults to match the name of the catalog database server. This option appears only if you select MSSQL in the Database type list.
Oracle service (Catalog database)
Sets the name of the Oracle net service for the catalog database connection. After you select the Oracle service, the Oracle service box for the catalog schema defaults to match that of the catalog database. This option appears only if you select Oracle in the Database type list.
Catalog database name
Specifies a name for the catalog database. After you type a name the catalog database, the Catalog schema name field defaults to match the catalog database name.
Paths for catalog database files: Physical database
Identifies the location of the physical database. Unless you specify otherwise, the software uses the default MS SQL Server location. For Oracle databases, this information is read-only.
Paths for catalog database files: Log file
Identifies the location of the log file. Unless you specify otherwise, the software uses the default MS SQL Server location. This option appears only if you select SQL Server in the Database type list.
Paths for catalog database files: Data tablespace file name
Identifies the location of the data tablespace for the catalog database. By default, the text in this field is Oracle Managed File, which means that tablespace file name will be 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. This option appears only if you select Oracle in the Database type list.
Paths for catalog database files: Index table space path
Specifies the location of the catalog database index table space. By default, the text in this field is Oracle Managed File, which means that tablespace file name will be 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. This option appears only if you select Oracle in the Database type list.
Symbol and custom program file locations
Specifies the path or browses to the server location of the SharedContent folder and custom program files. The path in the Symbol and custom program file folder box must be a UNC path. To obtain a UNC path, click Browse under My Network Places, not under My Computer. The SharedContent folder is created automatically on the server during the Smart 3D Reference Data installation. If you are running Oracle on Linux, the SharedContent folder must be on a Windows-based computer.
Template file to be used to create catalog database and schema
Specifies the template file you want the software to use when creating your catalog and schema databases. For SQL Server databases, the template file delivered with the software is located on the reference data computer at [Product Folder]\3DRefData\DatabaseTemplates. The SQL Server template file is catalogdb.dat. For Oracle databases, the template file is catalogdb.dmp.
If you are running Oracle on Linux, then the database templates must be on the Linux computer where the Oracle service is running. The account used for the Oracle service must have access to the folder. Remember that Linux is a case sensitive environment so the database dump file (catalogdb.dmp) and the folder path must be typeed in the correct case. The Browse feature is not available for navigating to Linux folder locations.
The catalogdb.dat (for MSSQL) and catalogdb.dmp (for Oracle) template files contain
sample Smart 3D reference data and, while they contain many useful examples, they are not certified
for production use by Hexagon Asset Lifecycle Intelligence.
Catalog schema server
Identifies the server on which the catalog schema database will reside. By default, the software displays the server location you specified in the Catalog database server box. This option appears only if you select SQL Server in the Database type list.
Oracle service (Catalog schema)
Sets the name of the Oracle net service for the catalog schema database connection. By default, the software displays the service that you specified in the Oracle service box for the catalog database. This option appears only if you select Oracle in the Database type list.
Catalog schema name
Identifies the name of the catalog schema database. By default, the software appends the name you typed for the catalog database with the word SCHEMA. For example, if you type Catalog_CDB as the database name, the schema name defaults to Catalog_CDB_SCHEMA.
Paths for catalog schema files: Physical database
Identifies the location of the physical database. Unless you specify otherwise, the software uses the default MS SQL Server location. For Oracle databases, this information is read-only.
Paths for catalog schema files: Log files
Identifies the location of the log file. Unless you specify otherwise, the software uses the default MS SQL Server location. This option appears only if you select SQL Server in the Database type list.
Paths for catalog schema files: Data tablespace file name
Identifies the location of the data tablespace for the catalog schema. By default, the text in this field is Oracle Managed File, which means that tablespace file name will be 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. This option appears only if you select Oracle in the Database type list.
Paths for catalog schema files: Index table space path
Specifies the location of the catalog schema index table space. By default, the text in this field is Oracle Managed File, which means that tablespace file name will be 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. This option appears only if you select Oracle in the Database type list.