Ups - I missed to put this information in the mail.

The filesystem-layout is

[EMAIL PROTECTED]:~> df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             487M  166M  296M  36% /
/dev/dws10vg/optlv    496M  165M  306M  36% /opt
/dev/dws10vg/tmplv    496M  185M  286M  40% /tmp
/dev/dws10vg/usrlv   1008M  234M  724M  25% /usr
/dev/dws10vg/varlv    2.0G  769M  1.2G  41% /var
/dev/dws10vg/sagvarlv
                      9.9G  1.6G  8.4G  16% /var/opt/sag
shmfs                1010M     0 1010M   0% /dev/shm

So only /var/spool/sql was affected by the no-space-left-on-device on /var.


Bye
Chris

>-----Original Message-----
>From: JUNG, Christian 
>Sent: Thursday, March 30, 2006 2:35 PM
>To: MaxDB Mailinglist (E-Mail)
>Subject: SAPDB 7.4 dbmcli sql_connect failed
>
>
>Hi!
>
>Last evening the /var-partition filled up on one of our 
>DB-server because of
>a wild-running application. Now I've got a problem with dbmcli:
>
>    ---8<---
>    [EMAIL PROTECTED]:~> dbmcli -d SAG -u SAGDBA,******** -uSQL -c quit
>    ERR
>    -24988,ERR_SQL: sql error
>    -4008,Unknown user name/password combination
>    [EMAIL PROTECTED]:~>
>    ---8<---
>
>But if I use xsql for example, it works:
>
>    ---8<---
>    [EMAIL PROTECTED]:~> xsql -d SAG -u SAGDBA,********
>    > exit
>    [EMAIL PROTECTED]:~> 
>    ---8<---
>
>knldiag.err:
>    ---8<---
>    2006-03-23 13:24:35  9824 ERR 51080 SYSERROR -9404 AK System error:
>VAK660 1
>    2006-03-26 03:07:50                          --- Starting 
>GMT 2006-03-26
>01:07:50           7.4.3    Build 027-121-048-452 
>    2006-03-28 15:24:43 32307 ERR 51080 SYSERROR -9404 AK System error:
>VAK660 1
>    2006-03-30 11:16:04                          --- Starting 
>GMT 2006-03-30
>09:16:04           7.4.3    Build 027-121-048-452 
>    ---8<---
>
>I suppose, that these entries don't correlate with my 
>sql_connect problem,
>because they aren't at the same time as my login-attempts and 
>I've made a
>lot of more login attempts... :-)
>
>knldiag: nothing to mention
>
>I restarted the instance and called "x_server update". But the problem
>persists. What can I do?
>
>It's a SAP DB 7.4.3.27 running on Linux (Kernel Version 
>2.4.21/SMP). The
>database is namely used by Java-apps and seems to work fine 
>(no problem to
>get on the database and work with it). 
>
>
>Thanks + Bye
>Chris
>
>
>phone: +49 6898/10-4987
>fax: +49 6898/10-54987
>http://www.saarstahl.de
>
>-- 
>MaxDB Discussion Mailing List
>For list archives: http://lists.mysql.com/maxdb
>To unsubscribe:    
http://lists.mysql.com/[EMAIL PROTECTED]

-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to