Error during Unicode Conversion - Import

Hi,
I am doing a Unicode conversion, done with the system export, while doing the
import during the Import ABAP phase system is throwing the error with R3load.
R3load -testconnect fails with following error.
emalonsbx002:wuuadm 18% R3load -testconnect
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
R3load: START OF LOG: 20071113095228
R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
R3load: version R7.00/V1.4 [UNICODE]
Compiled Oct 20 2007 06:20:06
R3load -testconnect
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1033
DbSl Trace: CONNECT failed with sql error '1033'
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1033
DbSl Trace: CONNECT failed with sql error '1033'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1033
DbSl Trace: CONNECT failed with sql error '1033'
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1033
DbSl Trace: CONNECT failed with sql error '1033'
(DB) ERROR: DbSlErrorMsg rc = 99
R3load: job finished with 1 error(s)
R3load: END OF LOG: 20071113095230
Please let me know if anybody have any idea on this.
Thanks in advance.

Your database isn´t fully started yet (in shutdown or startup) - check your alert.log
Also see
Note 655240 - Composite SAP note: ORA-01033
Markus

Similar Messages

Error during unicode conversion

Dear all,
we are facing one issue during unicode conversion. the code is as follows:
FIELD-SYMBOLS : <n> TYPE X,
                             <c> TYPE C.
