Installing Database Objects

The following information explains how to install and configure database objects (tables, triggers, indexes, and so forth) for synchronization with the default, driver configuration.

SQL scripts are located in the tools\sql\database directory.

This section contains information to help you:

IMPORTANT:  We recommend installing or uninstalling preconfigured drivers and database scripts as a unit. To prevent unintentional mismatching, database scripts and preconfigured drivers now contain headers with a version number, the target database name, and the database version.

For uninstallation information, refer to Uninstalling the Driver and Database Objects.


Configuring Oracle Objects

  1. From an Oracle client, such as SQL Plus, logon as user SYSTEM. By default, the password for SYSTEM is MANAGER.

  2. Execute the first installation script for direct or indirect synchronization. For example:

    SQL> @c:\tools\sql\oracle\direct\INSTALL_DIRECT_1.sql

    SQL> @c:\tools\sql\oracle\indirect\INSTALL_INDIRECT_1.sql

  3. Log on as user dirxml using dirxml as the password.

  4. Execute the second installation script for direct or indirect synchronization. For example:

    SQL> @c:\tools\sql\oracle\direct\INSTALL_DIRECT_2.sql

    SQL> @c:\tools\sql\oracle\indirect\INSTALL_INDIRECT_2.sql

NOTE:  Before executing the provided publication tests as SYSTEM, you must log in and create a new session. Otherwise, you won't be able to see the sequence objects owned by dirxml.

If the scripts execute correctly, you should see notifications that the database objects have been created. If there are errors, ensure that you are logged in as the correct user. Before re-running the installation scripts, be sure to execute the uninstallation script (for example, UNINSTALL_DIRECT.sql or UNINSTALL_INDIRECT.sql).


Troubleshooting Tips

  • When generating events for publication, make sure you are logged in as someone other than the dirxml user. If you make changes as the dirxml user, your changes will not be published.
  • Be sure to commit changes. Until you commit your changes, they will not be published.


Configuring Microsoft SQL Server Objects

  1. Start Query Analyzer.

  2. Log on to your database server as user sa. By default, the sa user has no password.

  3. Open and execute the first script for direct or indirect synchronization. For example:

    tools\sql\mssql\direct\INSTALL_DIRECT_1.sql

    tools\sql\mssql\indirect\INSTALL_INDIRECT_1.sql

  4. Log on to your database server as user dirxml by using dirxml as the password.

  5. Open and execute the second installation script for direct or indirect synchronization. For example:

    tools\sql\mssql\direct\INSTALL_DIRECT_2.sql

    tools\sql\mssql\indirect\INSTALL_INDIRECT_2.sql


Troubleshooting Tips

  • When generating events for publication, make sure you are logged in as someone other than the dirxml user. If you make changes as the dirxml user, your changes will not be published.
  • Be sure to commit changes. Until you commit your changes, they will not be published. The keyword for commit for Microsoft SQL Server is go.
  • Make sure you are logged in as the correct user in the correct database when running the scripts.


Configuring IBM DB2 Objects

For DB2 Universal Database, you must manually create a database user account and database before running the provided scripts.Because the process of creating user accounts differs between operating systems, Step 1 below is OS-specific. These instructions are for a Windows NT operating environment. If you reinstall the database objects, you only need to repeat Step 6 through Step 8.

  1. Create a user account for user dirxml using dirxml as the password in User Manager for Domains.

    • Remember to uncheck the User Must Change Password at Next Login check box for this account.
    • You might want to also check the Password Never Expires check box.

    NOTE:  The remaining instructions are OS-independent.

  2. Start the Control Center.

  3. Right-click Databases, then click Create Database Using Wizard.

  4. Name the database dirxml, then click Finish.

  5. Copy JDBCUtil.jar to your DB2 client.

  6. Start the Command Center from the Control Center.

  7. Change the name of the administrator account and password for your server before executing the first installation script.

    For direct synchronization, edit tools\sql\db2\direct\INSTALL_DIRECT_1.sql.

    For indirect synchronization, edit tools\sql\db2\indirect\INSTALL_INDIRECT_1.sql.

  8. Click the Script tab, open the Script menu, then import and execute the first script edited in Step 7.

  9. Change the path to JDBCUtil.jar to reflect its location on your client in the second script.

    For direct synchronization, edit tools\sql\db2\direct\INSTALL_DIRECT_2.sql.

    For indirect synchronization, edit tools\sql\db2\indirect\INSTALL_INDIRECT_2.sql.

  10. Import and execute the second script edited in Step 9.


