The dbmcli call for action DB_WARM failed.

[Former Member]

Hello everybody.

And thank in advance for help.

I want to install a Sap Instance (SOLMAN 4.0 SR2) on my server where there is already a IDES System installed.

During installation phase Create DB_Instance, i receive an error.

The error in file sapinst_dev.log:

TRACE

Running with toplevel file C:\Program Files/sapinst_instdir/SOLMAN/LM/UNINSTALL/AS/toplevel.xml

TRACE

Running with dialog file C:\Program Files/sapinst_instdir/SOLMAN/LM/UNINSTALL/AS/dialog.xml

TRACE

Running with keydb file C:\Program Files/sapinst_instdir/SOLMAN/LM/UNINSTALL/AS/keydb.xml

TRACE

Opened iaejs701.dll

TRACE

Opened iacdlib701.dll

TRACE

Opened iaccdlib.dll

TRACE

Opened iapasswdman701.dll

TRACE

This is SAPinst, version 701, make variant 700_REL, build 860072

compiled on Oct 6 2006, 03:58:22

TRACE [synxcaccmg.cpp:640]

CSyADsPath::fromString(SAP-SAV2\id2basis)

Account SAP-SAV2/id2basis has ADS path 'WinNT://SAP-SAV2/id2basis'

TRACE [synxcaccnt.cpp:967]

iastring CSyAccountImpl::getSID(IUnknown* pUnk) const

id2basis has SID S-1-5-21-2093825441-928787534-4179937713-1004

TRACE [synxcuser.cpp:1088]

CSyUserImpl::isExistingOnOS()

existence check for user id2basis returned true.

TRACE [syxxccache.cpp:208]

CSyAccountCache::getUserImpl(name="SAP-SAV2\id2basis", sid="", create=false, ISyProgressObserver* )

inserted account (id2basis, S-1-5-21-2093825441-928787534-4179937713-1004, USER) into the accountcache.

TRACE [syxxsyshlp.cpp:175]

syslib::logSystemState()

Process environment

===================

Environment Variables

=====================

= C:=C:\Program Files\sapinst_instdir\SOLMAN\LM\UNINSTALL\AS

= F:=F:\SOLMAN_IM\IM_WINDOWS_X86_64

ALLUSERSPROFILE = C:\Documents and Settings\All Users

APPDATA = C:\Documents and Settings\id2basis\Application Data

CLIENTNAME = LT-HEISAB

ClusterLog = C:\WINDOWS\Cluster\cluster.log

CommonProgramFiles = C:\Program Files\Common Files

CommonProgramFiles(x86) = C:\Program Files (x86)\Common Files

COMPUTERNAME = SAP-SAV2

ComSpec = C:\WINDOWS\system32\cmd.exe

FP_NO_HOST_CHECK = NO

HOMEDRIVE = C:

HOMEPATH = \Documents and Settings\id2basis

JAVA_HOME = C:\j2sdk1.4.2_16-x64

LOGONSERVER =
SAP-SAV2

NUMBER_OF_PROCESSORS = 4

OS = Windows_NT

Path = c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\usr\sap\saprouter;c:\j2sdk1.4.2_15\jre\bin

PATHEXT = .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH

PROCESSOR_ARCHITECTURE = AMD64

PROCESSOR_IDENTIFIER = EM64T Family 15 Model 4 Stepping 10, GenuineIntel

PROCESSOR_LEVEL = 15

PROCESSOR_REVISION = 040a

ProgramFiles = C:\Program Files

ProgramFiles(x86) = C:\Program Files (x86)

SAPINST_EXEDIR_CD = F:/SOLMAN_IM/IM_WINDOWS_X86_64

SAPINST_JRE_HOME = C:\j2sdk1.4.2_16-x64

SECUDIR = C:\usr\sap\saprouter

SESSIONNAME = RDP-Tcp#1

SNC_LIB = C:\usr\sap\saprouter\sapcrypto.dll

SystemDrive = C:

SystemRoot = C:\WINDOWS

TEMP = C:\DOCUME_{1\id2basis\LOCALS}1\Temp\1

TMP = C:\DOCUME_{1\id2basis\LOCALS}1\Temp\1

USERDOMAIN = SAP-SAV2

USERNAME = id2basis

USERPROFILE = C:\Documents and Settings\id2basis

windir = C:\WINDOWS

User: SAP-SAV2\id2basis, Id: S-1-5-21-2093825441-928787534-4179937713-1004

Working directory: C:\Program Files\sapinst_instdir\SOLMAN\LM\UNINSTALL\AS

TRACE [syxxsyshlp.cpp:185]

syslib::logSystemState()

System information

==================

OS version, host name: Microsoft Windows [Version 5.2.3790 Service Pack 1] SAP-SAV2

RAM size (MB): 8190.74

Swap size (MB): 7737.7

TRACE

