From: Resi W [mailto:[EMAIL PROTECTED] Subject: Database crashed and couldn't be restarted.
> To resolve this, I tried to add new devspaces since we can > still do that in admin mode. > But when I tried that it refused and gave this error msg : > > " You can not add devspaces now, the parameter file is changed. > Stop and then restart the database to get the new parameters active. " > > After I investigated, I learned that my co-worker has > attempted to change a few of the parameters (after the crash). > > Now I am facing some sort of a deadlock - The server can't be > restarted due to disk full, and I can't add new devspaces > because the parameter has been changed, thus the database > instance needs to be restarted (which I can't do) before I > can add devspaces. Hi Resi, you can restore the "last known good" version of the parameter file with the command "param_restore 1". Execute this command at the command line (with dbmcli or Instance->Command Line in the DBMGui). After this try again to add the devspace. If this doesnt work, we need the command line again in mode admin: util_execute ADD DATA DEVSPACE '<name>' PAGES <numofpages> DEVICE <devspacenumber> param_adddevspace <devspacenumber> DATA <name> <type> <numofpages> <name> is the name of the file or raw device <numofpages> size of the device in pages (8 KB) <devspacenumber> number of the new devspace (existing + 1) <type> type of new devspace F for file, R for raw device I hope this helps. Bernd -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
