Unable to retrieve nametab info for logic table BSEG

Question

Hi
We are performing a unicode export (CUUC from 4.6C upgrade to ECC 6.0) and we have incurred this error.
Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases
Our OS is HPUX11.31 & Database is 10.2.0.2
myCluster (63.21.Exp): 1610: inconsistent settings for table position validity detected.
myCluster (63.21.Exp): 1611: nametab says table positions are valid.
myCluster (63.21.Exp): 1614: alternate nametab says table positions are not valid.
myCluster (63.21.Exp): 1617: for field 310 of nametab displacement is 1877, yet dbtabpos shows 1885.
myCluster (63.21.Exp): 1621: character length is 1 (in) resp. 2 (out).
myCluster (63.21.Exp): 1257: unable to retrieve nametab info for logic table BSEG .
myCluster (63.21.Exp): 8358: unable to acquire nametab info for logic table BSEG .
myCluster (63.21.Exp): 2949: failed to convert cluster data of cluster item.
myCluster: RFBLG *400**AT10**0000100000**2004*
myCluster (63.21.Exp): 322: error during conversion of cluster item.
myCluster (63.21.Exp): 323: affected physical table is RFBLG.
(CNV) ERROR: data conversion failed. rc = 2
(DB) INFO: disconnected from DB
/usr/sap/SBX/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/SBX/SYS/exe/run/R3load: END OF LOG: 20081102104452
We checked the note 913783 as per the CUUC guide but the correction only for package SAPKB70004 to 6. but we are in package SAPKB70011.
We had found two notes:
1. Note 1238351 - Hom./Het.System Copy SAP NW 7.0 incl. Enhancement Package 1
:Solution:
There are two possible workarounds:
1. Modify DDL<dbs>.TPL (<dbs> = ADA, DB2, DB4, DB6, IND, MSS, ORA) BEFORE the R3load TSK files are generated;
              search for the keyword "negdat:" and add "CLU4" and "VER_CLUSTR" to thisline.
2. Modify the TSK file (most probably SAPCLUST.TSK) BEFORE R3load import is(re-)started.
              search for the lines starting with "D CLU4 I" and "D VER_CLUSTR I" and change the status (i.e. "err" or "xeq") to "ign" or remove the lines. "
I tried the above solution by editing the file DDL*.TPL but it is skipping the table and marks it as completed but its not the good solution as we will be miss the data from the table RFBLG.
2. Note 991401 - SYSCOPY EXPORT FAILS:SAPCLUST:ERROR: Code page conversion:
Solution
Activate the table.
Then call the RADCUCNT report. Do not change the selected parameters, but ensure that 'Overwrite Entries' is selected.  Set the 'Unicode Length' to 2 and fill the last two fields 'Type' and 'Name' with TABL and TACOPAB respectively. Then select 'No Log' or specify a log name.
Execute the RADCUCNT report and restart the export.
We have not tried this solution, bcos SAP is still down and CDCLS job is still running.
We would like to know whether you have faced any issues like the above one and what is your suggested approach and solution.
Is it safe to start SAP now (when the CDCLS job runs) and then try to activate the table RFBLG?
Regards
Senthil
Edited by: J. Senthil Murugan on Nov 3, 2008 1:40 AM
Edited by: J. Senthil Murugan on Nov 3, 2008 3:37 AM

Answer 1

Dear Senthil
I had faced this issue earlier.
Table BSEG Requires activity in the ACT phase, like activation etc.
If we do the ACT phase using the transports and not perform manual activation of this table, this issue arrives.
Please share the relevant information--- seems some steps are missed out or not carried properly in the CU&UC phase.
Otherways, we had applied the solution  Note 991401 - SYSCOPY EXPORT FAILS:SAPCLUST:ERROR: Code page conversion and it worked well..
But you need to be sure, that this table was changed(activated etc) during the Upgrade till export phase.
Issue is Nametab info is created during the Upgrade phase in CU&UC and if this table is touched, that nametab info is not getting it right as the runtime object is changed.
With RADCUCNT the nametab info will be created again.
All the Best
Best Regards
Deepak Dhawan