cancel
Showing results for 
Search instead for 
Did you mean: 

Error while installing NW7.3 ABAP for DB2 on z/OS Install DB CLI driver

Former Member
0 Kudos

Dear Experts,

i'm installing for the first time NW7.3 ABAP for DB2 on z/OS with AIX application server. Central Services was installed succesfull but next step Install Database on AIX stoped with error (establishConn.log):

db2radm (release: "720", patch level: "000", version: "Jan 14 2012") begin:28.02.2012 10:54:39

This is db2radm release: "720", patch level: "120", version: "Jan 14 2012".

This is db2radm setting up DB2 Connect.

Message file is /sapmnt/tmp/sapinst_instdir/NW73/INSTALL/NW73/DB2/HA/PI/DB/establishConn.log.

db2radm called as: /usr/sap/DW8/SYS/exe/uc/rs6000_64/db2radm -m db2i -P 456 -L DW8DDF -S DW88 -H s10d1 -u SAPADM -p ******** -W primary_only -l /sapmnt/tmp/sapinst_instdir/NW73/INSTALL/NW73/DB2/HA/PI/DB/establishConn.log

Adjusting environment

dbs_db2_ssid=DW88

SAPDBHOST=s10d1

dbs_db2_user=SAPADM

dbs_db2_schema=SAPADM

dbs_db2_schema8=1

dbs_db2_pw=********

Checking environment

DB host = s10d1

SSID = DW88

SAPSYSTEMNAME = DW8

DB2Trc: 000000 CLI_ALLOC_ENV 1

connect.ini file used: 'connect.ini.for.db2radm'

-


Fail over connection list of this application server:

-


NAME = DW88_on_s10d1

USER = SAPADM

PASSWORD = <***>

SCHEMA = SAPADM

PS = SAP0907U

LOCATION = DW8DDF

SSID = DW88

HOST = s10d1

PORT = 456

RETRY_CNT = 3

SLEEP_TIME = 0

DB2Trc: trace level of dbdb2cli set to 1

COLLECTION ID used is "SAP0907U"

DB2 Call 'SQLDriverConnectW' Warning: SQLCODE = 8007 : [IBM][CLI Driver][DB2] SQL8007W There are "90" day(s) left in the evaluation period for the product "DB2 Connect". For evaluation license terms and conditions, refer to the License Agreement document located in the license directory in the installation path of this product. If you have licensed this product, ensure the license key is properly registered. You can register the license via the License Center or db2licm command line utility. The license key can be obtained from your licensed product CD. SQL

use lib_dbsl for DB2 version V9.

Callback functions for dynamic profile parameter registered

DbSl library successfully loaded.

WARNING: schema with 8 bytes length allowed; shadow upgrate will not work

dbs/db2/use_accounting != 1 -> DB2 accounting is switched off

dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used

dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on

dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off

SQL DRIVER VERSION is "09.07.0003"

DB2Connect driver identified as THIN CLIENT

Now I'm connected to DW88_on_s10d1

DB2 DBMS version 09.01.0005

DB2 LOCATION name DW8DDF

(HYB): Info: Using OLD dbsl support.

DB2 connect shared library loaded successfully.

09.07.0003DB2Connect driver identified as THIN CLIENT

WARNING: schema with 8 bytes length allowed; shadow upgrate will not work

dbs/db2/use_accounting != 1 -> DB2 accounting is switched off

dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used

dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on

dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off

DBSLHA: Got Failover profile /usr/sap/DW8/SYS/global/connect.ini

DBSLHA: Using new Failover Support

DBSLHA: Using user( SAPADM) and password(<pwd>) from profile.

DBSLHA:

DBSLHA:Connection List

DBSLHA:

DBSLHA:NAME |HOST |SSID|COLLECTION |PLAN |PORT |SCHEMA |OWNER |LOCATION |RETRY|SLEEP|

DBSLHA:--


|
|
|
|

|

|

|

|

|
-|---|

DBSLHA:DW88_on_s1|s10d1 |DW88|SAP<DB2Conne| | |SAPADM |SAPADM |DW8DDF |00003|00000|

DBSLHA:--


|
|
|
|

|

|

|

|

|
-|---|

GetHaProfile: GetHaProfile: found 1 connections in connection profile.

GetHaProfile: found section DW88_on_s10d1, ssid DW88, port 456, location DW8DDF, host s10d1 in connection profile

connection profile /usr/sap/DW8/SYS/global/connect.ini opened.

>>>>>> dump of connection profile

  • ADDED 20120228 103331 by DB2RADM RELEASE 720 PATHLEVEL 000

