"-4 wrong connection state" error in database manager

[john_lewis5]

After adding new data volumes via the windows database manager (7.6.02.10), we get the popup error "-4 wrong connection state" when trying to display/change volume information, change parameters, and many other things. I've tried using dbmcli to do a param_getdevsall, and that also also returns the -4... error. Has anyone else seen this, or have any ideas on how to correct it? We're having this issue in an SCM/APO 4.1 system on a PA-RISC UNIX server, and the db release is 7.5.00.29. At this point, we can't add any new data volumes, or even compare the data volumes (for count and size) between our QA and PROD systems.

Thanks,

John

[former_member229109 · Accepted solution]

Hello John,

-> Did you already created the SAP OSS message on this issue?

Please read this thread: MaxDB/liveCache Forum: target audience and relevant support.

< >

-> Please update with additional information:

• How did you add the datavolume?

Was at that time the database online?

• Please update with the output of the following commands, run them as user in the sdba group:

xinstinfo <SID>

dbmcli -d <SID> -u <dbm-user>,<pwd> db_state

dbmcli -d <SID> -u <dbm-user>,<pwd> db_clear

dbmcli -d <SID> -u <dbm-user>,<pwd> param_getdevsall

uname -a

dbmcli inst_enum

dbmcli db_enum

sdbregview -l

ls -l /sapdb/data/config

-> Please run as root user:

cd /sapdb/programs/bin

./sdbverify > check_software_install.txt

review check_software_install.txt & let me know the results.

Thank you and best regards, Natalia Khlopina

[john_lewis5 · Accepted solution]

Natalia,

Thanks for the quick reply. Yes, we have an open OSS problem on this, I thought we might get more feedback via SDN. I was using the Windows Database Manager when I was adding the data volumes, and everything worked fine right up until I got the popup with the error. The last data volume I added did appear to get added (at least at the UNIX level). The database was up - we've never had any issues adding data volumes with the system up. Here is the output from the command you've asked for: (The db is only in admin mode because the system is down for other reasons currently.)

devg0d60:apqadm 17> xinstinfo

IndepData : /sapdb/data

IndepPrograms : /sapdb/programs

devg0d60:apqadm 18> dbmcli -d APQ –u user,pw db_state

OK

State

ADMIN

devg0d60:apqadm 19> dbmcli -d APQ -u user,pw db_clear

OK

devg0d60:apqadm 20> dbmcli -d APQ -u user,pw param_getdevsall

DBM-Api error ( -4'Reading header from pipe:(0:NO ERROR(0))')

devg0d60:apqadm 21> uname -a

HP-UX devg0d60 B.11.11 U 9000/800 1500384883 unlimited-user license

devg0d60:apqadm 22> dbmcli inst_enum

OK

7.5.0.29 /sapdb/APQ/db

7.5.0.27 /sapdb/LCA/db

devg0d60:apqadm 24> dbmcli db_enum

OK

APQ /sapdb/APQ/db 7.5.0.29 fast running

APQ /sapdb/APQ/db 7.5.0.29 quick offline

APQ /sapdb/APQ/db 7.5.0.29 slow offline

LCA /sapdb/LCA/db 7.5.0.27 fast offline

LCA /sapdb/LCA/db 7.5.0.27 quick offline

LCA /sapdb/LCA/db 7.5.0.27 slow offline

devg0d60:apqadm 25> sdbregview -l

PCR 7301 /sapdb/programs 7.3.01.18 valid

PCR 7401 /sapdb/programs 7.4.01.18 valid

PCR 7500 /sapdb/programs 7.5.00.29 64 bit valid

PCR 7240 /sapdb/programs 7.2.04.17 valid

PCR 7402 /sapdb/programs 7.4.02.21 64 bit valid

Server Utilities /sapdb/programs 7.5.00.29 64 bit valid

PCR 7250 /sapdb/programs 7.2.05.24 valid

JDBC /sapdb/programs 7.6.00.00 valid

PCR 7403 /sapdb/programs 7.4.03.39 64 bit valid

Database Kernel /sapdb/LCA/db 7.5.00.27 64 bit valid

Database Kernel /sapdb/APQ/db 7.5.00.29 64 bit valid

