Unicode conversion question

Hi
I would like to perform a unicode conversion of our Solution manager instance.
The current version of the database is 7.6.6.6.
Can I use the command db_migratecatalog or do I have to perform a homogeneous Migration?
The instance was migrated from Oracle 32bit to MaxDB 64bit 7.6.4.
The _UNICODE parameter is set to YES but the VARCHAR fields are all ASCII.
My preference is to perform the migration on the current instance rather than homogeneous migration process.
Thanks
Doug

> Can I use the command db_migratecatalog or do I have to perform a homogeneous Migration?
>
> The instance was migrated from Oracle 32bit to MaxDB 64bit 7.6.4.
> The _UNICODE parameter is set to YES but the VARCHAR fields are all ASCII.
Hello Doug,
'db_migratecatalog' is a command that migrates the database catalog - not the data or the application tables.
Since _UNCODE is already set to YES the catalog of your database is UNICODE already.
If you want to convert your SAP system into a UNICODE system, you have to do a UNICODE conversion - there's no way to skip or bypass this.
regads,
Lars

Similar Messages

  • 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

  • Question - Preparation Unicode Conversion

    Hi,
    I am proceeding with the preparation for unicode conversion our ECC6 EhP3.
    I have a question on paragraph 1.5 of the manual SCP700SP16.doc (Language Flag Maintenance), ie, the report RADNTLANG is launched by SPUMG or I have to throw me a hand? and with which flags?
    Best regads,
    Diego.

    Hi Diego,
    in the UCG you can find:
    "Run report RADNTLANG to set the Text Lang. flag for all tables with one LANG/SPRAS field. This report should be run in the background, since it may take several hours. "
    Hence it is not integrated in SPUMG and has to be executed seperately.
    Regarding settings:
    1) You can set "detailed log" (which is never a bad idea !).
    2) Please have a look at SAP note 678221 for option 'Activate Inactively'
    3) All other options can be left empty. (you might try test mode, see SAP note 1293249).
    In general it is a good idea to execute this report during very low system activity (better: no activity at all), otherwise problems as described in SAP note 678221 are very likely.
    Best regards,
    Nils Buerckel
    SAP AG

  • MDMP Unicode Conversion problem during ECC upgrade

    hi Experts,
    I met a problem when upgrade from 4.6c to ecc 6.
    in 4.6c, some key users made some chinese written entries in table field while he/she was logon as English, so, the language field in this entry is "EN" although the actual language was written by chinese, after upgrade to ECC6, we found the chinese words became messy code, maybe it was due to the chinese were encoded by english codepage during conversion, my question is, how can I avoid this? I really don't want this happen in our PRD upgrade.
    The second question is: if a field contains both chinese and english, then, which language should it be assigned? english or chinese? I'm afraid if we assign this word as "EN" in vocabulary, then, after upgrade, the chinese part will be messy code.
    Thank you for your kind suggestions.
    Freshman

    Hi,
    you can either use transaction SUMG (manually) to repair the entries ( you have to add the according table - please check unicode conversion guide for details) or you need to change the language key in the table to Chinese if you want the Unicode conversion to convert the data correctly.
    To your second question: If the English texts are restricted to US7ASCII characters ("normal" English without special characters) those texts containing Chinese and English words can (and must !)  be assigned to ZH, as US7ASCII characters are included in the Chinese code page.
    Best regards,
    Nilsn Buerckel

  • Unicode Attribute - Necessary before Unicode Conversion?

    We are about to upgrade to ECC 6.0 with a Unicode conversion.
    I know that the "Unicode Checks Active" flag must be set in every
    customer program in order for the code to run in an ECC 6.0 unicode environment.
    My question is does this HAVE to be done before we do the unicode
    conversion. What we would like to do is convert the system to ECC 6.0
    with Unicode and then apply the transports which set the "Unicode
    Checks Active" flag. Since some of these transports contain new
    objects, we would prefer to upgrade to ECC 6.0, then convert to unicode
    first and apply the transports afterwards, to reduce the risk of potentially needing to rerun
    scans.
    Ideally we would have cleared all this before the upgrade, but we only
    found this issue in our test system after we had upgraded it.
    Is this a bad plan?

    Hi Chris,
    it is not necessary to set the Unicode flag for programming objects in order to succeed with the technical Unicode conversion.
    However please keep in mind that the programs without flag will not work in the Unicode environment (as you already stated).
    Best regards,
    Nils Buerckel
    SAP AG

  • 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

  • SAP Data File size considerably reduced after Unicode Conversion

    Hello Experts
    I have just performed a CUUC (Upgrade along with unicode conversion) from R/3 4.7 to ECC 6.0 EHP5. The data size that i earlier had was close to 463 GB (MSSQL MDF, LDF Files), after the data export to be converted to unicode the size was 45 GB (10% of actual data size, i feel this is normal after heterogeneous system copy), but after the import again the DATA file size is only 247 GB, is this normal ? or have i lost some data ? For ex, I tried checking tables like MSEG and the number of entries have reduced from 15,678,790 to 15,290,545.
    Could you kindly let me know if there is a way to check from Basis perspective if i have not lost any data ? I have followed all the procedures as per SAP Standards.
    Waiting for your quick reply.
    Best Regards
    Pritish

    Hi Nicholas
    Data is compressed during the new R3load procedure is understood, but why number of table entries have reduced is something which is still a question to me (in some cases increased as well) ? For example      
                                 Source          Target
    STPO                  415,725          412,150
    STKO                 126,710          126,141
    PLAF                 74,671                   78,336
    MDKP                 193,487          192,747
    MDPB                 55,329                   63,557
    Any suggestions or ideas ?
    Best Regards
    Pritish

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

  • BI Unicode Conversion impact on Microsft office tools

    Hello Friends,
    The BI version is BI 7.0, but we are using both Bex 3.x and Bex 7.0.BI 7.0 is being Unicode converted.
    Questions
    Does Unicode conversion have any impact on running the new/existing reports in 3.x and 7.x
    Does Unicode conversion have any impact on running the new/existing WAD reports.
    Does Unicode conversion have any impact on any of the Microsoft office products used by BI.
    Thanks!

    Since Excel is the starting point for BEx Analyzer, Excel 2007 would need to be tested. In BEx Web, if you have Excel as a save as option for queries, you will need to test that too. It also requires that the .NET Framework 3.0 be on the end user machine.
    See [OSS Note 1013201|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1013201]

  • Support package requierement for unicode conversion

    We are currently planning a unicode conversion for a SAP 4.7enterprise 1.1 extension version, running under Aix and Oracle, Basis/ABAP SP 35, HR SP20.
    According to the conversion guide, we must implement at least Support Pachage 60 for Abap and Basis, no explicit requierement for HR SP level.
    I believed that we must applied SAP procedure and exclusively HR Support Package Stack up to 27, which include SP 60 for Basis and Abap and HR 61.
    Our HR guys argue there is no indication from SAP that the SUPPORT PACKAGE STACK policy is mandatory and that SAP will provide us with normal support if we run the unicode conversion with SP Basis/ABAP 60, in other word even if we do not respect the support package stack combinaison. Need help on this issue before starting the project

    Exterprise 4.7 is Unicode-Compliant,meaning that you can have unicode in 4.7.
    If that the case, you should convert to 4.7 Enterprise Ext 2.00 Unicode First.
    later only upgrade to ECC 6.0 after 2 years, as you said.
    My answer is yes, to your question.
    You can download the installation kits at:
    http://service.sap.com/swdc
    anyway, it is recommended to have the latest SP in your system.
    cheers,
    Vincent

  • 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

  • Changes in source system dyring Unicode conversion

    Hi,
    I've upgraded our R/3 non-Unicode installation to ERP 6.0 non-Unicode using CU&UC guide. Now I plan to do the export & import phase to migrate the source system to Unicode.
    My question is, does the export phase (where the Unicode conversion actually takes place) do any changes in the source system? It' is a production system, and when something goes wrong or the time exceeds the limit I have for the export, I need to stop the export, put it back to production and try another time. So I need to be sure that the export itself doesn't do any changes to the source system.
    Thanks in advance
    Tomas

    Hi Tomas,
    the export simply "copies" the source system (and converts the data to Unicode) - it does not change it.
    Therefore you can still use it after the export is finished.
    Best regards,
    Nils Buerckel
    SAP AG

  • Issue in Unicode Conversion

    Hi,
    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.
    kindly find the below screenshot when we are trying to edit one object, we are facing the issue. Any help will be highly appreciated .
    Thanks,
    Grace

    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 .

  • Where is the Combined Upgrade and Unicode Conversion Guide

    Hi All
    Embarassing question time.
    I am after the Combined Upgrade and Unicode Conversion Guide for 4.7 to ERP 6.0, but can only find the Combined Upgrade and Unicode Conversion Guide for 46C to ERP 6.0.
    Can anyone advise where the 4.7 guide is.
    Thanks
    Sam

    Thank God SAP don't include it in the Install guide. The Install Guides are complex already. BTW if you need more info on unicode and its conversion go here
    https://service.sap.com/unicode@sap

Maybe you are looking for