How to perform SAP Dual Stack Split - Netweaver

In a comparison of the Dual-Stack Split Tool vs Java Export SAPinst #sapadmin using the Software Logistic Toolset, which is identical to the sapinst tool,

During my installation, I came across an article that explained the differences between Java export with SAPinst and dual stack split.

With the current SAPINST, you may export and import Java.

Export: In a dual-stack system, SAPINST no longer allows merely JAVA schema export, hence the page that allowed us to choose which schema to export in prior SAPINST versions is no longer available.

In the current SAPINST for SAP Netweaver 7.0x, there were various options, similar to system copy. -> Oracle -> Source System Export -> Central System -> Based on AS ABAP and AS Java -> Database and Central Instance Export and system copy -> Oracle -> Source System Export -> Central System -> Based on AS Java -> Database and Central Instance Export and system copy -> Oracle -> Source System Export -> Central System -> Based on AS Java -> Database and Central Instance Export, deselect "Use Database specific tools"


1. When SAPINST is run, it exports the entire database (ABAP + JAVA).

2. Check that "Start Migration Monitor Manually" is selected.


Go to the file location - 

1. ABAP - control files, eg: .EXT and .STR maybe not required

2. The file LABELIDX.ASC - for "ABAP" and "JAVA"

3. In JAVA- LABEL.ASC, LABELIDX.ASC, JDMP, SDM, TOOLS, DB, APPS and SOURCE.PROPERTIES.


Next, we'll look at the Dual-Stack Split Tool, which I feel to be more practical and viable than SAPINST, and which is also supported by SAP.



With the Dual-Stack Split Tool, you can export, import, and uninstall Java.

Please read and comprehend the use cases, scenarios, supported OS & DB, limits, and known difficulties in the notes below.

Note 855534 - Dual Stack and SAP Business Suite 7

Note 1655335 - Use Cases for Splitting Dual-Stack Systems

Note 1561421 - Dual-Stack Split (2.0) for Systems Based on SAP NetWeaver


http://service.sap.com/sltoolset/download/dual-stack-split-guide 1.0 version of the Software Logistics Toolset -> Split into two stacks


Dual-Stack Split utility can be downloaded here:



./sapinst should be extracted and run.


Here you can view all of the features that Dual-Stack Split has to offer.



I Move Java Database - The Java engine, along with its schema and file system contents, will be exported and removed from the Dual-Stack system once it has been successfully imported to the target host.


ii) Maintain Database - Only the Java engine and its file system contents are exported, but the Java Schema is preserved. This is for MCOD's use only.


In this article, we'll concentrate on the option "Move Java Database - Export Java Stack."





Jload was used to perform the database export. jload.log and Export.SDA can be used to keep track of the progress.


After the export was completed, the files listed below were created in the export directory.


LABELIDX.ASC - "ABAP" and "JAVA" entries

ABAP - a blank folder

JAVA - LABELIDX.ASC, LABEL.ASC, JDMP, SDM, TOOLS, DB, APPS, SOURCE JAVA - LABELIDX.ASC, LABEL.ASC, JDMP, SDM, TOOLS, DB, APPS, SOURCE

LUP and EXE have been added to PROPERTIES.


In my upcoming blog, I'll go through how to use SAPINST to import Java and how to use the Dual-Stack Split tool. FYI, SAPINST's "Remove Java Stack from Dual-Stack System" function is essentially the "Uninstall" function. 


Conclusion: SAPINST and Dual-Stack Split use the same mechanism; SAP simply removed Java Schema Export functionality from SAPINST and merged it into Dual-Stack Split. Furthermore, the Dual-Stack Split tool now supports the import of a Java database from a dual-stack database into a Java-only system.



With the Dual-Stack Split tool, you may quickly copy the Java system using the "Move Database" option instead of the "Remove Java Stack from Dual-Stack system" option. Dual-Stack Split has the advantage of allowing you to export, import to the target host, and then split just (not necessary for system copy purposes) after a successful post-import verification test.

No comments: