AE DB Client Copy

Use the AE DB Client Copy utility (ucybdbcc) to copy clients to the same or a different database or to delete existing clients. You can include all messages, statistics, reports, and version management objects of the source client. If the source client is copied for the first time, objects are also copied. For security reasons, you must log in to system client 0. To do so, ensure that the password is the same in the source and target AE system. The login window opens automatically when the program starts.

Important!

  • Client Copy supports UTF-8 encoded data only if both Clients use the same encoding. If the Clients use different encoding, the utility aborts with an error message to prevent data corruption.

  • You can also use UTF-8 when specifying the INI file name and path (-I).

  • If you use a DB2 AE database and run this utility on Windows, you must set the client encoding to Unicode (DB2CODEPAGE = 1208). You can do so either via the registry variable or the Windows environment variable.

This page includes the following:

Copying Clients

Select one or several options from the Settings section in the user interface of the utility:

  • Copy objects

    The utility copies all objects that are not marked with a deletion flag. If the host definitions are not available in the destination client, they are logged in the log file. Objects are only copied when the client is copied for the first time.

  • Copy messages

    All messages that are not marked with a deletion flag are copied. In subsequent copying processes, the utility copies all messages that are available in the source client when the process starts.

  • Reset password

    All user passwords are reset to "pass".

  • Copy statistics/report

    All statistics and reports that are not marked with a deletion flag are copied. In subsequent copying processes, the utility only copies the statistics and reports of objects that were already considered in the first copying process. AE.DB Client Copy copies all the relevant data records that are available in the source client when the process starts.

  • Copy VC Objects

    Version management objects are copied. They can only be copied when the client is copied for the first time. For more information, see Version Management Page.

The destination client automatically stops while the AE.DB Client Copy utility is copying data even if only copies the statistics and report data.

To copy a client for the first time:

  1. Start the AE.DB ClientCopy utility.
  2. Select the client that should be copied in the source database.
  3. Select an unused client number (green hand symbol) in the destination database.
  4. Decide whether messages, statistics and so on should also be copied.
  5. Click Copy client to start the process.

To copy messages and statistics subsequently:

  1. Start the AE.DB ClientCopy utility.
  2. Select the client that you have already copied and the corresponding destination client.
  3. Select the messages, statistics, or reports that should be copied later. The utility skips data that is already available in the destination client.
  4. Click Copy client to start the process.

Deleting Clients

Important!

  • Unload all reorganized data before you start deleting a client. Doing so reduces the time that the database is blocked.
  • When you delete an existing client, the contents of all its AE database tables are deleted.
  • You cannot restore a deleted client.

To Delete a Client

  1. Start the AE.DB ClientCopy utility.
  2. Switch to the Delete client tab.
  3. (Optional) In the Settings section, select whether you want to delete a client in the source or destination database.
  4. Select the client that should be deleted in the database list.
  5. Click Delete client to start the deletion process

Specific Settings

  • In the INI file of the utility, you can specify database connections to a different database server. For example, you can copy a client from an MS-SQL Server to an Oracle or DB2 database. Ensure that both AE databases are of exactly the same version including service packs. If the versions are not identical, and the database structure has changed between service packs, the following message is logged:

    U00036002 The two databases do not have identical database versions.

    See also Utility DB Client Copy

    • Only one log file is used for this process. It contains one of the following messages so that entries can be distinguished:

    U0036000 database change to source

    U0036000 database change to destination

    Note: The value of the database trace must be set to at least 1 as otherwise, this message is not inserted.

  • In the INI file of the utility, you can define the WorkTablePath= parameter. In this case, the utility creates work files in XML format for messages, statistics, and reports. In doing so, you can copy them later. The name of these work files is composed of the client numbers of the source and destination client. They are separated by an underscore. For example: If you copy from client 0003 to 0333, the resulting file name is 0003_0333.xml. If the folder you define does not exist, the utility does not create work files. See also Utility DB Client Copy
  • In the UC_CLIENT_SETTINGS variable, you can use the PWD_DEFAULT key to set a client-wide default password for new User objects. These User objects are created without an individual password. When you use the client copy utility, all User objects that are included in the copied client are set to the default password you defined in that key. For more information, see PASSWORD Parameters.

    • If no password is defined there, the default system password pass is set at the copying process. Users have to change their password in both cases when they log on to the system the next time.

The Protocol tab supplies detailed information during the copying and deletion process, as well as the log file that is automatically created.

See also: