SPUMG Unicode Conversion Phase

Hello experts,
We are currently in an MDMP System, ECC5.
After running an analysis, it seems that our vocabulary contains many words than combine elements from two or more languages.
Therefore, the language field for those entries is not set.
We wanted to know how are we supposed to decide the correct language for those fields?.
thanks in advance,
Eli.

I have hebrew, english, and german.
as far as I know , english and german are in the same code page , so the decision is only whether its hebrew or not.
yes
are you saying that im supposed to login in hebrew and take a look at those entries?
Exactly.
This is MDMP. You get the characters displayed only in the codepage you logged on. So if you have that "abcde" plus the hebrew character it may be displayed completely different in Hebrew. The database stores ASCII codes and the SAPGUI displays those in the codepage you chose during logon. That's the concept of MDMP.
If e. g. someone entered an address of a customer with a character such as "à", this is displayed as "א" if you logon in Hebrew.
what am i supposed to see exactly? and how does it matter which table generated the entry?
The table does matter because you may estimate then what it could be by having a context.
another question, can I leave the language field empty? or is it neccessary to fill it in order to complete the conversion.
You can leave it empty but you will later in postprocessing (SUMG) need to specify the language anyway to complete the conversion.
I know, all that is very tedious and that's why it's best to convert to Unicode to never have to deal again with those kind of things.
Markus

