cancel
Showing results for 
Search instead for 
Did you mean: 

Systemcopy Problem with MaxDB 7.7/7.8 (Create Database Instance)

Former Member
0 Kudos

Hello Guys,

I have a problem with a system copy of a CRM 7 system (NW 7.01 J2EE with MaxDB 7.8.02.32).

The Source System runs on a Windows 2003 x64 Server. The Target System will be on the same server. There are already 2 Instances installed (SD1, SD2).

I made the Source System Extract (Standard System Copy) and started the target installation.

As database version I chose MaxDB 7.7 because I had trouble with 7.8 at another installation. I upgraded to 7.8 after the System Copy.

At phase 11 (create Database Instance) I get an error.

In the XCMDOUT.LOG there is following entry:

> Subprocess starts at 20130218104901

Execute Command : Y:\sapdb\programs\pgm\dbmcli.exe -n isw56 inst_enum

Execute Session Command : exit

> Subprocess stops at 20130218104901

OK

7.8.02.23    Y:\sapdb\SD3\db

7.8.02.23    Y:\sapdb\SD2\db

7.8.02.23    Y:\sapdb\SD1\db

7.8.01.16    Y:\sapdb\clients\DatabaseStudio

SD1 and SD2 are already installed and running. SD3 is my system copy that fails.

I also tried the system copy with 7.8 but it fails at the same phase.

Now I have no idea what I should do to make the system copy work.

best regards

Tobias Nagel

Accepted Solutions (1)

Accepted Solutions (1)

former_member229109
Active Contributor
0 Kudos

Hello Tobias,

-> "I have a problem with a system copy of a CRM 7 system (NW 7.01 J2EE with MaxDB 7.8.02.32).

The Source System runs on a Windows 2003 x64 Server. The Target System will be on the same server. There are already 2 Instances installed (SD1, SD2)."

The target database instance is SD3. It will be on the same server as source DB.

Is your source DB SD1 or SD2 ?

You already checked the SAP Note No. 919224. Correct?

-> Are you planning to do a system copy of a CRM 7 system (NW 7.01 J2EE with MaxDB 7.8.02.32) to a CRM 7 system (NW 7.01 J2EE with MaxDB 7.7).?

You wrote:

"As database version I chose MaxDB 7.7 because I had trouble with 7.8 at another installation. I upgraded to 7.8 after the System Copy."

=>

Please update with output of commands:

sdbregview -l

dbmcli inst_enum

If your source DB instance is on 7.8 version, you need to install the target DB instance of 7.8 version or higher.

Regards, Natalia Khlopina

Former Member
0 Kudos

Hello Natalia,

yes, I already checked this note. As I already said I tried the systemcopy with 7.8 also but getting the same error.

Note 1469675 implies that I have to use 7.7 for the systemcopy and upgrade to 7.8 afterwards. That worked fine for another system (same version of J2EE engine and OS).

This is the sapinst_dev.log:

WARNING[E] 2013-02-18 14:53:05.540 [iaxabactorext.cpp:465]

           CIaSdbActorExt::sdbSessionExecute_impl

MDB-07001  No action defined for actor.

WARNING[E] 2013-02-18 14:53:05.540

           CJSlibModule::writeError_impl()

The dbmcli call for action DB_CREATE failed. SOLUTION: Check the logfile XCMDOUT.LOG.

TRACE      2013-02-18 14:53:05.540 [iaxxejsbas.hpp:408]

           handleException<ESAPinstJSError>()

Converting exception into JS Exception EJSException.

TRACE      2013-02-18 14:53:05.540

Function setMessageIdOfExceptionMessage: dbmodada.actorext.dbmcliCallFailed

WARNING[E] 2013-02-18 14:53:05.540

           CJSlibModule::writeError_impl()

The dbmcli call for action DB_CREATE failed. SOLUTION: Check the logfile XCMDOUT.LOG.

TRACE      2013-02-18 14:53:05.540 [iaxxejsbas.hpp:483]

           EJS_Base::dispatchFunctionCall()

JS Callback has thrown unknown exception. Rethrowing.

Former Member
0 Kudos

Hello,

I solved the problem with Note 1463509

I downloaded the sapdb.inf file and copied it to sapinst_instdir and restarted the systemcopy.

It worked.

best regards

Tobias

Answers (1)

Answers (1)

former_member188883
Active Contributor
0 Kudos

Hi Tobias,

I could not make out when are you facing the problem. Is it after system copy or is it after upgrading your system to 7.8 version.

Regards,

Deepak Kori

Former Member
0 Kudos

Hello Deepak,

the problem occurs during the system copy.

regards

Tobias