Loader /sapdb/programs 7.5.00.29 64 bit valid

ODBC /sapdb/programs 7.5.00.29 64 bit valid

Base /sapdb/programs 7.5.00.29 64 bit valid

DB Analyzer /sapdb/programs 7.5.00.29 64 bit valid

PCR 7300 /sapdb/programs 7.3.00.53 valid

APO LC APPS /sapdb/LCA/db/sap 4.10.008 64 bit valid

devg0d60:apqadm 27> ls -l /sapdb/data/config

total 1158

-rw-rw---- 1 sdb sdba 31218 Feb 4 23:47 APQ

-rr--- 1 sdb sdba 31218 Feb 1 22:27 APQ.01

-rw-rw---- 1 sdb sdba 4970 Feb 4 23:48 APQ.cfg

-rw-rw---- 1 sdb sdba 930 Jan 10 20:09 APQ.mmm

-rw-rw---- 1 sdb sdba 297220 Dec 21 17:18 APQ.pah

-rw-rw---- 1 sdb sdba 3072 Oct 5 2005 APQ.upc

-rw-rw---- 1 sdb sdba 94 Oct 11 2005 Databases.ini

-rrr-- 1 sdb sdba 90 Oct 11 2005 Installations.ini

-rw-rw---- 1 sdb sdba 16598 Feb 2 02:20 LCA

-rr--- 1 sdb sdba 16598 Dec 21 17:23 LCA.01

-rr--- 1 sdb sdba 16598 Aug 24 14:32 LCA.02

-rr--- 1 sdb sdba 16598 Oct 17 2005 LCA.03

-rr--- 1 sdb sdba 16598 Oct 11 2005 LCA.04

-rw-rw---- 1 sdb sdba 16598 Oct 11 2005 LCA.05

-rw-rw---- 1 sdb sdba 5110 Feb 2 02:20 LCA.cfg

-rw-rw---- 1 sdb sdba 740 Jan 10 23:07 LCA.mmm

-rw-rw---- 1 sdb sdba 91868 Dec 21 17:22 LCA.pah

-rw-rw---- 1 sdb sdba 3072 Jan 27 00:31 LCA.upc

-rwxrwxr-x 1 sdb sapsys 756 Oct 5 2005 Registry1.dcom

-rwxrwxr-x 1 sdb sapsys 2636 Oct 11 2005 Registry2.dcom

-rrr-- 1 sdb sdba 48 Oct 5 2005 Runtimes.ini

drwxrwxr-x 2 apqadm sapsys 1024 Oct 11 2005 install

devg0d60:apqadm 28>

check_software_install.txt extracts

Here are the possible problems;

PCR 7240 7.2.04.17 in /sapdb/programs

-

---

check files... failed

owner of /sapdb/programs/runtime/7240/lib/lib64/libpcr.sl was modified

group of /sapdb/programs/runtime/7240/lib/lib64/libpcr.sl was modified

owner of /sapdb/programs/runtime/7240/lib/libpcr.sl was modified

group of /sapdb/programs/runtime/7240/lib/libpcr.sl was modified

check dependencies... ok

package data is inconsistent

PCR 7250 7.2.05.24 in /sapdb/programs

-

---

check files... failed

owner of /sapdb/programs/runtime/7250/lib/libpcr.sl was modified

group of /sapdb/programs/runtime/7250/lib/libpcr.sl was modified

owner of /sapdb/programs/runtime/7250/lib/lib64/libpcr.sl was modified

group of /sapdb/programs/runtime/7250/lib/lib64/libpcr.sl was modified

check dependencies... ok

package data is inconsistent

Database Kernel 7.5.00.29 64 bit in /sapdb/APQ/db

-

---

check files... failed

mode of /sapdb/APQ/db/pgm/lserver was modified

check dependencies... ok

check rte registration of package... ok

package data is inconsistent

VERIFICATION SUMMARY:

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

INVALID PACKAGES: 0

VALID PACKAGES: 17

INCONSISTENT PACKAGES: 3

TOTAL FILES: 488

MISSED FILES: 0

MODIFIED FILES: 0

FILES WITH MODIFIED PERMISSIONS: 5

I hope helps, and let me know if you any further information.

John

[former_member229109 · Accepted solution]

Hello John,

