The
mfdbcatc utility is used to partially automate the process of moving a disk-based catalog to a database-hosted one. It can scan an
existing catalog on disk, and generate the necessary files to deploy the
CATALOG.DAT and its cataloged data files to an MFDBFH-aware database. See
Scanning an Existing Catalog and
Deploy a Catalog to a Database for details on the two-step process.
Syntax:
mfdbcatc <action> <options>
<action> can be one of:
- -s
- Specify
-s if you are scanning the existing catalog; see
Scanning an Existing Catalog for more information.
- -u
- Specify
-u if you are producing the deployable files; see
Deploy a Catalog to a Database.
The following <options> can be specified, depending on the <action>:
- -c
- Specify the path and the catalog file you are scanning, or deploying to the database.
- -fs
- Specify the catalog folder (that is, the folder in which
catalog.dat is stored, and where all catalog-relative locations are based).
- -fd
- Specify the destination folder for
catalog.dat in the database. If you omit this option, the file is stored at the root location of the intended datastore. Only use this
option with the
-u action.
- -h
- Specify the host name of database. Only use this option with the
-u action.
- -d
- Specify the name of the datastore. Only use this option with the
-u action.
- -n
- Specify the name of the database instance. Only use this option with the
-u action.
- -v
- Verbose output is displayed if you specify this option. (Optional.)
- -i[cfg-type]
- cfg-type can be one of:
- r - relative configuration file
- s - static configuration file
- e -environment configuration file
- f - Fileshare configuration file
- q - SQL configuration file
Only use this option with the
-u action.