Running with control file C:\Program Files\sapinst_instdir\SOLMAN\LM\UNINSTALL\AS\control.xml version 701 changelist 19645

.................

TRACE [iaxxejsexp.cpp:199]

EJS_Installer::writeTraceToLogBook()

tSdbAccounts.updateRow(, WHERE dbsid='SM1' AND role='DBM'), updating

TRACE [iaxxejsexp.cpp:199]

EJS_Installer::writeTraceToLogBook()

set accountdata for DBM to

ERROR 2007-11-13 13:58:01

CJSlibModule::writeError_impl()

The dbmcli call for action DB_WARM failed. Check the logfile XCMDOUT.LOG.

TRACE [iaxxejsbas.hpp:388]

handleException<ESAPinstJSError>()

Converting exception into JS Exception EJSException.

TRACE [iaxxdlghnd.cpp:719]

CDialogHandler::doHandleDoc()

<b>The dbmcli call for action DB_WARM failed. Check the logfile XCMDOUT.LOG.</b>

TRACE [iaxxgenimp.cpp:1155]

showDialog()

waiting for an answer from gui

I checked the file XCMDOUT.LOG, the error is reported below:

> Subprocess starts at 20071113134632

Execute Command : c:\sapdb\programs\pgm\dbmcli.exe -n sap-sav2 -d SM1 -u CONTROL,******** db_online

Execute Session Command : exit

> Subprocess stops at 20071113134636

> Subprocess call failed

ERR

-24988,ERR_SQL: SQL error

-902,I/O error

<b> 3,Database state: OFFLINE

6,Internal errorcode, Errorcode 9050 "disk_not_accessible"

20017,RestartFilesystem failed with 'I/O error'</b>

The installation has created the db_instance, sapdata and saplog directory have files. But i think itu00B4s a hardware problem, because then iu00B4ve done the installation on one other Disk of this server, and i reached.

So iu00B4ve checked the hardware:

disk-properties - tools - error checking - check now, with the two options:

- automatically fix file system errors and

- scan for and attemp recovery of bad sectors.

After the check and recovery, iu00B4ve checked and tested my deinstallation again, but i have found again the error above.

What can i do?

Is hardware problem? Is linked with Maxdb tool?

What can i do with datavolumes and logfile which at the moment are created on thi disk (i donu00B4t want to see them anymore...but i want a corrected uninstall process with sapinst implement, not directly cancel).

Thanks.

Points will be awarded for help.

Alberto Di Fazio

[Former Member · Accepted solution]

Hallo Lars.

Thanks for the infos.

But this is a new installation. I´ve no backup available.

And at the moment i can´t deinstall too, for this error.

I want to ask you, maybe it´s not so correct, but i´ve later done a new installation of the same SOLMAN on a other disk. It has successfully ended.

What can i do?

I´d like deinstall with sapinst, because the installation ended at the create_db_instance phase, but if not possible are there others possibilities?

[lbreddemann · Accepted solution]

Hi Alberto,

hmm.. a new installation should have started the DB via db_activate - not via db_warm.

So I still believe something happened before (something like db_activate failed and the sapinst was restarted to resume from that point).

To uninstall the bad db-instance simply use:

dbmcli -d <DBSID> -u control,<pw> db_drop

Afterwards you can deinstall the DEPENDENT software parts for this installation with sdbuninst.

After that you should be able to use sapinst to get rid of the rest of the solman software - but as I've never done this last step I simply have to guess here.

Best regards

Lars

p.s.

In any cases where a SAP system is involved and you face a severe problem, please use the SAP Support messages for this. You already paid for it. Response times in the forums may not be as good as the ones of the SAP Support (provided the correct message priority has been chosen).

[Former Member]

Hi, ok i´ll do so.

Thank you.

Best Regards

Alberto Di Fazio

[Former Member]

This is what my hardware IT Colleague reply me:

No, no SAN available.

However the plates are reflected, with a IDE SCSI. I.e. two plates appear in the data medium management as a plate.

I.e. two plates appear in the data medium management as a plate. SAN (STORAGE AREA network) we do not have in any case in the employment.

What can i endlich do?

Hardware change?

Alberto

[lbreddemann]

Hi Alberto,

the message

ERR 18156 VOLUMEIO It's not a valid volume: 'E:\sapdb\SM1\sapdata\DISKD0001'

usually means that the DB KERNEL is actually able to read and open the file of the datavolume but that the content of this file do not look like a valid MaxDB datavolume.

Basically the fileheader is likely to be crapped.

How did you get the file to this location? Any filecopy action involved? Or has it been created by MaxDB right there?

If you want to know what to do now: restore a backup. The file is crapped and there is no way to use it any further.

Best regards,

Lars

[Former Member]

SAN?

Do you need hardware config?

Windows Server 2003 SR2

Enterprise x64 Edition

Service Pack 1

