Hello Ralf,
thank you for your tipps and tricks. After I wrote to the maxdb list I
discovered nearly the same way you described.
First off all, after installing the SAPDB software again with sdbinst I changed the Databases.ini file and add the entries
nessessary for the lost database. After that I was able to do a dbmcli -d TST -u dbm,dbm.
Also my TST database was a copie of a other db. Therefore I copied the parameter file from the source db to my TST database and
changed the parameters that were different from the source db via param directput. Fortunately I only changed to parameters, the
source db was also named TST.
After all I could restart the TST db into the online mode.
Thanks to all of you.
Best Regards
Frank Weise
On Sat, 29 Oct 2005 03:40:07 +0200
"Dr. Ralf Czekalla" <[EMAIL PROTECTED]> wrote:
Frank Weise wrote:
Hello @all
I hope someone can help me.
Folling situation occured:
I have lost all files and directories under /sapdb beside /sapdb/TST/*.
That means I have lost especially /sapdb/programs and /sapdb/data. All
files under /sapdb/TST/* and also all raw devices (logdevspaces and
dataevspaces) for the database TST are in place.
I have no backup of /sapdb/programs and /sapdb/data.
Therefore I installed the same database version via SDBINST. These
recreated all content under /sapdb/programs and /sapdb/data. No I
looking for a way to reregister the database instance TST without losing
the datas in the raw devices. If I would reinitialise the database TST
via DBMGUI I will lost the datas in the raw devices.
Can someone points me in the right direction. Under Oracle I would
reinstall the same software version with the same patchlevel, check the
init<SID>.ora, start the listener and could start up the database.
That's what I'm looking for MAXDB.
Thanks to all
Frank Weise
Hi Frank,
it is possible but you have lost the complete parameter files of that TST instance with loosing the /sapdb/data area. I think,
if you loose similar things with Oracle it is not only done by installing the Oracle software and do some minor tricks :-). Also
there you would need some more informations about the setup of the database instance itself.
Anyways you can reanimate the instance by creating a new parameter file for your instance name. But be carefull to specify
different files/RAW devices as volumes, otherwise the still available volumes would be freshly initialized during that process,
as you already mentioned. You can do so with the DBMGUI and the Instance Wizard there. You can reach him by Instance -> Create.
Finally you should get to a state where this database instance can be started
and stopped with the different, temporary volumes.
Maybe you might think of test this first on another server?
About what database version we are talking?
Then the faking part begins and you have to adapt all the parameters in the parameter file back to the values set up in the lost
parameter file, especcially the volume parameter. You have to know the exact size of the volumes in the RAW devices (the RAW
device size must not fit exactly with the MaxDB volume size) etc. You can do this with the dbmcli (try a param_directgetall first
and you will find all the relevant volume definitions - three for every volume) or the DBMGUI. If you create the volumes some
pages to big, you will later get corrupted pages at the end of the volume because due to the new definition you read outside the
original volume, or you might loose pages there, what it especcially a problem of the log volume as there MaxDB can not compress
the date to the beginning of the volume as with the data volumes. The size information is also located in the config page of each
volume but to get to this info is quite more tricky :-).
Is this enough info for the beginning?
BTW: Set up a backup strategy for the database asap :-)!!!
Greetings
Ralf
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
****************************************************************************
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail ist nicht gestattet.
Über das Internet versandte E-Mails können unter fremden Namen erstellt oder
manipuliert werden. Deshalb ist diese als E-Mail verschickte Nachricht keine
rechtsverbindliche Willenserklärung.
This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
e-mails sent over the internet may have been written under a wrong name or
been manipulated. That is why this message sent as an e-mail is not a
legally binding declaration of intention.
****************************************************************************
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
