Hi John, John Franklin wrote: > > Ralf, > > Thanks a lot. I copied the backup file and was able to restart sapdb. > Any ideas when these .01. .o2 etc files are created. In future when such > things happen is this a guaranteed way to restore the lost parameter file?
maybe the dbmcli command param_restore is the somehow more official way to restore the right parameter file here. But moving back the file from the console it might be more secure because you can directly compare the changing dates there. In the dbmcli you have only the possiblity to restore a parameter file version but couldn't get more information about that version file. As I tried to explain before, during every change of a parameter or even starting a parameter session a new parameter file is created and the current file will be moved to <DB-SID>.01 etc. The current parameters are copied into the new file and if the parameter session is canceled this new file will be deleted everything will be restored again and if it is committed it will stay as the new parameter file. Ciao Ralf > -----Original Message----- > From: Dr. Ralf Czekalla [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 09, 2003 1:40 PM > To: John Franklin > Cc: '[EMAIL PROTECTED]' > Subject: Re: SAPDB recovery after a crash > > Hi John, > > > The /opt where the sapdb is installed ran out of space and the db > > stopped working. I tried different ways to get the sapdb > > back to working state but failed. Any ideas how to recover. > > We are using sapdb 7.3.21 > > > > Here is the error I get. > > > > sapdb/indep_prog/bin>dbmcli -d xxx -u x,y db_start > > > > ERR > > > > -24994,ERR_RTE: runtime environment error > > -11987,Parameter RUNDIRECTORY is missing! > > > > [EMAIL PROTECTED] sapdb/indep_prog/bin>dbmcli -d xxx -u x,y db_state > > OK > > State > > STOPPED INCORRECTLY > > > > [EMAIL PROTECTED] sapdb/indep_prog/bin>dbmcli -d xxx -u x,y db_clear > > OK > > > > The documents say that doing a db_clear should clear all > > the runtime references. But apparently it is not working. > > Let me know how can I get out from this situation. > > That is a knwon problem. When the filesystem with the parameterfiles is > running out of diskspace and you try to change parameters than the > database kernel tries to create a new parameter file. But caused by the > missing disk space only the filename can be created with no parameter in > there. Therefore the error message is understandable as there are really > no parameters in there :-). > > So please have a look for the parameterfile at > <indepdatapath>/config/<DB-SID> (in a SAP R/3 environment it is usually > the file /sapdb/data/config/<SID>) and the older versions of the > parameterfiles marked with a .01, .02, .03 etc. extention. > > Now you have the possibility: > > 1. you can manually move back the right parameterfile to the filename > <DB-SID> (compare the last change date of that files) > > or > > 2. use the official dbmcli command param_restore. > > Ciao Ralf _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
