Hmmm... not very much help, but at least i can identify the error message
you got.

> -----Original Message-----
> From: Christoph Langguth [mailto:[EMAIL PROTECTED]]
> Sent: Donnerstag, 14. Februar 2002 13:40
> To: [EMAIL PROTECTED]
> Subject: 11608 wrong connection state ?
> 
> 
> Hello all,
> 
> I'm trying to set up the sapdb on my server (SuSE Linux 7.0);
> I have already had it running, and then I decided to try and 
> delete the TST database and set up a real one.
> Something must have gone terribly wrong then, because I kept 
> on getting the same error. As a last resort, I tried 
> completely uninstalling all rpms, rebooting and reinstalling. 
> But still, the create_demo_db script fails all the time. I've 
> tracked the problem a bit by manually executing the 
> statements, and found it to be the "quit" command in dbmcli 
> that causes the error. Even the "minimal" command, which 
> doesn't actually do anything, fails:
> 
> sapdb@bender:/opt/sapdb/testdb > ../indep_prog/bin/dbmcli
> ./indep_prog/bin/dbmcli>quit
> 
> ---
> 2002-02-14 13:27:04  3864 ERR -11608 COMMUNIC sql03_request: 
> wrong connection state, state is 'requested'

This is an error message issued, if a sqlarequest() is called for a
connection that is already busy with a request.
SAPDB can only work one request at a time on a given connection. The '3864'
is the process id of the client 
process the issued the sqlarequest() call.

> 
> sapdb@bender:/opt/sapdb/testdb >
> 
> I have tried all possible configurations, as root, as user 
> sapdb, with and without the environment variables set etc...
> I have also tried to find something in the online 
> documentation, but this is rather difficult - I didn't find 
> anything useful.
> 
> So, please, is there anybody who knows what is going on and 
> who can point me in some direction?
> What the heck could cause this?
> 
> Any help is much appreciated!
> 
> Thanks,
> 
> Christoph

Your welcomne
jrg
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to