System Copy Error while exporting ABAP

[Former Member]

Hi,

We want to system copy. Our platform is SAP Enterprise 4.7 Unicode on Solaris 8 and Oracle 9.2.0.4.

While exporting we have an error like below:

DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8

(GSI) INFO: dbname = "MDT20070711060724

"

(GSI) INFO: vname = "ORACLE "

(GSI) INFO: hostname = "sapmdtst "

(GSI) INFO: sysname = "SunOS"

(GSI) INFO: nodename = "sapmdtst"

(GSI) INFO: release = "5.8"

(GSI) INFO: version = "Generic_117350-12"

(GSI) INFO: machine = "sun4u"

(GSI) INFO: instno = "0020178964"

(NT) Error: AABLG: normal NameTab from 20031007162839 younger than alternate NameTab from 20000323230317!

(SYSLOG) INFO: k CQF : AABLG&20000323230317&20031007162839& rscpgdio 47

(RSCP) ERROR: -

---

3-

(RSCP) ERROR: code: 64 RSCPECALL

(RSCP) ERROR: Altername NameTab too old

(RSCP) ERROR: module: rscpgdio location: 47 line: 2884

(RSCP) ERROR: TSL01: CQF p3: AABLG&20000323230317&20031007162839&

(RSCP) ERROR: -

---

.

myCluster (55.16.Exp): 904: received return code 64 from rscpCheckNTTimeStamps.

myCluster (55.16.Exp): 905: suspicious create timestamp of alternate nametab encountered.

myCluster (55.16.Exp): 909: create timestamps of nametab: 20031007162839; alternate nametab: 20000323230317.

myCluster (55.16.Exp): 295: error when retrieving physical nametab for table AABLG.

(CNV) ERROR: data conversion failed. rc = 2

(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)

(DB) INFO: disconnected from DB

/sapmnt/MDT/exe/R3load: job finished with 1 error(s)

/sapmnt/MDT/exe/R3load: END OF LOG: 20090507145957

How can we resolve this error and we can continue to export operations for SAP System Copy? Please help us about this issue.

Best regards,

[Former Member · Accepted solution]

Hi Markus,

Also our system is 4.7x110 and kernel level is 620. I upgraded kernel level to 640 patch 196. Also can I use Master CD for 620/640 for this system copy operation? Because 4.7x110 system copy document says that you will use and start system copy from SAP Kernel CD for this operations. But I can start sapinst from Master CD. There is no problem about it.

Our error logs like below:

SAPPOOL.log:

(NT) Error: ARCH_NUM: normal NameTab from 20031007171326 younger than alternate NameTab from 20010222232417!

(SYSLOG) INFO: k CQF : ARCH_NUM&20010222232417&20031007171326& rscpgdio 47

(CNVPOOL) Altername NameTab too old ARCH_NUM&20010222232417&20031007171326& Abort.

(CNVPOOL) conversion failed for row 0 of table VARKEY = X

(CNV) ERROR: data conversion failed. rc = 2

(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)

(DB) INFO: disconnected from DB

############################################

SAPCLUST.log:

(NT) Error: AABLG: normal NameTab from 20031007162839 younger than alternate NameTab from 20000323230317!

(SYSLOG) INFO: k CQF : AABLG&20000323230317&20031007162839& rscpgdio 47

(RSCP) ERROR: -

---

3-

(RSCP) ERROR: code: 64 RSCPECALL

(RSCP) ERROR: Altername NameTab too old

(RSCP) ERROR: module: rscpgdio location: 47 line: 2884

(RSCP) ERROR: TSL01: CQF p3: AABLG&20000323230317&20031007162839&

(RSCP) ERROR: -

---

.

myCluster (55.16.Exp): 904: received return code 64 from rscpCheckNTTimeStamps.

myCluster (55.16.Exp): 905: suspicious create timestamp of alternate nametab encountered.

myCluster (55.16.Exp): 909: create timestamps of nametab: 20031007162839; alternate nametab: 20000323230317.

myCluster (55.16.Exp): 295: error when retrieving physical nametab for table AABLG.

(CNV) ERROR: data conversion failed. rc = 2

(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)

(DB) INFO: disconnected from DB

####################################

SAPSDIC.log

(EXP) ERROR: entry for /DSD/BAPERAORDERHD in DDNTT is newer than in DDNTT_CONV_UC: 20031007171503 > 20030430133910

(EXP) ERROR: entry for /DSD/BAPERAORDERIT in DDNTT is newer than in DDNTT_CONV_UC: 20031007171503 > 20030430133910

