Abab +Java Split step 4

[Former Member]

Hi

I´m trying my first Abab java split on a dual stack system.

This is a distributed system the database is ms sql running on a different host.

I´m doing the Move Java Database option.

I´ve done the first 3 steps but i´m stuck on the 4 step.

On the database host i´m running sapinst step install Java database Instance.

when I point to the the export media I get this

    Found the label SAP:JMIG:70:*:*:* but need the label SAP:JMIG:73:*:*:*

Why is it asking for some other label then I have in the export ?

[Former Member]

Hi,

are you using the right split tool version?

Looks like that the source system is NW 7.0 but you are using the tool for NW 7.3.

Also check the below note.

1899391 - Found the label SAP:JMIG:70:*:*:* but need the label SAP:MIGSDM:*:*:*:*

1909529 - Parallel System Copy export-import: Wrong LABEL.ASC

Thanks

RishiA brol

[Former Member]

I´m using the tool

DUAL STACK SPLIT TOOL 2.1 -> Windows on x64 64bit.

There is no other version for type NW.

Note 1899391 might some thing there, there is diagnostic agent on the host. I don't understand what the Resolution can you explain.

Reproducing the Issue

1. Import the java on the target server
2. Enter the migration export CD
3. Error occurred

CauseSDM exists only on the host where the Java-CI is running.  In that case the Java-CI export must be started on that host. (If using virtual hostnames then so on CI host): sapinst.exe SAPINST_USE_HOSTNAME=<virtual_hostname of CI>

Resolution

• In case the source system is distributed, then the Database (DB) export need to be started on DB-host and Java- Central Instance (CI) export on CI-host - as the system copy guide contains.
• For more information please refer to the guide as it provide more detail information.
• Please refer to SAP note  1556874 (Incomplete export or incomplete JVM switch)

[Former Member]

Hi,

I think you need to check the below settings as per the note 1556874

Before you start the export, ensure the following:

• Dual-stack system: The parameters rdisp/j2ee_start and rdisp/j2ee_start_control have the value "1".

• Only unique profiles exist for each instance in the profile directory.

                    If profiles exist several times for each instance (for example, with physical and virtual host names), errors may occur.

• UNIX: All entries under /usr/sap/sapservices are correct (that is, instances are permitted to be contained only if they are installed on this host and they must have the correct paths and profile names).

2. Start the export as follows:

• If the system is configured with virtual names, use SAPINST_USE_HOSTNAME=<virtual host> to start the export.

• If the database and the CI are configured with different virtual hosts, use SAPINST_USE_HOSTNAME= <virtual host of the instance> to start the export for each instance.

3. SOLARIS only:

• Use ifconfig -a to check whether the DEPRECATED flag is set and, if possible, deactivate if for the duration of the export. After the export, it is essential that you activate the DEPRECATED flag again. If you cannot deactivate the flag, you must change control.xml accordingly so that the function isHostLocal returns the correct host to SAPINST. Ideally, open a message for this and directly send the used control.xml with the message.

Thanks

Rishi Abrol

[Former Member]

This is in place , the problem has to with the label on the export.

[Former Member]

Hi,

Can you please confirm that you are using 70SWPM....SAR for Split.

1825382 - SAP Release Note for SL Toolset 1.0 SPS09

Dual-Stack Split
Software Provisioning Manager 1.0 SP04 supports the split of Dual Stack Systems into separate ABAP and JAVA systems for the following scenarios/products:

• Split of SAP Business Suite systems

• Split of SAP NetWeaver Business Warehouse (AS ABAP and BI JAVA based on EP, EP-Core and AS JAVA)

• Split of other Dual-Stack systems, that run stack-isolated applications without direct dependencies to applications running on the other stack

• Removal of the JAVA stack without performing a split (if the JAVA stack is not used and no longer required at all)

The systems need to run on the following SAP NetWeaver releases for (70SWPM....SAR😞

• SAP NetWeaver 7.0 SP14 or higher

• SAP NetWeaver 7.0 Enhancement Package 1, 2 or 3

The systems need to run on the following SAP NetWeaver releases for (SWPM....SAR😞

• SAP NetWeaver 7.3 or higher

1589311 - Replacements of outdated tools via SL Toolset

October 2013: Dual-Stack Split 2.1 and System Rename 1.0 including predecessors have been replaced by the Software Provisioning Manager 1.0 (SWPM.SAR, 70SWPM.SAR).
Dual-Stack Split Tool and System Rename have been integrated into the Software Provisioning Manager.

Thanks

Rishi Abrol

[Former Member]

I found the solution ,

I need to use

SOFTWARE PROVISIONING MGR 1.0 -> Windows on x64 64bit

[Former Member]

There is a smdagent on the host that is version 7.3 could that have some thing to do with this ?