Safeload

This option is similar to load except that field checks are performed during the loading process. Although you can run a safeload option on a failed system, you will receive a warning that not all database checks will work. This option can be used to load data on a live system.

Loading a text file containing a record that has a unique key identical to the unique key of any of the records that exist in the RealTime database (RTDB) generates an error. As a result of the error, the system will not modify the existing database record or load the text file record.

Important: Exercise extreme caution when using the dbll safeload option on a live system. "Runtime" fields, such as the analog table's curspt field or the status table's lastKrunchTime field, should never be included in the ASCII data file. The file should include only configuration fields, such as the analog table's units field or the status table's run.doit field. Use of this utility should be limited to those with a thorough understanding of the system.

Syntax

dbll safeload <data_file> <error_file>

Notes: The dbll safeload option should be used when creating new records. The dbll load option does not check for duplicate keys when loading a database.

After you create a new record, the system generates an event. When you update an existing record, the system generates an event for each field whose value has changed. However, for remconnjoin records, the system only generates one event when you modify one or more of the record's fields.