cancel
Showing results for 
Search instead for 
Did you mean: 

Heterogenous System Copy 6.40 SR1 to MaxDB 7.8

Former Member
0 Kudos

Hello,

I am performing a heterogenous system copy from Solaris/MaxDB

to SLES 11/MaxDB 7.8. I am using the Installation Master 51033746

(NetWeaver '04 SR1). The MaxDB 7.8 software is already installed

and I have configured raw devices. The existing DB instance should

be reused.

Unfortunately sapinst complains that it cannot use MaxDB 7.8 for the import:

The version of the database is not correct. Required version: 75. Found version: 78.

Is there any supported way to circumvent this problem? I haven't found

any note or hint in the system copy guides.

Regards,

Mark

Accepted Solutions (1)

Accepted Solutions (1)

markus_doehr2
Active Contributor
0 Kudos

> Is there any supported way to circumvent this problem? I haven't found

> any note or hint in the system copy guides.

Check

Note 1466917 - MaxDB 7.8: Installation/System Copy based on SAP Kernel 6.40

Markus

Former Member
0 Kudos

Hello Markus,

thanks for the note, somehow I must have missed it when searching for it.

If I understand the note correctly, then I have to import on MaxDB 7.7 and

then upgrade to MaxDB 7.8. Dang!

Regards,

Mark

markus_doehr2
Active Contributor
0 Kudos

> thanks for the note, somehow I must have missed it when searching for it.

> If I understand the note correctly, then I have to import on MaxDB 7.7 and

> then upgrade to MaxDB 7.8. Dang!

Yes.

What you can try however (haven't done myself so I don't know whether it works):

- Shut down database and x_server

- install the 7.7 software over the 7.8 one using

./SDBINST -indep_prog /sapdb/programs \
-indep_data /sapdb/data \
-depend /sapdb/<SID>/db \
-profile Server -o <user> -g <group>

- activate the database

- load system tables

Markus

Former Member
0 Kudos

I already had a different idea, I messed around with control.xml

to accept MaxDB 7.8 as an installation target. It worked quite

fine, but somehow I had to execute many commands (most

notably R3load) manually because sapinst couldn't execute

them automatically.

This made me believe that support for MaxDB 7.8 on 6.40

or 7.00 installations shouldn't be a big issue.

My test was just for a quick test migration, so no damage was done.

markus_doehr2
Active Contributor
0 Kudos

> fine, but somehow I had to execute many commands (most

> notably R3load) manually because sapinst couldn't execute

> them automatically.

You can use the "sapdb.inf" attached to that note to get the modified commands - though those are not for all of them.

> This made me believe that support for MaxDB 7.8 on 6.40

> or 7.00 installations shouldn't be a big issue.

Well, responses and some syntax changed slightly, adaptions are necessary and are not "complete".

Sometimes I question myself why SAP doesn't offer new installation medias for new operating system and new databases more frequently. Most of them are more than 2 years old and don't keep up with actual development, be it the database version or the operating system. Interestingly enough, for Oracle 11 there are new DVDs provided, for MaxDB there are not though 7.8 is longer out and released than 11g....

Markus

Answers (0)