Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Enterprise SCADA

TABLE OF CONTENTS

Usage examples

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedApr 24, 2025
  • 2 minute read

The following are examples of the usage types you can expect to see when performing a database conversion.

Example of the SchemaConverter:

Usage: SchemaConverter [-l <Header Location>] [-d <Database Location>] [-f] [-n] [-v] [-o]

Where the following are optional parameters:

  • -l: The destination path for generated .h files.

    Default: %DNADataRoot%\RealTime\sdk\database\include\auto.

  • -d: The destination path for generated database structure files.

    Default: %DNADataRoot%\RealTime\database\INTEL_NT.

  • -f: Do not generate .h files.

    Default: False.

  • -n: Do not generate database structure files.

    Default: False.

  • -v: Set the debug level to verbose to get all SchemaConverter debug messages.

  • -o: Full file path of the previous root.txt file.

    Important: If you have previously run the SchemaConverter command with the -o option, any subsequent call to the SchemaConverter utility must be done with the -o option.

    If a) you have previously upgraded your system and b) the SchemaConverter utility detects records named private# in the previous root.txt file, the utility will exit with an error asking you to use the -o option so that you can safely extend the RealTime database (RTDB) schema with custom tables while preserving previously assigned table numbers. In other words, if you invoke the Schemaconverter utility without the -o option (other possible options include -l, -d, -f, -n, and -v), the utility gracefully stops converting the RTDB schema and informs you that it has stopped since the previous root.txt file contains a private# tag.

    The -o "order" parameter is required during a product upgrade scenario.

    When you use the SchemaConverter command with the -o option, the system replaces the table locations in the root.txt file of any tables that existed in the old schema, but which were removed in the new schema, with internal placeholder tables called private<#>. This serves two purposes:

    1. Enables the system to preserve the table numbers for any tables that still exist in the new version of the RealTime database (RTDB).

    2. Fills any gaps in the sequence of RTDB table numbers with internal placeholder tables.

      These placeholder tables should not be used for any other purpose, as they may be replaced after you run the SchemaConverter command again.

    1. -h: Display the usage information.

    Example: SchemaConverter -l "C:\headers" -n -v