-> Thank you for the update.

• I asked that if the database was online, when you added the database volumes

to see if the datavolumes were created at the UNIX level by database kernel and NOT

changed only at the configuration param file. As you confirmed:

"The last data volume I added did appear to get added (at least at the UNIX level)."

• Did you run "dbmcli db_enum" before you run 'db_clear' command?

Did you restart the database in devg0d60:apqadm 23> ? Command ?

• Please update with output of the following commands::

ls -l /sapdb/APQ/db/pgm

dbmcli -d APQ –u user,pw db_state

dbmcli -d APQ –u user,pw db_offline

dbmcli -d APQ –u user,pw db_state

dbmcli db_enum

dbmcli -d APQ –u user,pw param_directget INSTANCE_TYPE

dbmcli -d APQ –u user,pw param_directget VOLUMENO_BIT_COUNT

dbmcli -d APQ –u user,pw param_directget MAXDATAVOLUMES

dbmcli -d APQ –u user,pw user_getall

dbmcli -d APQ –u user,pw user_get user

id

xinstinfo APQ

ps -efe | grep sdb

-> You could run dbm command:

param_getexplain MAXDATAVOLUMES

"Maximum number of data volumes

Allow for a reserve number of volumes which enables you to add

volumes during database operation.

The lower and upper limits are:

1 <= MAXDATAVOLUMES < POWER( 2, VOLUMENO_BIT_COUNT )"

&& run "param_getexplain VOLUMENO_BIT_COUNT" to get further details.

< Please review the values of the database parameters in the knldiag, knldiag.old files >

Thank you and best regards, Natalia Khlopina

Edited by: Natalia Khlopina on Feb 4, 2008 7:17 PM

[john_lewis5 · Accepted solution]

Natalia,

Sorry I missed your reply last night. The OSS ticket is #13633. I have tried stopping and restarting the database, and the problem still exists. I believe I've used both dbmcli and WDM to stop/start the db. Here is the information you've requested:

devg0d60:apqadm 1> ls -l /sapdb/APQ/db/pgm

total 180412

-r-xr-x--- 1 sdb sdba 1307624 Jun 13 2005 backup

-r-xr-x--- 1 sdb sdba 1402184 Jun 13 2005 cons

-r-xr-x--- 1 sdb sdba 1979896 Jun 13 2005 dbmext

-r-sr-s--x 1 sdb sdba 4746768 Jun 13 2005 dbmsrv

-r-xr-x--- 1 sdb sdba 4515880 Jun 13 2005 dbmstart

-r-xr-x--- 1 sdb sdba 4515808 Jun 13 2005 dbmstop

-r-sr-x--- 1 root sdba 1148768 Jun 13 2005 dbmverifypw

-r-xr-x--- 1 sdb sdba 2546776 Jun 13 2005 diagnose

-r-xr-x--- 1 sdb sdba 15640072 Jun 13 2005 kernel

-r-sr-x--- 1 sdb sdba 6548664 Jun 13 2005 lserver

-r-xr-x--- 1 sdb sdba 1445592 Jun 13 2005 pu

-r-xr-x--- 1 sdb sdba 950272 Jun 13 2005 python

-r-xr-x--- 1 sdb sdba 17958968 Jun 13 2005 quickknl

-r-xr-x--- 1 sdb sdba 23443624 Jun 13 2005 slowknl

-r-xr-x--- 1 sdb sdba 1465488 Jun 13 2005 sqlfilter

-r-xr-x--- 1 sdb sdba 1319848 Jun 13 2005 start

dr-x------ 2 sdb sdba 96 Oct 5 2005 starter

-r-xr-x--- 1 sdb sdba 1315688 Jun 13 2005 stop

-r-xr-x--- 1 sdb sdba 37872 Jun 13 2005 sysrc

-r-xr-x--- 1 sdb sdba 72288 Jun 13 2005 tracesort

devg0d60:apqadm 2> dbmcli -d APQ -u control,control db_state

OK

State

OFFLINE

devg0d60:apqadm 3> dbmcli -d APQ -u control,control db_offline

OK

devg0d60:apqadm 5> dbmcli -d APQ -u control,control db_state

OK

State

OFFLINE

