Message after applicated DB2 FP7

[Former Member]

Hello,

WE have upgrade  the DB2 Fixpack  from 05 to FP07, in the process ,, we didn´t have any problems and the system is running, however we have check in dev_w0 log and we found  this message:

C  ..retrieving configuration parameters

C  ..done

C  DB2 library has been loaded.

C  Info: successfully loaded DB2 library '/usr/sap/DEV/SYS/global/db6/AIX_64/db6_clidriver/lib/libdb2.

C  Running with UTF-8 Unicode

C  DB2 client driver version '09.07.0007'

C  *** ERROR => Error setting SQLSetEnvAttr( SQL_ATTR_DB2TRC_STARTUP_SIZE=32 ), rc=-2

[dbdb6.c      13967]

C  *** ERROR => SQLGetDiagField(SQL_DIAG_NUMBER): rc=-2

[dbdb6.c      11405]

C  *** ERROR in getConfigurationAndEnvironmentHandle[dbdb6.c, 13977] CON = -1 (BEGIN)

C  &+     DbSlConnectDB6( SQLSetEnvAttr 😞

C  &+

C  &+

C  *** ERROR in getConfigurationAndEnvironmentHandle[dbdb6.c, 13977] (END)

C  *** ERROR => Unable to retrieve effective SQL_ATTR_DB2TRC_STARTUP_SIZE

[dbdb6.c      14049]

C  *** ERROR => SQLGetDiagField(SQL_DIAG_NUMBER): rc=-2

[dbdb6.c      11405]

C  *** ERROR in getConfigurationAndEnvironmentHandle[dbdb6.c, 14059] CON = -1 (BEGIN)

C  &+     DbSlConnectDB6( SQLSetEnvAttr 😞

C  &+

C  &+

C  *** ERROR in getConfigurationAndEnvironmentHandle[dbdb6.c, 14059] (END)

C  Running with CLI driver.

C

C Sat Mar  9 02:07:41 2013

C  Connected to DB server type 'DB2/AIX64'

C  Connected to DB server version '09.07.0007'

C  Connected to 'DEV' as 'SAPDEV' schema 'SAPDEV' o.k.

C  Connected: con_hdl=0 ; appl_hdl=34; appl_id="10.16.114.50.53865.130309070706"

C  Current member="10.16.114.50:5912"

C  Database code page is ok.

C  Database collating sequence is ok.

C  DB2_WORKLOAD=SAP is set in DB2 registry as required.

C  CLI Insert Buffering is disabled on single partition databases.

C  DbSl trace SM50: switch request to level 1

B  Connection 0 opened (DBSL handle 0)

M  ThInit: db_connect o.k.

we don´t know What is the reason for this message? any suggestion??

Best Regards

Danny

[Former Member · Accepted solution]

Hello,

in spite of that you got no problems we have them.

An IDES BW system was regarded and so I tried to install on on Win 2008R2 with DB6 8 UDB (because the NW 7.0 SR3 installer isn't available anymore). During the installation - for several requirements for W2k8R2-   I had to upgrade the 7.00 UC-Kernel to 7.20EXT and the DB2 8 to 9.7 FP7.

Because before  NW7 SP14 the DB2 CLI Driver is not supported (also before DB2 9.1), we have the DB2 Runtime client.

On our IDES-system we get the same message in the dev-traces, but our prozesses are dying with this message.

I guess You have still installed the DB2 Runtime client while using the DB2 CLI driver.

You can determine whether it is so, by executing db2ilist  in a db2<sid> shell.

If you have the runtime client installed, your db2 instances will be listed.

Regards

Christian

[Frank-Martin · Accepted solution]

Hi Christian,

please provide a dev trace of a dying process. You can send it to me via mail. As I said the SQL_ATTR_DB2TRC_STARTUP_SIZE entries in the dev traces are harmless. There must be another reason for the dying processes.

Regards

               Frank

[Former Member · Accepted solution]

Hello, Frank,

unfortunately these original logs and traces are not available any more, because yesterday  I installed the CLI driver and the system started after doing so.

The errors in the traces are the same like in Danny's traces now, also the additional message

C  *** ERROR in getConfigurationAndEnvironmentHandle[dbdb6.c, 14059] (END)

C  Running with CLI driver.

C 

appears.

I know, it is not supported anyway, because it is an IDES with 7.00 SP9 (officially suport with SP14), but it works and that is enough in the moment, because it is a demo system.

Thank You anyway for Your help.

Kind regards

Christian.

[Frank-Martin · Accepted solution]

Hi Christian,

the error messages from Dannys trace look dangerous but can be savely ignored. I have meanwhile documented them in note 1835350. The messages appear on V9.7 FP7 clients only and will be avoided with the next dbdb6slib.* version which should appear on SMP some time next week.

I would have loved to understand why your WPs died but would need a full dev trace to investigate further.

Regards

                  Frank

[Frank-Martin · Accepted solution]

Sorry, correct note number is 1836451 . Regards Frank

[Former Member · Accepted solution]

Thanks  FRank ,

the message  is  fixed, I  update the library

Muchas Gracias

Danny

lib_dbsl_421-20005241.sar

Database Library

421

Info

2300

25.03.2013

[hugo_amo]

Hi Danny,

This error is described in:

Note 1789197 - DB6: CPU load caused by semget on SAP application server

Regards,

Hugo Amo.

[Frank-Martin]

Hi,

those error entries can be savely ignored. We are trying to allocated the CLI trace shared memory segments in the database interface starting with V9.7 FP7 ( note 1789197 ). After releasing the SAP database interface change it turned out that the new CLI attribute SQL_ATTR_DB2TRC_STARTUP_SIZE did not make it into the IBM CLI FP7 code. So our attempt fails but this does not cause any problems.

The error messages will go away with FP8 and with the next database interface patch.

Regards

              Frank

[former_member188883]

Hi Danny,

C  *** ERROR => Unable to retrieve effective SQL_ATTR_DB2TRC_STARTUP_SIZE
[dbdb6.c      14049]
C  *** ERROR => SQLGetDiagField(SQL_DIAG_NUMBER): rc=-2
[dbdb6.c      11405]

Above looks like system is trying to setsome environment variables and retrieve the same and its where this is failing. Above paramters are basically used for performance trace and hence it has nothing to do with normal system operations.

Please check db2sid and sidadm user environments whether such parameter has been set. If SET whether they are correctly maintained.

Regards,

Deepak Kori