[DEFAULT_GROUP]

CON1=DW88_on_s10d1

[DW88_on_s10d1]

SSID=DW88

HOST=s10d1

PORT=456

LOCATION=DW8DDF

<<<<<< end of dump of connection profile

ssid DW88 found in connection profile, section DW88_on_s10d1.

>>> analyse line: * ADDED 20120228 103331 by DB2RADM RELEASE 720 PATHLEVEL 000

>>> analyse line: [DEFAULT_GROUP]

>>> analyse line: CON1=DW88_on_s10d1

>>> analyse line:

>>> analyse line: [DW88_on_s10d1]

section DW88_on_s10d1 found.

>>> analyse line: SSID=DW88

>>> analyse line: HOST=s10d1

>>> analyse line: PORT=456

>>> analyse line: LOCATION=DW8DDF

>>> analyse line: section DW88_on_s10d1 found and data matches.

backup connection profile /usr/sap/DW8/SYS/global/connect.ini .

switch connection profile /usr/sap/DW8/SYS/global/connect.ini .

check for adapted connection profile.

WARNING: schema with 8 bytes length allowed; shadow upgrate will not work

dbs/db2/use_accounting != 1 -> DB2 accounting is switched off

dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used

dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on

dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off

DBSLHA: Got Failover profile /usr/sap/DW8/SYS/global/connect.ini

DBSLHA: Using new Failover Support

DBSLHA: Using user( SAPADM) and password(<pwd>) from profile.

DBSLHA:

DBSLHA:Connection List

DBSLHA:

DBSLHA:NAME |HOST |SSID|COLLECTION |PLAN |PORT |SCHEMA |OWNER |LOCATION |RETRY|SLEEP|

DBSLHA:--


|
|
|
|

|

|

|

|

|
-|---|

DBSLHA:DW88_on_s1|s10d1 |DW88|SAP<DB2Conne| | |SAPADM |SAPADM |DW8DDF |00003|00000|

DBSLHA:--


|
|
|
|

|

|

|

|

|
-|---|

GetHaProfile: GetHaProfile: found 1 connections in connection profile.

GetHaProfile: found section DW88_on_s10d1, ssid DW88, port 456, location DW8DDF, host s10d1 in connection profile

ssid DW88 found in connection profile, section DW88_on_s10d1.

check for adapted connection profile passed.

WARNING: schema with 8 bytes length allowed; shadow upgrate will not work

dbs/db2/use_accounting != 1 -> DB2 accounting is switched off

dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used

dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on

dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off

DBSLHA: Got Failover profile /usr/sap/DW8/SYS/global/connect.ini

DBSLHA: Using new Failover Support

DBSLHA: Using user( SAPADM) and password(<pwd>) from profile.

DBSLHA:

DBSLHA:Connection List

DBSLHA:

DBSLHA:NAME |HOST |SSID|COLLECTION |PLAN |PORT |SCHEMA |OWNER |LOCATION |RETRY|SLEEP|

DBSLHA:--


|
|
|
|

|

|

|

|

|
-|---|

DBSLHA:DW88_on_s1|s10d1 |DW88|SAP<DB2Conne| | |SAPADM |SAPADM |DW8DDF |00003|00000|

DBSLHA:--


|
|
|
|

|

|

|

|

|
-|---|

GetHaProfile: GetHaProfile: found 1 connections in connection profile.

GetHaProfile: found section DW88_on_s10d1, ssid DW88, port 456, location DW8DDF, host s10d1 in connection profile

WARNING: schema with 8 bytes length allowed; shadow upgrate will not work

dbs/db2/use_accounting != 1 -> DB2 accounting is switched off

dbs/db2/use_drda_lob_handling != 1 -> SAP LOB handling is used

dbs/db2/chaining = 20 -> CLI CHAIN optimization is switched on

dbs/db2/opt2_hint = 1 -> implicit 'optimize for 1 rows' hint is switched off

DBSLHA: Got Failover profile /usr/sap/DW8/SYS/global/connect.ini

DBSLHA: Using new Failover Support

DBSLHA: Using user( SAPADM) and password(<pwd>) from profile.

DBSLHA:

DBSLHA:Connection List

DBSLHA:

DBSLHA:NAME |HOST |SSID|COLLECTION |PLAN |PORT |SCHEMA |OWNER |LOCATION |RETRY|SLEEP|

DBSLHA:--


|
|
|
|

|

|

|

|

|
-|---|

DBSLHA:DW88_on_s1|s10d1 |DW88|SAP<DB2Conne| | |SAPADM |SAPADM |DW8DDF |00003|00000|

