cancel
Showing results for 
Search instead for 
Did you mean: 

DB02/DB50 after upgrade to 7.7.06.16

Former Member
0 Kudos

Hi MaxDB experts.

I have upgraded the MaxDB of a Netweaver BI 7.01 system (EHP1 SP5).

Possibly I have done something wrong, because the client-software seems not to be upgraded correctly.

In DB59, the connection test fails except for the native SQL.

System is running fine, but I have problems with DB02 and DB50.

I have looked up several notes ont this issue but somehow my situation is not exactly represented.

Can it be that the DBMRFC or DBMCLI are not used or installed in a proper way?

The DBVERIFY shows no locks or permission problems.

Can anyone help me?

Gr.,

Marc

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

hi Marc,

Can you repost the output of u2018sdbregview u2013lu2019 on the database server & the application server? The long list option(-l) also shows if each of the packages are valid or invalid. If you see an invalid package or two, that needs to be corrected.

Can you confirm, the verification summary from 'sdbverify' (SAP note 546737) is all good? no invalid/inconsistent packs, etc?

BR,

Junco Ueda

Former Member
0 Kudos

Hi Junco.

The sdbregview -l and sdbregview show valid and consistent packages only.

Previously I had read the note you mention that triggered me to check the packages even before posting this message. Therefor I can assure you that the solution for this problem is probably not to be found in invalid or inconsistent packages.

Reposting seems not very usefulll to my opinion.

Any other ideas?

Thanx for replying.

Gr.,

Marc.

former_member229109
Active Contributor
0 Kudos

Hello,

You wrote:u201D Possibly I have done something wrong, because the client-software seems not to be upgraded correctly.u201D

=> Junco was correct to recommend you to run the sdbverify

< Not dbverify, as you wrote, u201CThe DBVERIFY shows no locks or permission problems.u201D > .

The sdbverify tool located in <IndepProgPath>/bin.

Go to this directory & run sdbverify <enter > and post the results.

Also please update with ouput of the commands:

dbmcli u2013d MBI u2013n HTC001 u2013u <dbm-user>,<pwd> db_state

Please check the errors in dbmsrv* logs located in <IndepDataPath>/wrk

Please test connection in /nsm59: SAPDB_DBM & SAPDB_DBM_DAEMON, post results.

Test connection in /ndb59, go to /nst11 and check the latest logs for errors.

I recommend you to create the OSS message, so we could check the issue via OSS.

Thank you and best regards, Natalia Khlopina

Former Member
0 Kudos

Hi Junco.

Changed my mind.

Here's the log sdbverify:

DB Analyzer 7.7.06.16 64 bit in e:/sdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

Server Utilities 7.7.06.16 64 bit in e:/sdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

Database Studio 7.7.06.09 in e:/sdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

PCR 7301 7.3.01.22 in e:/sdb/programs

-


check files... ok

check dependencies... ok

check rte registration of package... ok

package data is consistent

PCR 7500 7.5.00.51 64 bit in e:/sdb/programs

-


check files... ok

check dependencies... ok

check rte registration of package... ok

package data is consistent

SAP Utilities 7.7.06.16 64 bit in e:/sdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

Base 7.7.06.16 64 bit in e:/sdb/programs

-


check files... ok

check dependencies... ok

check rte registration of package... ok

package data is consistent

Redist Python 7.7.06.16 64 bit in e:/sdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

JDBC 7.6.06.05 in e:/sdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

Messages MSG 0.7732 in e:/sdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

ODBC 7.7.06.16 64 bit in e:/sdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

SQLDBC 77 7.7.06.16 64 bit in e:/sdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

Database Kernel 7.7.06.16 64 bit in e:/sapdb/mbi/db

-


check files... ok

check dependencies... ok

check rte registration of package... ok

package data is consistent

Database Studio Utilities 7.7.06.09 in e:/sdb/programs/databasestudio/utilities

-


check files... ok

check dependencies... ok

check rte registration of package... ok

package data is consistent

Loader 7.7.06.16 64 bit in e:/sdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