DATA : a TYPE i.
DATA : x TYPE x.
MOVE <n> TO a.
a = a + 22.
MOVE a TO x.
ASSIGN x TO <c> CASTING TYPE c
and we are getting the following error:
ERROR : the length of "X" in bytes must be a multiple of the size of a Unicode character (regardless of the size of the unicode character
please guide on how this can be resolved in ECC.
Regards,
N.Jain

Hi,
here is some code to do it:
FIELD-SYMBOLS : <n> TYPE x,
                <c> TYPE c.
DATA : a TYPE i.
DATA : x TYPE x.
MOVE <n> TO a.
a = a + 22.
MOVE a TO x.
DATA:
buffer TYPE xstring,
conv TYPE REF TO cl_abap_conv_in_ce,
x_char.
buffer = x.
conv = cl_abap_conv_in_ce=>create(
       encoding = 'NON-UNICODE'
       input = buffer
CALL METHOD conv->read(
EXPORTING
    n    = 1
IMPORTING
    data = x_char
ASSIGN x_char TO <c>.
Regards
Walter Habich
Edited by: Walter Habich on Jun 10, 2008 4:09 PM

SAPInst Export Error during Unicode Conversion

Hello,
I started SAPInst, to export the source instance (for unicode conversion).
During the export preparation phase, I get the following error (in SAPInst)
ERROR
CJS-00030: Assertion failed: in component: NW_getDBInfo step: fillContextat this point the dbtype has to be != ind
ERROR
MUT-03025 Caught ESAPinstException in Modulecall:
ESAPinstException: error text undefined
ERROR
FCO-00011 The step fillContext with step key
|NW_Prepare_Export| ind| ind | ind | ind |0 |0 |NW_GetSidromProfiles |ind |ind |ind |ind |2 |0 |NW-getDBInfo |ind |ind |ind |4 |0 | fillContext was executed with status ERROR
Please help me how to rectify this error.
Thanks,
Haleem

Hello,
I recently experienced this problem, and it seems that when executing this step the <sid>adm account needs to be defined to use C shell. If its already set up to use C shell, check the <sid>adm logon scripts to make sure all the environment variables are being set correctly.
Regards,
Brad

Error during Unicode Conversion at DDNTF table

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

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!

Error during currency conversion and consistency check in a sales order

Hi Experts,
I am facing the below error in the sales order. The sales order is having so many items. The below error is coming for few items only. I have checked the currency exchange rates also. All are maintained properly.
Please advice me how to fix this error or which class,methods are responsible for checking the above details while saving the order.
Thanks,
Sri

Hi Christophe,
FYI
Error during currency conversion frm &1 to &2 (date &3, ref. curr. &4)
Message Class - CRM_CUMULATED_I
Message No     - 013
Error during currency conversion for &1 and &2
Message Class - CRM_CUMULATED_I
Message No     - 008
Consistency check: Logical key does not match
Message Class - CRM_CUMULATED_I
Message No     - 011
Thanks,
Sri

Error in Import during unicode conversion

Hello,
I am doing Combined upgrade and unicode conversion to ECC6 SR3.
Upgrade is completed sucessfully. During import i get an error stating :
bSl Trace: Error 959 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-959 occurred when executing SQL stmt (parse error offset=92)
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "REPOLOAD~0" ON "REPOLOAD" ( "PROGNAME", "R3STATE", "MACH" ) TABLESPACE PSAPSID620 STORAGE (INITIAL 209
7152 NEXT 0000010240K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )
DbSlExecute: rc = 99
(SQL error 959)
error message returned by DbSl:
ORA-00959: tablespace 'PSAPSID620' does not exist
This tablespace doesnt exist as it was upgraded to PSAPSID700.
I checked DBLORA.TPL and it has two references of 620 :
index storage parameters
loc: APPL0 PSAP@SCHEMAID@                 0000
     APPL1 PSAP@SCHEMAID@                   0000
     APPL2 PSAP@SCHEMAID@                  0000
     CLUST PSAP@SCHEMAID@                  0000
     DDIM PSAPDIMI                                      0000
     DFACT PSAPFACTI                                0000
     DODS PSAPODSI                                   0000
     POOL PSAP@SCHEMAID@                  0000
     SDIC PSAP@SCHEMAID@                     0
     SDOCU PSAP@SCHEMAID@                  0000
     *SLDEF PSAP@SCHEMAID@620              0000*
     *SLEXC PSAP@SCHEMAID@620            0000
     SLOAD PSAP@SCHEMAID@                  0000
     SPROT PSAP@SCHEMAID@                   0000
     SSDEF PSAP@SCHEMAID@700              0000
     SSEXC PSAP@SCHEMAID@700              0000
Thanks,
FBK

Hi Volker,
Thank you very much. Stupid error :-).
I also did step 2 with fixr3owns yesterday with SAPINST and then it worked. I got to step 3 "iSeries Installation Step", but got an error in SAPINST when "Creating infrastructure for SAP system BND". I logged off SAPINST, patched CRTR3SYS and started SAPINST again and then got the error in step 2 wirh fixr3owns.
I´m now past step 2 and in step 3 "iSeries Installation Step". And I get the same error as I got yesterday...
From the job log:
TMKSVR request processor: request was successful
Processing request from client 10.96.220.5:4350.
EXECUTE CRTR3SYS SID(BND) GLOBALHOST('SAP002') FORCEPROF(*NO)
ADBHOST('SAP002') 1 N
Keyword GLOBALHOST not valid for this command.
Keyword FORCEPROF not valid for this command.
Keyword ADBHOST not valid for this command.
Error found on CRTR3SYS command.
Errors occurred in command.
error: call_AS400_command: "CPF0006" caught after "CRTR3SYS SID(BND)
GLOBALHOST('SAP002') FORCEPROF(*NO) ADBHOST('SAP002')"
I can run "CRTR3SYS SID(BND) GLOBALHOST('SAP002') FORCEPROF(*NO)" manually.
Do you have any ideas?
Best regards
Henrik Hviid

Errors during Unicode Import

Hello,
I am getting errors during Import of Unicode Conversion. AABLG is a Cluster Table.
/usr/sap/P01/SYS/exe/run//R3load: START OF LOG: 20110110220222
/usr/sap/P01/SYS/exe/run//R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
/usr/sap/P01/SYS/exe/run//R3load: version R7.01/V1.4 [UNICODE]
Compiled Jun 19 2010 01:48:51
/usr/sap/P01/SYS/exe/run//R3load -ctf I /disk2/ABAP/DATA/SAPCLUST_1.STR /disk4/instdir/DDLORA.TPL SAPCLUST_1.TSK ORA -l SAPCLUST_1.log
/usr/sap/P01/SYS/exe/run//R3load: job completed
/usr/sap/P01/SYS/exe/run//R3load: END OF LOG: 20110110220222
/usr/sap/P01/SYS/exe/run//R3load: START OF LOG: 20110111135853
/usr/sap/P01/SYS/exe/run//R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
/usr/sap/P01/SYS/exe/run//R3load: version R7.01/V1.4 [UNICODE]
Compiled Jun 19 2010 01:48:51
/usr/sap/P01/SYS/exe/run//R3load -i SAPCLUST_1.cmd -dbcodepage 1100 -l SAPCLUST_1.log
DbSl Trace: ORA-1403 when accessing table SAPUSER
(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.
(GSI) INFO: dbname   = "P0120110110060126                                                                                "
(GSI) INFO: vname    = "ORACLE                          "
(GSI) INFO: hostname = "ecctemp                                                         "
(GSI) INFO: sysname = "HP-UX"
(GSI) INFO: nodename = "ecctemp"
(GSI) INFO: release = "B.11.31"
(GSI) INFO: version = "U"
(GSI) INFO: machine = "ia64"
(DB) INFO: AABLG created #20110111135853
myCluster (63.25.Imp): 679: error when retrieving table description for physical table AABLG.
myCluster (63.25.Imp): 682: return code received from nametab is 2
myCluster (63.25.Imp): 302: error when retrieving physical nametab for table AABLG.
(CNV) ERROR: data conversion failed. rc = 2
(DB) INFO: AABLG~0 created #20110111135854

Hello,
you need to ensure that the Unicode conversion is done during export (target code page 4102 or 4103).
This error typically occurs if the export does not include the Unicode conversion (simple system copy with Non-Unicode).
Best regards,
Nils Buerckel
Globalization Services
SAP AG

Unicode Conversion : Import Error in ABAP SAPCLUST Error

Hi
I am doing the unicode conversion ..
The export of the database is successful.. But during the import it is giving an error.
Export is done as per note 552464 (Code Page 4103)
Platform is windows server 2003 / Oracle 10.2
Loading of 'SAPCLUST' import package: ERROR
(GSI) INFO: vname    = "ORACLE                          "
(GSI) INFO: hostname = "CTSINTCOSNW5                                                    "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "CTSINTCOSNW5"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 1"
(GSI) INFO: machine = "8x Intel 801586 (Mod 4 Step 9)"
(DB) INFO: CLU4 deleted/truncated #20070301165425
myCluster (63.7.Imp): 2113: inconsistent field names (source) : physical field K1N05 appears as logic K1N5.
myCluster (63.7.Imp): 2114: further investigation recommended.
myCluster (63.7.Imp): 1952: error when checking key field consistency for logic table TACOPC    .
myCluster (63.7.Imp): 1955: logic table is canonical.
myCluster (63.7.Imp): 1958: received return code 2 from c3_uc_check_key_field_descr_consistency.
myCluster (63.7.Imp): 1252: unable to retrieve nametab info for logic table TACOPC    .
myCluster (63.7.Imp): 8096: unable to acquire nametab info for logic table TACOPC    .
myCluster (63.7.Imp): 2835: failed to convert cluster data of cluster item.
myCluster: CLU4       *00001*
myCluster (63.7.Imp): 320: error during conversion of cluster item.
myCluster (63.7.Imp): 323: affected physical table is CLU4.
(CNV) ERROR: code page conversion failed
             rc = 2
.--============--
RSCP - Error
`----
(DB) INFO: disconnected from DB
D:\usr\sap\ABU\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
D:\usr\sap\ABU\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20070301165425
Can any one help please ?
Thanks in advance

hi,
could you please have a look to SAP Note 902817 - Inconsistencies in cluster tables (log vs phys field name)
Cheers,
-Sunil

R/3 Export & Import during Unicod Conversion via SOCKET Method

Hi
We are in the process of upgrading our R/3 Enterprise to ECC 6.0. The size of the database is around 4 TeraBytes.
Can somebody help us with necessary documentation/ othe rinputs to handle R/3 Export & Import using SOCKET method? FYI we referred the SAP given doucments on the same. Any particular DOs & DO NOTs would be highly appreciated.
Thank You
Sai

Hi Rahul
regarding your 'Unicode doubt"' some ideas:
1) The Upgrade Master Guide SAP ERP 6.0 and the Master Guide SAP ERP 6.0 include introductory information. Among other, these guides reference the SAP Service Marketplace-location http://service.sap.com/unicode@sap.
2) In Unicode@SAP can you find several (content-mighty) FAQs
Conclusion from the FAQ: First of all your strategy needs to follow your busienss model (which we can not see from here):
Example. The "Upgrade to mySAP ERP 2005"-FAQ includes interesting remarks in section "DO CUSTOMERS NEED TO CONVERT TO A UNICODE-COMPLIANT ENVIRONMENT?"
"...The Unicode conversion depends on the customer situation....
... - If your organization runs a single code page system prior to the upgrade to mySAP ERP 2005, then the use of Unicode is not mandatory. ..... However, using Unicode is recommended if the system is deployed globally to facilitate interfaces and connections.
- If your organization uses Multiple Display Multiple Processing (MDMP) .... the use of Unicode is mandatory for the mySAP ERP 2005 upgrade....."
In the Technical Unicode FAQ you read under "What are the advantages of Unicode ...", that "Proper usage of JAVA is only possible with Unicode systems (for example, ESS/MSS or interfaces to Enterprise Portal). ....
=> Depending on the fact if your systems support global processes, or depending on your use of Java Applications, your strategy might need to look different
3) In particular in view of your 3rd option, I recommend you to take a look into these FAQs, if not already done.
Remark: mySAP ERP 2005 is the former name of the application, which is named SAP ERP 6.0, now
regards, and HTH, Andreas R

ORA-00942 Error during unicode export of BI 7.0

Hello Everyone,
I am doing an export of a non-unicode BI 7.0 system to convert and import it into a Unicode database. All the jobs have passed except one and I see the following error in the log file (SAPAPPL0_3.log)
/usr/sap/ABD/SYS/exe/run/R3load: START OF LOG: 20080302124247
/usr/sap/ABD/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
/usr/sap/ABD/SYS/exe/run/R3load: version R7.00/V1.4
Compiled Jun 9 2007 09:20:06
/usr/sap/ABD/SYS/exe/run/R3load -e SAPAPPL0_3.cmd -datacodepage 4102 -l SAPAPPL0_3.log -stop_on_error
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
(RSCP) WARN: UMGCONTAINER has 1 problems.
(RSCP) INFO: UMGSETTINGS nametab creation: ok.
(RSCP) INFO: Global fallback code page = 1100
(RSCP) INFO: Common character set is not 7-bit-ASCII
(RSCP) INFO: Collision resolution method is 'fine'
(RSCP) INFO: R3trans code pages = Normal
(RSCP) INFO: EXPORT TO ... code pages = Normal
(RSCP) INFO: Check for invalid language keys: active, by default
(RSCP) INFO: I18N_NAMETAB_NORM_ALLOW = 999999999
(RSCP) INFO: I18N_NAMETAB_NORM_LOG   = 1000000002
(RSCP) INFO: I18N_NAMETAB_ALT_ALLOW = 10000
(RSCP) INFO: I18N_NAMETAB_ALT_LOG    = 10003
(RSCP) INFO: I18N_NAMETAB_OLD_ALLOW = 0
(RSCP) INFO: I18N_NAMETAB_OLD_LOG    = 500
(GSI) INFO: dbname   = "ABD20070922100908
(GSI) INFO: vname    = "ORACLE                          "
(GSI) INFO: hostname = "ussbbdd5                                                        "
(GSI) INFO: sysname = "HP-UX"
(GSI) INFO: nodename = "ussbbdd5"
(GSI) INFO: release = "B.11.23"
(GSI) INFO: version = "U"
(GSI) INFO: machine = "ia64"
(GSI) INFO: instno   = "INITIAL   "
(EXP) ERROR: DbSlExeRead failed
rc = 103, table "/BIC/SZTERR_CD"
(SQL error 942)
error message returned by DbSl:
ORA-00942: table or view does not exist
(DB) INFO: disconnected from DB
/usr/sap/ABD/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/ABD/SYS/exe/run/R3load: END OF LOG: 20080302124251
When I run the following command on /BIC/SZTERR_CD, I do not get any table information back. I am not sure how to fix it though.
SELECT * FROM DBA_OBJECTS WHERE OBJECT_NAME = '/BIC/SZTERR_CD ';
I did finish all the unicode preconversion steps and also ran the SMIGR_CREATE_DDL program. I had exported recently from the same system but I never got this error during that run.
Another question is about the order in which the steps need to be performed. I completed the preconversion steps, then ran the SMIGR_CREATE_DDL program before proceeding to the export phase. Is this right or does it not matter?
Thanks again for your help!

Hello Stacy,
> When I run the following command on /BIC/SZTERR_CD, I do not get any table information back. I am not sure how to fix it though.
> SELECT * FROM DBA_OBJECTS WHERE OBJECT_NAME = '/BIC/SZTERR_CD ';
If the object does not exists on the source target database, please check if the ddic of sap still contains the table definition. (SE11 or SE14)
If yes you can set the status of the table /BIC/SZTERR_CD to "ok" in the corresponding task file.
You can not fix this problem in other way after you have started the conversion, because of the export files are already generated (with the information of the sap ddic)...
> I completed the preconversion steps, then ran the SMIGR_CREATE_DDL program before proceeding to the export phase. Is this right or does it not matter?
That was the right way.
Regards
Stefan

Syscopy (during Unicode convertion): Import on same tablespace layout

Hi forum,
we're working on a Unicode convertion of our ECC landscape made of Solaris
10 Sparc and Oracle 10.2.0.4.
We use the procedure described in UC for SAPNetWeaver 7.0 SP 14 and
higher. Export runs well without error
or problem in our db (1,6 TB of used space).
During import SAPinst show me a different, then source system,
tablespaces layout:
PSAPSR3
PSAPSR3700
PSAPSR3FACT
PSAPSR3ODS
PSAPSR3USR
SYSAUX
PSAPUNDO
PSAPTEMP
SYSTEM
But my soursce system was:
PSAPBTABD
PSAPBTABI
PSAPCLUD
PSAPCLUI
PSAPDDICD
PSAPDDICI
PSAPDIMD
PSAPDIMI
PSAPDOCUD
PSAPDOCUI
PSAPEL700D
PSAPEL700I
PSAPES700D
PSAPES700I
PSAPFACTD
PSAPFACTI
PSAPLOADD
PSAPLOADI
PSAPODSD
PSAPODSI
PSAPPOOLD
PSAPPOOLI
PSAPPROTD
PSAPPROTI
PSAPSOURCED
PSAPSOURCEI
PSAPSTABD
PSAPSTABI
PSAPTEMP
PSAPUNDO
PSAPUSER1D
PSAPUSER1I
PSAPZ***********
PSAPZ***********
PSAPZ***********
SYSAUX
SYSTEM
We have already read 425079, so, can we use source system layout?
can SAPinst use our previous tablespace layout during import? ... or do
we must it manualy?
Regards.

Hi,
>It is far better that you create the target database using the new layout. The old tablespace layout with multiple tablespaces and >data/index separation is no longer adapted to modern environments, and a Unicode conversion gives you a unique opportunity to >switch to a more appropriate structure for your DB.
So... to do it: I leave standard tablespace (without create my old tablespace PSAPZ*******) and then enlarge enough to load our tables? ... do I modify any other file/script for the import?
Regards.

Performance during Unicode Conversion

Hello,
currently we are planning to do a Unicode Conversion on a Linux/MaxDB System.
The DB has a size of approx. 350 GB. The system runs on Fujitsu-Siemens FlexFrame hardware.
One problem is that during a test conversion the export of the DB took more than 24 hours.
This seems too much regarding the DB size.
We know that filesystem and RAM and CPUs influence the export duration.
What possibilities do we have to tune the export with "software" tools?
- table splitting
For example: Our largest table has ~26GB datasize.
How do we split this table?
In 10 parts or in 20 or in 200?
If you could please post your experiences.
Regards, Michael

I don´t wanna discourage you but I´m not sure if splitting that single table will help alot.
The problem with this combination is the fact, that the MaxDB database reads data block-by-block, means, exeucting single I/Os for each block to read. Given that fact and the fact, that each I/O will be ran over an NFS (with the known latency) it´s unlikely that you will get much more speed out of this.
The problem is NOT the speed between the NAS and the database server, if you will look on the network traffic you will see, that there´s plenty left. The problem is the latency on the client side (the database server) when you put your files on NFS.
I can export a 250 GB database in under 3 hours (admittedly - without UC conversion) using a direct fibrechannel connection (so non-NFS) so the database itself is certainly not the problem, it´s the combination of the usage of NFS (no matter if v2 or v3) and the way the MaxDB database reads data.
I´ve been involved in a likewise project and with a NetApp specialist and some in-depth tuning we were able to gain 15 - 20 % speed but not more.
Markus

Usage of Conversion Classes During Unicode Conversion

Hi,
I have code
"TRANSLATE BBKF-SGTXT FROM CODE PAGE '0100' TO '0120'" Now During Unicode i need to Use the Conversion classes
Can any one help to proceede further on this
Actually I am using CL_ABAP_CONV_OUT_CE and I am getting the Data in Binary Format But I want that to be in Character format can any one suggest me
Thanks & Regards,
Prasad

Do you have an EBCDIC system with code page 0100? (check it using SNLS transaction)
In that case, CL_ABAP_CONV_OUT_CE is okay.
After having converted to code page 0120 (into xstring), here is how to cast xstring variable to character.
DATA x TYPE x LENGTH 800. " so that to compile, x length
" must be a multiple of 4 (don't ask why)
FIELD-SYMBOLS <c> TYPE c.
x = xstring. "make sure x is long enough
ASSIGN x TO <c> CASTING.
BBKF-SGTXT = <c>.

Minimize downtime during UNICODE conversion

Hello forum !
I am looking at the UNICODE conversion of a large (?) SAP Oracle database for ECC. The Database it self is at about 10 TB. UNICODE converting this in one single run will take too long to fit inside the company defined tolerable downtime window.
When looking at the data I find that the largest 50 tables makes up about 75% of the total database size. Most of the 50 largest tables have data for several years back, and I am able to partition the tables with one partition pr year.
The good thing about this is that I am able to make the partitions with old data (more than one year old data) READ-ONLY.
My assumption is that I will be able to UNICODE convert 60-70% and create the indexes for these partitions without taking down the database to be converted.
Now,- doing the downtime-phase I will be able to exclude the old partitions of the largest tables in the export since I have already created a new UNICODE database with these objects and thereby drastically reducing the required downtime.
Is there anyone who has any experience with an approach like the one I have schetched out here ?
Kjell Erik Furnes

Can you please be a bit more specific on your installation? How long is your possible downtime (export time should be about 2/3 of that)? How long is your actual export estimation? Do you have suitable hardware (CPU/disk)?
What you absolutely need to have:
[1043380 - Efficient Table Splitting for Oracle Databases|https://service.sap.com/sap/support/notes/1043380] -> export tables with ROWID splitting
[855772 - Distribution Monitor|https://service.sap.com/sap/support/notes/855772] -> enables distributed and parallel export/import
So on the hardware side you will need, a storage subsystem as fast as possible with two copies of the disks (one for exporting and one for importing). A bunch of application servers with fast CPUs helps a lot, everything connected with at least gigabit ethernet.
If you knew all this already, sorry for the spam. But i achived throughputs at about 400gb/hour on a medium sized hardware, i think throughputs of 1tb/hour should be possible (not talking about cluster tables
Regards, Michael

Nametab issue during unicode conversion

There are some tables inconsistent durning Unicode conversion, is it possible to delete them?
Moderator message: not directly related to ABAP development, please have a look in the Netweaver forums, alway search for information before asking.
Edited by: Thomas Zloch on Dec 23, 2010 1:32 PM

Hi,
Reposting the question again, as earlier one was incomplete.
We are doing Unicode Conversion activity in one of our system. After running through UCCHECK transaction, we got around 80 programs in which most of them were resolved manually. When we are trying to edit one object, the error"Namespace /OSJ8C/' does not exists is displayd. Any help to resolve this issue will be highly appreciated .

Error during Unicode Conversion - Import

Similar Messages

Maybe you are looking for