System Copy problems with seperate DB/CI-instances

[Pepa]

Hi,

We have some problem to get the system copy to work for our SCM 5.0 installation. We are planning to move the installation to new hardware during a unicode migration.

The current configuration is: SQL Server 2005 SP3, Windows 2003, non-unicode, AMD64 servers and we use the Netweaver 7.0 SR3 DVD's for the export.

The database is installed on a MSCS (2 servers) and the central instance (with ASCS and SCS) on a seperate server (not in MSCS).

We got the database export to work after we added the envirorment variabel SAPINST_uSE_HOSTNAME=<virtual db name> and it finished sucessfully.
DVD used - 51033511 Installation Master
(SAP SCM 5.0 Support Realese 3 --> Software Life-Cycle Options --> System Copy --> MS SQL Server --> Source System Export --> High-Availability System --> Based on AS ABAP and AS Java --> Database Instance Export)

When we then trying to export the Central Instance (after logging on the central instance server) we got problems.
(SAP SCM 5.0 Support Realese 3 --> Software Life-Cycle Options --> System Copy --> MS SQL Server --> Source System Export --> High-Availability System --> Based on AS ABAP and AS Java --> Central Instance Export)

sapinst.exe is btw started from folder \\51033511_Installation_Master\51033511_BS_SR3_x64 \IM_WINDOWS_X86_64

Not everything is coming up in sapinst when filling in the information which it normally does at a system copy export. The parameter Summary is only showing "General Parameters", "OS User Passwords" and "Database Export" and the rest is missing. The phases which shows in the export phase are "NW_Export", Prepare to export Java", "Export from Java central instance" and "Archive Adobe Document Services data" and the rest of the phases are missing.

No errors messages can be found in sapinst.log and the export finished successfully, but much is missing from the export (ABAP folder is for exemple empty in the export folder).

The environment parameters set on the central instance server for <sapsid>adm account are
DBMS_TYPE, MSSQL_DBNAME, MSSQL_SCHEMA, MSSQL_SERVER, SAPEXE, SAPLOCALHOST and SAPSYSTEMNAME

Anyone which have an idea what the problem is? Any suggestion are welcome.

[Zoom]

Hello,

Have You used the SAPINST_USE_HOSTNAME parameter during the CI export?

in a distributed system it have to be defined for all exports (and imports)

Regards,
Zoom

[Pepa]

Hi,

Yes, we have tried that scenario. We get the same result (as in my initial post) when running sapinst directly or when we use the SAPINST_USE_HOSTNAME parameter. It seems that the sapinst only finds the J2EE part of the export for CI and the ABAP parts with (among other) the migration checkbox is never visible.

[mister.sap]

Could you tell me what was the solution?