Spliting MCOD Instances (CRM ABAP+JAVA)

[Former Member]

Hi All,

We have a new requirement to separate one MCOD system ABAP & JAVA instance in the target system using system copy method.

Scenario:

Source System

SAP App: CRM 7.0

Database: Oracle 11.2.0.2

Database Schema: Two schema in one DB (ABAP- SAPSR3 + JAVA- SAPSR3DB)

Target System

Database Schema: Two schema in two separate DB (ABAP- SAPSR3) & (JAVA- SAPSR3DB)

We have to use BACKUP/RESTORE approach to build the system copy

Plan so far:

1. Take a Offline DB backup in source & take export of JAVA schema only.

2. Restore the backup which will include DB schema of both ABAP and JAVA.

3. Once the import is completed.Drop the Target Schema of Java system.

4. Start the import using based on JAVA system and used the exported dump.

I know this approach looks quite odd, as we are mixing backup/restore & Export/Import process. We have some constraints

Technically this approach will work. please share your suggestion / experience.

Regards

RM

[ACE-SAP]

Hi ,

Just to be sure I understand your scenario...

Your are moving an MCOD Abap + Java from a single host A

to have an host B with Abap only and an host C with Java only ?

If so your scenario is fine and I could not think of a faster method.

Maybe you could delete Java schema after exporting it and before the backup in order to have less data in the backup set and be able to copy/restore it faster to host B... but Java schema is not that big so you won't save a lot of time.

You can save time also by switching to an incremental backup (activating block change tracking => 964619 - RMAN: Incremental backups with Block Change Tracking), take a full backup on Wednesday night, restore it to host B. Let the system productive on Friday and on Friday evening just take an incremental backup that will be faster to process & restore.

If you are willing to keep host A with Abap schema just follow the steps described by Reagan.

Best regards

[Former Member]

Hi YK / RB,

Thanks for your response.

@YK, yes your understanding is correct. Only one small correction in target host B only we have to install ABAP & JAVA separately (Separate DB & Separate schema).

Are you recommending to install JAVA 1st (using Export/Import method) and then install ABAP (using Restore/Recovery method)?

We are installing the target system with offline backup. So, incremantal option is not aplicable in our case.

Source system will be decomissioned after it moved to target.

Regards

RM

[Reagan]

Source system will be decomissioned after it moved to target.

In that case take a full backup of the system.

Take an export of the Java stack.

First setup ABAP on a new server as Java will be using the ABAP for UME.

Setup Java on a new server.

Regards

RB

[Reagan]

Hello

If you want to split the ABAP and Java part with two separate databases then you need to:

Create a new Java system by exporting and importing the Java stack from the existing system to the new system.

Remove all the J2EE related parameters from the profiles of the ABAP stack (if there are some)

Replug the newly created Java stack to the ABAP stack (UME).

Did I answer your question correctly ?

Regards

RB

[Former Member]

you should have searched for 'dual stack split' before posting here.

With the release of SL Toolset 1.0 SPS09, the dual-stack split procedure got integrated.

see

[Former Member]

SB, Thanks for the link.

In our case its not possible to split Dual-Stack in the source system.

If you read my post which clearly mention we have to use Backup/Restore for ABAP & JAVA will be installed using export/import jload method.

This approach used to minimize the downtime.