Intel(R) Xeon (TM) CPU 3.20Ghz

3.20Ghz, 8 GB RAM

[markus_doehr2]

SAN = Storage Area Network

Where do those files reside?

You have a hardware problem.

--

Markus

[Former Member]

Yes,

Under E:\sapdb\SM1\sapdata\ i found 7 datavolumes:

DISKD0001

DISKD0002

..

DISKD0007

And in MAxdb Database Manager, chosing Add, i find my Instance SM1.

The datavolumes and logfiles seems allocated, but MaxDb seems not to reach them due to hardware or disk_access problems.

What do u think about?

Thank you

Alberto

[markus_doehr2]

Yes... there seems to be a hardware error.

Are they located on a SAN?

--

Markus

[Former Member]

Here the log in kernel dialog trace file:

2007-11-13 13:46:32 --- Starting GMT 2007-11-13 12:46:32 7.6.00 Build 035-123-139-084

2007-11-13 13:46:36 0x190 ERR 18156 VOLUMEIO It's not a valid volume: 'E:\sapdb\SM1\sapdata\DISKD0001'

2007-11-13 13:46:36 0xBD0 ERR 20027 IOMan Attach error on data volume 1: error evaluating volume

2007-11-13 13:46:36 0xBD0 ERR 3 Admin Database state: OFFLINE

2007-11-13 13:46:36 0xBD0 ERR 6 KernelCo + Internal errorcode, Errorcode 9050 "disk_not_accessible"

2007-11-13 13:46:36 0xBD0 ERR 20017 Admin + RestartFilesystem failed with 'I/O error'

2007-11-13 13:46:36 0xAA0 ERR 7 Messages Begin of dump of registered messages

2007-11-13 13:46:36 0xAA0 ERR 10 Messages abort dump of registered messages

2007-11-13 13:46:36 0xAA0 ERR 8 Messages End of the message list registry dump

2007-11-13 13:46:37 ___ Stopping GMT 2007-11-13 12:46:37 7.6.00 Build 035-123-139-084

2007-11-13 13:57:58 --- Starting GMT 2007-11-13 12:57:58 7.6.00 Build 035-123-139-084

2007-11-13 13:58:01 0x470 ERR 18156 VOLUMEIO It's not a valid volume: 'E:\sapdb\SM1\sapdata\DISKD0001'

2007-11-13 13:58:01 0x434 ERR 20027 IOMan Attach error on data volume 1: error evaluating volume

2007-11-13 13:58:01 0x434 ERR 3 Admin Database state: OFFLINE

2007-11-13 13:58:01 0x434 ERR 6 KernelCo + Internal errorcode, Errorcode 9050 "disk_not_accessible"

2007-11-13 13:58:01 0x434 ERR 20017 Admin + RestartFilesystem failed with 'I/O error'

2007-11-13 13:58:01 0xBBC ERR 7 Messages Begin of dump of registered messages

2007-11-13 13:58:01 0xBBC ERR 10 Messages abort dump of registered messages

2007-11-13 13:58:01 0xBBC ERR 8 Messages End of the message list registry dump

2007-11-13 13:58:02 ___ Stopping GMT 2007-11-13 12:58:02 7.6.00 Build 035-123-139-084

2007-11-13 14:17:24 --- Starting GMT 2007-11-13 13:17:24 7.6.00 Build 035-123-139-084

2007-11-13 14:17:28 0xF94 ERR 18156 VOLUMEIO It's not a valid volume: 'E:\sapdb\SM1\sapdata\DISKD0001'

2007-11-13 14:17:28 0xBAC ERR 20027 IOMan Attach error on data volume 1: error evaluating volume

2007-11-13 14:17:28 0xBAC ERR 3 Admin Database state: OFFLINE

2007-11-13 14:17:28 0xBAC ERR 6 KernelCo + Internal errorcode, Errorcode 9050 "disk_not_accessible"

2007-11-13 14:17:28 0xBAC ERR 20017 Admin + RestartFilesystem failed with 'I/O error'

2007-11-13 14:17:28 0x488 ERR 7 Messages Begin of dump of registered messages

2007-11-13 14:17:28 0x488 ERR 10 Messages abort dump of registered messages

2007-11-13 14:17:28 0x488 ERR 8 Messages End of the message list registry dump

2007-11-13 14:17:30 ___ Stopping GMT 2007-11-13 13:17:30 7.6.00 Build 035-123-139-084

[markus_doehr2]

Do you have an "E:" with the given file?

--

Markus

[markus_doehr2]

> b] 3,Database state: OFFLINE

> 6,Internal errorcode, Errorcode 9050

> "disk_not_accessible"

> 20017,RestartFilesystem failed with 'I/O error'</b>

>

The database tried to access a file that was not on the given place.

Check knldiag.err in the "wrk"-directory of your instance for the exact error.

--

Markus