Is import running properly? Any problems expected later?

[Former Member]

Hi,

I'm performing a Database import for a distributed SAP ECC 6.0 EhP4 SPS06 system based on SunOS 5.10 Oracle 10.2.0.4 for converting from non-Unicode to Unicode as part of a CUUC project.

When performing the export:

1. The checkbox for "Unicode Target System (Recommended)" was checked/selected

2. Target Hardware Platform was selected correctly as Big-endian 4102 (for Sun SPARC as per SAP note 552464)

When performing the import:

1. DB character set was selected as UTF8

2. SAP Code page was selected as 1100

SAPINST is now performing the ABAP load and seems to be running well. However, Now I notice the following messages in the <package>.log files:

(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(CNV) WARN: you set dbcodepage '1100' but platform requires '4102'.
(CNV) WARN: dbcodepage rectified to required value.

It seems R3load has corrected the dbcodepage value for me.

I also saw a post on SDN where Markus Doehr has replied stating that if Unicode is selected before starting to export, the correct codepage should be automatically selected.

I would like to know if anyone else has encountered a similar problem?

If yes, did you face any further issues once SAP was up after the ABAP import?

Thanks.

Regards,

Kailash

[markus_doehr2]

> SAPINST is now performing the ABAP load and seems to be running well. However, Now I notice the following messages in the <package>.log files:

>

(DB) INFO: connected to DB
> (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
> (CNV) WARN: you set dbcodepage '1100' but platform requires '4102'.
> (CNV) WARN: dbcodepage rectified to required value.

>

> It seems R3load has corrected the dbcodepage value for me.

Correct.

> If yes, did you face any further issues once SAP was up after the ABAP import?

The data will be imported correctly because the correct codepage was used.

Markus