How to perform SAP Dual Stack Split - Netweaver

When I was doing an installation, I stumbled across an article explaining the differences between using SAPINST for Java export and the newer Dual-Stack Split tool. At first, I thought SAPINST would let me just export the Java schema like older versions did, but that option isn’t there anymore. Instead, SAPINST now exports the whole database (ABAP + Java) together.

🔍 What I Noticed with SAPINST

• In older releases, you could pick which schema to export. That’s gone now.

• Running SAPINST basically exports the entire database, not just Java.

• You can still monitor the migration manually, and the export directory will contain ABAP and Java control files.

• For Java, you’ll see files like LABEL.ASC, LABELIDX.ASC, JDMP, SDM, TOOLS, DB, APPS, and SOURCE.PROPERTIES.

So SAPINST still works, but it’s more of a “whole system copy” approach rather than a selective Java export.

✅ Dual-Stack Split Tool

Then I looked at the Dual-Stack Split utility, and honestly, it feels more practical. It’s designed specifically for splitting ABAP and Java stacks. With it, you can:

• Export, import, and even uninstall Java.

• Choose between “Move Java Database” (export and remove Java schema/files to a new host) or “Maintain Database” (export Java engine/files but keep the schema for MCOD scenarios).

• Track progress with logs like jload.log and Export.SDA.

After the export, the directory structure is clearer: ABAP folder (often empty), and Java folder with all the expected files.

📌 Lesson Learned

SAPINST and Dual-Stack Split use the same underlying mechanism, but SAP moved the Java schema export functionality into the Dual-Stack Split tool. The big advantage of the split tool is flexibility—you can move Java to a standalone system, import it cleanly, and verify everything before finalizing.

For me, the takeaway was:

• SAPINST → whole database export (ABAP + Java).

• Dual-Stack Split → targeted Java export/import, better suited for modern setups.