AE DB Load

Administrators use the AE DB Load utility (ucybdbld) to load data to the AE database for various purposes. You can load initial data, contents that have been transported with the transport case, or contents for calculating the expected runtimes of executable objects. You can also install ILM partitions and load Rapid Automation solutions.

This page includes the following:

Starting the Utility

Follow one of the options below:

Windows

  • *G.EXE (ucybdbldg.exe)

    Regular utility start, G stands for the graphical user interface

  • *.EXE

    Program to which start parameters can be assigned for batch calls, see Start Parameters - Utilities

  • *.BAT

    Batch file for the utility

UNIX

  • *.sh

    Regular utility start

  • Without file ending

    Program to which start parameters can be assigned for batch call.

Loading Data to the Database

AE DB Load automatically identifies the loading type and allows you to do the following actions:

  • Load data for new and upgrade installations

    • The utility creates the database schema and loads INITIAL and DEFAULT data. Select the <DB directory>\DB\GENERAL\<vers>\UC_UPD.TXT file of the version you require.

    When you load initial data to the AE database, a dialog displays in which you can install and configure. For more information, see Loading the AE Database. You can also install ILM using the start parameters for utilities with a command line interface (CLI), see Start Parameters - Utilities.

    When you install or update the database, a dialog displays in which you can select the authentication method. Enter the pass phrase in the text fields of the Server and Server and Agent options. It is used to generate the company key. For more information, see Agent Authentication.

  • Load data that has previously been unloaded by using AE DB Unload

    • Contents of transport cases or specific tables are stored in the UC_DATA.TXT file. You can load them to the same or to a different AE database. The target system must use the same service pack version as the source system or a later one for this purpose. For more information, see Transporting Data.

  • Calculate an expected runtime (ERT)

    • For this purpose, the value of the ERT_CALCULATION key in the UC_CLIENT_SETTINGS variable must be configured to BATCH. Select the DB directory>\DB\GENERAL\<vers>\UC_UPD_ESTIMATE_ERT. TXT file which automatically calculates the runtime, and load it to your database. The last line of this file calls the ERT-calculation function. By default, it includes the whole AE system but you can also define a specific client. For more information, see ERT Parameters.

    Example

    ESTIMATE_ERT 1000

Possible Messages and Errors

  • If an SQL error occurs while you update the database or load initial data, a dialog displays which offers the following options:

    • Retry
      Re-processes the SQL commands starting from the position where the error occurred. Processing continues if the problem does not occur again.

    • Cancel
      Ends the loading process and the utility.

    • Ignore
      Skips the command that caused the error.

    • Important! Ignore and Cancel can result in an inconsistent database. A corresponding message displays that you must confirm if you want to proceed.

  • Message U0038128 displays and informs you that the utility version and the database version do not match. This happens when you try to load transport-case data while revisioning is active in the AE system.

    Important: Do not cancel the AE DB Load utility. It will start the loading process as soon as it has finished processing the data that is required for revisioning (see AE DB Revision Report). This procedure ensures that no data that is relevant for the revisioning process is lost even if you load data several times. Depending on the size of objects that should be loaded, this process may take some time.

  • Message U00038042 Action required! Check index NK_AH_IDNR_bearb if it matches the definition in uc_ddl.sql

    If the AE DB Load log includes this message, you have to update the NK_AH_IDNR_bearb index manually by dropping the index and copying the matching create statement from the uc_ddl.sql because an automatic update could take a long time. However, you do not have to do it during DB Load, you can do it at a later point in time.

See also: