I got this error when install SAP ECC v6.0 SR3 IDES Oracle 10.2.0.2. Anyone could you help me please?

Program is starting... Please wait!

Starting GUIServer using:

  SAPinst port  : 21200

  GUIServer port: 21212

  HTTP port     : 4239

  GUI autostart : on

  GUI mode      : normal

  command       : "C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/sapinst_exe.200.1459798221/jre/bin\java.exe" -cp "C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/sapinst_exe.200.1459798221\jar\instgui.jar" -Xmx256M -Dsun.java2d.noddraw=true -Dsap.env.var.javahome=SAPINST_JRE_HOME SDTGui sapinst host=localhost port=21200 -nolock

load resource pool \\vmware-host\Shared Folders\BIASI\Desktop\51037622\IM_WINDOWS_X86_64\resourcepool.xml

guiengine: No GUI server connected; waiting for a connection on host sap, port 21200 to continue with the installation

Apr 4, 2016 4:30:30 PM [Info]: *************************

Apr 4, 2016 4:30:30 PM [Info]: Starting Server

Apr 4, 2016 4:30:30 PM [Info]: Reading server configuration.

Apr 4, 2016 4:30:30 PM [Info]: Reading service configuration SAPinstService.

Apr 4, 2016 4:30:30 PM [Info]: Configuring LogManager ...

Apr 4, 2016 4:30:30 PM [Info]: *************************************************

Apr 4, 2016 4:30:30 PM [Info]: Starting SL Controller ...

Apr 4, 2016 4:30:30 PM [Info]: StorageService switched off.

Apr 4, 2016 4:30:30 PM [Info]: Initializing SecurityManager ...

Apr 4, 2016 4:30:30 PM [Info]: Key Store management switched off.

Apr 4, 2016 4:30:31 PM [Info]: Configuring HTTPManager ...

Apr 4, 2016 4:30:31 PM [Info]: WebstartService switched off.

Apr 4, 2016 4:30:31 PM [Info]: RoleService switched off.

Apr 4, 2016 4:30:31 PM [Info]: AlertService switched off.

Apr 4, 2016 4:30:31 PM [Info]: NotesService switched off.

Apr 4, 2016 4:30:31 PM [Info]: ProcessService switched off.

Apr 4, 2016 4:30:31 PM [Info]: Starting MIDService ...

Apr 4, 2016 4:30:31 PM [Info]: Starting FileService ...

Apr 4, 2016 4:30:31 PM [Info]: LogService switched off.

Apr 4, 2016 4:30:31 PM [Info]: MailService switched off.

Apr 4, 2016 4:30:31 PM [Info]: Starting services ...

Apr 4, 2016 4:30:31 PM [Info]: Starting service "SAPinstService" ...

Apr 4, 2016 4:30:32 PM [Info]: Service "SAPinstService" started

Apr 4, 2016 4:30:32 PM [Info]: Services started.

Apr 4, 2016 4:30:32 PM [Info]: Starting HTTP server listening on port 4239 ...

Apr 4, 2016 4:30:32 PM [Info]: HTTP server started.

Apr 4, 2016 4:30:32 PM [Info]: SL Controller started.

Apr 4, 2016 4:30:32 PM [Info]: Starting GUI ...

guiengine: 2016-04-04 16:30:37 Login in progress

guiengine: 2016-04-04 16:30:37 Login successful

Apr 4, 2016 4:30:38 PM [Info]: GUI started.

INFO       2016-04-04 16:30:26.820 [synxcpath.cpp:776]

           CSyPath::createFile()

Creating file C:\Program Files\sapinst_instdir\x.

INFO       2016-04-04 16:30:26.820 [synxcfile.cpp:177]

           CSyFileImpl::remove()

Removing file C:\Program Files\sapinst_instdir\x.

INFO       2016-04-04 16:32:03.006 [synxcpath.cpp:776]

           CSyPath::createFile()

Creating file C:\Program Files\sapinst_instdir\ERPEhP4\AS-ABAP\ORA\CENTRAL\x.

INFO       2016-04-04 16:32:03.006 [synxcfile.cpp:177]

           CSyFileImpl::remove()

Removing file C:\Program Files\sapinst_instdir\ERPEhP4\AS-ABAP\ORA\CENTRAL\x.

INFO       2016-04-04 16:32:19.990 [synxcpath.cpp:776]

           CSyPath::createFile()

Creating file C:\Program Files\sapinst_instdir\x.

INFO       2016-04-04 16:32:19.990 [synxcfile.cpp:177]

           CSyFileImpl::remove()

Removing file C:\Program Files\sapinst_instdir\x.

INFO       2016-04-04 16:32:22.427 [synxcfile.cpp:493]

           CSyFileImpl::copy(const CSyPath & C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/statistic.24.xml, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const 

Copied file 'C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/statistic.xml' to 'C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/statistic.24.xml'.

INFO       2016-04-04 16:32:24.068 [synxcfile.cpp:493]

           CSyFileImpl::copy(const CSyPath & C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/statistic.25.xml, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const 

Copied file 'C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/statistic.xml' to 'C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/statistic.25.xml'.

WARNING    2016-04-04 16:32:30.380 [synxcpath.cpp:912]

           CSyPath::getOSNodeType(bool )

Unable to get information about path \\LABEL.ASC\ using GetVolumeInformation. Operating system error message: The filename, directory name, or volume label syntax is incorrect.

INFO       2016-04-04 16:32:35.490 [synxcfile.cpp:493]

           CSyFileImpl::copy(const CSyPath & C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/inifile.10.xml, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const 

Copied file 'C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/inifile.xml' to 'C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/inifile.10.xml'.

INFO       2016-04-04 16:32:35.646 [sixxcstepexecute.cpp:388]

Execute step

Component  W2K_ServicePack_Check|ind|ind|ind|ind

Preprocess  of component |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|0|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0

INFO       2016-04-04 16:32:49.880 [synxcfile.cpp:493]

           CSyFileImpl::copy(const CSyPath & C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/keydb.9.xml, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const 

Copied file 'C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/keydb.xml' to 'C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/keydb.9.xml'.

INFO       2016-04-04 16:32:49.942 [synxcfile.cpp:493]

           CSyFileImpl::copy(const CSyPath & C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/statistic.26.xml, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const 

Copied file 'C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/statistic.xml' to 'C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/statistic.26.xml'.

INFO       2016-04-04 16:32:49.974 [sixxcstepexecute.cpp:790]

Execute step runMigrationMonitor of component |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0

INFO       2016-04-04 16:32:55.380 [synxccuren.cpp:1054]

           CSyCurrentProcessEnvironmentImpl::setUser()

Switched to user: c11adm.

INFO       2016-04-04 16:32:55.395 [synxcpath.cpp:776]

           CSyPath::createFile()

Creating file C:\Program Files\sapinst_instdir\ERPEhP4\AS-ABAP\ORA\CENTRAL\import_monitor.java.log.

INFO       2016-04-04 16:32:55.395 [synxccuren.cpp:1054]

           CSyCurrentProcessEnvironmentImpl::setUser()

Switched to user: c11adm.

INFO       2016-04-04 16:32:55.583 [syxxccuren.cpp:106]

           CSyCurrentProcessEnvironmentImpl::setWorkingDirectory(iastring)

Working directory changed to C:\Program Files\sapinst_instdir\ERPEhP4\AS-ABAP\ORA\CENTRAL.

INFO       2016-04-04 16:32:55.583

           CJSlibModule::writeInfo_impl()

Output of C:\j2sdk1.4.2_17\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.

WARNING    2016-04-04 16:43:58.123

           CJSlibModule::writeWarning_impl()

Execution of the command "C:\j2sdk1.4.2_17\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:

java version "1.4.2_17"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_17-b06)

Java HotSpot(TM) Client VM (build 1.4.2_17-b06, mixed mode)

Import Monitor jobs: running 1, waiting 64, completed 40, failed 0, total 105.

Import Monitor jobs: running 2, waiting 63, completed 40, failed 0, total 105.

Import Monitor jobs: running 3, waiting 62, completed 40, failed 0, total 105.

Loading of 'SAPAPPL2_6' import package: ERROR

Import Monitor jobs: running 2, waiting 62, completed 40, failed 1, total 105.

Loading of 'SAPAPPL0_4' import package: ERROR

Import Monitor jobs: running 1, waiting 62, completed 40, failed 2, total 105.

Loading of 'E071K' import package: ERROR

Import Monitor jobs: running 0, waiting 62, completed 40, failed 3, total 105.

Import Monitor jobs: running 1, waiting 61, completed 40, failed 3, total 105.

Import Monitor jobs: running 2, waiting 60, completed 40, failed 3, total 105.

Import Monitor jobs: running 3, waiting 59, completed 40, failed 3, total 105.

Loading of 'SAPSSEXC_1' import package: ERROR

Import Monitor jobs: running 2, waiting 59, completed 40, failed 4, total 105.

Loading of 'SAPAPPL2_8' import package: ERROR

Import Monitor jobs: running 1, waiting 59, completed 40, failed 5, total 105.

Loading of 'SAPAPPL2_9' import package: ERROR

Import Monitor jobs: running 0, waiting 59, completed 40, failed 6, total 105.

Import Monitor jobs: running 1, waiting 58, completed 40, failed 6, total 105.

Import Monitor jobs: running 2, waiting 57, completed 40, failed 6, total 105.

Import Monitor jobs: running 3, waiting 56, completed 40, failed 6, total 105.

Loading of 'SOTR_TEXT' import package: ERROR

Import Monitor jobs: running 2, waiting 56, completed 40, failed 7, total 105.

Loading of 'SAPAPPL1_1' import package: ERROR

Import Monitor jobs: running 1, waiting 56, completed 40, failed 8, total 105.

Loading of 'SAPAPPL1_3' import package: ERROR

Import Monitor jobs: running 0, waiting 56, completed 40, failed 9, total 105.

Import Monitor jobs: running 1, waiting 55, completed 40, failed 9, total 105.

Import Monitor jobs: running 2, waiting 54, completed 40, failed 9, total 105.

Import Monitor jobs: running 3, waiting 53, completed 40, failed 9, total 105.

Loading of 'ATAB' import package: ERROR

Import Monitor jobs: running 2, waiting 53, completed 40, failed 10, total 105.

Loading of 'DD02T' import package: ERROR

Import Monitor jobs: running 1, waiting 53, completed 40, failed 11, total 105.

Loading of 'FUNCT' import package: ERROR

Import Monitor jobs: running 0, waiting 53, completed 40, failed 12, total 105.

Import Monitor jobs: running 1, waiting 52, completed 40, failed 12, total 105.

Import Monitor jobs: running 2, waiting 51, completed 40, failed 12, total 105.

Import Monitor jobs: running 3, waiting 50, completed 40, failed 12, total 105.

Loading of 'E071' import package: ERROR

Import Monitor jobs: running 2, waiting 50, completed 40, failed 13, total 105.

Loading of 'SAPAPPL2_1' import package: ERROR

Import Monitor jobs: running 1, waiting 50, completed 40, failed 14, total 105.

Loading of 'SAPAPPL2_5' import package: ERROR

Import Monitor jobs: running 0, waiting 50, completed 40, failed 15, total 105.

Import Monitor jobs: running 1, waiting 49, completed 40, failed 15, total 105.

Import Monitor jobs: running 2, waiting 48, completed 40, failed 15, total 105.

Import Monitor jobs: running 3, waiting 47, completed 40, failed 15, total 105.

Loading of 'SAPAPPL2_4' import package: ERROR

Import Monitor jobs: running 2, waiting 47, completed 40, failed 16, total 105.

Loading of 'SAPAPPL1_11' import package: ERROR

Import Monitor jobs: running 1, waiting 47, completed 40, failed 17, total 105.

Loading of 'SAPAPPL0_1' import package: ERROR

Import Monitor jobs: running 0, waiting 47, completed 40, failed 18, total 105.

Import Monitor jobs: running 1, waiting 46, completed 40, failed 18, total 105.

Import Monitor jobs: running 2, waiting 45, completed 40, failed 18, total 105.

Import Monitor jobs: running 3, waiting 44, completed 40, failed 18, total 105.

Loading of 'SEOSUBCOTX' import package: ERROR

Import Monitor jobs: running 2, waiting 44, completed 40, failed 19, total 105.

Loading of 'INDTEXT' import package: ERROR

Import Monitor jobs: running 1, waiting 44, completed 40, failed 20, total 105.

Loading of 'SAPAPPL0_9' import package: ERROR

Import Monitor jobs: running 0, waiting 44, completed 40, failed 21, total 105.

Import Monitor jobs: running 1, waiting 43, completed 40, failed 21, total 105.

Import Monitor jobs: running 2, waiting 42, completed 40, failed 21, total 105.

Import Monitor jobs: running 3, waiting 41, completed 40, failed 21, total 105.

Loading of 'SAPAPPL1_9' import package: ERROR

Import Monitor jobs: running 2, waiting 41, completed 40, failed 22, total 105.

Loading of 'SAPAPPL1_6' import package: ERROR

Import Monitor jobs: running 1, waiting 41, completed 40, failed 23, total 105.

Loading of 'SAPAPPL0_5' import package: ERROR

Import Monitor jobs: running 0, waiting 41, completed 40, failed 24, total 105.

Import Monitor jobs: running 1, waiting 40, completed 40, failed 24, total 105.

Import Monitor jobs: running 2, waiting 39, completed 40, failed 24, total 105.

Import Monitor jobs: running 3, waiting 38, completed 40, failed 24, total 105.

Loading of 'GLFUNCA' import package: ERROR

Import Monitor jobs: running 2, waiting 38, completed 40, failed 25, total 105.

Loading of 'DDFTX' import package: ERROR

Import Monitor jobs: running 1, waiting 38, completed 40, failed 26, total 105.

Loading of 'OCSCMPLOBJ' import package: ERROR

Import Monitor jobs: running 0, waiting 38, completed 40, failed 27, total 105.

Import Monitor jobs: running 1, waiting 37, completed 40, failed 27, total 105.

Import Monitor jobs: running 2, waiting 36, completed 40, failed 27, total 105.

Import Monitor jobs: running 3, waiting 35, completed 40, failed 27, total 105.

Loading of 'USRBF2' import package: ERROR

Import Monitor jobs: running 2, waiting 35, completed 40, failed 28, total 105.

Loading of 'SAPAPPL0_7' import package: ERROR

Import Monitor jobs: running 1, waiting 35, completed 40, failed 29, total 105.

Loading of 'SAPSSEXC_4' import package: ERROR

Import Monitor jobs: running 0, waiting 35, completed 40, failed 30, total 105.

Import Monitor jobs: running 1, waiting 34, completed 40, failed 30, total 105.

Import Monitor jobs: running 2, waiting 33, completed 40, failed 30, total 105.

Import Monitor jobs: running 3, waiting 32, completed 40, failed 30, total 105.

Loading of 'SCPRSVALS' import package: ERROR

Import Monitor jobs: running 2, waiting 32, completed 40, failed 31, total 105.

Loading of 'DD07T' import package: ERROR

Import Monitor jobs: running 1, waiting 32, completed 40, failed 32, total 105.

Loading of 'PPOIX' import package: ERROR

Import Monitor jobs: running 0, waiting 32, completed 40, failed 33, total 105.

Import Monitor jobs: running 1, waiting 31, completed 40, failed 33, total 105.

Import Monitor jobs: running 2, waiting 30, completed 40, failed 33, total 105.

Import Monitor jobs: running 3, waiting 29, completed 40, failed 33, total 105.

Loading of 'SEOCOMPOTX' import package: ERROR

Import Monitor jobs: running 2, waiting 29, completed 40, failed 34, total 105.

Loading of 'TRDIRT' import package: ERROR

Import Monitor jobs: running 1, waiting 29, completed 40, failed 35, total 105.

Loading of 'SCPRSVALL' import package: ERROR

Import Monitor jobs: running 0, waiting 29, completed 40, failed 36, total 105.

Import Monitor jobs: running 1, waiting 28, completed 40, failed 36, total 105.

Import Monitor jobs: running 2, waiting 27, completed 40, failed 36, total 105.

Import Monitor jobs: running 3, waiting 26, completed 40, failed 36, total 105.

Loading of 'SEOSUBCODF' import package: ERROR

Import Monitor jobs: running 2, waiting 26, completed 40, failed 37, total 105.

Loading of 'WBCROSSGT' import package: ERROR

Import Monitor jobs: running 1, waiting 26, completed 40, failed 38, total 105.

Loading of 'TMENU01T' import package: ERROR

Import Monitor jobs: running 0, waiting 26, completed 40, failed 39, total 105.

Import Monitor jobs: running 1, waiting 25, completed 40, failed 39, total 105.

Import Monitor jobs: running 2, waiting 24, completed 40, failed 39, total 105.

Import Monitor jobs: running 3, waiting 23, completed 40, failed 39, total 105.

Loading of 'FUPARAREF' import package: ERROR

Import Monitor jobs: running 2, waiting 23, completed 40, failed 40, total 105.

Loading of 'SCPRVALS' import package: ERROR

Import Monitor jobs: running 1, waiting 23, completed 40, failed 41, total 105.

Loading of 'TODIR' import package: ERROR

Import Monitor jobs: running 0, waiting 23, completed 40, failed 42, total 105.

Import Monitor jobs: running 1, waiting 22, completed 40, failed 42, total 105.

Import Monitor jobs: running 2, waiting 21, completed 40, failed 42, total 105.

Import Monitor jobs: running 3, waiting 20, completed 40, failed 42, total 105.

Loading of 'DOKHL' import package: ERROR

Import Monitor jobs: running 2, waiting 20, completed 40, failed 43, total 105.

Loading of 'TADIR' import package: ERROR

Import Monitor jobs: running 1, waiting 20, completed 40, failed 44, total 105.

Loading of 'FAGLFLEXA' import package: ERROR

Import Monitor jobs: running 0, waiting 20, completed 40, failed 45, total 105.

Import Monitor jobs: running 1, waiting 19, completed 40, failed 45, total 105.

Import Monitor jobs: running 2, waiting 18, completed 40, failed 45, total 105.

Import Monitor jobs: running 3, waiting 17, completed 40, failed 45, total 105.

Loading of 'DSYS_PHFILE_ECD2' import package: ERROR

Import Monitor jobs: running 2, waiting 17, completed 40, failed 46, total 105.

Loading of 'DOKIL' import package: ERROR

Import Monitor jobs: running 1, waiting 17, completed 40, failed 47, total 105.

Loading of 'DD08T' import package: ERROR

Import Monitor jobs: running 0, waiting 17, completed 40, failed 48, total 105.

Import Monitor jobs: running 1, waiting 16, completed 40, failed 48, total 105.

Import Monitor jobs: running 2, waiting 15, completed 40, failed 48, total 105.

Import Monitor jobs: running 3, waiting 14, completed 40, failed 48, total 105.

Loading of 'BSIS' import package: ERROR

Import Monitor jobs: running 2, waiting 14, completed 40, failed 49, total 105.

Loading of 'COEP' import package: ERROR

Import Monitor jobs: running 1, waiting 14, completed 40, failed 50, total 105.

Loading of 'SAPSPROT' import package: ERROR

Import Monitor jobs: running 0, waiting 14, completed 40, failed 51, total 105.

Import Monitor jobs: running 1, waiting 13, completed 40, failed 51, total 105.

Import Monitor jobs: running 2, waiting 12, completed 40, failed 51, total 105.

Import Monitor jobs: running 3, waiting 11, completed 40, failed 51, total 105.

Loading of 'REGUH' import package: ERROR

Import Monitor jobs: running 2, waiting 11, completed 40, failed 52, total 105.

Loading of 'WDY_UI_PROPERTY' import package: ERROR

Import Monitor jobs: running 1, waiting 11, completed 40, failed 53, total 105.

Loading of 'SAPSDOCU' import package: ERROR

Import Monitor jobs: running 0, waiting 11, completed 40, failed 54, total 105.

Import Monitor jobs: running 1, waiting 10, completed 40, failed 54, total 105.

Import Monitor jobs: running 2, waiting 9, completed 40, failed 54, total 105.

Import Monitor jobs: running 3, waiting 8, completed 40, failed 54, total 105.

Loading of 'CATF' import package: ERROR

Import Monitor jobs: running 2, waiting 8, completed 40, failed 55, total 105.

Loading of 'COEJ' import package: ERROR

Import Monitor jobs: running 1, waiting 8, completed 40, failed 56, total 105.

Loading of 'SAPSLOAD' import package: ERROR

Import Monitor jobs: running 0, waiting 8, completed 40, failed 57, total 105.

Import Monitor jobs: running 1, waiting 7, completed 40, failed 57, total 105.

Import Monitor jobs: running 2, waiting 6, completed 40, failed 57, total 105.

Import Monitor jobs: running 3, waiting 5, completed 40, failed 57, total 105.

Loading of 'SAPDDIM' import package: ERROR

Import Monitor jobs: running 2, waiting 5, completed 40, failed 58, total 105.

Loading of 'SAPUSER' import package: ERROR

Import Monitor jobs: running 1, waiting 5, completed 40, failed 59, total 105.

Loading of 'SAPPOOL' import package: ERROR

Import Monitor jobs: running 0, waiting 5, completed 40, failed 60, total 105.

Import Monitor jobs: running 1, waiting 4, completed 40, failed 60, total 105.

Import Monitor jobs: running 2, waiting 3, completed 40, failed 60, total 105.

Import Monitor jobs: running 3, waiting 2, completed 40, failed 60, total 105.

Loading of 'SAPUSER1' import package: ERROR

Import Monitor jobs: running 2, waiting 2, completed 40, failed 61, total 105.

Loading of 'SAPDFACT' import package: ERROR

Import Monitor jobs: running 1, waiting 2, completed 40, failed 62, total 105.

Loading of 'SAPDODS' import package: ERROR

Import Monitor jobs: running 0, waiting 2, completed 40, failed 63, total 105.

Import Monitor jobs: running 1, waiting 1, completed 40, failed 63, total 105.

Loading of 'SAP0000' import package: ERROR

Import Monitor jobs: running 0, waiting 1, completed 40, failed 64, total 105.

ERROR      2016-04-04 16:43:58.123

           CJSlibModule::writeError_impl()

CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.

ERROR      2016-04-04 16:43:58.342 [sixxcstepexecute.cpp:950]

FCO-00011  The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).

INFO       2016-04-04 16:47:48.964 [sixxcstepexecute.cpp:1003]

An error occured and the user decided to stop.\n Current step "|NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor".

a C:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/sapinst_exe.200.1459798221/dev_selfex.out

a C:/Documents and Settings/Administrator/.sdtgui/log/FileService.log

a C:/Documents and Settings/Administrator/.sdtgui/log/MIDService.log

a C:/Documents and Settings/Administrator/.sdtgui/log/SAPinstService.log

a C:/Documents and Settings/Administrator/.sdtgui/log/SDTServer.log

a C:/Documents and Settings/Administrator/.sdtgui/log/gui.err

a C:/Documents and Settings/Administrator/.sdtgui/log/gui.log

a C:/Documents and Settings/Administrator/.sdtgui/log/gui.log.lck

a C:/Documents and Settings/Administrator/.sdtgui/log/gui.out

a C:/Documents and Settings/Administrator/.sdtgui/log/gui.trc

a C:/Documents and Settings/Administrator/.sdtgui/log/gui.trc.lck

a C:/Documents and Settings/Administrator/.sdtgui/log/server.err

a C:/Documents and Settings/Administrator/.sdtgui/log/server.out

a C:/Documents and Settings/Administrator/.sdtgui/log/server.trc

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/AGR_HIERT.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/ARFCSDATA.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/ATAB.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/BSIS.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/CATF.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/COEJ.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/COEP.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/D021T.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/DBATOOLS.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/DD02T.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/DD03L.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/DD04T.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/DD07T.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/DD08T.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/DDFTX.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/DOKCLU.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/DOKHL.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/DOKIL.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/DSYS_PHFILE_ECD2.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/E071.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/E071K.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/FAGLFLEXA.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/FUNCT.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/FUPARAREF.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/FormalPasswordCheck.1.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/FormalPasswordCheck.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/GLFUNCA.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/IGSEXE.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/IGSHELPER.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/INDTEXT.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/ImportMonitor.console.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/OCL10264.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/OCSCMPLOBJ.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/PCL2.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/PCL4.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/PPOIX.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/R3load.exe.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/REGUH.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/REPOSRC.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/REPOTEXT.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/RFBLG.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/RSMPTEXTS.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAP0000.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL0_1.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL0_2.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL0_3.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL0_4.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL0_5.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL0_6.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL0_7.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL0_8.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL0_9.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL1_1.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL1_10.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL1_11.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL1_12.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL1_2.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL1_3.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL1_4.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL1_5.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL1_6.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL1_7.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL1_8.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL1_9.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL2_1.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL2_2.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL2_3.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL2_4.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL2_5.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL2_6.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL2_7.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL2_8.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPAPPL2_9.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPCLUST.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPDDIM.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPDFACT.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPDODS.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPEXE.1.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPEXE.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPEXEDB.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPNTAB.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPPOOL.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPSDIC_1.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPSDIC_2.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPSDOCU.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPSLEXC.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPSLOAD.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPSPROT.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPSSEXC_1.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPSSEXC_2.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPSSEXC_3.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPSSEXC_4.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPSSRC.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPUSER.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SAPUSER1.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SCPRSVALL.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SCPRSVALS.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SCPRVALS.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SECINSTTOOLS.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SEOCOMPODF.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SEOCOMPOTX.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SEOSUBCODF.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SEOSUBCOTX.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SOC3.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/SOTR_TEXT.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/STERM_TEXT.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/T100.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/TADIR.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/TMENU01T.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/TODIR.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/TRDIRT.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/USRBF2.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/VRSMODISRC.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/VRSX.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/WBCROSSGT.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/WDY_UI_PROPERTY.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/change.1.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/change.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/control.xml

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/controllerKdbClient.dmp

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/dbms_scheduler.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/import_monitor.java.1.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/import_monitor.java.2.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/import_monitor.java.3.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/import_monitor.java.4.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/import_monitor.java.5.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/import_monitor.java.6.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/import_monitor.java.7.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/import_monitor.java.8.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/import_monitor.java.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/import_monitor.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/instana.xsl

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/keydb.xml

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/lsnrctl.1.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/lsnrctl.2.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/lsnrctl.3.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/lsnrctl.4.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/lsnrctl.5.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/lsnrctl.6.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/lsnrctl.7.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/lsnrctl.8.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/lsnrctl.9.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/lsnrctl.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/msiexec.1.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/msiexec.2.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/msiexec.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/ora_sql.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/ora_sql_results.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/ora_successful_sql.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/oradbusr.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/oradim.1.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/oradim.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/orapwd.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/recompile.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapconn_role.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapdba_role.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapinst.1.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapinst.2.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapinst.3.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapinst.4.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapinst.5.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapinst.6.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapinst.7.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapinst.8.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapinst.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapinst_dev.1.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapinst_dev.2.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapinst_dev.3.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapinst_dev.4.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapinst_dev.5.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapinst_dev.6.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapinst_dev.7.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapinst_dev.8.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapinst_dev.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapinst_ora_environment.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sapmmcX64u.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/sqlnet.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/start_dir.cd

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/stepKeydbClient.dmp

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/summary.html

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/vcredist_x64.1.log

a C:/Program Files/sapinst_instdir/ERPEhP4/AS-ABAP/ORA/CENTRAL/vcredist_x64.log

################################################

Abort execution because of

controller.userDecideToStop

##############################################

INFO       2016-04-04 16:48:16.761 [synxcpath.cpp:776]

           CSyPath::createFile()

Creating file C:\Program Files\sapinst_instdir\.lastInstallationLocation.

INFO       2016-04-04 16:48:17.089 [synxcpath.cpp:776]

           CSyPath::createFile()

Creating file C:\Program Files\sapinst_instdir\ERPEhP4\AS-ABAP\ORA\CENTRAL\__instana_tmp.xml.

Apr 4, 2016 4:48:17 PM [Info]: Stopping services ...

Apr 4, 2016 4:48:17 PM [Info]: Stopping service "SAPinstService" ...

Apr 4, 2016 4:48:17 PM [Info]: Service "SAPinstService" stopped.

Apr 4, 2016 4:48:17 PM [Info]: Services stopped.

Apr 4, 2016 4:48:17 PM [Info]: Server shutdown by SAPinstService

Exit status of child: 2

Dear Experts,

I am facing a peculiar issue. In our SAP system(Linux platform)... the Development system and QAS system the root users can read the /sapmnt/SID/profile/Start Profile.

But in production it is showing the permission denied. though the permission for the start profile is same at all the systems.

I have shared the screens at below:

I am not getting any clue where all the permissions are same. And sap is running at all the systems. Can anybody help me ?

Regards

Asaduzzaman

Dear community,

does anybody know about using open-vm-tools on SLES11 in a vmware guest?

We are trying to use enhanced monitoring (from SAP note 1606643) - but have no success.

saposcol claims

WARNING: VMware guest library not found.

WARNING: Couldn't read path to VMware guest lib

Is enhanced monitoring possible with open-vm-tools or are the generic vm-tools needed?

Thanks in advanced

Stefan

Supported Linux Distributions:

The following Linux distributions are tested and certified for use in SAP environments. See also SAP note 171356:

Oracle:

• Oracle Linux 7 for x86_64
• Oracle Linux 6 for x86_64
• Oracle Linux 5 for x86_64

Red Hat:

• Red Hat Enterprise Linux 7 for x86_64, IBM System p and IBM System z
• Red Hat Enterprise Linux 6 for x86, x86_64, IPF, IBM System p and IBM System z
• Red Hat Enterprise Linux 5 for x86, x86_64, IPF, IBM System p and IBM System z 
• Red Hat Enterprise Linux 4 for x86, x86_64, IPF and IBM System p 
• Red Hat Enterprise Linux 3 for x86 and IPF (out of maintenance)
• Red Hat Enterprise Linux 2.1  for x86 (out of maintenance)
• Red Hat Linux 7.1 Professional (out of maintenance)
• Red Hat Linux 6.2 (out of maintenance)
• Red Hat Linux 6.1 Enterprise Version 1.0 (out of maintenance)

SUSE:

• SUSE Linux Enterprise Server 12 for x86_64 and IBM System z
• SUSE Linux Enterprise Server 11 for x86_64, IPF, IBM System p and IBM System z 
• SUSE Linux Enterprise Server 10 for x86, x86_64, IPF, IBM System p and IBM System z 
• SUSE Linux Enterprise Server 9  for x86, x86_64, IPF, IBM System p and IBM System z (out of maintenance)
• SUSE Linux Enterprise Server 8  for x86, IPF and IBM System z (out of maintenance) 
• SUSE Linux Enterprise Server 7  for IA32 and IBM System z (out of maintenance) 
• SUSE Linux Enterprise Server for IA32 (out of maintenance)

Supported Hardware:

Hardware which is generally certified by our hardware partners for the SAP product portfolio.

Here are the links to the partners' current hardware compatibility lists in alphabetical order. Please refer to the SAP Product Availability Matrix (PAM) for the SAP certification status of your specific SAP product release.

• Bull
• Cisco
• Dell
• Fujitsu
• Hitachi
• Huawei
• HP
• IBM
• Lenovo
• NEC
• Nutanix
• Oracle-Sun
• SGI
• Unisys
• VCE

General Remarks:

The Linux distributors provide updates for their software on a regular basis, e.g. for security reasons. These updates are checked for compatibility with SAP software by the distributors before they are released and, from SAP point of view, can be used immediately after availability also in production environments. This tested compatibility can only be granted when using the original packages provided by the distributors. Theses packages are available to you if you have a valid contract with the distributor or an authorized OEM. The same applies for "update collections" like Service Packs from SUSE or Updates by Oracle or Red Hat. SAP recommends always to use the newest "update collection" with recent online updates.

Related SAP Notes:

These links refer to the SAP service marketplace which is available to customers and partners only. You will need to log on with your SAP Service Marketplace password.

• SAP software on Linux: Essential comments (Note 171356)
• Oracle Linux 7.x SAP Installation and Upgrade (Note 2069760)
• Oracle Linux 6.x SAP Installation and Upgrade (Note 1635808)
• Oracle Linux 5.x SAP Installation and Upgrade (Note 1567511)
• Red Hat Enterprise Linux 7.x: Installation and Upgrade (Note 2002167)
• Red Hat Enterprise Linux 6.x: Installation and Upgrade (Note 1496410)
• Red Hat Enterprise Linux 5.x: Installation and Upgrade (Note 1048303)
• SUSE Linux Enterprise Server 12: Installation notes (Note 1984787)
• SUSE LINUX Enterprise Server 11: Installation notes (Note 1310037)
• SUSE LINUX Enterprise Server 10: Installation notes (Note 958253)

Find more notes related to SAP on Linux in the SCN Wiki: SAPonLinuxNotes

Are you concerned about any of these questions?

• How can you achieve zero-downtime for your mission critical SAP workloads?
• How can you automate SAP HANA system replications?
• What are the important steps to consider to move to S/4 HANA?
• As an SAP partner, where can you find guidance for migrating to S/4 HANA?
• What is the right cloud strategy for your SAP workloads?
• What do digital transformation and the third platform really mean for you?

For answers to these and other questions join SUSE at the SAPPHIRE NOW and ASUG Annual Conference, May 17-19. 2016 in Orlando, Florida. Just stop by the SUSE booth (#655) and talk to our experts on the topics that concern you most. Get tips and tricks from our technical specialists, watch demos, listen to success stories and connect with SUSE executives on strategies and roadmaps. You’ll also learn why SUSE Linux Enterprise Server for SAP Applications is the recommended and supported OS of choice for SAP HANA, on premise or in the cloud and why SAP runs SUSE for its own workloads.

How are SUSE partners and customers achieving success?

Listen to presentations from our ecosystem partners: AWS, Dell, Hitachi, Fujitsu, HP, Hitachi, IBM, Lenovo, Microsoft, NetApp, SGI, Huawei, DataVard (logo attached), NetApp, Protera, Wipro, TCS, VMWare and others.

Interested in running SAP solutions or SAP HANA in the cloud?

Learn how SAP customers can run SAP workloads in the private cloud using SUSE OpenStack Cloud or in the public cloud on the HANA Cloud Platform, Amazon or Microsoft Azure.

Looking for zero downtime for you mission-critical SAP applications?

Join our 20-minute discussion and learn how you can minimize your server downtime, maximize your service availability and build an environment that keeps SAP HANA running 24x7, 365 days a year.

More details for SUSE and partner sessions will be published soon.

We look forward to seeing you there.

Hi ,

I am facing issue in the database instance installation step " perform post load activities" for SCM 7.0 ehp3 system and not showing any errors.

CI is on linux and database is on AIX

what could be reason and what are all need to be checked.

I would appreciate your inputs and suggestions

Thanks in advance

Red Hat - an SAP Global Technology Partner

Welcome to the "SAP on Red Hat"  landing page where you can find information on confidently running SAP using Red Hat technologies including Red Hat Enterprise Linux (RHEL), Red Hat Enterprise Virtualization (RHEV), Cloud, and JBoss Middleware.

What's New

• SGI, a leader in high performance computing (HPC) and an early driver of big data technologies, has certified its SGI UV 300H server for Red Hat Enterprise Linux for SAP HANA. Read more
• Keynote at Red Hat Summit, by Steve Lucas, President of Platform Solutions at SAP. Watch it on youtube

What's In the Press

• Red Hat Enterprise Linux 7 is now certified for SAP Business Applications
  • SAP Note 2002167 - Red Hat Enterprise Linux 7.x: Installation and Upgrade

• Red Hat Deepens Collaboration with SAP on SAP® Data Management Portfolio, Launches Red Hat Enterprise Linux for SAP HANA®
  • Raleigh - June 2, 2014 - Red Hat Enterprise Linux now available across the entire SAP® Data Management Portfolio
  • As the foundation of the enhanced partnership, Red Hat Enterprise Linux is now available and qualified for production use of SAP HANA and supported by partners’ SAP-certified hardware solutions.
  • FULL STORY
  • Datasheet: Red Hat Enterprise Linux for SAP HANA
  • Whitepaper: CITO Research: Why you should put a Red Hat under your SAP systems
• Red Hat Teams with SAP to Bring Data Management Offerings to OpenShift

SAN FRANCISCO – RED HAT SUMMIT 2014, April 16, 2014 - Industry leaders cooperate to bring SAP® database technologies to developers with new cartridges for Red Hat’s award-winning Platform-as-a-Service portfolio. FULL STORY

• Guinness World Records: The largest data warehouse contains 12.1 petabytes (12,100 terabytes) of raw data, achieved by a collaboration between SAP (Germany), BMMsoft, HP, Intel, NetApp and Red Hat (all USA) at the HP Lab, Santa Clara, California, USA, on 17 February 2014.
• SAP Sybase IQ Software Smashes Previous Results and Sets World Record for Fastest Loading of Big Data

June 25, 2013 by SAP News WALLDORF - SAP today announced that version 16 of SAP Sybase IQ software has achieved a Guinness World Record for loading and indexing big data. In cooperation with BMMsoft, HP and Red Hat, SAP Sybase IQ 16 achieved an audited result of 34.3 terabytes per hour*, far surpassing the previous record of 14 terabytes per hour achieved by the same team using a previous version of SAP Sybase IQ.

IN THE SAP PRESS

• Red Hat Expands Technical Account Management Services to Offer SAP® Solution-centric Support

Raleigh, N.C. and ORLANDO, Fla. - SAP SAPPHIRE NOW - May 14, 2013 - Red Hat, Inc. (NYSE: RHT), the world’s leading provider of open source solutions, today announced it has expanded its Technical Account Management Services portfolio to include specific support for SAP® solutions. Now, Red Hat customers who also use SAP products can benefit from Red Hat Technical Account Managers (TAMs) specializing in SAP solutions, allowing customers to benefit from the TAMs' in-depth knowledge and expertise and proactive guidance.

FULL STORY

• Keynote@Summit: Irfan Khan, senior vice president and chief technology officer of the Database and Technology Group at Sybase (an SAP company), gives a keynote at the 2012 Red Hat Summit and JBoss World.

Customer Success Stories

Bayer Business Services lowers cost, achieves performance

Generali SAP Migration Success Story - REALTECH

Munich Re - REALTECH

Eli Lilly Case Study - Intel

Red Hat Provides CEPSA with a Scalable, Standardized, High-Availability SAP Platform

Bilcare research cost-effectively scales for Business Growth with Red Hat Enterprise Linux with Integrated Virtualization

Purdue University gives high grade to HP Converged Infrastructure (2012 - SAP, RHEL, VMware, HP Technical Services case study)

Red Hat Enterprise Linux for SAP Business Applications

RHN KnowledgeBase Article: What is "Red Hat Enterprise Linux for SAP Business Applications" Subscription?

Datasheet: SAP and Red Hat Enterprise Linux

Red Hat Enterprise Linux for SAP HANA

Product Page

Getting The most from Red Hat Enterprise Linux And SAP HANA platform

RHN KnowledgeBase Article: What is "Red Hat Enterprise Linux for SAP HANA" Subscription?

FAQ - RHEL for SAP HANA

Red Hat Enterprise Virtualization (RHEV)

Product Page

Virtualization Datasheets

High Availability Solution for SAP

RHEL 6.5 HA add-on (with pacemaker) has passed the SAP HA Interface certification inDecember 2013, see High Availability Partner Info

Performance - SD Benchmark

Published SAP SD Benchmarks on Red Hat

JBoss Enterprise Middleware (SCN Page)

The long-standing collaboration between Red Hat and SAP is thriving. Engineers from both companies are working together with a focus on developing new tools to further the integration of SAP Business Suite with enterprise Java applications running on JBoss Enterprise Middleware. The aim of such integration, of course, is a more intelligent, integrated enterprise — one that can maximize the value of your data assets and accelerate business decisions.  Learn More

Technical Resource Library

SAP Notes on Red Hat

SAP on Red Hat Technical Documents

Communication

Should you have any question on Red Hat products or solutions for SAP, please email sap@redhat.com

Red Hat Enterprise Linux for SAP Business Applications (RHEL for SAP)

• Large-Scale SAP BusinessObjects Bi 4 Platform Deployment Over SAP Sybase® ASE and SAP Sybase IQ Databases– SAP SCN
  • This white paper describes the outcome of a project enabled by SAP Co-Innovation Lab to validate the performance and scalability of a large-scale deployment of the SAP® BusinessObjects™ Business Intelligence (BI) platform, release 4, capable of sustaining ten thousand plus concurrent users. The SAP BusinessObjects BI platform and database technologies were configured to run over a standard enterprise-ready open source operating system from Red Hat (RHEL 6), using enterprise data center–ready Intel® Xeon® processor-based hardware from Supermicro (TwinBlades and SuperServers) and an application delivery control system from F5.
  • Download

• SAP-SD benchmark using Red Hat Enterprise Linux 6.2
  • On the latest 2-tier SAP SD standard application benchmark results for Linux® servers:

1. Red Hat® Enterprise Linux 6 achieved the highest SAP SD benchmark score (number of users) on a single 4-socket system. This was achieved by: Fully utilizing all 40 cores and 80 threads, and Running DB2 9.7 and the SAP enhancement package 4 for SAP ERP 6.0.
2. Red Hat Enterprise Linux 6 achieved the highest SAP SD benchmark score (number of users) on a single 8-socket system. This was achieved by: Fully utilizing all 80 cores and 160 threads and Running MaxDB 7.8 and the SAP enhancement package 4 for SAP ERP 6.0.

• Download

High Availability

• Automated SAP HANA System Replication with Pacemaker on RHEL Setup Guide
  • As SAP HANA moves to take on a more central function as the primary database platform for SAP landscapes, requirements for stability and reliability increase dramatically. Red Hat Enterprise Linux for SAP HANA with High Availability and Smart Management meets those requirements by enhancing native SAP HANA replication and failover technology to automate the failover process. During a failover in a typical SAP HANA deployment, a system administrator must manually point the application to the secondary server. The Red Hat Enterprise Linux for SAP HANA with High Availability and Smart Management uses Pacemaker resource agents to complete the switch from primary to secondary server.
  • Download
    
• Deploying Highly Available SAP NetWeaver-based Servers Using Red Hat Enterprise Linux HA add-on with Pacemaker
  • Paper describes how to set up a two-node-cluster solution that conforms to the guidelines for high availability that have been established by both SAP and Red Hat. It is based on SAP NetWeaver on top of Red Hat Enterprise Linux 6.5 with RHEL HA Add-on. In addition to describing the the technical prerequisites for setting up a highly available SAP NetWeaver system on RHEL, it also provides provides an example showing a working SAP HA solution using Red Hat Enterprise Linux HA add-on with Pacemaker.
  • Download

KVM, Red Hat Enterprise Virtualization (RHEV), and Cloud

• RHEL6 KVM and Cisco VM-FEX performance with SAP ERP
  • This document shows how you can improve virtualized SAP ERP performance with Red Hat® Enterprise Linux® and Cisco Data Center VM-FEX.
  • Download

• SAP SD benchmark running in a VM: Leadership performance using Red Hat Enterprise Linux 6/KVM
  • Red Hat® Enterprise Linux® 6/KVM demonstrated excellent virtualization efficiency (of 85%). Red Hat Enterprise Linux 6/KVM demonstrated the best SAP SD benchmark performance among all published SAP SD results using various virtualization technologies.
  • Download

• RHEL 6 KVM and tuned-adm analysis on Sybase IQ 15.4
  • This paper examines the performance characteristics of tuned-adm profiles and Kernel-based Virtual Machine (KVM) on Red Hat® Enterprise Linux® 6 with Fusion-io technology. A DSS type workload deployed on Sybase IQ 15.4 serves as the benchmark characterized.
  • Download

• Scaling SAP in a RHEV 3 Environment 2012
  • This paper discusses the scaling of SAP running in Red Hat Enterprise Linux 6 virtual machines. The virtual machines are running in a Red Hat Enterprise Virtualization (RHEV) 3.0 environment using a Red Hat Enterprise Linux 6 server as the hypervisor. The workload used to perform the scaling tests for this paper was Version 2.3 of the SAP LinuxLab Certification Suite (SLCS) running the ERP2005 SR1.
  • Download

• Installing SAP on Red Hat Enterprise Virtualization (RHEV) 3.0
  • This document describes the installation of the SAP Business Suite Application in a Red Hat® Enterprise Virtualization 3.0 environment, and is intended as a starting point for evaluating or planning an SAP on Red Hat Enterprise Virtualization deployment.
  • Download

• Running SAP on Red Hat Enterprise Virtualization 3
  • Running SAP solutions on Red Hat® Enterprise Linux® and Red Hat Enterprise Virtualization helps enterprises address the challenges of flexibility and price/performance with a scalable and highly available SAP platform that is cloud-ready.
  • Download

JBoss Enterprise Middleware

• JBoss SAP JCA Connector Architecture and Implementation
  • The JBoss SAP JCA Connector is a Resource Adapter for the JBoss Application Server 7 (JBoss AS7) platform which provides connectivity from the JBoss AS7 platform to SAP® R/3 Enterprise Information Systems (SAP EIS).
  • Download

Related Links

SAP on Red Hat | SCN: stay tuned and learn more about Red Hat solutions for SAP. We offer a broad range of solutions across RHEL, HA, Virtualization, Cloud, and Middleware, etc.

Visit the SUSE SAP Team at Sapphire 2016 on booth 655

If you're looking for answers to the following questions, please come by as we can answer them:

• How can you achieve zero-downtime for your mission critical SAP workloads?
• How do you automate SAP HANA system replications?
• What are the important steps to consider to move to S/4 HANA?
• As an SAP partner, where can you find guidance for migrating to S/4 HANA?
• What is the right cloud strategy for your SAP workloads?
• What do digital transformation and the third platform really mean for you?

Get tips and tricks from our technical experts, watch demos, listen to success stories and connect with SUSE executives on strategies and road-maps. You’ll also learn why SUSE Linux Enterprise Server for SAP Applications is the recommended and supported OS of choice for SAP HANA, on premise or in the cloud and why SAP runs SUSE for its own workloads.

SUSE Presentation

May 17, 11:30 AM, Mini-theater PS603: Zero Downtime for SAP HANA, Hannes Kuehnemund, SUSE

Downtime isn’t an option. Whether planned downtime for SAP HANA, or the more unpredictable unplanned downtime from failures or even nature disasters, your business is incurring business loss. You're under pressure to supply more up-time in data center to stay competitive and meet customer demands. Join our 20min discussion and learn how you can minimize your server downtime, maximize your service availability and build an environment that keeps SAP HANA running 24x7, 365 days a year.

How are SUSE partners and customers achieving success?

Listen to on-booth presentations from our ecosystem partners: AWS, Dell, Hitachi, Fujitsu, HPE, Hitachi, IBM, Lenovo, Microsoft, NetApp, SGI, Huawei, DataVard, Protera, Wipro, TCS, VMWare and others.

On booth presentation agenda:

See you there!

Dear experts,

We are trying to upgrade SAP ERP 6.0 Ehp 5 using Software Update Manager tool 1.0 remotely from my desktop. OS version: Linux RHEL 6.5. DB version: Oracle 11.2.

While executing the command ./STARTUP from SUM folder, GUI is opening from browser but can not connect to guiport 4241. The error shows,

Error while connecting to communication partner.

Could not connect to host <hostname> on port 4241.

java.net.ConnectException: Connection refused: connect

java.net.ConnectException: Connection refused: connect    

Taking reference from other blogs, we have tried using other ports (guiport 4242,4243), but no luck.

Took reference from Note. 1238121 - SAP JVM for Software Logistics Tools, set the environment variants JCE_POLICY_ZIP, still it didn't work.

Stopped the default router of OS using iptables, didn't work.

I am attaching the DETECT.TRC log from ..//SUM/sdt/trc folder.

<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[2.0.7.1006]/-->

<!--NAME[/usr/sap/trans/SUM/sdt/trc/DETECT.TRC]/-->

<!--PATTERN[DETECT.TRC]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %-100l [%t]: %m)]/-->

<!--ENCODING[UTF8]/-->

<!--LOGHEADER[END]/-->

Apr 23, 2016 12:41:25 PM [Error]:                                                                    com.sap.sdt.dmt.DMTFactoryManager [Thread[main,5,main]]: Property file dmt.properties not found in class path

Apr 23, 2016 12:41:26 PM [Error]:                                                                  com.sap.sdt.jspm.JspmFactoryManager [Thread[main,5,main]]: Property file jspm.properties not found in class path

Apr 23, 2016 12:41:26 PM [Error]:                                                                    com.sap.sdt.dmt.DMTFactoryManager [Thread[main,5,main]]: Property file dmt.properties not found in class path

Apr 23, 2016 12:41:26 PM [Error]:                                                                  com.sap.sdt.jspm.JspmFactoryManager [Thread[main,5,main]]: Property file jspm.properties not found in class path

Apr 23, 2016 12:41:28 PM [Error]:                                                               com.sap.sdt.tools.var.XMLFileConverter [Thread[main,5,main]]: File /usr/sap/trans/SUM/sdt/config/./JUP.J2EE.xml does not exist.

What could be wrong? Am I missing something? Or is there any network issue from server to my local desktop?

Please help me out.

Thanks,

Joy

HOW TO SET UP SAPHanaSR IN THE COST OPTIMIZED SAP HANA SR SCENARIO

To make this article a bit more easy to edit, I have split the article into 3 parts:

• Part 1 (http://scn.sap.com/docs/DOC-65899) describes the concept, the setup of the SUSE Linux Enterprise Server for SAP Applications and the set-up and installation of SAP HANA
• Part 2 (http://scn.sap.com/docs/DOC-68633) describes the cluster configuration and SAP HANA integration into the cluster
• Part 3 describes the test cases

4  Setup and configure SUSE Linux Enterprise High Availability

This section of the article describes the configuration of the cluster framework SUSE Linux Enterprise High Availability Extension, which is part of the SUSE Linux Enterprise Server for SAP Applications and SAP HANA Database Integration.

4.1  Install the HA software packages and SAPHanaSR resource agents on both cluster nodes

If not already done, install the software packages with YaST. Alternatively, you can install them from the command line with zypper. This has to be done on both nodes.

suse01:~> zypper in -t pattern ha_sles
suse01:~> zypper in SAPHanaSR
suse01:~> zypper in ClusterTools2  # optional

For more information please read Section 3.2.2 Initial Cluster Setup of SUSE Linux Enterprise High Availability Extension

4.2  Configure cluster communication on the first node

First we have to setup the base cluster framework. For convenience use YaST2 or the sleha-init (on node1) and sleha-join (on node2) scripts. These scripts create a working configuration proposal, but for production you had to customize this configuration. It is although strongly recommended to add a second cluster communication ring. The cluster communication protocol should be changed to unicast (UCAST) and the timeout values must be adjusted according to your network characteristics.

We call sleha-init to create a cluster configuration on node 1 (suse01). After adapting the configuration we will run sleha-join on node 2 (suse02)  to complete the basic cluster configuration.

To configure the cluster stop the first node and change the cluster communication settings with your preferred editor. These changes are activated when we start the cluster again.

suse01:~ # rcopenais stoppin
suse01:~ # vi /etc/corosync/corosync.conf

The following sample configuration for /etc/corosync/corosync.conf shows how to add a second ring and switch from multicast to unicast (UCAST):

totem {     ...    interface {          ringnumber:     0        #Network Address to be bind for this interface setting        bindnetaddr:    192.168.1.0        member {            memberaddr:     192.168.1.10        }        member {            memberaddr:     192.168.1.11        }        #The multicast port to be used        mcastport:      5405        #The ringnumber assigned to this interface setting    }      interface {          ringnumber:     1        #Network Address to be bind for this interface setting        bindnetaddr:    192.168.2.0        member {            memberaddr:     192.168.2.10        }        member {            memberaddr:     192.168.2.11        }        #The multicast port to be used        mcastport:      5415        #The ringnumber assigned to this interface setting    }    #How many threads should be used to encypt and sending message.     threads:        4     #     transport:      udpu     #How many token retransmits should be attempted before forming     # a new configuration.     token_retransmits_before_loss_const:    10     #To make sure the auto-generated nodeid is positive     clear_node_high_bit:    new     ...
}

4.2.1  Configure SBD for STONITH fencing

You can skip this section if you do not have any SBD devices, but be sure to implement an other supported fencing mechanism. If you use the latest version of the pacemaker packages from the SUSE maintenance-channels, the -P option (Check Pacemaker quorum and node health) is available, which enables the cluster nodes not to self-fence if SBDs are lost, but pacemaker communication is still available. The timeout parameter -t defines the reprobe intervall for the SBD device in seconds. It is highly recommended to configure a watchdog for SDB devices to protect against failures of the SBD process itself. Please refer to the SLES manual for setting up a watchdog.

Replace /dev/disk/by-id/SBDA and SBDB by your SBD device names in the example configuration file.

# /etc/sysconfig/sbd
SBD_DEVICE="/dev/disk/by-id/SBDA;/dev/disk/by-id/SBDB"
SBD_OPTS="-W -S 1 -P -t 300"

4.2.2  Verify the SBD device

You can skip this section, if you do not have any SBD devices, but be sure to implement an other supported fencing mechanism..

It's a good practice to check, if the SBD device could be accessed from both nodes and does contain valid records. Check this for all devices configured in /etc/sysconfig/sbd.

suse01:~ # sbd -d /dev/disk/by-id/SBDA dump
==Dumping header on disk /dev/disk/by-id/SBDA
Header version     : 2.1
UUID               : 0f4ea13e-fab8-4147-b9b2-3cdcfff07f86
Number of slots    : 255
Sector size        : 512
Timeout (watchdog) : 20
Timeout (allocate) : 2
Timeout (loop)     : 1
Timeout (msgwait)  : 40
==Header on disk /dev/disk/by-id/SBDA is dumped
The timeout values in our sample are only common values, which need to be tuned in your environment.
To check the current SBD entries for the various cluster nodes you can use “sbd list”. If all entries are “clear” no fencing task is marked in the SBD device.
suse01:~ # sbd -d /dev/disk/by-id/SBDA list
0       suse01  clear
1       suse02  clear

For more information on SBD configuration parameters, please read section 17.1.3 of SUSE Linux Enterprise High Availability Extension.

Now it's time to start the cluster on node 1 (suse01) again (rcopenais start).

4.3  Configure cluster communication on the second node

After we have adapted the cluster configuration on node 1 and prepared the SBD fencing (if you use this type of STONITH device) we can join node 2 (suse02) to the cluster. The procedure will inherit all changes from node 1:

suse02:~ # sleha-join
suse02:~ # rcopenais status

4.4  Basic pacemaker configuration

After we have completed the cluster communication and have two active nodes in our cluster we can proceed with the the pacemaker cluster configuration:

node suse01 \    description="PRDp"
node suse02 \    description="PRDs and QAS"
property $id="cib-bootstrap-options" \        no-quorum-policy="ignore" \        stonith-enabled="true" \        stonith-action="reboot" \        stonith-timeout="150s"
rsc_defaults $id="rsc-options" \        resource-stickiness="1000" \        migration-threshold="5000"
op_defaults $id="op-options" \        timeout="600"

To add resources, constraints or other definitions you should create a text file containing the crm definition and load the definition to the cluster:

suse01:~ # vi crm-bs.txt
...
suse01:~ # crm configure load update crm-bs.txt

4.5  Setup the STONITH fence mechanism

4.5.1  Using SBD as fencing mechanism

The integration of the SBD STONITH mechanism into the pacemaker cluster configuration is quite easy. Just add the following crm resource definition to your cluster:

primitive stonith-sbd stonith:external/sbd \     op start interval="0" time="15" start-delay="5"

To add resources, constraints or other definitions you should create a text file containing the crm definition and load the definition to the cluster:

suse01:~ # vi crm-sbd.txt
...
suse01:~ # crm configure load update crm-sbd.txt

4.5.2  Using IPMI as fencing mechanism

Instead of using SBD for fencing you can use remote management boards compatible with the IPMI standard. Our cluster configuration example below shows the usage of the IPMI STONITH devices.

For further information about fencing, see SUSE Linux Enterprise High Availability Guide.

For the IPMI based fencing you need to configure a primitive per cluster node. Each resource is responsible to fence exactly one cluster node. You need to adapt the IP addresses and login user / password of the remote management boards to the STONITH resource agent. We recommend to create a special STONITH user instead of providing root access to the management board. The location rules defining that a host should never run its own STONITH resource are:

primitive rsc_suse01_stonith stonith:external/ipmi \    params hostname="suse01" ipaddr="10.1.1.210" userid="stonith" passwd="k1llM3" interface="lanplus" \    op monitor interval="1800" timeout="30"
primitive rsc_suse02_stonith stonith:external/ipmi \    params hostname="suse02" ipaddr="10.1.1.211" userid="stonith" passwd="k1llM3" interface="lanplus" \    op monitor interval="1800" timeout="30" \
location loc_suse01_stonith rsc_suse01_stonith  -inf: suse01
location loc_suse02_stonith rsc_suse02_stonith  -inf: suse02

4.5.3  Using other STONITH fencing mechanisms

We recommend to use SBD (best practice) or IPMI (second choice) as STONITH mechanism. The SUSE Linux Enterprise High Availability product also supports additional fencing mechanism not covered here.

For further information about fencing, see SUSE Linux Enterprise High Availability Guide.

5  Integrating the Control of the HANA databases into the Cluster

5.1  Setup of cluster resources for SAPHanaSR

Follow the setup guide of SAPHanaSR.

Remark: For SAP HANA SPS9+ and SAPHanaSR 0.152+ you can skip all activities to create SAP HANA database users and secure store keys for the productive system. The system controlled via SAPDatabase and SAPHOSTAGENT still needs the user secure store key.

This snippet describes the cluster configuration part for the SAP HANA productive database (SLE) and the virtual IP address for the client access: We refer to the cluster nodes as suse01 and suse02 respectively:

primitive rsc_ip_SLE_HDB00 ocf:heartbeat:IPaddr2 \    meta target-role="Started" \    op monitor interval="10s" timeout="20s" \    params ip="192.168.1.100"
primitive rsc_SAPHanaTopology_SLE_HDB00 ocf:suse:SAPHanaTopology \    op monitor interval="10" timeout="30" start_delay="10" \    op start interval="0" timeout="600" \    op stop interval="0" timeout="600" \    params SID="SLE" InstanceNumber="00"
primitive rsc_SAPHana_SLE_HDB00 ocf:suse:SAPHana \    op monitor interval="60" role="Master" timeout="3600" \    op monitor interval="61" role="Slave" timeout="3600" \    op promote interval="0" timeout="3600" \    op start interval="0" timeout="3600" \    op stop interval="0" timeout="3600" \    params SID="SLE" InstanceNumber="00" \      PREFER_SITE_TAKEOVER="false" \      DUPLICATE_PRIMARY_TIMEOUT="7200" \      AUTOMATED_REGISTER="false"
ms msl_SAPHana_SLE_HDB00 rsc_SAPHana_SLE_HDB00 \    meta clone-max="2" clone-node-max="1" master-max="1" \      interleave="true" priority="1000"
clone cln_SAPHanaTopology_SLE_HDB00 rsc_SAPHanaTopology_SLE_HDB00 \    meta clone-node-max="1" target-role="Started" interleave="true"
colocation col_saphana_ip_SLE_HDB00 2000: rsc_ip_SLE_HDB00 \      msl_SAPHana_SLE_HDB00:Master
order ord_SAPHana_SLE_HDB00 Optional: cln_SAPHanaTopology_SLE_HDB00 \      msl_SAPHana_SLE_HDB00

5.1.1  Add the cluster resource for the non-productive SAP HANA database

This snippet describes the cluster configuration part for the SAP HANA QAS database:

We refer to the cluster nodes as suse01 and suse02 respectively:

primitive rsc_SAP_QAS_HDB10 ocf:heartbeat:SAPDatabase \    params DBTYPE="HDB" SID="QAS" \    MONITOR_SERVICES="hdbindexserver|hdbnameserver" \    op start interval="0" timeout="600" \    op monitor interval="120" timeout="700" \    op stop interval="0" timeout="300" \    meta priority="100"

5.1.2  Adding the cluster rules for the automatic shutdown of SAP HANA QAS

We refer to the cluster nodes as suse01 and suse02 respectively:

location loc_QAS_never_suse01 rsc_SAP_QAS_HDB10 -inf: suse01
colocation col_QAS_never_with_PRDip -inf: rsc_SAP_QAS_HDB10:Started rsc_ip_SLE_HDB00
order ord_QASstop_before_PRDpromote inf: rsc_SAP_QAS_HDB10:stop msl_SAPHana_SLE_HDB00:promote

The next step is now to running cluster tests.

Hi Experts,

When i enter isql command in my redhat linux server show the message like

not able to login isql server,what to do? how to solve this problem?

Regards,

Dinesh Kumar S.

Hi,

I'm getting NullPointerException when starting SAPGUI 7.40 rev 2 on my Linux box (RedHat Enterprise Linux 7.2 / Open Client).

[nza@t450 bin]$ ./guilogon

Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException

        at com.sap.platin.base.logon.landscape.LandscapeUtil.addBackup(LandscapeUtil.java:1292)

        at com.sap.platin.base.logon.landscape.LandscapeUtil.getCachedLandscape(LandscapeUtil.java:865)

        at com.sap.platin.base.logon.landscape.LandscapeUtil.getCachedLandscape(LandscapeUtil.java:842)

        at com.sap.platin.base.logon.util.GlobalConnectionData.loadLandscape(GlobalConnectionData.java:73)

        at com.sap.platin.base.logon.util.GlobalConnectionData.loadLandscape(GlobalConnectionData.java:44)

        at com.sap.platin.base.config.GuiConfiguration.loadDefaultLandscape(GuiConfiguration.java:1032)

        at com.sap.platin.base.config.GuiConfiguration.getLandscape(GuiConfiguration.java:995)

        at com.sap.platin.base.logon.GuiLogonLS.loadLandscape(GuiLogonLS.java:1871)

        at com.sap.platin.base.logon.GuiLogonLS.initViewType(GuiLogonLS.java:1177)

        at com.sap.platin.base.logon.GuiLogonLS.initComponents(GuiLogonLS.java:508)

        at com.sap.platin.base.logon.GuiLogonLS.<init>(GuiLogonLS.java:342)

        at com.sap.platin.base.logon.GuiLogonLS.getLogonFrame(GuiLogonLS.java:2078)

        at com.sap.platin.base.logon.GuiLogonManager.getLogonFrame(GuiLogonManager.java:63)

        at com.sap.platin.base.logon.GuiLogonManager.setVisibleLogonFrame(GuiLogonManager.java:83)

        at com.sap.platin.base.logon.GuiImpl$2.run(GuiImpl.java:158)

        at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)

        at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)

        at java.awt.EventQueue.access$500(EventQueue.java:97)

        at java.awt.EventQueue$3.run(EventQueue.java:709)

        at java.awt.EventQueue$3.run(EventQueue.java:703)

        at java.security.AccessController.doPrivileged(Native Method)

        at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)

        at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)

        at com.sap.platin.micro.event.GuiEventQueue.dispatchEvent(GuiEventQueue.java:79)

        at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)

        at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)

        at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)

        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)

        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)

        at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

Environment:

[nza@t450 bin]$ ./guilogon -checkscript

guilogon -checkscript output:

Before processing:

  PLATINHOME      =

  PLATIN_JAVA     = /home/nza/soft/jre1.8.0_91/bin/java

  uname           = Linux

  PATH            = /usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/opt/ibm/c4eb/bin:/home/nza/.local/bin:/home/nza/bin:/usr/kerberos/bin:/home/nza/sqllib/bin:/home/nza/sqllib/adm:/home/nza/sqllib/misc

After processing:

  THISSCRIPTPATH  = ./../../SAPGUI7.40rev2/bin/guilogon

  PLATINHOME      = /opt/ibm/sap/SAPGUI7.40rev2

  PLATIN_JAVA     = /home/nza/soft/jre1.8.0_91/bin/java

  PLATIN_DEBUG    =

  JRE_ARGS        = -Xms32M -Xmx512M

  START_JARS      = /opt/ibm/sap/SAPGUI7.40rev2/jar/GuiStartS.jar

  STARTCLASS      = com.sap.platin.Gui

  RFC_TRACE       =

Command to start:

  /home/nza/soft/jre1.8.0_91/bin/java -Xms32M -Xmx512M -cp /opt/ibm/sap/SAPGUI7.40rev2/jar/GuiStartS.jar com.sap.platin.Gui 

[nza@t450 bin]$ /home/nza/soft/jre1.8.0_91/bin/java -version

java version "1.8.0_91"

Java(TM) SE Runtime Environment (build 1.8.0_91-b14)

Java HotSpot(TM) Server VM (build 25.91-b14, mixed mode)

[nza@t450 bin]$ uname -r

3.10.0-327.13.1.el7.x86_64

[nza@t450 bin]$ yum list installed | grep qt

ibus-qt.x86_64                   1.3.2-4.el7             @base/$releasever     

imsettings-qt.x86_64             1.6.3-9.el7             @base/$releasever     

qt.i686                          1:4.8.5-11.el7          @base/$releasever     

qt.x86_64                        1:4.8.5-11.el7          @base/$releasever     

qt-settings.noarch               19-23.5.el7             @base/$releasever     

qt-x11.i686                      1:4.8.5-11.el7          @base/$releasever     

qt-x11.x86_64                    1:4.8.5-11.el7          @base/$releasever     

qt3.x86_64                       3.3.8b-51.el7           @base/$releasever

(This conf above is with 32bit Java, but is failing with the system-default 64bit 1.8.0_91-b14 Oracle Java too)

Do you sell software or services that supports SAP solutions?

In case you haven't heard, we have just launched an ingenious program SUSE Connect that provides a discovery zone for software, web services and special services like consulting from within SUSE Linux Enterprise Server for SAP Applications.

The idea is to make it really easy for customers to find related partner products and offerings and to connect our partners to our customers.

Customers can review the list of partner products and offerings, choosing to try or learn more about those that will meet their specific business needs, such as high availability and data center modernization.

All partner software products are tested and certified with SUSE Linux Enterprise, and trial versions can be automatically installed to a customer server through the SUSE Linux Enterprise Server for SAP Applications administration framework (YaST) for free testing. For web services or special services such as consulting, customers can browse information about them through SUSE Connect and connect directly to the solution or service website.

SUSE and SAP Partners can get application information by sending an email to sapalliance@suse.com.

See www.suse.com/suseconnect for more information.

Just one more way SUSE is ensuring that we adapt so you succeed.

hi i got this run time error for a stamdard transaction..can anyboby throw some light?

LOAD_TYPEPOOL_VERSION_MISMATCH

02.08.2007 21:23:11

ShrtText

Type group was changed at runtime.

What happened?

Error in ABAP application program.

The current ABAP program "SAPLCOBADI" had to be terminated because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

What can you do?

Print out the error message (using the "Print" function)

and make a note of the actions and input that caused the

error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

is especially useful if you want to keep a particular message.

The system attempted to correct the error

automatically, so you should try to restart

the program.

The type group "COBAI" was changed while the program was running, so that an

inconsistence occurred at runtime.

The type group "COBAI" has the version 20070627153024.

The program "%_CCOBAI" uses the version 20070802190113.

The internal session was started at 20070802212309.

hi all

i has just finish  system copy from AIX on oracle central installation to  SUSE on oracle distributed installation

and it finished successfully and i was able to login and use the system .

after i restart the db server and the instance server only the DB start but the sap instant did not start with error

sbsapr3:vzaadm 51> startsap

Database VZA must be started first

Log on to remote server and start database

sbsapr3:vzaadm 52>

ps i make the restart after i update the libuuid1

thanks

Hello,

do you have nay guide or best practice how to configure SAP web dispatcher with Red Hat High availabllity(pacemaker)?

Regards,

Jinkoo

Hello,

I've installed SUM on SLES 12  with SAP  and MaxDB. While I'm on second step (Configuration) called: "Determine JDBC driver" I've got error:

-----

Error in Determine JDBC driver

The following error has occured during the execution of the current step:

Error while executing Task with input file ReadProfiles.xml and task READ_DB_DRIVER_LOCATION. Task READ_DB_DRIVER_LOCATION not found in configuration file ReadProfiles.xml.

For more information, see the files /backup/SUM/sdt/log/SUM/DETERMINE-JDBC-DRIVER_01.LOG and ProcessOverview.html.

