Daniel,

Unfortunately, I have no such file in that directory. However, I do have that
file in /var/opt/sdb/data/wrk/TST (I'd created that DB by following the example
on in the MaxDB docs earlier, in the hopes that I'd just hosed database creation
and that following instructions would fix the problem).

Given that this file is just a bunch of commands, could I make a copy, change
all instances of the database name, and then run the file with "dbmcli -d MYDB
-u USER,PASS -i dbm.ins"?

In a related question, I've rebooted the box this is on, gone back to my
database, and tried re-running "load_systab", in case that fixed the problem.
The error I'm getting is quite surprising:

-24904,ERR_DOMPWRONG: wrong DOMAIN password

I didn't even realize I'd set up a domain password, and I have no idea what it
might be or how to reset it. Do you have any thoughts on that? Might it just be
simplest for me to completely remove MaxDB and reinstall at this point, so I
have all of this information (it would be no great loss, since I really have no
data in the database at this point).

Thanks,
Alex Kirk


> Hi Alex,
> 
> you're right. The internal server error occurs for the table mentioned
> would have been created by load_systab. 
> You might have a look into the load_systab log file. Go to the run
> directory of your database (might be something like
> /var/opt/sdb/data/wrk/<your db name>). There you find a file named
> dbm.ins. This is the protocol of load_systab. 
> 
> Cheers,
> Daniel
> 
> 
> 
> 
> -----Original Message-----
> From: Alex Kirk [mailto:[EMAIL PROTECTED] 
> Sent: Donnerstag, 28. April 2005 16:17
> To: Kirmse, Daniel
> Cc: [email protected]
> Subject: RE: WebDAV Not Using Provided Password?
> 
> Daniel,
> 
> Well, we've made some significant progress here (and again, thank you
> for
> sticking with me while I fool with this). I created a whole new database
> and ran
> the script suggested on that page; my output was *almost* perfect:
> 
> >param_startsession
> OK
> 
> ---
> >param_init
> OK
> 
> ---
> >param_put MAXUSERTASKS 5
> OK
> 
> ---
> >param_put MAXSERVERTASKS 15
> OK
> 
> ---
> >param_put CACHE_SIZE 3000
> OK
> 
> ---
> >param_put MAXDATAVOLUMES 5
> OK
> 
> ---
> >param_checkall
> OK
> 
> ---
> >param_commitsession
> OK
> 
> ---
> >param_addvolume 1 LOG LOG_001 F 2000
> OK
> 
> ---
> >param_addvolume 1 DATA DAT_001 F 10000
> OK
> 
> ---
> >db_admin
> OK
> 
> ---
> >db_activate DBA,DBA
> OK
> 
> ---
> >load_systab
> ERR
> -24988,ERR_SQL: sql error
> 
> When I tried to connect to that database, just to see if it worked, my
> webdav32.log gave me this message:
> 
> [2005/04/28 05:47:10] GET: Internal server error: [MySQL MaxDB][LIBSQLOD
> SO][MaxDB] Base table not found;-4004 POS(95) Unknown table
> name:WEBDAV_PROPERTY[WDVCAPI_Resource.c: 625]
> 
> Obviously, it can now authenticate, but we've got to figure out what
> this
> load_systab error is, because it's probably quite related to the
> Internal Server
> Error above. I'll be looking through the archives, but if you know it
> off the
> top of your head, I'd appreciate hearing the solution the easy way. :-)
> 
> Alex Kirk
> 
> > Hi Alex,
> > 
> > Here you are! The problem is the creation of your database.
> > Unfortunately db_create is by not all you have to do to get a working
> db
> > instance. Please have a look in here:
> >
> http://dev.mysql.com/doc/maxdb/en/c3/c82a6ba99d11d4aa90006094b92fad/fram
> > eset.htm 
> > There you will find an example for creating a db instance by using the
> > command line tool dbmcli. The user provided with the db_create command
> > is the DBM user. Please notice the db_activate command. The user
> > provided there will be the SYSDBA of your db. Please use that one for
> > the WebDAV session pool.
> > 
> > Cheers,
> > Daniel
> > 
> > -----Original Message-----
> > From: Alex Kirk [mailto:[EMAIL PROTECTED] 
> > Sent: Mittwoch, 27. April 2005 18:12
> > To: Kirmse, Daniel
> > Subject: RE: WebDAV Not Using Provided Password?
> > 
> > Daniel,
> > 
> > I just created a fresh database with dmbcli, called TESTDB, with a
> user
> > of TESTU
> > and a password of TESTP:
> > 
> > ./dbmcli>db_create TESTDB TESTU,TESTP <system user>,<system pass>
> > OK
> > 
> > I was able to log into it no problem with dbmcli. However, when I used
> > those
> > settings for WebDAV, the same old ugly "Could get no connection to
> > database"
> > problem reared its head:
> > 
> > <html><head><meta http-equiv="Content-Type" content="text/html;
> > charset=utf-8"></head><body ><PRE><PLAINTEXT>
> > PRODUCT : MaxDB C-PreComp Runtime
> > VERSION : 7.5.0
> > BUILD   : 016-121-077-688
> > 
> > DATASOURCE:
> > SESSION   : 0;
> > SQLMODE   : INTERN
> > SERVERDB  : TESTDB
> > SERVERNODE: localhost
> > CONNECT "TESTU             " IDENTIFIED BY :A   ISOLATION LEVEL 1
> > SQLCODE:  -709       CONNECT: (database not running: no request pipe)
> > START  :  DATE :  2005-04-27    TIME :  0007:42:06
> > END    :  DATE :  2005-04-27    TIME :  0007:42:06
> > 
> > SQCFINISH
> > 
> > It's almost as is the WebDAV installation is broken, and I need to
> > reinstall.
> > What do you think?
> > 
> > Alex Kirk
> > 
> > > Hi Alex,
> > > 
> > > How did you create your database? Webdbm? You could try DBA/DBA or
> > > SYSDBA/secret as these are commonly known defaults for the SYSDBA
> > user.
> > > Usually this is one step in the create database wizard.
> > > 
> > > Cheers,
> > > Daniel
> > > 
> > > -----Original Message-----
> > > From: Alex Kirk [mailto:[EMAIL PROTECTED] 
> > > Sent: Mittwoch, 27. April 2005 17:36
> > > To: Kirmse, Daniel
> > > Cc: [email protected]
> > > Subject: RE: WebDAV Not Using Provided Password?
> > > 
> > > > One more detail: The Password is Opensnort containing an uppercase
> O
> > > and
> > > > some lowercase characters. Is this significant? If yes you would
> > have
> > > to
> > > > enclose the password with double quotes. You could check this with
> > > > websql for websql and webdav session pool use the same mechanism.
> > What
> > > > is working with websql must work with webdav as well.
> > > 
> > > It's just a standard password I use for things I don't need to worry
> > > about
> > > security-wise. I tried enclosing it in double quotes within the
> admin
> > > interface,
> > > and when I return to the page to make sure the change took, the
> > password
> > > has
> > > vanished. So that's not an option.
> > > 
> > > Interestingly enough, when I chose WebDAV as the session pool for
> > websql
> > > (with
> > > an Update followed by a Reload Service, which I confirmed in
> > > websql32.log) and
> > > then tried to log into websql, it took me to a login page; when I
> > > entered my
> > > database login info there, I got a nice "Page Cannot Be Displayed"
> > > error. 
> > > 
> > > > But by the way: Come to think of it. After installation the WebDAV
> > > > tables are only accessible for the SYSDBA user, so you should use
> > this
> > > > user in your session pool anyway. So I suggest we try login on
> with
> > > that
> > > > one to ensure that WebDAV is in working order (in principle).
> > > 
> > > Certainly a solid idea. The only issue there is that I have no
> > > recollection of
> > > ever setting the SYSDBA password, and I don't know the default
> > > (SYSDBA?). That, and:
> > > 
> > > <html><head><meta http-equiv="Content-Type" content="text/html;
> > > charset=utf-8"></head><body ><PRE><PLAINTEXT>
> > > PRODUCT : MaxDB C-PreComp Runtime
> > > VERSION : 7.5.0
> > > BUILD   : 016-121-077-688
> > > 
> > > DATASOURCE: OWNME
> > > SESSION   : 1;
> > > SQLMODE   : INTERN
> > > SERVERDB  : OWNME
> > > SERVERNODE: localhost
> > > CONNECT "SYSDBA            " IDENTIFIED BY :A   ISOLATION LEVEL 1
> > > SQLCODE:  -4008      Unknown user name/password combination
> > > SQLERRD(INDEX_5) : 1         SEC. FOR STATEMENT
> > > START  :  DATE :  2005-04-27    TIME :  0007:04:49
> > > END    :  DATE :  2005-04-27    TIME :  0007:04:50
> > > 
> > > SQCFINISH
> > > 
> > > Does that lead you anywhere?
> > > 
> > > Alex Kirk
> > > 
> > 
> > 
> > 
> 
> 
> 



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

Reply via email to