Exporting Content Manager data

This process will allow the administrator to select what data can be exported from the currently selected database into data files and scripts so that it’s ready for the import into a new database at a later date.

  1. Right-click on the dataset to be exported, i.e. the source dataset, and select Export from the Utilities menu.

    The Export Tables to Bulk Loader Format dialog box displays.

  2. Choose the target database type for Export suitable for the following DBMS. Options are:
    1. Microsoft SQL Server
    2. Oracle - the following additional information is required:
      1. Server Name - the name used to identify the specific Oracle database in Oracle’s Transparent Network Substrate (TNS).
      2. User Name - enter the name of the user (schema), created within the Oracle database.
      3. Password - enter the appropriate password for the User Name provided.
    3. PostgreSQL - the following additional information is required:
      1. Schema Name - Enter the name of the schema, created within the PostgreSQL database.
  3. Enter the output path for Export Data and Scripts To Folder. This is where the data files and scripts will be created.
      4. NOTE:
    • The output path must be an UNC path to allow the Workgroup Server(s) and Database Server to access the files contained with.
    • Full permissions to the given path must be given to the following logins:
      • the network login running the Workgroup Server service
      • the network login running the Database Instance
  4. Choose whether to create a Unicode target database by selecting Export as Unicode UTF16.
  5. Use Direct Path Load for Oracle SQLLDR - This option is for Oracle target databases only. The migrate option instructs Oracle's SQL *Loader (SQLLDR.EXE) utility to load the data files created straight into the Oracle data files instead of issuing standard SQL Insert Statements. This action can be less taxing on the target database. There are exceptions for when not to use this option. Refer to Oracle’s own online documentation for SQLLDR https://docs.oracle.com/database/122/SUTIL/oracle-sql-loader.htm#SUTIL3311
    If your version of Oracle does not have SQL *Loader installed, or it is called by a different name, the migration process will not work. Check it is installed and named correctly before completing this process.
  6. Use the Select migrate style option to determine how much data will be migrated to the target database. Choose from the following options:
    1. Entire Dataset - Everything from the old database
    2. Basic Setup Data (Record Types, Security, etc) - The new database will be mostly empty except for some reference tables used for record types, lookup sets and other “reference” information from the old database
    3. Basic Setup Data with Internal Locations - The new database is the same as above plus data related to Internal Locations from the old database
  7. Click OK.
      8. NOTE:
    • The tool creates one data file for each table exported, which is in a format suitable for import into an empty Content Manager database of the chosen format.
    • For Oracle, the tool also creates a control file for each table, which the bulk loader tool uses for these database types uses.
    • Additionally, the tool creates a script file which contains all the data loading statements. This script is used to automate the loading process into the target database. It is called MigrateTo[target database type].sql (where [target database type] is determined by Step 2 above). Database administrators should examine the contents of this file before executing it .
    • If the source database is GIS-enabled then additional update scripts may be included. 

Importing the exported data

  1. Creating a new dataset based on the target database - start here: Creating or upgrading Content Manager datasets
    Make the following adjustment - On the Initialization dialog, choose New Dataset. Uncheck the Initialize with standard setup data option. See Initialization dialog box.
  2. On the target RDBMS server, use the RDBMS’s own tools to load the MigrateTo[target database type].sql script produced by the export process.
    For example, for MS SQL Server, execute the SQL statements in the file MigrateToSQLServer.sql using an SQL Server query execution tool.
      3. NOTE:
    • Regardless of which migration choice used, when creating the target database, Content Manager creates it without any referential integrity constraints, and with all indexes created as duplicate. This is to compensate for input data that may violate the normal constraints. The intent here is to create the data correctly in the first place and then repair the constraint violations later. 
  3. Once the import is completed, run Schema Manager to check the database is intact. You access this by right-clicking the newly created dataset and selecting Manage from the Schema menu. Address any issues found. See Manage a dataset schema.

Contact your Content Manager Software help desk for further details and assistance.

See Support.