To troubleshoot the problem use the provided information. An SAP Note may provide a solution to this problem. Search for SAP Notes with the following

keywords:

SUM  configure  prepare-configuration  determine-jdbc-driver  com.sap.sdt.j2ee.services.servicesimpl.EngineProfileService  class com.sap.sdt.util.diag.DiagException

You may now do one of the following:

Repeat step from point of failure. After you have corrected the error, you can repeat the step from the exact point where the error occurred.

-----

This is what cat command on log mentioned in error content returns:

-----

cat /backup/SUM/sdt/log/SUM/DETERMINE-JDBC-DRIVER_01.LOG

<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[2.0.7.1006]/-->

<!--NAME[/backup/SUM/sdt/log/SUM/DETERMINE-JDBC-DRIVER_01.LOG]/-->

<!--PATTERN[DETERMINE-JDBC-DRIVER_01.LOG]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%6s]: %m)]/-->

<!--ENCODING[UTF8]/-->

<!--LOGHEADER[END]/-->

Mar 18, 2016 12:57:53 PM [Info  ]: Configuration has been built from input file /backup/SUM/sdt/config/ReadProfiles.xml.

Mar 18, 2016 12:57:53 PM [Info  ]: Global configuration has been built from input file /backup/SUM/sdt/config/ReadProfiles.xml.

