Migration key w/ unicode conversion only

hello - i'm doing a unicode conversion of a NW04 system, following the Unicode conversion guide point by point for the proces. 
source:  nw04 / ora10202 / hpux ia64 (non-unicode)
target:  nw04 / ora10202 / hpux ia64 (unicode)
the import is failing bc it says the migration key is not good.  the guide didn't even mention the need for the key and i was not expecting to have to use one since the OS/DB remain the same on the target system.  any ideas?
==
from the MIGKEY.log file -
/sapmnt/LH7/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
/sapmnt/LH7/exe/R3load: version R6.40/V1.4 [UNICODE]
/sapmnt/LH7/exe/R3load -dbcodepage 4102 -i /tmp/sapinst_instdir/NW04/COPY/IMPORT/SYSTEM/ABAP/ORA/UC/DB/SAPUSER.cmd -l MIGKEY.log -K 
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12154
DbSl Trace: CONNECT failed with sql error '12154'

Hi Ben,
This looks more like a Oracle Error and not a Migration key related error.
I think its TNS Related, please check the following URL:
/thread/361384 [original link is broken]

Similar Messages

  • Migration Key for Unicode conversion

    Hi,
    I want to do a unicode conversion off ECC 6.0. The system was upgraded few days back from R/3 4.7 to ECC 6.0. Now it is required to convert the system to unicode. So to do the activity do we require Migration Key or any other approval from SAP for them to support us?
    Thanks,
    Suman

    If you don't change the platform no migration key is required and no intervention or migration consultant necessary.
    Depending on the number of languages/codepages it would probably make sense to get a Basis consultant (maybe remotely will be sufficient) to assist.
    Markus

  • SAP R/3 4.6 C to ECC 6.0 Upgrade using CU &UC method- Unicode conversion

    Basis Gurus
       I am working on upgrade from R/3 4.6C to ECC 6.0.
    ECC 6.0 upgrade completed( still in non Unicode).  Now I am in the process of Unicode conversion.
    I have used following methods for the upgrade.
    1. Combined Upgrade & Unicode conversion(CU & UC)
    2. Resource minimized( as I am doing it in Sandbox).
      As I understand I need to perform the DB export and Import now for the unicode conversion.
      According to the Upgrade document, First I need to run Export using R3load in ECC6.0(Non unicode)
      and then install Unicode system and import the same data file.
      My understanding was, when I choose, Resource minimized, I need to run Export and import
      in the same system.
      Can you please help me , whether I need another Unicode system for import ??
    Graham

    Hi,
    Dont get confused with upg strategy and unicode conversion.
    In general Upgrade strategy (either downtime-minimized/resource minimized)
    In unicode conversion you have export/import(exp/imp) of data concept
    In CU&UC approach you have to do in a streach to complete migrate from old release to new realease ECC 6.00.
    Using database independent (sapinst only) or Using database dependent (migration monitor or Distribution monitor)
    It can be done in 2 ways.
    If you dont have addtional server for unicode conversion
           1)you can either do exp on same hardware and take bakup and do import using the exp dump.
           2)Do exp on one server and prepare your target empty database on another server and complete imp of data.
    Hope this is clear.
    Regards,
    Vamshi.

  • Could you pls give the details about the Unicode conversion during Upgrade

    Hi,
    Can anyone give details about the Unicode conversion during SAP Upgradation fro 4.6C to ECC6.
    Waiting for quick response
    Best Regards,
    Padhy

    Hi,
    These are the few points i gathered during my upgradation project.
    Before starting any upgradation project, it is necessary to take up the back-up of the existing systems. As we are going to upgrade the entire system, we will be changing so many things and if something happens, without back-up, we will be in a trouble.
    So it is advised to keep a back-up of the existing system.
    Say for example we have the existing system E4B which is of Version 4.6C. Now we want to upgrade it to Version 4.7. Let us see how we can do it.
    Version upgrades not only means that we need to run the new Version CD over the existing Version System but only involves some other thing.
    Version Upgrade involves the following Steps.
    Say we want to upgrade for Version 4.7 from Version 4.6, which is in the System E4B. Now we created one more system called as E1B in which the upgradation for Version 4.7 can be done.
    • First copy the entire E4B system into the E1B System which is created for Version 4.7.
    • Apply the Version 4.7 CD provided by SAP over the E1B System.
    • Now check whether all the functionalities that was in E4B system works fine with E1B system also.
    Thus the Version Upgrade involves two steps.
    1. SAP Upgradation with the help of the CD
    2. Manual Upgradation.
    1. SAP Upgradation with the help of the CD
    This is nothing but after taking the copy of the existing system into a new system, the upgradation CD from SAP is applied over the new system.
    2. Manual Upgradation.
    This Manual Upgradation involves
    2.1 Upgradation of Standard Objects
    2.1.1 SPAU Objects
    2.1.2 SPDD Objects
    2.2 Upgradation of Custom Objects.
    Upgradation of Custom Objects can be placed under the following three categories.
    Unicode Compliance
    Retrofit
    Upgrade
    Please Find below some of the common Unicode Errors and their solutions
    1. Error:
    In case of Translate Error; ‘Dangerous use of Translate in Multilingual system.’
    Correction:
    To correct the Error occurring on TRANSLATE statement – use this additional statement before the Translate statement.
    SET LOCALE LANGUAGE sy-langu.
    This statement defines the Text Environment of all the programs & internal sessions in the language specified in the LANGUAGE KEY, which in this case is “sy-langu”, i.e. the log on language of the user.
    2. Error:
    In case of Open Dataset Error; ‘Encoding Addition must be included.’
    Correction:
    This Error occurs only when the MODE is TEXT.
    To correct the Error occurring on OPEN DATASET statement – use this statement instead.
    OPEN DATASET dataset_name FOR access IN TEXT MODE ENCODING DEFAULT.
    Where: dataset_name – NAME OF THE DATASET.
    Access – INPUT or OUTPUT or APPENDING or UPDATE.
    DEFAULT - Corresponds to UTF-8 in UNICODE systems &
    NON_UNICODE in NON-UNICODE systems.
    3. Error:
    In case of the usage of the Obsolete FM UPLOAD/DOWNLOAD or WS_UPLOAD/DOWNLOAD; ‘Function module UPLOAD is flagged as obsolete.’
    Correction:
    The FM GUI_DOWNLOAD/UPLOAD is used.
    The variations to be made in the parameters of the FM:
    1. Filename – It must be of STRING type.
    2. Filetype – “DAT” is not used any longer, instead “ASC” is used.
    3. Field Separator – The default value “SPACE” is used, incase for a TAB separated file “X” can be used.
    4. Error:
    In case of CURRENCY/UNIT Addition Error; ‘Use addition CURRENCY/UNIT when outputting.’
    Correction:
    The CURRENCY addition specifies the currency-dependant decimal places for the output of the data objects of type i or p. To obtain the currency-key, the field CURRKEY of the table TCURX is used. The system determines the number of the decimal places from the field CURRDEC of the selected CURRKEY.
    To correct this error follow the following method:
    WRITE: /3 'TOTAL',' ', TOTAL.
    WRITE: /3 ‘TOTAL’,’ ‘, TOTAL CURRENCY ‘2’. --- Where ‘2’is the Currency Key for Getting 2 decimal places.
    5. Error:
    In case of TYPE X Error; ‘Variable must be of C, N, D, T or STRING type.’
    Correction:
    We need to change all the Type X (Hexadecimal) variables to Type C with their values unchanged.
    So the method to be followed is:-
    1. Load the definition of the class CL_ABAP_CONV_IN_CE or CL_ABAP_CHAR_UTILITIES.
    2. Declare the variable as Type C, and use the method UCCP(‘XXXX’) of the class CL_ABAP_CONV_IN_CE where XXXX represents the 8-bit Hexadecimal value and incase the variable holds a Hex value for a Horizontal Tab , then the Attribute “HORIZONTAL_TAB” of the class CL_ABAP_CHAR_UTILITIES can be used directly instead of using the method UCCP.
    E.g.:
    i) *DATA: TAB TYPE X VALUE 09, “Tab character
    CLASS: CL_ABAP_CHAR_UTILITIES DEFINITION LOAD.
    DATA TAB TYPE C VALUE CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
    ii) * DATA: CHAR TYPE X VALUE 160.
    CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
    DATA CHAR TYPE C.
    CHAR = CL_ABAP_CONV_IN_CE=>UCCP(‘00AO’).
    (Here ‘00A0’ is the Hexadecimal equivalent of the decimal 160).
    3. Incase the TYPE X Variable has a length more than 1, then an internal table must be created for the variable.
    E.g.:
    CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
    DATA : LF(2) TYPE X VALUE 'F5CD'.
    DATA : BEGIN OF LF,
    A1 TYPE C,
    A2 TYPE C,
    END OF LF.
    LF-A1 = CL_ABAP_CONV_IN_CE=>UCCP('00F5').
    LF-A2 = CL_ABAP_CONV_IN_CE=>UCCP('00CD').
    6. Error:
    In case of the Character “-“Error; ‘The Character “-“can’t appear in names in Unicode Programs.’
    Correction:
    The Character “-“(Hyphen) appearing in Variable names is replaced by the character “_” (Under Score) for Unicode/Upgrade Compliance.
    E.g.:
    *wk-belnr LIKE bkpf-belnr,
    *wk-xblnr LIKE bkpf-xblnr,
    *wk-date LIKE sy-datum,
    *wk-wrbtr LIKE bseg-wrbtr,
    *wk-name1 LIKE lfa1-name1,
    *wk-voucher(8) TYPE c.
    wk_belnr LIKE bkpf-belnr,
    wk_xblnr LIKE bkpf-xblnr,
    wk_date LIKE sy-datum,
    wk_wrbtr LIKE bseg-wrbtr,
    wk_name1 LIKE lfa1-name1,
    wk_voucher(8) TYPE c.
    7. Error:
    In case of The SUBMIT-TO-SAP-SPOOL Error; ‘you should not use the statement SUBMIT-TO-SAP-SPOOL without the WITHOUT SPOOL DYNPRO addition. ‘
    Correction:
    1. Declare variables of type PRI_PARAMS, ARC_PARAMS, and a variable of TYPE C which would be used as a VALID FLAG.
    2. Call the FM GET_PRINT_PARAMETERS:
    CALL FUNCTION 'GET_PRINT_PARAMETERS'
    EXPORTING
    ARCHIVE_MODE = '3'
    DESTINATION = P_DEST
    IMMEDIATELY = 'X'
    IMPORTING
    OUT_ARCHIVE_PARAMETERS = archive_parameters
    OUT_PARAMETERS = print_parameters
    VALID = valid_flag
    EXCEPTIONS
    INVALID_PRINT_PARAMS = 2
    OTHERS = 4
    3. Use the SUBMIT-TO-SAP-SPOOL statement.
    E.g.:
    •     submit zrppt500
    •     using selection-set 'AUTO3'
    •     with res_no eq lo_rsnum
    •     with sreserv in preserv
    •     to sap-spool destination p_dest
    •     immediately 'X'. "print immediate
    DATA: print_parameters type pri_params,
    archive_parameters type arc_params,
    valid_flag(1) type c.
    CALL FUNCTION 'GET_PRINT_PARAMETERS'
    EXPORTING
    ARCHIVE_MODE = '3'
    DESTINATION = P_DEST
    IMMEDIATELY = 'X'
    IMPORTING
    OUT_ARCHIVE_PARAMETERS = archive_parameters
    OUT_PARAMETERS = print_parameters
    VALID = valid_flag
    EXCEPTIONS
    INVALID_PRINT_PARAMS = 2
    OTHERS = 4
    Submit zrppt500
    Using selection-set 'AUTO3'
    With res_no eq lo_rsnum
    with sreserv in preserv
    to sap-spool
    SPOOL PARAMETERS PRINT_PARAMETERS
    ARCHIVE PARAMETERS ARCHIVE_PARAMETERS
    WITHOUT SPOOL DYNPRO.
    8. Error:
    In case of Message Error; ‘Number of WITH fields and number of Place Holders are not same ‘.
    Correction:
    Split the statement after WITH into the same number as the place holder for that Message ID.
    E.g.:
    1. * MESSAGE E045.
    MESSAGE E045 WITH '' ''.
    2. in program ZIPI0801
    •     Start of change for ECC6
    •     message e398(00) with 'Could not find access sequence'
    •     'for condition type:'
    •     p_ptype.
    message e398(00) with 'Could not find '
    'access sequence'
    'for condition type:'
    p_ptype.
    •     End of change made for ECC6
    9. Error:
    In case of Move between 2 different Structures; ‘The structures are not mutually convertible in a Unicode program.’
    Correction:
    Make both the Data Types compatible and then assign the contents.
    E.g.:
    The statement –“move retainage_text to temp_text.” Gives an error, where RETAINAGE_TEXT is an internal table and TEMP_TEXT is a string of length 200.
    A Feasible solution for this is to specify from which position to which position of the string, the fields of RETAINAGE_TEXT should be assigned.
    TEMP_TEXT+0(1) = RETAINAGE_TEXT-DQ1.
    TEMP_TEXT+1(1) = RETAINAGE_TEXT-HEX.
    TEMP_TEXT+2(20) = RETAINAGE_TEXT-FILLER1.
    TEMP_TEXT+22(15) = RETAINAGE_TEXT-AMT_DUE.
    TEMP_TEXT+37(8) = RETAINAGE_TEXT-TEXT.
    TEMP_TEXT+45(10) = RETAINAGE_TEXT-DUE_DATE.
    TEMP_TEXT+55(1) = RETAINAGE_TEXT-DQ2.
    10. Error:
    In case of ‘no description found’; ‘add a GUI title’.
    Correction:
    In this type of error gui title is generally missing so add a GUI title to the module pool.
    11. Error:
    In case of ‘writing internal or transparent table’
    Correction:
    Write individual fields.
    E.g.:
    WRITE: / EXT. --> EXT should be a character type field
    WRITE: / EXT-ZZSTATE, EXT-LINE_NO, EXT-LINE_TXT, EXT-AMT, EXT-ZZSKUQTY.
    12. Error:
    In case of ‘combination reference table/field S541-UMMENGE does not exist’
    Correction:
    Was due to error in reference table S541. TABLE S541 has errors
    1)”Foreign key S541- ZZMARKET (ZZMARKET AND KATR2 point to different domains)”
    2)”Foreign key S541-ZZACQUIGRP (ZZACQUIGRP AND KATR8 point to different domains)”
    Changed the domain of ZZMARKET (from ZMKCODE to ATTR2)
    And that of ZMKCODE (from ZACCODE to ATTR8)
    13. Error:
    In case of ‘KEY does not exist’
    Correction:
    The reference table for field KBETR was KNOV earlier changed it to RV61A as KNOV was in turn referring to RV61A.
    14. Error:
    Incase of ‘WRITE’ statement, ‘Literals that take more than one line is not permitted in Unicode systems.’
    Correction: To correct this error, we need to align the spaces accordingly so that the statement doesn’t go beyond the line.
    15. Error:
    Incase of Data statement, ‘The data type ZWFHTML can be enhanced in any way. After a structure enhancement, this assignment or parameter might be syntactically incorrect………..’
    Correction: To correct this error, instead of “like” in the Data statement, use “type”.
    16. Error:
    Incase of DESCRIBE statement, ‘DESCRIBE can be used only with IN BYTE... Or IN CHARACTER mode in Unicode systems.’
    Correction: To correct this error, use additional text, IN BYTE MODE / IN CHARACTER MODE along with this statement.
    CHARACTER MODE is added when the data object is of flat/ character type.
    BYTE MODE is added when the data object is a deep structure.
    Syntax: DESCRIBE FIELD data_obj : LENGTH blen IN BYTE MODE,
    LENGTH clen IN CHARACTER MODE.
    Where blen and clen must be of type I.
    17. Error:
    Incase of DO-LOOP Error,’ In Do loop range addition needed‘
    Correction:
    An internal tables is declared and the two fields (VARYING field and NEXT field) were
    Included inside the internal table
    E.g.: In program SAPMZP02
    DO 11 TIMES
    •     VARYING STATION_STATE FROM STATION1 NEXT STATION2. “ECC6
    CASE SYST-INDEX.
    WHEN ‘1’
    STATION_STATE = STATION1.
    WHEN ‘2’
    STATION_STATE = STATION2.
    WHEN ‘3’
    STATION_STATE = STATION3.
    WHEN ‘4’
    STATION_STATE = STATION4.
    WHEN ‘5’
    STATION_STATE = STATION5.
    WHEN ‘6’
    STATION_STATE = STATION6.
    WHEN ‘7’
    STATION_STATE = STATION7.
    WHEN ‘8’
    STATION_STATE = STATION8.
    WHEN ‘9’
    STATION_STATE = STATION9.
    WHEN ‘10’
    STATION_STATE = STATION10.
    WHEN ‘11’
    STATION_STATE = STATION11.
    18. Error:
    Incase of the parameter QUEUE-ID Error,’ QUEUE-ID’ is neither a parameter nor a select option in program rsbdcbtc.’
    Correction:
    The parameter in program rsbdcbtc is QUEUE_ID and so is changed in this program
    E.g.: In program Z_CARRIER_EDI_INTERFACE
    •     submit rsbdcbtc with queue-id = apqi-qid and return. "ECC6
    •     The parameter name changed by replacing '-' with '_' as in program rsbdcbtc "ECC6
    Submit rsbdcbtc with queue_id = apqi-qid and return. "ECC6
    19. Error:
    Incase of EPC Error,’ Field symbol <TOT_FLD> is not assigned to a field ‘.
    Correction:
    This error couldn't be rectified as the error occurs in a Standard SAP include- LSVIMF29.
    The OS Note - 1036943 needs to be applied.
    Error:
    OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE.
    Correct:
    OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
    Error:
    Constants : c_tab type x value '09' .
    Correct:
    Constants : c_tab type abap_char1 value cl_abap_char_utilities=>horizontal_tab .
    Error:
    Data : begin of output_options occurs 0 . Include structure ssfcompop.
    Data : end of output_options .
    Correct:
    Data : output_options type standard table of ssfcompop with header line .
    Error:
    PARAMETERS : NAST TYPE NAST .
    Correct:
    PARAMETERS : NAST TYPE NAST NO-DISPLAY .
    Replace WS_DOWNLOAD and WS_UPLOAD by
    GUI_UPLOAD and GUI_DOWNLOAD and check the import and export parameter types , do the changes accordingly. Because FILENAME paramater type is different because of this it will give dump.
    For issue during Issue using SO_NEW_DOCUMENT_ATT_SEND_API1 Function module, the solution is After this FM we should put COMMIT WORK.
    Issue:
    Moving data from one structure to another structure if those two structures are not compatible
    Solution:
    we should use move-corresponding or field by filed we need to move it.
    If database structures are different in 4.6c and ECC6.0,
    Then we should go with append structure concept.
    While testing the report if it gives dump at Select query level or any database or view level,then just goto that table or view and goto the data base utility(se14) adjust the database. But make sure that selected radio button in se14 transaction should be activate and adjust database
    Also Check this link.
    http://help.sap.com/saphelp_nw04/helpdata/en/62/3f2cadb35311d5993800508b6b8b11/frameset.htm
    Reward points if helpful.
    Regards,
    Ramya

  • Syntax errors while migrating from non- unicode to Uni code

    What are the syntax errors while migrating from non unicode to Uni code

    Hi Sudheer,
    u can get the information related to errors while migrating from non- unicode to Uni code from the below...pls go through...
    Note 765475 - Unicode Conversion: Troubleshooting
    these are the notes related to the issues of migration form non unicode to ounicode.
    Related Notes
    986907 - SQL Server settings for R3load based system copy
    954001 - Error fix: ILLEGAL_SUBSTRING_MODIFICATION in SUMG
    936441 - Oracle settings for R3load based system copy
    928909 - Repair table data in SUMG in Unicode systems
    895804 - Problematic rows in table DMEE_TREE_NODE
    895560 - Support for languages only available in Unicode system
    885441 - Common Migration Errors
    842788 - DB Multiconnect: Unicode Migration
    837173 - RADCUCNT in Unicode Conversion: Collective Note
    756534 - Automatic Assignment of Languages with Character Statistics
    753334 - Unicode Conversion: Problem in Japanese device types
    726954 - Private Use Areas in Unicode Systems
    722193 - RFC legacy non-Unicode clients and Unicode servers
    718329 - R3load terminates the export during a Unicode conversion
    695196 - Error in the export for Unicode migration
    672835 - Textflags could cause problems during Unicode conversion
    627764 - Unicode migration: table pools inconsistent after conversion
    614550 - Troubleshooting BC-I18
    587896 - Add. info on upgrade to SAP R/3 Enterprise Core 4.70 SR1
    573044 - Unicode conversion for HR application
    480671 - The Text Language Flag of LANG Fields
    379940 - Unicode based mySAP availability
    79991 - Multi-Language and Unicode support of SAP applications
    73606 - Supported Languages and Code Pages
    42305 - RSCPINST (I18N configuration tool)
    regards,
    rudra..
    Assign points if helpful

  • Doubt about unicode conversion

    Dear Friends,
    I have a doubt about the unicode conversion. I have read (one server strategy) that I have to do export (R3load), delete the ECC 6.0 non-unicode, install an unicode database and then import with R3load. My doubt is about the deletion of ECC 6.0 non unicode. Why?  can I convert to unicode only with an export (R3load) and subsequent import (R3load) without any deletion?. Obviously I must to change the SAP kernel with a unicode one. Is it correct?
    Cheers

    you can not convert a SAP System to unicode by just exchanging the executables from non unicode to unicode ones.
    a non unicode SAP Oracle database is typically running with a database codepage WE8DEC or US7ASCII (well this one is out of support).
    so every string stored in the database is stored using this codepages or SAP-Internal codepages.
    When converting to unicode you have to convert also the contents of the database to unicode. As unicode implementation starts at a time where Oracle did not support mixed codepage databases (one tablespace codepage WE8DEC the other one UTF8) inplace conversions are not possible. To keep things simpler, we still do not support mixed codepage databases.
    Therefore you have to export the contents of your database and import it to a newly created database with a different codepage if you want to migrate to unicode.
    regards
    Peter

  • Urgent: Unicode conversion - table splitting

    Hi all,
    I am having a problem when trying to perform the export step of the unicode conversion on ERP2005, MSSQL server 2005. Due to previously very long runtime, I am trying to use the table splitting option. I have performed the "Table Splitting Preparation" step with what seems to be a success.
    The problem is when I run the actual database instance export.
    First of all:
    Which filepath should I provide SAPinst when it is asking for "Table input file"?
    Second:
    How can I actually determine the Package Unload Order? I tried selecting this option, but I was not given the opportunity to change this order in the subsequent screen. (The F1 help in SAPinst sais that I would be able to...)
    Have anyone of you experience with this?
    Best Regards,
    Thomas

    Hi Thomas,
    As I can imagine from the date of your last posting, you probably have your answers. But just so other people, who are searching on this topic, can find the answer here, I will fill in the blanks.
    First, when using table splitting, you must export using the migration monitor (MIGMON). That means, when you run SAPINST, on the ABAP System -> Database Export screen, select the Export Method: Export using Migration Monitor.
    At this point, as you said, you have already run the Table Splitting option from SAPINST, so the WHR files are in the export DATA directory. This whr.txt file is also there.
    The file input screen you are mentioning does not appear when you select the Export method mentioned above. But you can create such a file for MIGMON. You have to create this on your own and can only do it after the SAPINST has split the STR files.
    When finished with SAPINST, create the .txt file (I usually call it table_order.txt) and add the names of the STR files which you want to make sure are exported first. After MIGMON completes that list, all other STR files are exported in alphabetical order.
    Create your table_order.txt file inserting the filenames of the packages that were created, without the STR/WHR extensions (using some large tables which STR splitter broke out into their own STR files during my last export). You have to look in DB02 and sort descending based on used space to determine the order in which these tables should be exported and listed in the .txt file:
    <SPLIT Table>-1
    <SPLIT Table>-2
    <SPLIT Table>-n
    BSIS
    RFBLG
    CE1VVOC
    CE1WWOC
    DBTABLOG
    CE3VVOC
    COEP
    ARFCSDATA
    GLPCA
    KONV
    SWW_CONT
    SOC3
    CDCLS
    CE3WWOC
    BSE_CLR
    STXL
    EDIDS
    COSP
    BSAD
    EDI40
    ACCTIT
    BSIM
    VBFS
    BSAS
    ACCTCR
    CDHDR
    CE4VVOC_ACCT
    SGOHIST
    MSEG
    In the export_monitor_cmd.properties file, you specify this file name for the 'orderBy=' parameter. Create and keep the table_order.txt file in the same directory as the export_monitor.sh/.bat files.
    For importing, again you will need to use the Migration Monitor. SAPINST will automatically stop and prompt you to start the import using MIGMON. Here, you can specify the same table_order.txt file. You might want to amend it to control when the rest of the packages are imported, if you found one or more tables holding up the completion of the export.
    I hope this helps someone.
    Best Regards,
    Warren Chirhart

  • Export DB for Unicode conversion by SAPInst for distributed System

    Hi,
    In a distributed SAP system (CI and DB on separate host),
    (1) I run SAPInst to export DB for unicode conversion via system copy option in DB host. After the parameter input up to General Unload settings e.g. Unicode Target system ? Yes, Parallel import/export ? No
    The following warning/error occurred and drive K:\usr\sap\MD3 is located at CI host.
    How to solve it?
    WARNING 2007-09-04 22:53:39
    Execution of the command "K:\JDKRoot\bin\java.exe -classpath K:\usr\sap\MD3\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
    ebpshd01/sapmnt/MD3/SYS/global/security/lib/tools;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/antlr.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/exception.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/jddi.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/logging.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/offlineconfiguration.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/opensqlsta.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/SDMutil.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/SLUtil.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/base.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/util.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/sqlserver.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/spy.jar -export -type=keydb "-expfile=D:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/DISTRIBUTED/AS/EXPDB/usages_data.xml" -log=UTL_load_usages.log -sid=MD3 -dsn=jdbc/pool/MD3 -ssprops=K:/usr/sap/MD3/SYS/global/security/data/SecStore.properties -ssk=K:/usr/sap/MD3/SYS/global/security/data/SecStore.key" finished with return code 1. Output:
    java version "1.4.2_12"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
    Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_12-b03, mixed mode)
    java.lang.NoClassDefFoundError: com/sap/engine/offline/OfflineToolStart
    ERROR 2007-09-04 22:53:39
    CJS-30074  Execution of UTL tool 'K:\JDKRoot\bin\java.exe -classpath K:\usr\sap\MD3\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
    ebpshd01/sapmnt/MD3/SYS/global/security/lib/tools;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/antlr.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/exception.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/jddi.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/logging.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/offlineconfiguration.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/opensqlsta.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/SDMutil.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/SLUtil.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/base.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/util.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/sqlserver.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/spy.jar -export -type=keydb "-expfile=D:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/DISTRIBUTED/AS/EXPDB/usages_data.xml" -log=UTL_load_usages.log -sid=MD3 -dsn=jdbc/pool/MD3 -ssprops=K:/usr/sap/MD3/SYS/global/security/data/SecStore.properties -ssk=K:/usr/sap/MD3/SYS/global/security/data/SecStore.key' aborts with return code 1.<br>Check 'UTL_load_usages.log' and 'D:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/DISTRIBUTED/AS/EXPDB/UTL.java.log' for more information.
    ERROR 2007-09-04 22:53:39
    FCO-00011  The step getUsageTypes with step key |NW_Export|ind|ind|ind|ind|0|0|NW_Java_Export_Dialog|ind|ind|ind|ind|5|0|getUsageTypes was executed with status ERROR .
    (2) I run Table Splitting Preparation  in CI host by SAPInst before using DB export option, there are some files generated under the respective folder of sapinst_instdir. Will these files in CI be used when running SAPinst in DB host for DB export option? Is it required to move these files to DB host ? which is the target location if necessary ?
    Regards,
    Ricky Chan

    === Reformated it and added further information ===
    Hi,
    In a <b>distributed</b> (CI and DB on separate host) SAP system NW 7.0 ABAP+JAVA usage type MI ,
    (1) I run SAPInst to <b>export DB for unicode conversion via system copy option</b> in <u>DB host</u>. After the parameter input screen up to <u>"General Unload settings"</u> e.g. Unicode Target system ? Yes, Parallel import/export ? No
    The following warning/error occurred and drive K:\usr\sap\MD3 is <b>only located at CI host. No such folder in DB host as no SAP instance was installed in it</b>.
    ============ sapins_dev.log ============
    WARNING 2007-09-04 22:53:39 Execution of the command "K:\JDKRoot\bin\java.exe -classpath K:\usr\sap\MD3\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
    ebpshd01/sapmnt/MD3/SYS/global/security/lib/tools;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/antlr.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/exception.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/jddi.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/logging.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/offlineconfiguration.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/opensqlsta.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/SDMutil.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/SLUtil.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/base.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/util.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/sqlserver.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/spy.jar -export -type=keydb "-expfile=D:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/DISTRIBUTED/AS/EXPDB/usages_data.xml" -log=UTL_load_usages.log -sid=MD3 -dsn=jdbc/pool/MD3 -ssprops=K:/usr/sap/MD3/SYS/global/security/data/SecStore.properties -ssk=K:/usr/sap/MD3/SYS/global/security/data/SecStore.key" finished with return code 1. Output: java version "1.4.2_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03) Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_12-b03, mixed mode) java.lang.NoClassDefFoundError: com/sap/engine/offline/OfflineToolStart
    ERROR 2007-09-04 22:53:39 CJS-30074 Execution of UTL tool 'K:\JDKRoot\bin\java.exe -classpath K:\usr\sap\MD3\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
    ebpshd01/sapmnt/MD3/SYS/global/security/lib/tools;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/antlr.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/exception.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/jddi.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/logging.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/offlineconfiguration.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/opensqlsta.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/SDMutil.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/SLUtil.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/base.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/util.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/sqlserver.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/spy.jar -export -type=keydb "-expfile=D:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/DISTRIBUTED/AS/EXPDB/usages_data.xml" -log=UTL_load_usages.log -sid=MD3 -dsn=jdbc/pool/MD3 -ssprops=K:/usr/sap/MD3/SYS/global/security/data/SecStore.properties -ssk=K:/usr/sap/MD3/SYS/global/security/data/SecStore.key' aborts with return code 1.
    Check 'UTL_load_usages.log' and 'D:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/DISTRIBUTED/AS/EXPDB/UTL.java.log' for more information.
    ERROR 2007-09-04 22:53:39 FCO-00011 The step getUsageTypes with step key |NW_Export|ind|ind|ind|ind|0|0|NW_Java_Export_Dialog|ind|ind|ind|ind|5|0|getUsageTypes was executed with status ERROR .
    ============
    The content of file UTL.java.log:
    java version "1.4.2_12"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
    Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_12-b03, mixed mode)
    java.lang.NoClassDefFoundError: com/sap/engine/offline/OfflineToolStart
    =============
    File 'UTL_load_usages.log' does not exist in the sapinst_dir folder.
    (2) I run Table Splitting Preparation in CI host by SAPInst before using DB export option, there are some files generated under the respective folder of sapinst_instdir.
    Will these files in CI be used automatically when running SAPinst in DB host for DB export option?
    Is it required to move these files to DB host manually? Which is the target location if necessary ?
    (3) Any guide with detail on the preparation of tool or files in a standalone DB host prior to Export DB from it with SAPInst.
    Regards,
    Ricky Chan

  • Expertise Advices on ASSM + Unicode Conversion

    Hi,
    I need some Expertise advice on Converting oracle Table Space to ASSM and Unicode.
    Our company planning on upgrading ECC 5.0 to ECC 6.0 then we also want to do Unicode migration, but we need to know; what/when are the best practices to convert the oracle tablespace to ASSM?
    I believe part of Unicode migrations we have to convert the Oracle tablespace to ASSM.
    Option 1:
    Is it better to convert all the tablespaces to ASSM before we do a Unicode migration? And then do the Unicode migrations?
    Option 2:
    Or is it better to do everything together at the same time Unicode Migrations and Tablespace conversation?
    Is there are any benefits between those two options? Which one is really time saving? Option 1 or Option 2
    Quick question on the side, how long would it take to convert 450 GB total data to ASSM?
    Please advice on this!
    Thanks in Advances
    Kumar

    I would suggest the following: Forget about ASSM - it will be enabled by default after your conversion, that's all I can say about ASSM in this context.
    The Unicode migration itself is a really complex process, we had quite some issue to fight with. To see the whole story we were going through read that thread:
    combined upgrade and unicode conversion
    The topic is a bit different but I explain in-depth there, what problems we encountered, maybe this will helpful for you too.
    You're right, the guides are pretty complex and the procedure and preparation is too so I would NOT do that as newbie (no offense). We had a consultant from SAP on-site while we were doing the preparation for the migration because of those many languages we had. The migration itself was then done by me after those four tests migrations I mentioned earlier.
    If your system is a single codepage migration, it's not that difficult if you follow the guides provided (http://service.sap.com/unicode@sap) for your specific support package level. Just follow it step-by-step, read all the note (yes, I know, there are SO MANY).
    My "best practice recommendations" are:
    - use the VERY LATEST tools (kernel, R3load and dboraslib) for the export (VERY important!)
    - if possible, install the latest Basis support package (SP 12 in your case) <b>before</b> you start the preparation (that is running the task of SPUMG)
    - If you install the unicode instance, also use the latest tools there, latest kernel and latest R3load, you can patch the system while the database is created (there's enough time)
    - if you have external systems connected, make sure, they are aware of the fact, that they are "talking" to Unicode systems after the migration (Fax-Servers, EDI and also all SAP systems such as BW, CRM, SCM or also SAP-KPRO-Servers or what else you have there)
    - test, test, test, don't do the migration just theoretically
    I can't provide a guide, they are highly individual depending on what modules are implemented, what external interfaces and connections to systems you have etc. etc. I could provide you with a "guide" but I'm VERY sure, there's something missing/too much and I won't be responsible for any errors/problems you will get. We did a full day of just evaluating the system, interfaces etc.
    The only advise is - do a test migration, connect the system to everything you also have on production and test.
    Markus

  • Error while database export in package SAPDODS_33 (Unicode conversion)

    Hello,
    I am performing Unicode conversion on an upgraded BI 7.0 system. This is running on AIX/DB2.
    When I take database export for conversion, one package fails (SAPDODS_33) with error "The file system is full". In fact, df -k doesn't show that any file system is full.
    I am taking the export to the following location: /db2/BWS/sapdata/EXPORT_DIR
    There are 3 system-managed temporary tablespaces: PSAPTEMP, PSATEMP16 & SYSTOOLSTMPSPACE which were residing in /db2/BWS/saptemp1/NODE0000. This was getting full during the export. Now these temp.tablespaces have been relocated to a new file system of size 15GB.
    But still the package SAPDODS_33 doesn't get exported. Could you please let me know how to solve this issue?
    Thanks a lot!
    Sundar.
    =====================================================================================
    SAPDODS_33.log
    (DB) INFO: connected to DB
    (rscpsumg) Please look also into "SAPDODS_33012.xml".
    (rscpMC) Warn: env I18N_NAMETAB_TIMESTAMPS = IGNORE
    (rscpMC) Warn: UMGCONTAINER has 1 problems.
    (rscpMC) Warn: Global fallback code page = 1160
    (rscpMC) Warn: Common character set is  not  7-bit-ASCII
    (rscpMC) Warn: Collision resolution method is 'fine'
    (rscpMC) Warn: R3trans code pages = Normal
    (rscpMC) Warn: EXPORT TO ... code pages = Normal
    (rscpMC) Warn: Source is 'MDMP'
    (rscpMC) Warn: I18N_NAMETAB_NORM_ALLOW = 0
    (rscpMC) Warn: I18N_NAMETAB_NORM_LOG   = 0
    (rscpMC) Warn: I18N_NAMETAB_ALT_ALLOW  = 0
    (rscpMC) Warn: I18N_NAMETAB_ALT_LOG    = 0
    (rscpMC) Warn: I18N_NAMETAB_OLD_ALLOW  = 0
    (rscpMC) Warn: I18N_NAMETAB_OLD_LOG    = 0
    (GSI) INFO: dbname   = "BWS
    (GSI) INFO: vname    = "DB6                             "
    (GSI) INFO: hostname = "UNKNOWN
    (GSI) INFO: sysname  = "AIX"
    (GSI) INFO: nodename = "itmlartdev01x"
    (GSI) INFO: release  = "3"
    (GSI) INFO: version  = "5"
    (GSI) INFO: machine  = "002417CA4C00"
    (GSI) INFO: instno   = "0020169337"
    (EXP) ERROR: DbSlExeRead failed
      rc = 99, table "/BIC/B0000786000"
      (SQL error -968)
      error message returned by DbSl:
    SQL0968C  The file system is full.  SQLSTATE=57011
    (DB) INFO: disconnected from DB
    /usr/sap/BWS/SYS/exe/run/R3load: job finished with 1 error(s)
    /usr/sap/BWS/SYS/exe/run/R3load: END OF LOG: 20071211053119
    p/sapinst/sapinst_instdir/NW04S/LM/COPY/DB6/EXP/CENTRAL/AS-ABAP/EXP #

    Hi Sundar,
    if the problem is due to a high temp space usage. The root cause is typically the
    sort during export. If the table is large, the sort spills to temp.
    You can avoid the sort by doing an unsorted export or tweak the DB2 optimizer to use the primary key to do the sort.
    Before DB2 9, you can reduce the OVERHEAD tablespace parameter to zero. Return this value to its previous value after the successful export. This is a indirect hint to the optimizer that random IOs are cheap. This might not help.
    With DB2 9, this should not happen, because the  DB2_OPT_MAX_TEMP_SIZE=10240 registry variable is set under DB2_WORKLOAD=SAP which limits the temp space usage to 10GB if possible. You can reduce this parameter further if necessary. Another problem could be that the optimizer has chosen the wrong temp space. The optimizer choses the temp space with the largest amount of pages (not size).
    Regards, Jens

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

  • How to go for Unicode conversion?

    Hi All,
    Presently i'm upgrading my SAP 4.7 system (6.2 WAS) in to ERP 2004 (6.40 WAS), which is an non-unicode upgrade.
    Now should i first complete Unicode conversion or apply the latest SP stack.
    Also please tell me how this Support pack will affect me in Unicode conversion?
    Order of this steps will be really helpful for smooth flow of work
    Thanks in Advance

    If you have already completed your upgrade, the best practice would be to install the SP stack first in order to have the latest updates available for the unicode migration tools.  Then proceed with the unicode migration.  There are slight differences in the process between support packages where you may have to create a migration program manually in an older support package and the very same migration program is included in the later support package.  SAP publishes separate unicode migration guides, based on the support package level, due to these updates.

  • 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

  • 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

  • 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

Maybe you are looking for

  • Crystal Report Group section in new page

    Hi all, I have a program written in VB.Net 2005 which display a report. In this report, I have a group by Item type ascending. When I run the program and load the report, it display the data correctly. When I move my mouse cursor on Group Section Hea

  • How can I get Mavericks off my comp and go back to the old OS?

    Anything related to the internet is slow or doesn't work.  My Outlook crashes constantly and I hate using Mail.  I knew better than to downgrade to the new OS but did it anyway.  This is so irritating. <Re-Titled By Host>

  • Duplicates and Deleted Songs

    Besides the duplicates problem, has anyone found music - installed from music CD - missing from their music library? I've found many albums missing from the library since the recently 9.1.1.xx upgrades. The folder still contains the album art, small

  • Web dispatcher redirects to Message Server

    Hello SDN members. Iu2019m using web dispatcher in front of a ABAP+JAVA installation. When Iu2019m tracing (HTTP) requests from the portal that are aimed to the ABAP WAS (usually requests to the webgui service) I can see the following: 1. the request

  • Export to Excel Hangs

    It seems that under certain circumstances (presumably the number/size of the records set), the Export (of query results) to Excel hangs. In my case, the Export to xls slows down at about 9,000 records. If I open TaskManager, I see both sqldeveloper.e