Combined Upgrade and Unicode conversion of Sap 4.6C to ECC6.0

Hello all,
my project team intends to carry out a combined upgrade and unicode conversion of an SAP ERP 4.6C system with MDMP to ECC6.0 (no enhancement package). The system is running on Oracle 10.2.
In preparation for this upgrade, I have gone through the SAP notes 928729, 54801.
We need to get a rough estimate of the entire downtime so as to alert our end users. From the CU&UC documentation in 928729, I read up note 857081. However the program in this note cannot be used to estimate the downtime as my system is < SAP netweaver 6.20.
Is there any other SAP note or tool or program that I can use to estimate the downtime for the entire CU&UC? Thanks a lot!

Hi,
Combined upgrade depend upon number of factors like database size, resources on the server and optimization. In order to get idea of how much downtime, it will take, I would suggest you to do combined upgrade and unicode conversion on sandbox system which should be the replica of your production system. And try to optimize it. From there you can get approx. downtime required.
Also, please read combined upgrade and unicode conversion guides on  http://service.sap.com/unicode@sap
Thanks
Sunny

Similar Messages

  • Combined upgrade and Unicode conversion for ECC5 MDMP system

    Hello,
    We are planning to do Upgrade and Unicode conversion of ECC5 MDMP system to ECC6 EHP4 Unicode. We are adopting Combined upgrade and Unicode conversion strategy to minimise the downtime.
       In source version ECC5 we are in support pack level 6. Should we need to update the support pack to any target version to start with CU&UC or we can start with ECC5 with SP 6 itself.
    Since we cant afford more downtime for support pack update also, is it ok to start with upgrade and unicode conversion with current version.
    please advice.
    Regards
    Vinay

    Hello Vinay,
    please note that as a prerequisite the Basis SP should be accurate for an MDMP conversion.
    There is no MUST to have the latest Basis SP, but without you could have severe issues in SPUMG.
    On the application side, there are in most cases no hard requirements on the SP level.
    Best regards,
    Nils Buerckel
    SAP AG

  • 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

  • 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

  • Combined Upgrade and Unicode Conversion

    Hello, I'm planning to implement an Upgrade from I386/ORA8/46C TO I386/ORA10/ECC6 using CUUC method.
    According to the guide, I better build up a sperate Sandbox Server for ABAP Program Modification and Testing. Since the customed ABAP Reports used to be related with the customed table, I suppose the best way for the Sandbox Server is to upgrade it to higher version.
    I'm running the Prepare and stuck on the Transport Request import. The sandbox server is not ready yet in a few days.
    My question is, can I just ignore the ABAP Program Import at the current phase and import it at the end of 'Prepare' and before the 'Upgrade'.
    If yes, how?  mannually import the TR for Abap Program changes to 46c after the 'Prepare' finished?  Any steps that I should pay attention to spcially?
    Any experience is welcome.
          Thanks in advance and BR,   Sam

    This would depend on whether your quality and production are consistent in terms of modifications along with your development server. If all changes to quality and production has happened through changes in development and then transporting those changes to qas and prd, then i would suggest when you run your development system upgrade (sandbox in this case) ideally you should do the changes and modifications and record them in transport request using the option "select for transport". Later when you upgrade another sandbox (copy of qas or prd) you should select the transport request to be imported during the prepare.
    But as you are now running PREPARE for copy of development, the prompt for importing transport request into this system is irrelevant and you should say " no" and complete the upgrade, and then the process outlined above..
    Hope this helps.
    Cheers,
    Chetan

  • UC&UC Combined Upgrade and Unicode Conversion from 4.6c to Netweaver 7.01

    Hi Gurus,
    I need to do (UC&UC) from 4.6c to Netweaver 7.01, after reading SAP guide still unsure about exact STEPS how to execute this,
    is there someone who has done, and pl. can explain STEPS how exactly to do that.
    Thanks for your help in advance
    sahmad

    Thanks, documentation found

  • 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

  • Twin upgrade and Unicode conversion: UMG_TWIN_PROCESS_LOGS Could not adjust

    Hello,
    We have done Upgrade of 4.5B MDMP system to ECC6 EHP4 MDMP and currently Unicode conversion in progress.
    We adopted TU&UC. Now we are importing twin spumg results of last run to our procution copy system.
    During running UMG_TWIN_PROCESS_LOGs. we are facing some errors
    INDX lines to be corrected:               4.417
    INDX lines corrected      :               4.144
    IN that Could not adjust:        SMODISRC, we are referring Note 991654 - UMG_TWIN_PROCESS_LOGS shows errors on SMODISRC.
    please suggest for other error tables  below
    Could not adjust:        VARI 1160
    Could not adjust:        MONI
    Could not adjust:        BDLDATCOL 1160 DLR000000492TSK0020305440PV1     0000000000DIFF    BDL   000614a01822pr                        000000Field List          S1100
    Please suggest what action can be taken
    Regards
    Vinay

    Hi Vinay,
    did you already check attachment of  SAP note 765475 - "Unicode conversion Troubleshooting guide" ?
    Excerpt:
    ...check if the entries in
    <table name> still exist. In some cases those entries only exist in the
    Twin System but no longer in the Production System. In such cases the
    message is not an error message but only information.
    Best regards,
    Nils Buerckel
    SAP AG

  • Preparing for upgrade and Unicode conversion while on 4.6c

    We're currently on 4.6c and preparing to upgrade to ERP 2005 and do a Unicode conversion.  I'm trying to compile a list of coding techniques that can used in 4.6c that will minimize changes needed for Unicode.  Does anyone have such a list?
    Some things I've discovered reading about Unicode include:
    1) Use GUI_UPLOAD and GUI_DOWNLOAD rather than WS_UPLOAD and WS_DOWNLOAD.
    2) Structures or table headers that contain non-character data need to be identical when moving, comparing, selecting into, updating from, etc.  This includes not moving structures/tables with non-character data to a character field or vice-versa.
    3) Offsets can't cross non-character data.
    4) Assign statement with offset must specify a length.
    5) Open dataset must specify "FOR INPUT", "FOR OUTPUT", "FOR APPENDING", or "FOR  UPDATE".  It no longer defaults to FOR INPUT when omitted.
    6) Many implicit conversions from char to numeric are no longer allowed.  Use explicit conversion instead; such as the move statement.
    I know there are others.  Any help would be appreciated.
    Regards,
    Mark Perrey

    Hai Mark
    Check the following F.M Replacents
    Upgrade Error Details     Suggestions
    Function Module "DOCUMENT_REGISTRY_PROGRAM"not found in the target system     Suggest to replace this FM with the function module CV120_GET_APPL_FROM_REGISTRY.
    Function Module "RP_HIRE+FIRE"not found in the target system     Suggest to replace this FM with the function module RP_HIRE_FIRE .
    Function Module "ME_READ_HEADER_SINGLE" not found in the target system     Suggest to replace this FM with the function module ME_EKKO_SINGLE_READ.
    Function Module "ME_READ_ITEM_SINGLE" not found in the target system     Suggest to replace this FM with the function module ME_EKPO_SINGLE_READ.
    Function Module "RZL_ALERT_CONTROL" not found in the target system     Function Module "RZL_ALERT_CONTROL" is not available in the Enterprise Version. Suggest to use the function module "TH_SEND_ADM_MESS" to acheive the same functionality of "RZL_ALERT_CONTROL".
    Function Module "MM_SELECT_ADDRESS" not found in the target system     Suggest to replace this FM with the function module MM_SELECT_PARTNER.
    Function Module "MM_READ_ADDRESS" not found in the target system     Suggest to replace this FM with the function module MM_PARTNERS_FOR_MESSAGING
    Function Module "ME_VALUES_T161" not found in the target system     Suggest to replace this FM with the function module HELP_VALUES_BSART.
    Function Module "ME_VALUES_T024W" not found in the target system     . Suggest to replace this FM with the function module HELP_VALUES_WERKS.
    Function Module "SD_PACKING_REFRESH" not found in the target system     Suggest to replace this FM with the function module HU_PACKING_REFRESH.
    Function Module "SD_PACKING_RENAME" not found in the target system      Suggest to replace this FM with the function module V51P_PACKING_RENAME.
    Function Module "RV_EXPORT_CONTROL_UPDATE" not found in the target system     Suggest to replace this FM with the function module RV_EXPORT_CONTROL_UPD_PREPARE.
    Function Module "RV_INVOICE_COPY" not found in the target system     Suggest to replace this FM with the function module RV_SALES_DOCUMENT_COPY.
    Function Module "SD_SCHEDULE_AGREEMENT_PACKING" not found in the target system     Suggest to replace this FM with the function module HU_PACKING_SALES_PROPOSAL.
    Function Module "SERIAL_RENUM_WV" not found in the target system     Suggest to replace this FM with the function module IWOL_WV_SWITCH_NUMBER.
    Function Module "CUD0_DISPLAY_CONFIGURATION" not found in the target system     Suggest to replace this FM with the function module VC_I_DISPLAY_CONFIGURATION.
    Function Module "SD_PACKING_CREATE" not found in the target system     Suggest to replace this FM with the function module V51F_PACKING_CREATE.
    Function Module "FI_ARCHIVE_CHECK_DOC" not found in the target system     Function Module FI_ARCHIVE_CHECK_DOC is not available in the Enterprise Version. Suggest to replace this FM with the function module FI_DOCUMENT_ARCH_CHECK_DOCS.
    Function Module "OPEN_FI_CHECK" not found in the target system     Function Module OPEN_FI_CHECK is not available in the Enterprise Version. Suggest to replace this FM with the function module OPEN_FI_PERFORM_******_E.
    Function Module "SD_PACKING_UPDATE"not found in the target system     Function Module SD_PACKING_UPDATE is not available in the Enterprise Version. Suggest to replace this FM with the function module HU_PACKING_UPDATE.
    Function Module "F4_MACO" is being used in the program     Function Module "F4_MACO" is not available in the Enterprise Version. Since the Matchcode objects are not used in the Enterprise Version, Suggest to replace this FM with Search help's Value Request function module F4_SEARCH_HELP.
    Function Module "SWZ_AI_RELEASE_S" is used in the program     Suggest to use the function module "SWZ_AI_RELEASE" instead of "SWZ_AI_RELEASE_S".
    Function Module "SWW_WI_ORGTASK_READ" is  used in the program      Suggest to replace this FM with the function module RH_WI_ORGTASK_READ.
    Function Module "RH_READ_EXCEL_PATH" is being used in the program     Suggest to replace this FM with "RH_CHECK_EXCEL_SUPPORT".
    Function Module "RZL_ALERT_CONTROL" is used in the program     Function Module "RZL_ALERT_CONTROL" is not available in the Enterprise Version. Suggest to use the function module "TH_SEND_ADM_MESS" to acheive the same functionality of "RZL_ALERT_CONTROL".
    Function Module "CONVERT_TO_OTHER_CURRENCY" is used in the program     Suggest to ruse the function module "CONVERT_TO_LOCAL_CURRENCY" for currency conversion.
    Function Module "LOAN_TABLECONTROL_SCROLLING" is not available in the Enterprise Version.      Suggest to replace this FM with the function module SCROLLING_IN_TABLE.
    CALL FUNCTION 'DOWNLOAD' used in program is obsolete in target system.     "DOWNLOAD function module is obsolete and result in errors on Unicode systems or on systems that may potentially be Unicode enabled.
    Suggest to use the unicode enabled methods
    FILE_SAVE_DIALOG and GUI_DOWNLOAD
    from class CL_GUI_FRONTEND_SERVICES.
    Note:
    However, to support existing applications, a compatibility mode was added to the function module(enhanced with Support Package) that will forward calls to DOWNLOAD to the new GUI_DOWNLOAD functions."
    CALL FUNCTION 'HELP_VALUES_GET_NO_DD_NAME' used in program is obsolete in target system.     "HELP_VALUES_GET_NO_DD_NAME function module is obsolete and result in errors on Unicode systems or on systems that may potentially be Unicode enabled.
    Suggest to use the function module F4IF_INT_TABLE_VALUE_REQUEST in the target system."
    CALL FUNCTION 'POPUP_TO_CONFIRM_LOSS_OF_DATA' used in program is obsolete in target system.     "POPUP_TO_CONFIRM_LOSS_OF_DATA is obsolete in the target system.
    Suggest to use function module POPUP_TO_CONFIRM."
    CALL FUNCTION 'POPUP_TO_CONFIRM_STEP' used in program is obsolete in target system.     "POPUP_TO_CONFIRM_STEP is obsolete in the target system.
    Suggest to use function module POPUP_TO_CONFIRM."
    CALL FUNCTION 'WS_DOWNLOAD' used in program is obsolete in target system.     "WS_DOWNLOAD function module is obsolete and result in errors on Unicode systems or on systems that may potentially be Unicode enabled.
    Suggest to use the unicode enabled GUI_DOWNLOAD function module.
    Note:
    However, to support existing applications, a compatibility mode was added to the function module(enhanced with Support Package) that will forward calls to WS_DOWNLOAD to the new GUI_DOWNLOAD function."
    CALL FUNCTION 'WS_FILENAME_GET' used in program is obsolete in target system.     "WS_FILENAME_GET function module is obsolete, and results in errors on Unicode systems.
    Suggest to use FILE_OPEN_DIALOG und FILE_SAVE_DIALOG Unicode-enabled methods of the cl_gui_frontend_services class.
    Note:
    New applications should restart on these methods instead of the function module. The function module is extended by a Support Package so that it diverts calls to the methods without the application having to be changed."
    CALL FUNCTION 'WS_UPLOAD' used in program is obsolete in target system.     "WS_UPLOAD function module is obsolete and result in errors on Unicode systems or on systems that may potentially be Unicode enabled.
    Suggest to use the unicode enabled GUI_UPLOAD function module.
    Note:
    However, to support existing applications, a compatibility mode was added to the function module(enhanced with Support Package) that will forward calls to WS_UPLOAD to the new GUI_UPLOAD function."
    Function parameters EBENE, GRUPP, DATE_LOW, DATE_HIGH, BANKK. BUKRS, S_BUKRS, S_DISPW in function module CASH_FORECAST_TR_SELECT_ITEM is missing in the target system.     "Function Module CASH_FORECAST_TR_SELECT_ITEM is no longer used, instead it has been split based on the functionalities.
    Suggest to use function module
    1) CASH_FORECAST_PR_SELECT_ITEM for Payment Arrangements.
    2) For TR, WP, DA use function module CASH_FORECAST_TR_ITEM_2.
    The IMPORT and TABLES parameters of the above 2 function modules are almost same as CASH_FORECAST_TR_SELECT_ITEM.
    The IMPORT parameter BUKRS is not available in the above 2 function modules. Hence suggest to change the coding accordingly."
    Import parameter BUKRS in function CASH_FORECAST_LO_SELECT_ITEM is missing in the target system.     "Import parameter BUKRS in function CASH_FORECAST_LO_SELECT_ITEM is not available in the target system.
    Also the coding in Function Module based on the parameter BUKRS has been removed, instead the TABLES parameter S_BUKRS and S_GSBER has been used.
    Suggest to check the coding in the program accordingly.
    Import parameter BUKRS in function CASH_FORECAST_RE_SELECT_ITEM is missing in the target system.     "Import parameter BUKRS in function CASH_FORECAST_RE_SELECT_ITEM is not available in the target system.
    Also the coding in Function Module based on the parameter BUKRS has been removed, instead the TABLES parameter S_BUKRS and S_GSBER(new parameter) has been used.
    Suggest to check the coding in the program accordingly.
    Function Module HELP_VALUES_GET_WITH_MACO is obsolete in target system     Suggest to use F4IF_FIELD_VALUE_REQUEST
    Function Module G_OBJECT_GET is obsolete in target system.     Suggest to Use G_INTERVAL_GET_NEXT
    Function Module READ_COSTCENTER is obsolete in target system     Suggest to Use K_COSTCENTER_SELECT_SINGLE
    Function Module K_BUSINESS_PROCESS_READ_MULTI is obsolete or not available in target system     Suggest to Use K_PROCESSES_SELECT_TAB
    G_SET_AVAILABLE     Suggest to Use G_SET_GET_INFO
    Function Module G_SET_DOUBLE_CHECK is obsolete or not available in target system     "DO NOT CALL THIS FUNCTION MODULE
    FROM 4.0A VERSION ,THIS PROBLEM WILL NOT OCCUR"
    Function Module HELP_VALUES_GET is obsolete or not available in target system     Suggest to Use F4IF_FIELD_VALUE_REQUEST
    G_SELECT_SET     Suggest to Use G_SET_SELECT
    Function Module G_SET_AVAILABLE is obsolete or not available in target system     Suggest to Use G_SET_GET_INFO
    Function Module NAMETAB_GET is obsolete or not available in target system     Suggest to Use DDIF_FIELDINFO_GET
    Function Module DD_GET_DD03P is obsolete or not available in target system     Suggest to Use DDIF_FIELDINFO_GET / DDIF_TABL_GET
    CALL FUNCTION 'POPUP_TO_CONFIRM_WITH_MESSAGE' used in program is obsolete in target system.     Suggest to use function module POPUP_TO_CONFIRM.
    CALL FUNCTION 'POPUP_TO_DECIDE' used in program is obsolete in target system.     Suggest to use function module POPUP_TO_CONFIRM.
    Function Module HELP_VALUES_GET_WITH_TABLE is obsolete or not available in target system     Suggest to Use F4TOOL_F4FUNCTION_BRIDGE
    Function Module CLPB_EXPORT is obsolete or not available in target system     "Suggest to Use Suggest to use the unicode enabled methods
    CLIPBOARD_EXPORT from class CL_GUI_FRONTEND_SERVICES."
    Function Module SAP_TO_ISO_MEASURE_UNIT_CODE is obsolete or not available in target system     Suggest to Use UNIT_OF_MEASURE_SAP_TO_ISO
    Regards
    Sreeni

  • Unicode Conversion for SAP BI

    Hi
    We are upgrading out SAP BW 3.1 system to SAP NW 7.0. We are also planning to do a Unicode conversion of the upgraded system.
    Please let me know the following:
    1. What extra tests we need to do for Unicode Conversion
    2. If you have done a Unicode conversion, please share the errors that you have got after the conversion, and the possible solutions.
    Best Regards,
    Rajib

    hi,
    Please refer
    SAP Note Number: 928729 : Combined Upgrade & Unicode Conversion (CU&UC)
    https://wiki.sdn.sap.com/wiki/display/unicode/ChallengesinBIUnicodeconversion
    Below is the link for R/3... but still will give you some insight.
    /people/tikkana.akurati/blog/2009/02/27/combined-upgrade-and-unicode-conversion-cuuc-cutover-project-plan-execution
    This will also help you understand more about unicode...
    /docs/DOC-8284#section5 [original link is broken]
    Hope this helps
    Regards
    Raj

  • BI7 Upgrade - Data Classes and Unicode Conversion

    It is mentioned that we need to Convert Data Classes of InfoCube, but I still dont quite understand. Do you know what exactly is this Data Classes mean?
    NW2004s upgrade
    Also, why do we need to perform Unicode Conversion during the 3.x to BI7 upgrade?
    Please advice.

    It is mentioned that we need to Convert Data Classes of InfoCube, but I still dont quite understand. Do you know what exactly is this Data Classes mean?
    NW2004s upgrade
    Also, why do we need to perform Unicode Conversion during the 3.x to BI7 upgrade?
    Please advice.

  • Unicode conversion in sap query

    i need to whether unicode conversion is possible in sap query

    Hi again
    The point 2 is still not clear for me..
    1. Should I put in the source code (256 lines) of the function module here, or should I just put in a reference to the Function module like:
    FM convert_to_local_currency;
    2. Where should I put in the import variables you refer to?
    3. When I push "single test" of the Function module I get these import parameters:
    CLIENT                          210     
    DATE                                    
    FOREIGN_AMOUNT                          
    FOREIGN_CURRENCY                        
    LOCAL_CURRENCY                          
    RATE                            0       
    TYPE_OF_RATE                    M       
    READ_TCURR                      X       
    Is this the import parameters you are reffering to?
    Best regards
    Ellen

  • FJS-00003  TypeError: fsTableSplit for system copy and unicode conversion

    Dear Sir:
    Current I want to do the system copy for unicode conversion, but i go the following message on phase table splitting preparation. did you got this message before? Thanks!
    Br,
    GX
    ERROR      2009-02-05 18:03:12.214 [iaxxejsbas.cpp:204]
    FJS-00003  TypeError: fsTableSplit has no properties (in script TableSplitter|in
    d|ind|ind|ind, line 69516: ???)
    TRACE      2009-02-05 18:03:12.294 [syuxctask.cpp:1382]
               CSyTaskImpl::start(bool)
    A child process has been started. Pid = 5708
    ERROR      2009-02-05 18:03:12.344 [sixxcstepexecute.cpp:951]
    FCO-00011  The step ReadTableSplitList with step key |TableSplitter|ind|ind|ind|
    ind|0|0|ReadTableSplitList was executed with status ERROR .

    Hi,
    Table split option is used for very large databases, you can use normal export/import method.
    What is your database size ?
    I had done UC for databases upto 1.5 TB, never used table split technique.
    Keep it simple while doing complex tasks.
    Regards
    KT

  • 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

  • Error in Import during unicode conversion

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

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

Maybe you are looking for