(EXP) ERROR: entry for /DSD/BAPERATS in DDNTT is newer than in DDNTT_CONV_UC: 20031007171503 > 20030430133910

(EXP) ERROR: entry for /DSD/BAPIRACLEARING in DDNTT is newer than in DDNTT_CONV_UC: 20031007171503 > 20030430133910

(EXP) ERROR: entry for /DSD/BAPIRACOCIHD in DDNTT is newer than in DDNTT_CONV_UC: 20031007171503 > 20030430133910

(EXP) ERROR: entry for /DSD/BAPIRACOCIITM in DDNTT is newer than in DDNTT_CONV_UC: 20031007171503 > 20030430133910

(EXP) ERROR: entry for /DSD/BAPIRACOCIMONEYITM in DDNTT is newer than in DDNTT_CONV_UC: 20031007171503 > 20030430134358

(EXP) ERROR: entry for /DSD/BAPIRACUSTADDR in DDNTT is newer than in DDNTT_CONV_UC: 20040620112731 > 20031001154604

##############################################

SAPSLEXC.log

(EXP) TABLE: "DDFTX"

(DBC) Info: No commits during lob export

(EXP) TABLE: "DYNPLOAD"

(EXP) TABLE: "DYNPTXTLD"

(EXP) TABLE: "O2PAGINC"

(EXP) TABLE: "O2PAGRT"

(DB) INFO: disconnected from DB

/sapmnt/MDT/exe/R3load: job completed

/sapmnt/MDT/exe/R3load: END OF LOG: 20090507152046

/sapmnt/MDT/exe/R3load: START OF LOG: 20090508094648

/sapmnt/MDT/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#20 $ SAP

/sapmnt/MDT/exe/R3load: version R6.40/V1.4 [UNICODE]

Compiled Aug 13 2007 17:04:48

/sapmnt/MDT/exe/R3load -datacodepage 1100 -e /tmp/sapinst_instdir/R3E47X2/COPY/EXPORT/ABAP/COPY/UC/DBEXP/SAPSLEXC.cmd -l /tmp/sapinst_instdir/R3E47X2/COPY/EXPORT/ABAP/COPY/UC/DBEXP/SAPSLEXC.log -stop_on_error

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8

(GSI) INFO: dbname = "MDT20070711060724 "

(GSI) INFO: vname = "ORACLE "

(GSI) INFO: hostname = "sapmdtst "

(GSI) INFO: sysname = "SunOS"

(GSI) INFO: nodename = "sapmdtst"

(GSI) INFO: release = "5.8"

(GSI) INFO: version = "Generic_117350-12"

(GSI) INFO: machine = "sun4u"

(GSI) INFO: instno = "0020178964"

(DB) INFO: disconnected from DB

/sapmnt/MDT/exe/R3load: job completed

/sapmnt/MDT/exe/R3load: END OF LOG: 20090508094650

/sapmnt/MDT/exe/R3load: START OF LOG: 20090508095402

/sapmnt/MDT/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#20 $ SAP

/sapmnt/MDT/exe/R3load: version R6.40/V1.4 [UNICODE]

Compiled Aug 13 2007 17:04:48

/sapmnt/MDT/exe/R3load -datacodepage 1100 -e /tmp/sapinst_instdir/R3E47X2/COPY/EXPORT/ABAP/COPY/UC/DBEXP/SAPSLEXC.cmd -l /tmp/sapinst_instdir/R3E47X2/COPY/EXPORT/ABAP/COPY/UC/DBEXP/SAPSLEXC.log -stop_on_error

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8

(GSI) INFO: dbname = "MDT20070711060724 "

(GSI) INFO: vname = "ORACLE "

(GSI) INFO: hostname = "sapmdtst "

(GSI) INFO: sysname = "SunOS"

(GSI)

How can I resolve this problem and contunie to export operation?

Best regards,

[markus_doehr2 · Accepted solution]

> Also our system is 4.7x110 and kernel level is 620.

Kernel 6.20 is out of support for years now

> I upgraded kernel level to 640 patch 196. Also can I use Master CD for 620/640 for this system copy operation?

Your problem is, that you are exporting a Unicode system with codepage 1100 - which is wrong.

I would

- upgrade the kernel to the latest patchlevel

- upgrade R3load and dboraslib.so to the latest level (your R3load is still from 2007!)

- use the DVD mentioned in "Note 969660 - 6.20/6.40 Patch Collection Installation : Unix" to do the copy.