Similar Messages

  • Unicode conversion phase after ECC6 Upgrade

    Hello guros,
    We have successfuly completed the upgrade from ECC5 to ECC6 EHP4.
    Part of our full upgrade plan is to also convert the system to a unicode compliant system.
    I assume something went wrong during the DB export , because now many entries that are supposed to be in hebrew in our database tables appear like gibberish (Its a trial system - dont worry).
    What I find weird about these occurances is that within such a table, some lines appear fine and even some rows appear fine in hebrew , whereas others dont.
    Let's take the system user table for example:
    (USER, NAME , SURNAME, ADDRESS).
    USER1 | שלום | עליכם | יקרים |
    USER2 | %%$% | אלי | #$$%#$ |
    USER3| #$%#$% | $##%$#%| $#%#$$%%#
    Unresolved symbols represnt gibberish.
    Is there  something that we might have missed?
    Thanks in advance, Udi.

    > Let's take the system user table for example:
    > (USER, NAME , SURNAME, ADDRESS).
    >
    > USER1 | שלום | עליכם | יקרים |
    > USER2 | %%$% | אלי | #$$%#$ |
    > USER3| #$%#$% | $##%$#%| $#%#$$%%#
    I would say that those entries were not correctly specified in your vocabulary as being Hebrew - OR
    Addresses have another speciality, they have a "creation language" field (LANGU_CREA). That field may be wrong filled if you e. g. create the user with an english logon and then change the user data to Hebrew (with Hebrew characters). The entry in the LANGU_CREA field however stays english. If you use that field now to decide the conversion of the addresse it will be converted wrong and you see gibberish.
    Markus

  • Unicode Conversion Preparations not finished

    Hello,
    we are upgrading our system to ERP 6.0 EHP 4 with unicode conversion.
    During the "Preprocessing" phase I get the following error:
    Error: The Unicode Conversion Preparations on the startrelease (transaction SPUMG)
    have not been finished yet.
    You cannot proceed with the upgrade unless the preparation has been finished.
    I started the transaction SPUMG, but I don't know what to do there. What needs to be done to continue the upgrade process.
    Thanks in advance
    Andreas Kasper

    SPUMG -
    Unicode conversion preparation transaction. Provides several database scans for checking the consistency of the non-Unicode database and for preparing the database tables for the export and conversion. These scans must be executed manually. 
    SPUMG is used to prepare the database tables for the system conversion.
    CHeck SAPnote # 928729, this has attached Unicode conversion guides.
    Download as per your scenario and proceed ahead accordingly.
    - Niraj

  • Unicode conversion in situ

    Hi SCN,
    I'm looking at the possibility of running a Combined Upgrade & Unicode Conversion (CUUC) in-situ; i.e. without a migration to new hardware.
    However in all my years of SAP Basis projects any Unicode conversion I've seen has involved a migration to new hardware (which makes good sense as the process is the same as an OSDB migration with R3load/MigMon).
    What I want to know is - has anyone ever run one in-place. I.e. keeping the same server and running the CUUC entirely inplace?
    This seems logically problematic as you need a target system to import to.
    I can imagine a process along these lines though...:
    1. Take SAP layer offline
    2. Run full backup of system
    3. Export system
    4. Drop database* (to make clean ready for new import)
    5. Run SPUMG/SUMG/SAPINST to setup Unicode database ready to receive import...
    6. ....and continue to run import into that database
    7. Complete Unicode conversion process
    However the big issue here for me is
    (a) *dropping the live production system is far from attractive.... I'm presuming everyone would do as I've always seen and combine this with a migration to new improved hardware, so that a backout to the old system is simple
    (b) I'm not sure at what point with the SAP tools (SPUMG/SUMG/SAPINST) this process would become convoluted with it all being in-situ on the same box. I.e. I'm not sure if it's something the SAP tools are really designed to cater for.
    Any input/discussion on these points would be very welcome.
    Regards, doonan_79

    FYI Community. Feeling after reading and research is to use a temorary server to import unicode converted system data into; then swing disks back to the original host. Making all required hostname updates during the process.
    Allowing for parallel export/import, but going back to the original configured host to complete the process.

  • LRAW data Conversion during Unicode Conversion

    Hi,
    We have upgraded our 46C MDMP system to Unicode system.
    After conversion we found that some of the tables with field of LRAW type are having conversion issue.
    In 46C system, Russian data which enetered in the MS Cyrillic (Code page 1504), is converted to code page 1500 after unicode conversion.
    We have not found any entries for this table in vocabulary, reprocess log or in SUMG.
    For example table STXL. This table contains Purchase order text for the material.
    Report HRUU_CONVERT_IN_UNICODE does not shows LRAW data field for conversion.
    Can you suggest how LRAW data can be converted from 1500 to 1504 code page.
    Thanks and Regards
    Rahul

    Hi Rahul,
    STXL is a language dependent INDX type table. Hence SPUMG will not scan this one with the default settings.
    Please have a look at the description of INDX type table handling in the Unicode conversion Guide.
    In the Unicode system, you can use UMG_ADJUST_STXL for the conversion.
    However please be aware of the restrictions:
    Once you have decided about the code page and converted the object, this cannot be reverted !
    Therefore it is highly recommended to check the display mode first and in addition test it extensively on a sandbox system !
    Best regards,
    Nils Buerckel
    SAP AG

  • 4.7EEx1.10 to ECC6.0 upgrade and Unicode conversion

    Hi Experts,
    We are going to initiate the upgrade from next month onwards. Subsequently i have started preparing the plan and strategy for the same.
    As our current setup is 4.7EEx110/Win 2003 R2-64 bit/Oracle 10.2.0.4.0 (Non unicode). And we have recently migrated on to this setup from WIn2k 32 bit. Also the current hardware is Unicode compatible.
    With respect to strategy for achieving this Upgrade and Unicode conversion, i am planning as follows.
    Step 1) Perform Unicode conversion on the current landscape (Both Export/import on the same servers)
    Step 2) Setup Temporary landscape as part of Dual maintenance strategy and migrate data from the current systems to temporary systems using backup/restore method.
    Step 3) Perform the SAP version upgrade on the current landscape and setup transport routes from temporary to current landscape in order to keep it in sync
    Step 4) after successful upgrade, decommission the temporary landscape
    Please provide your suggestions and valuable advices if there is anything wrong with my strategy and execution plan.
    Regards,
    Dheeraj

    Hi,
    Thanks. As i have already referred these notes as i am seeking advise with respect to my upgrade approach.
    However i have planned to perform in the following manner.
    1) Refresh Sandbox with Prod data and perform Upgrade to ECC6.0 EHP5 & subsequently Unicode conversion on the same server (Since both export & Import has to perform on the same hardware as we have recently migrated on this hardware which is Unicode compatible)
    2) Setup temporary landscape for DEv & QAs and establish transport connection to Production system in order to move urgent changes
    3) Keep a track of the changes which have transported during upgrade phase so that the same can be implemented in the upgraded systems i.e. Dev & QAS
    4) After Sandbox Migration and signoff, we will perform Dev & QAS upgrade & unicode conversion on the same hardware (Note: Since these are running on VMware can we export the data from the upgraded system and import on to a new VM?)
    5) Plan for production cutover and Upgrade the Prod system to ECC6.0 Ehp5 and then Unicode conversion. As i am planning to perform upgrade over the weekend and then Unicode conversion activity in the next weekend (Is it a right way?)
    My Production setup: DB on one Physical host and CI on separate Virtual host
    6) After the stabilization phase, we are planning for OS & DB upgrade as follows:
          a) Windows upgrade from 2003 R2 to Windows 2008 R2
          b) Oracle Upgrade from 10.2 to 11.2
    If anyone thinks that there is anything wrong with my above approach and need changes then please revert.
    I have one more doubt as I am going to upgrade 4.7EEx110 (WAS 620, Basis SP64) to ECC6.0 EHp5.As I presume that I can straight away upgrade from the current version to ECC6.0 Ehp5 without installing EHP. Kindly confirm
    Thanks

  • Unicode Conversion

    Hi ,
           We are into the initial phase of upgradation from 4.6 to ECC6 .
    ineed  some of the questions below ...
    1.    what is mean by unicode conversion ?
    2.    in an object example reoprt or script or bdc or module pool objects what are      need to be done to convert it as ab unicode object ?
    3.    next is after working on the unicode object we need to work on the spoue objects .what is mean by that ?
    could you guys can clear my dought for the above mentioned question ?
    thanks,
    vinay

    plz go through the following links.....
    http://help.sap.com/saphelp_nw04/helpdata/en/79/c5546db3dc11d5993800508b6b8b11/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/79/c55470b3dc11d5993800508b6b8b11/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/79/c55473b3dc11d5993800508b6b8b11/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/79/c55476b3dc11d5993800508b6b8b11/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/79/c5547cb3dc11d5993800508b6b8b11/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/79/c5547fb3dc11d5993800508b6b8b11/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/79/c55482b3dc11d5993800508b6b8b11/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/79/c55485b3dc11d5993800508b6b8b11/content.htm
    The Link will be helpful to you.
    Re: Upgrade 4.6 to ECC - What are the responsibilites
    regarding Unicode influence in Standard programs
    Very good document:
    http://www.doag.org/pub/docs/sig/sap/2004-03/Buhlinger_Maxi_Version.pdf
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d37d1ad9-0b01-0010-ed9f-bc3222312dd8
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/589d18d9-0b01-0010-ac8a-8a22852061a2
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f8e316d9-0b01-0010-8e95-829a58c1511a
    You need to use the transaction UCCHECK.
    The report documentation is here
    ABAP Unicode Scan Tool UCCHECK
    You can use transaction UCCHECK to examine a Unicode program set for syntax errors without having to set the program attribute "Unicode checks active" for every individual program. From the list of Unicode syntax errors, you can go directly to the affected programs and remove the errors. It is also possible to automatically create transport requests and set the Unicode program attribute for a program set.
    Some application-specific checks, which draw your attention to program points that are not Unicode-compatible, are also integrated.
    Selection of Objects:
    The program objects can be selected according to object name, object type, author (TADIR), package, and original system. For the Unicode syntax check, only object types for which an independent syntax check can be carried out are appropriate. The following object types are possibilities:
    PROG Report
    CLAS Class
    FUGR Function groups
    FUGX Function group (with customer include, customer area)
    FUGS Function group (with customer include, SAP area)
    LDBA Logical Database
    CNTX Context
    TYPE Type pool
    INTF Interface
    Only Examine Programs with Non-Activated Unicode Flag
    By default, the system only displays program objects that have not yet set the Unicode attribute. If you want to use UCCHECK to process program objects that have already set the attribute, you can deactivate this option.
    Only Objects with TADIR Entry
    By default, the system only displays program objects with a TADIR entry. If you want to examine programs that don't have a TADIR entry, for example locally generated programs without a package, you can deactivate this option.
    Exclude Packages $*
    By default, the system does not display program objects that are in a local, non-transportable package. If you want to examine programs that are in such a package, you can deactivate this option.
    Display Modified SAP Programs Also
    By default, SAP programs are not checked in customer systems. If you also want to check SAP programs that were modified in a customer system (see transaction SE95), you can activate this option.
    Maximum Number of Programs:
    To avoid timeouts or unexpectedly long waiting times, the maximum number of program objects is preset to 50. If you want to examine more objects, you must increase the maximum number or run a SAMT scan (general program set processing). The latter also has the advantage that the data is stored persistently. Proceed as follows:
    Call transaction SAMT
    Create task with program RSUNISCAN_FINAL, subroutine SAMT_SEARCH
    For further information refer to documentation for transaction SAMT.
    Displaying Points that Cannot Be Analyzed Statically
    If you choose this option, you get an overview of the program points, where a static check for Unicode syntax errors is not possible. This can be the case if, for example, parameters or field symbols are not typed or you are accessing a field or structure with variable length/offset. At these points the system only tests at runtime whether the code is sufficient for the stricter Unicode tests. If possible, you should assign types to the variables used, otherwise you must check runtime behavior after the Unicode attribute has been set.
    To be able to differentiate between your own and foreign code (for example when using standard includes or generated includes), there is a selection option for the includes to be displayed. By default, the system excludes the standard includes of the view maintenance LSVIM* from the display, because they cause a large number of messages that are not relevant for the Unicode conversion. It is recommended that you also exclude the generated function group-specific includes of the view maintenance (usually L<function group name>F00 and L<function group name>I00) from the display.
    Similarly to the process in the extended syntax check, you can hide the warning using the pseudo comment ("#EC *).
    Applikation-Specific Checks
    These checks indicate program points that represent a public interface but are not Unicode-compatible. Under Unicode, the corresponding interfaces change according to the referenced documentation and must be adapted appropriately.
    View Maintenance
    Parts of the view maintenance generated in older releases are not Unicode-compatible. The relevant parts can be regenerated with a service report.
    UPLOAD/DOWNLOAD
    The function modules UPLOAD, DOWNLOAD or WS_UPLOAD and WS_DOWNLOAD are obsolete and cannot run under Unicode. Refer to the documentation for these modules to find out which routines serve as replacements.
    Plzz Reward if it is useful

  • Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

    Hallo All,
    We perform CU&UC of R/3 4.6C sandbox system to the ERP 6.0 EHP5.
    Currently the upgrade phase is completed and Unicode conversion should
    be started (we are in the step "Additional Preparation Steps in NW 7.02
    non-UC" in the CU&UC guide).
    In various transactions (PFCG - Generating of profiles, SPAM/SAINT ) we
    received an error "SAP characters 00367 and 00065 are not unique in
    character set 1180". As a workaround we temporarily deleted Polish
    language (PL) in program RSCPINST and activated (so only codepage 1100
    was active). Currently we have activated the Polish language again.
    In the source 4.6C system TMB (created by System Copy from productive
    system PMB) there was also the configuration in RSCPINST of more than 1
    codepage (1100, 1401) and in TCPDB table 1180 codepage was configured
    (see attached pictures).
    Our question :
    How is it possible to avoid this situation in upgrades of following
    system (IMB, QMB, PMB)? Could this configuration cause any
    problems/inconsistencies during/after Unicode conversion export &
    import ?
    Regards Peter Gauer

    Hello Nils,
    After upgrade, before unicode conversion we got the following error message in PFCG, SAINT,..
    "SAP characters 00367 and 00065 are not unique in character set 1180"
    I got the information from T-Systems that they excluded polish languages out of RSCINST,
    then codepage 1100 was used, than T-Systems added polish language again to have the original situation.
    First message I got with the simulation (choose  blank latin-1)
    The required language combination is supported
    only in Unicode systems
    Please refer to SAP Note 73606.
    Now I Choose: 4EU,  EuropTranslit
    and  simulation showed no message above, but went to the next page.
    see below
    S e l e c t e d   S e t t i n g s :
    Language(s):
    EN (E) English
    FR (F) French
    DE (D) German
    PL (L) Polish
    ES (S) Spanish
    Country code:
    4EU    EuropTranslit
    R e s u l t s :
    Code page configuration type:
    Non-Unicode - Single Code Page configuration
    Processed language entry:
    DEFLS
    Language(s) and Corresponding Code Page(s):
    EN (E) 1180   Transliteration from Latin-2 (...) to Latin-1
    FR (F) 1180   Transliteration from Latin-2 (...) to Latin-1
    DE (D) 1180   Transliteration from Latin-2 (...) to Latin-1
    PL (L) 1180   Transliteration from Latin-2 (...) to Latin-1
    ES (S) 1180   Transliteration from Latin-2 (...) to Latin-1
    T a s k s :
    Required OS locales and their current status:
    Locale installed     = the locale is installed correctly
    Set locale failed    = the locale needs to be corrected on the app server
    citmb07_TMB_07       de_DE.ISO-8859-1               Locale installed
                         en_US.ISO-8859-1               Locale installed
                         fr_FR.ISO-8859-1               Locale installed
                         de_DE.ISO-8859-1               Locale installed
                         es_ES.ISO-8859-1               Locale installed
    Required profile parameter modifications:
    RSCPINST does NOT change the value of profile parameter.
    Please check the value of below parameter(s) after activation.
    1)  Please update zcsa/installed_languages.
        e.g. Copy the new value and paste it into a field in transaction RZ10
    New:                  DEFLS
    Current (sorted):
    citmb07_TMB_07       DEFLS
    2)  Please proceed with Check result for below parameter(s):
    OK     Checked and no inconsistency found.
    Regards Peter

  • 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 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

  • 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

  • Combined Upgrade and Unicode conversion question

    Hello Everyone,
    I will be performing combined Upgrade and Unicode conversion soon. Currently i have run Prepare and do not have any errors.
    I have already run SPUMG consistency check and i do not have any errors there. Since this is Combined Upgrade and unicode conversion according to guide i do not need to do the Nametab conversion right now. But now if i go this place:
    SPUMG -> Status -> Additional Information  , i see a status with red for Unicode nametabs are not consistent or not up-to-date.
    Please let me know if i can ignore this step and do the nametab conversion after upgrade is complete and before unicode conversion.
    Thanks,
    FBK

    Please follow the instructions from the guides.
    The Unicode nametabs will be generated automatically during the upgrade.
    An additional check is integrated into the final preparation steps in the target releases.
    Regards,
    Ronald

  • MDMP unicode conversion - Vocabulary maintenace

    Hello,
              W have upgraded 4.5B MDMP system to ECC4 EHP4 and now we are in process of unicode conversion.
    please advice on as specified below.
    In SPUMG Scan process, we have completed the following scans:
    a) Tables without language Info
    b) Tables with Ambiguous language Info
    c) Indx Analysis
    For maintaining vocabulary  we have implemented notes 756534 &  756535, 871541. and Tables with language are also scanned. While handling vocabulary the system has displays 539158 with duplicates and 189314 when duplicates are discarded, which doesnot assigened any languages. We have 9 acive languages.
    As per Unicode conversion document i left out with only 2 more option a) HInt management b) Manual assignment
    How to handle this? is this a normal situation or any correction can be done?
    Thanks and Regards
    Vinay

    Hi Vinay,
    This Thread belongs to the Unicode forum:
    Internationalization and Unicode
    In my opinion one of the best and most efficient possibility to reduce the number of words
    is to make use of hints. Please follow the  Unicode Conversion Guide and SAP note 1034188.
    Application colleagues should be contacted in order to find proper hints.
    Please also note that report umg_vocabulary_statistic or um4_vocabulary_statistic is the best tool to evaluate tables for hint processing.
    And the rest of the vocab, which can not be assigned by the hints method or by the SAP notes you mentioned, need to be assigned by native speakers (manual effort !).
    As you can see, SPUMG is NOT just a tool to be executed by Basis staff.
    It needs in deed collaboration between Basis, Application and native speakers.
    And it should be clear that the duration of the scans can be quite high - therefore a trial & error approach will take time (especially for large systems).
    Best regards,
    Nils Buerckel
    SAP AG

  • Single Code Page Unicode conversion when source and target are the same

    Hi everyone.  We have recently upgraded our non-unicode 4.7 to ECC6 non-unicode.  Now we have begun researching the next step to convert to Unicode.  I know we could have done the Combined Upgrade and Unicode Conversion but I wanted to do thorough testing after the upgrade to eliminate too many variables if problems arose.
    So, my question is...has anyone done the Unicode conversion when source and target servers are the same?  Most documentation I've seen recommends a system copy to another box first.  I did find one forum thread that gave a high level approach to doing the conversion with just one server and listed this:
    Step 1:- Run Tcode SPUMG to scan
    Step 2:- Export Database
    Step 3:- Drop Database
    Step 4:- Create New Database
    Step 5:- Import database
    Step 6:- Chnage unicode Kernel
    What are your thoughts?  Is it supported?  Am I wasting my time and should I just bite the bullet and buy yet another system?  Thanks in advance.
    -Anthony

    Theoretically that's possible, yes. However...
    > Step 5:- Import database
    > Step 6:- Chnage unicode Kernel
    the import must be done using the Unicode kernel.
    So basically you can
    - export the old systm
    - uninstall system + database
    - start as if you were installing "from scratch" on a new box
    Markus

Maybe you are looking for