devg0d60:apqadm 6> dbmcli db_enum

OK

APQ /sapdb/APQ/db 7.5.0.29 fast offline

APQ /sapdb/APQ/db 7.5.0.29 quick offline

APQ /sapdb/APQ/db 7.5.0.29 slow offline

LCA /sapdb/LCA/db 7.5.0.27 fast offline

LCA /sapdb/LCA/db 7.5.0.27 quick offline

LCA /sapdb/LCA/db 7.5.0.27 slow offline

devg0d60:apqadm 7> dbmcli -d APQ -u control,control param_directget instance_type

OK

INSTANCE_TYPE OLTP

devg0d60:apqadm 8> dbmcli -d APQ -u control,control param_directget volumeno_bit_count

OK

VOLUMENO_BIT_COUNT 8

devg0d60:apqadm 9> dbmcli -d APQ -u control,control param_directget maxdatavolumes

OK

MAXDATAVOLUMES 255

devg0d60:apqadm 10> dbmcli -d APQ -u control,control user_getall

OK

CONTROL

SUPERDBA

Domain

devg0d60:apqadm 11> dbmcli -d APQ -u control,control user_get userid

ERR

-24951,ERR_USRREAD: could not read user data

devg0d60:apqadm 13> xinstinfo APQ

IndepData : /sapdb/data

IndepPrograms : /sapdb/programs

InstallationPath : /sapdb/APQ/db

Kernelversion : KERNEL 7.5.0 BUILD 029-121-099-958

Rundirectory : /sapdb/data/wrk/APQ

devg0d60:apqadm 14> ps -efe | grep sdb

sdb 29708 1 0 23:03:13 ? 0:00 /sapdb/programs/pgm/vserver -sdbstarter 2906 201 A start

sdb 29701 1 0 23:03:12 ? 0:00 /sapdb/programs/pgm/niserver

sdb 29713 29708 0 23:03:13 ? 0:00 /sapdb/programs/pgm/vserver -sdbstarter 2906 201 A start

devg0d60:apqadm 15>

If I've done my math correctly, we should be ok for up to 255 data volumes, based on the mxdatavolumes and the volumeno_bit_count parameters.

Here are some of the lines from knldiag that show the last few data volumes:

2008-02-04 23:47:49 1 226 RTE DATA_VOLUME_NAME_0215=/sapdb/APQ/data23/DISKD0215

2008-02-04 23:47:49 1 226 RTE DATA_VOLUME_TYPE_0215=F

2008-02-04 23:47:49 1 226 RTE DATA_VOLUME_SIZE_0215=256000

2008-02-04 23:47:49 1 226 RTE DATA_VOLUME_MODE_0215=NORMAL

2008-02-04 23:47:49 1 195 RTE Using mode NORMAL for data volume 215

2008-02-04 23:47:49 1 226 RTE DATA_VOLUME_NAME_0216=/sapdb/APQ/data24/DISKD0216

2008-02-04 23:47:49 1 226 RTE DATA_VOLUME_TYPE_0216=F

2008-02-04 23:47:49 1 226 RTE DATA_VOLUME_SIZE_0216=256000

2008-02-04 23:47:49 1 226 RTE DATA_VOLUME_MODE_0216=NORMAL

2008-02-04 23:47:49 1 195 RTE Using mode NORMAL for data volume 216

2008-02-04 23:47:49 1 226 RTE DATA_VOLUME_NAME_0217=/sapdb/APQ/data23/DISKD0217

2008-02-04 23:47:49 1 226 RTE DATA_VOLUME_TYPE_0217=F

2008-02-04 23:47:49 1 226 RTE DATA_VOLUME_SIZE_0217=256000

2008-02-04 23:47:49 1 226 RTE DATA_VOLUME_MODE_0217=NORMAL

2008-02-04 23:47:49 1 195 RTE Using mode NORMAL for data volume 217

I took a look at the whole file, and I don't see any msgs that indicate an error.

Thanks again,

John

[former_member229109 · Accepted solution]

Hello John,

As this issue already reported in the SAP OSS ticket is #13633, please follow

the OSS message to resolve this issue.

Please read this thread: MaxDB/liveCache Forum: target audience and relevant support.

< >

Thank you and best regards, Natalia Khlopina