Troubleshooting Tips

  • When generating events for publication, make sure you are logged in as someone other than the dirxml user. If you make changes as the dirxml user, your changes will not be published.
  • Make sure you commit your changes. Until you commit changes, they won't be published.


Configuring Sybase Objects

This section explains how to install database objects on Sybase Adaptive Server Enterprise (ASE).

If you haven't installed JDBC support on your Sybase server, you should complete this task. Refer to your server's installation manual for further details. If installation is required, you should execute the sql_server*.sql script to install java.sql.DatabaseMetaData support.

  1. From a Sybase client, such as isql, logon as user sa and execute the first installation script for direct or indirect synchronization. By default, the sa account has no password. For example:

    isql -U sa -P -i tools\sql\sybase\direct\INSTALL_DIRECT_1.sql

    isql -U sa -P -i tools\sql\sybase\indirect\INSTALL_INDIRECT_1.sql

  2. Log on as user dirxml using dirxml as the password and execute the second installation script for direct or indirect synchronization. For example:

    isql -U dirxml -P dirxml -i tools\sql\sybase\direct\INSTALL_DIRECT_2.sql

    isql -U dirxml -P dirxml -i tools\sql\sybase\direct\INSTALL_INDIRECT_2.sql


Troubleshooting Tips

  • Make sure you commit your changes. Until you commit changes, they won't be published. The keyword for commit for Sybase is go.


Configuring MySQL Objects

  1. From a MySQL client, such as mysql, log on as user root or another user with administrative privileges. By default, the root user has no password.

  2. Execute the first script for indirect synchronization. For example:

    mysql> \. c:\tools\sql\mysql\indirect\INSTALL_INDIRECT_1.sql

  3. Open and execute the second installation script for indirect synchronization. For example:

    mysql> \. c:\tools\sql\mysql\indirect\INSTALL_INDIRECT_2.sql


Configuring Informix Objects

For Informix Dynamic Server, you must manually create a database user account before running the provided scripts.

Because the process of creating user accounts differs between operating systems, Step 1 below is OS-specific. These instructions are for a Windows NT operating environment. If you reinstall the database objects, you only need to repeat Step 2 through Step 6.


Installation Instructions

  1. Create a user account for user dirxml using dirxml as the password in User Manager for Domains.

    • Remember to uncheck the User Must Change Password at Next Login check box for this account.
    • You might want to also check the Password Never Expires check box.

    NOTE:  The remaining instructions are OS-independent.

  2. Start SQL Editor.

  3. Log on to your server as user informix. By default, the password for informix is informix.

  4. Open and execute the first script for direct or indirect synchronization. For example:

    tools\sql\informix\direct\INSTALL_DIRECT_1.sql

    tools\sql\informix\indirect\INSTALL_INDIRECT_1.sql

  5. Log on to your database server as user dirxml using password dirxml.

  6. Open and execute the second installation script for direct or indirect synchronization. For example:

    tools\sql\informix\direct\INSTALL_DIRECT_2.sql

    tools\sql\informix\indirect\INSTALL_INDIRECT_2.sql


Troubleshooting Tips

  • When generating events for publication, make sure you are logged in as someone other than the dirxml user. If you make changes as the dirxml user, your changes will not be published.
  • Be sure to commit changes. Until you commit your changes, they will not be published.
  • Make sure you are logged in as the correct user on the correct database when running the scripts.