cancel
Showing results for 
Search instead for 
Did you mean: 

Error during Unicode Conversion at DDNTF table

former_member192334
Participant
0 Kudos

Hello

We are doing a Unicode Conversion for our CRT systems. This system now

is a SAP CRM 7.0 SR1 ABAP.

We have performed preparatory steps (SPUMG, checks, updating R3load,

R3ldctl, R3szchk, dboralib, ...),

but when we start Import process we get an error in SAPSDIC package.

The error looks like:

*************************+

****

(RTF) ########## WARNING ###########

Without ORDER BY PRIMARY KEY the exported data may be unusable

for some databases

(EXP) INFO: table DDNTF will be exported with sorting

(RSCP) ERROR: 'DDNTF' in UMGCCTL: Guess has illegal value.

(RSCP) WARN: DDNTF: Missing in UMGSTAT,

ERROR in nametab conversion

conversion of nametab table 'DDNTF ':

rscpMCStartTab: rc = 128

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

(DB) INFO: disconnected from DB

/usr/sap/CRT/SYS/exe/run/R3load: job finished with 1 error(s)

/usr/sap/CRT/SYS/exe/run/R3load: END OF LOG: 20091229193651

****

Any idea??

Thanks in advance

Regards

Accepted Solutions (0)

Answers (4)

Answers (4)

former_member192334
Participant
0 Kudos

Ok, problem have been solved

After reset SPUMG, and reestarting again I get STATUS tabstript in status OK.

Consistency chek also was ok.

And the export have been finished well

Thanks to everybody

former_member192334
Participant
0 Kudos

Hello again

We are not using CU&UC. Before we performed the upgrade. Now we are converting to Unicode.

I think I performed all preparation steps according to guide "Single Code Page System Conversion to Unicode NW AS 7.0 Ehp1"

I have read Note 932279 but dont' solve anything.. We don't see any problem of inconsistencies.. All previous task are well finished.

Regarding to report UMG_FINISH_PREPARATION: Nothing done. I think this report is not able for this release.

Any suggestion?

Thanks and regards

Former Member
0 Kudos

Hi,

Looks like as Gerard mentioned the namtab has not been converted.....

Did you run RADCUCNT and used variant UNICODE-02-CRE ?

and did you inspect the logfile for errors after it finished......

Mark

former_member192334
Participant
0 Kudos

Yes I executed this Report using Menu Tool Bar.

The first execution gave me some errors regarding some tables existing at database level but not in DDIC. We ignored this errrors because those tables are not important.

But the last try, we decided solve this inconsistencies deleteting those tables at database level, repeting report RADUCNT (in this case no errors appeared) and repeting the export with the same error..

Now, we have seen in Tabscript STATUS of SPUMG there are some errors regarding DDNTF inconsistency found at table control. Reason 4. But this reason means that faillback codepage missing at table control for this table. But as far I know, I can't fill failbak field for this kind of table...

So know I'm reseting SPUMG, and reestarting again..

But I don't understand what is the problem

In a few minutes I will you inform about results

Meanwhile is anybody have any suggestion or idea... please let me know

Thanks!

Former Member
0 Kudos

Did you run the report UMG_FINISH_PREPARATION, that would run the RADCUCNT which does the nametab conversion.

see whether you can rerun the report and continue import.

Gerard

peter_dzurov
Contributor
0 Kudos

Have you followed ALL (preparation) steps according to guide?

Some of them are needed just before export is about to start.

Did you use CU&UC scenario?

Please check note 932779, mainly sections:

2.2 Known problems

2.3 Analyzing problems

2.4 Nametab Check in R3load

3. Nametabs and CU&UC

3.1 The nametab handling during CU&UC

3.2 Analyzing problems