upgrading MaxDB 73 to 76

[Former Member]

Dear Forum,

We should upgrade a MaxDB version 7.3.0 Build 035-000-090-084 database to MaxDB version 7.6.

This database holds 3 instances: SDB, QAS and DEV and it are ContentServer installations.

Unfortunately two of these installations: SDB and QAS share the same Installation path: c:\sapdb\SDB\db, although the system shows that the c:\sapdb\QAS\db directory exists as well.

I have read in the upgrade guide that instances shouldn't share the installation path, otherwise the upgrade, using SDBUPD, can't be done.

On the other hand there is still a option for migration of the instance using SDBINST, but the guide ( migration73_74eng.pdf) lists as prereq. that the installation shouldn't be a SAP installation.

I have read several documents, notes etc. but I can't find a conclusive solution.

Can someone shed some light on this?

I s f.i. dbmrelocate a solution for this?

best regards,

Louis Cladder

Edited by: L. Cladder on Dec 4, 2010 5:56 PM

[Former Member · Accepted solution]

Hello,

what I would do in this case:

A)

1) create offlie backup of QAS instance

2) create new instance QA1 for software installation c:\sapdb\QAS\db and restore QA1 intance from QAS backup

3) change in your r/3 sustem (QA) configuarion so it points to QA1 instance instead og QAS

4) thet/test/test , if you are happy with this change and QA1 instance works fine with CS , you can drop QAS instance

-

---

you can do this whole procedure by droppping QAS just after the backup and creating new QAS instance using sapdb\QAS\db , in this case you will end up with QAS instance directly ,

1) backup of QAS ,

2) drop of QAS

3) create new QAS with restore from backup

B)

thereis one better , more elegant solution

you can use command

dbmcli -s -d QAS -u <dbm_user>,<password> db_drop WITHOUTFILES

and

register QAS with sapdb/QAS/db software

dbmcli -s -R <drive>:\sapdb\QAS\db inst_reg <drive>:\sapdb\QAS\db

see SAP note 604680 for details !!!

*****************************************************

-> anyway, please make sure you have proper backup of all instances before you do any changes

(proper backup means backup done by maxdb/sapdb tools , the best one is offline for 7.3)

->before upgrading to 7.6 I would apply lates SAPDB 7.3 patch ( 7.3.0.62 i think)

Regards

Ivan

[Former Member · Accepted solution]

Thank you for the tips but it didn't work out properly

After dropping the database using:

dbmcli -s -d QAS -u user,passwd db_drop WITHOUTFILES

I tried to register using

dbmcli -s -R d:\sapdb\QAS\db inst_reg d:\sapdb\QAS\db ( according to note 604680) but it ended in error

Other alternitives with renaming the database where note 604680 is about didn't workout.

Using DBM I tried to recover the database, but that works partly. It is only initializing the database.

Recovering the data ends in 'wrong path' .

So, what should I do now?

[former_member229109 · Accepted solution]

Hello L. Cladder ,

as you could see the SAP note, you are SAP customer.

I recommend you to create the SAP message & get SAP support.

Personaly for me, in the current situation before to give you any further recommendations, I need to check the current status of the issue,

check what was done by you, check the database logs, run the database commands to get clear on the solution - steps.

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

Hi Natalia,

Thanks for your answer.

That's what I am doing now, so I am trying both ways.

best regards,

Louis Cladder