cancel
Showing results for 
Search instead for 
Did you mean: 

Installtion CI after migration failed - The dbmcli call for action SDB_DBMVERSION failed

Former Member
0 Kudos

Hello,

we would like to migrate Portal NW 7.01 with database 7.8.01.12. The installer was running with MaxDB 7.7

we installed the maxdb 7.7, the backup/restore with SAPINST, before we started we patched the destination DB to 7.8 and we finished the db install with SAPinst without problems.

Now only the CI ist missing but we got following mistakes

 

WARNING[E]
2012-07-13 17:08:16.320

 

FSL-02015
Node /proc/sys/vm/compact_memory does not exist.

    

WARNING[E]
2012-07-13 17:08:16.356

 

FSL-02015
Node /proc/sys/net/ipv4/route/flush does not exist.

    

WARNING
2012-07-13 17:08:16.508

 

Host name
has been overridden. Using host name 'xxxxxci' which might not be the real host
name.

ERROR
2012-07-13 17:09:04.787

 

MDB-07001 No action defined for actor.

    

ERROR
2012-07-13 17:09:04.787

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

ERROR 2012-07-13 17:09:04.787

 

MUT-03025 Caught ESAPinstException in Modulecall: SDB_DBMVERSION.

    

ERROR 2012-07-13 17:09:04.811

FCO-00011 The step CheckExistingSoftware with step key |NW_Java_CI|ind|ind|ind|ind|0|0|NW_DBClient|ind|in

d|ind|ind|11|0|NW_ADA_DBClient|ind|ind|ind|ind|4|0|Sdb_ClientSoftware_Dialogs|ind|ind|ind|ind|0|0|CheckExi 

stingSoftware
was executed with status ERROR ( Last error reported by the step :Caught
ESAPinstException in
Modulecall: SDB_DBMVERSION.).

The XCMDOUT.LOG shows no problems, any ideas?

Thanks a lot

Best Regards

Steffi

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

Did you run CI installation part as :

./sapinst SAPINST_USE_HOSTNAME=xxxxxci'

and DB installation part as:

./sapinst SAPINST_USE_HOSTNAME=xxxxxdb'

If not this is probably part of your error can you attach more specific logs maybe?

Kind Regards,

Johan

Sriram2009
Active Contributor
0 Kudos
Former Member
0 Kudos

Hello,

It seems like your central instance and DB host are different.

Please check the central host name which you have entered in the DB installation.

Also check that files from Central instance to DB instance are mounted.

Regards,

Jyoti Kokate