IBM Support

Using the Relational Schema Center (Data Perspective) to connect to a DB2 UDB v8.x on AIX 64-bit or Linux 64-bit fails

Troubleshooting


Problem

In the Data Perspective of Rational® Application Developer, if you are attempting to connect to a DB2® Universal Database version 8.x running on a 64-bit AIX or Linux® operating system, you encounter the following error: "IWAS0223E - not a DB2 UDB 8.x database" Testing the connection shows that you have a successful connection but when trying to read the database, it fails.

Cause

This error occurs because using the Relational Schema Center (Data Perspective) to connect to DB2 version 8.x residing on an AIX 64-bit or Linux 64-bit operating system is NOT SUPPORTED.

Resolving The Problem

The following information is provided only as a possible workaround for this issue, as connecting to DB2 version 8.x residing on an AIX 64-bit or Linux 64-bit operating system is not supported for WSAD or RAD.

Workarounds:
If you are using WebSphere® Studio Application Developer (WSAD) and trying to connect to DB2 version 8.x on a 64-bit operating system, as a workaround you can modify the domain file (on the client machines, where WSAD is running). For example:
DB2 UDB v8.1
C:\Program Files\IBM\WebSphere Studio\Application
Developer\v5.1.2\wstools\eclipse\plugins\com.ibm.etools.sqlmodel_5.1.2.*\runtime\vendors\DB2UDBNT_V8\DB2UDBNT_V8_Domain.xmi.

Where * is the latest version of the plugin available.

Below each JDBC driver being used, add a new metaData entry:
<metaData name="METADATA_PRODUCT_NAME" value="DB2/AIX64"/>

Thus, in the DB2UDBNT_V8_Domain.xmi file, you would see:
<drivers xmi:id="JDBCDriver_6" name="IBM DB2 UNIVERSAL DRIVER" subprotocol="db2" driverClassName="com.ibm.db2.jcc.DB2Driver" defaultPortNumber="50000" subprotocolTemplate="{0}:" hostSubnameTemplate="//{1}" portSubnameTemplate=":{2}" dbSubnameTemplate="/{3}" readerClassName="com.ibm.etools.rdb2xmi.DB2UDBReader">
<metaData name="METADATA_PRODUCT_NAME" value="DB2/NT"/>
<metaData name="METADATA_PRODUCT_NAME" value="DB2/LINUX"/>
<metaData name="METADATA_PRODUCT_NAME" value="DB2/6000"/>
<metaData name="METADATA_PRODUCT_NAME" value="DB2/HPUX"/>
<metaData name="METADATA_PRODUCT_NAME" value="DB2/SUN"/>
<metaData name="METADATA_PRODUCT_NAME" value="DB2/LINUX390"/>
<metaData name="METADATA_PRODUCT_NAME" value="DB2/AIX64"/>
</drivers>


If you are using Rational® Application Developer (RAD) and attempting to connect to DB2 version 8.x running on a 64-bit operating system, as a workaround you can modify the domain file (on the client machines, where RAD is running). For example:
DB2 UDB v8.1
C:\IBM\Rational\SDP\6.0\rwd\eclipse\plugins\com.ibm.etools.sqlmodel_6.0.1.*\runtime\vendors\DB2UDBNT_V8\DB2UDBNT_V8_Domain.xmi

DB2 UDB v8.2
C:\IBM\Rational\SDP\6.0\rwd\eclipse\plugins\com.ibm.etools.sqlmodel_6.0.1.*\runtime\vendors\DB2UDBNT_V82\DB2UDBNT_V82_Domain.xmi

Where * is the latest version of the plugin available.

Below each JDBC driver being used, add a new metaData entry:
<metaData name="METADATA_PRODUCT_NAME" value="DB2/AIX64"/>

<drivers xmi:id="JDBCDriver_1" name="Other DB2 Driver" hostSubnameTemplate="{1}:" portSubnameTemplate="{2}:" dbSubnameTemplate="{3}" readerClassName="com.ibm.etools.rdb2xmi.JDBCReader"/>
<drivers xmi:id="JDBCDriver_6" name="IBM DB2 UNIVERSAL DRIVER" subprotocol="db2" driverClassName="com.ibm.db2.jcc.DB2Driver" defaultPortNumber="50000" subprotocolTemplate="{0}:" hostSubnameTemplate="//{1}" portSubnameTemplate=":{2}" dbSubnameTemplate="/{3}" readerClassName="com.ibm.etools.rdb2xmi.DB2UDBReader">
<metaData name="METADATA_PRODUCT_NAME" value="DB2/NT"/>
<metaData name="METADATA_PRODUCT_NAME" value="DB2/LINUX"/>
<metaData name="METADATA_PRODUCT_NAME" value="DB2/6000"/>
<metaData name="METADATA_PRODUCT_NAME" value="DB2/HPUX"/>
<metaData name="METADATA_PRODUCT_NAME" value="DB2/SUN"/>
<metaData name="METADATA_PRODUCT_NAME" value="DB2/LINUX390"/>
<metaData name="METADATA_PRODUCT_NAME" value="DB2/AIX64"/>
</drivers>

Please note that though this can work, it is not officially supported in WSAD version 5.x or RAD version 6.x.

In the Related URL section below, there is a link to another technote documenting an additional suggestion for resolving the issue.



[{"Product":{"code":"SSRTLW","label":"Rational Application Developer for WebSphere Software"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Data Access Applications","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"6.0;6.0.0.1;6.0.1.0;6.0.1.1","Edition":"All Editions","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSBRLP","label":"WebSphere Studio Application Developer"},"Business Unit":{"code":"BU050","label":"BU NOT IDENTIFIED"},"Component":"Relational database tools","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"5.0;5.0.1;5.1;5.1.1;5.1.2","Edition":"All Editions","Line of Business":{"code":"","label":""}},{"Product":{"code":"SSYK2S","label":"Rational Software Architect Designer"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Data Access Applications","Platform":[{"code":"PF033","label":"Windows"},{"code":"PF016","label":"Linux"}],"Version":"6.0;6.0.0.1;6.0.1.0;6.0.1.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Historical Number

apar PK22213

Document Information

Modified date:
10 September 2020

UID

swg21233268