SQLDBC 7.7.06.16 64 bit in e:/sdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

SQLDBC 76 7.6.06.06 64 bit in e:/sdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

Fastload API 7.7.06.16 64 bit in e:/sdb/programs

-


check files... ok

check dependencies... ok

package data is consistent

VERIFICATION SUMMARY:

*********************

NUMBER OF INVALID PACKAGES: 0

NUMBER OF VALID PACKAGES: 18

NUMBER OF INCONSISTENT PACKAGES: 0

TOTAL NUMBER OF FILES: 1834

NUMBER OF MISSED FILES: 0

NUMBER OF MODIFIED FILES: 0

NUMBER OF FILES WITH MODIFIED PERMISSIONS: 0

former_member229109
Active Contributor
0 Kudos

Hello,

could you please update with ouput of the commands:

dbmcli u2013d MBI u2013n HTC001 u2013u <dbm-user>,<pwd> db_state

dbmcli -d MBI -n HTC001 -tpi MBI -tpc MBI -tpp no_longer_used db_state

Please check the errors in dbmsrv* logs located in <IndepDataPath>/wrk

Please test connection in /nsm59: SAPDB_DBM & SAPDB_DBM_DAEMON, post results.

Test connection in /ndb59, go to /nst11 and check the latest logs for errors.

I recommend you to create the OSS message, so we could check the issue via OSS.

Thank you and best regards, Natalia Khlopina

former_member229109
Active Contributor
0 Kudos

Dear Marc,

1. As SAP customer you have option to create the SAP ticket & get SAP support.

Did you create the SAP ticket on this issue?

2. Itu2019s not clear from your information what error did you get.

a) Run the Test connection in /ndb59 & post the test log.

b) Update with information on the database version & database client version

< run the command u2018sdbregview u2013lu2019 on the database server & the application server>

c) Check the errors in the system log < /nsm21 > & the corresponding dev log of the WP.

Thank you and best regards, Natalia Khlopina

Former Member
0 Kudos

Hi Natalia.

1.

I haven't made a SAP-message, because I want to try to solve it myself first. Possibly I have created the problem myself too.

Besides: it doesn't concern a customer-system but our own training system.

2.

This the log from DB59:

General Connection Data

Connection Name....: MBI

Database Name......: MBI

Database Server....: HTC001

tp Profiles........: no_longer_used

DBM User...........: CONTROL

Test Scope

1. Execute an external operating system command (DBMCLI)

2. Determine status using TCP/IP connection SAPDB_DBM (DBMRFC command mode)

3. Determine status using TCP/IP connection SAPDB_DBM_DAEMON (DBMRFC session mode)

4. Test the SQL connection (Native SQL at CON_NAME)

Application Server: HTC001_MBI_00 ( Windows NT )

1. Connect. test with "dbmcli db_state" Unsuccessful

dbmcli_command_execute_error

Error! Connection failed to node HTC001 for database MBI:

Connection broken to PID 7364 (D)

External program terminated with exit code 2

2. Connect. test with command mode "dbmrfc db_state" Unsuccessful

dbm_system_error

Name and Server : MBI - HTC001

DBMRFC Function : DBM_EXECUTE

Command : db_state

Error : DBM Error

Return Code : -4

Error Message : Connection broken to PID 6360 (D)

3. Connect. test with session mode "dbmrfc db_state" Unsuccessful

dbm_system_error

Name and Server : MBI - HTC001

DBMRFC Function : DBM_CONNECT

Error : DBM Error

Return Code : -4

Error Message : Connection broken to PID 5508 (D)

4. Connect. test with "native SQL" ( MBI ) Successful

sdbregview:

Server Utilities: 7.7.06.16

Base: 7.7.06.16

SAP Utilities: 7.7.06.16

SQLDBC 77: 7.7.06.16

SQLDBC: 7.7.06.16

SQLDBC 76: 7.6.06.06

Database kernel : 7.7.06.16

Loader: 7.7.06.16

SM21:

no error WP's when executing DB50 or DB02

Any suggestions?

Gr.,

Marc.