cancel
Showing results for 
Search instead for 
Did you mean: 

System copy with Export/Import Distribyted system UNIX database, Windows CI

0 Kudos

HI

we have a distributed system witch I want to make a copy of

Oracle Database on HP-UX

CI + SCS on Windows

Dual stack system ABAP/Java

1) I have made an system copy with data base copy tools, and that works fine.

2) I have made a system copy export/import of a "central system"

If I try to make an export/import system copy on a distributed system it wont work.

( this work fine in a central system) I dont get anny error messages all gren checks marks !

It seems like the problem are in not finding the profiles from CI ?

It find the profiles for the sapgateway.

I someone are more interested I have more documentation with screen shots in a word document.

I Have used Installation Master SR3 and tryed with some older versions as well.

I have read SAP Note 970518 - Hom./Het.System Copy SAP NetWeaver 7.0 (2004s) SR2

SAPINST

Using virtual hosts for central and/or DB instances

SYMPTOM:

You are using virtual host names for your central instance and/or the database instance (e.g. in a HA environment). Although SAPinst finishes successfully, some export steps are not being performed.

SOLUTION:

Start the export with the property SAPINST_USE_HOSTNAME=<virtual host>.

If the central instance and the database instance run on different hosts, run the database export with SAPINST_USE_HOSTNAME=<virtual host name of the DB server> and - if you run a Java or ABAP+Java system - run the central instance export with SAPINST_USE_HOSTNAME=<virtual host nameof the central instance host>.

If you run a central system with different host names in the profiles, handle the export as a distributed export, calling SAPinst with parameter SAPINST_USE_HOSTNAME. Perform the export of the database instance on the DB server, calling SAPinst with SAPINST_USE_HOSTNAME=<virtual host of the DB server>.

Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos

Hi I have received folloving answer from SAP:

You're doing everything correct - besides one thing.

When you specify the profiles during the database export it cannot be

correct to specify the profiles of the gateway instance located on

the same host.

As a consequence - it picks up the wrong instance G01 and sets the

property 'hasABAP' and 'hasJava' to 'false'... - thus the export

is empty. You can see this within the corresponding 'sapinst.log' file.

The correct procedure would be to specify the profiles of the central

instance on the Windows Machine. If you cannot access them, you should

make them available by Samba or by any type of software which makes

it's possible to export filesystems or directories from windows to

unix.

Best regards

Bent