A Smart 3D project uses a set of seven interrelated databases: site, site schema, catalog, catalog
schema, model, reports, and reports schema. You must create these databases before using Smart 3D.
The graphic below depicts the order of creation and the relationships between these
databases.
|
1 - Site
2 - Site schema
3 - Catalog
4 - Catalog schema
5 - Model
6 - Reports
7 - Reports schema
|
Administrative privileges are required to create databases. Do not proceed unless
you are an administrator on the database server computer and in the database provider
software.
The site database and schema organize the interactions of the other databases. Because
the site database and site schema are containers for the other required databases,
they are the first databases you must create after installing the software. The site
database stores work-breakdown and user access for the models. Typically, there is
one site database set for each customer location, or for each set of interrelated
model designs. You use the Database Wizard to create the site and site schema databases.
General information for creating a new site (Oracle)
Dump files
The dump files used to create the site and catalog database are delivered on the server
computer to the [Product Folder]\3DRefData\DatabaseTemplates\Site folder. This location must be shared and write
permissions given to both the user login used to create the Smart 3D databases and the account on which the Oracle service (OracleService<SID>) is running (for example, OracleUser\SYSTEM). Before proceeding, verify that the
share (with the appropriate permissions) exists on the server computer.
If you are running Oracle on Linux, the database template location must be on the
Linux-based computer where the Oracle service is running. Linux is case sensitive
environment. The database template names (catalogdb.dmp and apprepos.dmp) and the
folder path must be typed correctly when creating the database. The Browse feature is not available for navigating to Linux folder locations.
Log files
The software delivers two log files on the server computer at the local user %temp% folder: one for the site database generation process and one for the catalog database
restore process.
Naming
You must name the databases with unique entries. To better differentiate between one
database and another, include the type of database in the name you type, such as Model1SiteDB. Do not use a name that starts with a digit as its first character in Oracle. For
example, if you typea name such as 1ModelSiteDB, Oracle will not create the database.
When you name the site database, the name of the schema database will automatically
populate with _SCHEMA to match the site database.
Tablespace
We recommend that you increase and/or redefine initial tablespace values based on
the expected scope of your project(s). For more information, see your Oracle documentation.
View errors
During the site database creation process for an Oracle model, the software attempts
to connect to the site database to create the user interface prior to generating the
views, resulting in a "table or view does not exist" error being reported in the various
log files. Because views are generated after the user interface is created, these
errors cannot be avoided. Additionally, these errors do not have any negative impact
on using the software and can be disregarded when reviewing the log files.
General information for creating a new site (SQL)
You must name the databases with unique entries.
Site database workshare location
This location is the location of the host site database and is required even if the
host is not going to be replicated for worksharing purposes. During generation of
the site database, the software creates a location object and associates it with the
site database.
Name Generator Service
The Name Generator Service that runs on the server computer you specify in the Name generator server for site box supplies unique names to items placed in the model database. In a replicated
configuration, there are multiple servers and multiple instances of the Name Generator
Service running at each location; consequently, there is no way to ensure unique and
sequential naming of placed objects. The value you type in the Name rule ID box functions as a substring (an internal ID number) that represents the location
at which an item is placed into the replicated model.
Catalog Database and Schema page
The option control at the top of the page allows you either to create a new catalog
database by restoring a backup or use an existing catalog database. If you choose
to create a new catalog database using the Restore option, the wizard will restore the .dat template file specified in the Template file to be used to create the Catalog database and schema box. The default is to Restore catalog from backup. If you select Use existing catalog, then no further options are available.
The .dat template file contains sample Smart 3D reference data and, while this template contains many useful examples, it is not
certified for production use by Hexagon PPM.
Symbols and custom program file folder
The SharedContent folder is created automatically on the server during the Smart 3D Reference Data installation. The path you specify in the Symbol and custom program file folder box must be a UNC path. To obtain a UNC path, click the ellipsis button and browse
under My Network Places, not under My Computer.
Optionally, you can create a starting catalog and catalog schema database using the
database template file delivered with the software within the site databases set creation
workflow. The catalog template file delivered with the software is a backup of an
already complete catalog database. This template contains the definition of a default
catalog of objects, including specific sizes of pipes, pipe specifications, steel
section sizes, and so forth. After the catalog database is created, you can then bulkload
your customized piping specifications into the catalog database, as needed.
After you create the databases for site, catalog, and their associated schemas, you
use the tools in Project Management to create the model and reports databases.
Standard workflows
The software supports two standard workflows for creating new databases when setting
up your project. The only difference between the two workflows is when you create
the catalog database set. In Workflow 1, the catalog databases are created as part
of the site database creation process using the Database Wizard. In Workflow 2, you first use the Database Wizard to create the new site databases, and then you use Project Management to create the
new catalog databases.
Which workflow do you want to use to create your databases?