No replies yet. Follow up...
I found another way to get sapdb to tell me status of the database storage,
I wish I had been using this command all along!
=========== output ===================
F:\>dbmcli -d ESNIPE -u dbm,dbm -uSQL -c info state
OK
END
Name | Value
Data (KB) = 3558408
Perm Data (KB) = 3038424
Temp Data (KB) = 519984
Data (Pages) = 444800
Perm Data (Pages) = 379803
Temp Data (Pages) = 64998
Data (%) = 100
Perm Data (%) = 85
Temp Data (%) = 15
Log (KB) = 139248
Log (Pages) = 17406
Log (%) = 13
Sessions = 3
Sessions (%) = 6
Data Cache (%) = 100
Converter Cache (%) = 100
Data Max (KB) = 3558400
Log Max (KB) = 1039976
Data Max (Pages) = 444800
Log Max (Pages) = 129997
Sessions Max = 50
Database Full = Yes
Connect Possible = Yes
Command Monitoring = Off
Database Monitoring = On
Kernel Trace = Off
Autosave = On
Bad Indexes = 0
Bad Devspaces = 0
====================================================
Ok, here it is clear that "Database Full = Yes".
How do I dump the 15% "Temp Space"? I did a full backup, and it did not
free up. I have rebooted the server, still didn't free it. It isn't like I
have a transaction going!
OBSERVATIONS
-=-=-=-=-=-=-=
1) The output of "info devspaces" shows the number 64997 as "Free Space
(KB)" - but the command "info state" shows the number 64998 as "Temp Data
(Pages)" - is the "info devspaces" output MIXING UP the terms PAGES and
KILOBYTES? I have asked why these numbers don't make sense in the past...
2) If the state is "Database Full = Yes" why does the ODBC 7.3 driver
just HANG the calling application, shouldn't it return a error! The
versions of my products are listed below.
If anyone can help me ASAP - I need to dump that 15% Temp Space, please
write. One of my servers is down! Thank you.
Stephen Gutknecht
-----Original Message-----
From: Stephen Gutknecht (SAPDB)
Sent: Monday, January 28, 2002 11:13 AM
To: [EMAIL PROTECTED]
Subject: sapdb 7.3 Stalls on record insert, can not find cause - HELP!
We just encountered another production problem. I took the problem server
out of production to try and figure out what is going on.
I am running Windows 2000 Server - Service Pack 2, SAPDB ODBC driver
7.03.00.00, KERNEL 7.3.0 BUILD 015-000-070-423. Autocommit is on (all my
insert transactions are very simple for this application).
I can do SELECT against the database without problem, but any attempt to
INSERT just stalls (ODBC call never comes back). I encountered this problem
once months ago when the sapdb storage was full, but based on my study -
things this database is not full.
I did a backup and tried to do another insert again, same results. Here is
some info on the storage:
==================== vital space info ==============
F:\>dbmcli -n localhost -d prod -u dbm,dbm -uSQL prodall,**** info devspaces
OK
END
Type | Internal ID | Name
| Size (KB) | Mirrored
SYS | 1 | f:\sapdb-data\data\prod\DISKSYS01
| 8928 | No
DATA | 1 | f:\sapdb-data\data\prod\DISKDATA0001
| 3558400 | No
LOG | 1 | f:\sapdb-data\log\prod\DISKLOG001
| 1040000 | No
F:\>dbmcli -n localhost -d prod -u dbm,dbm -uSQL prodall,**** info data
OK
END
Name | Value
Devspace Name = f:\sapdb-data\data\prod\DISKDATA0001
Total Space (KB) = 3558400
Max. Perm. Space (KB) = 3038412
Used Space (KB) = 379803
Used Space (%) = 85
Free Space (KB) = 64997
Free Space (%) = 15
Updated Permanent Pages =
F:\>dbmcli -n localhost -d prod -u dbm,dbm -uSQL prodall,**** info log
OK
END
Name | Value
Log Mode = SINGLE
Max. Size (KB) = 1039976
Backup Segment Size (KB) = 0
Used Size (KB) = 139640
Used Size (%) = 13
Not Saved (KB) = 139200
Not Saved (%) = 13
Log Since Last Data Backup (KB) = 0
Savepoints = 11487
Checkpoints = 21
Physical Reads = 0
Physical Writes = 6
Queue Size (KB) = 400
Queue Overflows = 0
Group Commits = 0
Waits for Logwriter = 4
Max. Waits = 1
Average Waits = 1
========== end vital space info ===========
This is one of our lower-use backup severs, we normally don't have data and
log on the same disk. The F: partition has over 2.5GB free.
thank you.
Stephen Gutknecht
p.s. sapdb has not been very reliable for us lately. The -904 bug
discussed on this list has been hitting us too, we also have other leaks
(-907 after running for more than a week). I would like to turn the
situation around!
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
