Initialization dialog box

The Initialization dialog box appears when you click Next in the Storage dialog box in the Create New Dataset dialog.

  • New Dataset - to create a new Content Manager dataset for the current version
    • Initialize with standard setup data - inserts extra setup data such as document and folder Record Types, document store and administration users.

      • NOTE: Clear this option if you are planning to migrate manually exported data to this new dataset.

  • Migrate - enables you to import data from another existing Content Manager dataset as part of the process of creating the new dataset

    NOTE: For Oracle target databases only. The migrate option instructs Oracle's SQL *Loader (SQLLDR.EXE) utility to load the data files create d 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.
    Also, 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.

    • Migrate data from Content Manager dataset - select the Content Manager dataset to import data from.
    • Select migrate style - this dropdown determines how much data will be migrated into the new database from the old database. Choose from the following options:
      • Entire Dataset - Everything from the old database.
      • 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.
      • Basic Setup Data with Internal Locations - The new database is the same as above plus data related to Internal Locations from the old database.
    • Support storing Unicode characters in string columns - select this option for the new dataset to support Unicode.

      • NOTE: The database to be created must support Unicode for this option to be used. See CM23.4_Spec.pdf for more information about Unicode support.

    • Support GIS columns and spatial indexes - select this option for the new dataset to support geographical information.

      • NOTE: The database to be created must support GIS for this option to be used. See CM23.4_Spec.pdf for more information about GIS support.

    • Support SQL text indexing - select this option to enable SQL text indexing for the new dataset. See SQL Text Index for details.
      • Ignore accents on characters (treats garçon and garcon as identical words) - select this option to ignore the accents on characters so all words are indexed as the same words.

Click Next to continue to the Run Parameters dialog box. See Run Parameters dialog box.