Thanx for helping me Martin, I changed user id in instance init file to root and on command line to dbadmin during instance creation and initialization and it works. I probably miss something, but it never works if users are same at both -command line and ini file (root or dbadmin). both users are in dbadmin group..
Well, this works omehow, but I have another ugly problem - it is very similar to http://lists.mysql.com/maxdb/12693 My carefully prepared long sql script got lost!!! during editing in SQL Studio (under win XP). It is stored to remote linux server (I use file storage - I can find the name of the script in binary file of this storage, but thats all I can do with it). I have no local copy of this script. I did not yet deleted the corrupted file - Is there some way how to reincarnate him? Could this bug be fixed with some patch please? Have a nice weekend, Best Regards, Tom On 9 Mar 2004 at 12:10, Kittel, Martin wrote: > Hi Tom, > > if I remember correctly, then the WebDBM in 7.5.00.08 has a problem when trying to create 7.5.00 database instances because it is still issuing commands for version 7.4.03 (it will send and 'init config' command to the dbmserver which has been removed in 7.5.00). > > If I'm correct, then you could still try to get your database up *after* the error > has occured if you run the commands 'db_activate <dba,dbapwd>' and 'load_systab -ud <domainpwd>' from within dbmcli. > > You could also use the dbmgui to create your instance. It does not suffer from this problem. > > Best wishes, > > Martin. > > > > > -----Original Message----- > > From: Hahn, Uwe > > Sent: Dienstag, 9. M�rz 2004 11:42 > > To: 'Tom Skalik' > > Cc: [EMAIL PROTECTED] > > Subject: RE: MaxDB problem > > > > > > It may be an error in the webdbm but I see in both protocol > > files you sent that there was only one attempt to create an > > instance and this attempt failed. After that only restart > > commands were sent to the database kernel which of course > > fail with the message "ACTIVATE is missing" (knldiag) what > > means that the instance was not correctly created. > > > > It may help you to completely drop the instance and to try > > the installation again with the web dbm or to use the windows > > based dbmgui or one of the various scripts which were posted > > here in the list. > > > > In addition I will show this to the webdbm developer to ask him about. > > Kind regards, > > Uwe > > > > >-----Original Message----- > > >From: Tom Skalik [mailto:[EMAIL PROTECTED] > > >Sent: Tuesday, March 09, 2004 11:29 AM > > >To: Hahn, Uwe > > >Cc: [EMAIL PROTECTED] > > >Subject: RE: MaxDB problem > > > > > >Hi Uwe, > > >yes, I used wrong user id once, but even if I use the correct one, it > > >simply crashes as > > >described below. > > > > > >Kind Regards, Tom > > > > > >On 9 Mar 2004 at 11:24, Hahn, Uwe wrote: > > > > > >> Dbm.utl: > > >> 2004-03-08 15:06:03 404C7DCB0001 0000 IC1 CREATE > > INSTANCE SYSDBA ROOT > > >> 2004-03-08 15:06:08 404C7DCB0001 0001 RET RETURNCODE -7017 > > >> 2004-03-08 15:13:03 404C7F6F0004 0000 VER VERIFY > > >> 2004-03-08 15:13:03 404C7F6F0004 0001 RET RETURNCODE > > 0; 0000000008 > > >PERM PAGES, 0000000000 RELEASED BLOCKS > > >> 2004-03-08 15:18:52 404C80CC0005 0000 RST RESTART > > >> 2004-03-08 15:19:57 404C810D0001 0000 RST RESTART > > >> 2004-03-08 15:20:29 404C812D0001 0000 RST RESTART > > >> [...] > > >> > > >> -7017 means "User not allowed" > > >> So your initialization procedure failed because you > > probably took the > > >same user as > > >your database admin user. If you use a different name for > > creating your > > >instance it will > > >work as specified. > > >> Kind Regards, > > >> Uwe > > >> >-----Original Message----- > > >> >From: Tom Skalik [mailto:[EMAIL PROTECTED] > > >> >Sent: Monday, March 08, 2004 6:47 PM > > >> >To: Hahn, Uwe > > >> >Cc: [EMAIL PROTECTED] > > >> >Subject: RE: MaxDB problem > > >> > > > >> >Hi Uwe, > > >> >here you go > > >> >Kind Regards, Tom > > >> > > > >> > > > >> >On 8 Mar 2004 at 17:26, Hahn, Uwe wrote: > > >> > > > >> >> Tom, could you please send the files dbm.utl and dbm.prt. > > >> >> Kind regards, > > >> >> Uwe > > >> >> > > >> >> >-----Original Message----- > > >> >> >From: Schroeder, Alexander > > >> >> >Sent: Monday, March 08, 2004 4:53 PM > > >> >> >To: 'Tom Skalik' > > >> >> >Cc: [EMAIL PROTECTED] > > >> >> >Subject: RE: MaxDB problem > > >> >> > > > >> >> >Tom Skalik wrote (unfortunately directly, and not in the list): > > >> >> > > > >> >> >> Hi Alexandr, > > >> >> >> I got next troubles with MaXDB under LINUX > > >> >> >> When I try to set DB to online mode via the webdbm tool, it > > >> >> >> ends with error -24895 > > >> >> >> here is corresponding part of the diag file: > > >> >> >> > > >> >> >> > > >> >> >> 2004-03-08 15:30:27 4055 12821 TASKING Thread 4055 starting > > >> >> >> 2004-03-08 15:30:27 4055 11565 startup DEVi started > > >> >> >> 2004-03-08 15:30:27 4047 11000 vattach 'DAT_001' devno 1 T37 > > >> >> >> succeeded > > >> >> >> 2004-03-08 15:30:27 4009 11597 IO Open 'LOG_001' > > >> >successfull, fd: 15 > > >> >> >> 2004-03-08 15:30:27 4056 12821 TASKING Thread 4056 starting > > >> >> >> 2004-03-08 15:30:27 4056 11565 startup DEVi started > > >> >> >> 2004-03-08 15:30:27 4009 11597 IO Open 'LOG_001' > > >> >successfull, fd: 16 > > >> >> >> 2004-03-08 15:30:27 4057 12821 TASKING Thread 4057 starting > > >> >> >> 2004-03-08 15:30:27 4057 11565 startup DEVi started > > >> >> >> 2004-03-08 15:30:27 4047 11000 vattach 'LOG_001' devno 2 T37 > > >> >> >> succeeded > > >> >> >> 2004-03-08 15:30:27 4047 12 Pager Start Read Converter > > >> >> >> 2004-03-08 15:30:27 4047 13 Pager Stop Read Converter, > > >> >Pages: 4 IO: 4 > > >> >> >> 2004-03-08 15:30:27 4047 54003 dynpool > > >> >DATA_CACHE_REGIONS : 8 > > >> >> >> 2004-03-08 15:30:27 4047 54003 dynpool > > >> >B20_DATACACHE_HEAD : 79784 > > >> >> >> 2004-03-08 15:30:27 4047 54003 dynpool DATACACHE head > > >> >num item: 9973 > > >> >> >> 2004-03-08 15:30:27 4047 54003 dynpool DATACACHE head > > >> >item siz: 8 > > >> >> >> 2004-03-08 15:30:27 4047 54003 dynpool DATACACHE task > > >> >queue : 720 > > >> >> >> 2004-03-08 15:30:27 4047 54003 dynpool US + SV + DW + 8 : 45 > > >> >> >> 2004-03-08 15:30:27 4047 54003 dynpool DATACACHE taskq > > >> >elem : 16 > > >> >> >> 2004-03-08 15:30:27 4047 54003 dynpool > > >> >B20_DATACACHE_TASKQ : 80504 > > >> >> >> 2004-03-08 15:30:27 4047 54003 dynDATA > > >> >DATA_CACHE_PAGES : 1247 > > >> >> >> 2004-03-08 15:30:27 4047 54003 dynpool > > >> >B20_DATACACHE_CB : 84796 > > >> >> >> 2004-03-08 15:30:27 4047 54003 dynpool DATACACHE num > > >> >cblocks : 1247 > > >> >> >> 2004-03-08 15:30:27 4047 54003 dynpool DATACACHE cblock > > >> >size : 68 > > >> >> >> 2004-03-08 15:30:27 4047 54003 dynpool > > >> >DYNP_B20_DATACACHE :1322400 > > >> >> >> 2004-03-08 15:30:27 4047 54003 dynDATA > > >> >DYND_B20_DATACACHE : 9976 > > >> >> >> 2004-03-08 15:30:27 4047 53000 B*TREE Restart FileDir > > >> >> >> finished successfully > > >> >> >> 2004-03-08 15:30:27 4047 WNG 17 Admin ACTIVATE is missing > > >> >> >> 2004-03-08 15:30:27 4047 34 Admin Kernel state: 'OFFLINE' > > >> >reached > > >> >> >> 2004-03-08 15:30:27 4047 12696 DBSTATE Change DbState to > > >> >> >> 'SHUTDOWN'(25) ----- ---------------------------------- > > >> >> >> current write position ----------------- > > >> >> >> +++++++++++++++++++++++++++++++++++++++ Kernel Exit > > >> >> >> ++++++++++++++++++++++++++++ 2004-03-08 15:30:28 0 > > >> >12845 > > >> >> >> DBSTATE Kernel exited normal 2004-03-08 15:30:28 0 12808 > > >> >> >> DBSTATE Flushing knltrace pages 2004- 03-08 15:30:28 0 > > >> >11560 > > >> >> >> COMMUNIC Releasing T37 2004-03-08 15:30:28 0 12696 > > >> >DBSTATE > > >> >> >> Change DbState to 'OFFLINE '(29) > > >> >> >> --------------------------------------- current write > > >> >> >> position ----------------- > > >> >> > > > >> >> >Have you made sure that the web tools itself are started in an > > >> >environment > > >> >> >where > > >> >> >the LD_ASSUME_KERNEL environment variable is set? Can the > > >> >database be > > >> >> >started > > >> >> >using the command-line tools? > > >> >> > > > >> >> >Regards > > >> >> >Alexander Schr�der > > >> >> >SAP DB, SAP Labs Berlin > > >> >> > > > >> >> >-- > > >> >> >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] > > >> >> > > >> > > > >> > > > >> >T.Skalik > > >> >KUCERA IPC > > >> >http://www.kuceraipc.de > > >> >+49 69 7171 3580 > > > > > > > > >T.Skalik > > >KUCERA IPC > > >http://www.kuceraipc.de > > >+49 69 7171 3580 > > > > -- > > 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] > T.Skalik KUCERA IPC http://www.kuceraipc.de +49 69 7171 3580 -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