Mar 18, 2016 12:57:54 PM [Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Error while executing Task with input file ReadProfiles.xml and task READ_DB_DRIVER_LOCATION.

Task READ_DB_DRIVER_LOCATION not found in configuration file ReadProfiles.xml.

-----

I've read everything in google what I could about that problem, but still I don't have any idea to solve ths.

Can you help me?

OPEN SOCIETY

In many ways the SAP community is undergoing a constant transformation process. The meta level is Digital Change Management. In practice, the SAP customer is observing a transition from a black box R/3 to S/4 based on Open Source. Terms, such as Linux, OpenStack, Apache, Hadoop are ever-present. E-3 journalists have written this feature story with the help of representatives from Suse Linux, Fujitsu, NetApp, Realtech and B1 Systems. An initial view of the future open ERP platform S/4 Hana.

The digital transformation process is the motor for important and long-term changes in the SAP ecosystem. This evolution is increasingly driven by Open Source ideas and projects. „Everyone is talking about OpenStack and it is slowly appearing more and more in the IT infrastructures of German companies“, wrote René Büst, an analyst from Crisp Research, in a blog. „58% of German CIOs regard OpenStack to be a real alternative to existing cloud management solutions. However, we should look more closely at what is currently in the hands of IT decision-takers. After all, OpenStack is basically just an infrastructure management solution and does not generate a direct value towards the success of your company.“

Hadoop & OpenStack

From the SAP community viewpoint Linux, OpenStack, Hadoop, Apache, etc. are almost a revolution. Access to R/3 data was restricted for a long time and was only possible at best via NetWeaver, RFC (Remote Function Calls) and SAP Business Connector. A long-serving CIO must regard Linux, Hadoop, OpenStack and the rest as a real „liberating step“. „Suse Linux provides open standards and an optimal Euro/SAPS ratio. In other words, Suse Linux and Intel provide optimal cost structures for SAP infrastructures“, explained Michael Jores to E-3 senior editor Peter Färbinger. He adds: „The combination of Hana and Linux paves the way towards a future-oriented state-of-the-art SAP infrastructure regarding open standards and cloud readiness. Infrastructures with Linux and Hana can thus be optimally prepared for future big data and cloud operations in the SAP data center.“

OpenStack as infrastructure management is already the de-facto standard for an Open Source based platform solution (see the interview with Fujitsu CTO Joseph Reger). The willingness of SAP last year to support OpenStack has resulted in an increasing number of existing customers relying on the module Open Source IaaS cloud platform as part of their cloud initiatives, stated Ralph Dehner from B1 Systems. Suse also recognized this development

at an early stage and provided OpenStack Cloud as the world‘s first Enterprise product for OpenStack. Suse, as a member of the OpenStack Foundation, also provides Alan Clark as the chairman of this important group, which coordinates and ensures the further development of OpenStack. SAP itself is also an official member. „We have already established best practices for deploying SAP on the Suse OpenStack Cloud“, explained Jores.

Hadoop and Hana can be used to implement a comprehensive big data strategy in order to link up the best of the structured and non-structured data worlds. „And Linux showed the way for OpenStack and Hadoop“, said Michael Jores. „Since 1999

Linux has quietly evolved into the strategic SAP platform so that Linux today is already the exclusive technology platform for Hana; SAP has also already become a member of the OpenStack community and uses OpenStack productively in its data center. This means that Open Source is systematically moving into the SAP data center.“ Professor Heiner Diefenbach from Fujitsu added in an E-3 interview: „Open Source enables you to move away from proprietary Unix systems and to introduce standardized architectures. This topic has been of great significance for quite a while in the SAP environment. And this will definitely not lessen.“

Big data & cloud

Heiner Diefenbach is optimistic with regard to Open Source: „The SAP community is very open towards this topic; many SAP customers already use Linux and the amount of know-how available is thus really high – and we believe it will improve even more.“ SAP can cover its two core strategies with Linux, Hadoop and OpenStack, on the one hand big data where Hana and Hadoop are a couple and, on the other hand, OpenStack which underpins the SAP cloud strategy and is to be the basis for further cloud adaptations within the market. „Suse has closely followed the Linux topic over the last fifteen years and helped with its progress“, emphasized Michael Jores.

„Suse as a development platform has laid the basis for many innovations, such as providing the first Open Source based Hypervisor XEN, the one-stop support infrastructure created by integrating Suse support in SolMan, the development of the HA cluster reference architecture and the provision of Suse high availability for the automation of the Hana system replication.“ Jürgen Hamm from NetApp is more cautious when talking to E-3 about the general role of Open Source: „A trend can be seen where proprietary applications will continue to play a large role; the questions arising relate to support, maintenance and liability.“ It works, but the challenges and dangers have to be defined and analyzed.

Crisp Research analyst René Büst wrote a warning in his blog: „CIOs must thus clarify the basic question of how OpenStack can offer them strategic benefits. This will only be the case if they use OpenStack in a different way to their competitors and do not just rely on operational excellence. On the contrary, you have to see OpenStack technology as part of the IT strategy in order to generate real benefits for the company.“

Heiner Diefenbach sees the OpenSource trend in the SAP community directly: „OpenStack enables the standardization of architectures to operate data centers and is thus extremely suitable to develop hybrid cloud scenarios but also to establish a standardized basis during mergers and acquisitions.“ The Fujitsu manager believes that the user has – with OpenStack – a simple option when migrating its cloud scenarios from one provider to the other.

„We believe that OpenStack will become more significant and we will thus integrate our operations concept for SAP, Flexframe Orchestrator, via API into this architecture“, explained Diefenbach. And he has seen another aspect in the community: Hadoop supplements the Hana portfolio in a complementary manner in order to analyze above all non-structured mass data. „The demand for Hadoop solutions, such as Appliance Primeflex for Hadoop, is growing“, said Heiner Diefenbach happily.

Cloud computing strategy

„The significance of OpenStack cannot be valued highly enough“, emphasized Bernd Kappesser, Managing Director of Realtech in Walldorf. „SAP‘s commitment includes the strategic aim of reducing the license costs for managing a private cloud and to simultaneously establish independence towards the infrastructure

providers of hardware, storage, network and even virtualization. As a customer I remain flexible and can swap my cloud providers as required. Another long-term objective is to be able to decide regarding each application as to whether it runs on premise within my company or at a cloud provider‘s.“ Experts agree that OpenStack can become for the cloud what the x86 processor is when it comes hardware procurement: comparable and exchangeable.

The aim is also wide-ranging management. And with regard to Hadoop, the Realtech manager Hinrich Mielke believes that the big data approach of the highend, high performance solution Hana will be extended towards big data in petabytes and a low-price infrastructure. „This combination will provide interesting new use

cases“, said Bernd Kappesser, „which will seamlessly link high performance data access with access to non-structured mass data – without having to switch media.“

Linux and OpenStack provide a stable basis for cloud computing. The journey to the cloud means a number of individual steps for existing SAP customers and alignment with ERP and Hana. „Cloud Computing covers a wide range – from the pure offer of server resources with operating system to the software-asa-service portfolio“, explained Michael Jores. It is above all the quality, performance, security and flexibility which will show which type of cloud offers is the strongest in future. Jores is convinced „If a cloud offering results in a vendor lock-in, then we are back to where we were before the Unix/Linux migration

wave“. Where could cloud computing be at home as far as SAP customers are concerned – with SAP. (Hana Enterprise Cloud), with Amazon (AWS), Google, Microsoft (Azure) or with SAP partners and local providers?

Jürgen Hamm from NetApp: „SAP, AWS and Azure are making considerable investments, but I also see local hosting companies which have very interesting cloud offerings.“ Hinrich Mielke also refers to the vendor lock-in topic: „My recommendation is always independent of the customer – I have no magical objects, potions or lucky charms. It is always important to remain flexible and independent, i.e. not to succumb to a vendor lock-in. This should always be verified before deciding in favor of a solution. OpenStack a very good option here, but when setting it up you should ensure you do not get a make-solution instead of a buy-solution. OpenStack is highly adaptable and in this case, it is possible to stumble into the same pitfall that results from a major SAP ERP system change. The solution‘s application lifecycle management can then become too complex.“ CIOs with an SAP history are aware of this danger and are therefore well equipped, says Mielke with a smile and adds: „In any case, there is always the basic principle that problems cannot be outsourced! If the general conditions are not clearly defined, resorting to the cloud or to the outsourcer will not be crowned with success. For this reason, accurate preparation, ideally with an external consultant, is the foundation for successful and productive sourcing.“

Public, hybrid or private cloud?

„This differs from one customer to the next,“ says Heiner Diefenbach. „We provide our customers with support for all three models. However, in the case of business- critical data there is a clear trend towards private cloud among customers or for operations in our highly secure data centers in Germany, which are governed by German law.“ Consensus has not quite been achieved as far as Hana and cloud computing are concerned. According to Peter Wüst, NetApp, on premise is still in demand for the core application for ERP and Hana, „although on-demand concepts for companies are increasingly worth considering in individual cases and can also come from the cloud.“ However, he observes that security and data sovereignty are of great importance here. Likewise Heiner Diefenbach says: „There is still no sign of a clear trend, because personal preferences are predominant. The concerns regarding

data protection and the competence for in-house operations are very different.“

Friedrich Krey from Suse Linux clearly sees the private cloud as the choice for productive SAP operations. „In order to cover outsourced SAP test, training or development areas the customer can accordingly access public cloud solution offerings,“ is how he explains options such as the S/4 Hana trial version on AWS. „This then results in the construct of a hybrid cloud, which we also underpin correspondingly with Suse technology, namely with the Linux Enterprise Server for SAP Applications and the Suse OpenStack Cloud.“

S/4 Hana is disruptive, isn‘t it?

Hana is the new platform in the SAP eco-system, to which the mentioned technologies and procedures such as Linux and OpenStack are by nature connected. Open Source and cloud computing are the cornerstones of the open society. The S/4 roadmap – on demand and on premise – is outlined by SAP. Linux and OpenStack as well as other Open Source products play a decisive role. And so the question as to whether they are on a disruptive or non-disruptive journey will arise in the coming years for existing SAP customers.

„SAP Hana is a disruptive technology and if it ultimately succeeds in consolidating OLAP and OLTP transactions in a database- specific manner and making them consumable for business via S/4 applications“, says Michael Jores, „then I believe e can speak of disruptive technology. Since it is an innovation that is designed for long-term further development, SAP has logically relied on Linux, thus ensuring that the infrastructure also keeps pace as far as its rate of innovation is concerned, and does not encounter any impasses, because Linux guarantees that this innovation will also remain mainstream.“

Jürgen Hamm from NetApp logically notes that the new SAP data center operation may not become more complex than SAP Classic. „As soon as there are also operational concepts for Hana, I no longer see anything to prevent referring to Hana as data-center-ready. NetApp and Fujitsu have with Flexframe an excellent solution on the market“, says Hamm on the basis of his professional experience. Heiner Diefenbach differentiates this by saying: „Purely from a technical perspective SAP Hana is undoubtedly a disruptive database-technology. However, the way in which SAP has in the meantime integrated the solution into the portfolio and the solutions that we provide enable companies to implement them without having to switch media. Our experience from numerous consulting projects shows that each individual case can be disruptive or even non-disruptive for the customer.“

And Diefenbach knows from countless discussions with users that „IT and business processes are inseparably connected with each other here. And we are in demand as the mediator between these two poles.“

To conclude, Michael Jores defines the status of the open society in the SAP community: „For years now SAP has also been working directly in the corresponding Open Source projects and is supported by Open Source technology partners, which – like

Suse – have also reliably been continuously working on such disruptive technologies over the years. No other Enterprise-Linux manufacturer has demonstrated the same reliability in a partnership with SAP in the almost 16 years since the existence of the SAP Linux laboratory. SAP has implemented the data-center-readiness topics for Hana at top speed: for example backup and restore, high availability and disaster recovery, security, virtualization and multi- tenant capabilities. As an SAP technology partner Suse has resolutely supported this data center readiness. The S/4 Hana strategy is the logical consequence for transforming the added value of in-memory technology for customers into disruptive technology and thus also creating the business cases and added values of and for Hana at application level.“

E-3: Dear Dr. Reger, how would you explain the OpenStack concept to an existing SAP customer with a traditional R/3 data center?

Joseph Reger: OpenStack is an Open Source based operational environment for cloud data centers – whether they are self-operated on premise, but are also of interest for operators of public clouds. OpenStack is the preferred operational environment, particularly with regard to the SAP cloud strategy and the resulting extended options of also being able to set up hybrid SAP scenarios. Thus, if an existing SAP customer‘s goal is to have a cloud operating platform, which

is something such a customer should do, then OpenStack is the way to go.

E-3: Is OpenStack only something for innovative cloud users or does this free IT architecture also have a more far-reaching significance?

Reger: In addition to low-cost and reliable operations, data centers always call for more agility. A vendor lock-in – be it for middleware or even hardware – should also be avoided. All this is promised by using OpenStack and that is why it is highly interesting for CIOs. It goes without saying that the activities of SAP also play an important role in the SAP environment. However, new applications have to communicate with the classic applications and this calls for hybrid

scenarios. Experience has shown that this of course works more efficiently if similar operating models are taken as a basis – in this case OpenStack can be the better answer than an integration platform.

E-3: What significance does OpenStack have for Fujitsu itself?

Reger: Fujitsu strategically uses OpenStack – there have been official press releases to this end. For us this also means that Fujitsu will in future use OpenStack as the operational environment for its own cloud offerings from more than 100 data centers worldwide. Furthermore, Fujitsu is a member of the OpenStack Community and also the OpenStack Consortium, where it also makes active contributions towards further development.

E-3: And what significance could OpenStack have for Fujitsu/SAP customers? What do you recommend to an existing SAP customer?

Reger: For many years Fujitsu‘s Primeflex for SAP Landscapes based on Flexframe Orchestrator has provided a standardized operational environment for classic and Hana based SAP landscapes. This means that Fujitsu already provides an operating platform today, which ensures highly reliable and low-cost SAP operations. We are already working on gradually integrating Flexframe- Orchestrator functionality with OpenStack. In other words, our customers will use the quasi-standard OpenStack with special, very convenient additional features for fully integrated, largely automated SAP operations.

E-3: Thank you for the interview.

For download:

http://sp.ts.fujitsu.com/dmsp/Publications/public/prw-sap-e3-coverstory-open-society.pdf