DBSLHA:--


|
|
|
|

|

|

|

|

|
-|---|

SQL DRIVER VERSION is "09.07.0003"

DB2Connect driver identified as THIN CLIENT

DB2Trc: 00 000000 cli_get_cli_driver_bld_level 1 s101006

SQL DRIVER NAME is "libdb2.a"

SQL DBMS NAME is "DB2"

SQL DBMS VERSION is "09.01.0005"

DATABASE NAME(DB2 Connect DCS database name) is "DW8DDF"

The bind is skipped since collection for ssid DW88 is already bound.

To force the bind, use option "-B force".

DB2TRC: 0000000000 00 000000 CLI_DISCONNECT

DB2TRC: 0000000000 00 000000 CLI_FREE_DBC 1

DB2TRC: 0000000000 00 000000 CLI_FREE_ENV 1

DB VERSION is 09.01.0005.

Starting Grants .

DB2Trc: 000000 CLI_ALLOC_ENV 1

COLLECTION ID used is "SAP0907U"

DB2 Call 'SQLDriverConnectW' Warning: SQLCODE = 8007 : [IBM][CLI Driver][DB2] SQL8007W There are "90" day(s) left in the evaluation period for the product "DB2 Connect". For evaluation license terms and conditions, refer to the License Agreement document located in the license directory in the installation path of this product. If you have licensed this product, ensure the license key is properly registered. You can register the license via the License Center or db2licm command line utility. The license key can be obtained from your licensed product CD. SQL

Connecting to <DW88_on_s10d1> on connection 0 ...

Now I'm connected to DB2 (09.01.5)

SQL DRIVER NAME is "libdb2.a"

SQL DBMS NAME is "DB2"

SQL DBMS VERSION is "09.01.0005"

DATABASE NAME(DB2 Connect DCS database name) is "DW8DDF"

New functions of DB2 V9 are switched on

Profile parameter dbs/db2/cli_trace_dir is not set

dbdb2dic.c 1709 INFO Profile: SDB2_DEBUG=<UNSET>

dbdb2dic.c 1733 INFO Envrmnt: sdb2_debug=<UNSET>

dbdb2dic.c 1733 INFO Envrmnt: SDB2_DEBUG=<UNSET>

DB2 Call 'CLI_EXECUTE' Error: sqlcode = -204 : [IBM][CLI Driver][DB2] SQL0204N "SAPADM.#LOBU" is an undefined name. SQLSTATE=42704

dbdb2dic.c 2251 INFO rc=103,sqlcode=-204: ExeRead

dbdb2dic.c 1709 INFO Profile: dbs/db2/max_retry=<UNSET>

dbdb2dic.c 1733 INFO Envrmnt: DB2_MAX_RETRY=<UNSET>

dbdb2dic.c 1709 INFO Profile: dbs/db2/retry_on_924=<UNSET>

dbdb2dic.c 1733 INFO Envrmnt: DB2_RETRY_ON_924=<UNSET>

dbdb2dic.c 1709 INFO Profile: dbs/db2/no_retry_on_10=<UNSET>

dbdb2dic.c 1733 INFO Envrmnt: dbs_db2_no_retry_on_10=<UNSET>

dbdb2dic.c 1733 INFO Envrmnt: DBS_DB2_NO_RETRY_ON_10=<UNSET>

DB2 Call 'SQLEndTran' Error: sqlstate = 08003 : [IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE=08003

[dbdb2dic.c 1873:rc=99: COMMIT WORK failed]

dbdb2dic.c 1873 ERROR rc=99: COMMIT WORK failed

[dbdb2dic.c 2019:rc=99,sqlcode=268435455: ExecDDL failed (DB error)]

dbdb2dic.c 2019 ERROR rc=99,sqlcode=268435455: ExecDDL failed (DB error)

DB2 Call 'SQLEndTran' Error: SQLCODE = -99999 : [IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE=08003

ROLLBACK failed with SQL error '-99999'

ERROR: couldn't connect to DB

rc = 99

error message returned by DbSl:

rc=99,sqlcode=268435455: ExecDDL failed (DB error)

DB2RADM EXITCODE: 12

db2radm finished (0012)

db2radm stop:28.02.2012 10:54:39

-


i've patched db2radm and sapinst to the latest version.

May be i should manually create "SAPADM.#LOBU"?

Please help to solve these issue.

Best regards,

Alexander V

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi ,

Please check if Note 1581637 - Installing a System with DB2CODEPAGE other than the default is useful.

Award points if useful.

Thanks,

Ravi

Answers (0)