Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Installing MDM Registry Edition
  4. Post-Installation Tasks
  5. Troubleshooting
  6. Upgrading MDM Registry Edition
  7. Uninstalling MDM Registry Edition

Installation and Configuration Guide

Installation and Configuration Guide

Troubleshooting IBM DB2 UDB

Troubleshooting IBM DB2 UDB

The first time when you use IBM DB2 UDB after you install
MDM Registry Edition
, you might encounter the following issues:
When I ran the Update Synchronizer, I received an SQL07323N error message.
If you do not install the user-defined functions, the Update Synchronizer displays the following message:
SQL07323N An error occurred in a triggered SQL statement in trigger "SSA.IDS0000U" Information returned from the error includes SQLCODE "-444", SQLSTATE "42724" and message tokens "*_VARCHAR|SQL050704134911400|...qllib/function". SQLSTATE=09000
Run the following command to get the reason code, and install the user-defined functions on all the source and target databases.
db2 values ids_comp_varchar (SMALLINT(3),’fred’,’tony’,’henry’,’’,’’,’’,’’,’’,’’,’’,’’,’’,’’,’’,’’,’’);:
When I ran a database process, I received an SQL1224N error message.
If you do not start the database manager or the database agent, the following error might appear:
SQL1224N A database agent could not be started to service a request, or was terminated as a result of a database system shutdown or a force command.
Perform the following tasks:
  1. Ensure that the database manager runs on the database server.
  2. Ensure that the database agent runs.
  3. Ensure that the number of agents allocated to the database manager does not exceed the maximum limit.
  4. Connect your local machine as a remote client by performing the following tasks:
    1. Run the following command to catalog the node:
      db2 catalog tcpip node <Node Name> remote <Host Name> server <Server Name>
    2. Run the following command to verify that the catalog command worked correctly:
      db2 list node directory
    3. Run the following command to catalog the database:
      db2 catalog db <Database Name> as <Database Alias> db2 uncatalog db <Database Name> db2 catalog db <Database Alias> as <Database Name> at node <Node Name>
      This command prevents the SQL1334N error that can occur when the database name is same as the database alias.
    4. Stop and start IBM DB2 UDB.
On Windows, from the Start menu, when I selected Informatica
MDM - Registry Server
- start, the idsup.bat file launched a Windows command prompt instead of the IBM DB2 UDB command prompt.
If you configure IBM DB2 UDB as your database after installing
MDM Registry Edition
, the
Informatica MDM - Registry Server - start
menu might launch the Windows command prompt,
cmd.exe
.
You get the Windows prompt if the
Informatica MDM - Registry Server - start
shortcut refers to the Windows command prompt. For example,
C:\SQLLIB\bin\cmd.exe /C C:\InformaticaIR\bin\idsup.bat.
To get the IBM DB2 UDB command prompt, manually update the shortcut to launch the IBM DB2 UDB command prompt,
db2cmd.exe
. For example,
C:\SQLLIB\bin\db2cmd.exe /C C:\InformaticaIR\bin\idsup.bat.
On AIX, when I ran the dblist command, I received an error message.
If the ODBC Driver Manager is linked with an archived library instead of a shared library, the
dblist
command might fail with the following message:
The module has an invalid magic number.
To resolve this issue, link the ODBC Driver Manager with a shared library.
To link the ODBC Driver Manager with a shared library, perform the following tasks:
  1. Run the following commands to extract the shared library:
    cd <IBM DB2 UDB Installation Directory>/sqllib/lib ar -x -X 64 libdb2.a mv shr_64.o db2_64.o
  2. Open the configuration file of the ODBC Driver Manager, which is usually
    odbcinst.ini
    , and update the value of the ODBC driver with the shared library,
    db2_64.o
    .