> -----Original Message-----
> From: Thomas Markus [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 14, 2002 9:54 AM
> To: [EMAIL PROTECTED]
> Subject: Blocking Connections
>
>
> Hi,
>
> I have a strange problem. I use sapdb 7.3.0.21 on linux and
> connect via
> jdbc.
>
> I created a db using create_demo_db.sh.
>
> I repeated following steps some times
> - create a user devel as dba
> - connect via devel and create some tables (about 100)
> with some test
> data (<10000 rows at all)
> - do some selects
> - connect as dba and drop user devel cascade
>
> after some times I can't connect. The program tries to connect and no
> message and no error comes up. I tried to connect with xsql and xload
> with same effect. The only way to kill the client is a hard kill. The
> processes under vserver are still exists. The only way to
> connect is via
> dbmcli with user dbm. I can't drop that user devel.
> Restarting DB has no effect. The only solution is to drop the
> DB and to
> recreate.
>
> Whats my problem?
>
>
I've seen this problem, or what I believe to be this problem, on Win2K systems. I'm not sure if it also applies to Linux et. al. but in my case I found that the autolog setting was important (anyone want to explain why?). Setting autolog to 'on' allowed jdbc connections to be made again. That can be done in the dbmcli as follows. Note that the database must be in a warm state.
$ dbmcli -u dbm,dbm -d DATABASE
dbmcli on DATABASE> db_state
OK
State
WARM
dbmcli on DATABASE> autolog_show
OK
AUTOSAVE IS OFF
dbmcli on DATABASE> autolog_on
OK
dbmcli on DATABASE> autolog_show
OK
AUTOSAVE IS ON
Hope that helps!
ss
