MAIN_NEWBAS/SHADOW_NTACT_REDEL

[Former Member]

Hi All,

Our Landscape : HP Unix / DB2 10.5

Performing Upgrade : From EHP5 to EHP7

Currently we are in the downtime phase and believe almost nearing to the completion. However things getting into trouble because of the environment varaibale.

Now we are in the downtime phase MAIN_NEWBAS/SHADOW_NTACT_REDEL - and it says that tp is not able to get connect with the database and hence it fails. When we wheck the logs its looking for variable  DB2DB6EKEY it seems, however this variable is existing in sidadm and also in db2sid.

R3trans working fine and even the original systems are up and running (I could see that )

However not able to proceed further in the phase as its not constantly looking for this - Any inputs will help us alot.

TP.ECO Log

This is tp version 380.28.39 (release 742, unicode enabled)

ERROR: Connect to MED failed (20150627084546, probably wrong environment).

TRACE-INFO: 1: [     dev trc,00000]  Sat Jun 27 08:45:46 2015 41902  0.041902

TRACE-INFO: 2: [     dev trc,00000]  DlLoadLib() success: dlopen("/usr/sap/MED/DVEBMGS10/exe/dbdb6slib.so"), hdl 0, count 1, addr 9fffffffef44f9f0

TRACE-INFO: 3: 9  0.041911

TRACE-INFO: 4: [     dev trc,00000]  *** ERROR in DbSlConnectDB6[/bas/742_REL/src/dbs/db6/dbsldb6.c, 1323] CON = 0 (BEGIN)

TRACE-INFO: 5: 3760  0.045671

TRACE-INFO: 6: [     dev trc,00000]  &+ DbSlConnectDB6: DB2DB6EKEY not found in environment or password file

TRACE-INFO: 7: 21  0.045692

TRACE-INFO: 8: [     dev trc,00000]  &+

TRACE-INFO: 9: 17  0.045709

TRACE-INFO: 10: [     dev trc,00000]  &+

TRACE-INFO: 11:                                                                                                           16  0.045725

TRACE-INFO: 12: [     dev trc,00000]  &+

TRACE-INFO: 13: 24  0.045749

TRACE-INFO: 14: [     dev trc,00000]  &+

TRACE-INFO: 15: 16  0.045765

TRACE-INFO: 16: [     dev trc,00000]  *** ERROR in DbSlConnectDB6[/bas/742_REL/src/dbs/db6/dbsldb6.c, 1323] (END)        15 0.045780

tp returncode summary:

SAP Log

CURRENTPHASE MAIN_NEWBAS/SHADOW_NTACT_REDEL

...started at 20150627094246

# Using phase log file 'NTSHDDEL.LOG'.

# Phase error status set: ERRORS in NAMETAB ACTION found

..finished at 20150627094246 with status ABORTED.

# Error message set: 'No new lines found in logfiles.'

...begin dialog at 20150627094249

...end dialog at 20150627100335

..answered at 20150627100335.

-> decided to try again.

CURRENTPHASE MAIN_NEWBAS/SHADOW_NTACT_REDEL

...started at 20150627100335

# Using phase log file 'NTSHDDEL.LOG'.

# Phase error status set: ERRORS in NAMETAB ACTION found

..finished at 20150627100336 with status ABORTED.

# Error message set: 'No new lines found in logfiles.'

...begin dialog at 20150627100338

Environament Variables

SAPSYSTEMNAME=MED

DIR_LIBRARY=/usr/sap/MED/SYS/exe/run

RSEC_SSFS_DATAPATH=/usr/sap/MED/SYS/global/security/rsecssfs/data

RSEC_SSFS_KEYPATH=/usr/sap/MED/SYS/global/security/rsecssfs/key

rsdb_ssfs_connect=0

SHLIB_PATH=/usr/sap/MED/SYS/exe/run:/usr/sap/MED/SYS/exe/uc/hpia64

JAVA_HOME=/opt/java1.4

DB2INSTANCE=db2med

INSTHOME=/db2/db2med

CLASSPATH=:/db2/db2med/sqllib/java/db2java.zip:/db2/db2med/sqllib/java/runtime.zip:.:/db2/db2med/sqllib/java/db2java.zip:/db2/db2med/sqllib/java/runtime.zip:.

DB2DBDFT=MED

LANG=en_US.iso88591

DB2DB6EKEY=MEDMHZKED1

dbms_type=db6

dbs_db6_schema=SAPMED

Highly appreciate your inputs - week end about to finish  😞 and have raised the messsage with SAP in parallel

Regards

VJ

[mirra_yin · Accepted solution]

Hello Vijay

Please check the environment  files (.csh, .sh) from the home directory of sidadm (/home/sidadm).

Maintain the DB2DB6EKEY environment variable according to the guidelines of the note:

#582875 DB6: SAP cannot log onto the database

"

The passwords of the <sid>adm and sap<sid> or sapr3 users are stored in enciphered form in the file system. The value of the environment variable DB2DB6EKEY isused for the code. This variable can be maintained inconsistently on UNIX systems for different users and shells.

The error occurs in particular when shell scripts are called that are often written for the corn shell while the users are running under the C shell."

Regards

Mirra

[former_member185239]

Dear Gopal,

Which version of SUM are you using?

if possible remove the line /DB2/cli_version = 09.07.0003 from SAPup.par file and retry the step.

With Regards

Ashutosh Chaturvedi

[Former Member]

Hi Vijay,

Please check the dbdb6slib.so file version and check the compatibility in shadow instance.

Please use the command give below:-

sapcontrol -nr 00 -function GetVersionInfo  where 00 is your system number

Regards

Satya velivela

[former_member182034]

hi Vijay,

did you check these SAP note? If not, please check it might be resolve this issue.

1159020 - SAP NetWeaver 7.0 EHP1/Business Suite 7: IBM DB2 for z/OS

1966797 - Errors: connect failed due to DbSL load lib failure

Regards,

[Former Member]

Thanks Abdul.

Nothing helped and tried the both.

Also after a restart in the very next phase it says the same thing stating DB environment variable is the issue and I would prefer to wait for sometime as its getting critical for each thing.

SAP also not responding to it -

Regards

VJ