AW: ODBC-Call for <DB-Name> failed

"Hübschen, Peter" <[email protected]>
Newsgroups gmane.comp.db.sapdb.general
Message-ID <5037282E0DC5D711974C00304852417A025E5F@SERVER-XCH>
Hello, 

the option MAXUSERTASKS I found myself and it's from the beginning set to an
appropriate value. This exclusive option was probably something that I have
missed to read.

Thanks
Peter
> -----Ursprüngliche Nachricht-----
> Von:	Schroeder, Alexander [SMTP:[email protected]]
> Gesendet am:	Dienstag, 19. August 2003 08:33
> An:	Hübschen, Peter; Mailingliste SAPDB (E-Mail)
> Betreff:	RE: ODBC-Call for <DB-Name> failed
> 
> Hello Peter,
> 
> There are two kinds of limits that may apply.
> 
> First, make sure that the user is NOT EXCLUSIVE. 
> (see
> http://www.sapdb.org/7.4/htmhelp/48/f0daa5225811d3a97d00a0c9449261/content
> .htm )
> Users are created by default in EXCLUSIVE mode, if nothing else is
> specified.
> If your user seems, to be EXCLUSIVE, use
>   
>    ALTER USER username NOT EXCLUSIVE
> 
> to lift that restriction.
> 
> Second (not very probable in this case) there is a database parameter
> MAXUSERTASKS
> that defines the maximum number of parallel sessions that the database
> will handle.
> 
> Regards
> 
> Alexander Schröder
> SAP DB, SAP Labs Berlin 
> 
> > -----Original Message-----
> > From: "Hübschen, Peter" [mailto:[email protected]]
> > Sent: Tuesday, August 19, 2003 8:10 AM
> > To: Mailingliste SAPDB (E-Mail)
> > Subject: ODBC-Call for <DB-Name> failed
> > 
> > 
> > Hello all, 
> > 
> > is there any limitation how many simultanous sessions a 
> > single user can open
> > and how can I change this (I didn't find a possibility to change)?
> > 
> > I'm asking this, because I've been run into the same error a 
> > lot of times in
> > different circumstances. I'm using Access 97 as frontend and 
> > if I open for
> > example two objects (one connection and one database object) 
> > I get the error
> > 'the ODBC-Call for <MyDB> failed'. I'm also running into the 
> > same problem if
> > I open a bound form (the tables are linked) which has one/some unbound
> > combo-boxe(s) which are filled through SQL-statements. Or I 
> > have open a
> > bound form and I try to open a linked table. Or if I tried to export 2
> > Access tables to SAP-DB it always failed on the second table. 
> > I had to close
> > and reopen my database for every table I wanted to export.
> > I forgot to mention, before I get the ODBC-Call error, the 
> > ODBC-driver Input
> > form pops up. 
> > 
> > I think it's SAPDB related, since I can't open a 
> > SQL-Studio-Session, if I
> > have Access open and the tables linked.
> > 
> > Regards
> > Peter
> > 
> > _______________________________________________
> > sapdb.general mailing list
> > [email protected]
> > http://listserv.sap.com/mailman/listinfo/sapdb.general
> > 
> 
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.