If you use R3load to do system copies make sure, you ALWAYS use the latest patchlevels.

Markus

[Former Member · Accepted solution]

Hi Markus

I upgraded kenel 640 patch 196 also. But still I have same error. And I am using 51033746_12 Installation Master 6.20/6.40 Solaris on SPARC 64bit for System Copy.

I will upgrade patch level to latest level (274). After that I will restart system copy. Which kernel patch will I use? SAP KERNEL 6.40 64-BIT UC or SAP KERNEL 6.40_EX2 64-BIT UC ? What is the differences for these kernels? What is the mean of EX2?

Best regards,

[markus_doehr2 · Accepted solution]

You have to RESTART the copy all over. Since parts of the export are now with the wrong codepage exported the export is useless/corrupt.

The 640_EX2 kernels are kernels that are linked for newer operating systems (see Note 1058988 - 640_EX2 Kernels).

I would

- delete the export

- delete the installation directory

- upgrade R3load, R3ldctl, R3szchk and dboraslib.so separately (there are newer versions than in the SAPEXE and SAPEXEDB archives)

- start the export from scratch with the given new DVD

- make sure you select codepage 4102 during export (Unicode - Big Endian)

Markus

[Former Member · Accepted solution]

Ok Markus.

I will upgrade kernel to latest level of 640 and I will restard system export from scratch again. But there is no selection about the codepage while starting to system copy. There is only database character set selection and I am choosing UTF-8. Other choices are WE8DEC and US7ASCII. When will I select 4102 as codepage?

Thank you for your help.

Best regards

[markus_doehr2 · Accepted solution]

Not sure what you mean...

Sapinst has a field for that... this may not have been existed on your old DVD.

Markus

[Former Member · Accepted solution]

Ok Markus you are right. I have this selection in my DVD. My last question: Our system is Solaris SPARC and I will make Heterogeneous System copy from Solaris Sparc to Linux X86_64. Which codepage will I choose? SPARC use big endian 4102 but Linux X86_64 use little endian 4103. Our source system is Solaris SPARC and our taget system Linux X86_64. Which codepage will I choose before exporting?

Thank you for your help

Best regards,

[markus_doehr2 · Accepted solution]

> Ok Markus you are right. I have this selection in my DVD. My last question: Our system is Solaris SPARC and I will make Heterogeneous System copy from Solaris Sparc to Linux X86_64. Which codepage will I choose? SPARC use big endian 4102 but Linux X86_64 use little endian 4103. Our source system is Solaris SPARC and our taget system Linux X86_64. Which codepage will I choose before exporting?

You choose the codepage for the target system (4103).

Note:

If you to a heterogeneous copy you must have a certified migration consultant on site, otherwise you will loose support during and after the migration and for problems resulting out of the migration.

http://service.sap.com/osdbmigration

--> FAQ

Markus

[Former Member · Accepted solution]

Thank you very much for your help Markus.

Best regards

[markus_doehr2 · Accepted solution]

You're welcome!

For a more step-by-step procedure also check my posting in

(and replace "dll" by "so")

Markus

[Former Member]

I am sorry for last message. I sent you 4 log files about this error in last message:

SAPCLUST.log , SAPPOOL.log, SAPSDIC.log and SAPSLEXC.log files.

Best regards,

[Former Member]

Yes I selected unicode before starting to export.

[markus_doehr2]

> Yes I selected unicode before starting to export.

This is really strange - because then, the correct codepage should be automatically selected.

Sapinst offers a field where to enter the codepage. Did you use the latest available sapinst DVDs?

And just to add:

Solaris 8 it out of support already (Note 1174174 - Solaris: End of Support Dates)

Oracle 9.2 is also out of support

Markus

[Former Member]

Hi Markus,

Yes I checked:) But I didn't understand about this sapnote. Also I sent this problem to SAP. Also they said me that:

"As per provided note, since your source system is unicode and your

target too, you have to use a different codepage (4103/4102), depending

on your target system. While exporting R3load use 1100 as default codepage and you must change codepage while exporting. Command: R3load -datacodepage 4102"

How can I change codepage while exporting and how can I continue to system copy export?

Best regards,

[markus_doehr2]

The codepage to export is given in sapinst. Did you select there the "Unicode" flag?

Markus

[markus_doehr2]

> (RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)

> How can we resolve this error and we can continue to export operations for SAP System Copy? Please help us about this issue.

Well - the error messages says it Did you check the mentioned note?

Markus