Migration unicode Linux to unicode AIX

Not sure if this is the right forum.
I am trying to run heterogeneous system copy of Unicode SolMan 7 Enh 1 system from Source Linux target AIX.
Having problems with R3load export.
/usr/sap/SID/SYS/exe/run/R3load -e D010INC.cmd -datacodepage 4102 -l D010INC.log
-stop_on_error
(DB) INFO: connected to DB
(DB) INFO: Export without hintfile
(CNV) ERROR: There shall be only one Unicode in a database
I THINK I have to do a Unicode migration to get from Linux Unicode little endian
to AIX Unicode big endianu2026
Is there such a thing as Unicode to Unicode migration documentation anywhere?
Does current Unicode Migration document have Unicode source section?
This system already had Unicode migration at SM 7.0 level...
Does this mean UMG tables need reset?
Ken

TRACE 2010-08-10 16:25:53.385 [syuxctask.cpp:1382]
 CSyTaskImpl::start(bool)
A child process has been started. Pid = 20731
ERROR 2010-08-10 16:25:53.421 [sixxcstepexecute.cpp:950]
FCO-00011 The step runMigrationMonitor with step key |NW_Export|ind|ind|ind|ind|0|0|NW_ABAP_Export_Dialog|ind|ind|ind|ind|4|0|NW_ABAP_Export|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
TRACE 2010-08-10 16:25:53.440 [iaxxgenimp.cpp:752]
 CGuiEngineImp::showMessageBox
<html> <head> </head> <body> An error occurred while processing option SAP Solution Manager 7.0 EhP1 > Software Life-Cycle Options > System Copy > IBM DB2 for Linux, UNIX, and Windows > Source System Export > Central System > Based on AS ABAP and AS Java > Database and Central Instance Export. You can now: <ul> <li> Choose Retry to repeat the current step. </li> <li> Choose View Log to get more information about the error. </li> <li> Stop the option and continue with it later. </li> </ul> Log files are written to /nfs/@soulman-t/cd/tmpdir/sapinst_instdir/SOLMAN/LM/COPY/DB6/EXP/CENTRAL/AS/EXP. </body></html>
export_monitor.java.log -
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142-20080923 (JIT enabled)
J9VM - 20080922_23329_LHdSMr
JIT - 20080815_1845_r8
GC - 200809_04)
Export Monitor jobs: running 1, waiting 55, completed 0, failed 0, total 56.
Export Monitor jobs: running 2, waiting 54, completed 0, failed 0, total 56.
Export Monitor jobs: running 3, waiting 53, completed 0, failed 0, total 56.
Export Monitor jobs: running 3, waiting 52, completed 1, failed 0, total 56.
Export Monitor jobs: running 3, waiting 51, completed 2, failed 0, total 56.
Unloading of 'BALDAT' export package: ERROR
Export Monitor jobs: running 1, waiting 51, completed 2, failed 2, total 56.
Unloading of 'BDLDATCOL' export package: ERROR
Export Monitor jobs: running 0, waiting 51, completed 2, failed 3, total 56.
Unloading of 'D010INC' export package: ERROR
Export Monitor jobs: running 0, waiting 51, completed 2, failed 3, total 56.
Export Monitor jobs: running 1, waiting 50, completed 2, failed 3, total 56.
Export Monitor jobs: running 2, waiting 49, completed 2, failed 3, total 56.
Export Monitor jobs: running 3, waiting 48, completed 2, failed 3, total 56.
Unloading of 'DOKCLU' export package: ERROR
Export Monitor jobs: running 2, waiting 48, completed 2, failed 4, total 56.
Unloading of 'DSVASREPODOCS' export package: ERROR
Export Monitor jobs: running 1, waiting 48, completed 2, failed 5, total 56.
Unloading of 'D010TAB' export package: ERROR
Export Monitor jobs: running 0, waiting 48, completed 2, failed 6, total 56.
Export Monitor jobs: running 1, waiting 47, completed 2, failed 6, total 56.
Export Monitor jobs: running 2, waiting 46, completed 2, failed 6, total 56.
Export Monitor jobs: running 3, waiting 45, completed 2, failed 6, total 56.
Unloading of 'DSVASRESULTSGEN' export package: ERROR
Export Monitor jobs: running 2, waiting 45, completed 2, failed 7, total 56.
Unloading of 'DSVASRESULTSATTR' export package: ERROR
Export Monitor jobs: running 1, waiting 45, completed 2, failed 8, total 56.
Unloading of 'DSVASTEXTCLUSTER' export package: ERROR
Export Monitor jobs: running 0, waiting 45, completed 2, failed 9, total 56.
Export Monitor jobs: running 1, waiting 44, completed 2, failed 9, total 56.
Export Monitor jobs: running 2, waiting 43, completed 2, failed 9, total 56.
Export Monitor jobs: running 3, waiting 42, completed 2, failed 9, total 56.
Unloading of 'DYNPSOURCE' export package: ERROR
Export Monitor jobs: running 1, waiting 42, completed 2, failed 11, total 56.
Unloading of 'E071K' export package: ERROR
Export Monitor jobs: running 1, waiting 42, completed 2, failed 11, total 56.
Unloading of 'OCSCMPLOBJ' export package: ERROR
Export Monitor jobs: running 0, waiting 42, completed 2, failed 12, total 56.
Export Monitor jobs: running 1, waiting 41, completed 2, failed 12, total 56.
Export Monitor jobs: running 2, waiting 40, completed 2, failed 12, total 56.
Export Monitor jobs: running 3, waiting 39, completed 2, failed 12, total 56.
Unloading of 'RSDDSTATEVDATA' export package: ERROR
Export Monitor jobs: running 2, waiting 39, completed 2, failed 13, total 56.
Unloading of 'REPOTEXT' export package: ERROR
Export Monitor jobs: running 1, waiting 39, completed 2, failed 14, total 56.
Unloading of 'REPOSRC' export package: ERROR
Export Monitor jobs: running 0, waiting 39, completed 2, failed 15, total 56.
Export Monitor jobs: running 1, waiting 38, completed 2, failed 15, total 56.
Export Monitor jobs: running 2, waiting 37, completed 2, failed 15, total 56.
Export Monitor jobs: running 3, waiting 36, completed 2, failed 15, total 56.
Unloading of 'SACONT01' export package: ERROR
Unloading of 'SAPAPPL0_1' export package: ERROR
Export Monitor jobs: running 1, waiting 36, completed 2, failed 17, total 56.
Export Monitor jobs: running 1, waiting 36, completed 2, failed 17, total 56.
Unloading of 'RSDDSTATLOGGING' export package: ERROR
Export Monitor jobs: running 0, waiting 36, completed 2, failed 18, total 56.
Export Monitor jobs: running 1, waiting 35, completed 2, failed 18, total 56.
Export Monitor jobs: running 2, waiting 34, completed 2, failed 18, total 56.
Export Monitor jobs: running 3, waiting 33, completed 2, failed 18, total 56.
Unloading of 'SAPAPPL0_4' export package: ERROR
Export Monitor jobs: running 2, waiting 33, completed 2, failed 19, total 56.
Unloading of 'SAPAPPL0_2' export package: ERROR
Export Monitor jobs: running 1, waiting 33, completed 2, failed 20, total 56.
Unloading of 'SAPAPPL0_3' export package: ERROR
Export Monitor jobs: running 0, waiting 33, completed 2, failed 21, total 56.
Export Monitor jobs: running 1, waiting 32, completed 2, failed 21, total 56.
Export Monitor jobs: running 2, waiting 31, completed 2, failed 21, total 56.
Export Monitor jobs: running 3, waiting 30, completed 2, failed 21, total 56.
Unloading of 'SAPAPPL0_5' export package: ERROR
Export Monitor jobs: running 2, waiting 30, completed 2, failed 22, total 56.
Unloading of 'SAPAPPL1_1' export package: ERROR
Export Monitor jobs: running 1, waiting 30, completed 2, failed 23, total 56.
Unloading of 'SAPAPPL1_2' export package: ERROR
Export Monitor jobs: running 0, waiting 30, completed 2, failed 24, total 56.
Export Monitor jobs: running 1, waiting 29, completed 2, failed 24, total 56.
Export Monitor jobs: running 2, waiting 28, completed 2, failed 24, total 56.
Export Monitor jobs: running 3, waiting 27, completed 2, failed 24, total 56.
Unloading of 'SAPAPPL1_3' export package: ERROR
Export Monitor jobs: running 2, waiting 27, completed 2, failed 25, total 56.
Unloading of 'SAPAPPL2_1' export package: ERROR
Export Monitor jobs: running 1, waiting 27, completed 2, failed 26, total 56.
Unloading of 'SAPAPPL2_2' export package: ERROR
Export Monitor jobs: running 0, waiting 27, completed 2, failed 27, total 56.
Export Monitor jobs: running 1, waiting 26, completed 2, failed 27, total 56.
Export Monitor jobs: running 2, waiting 25, completed 2, failed 27, total 56.
Export Monitor jobs: running 3, waiting 24, completed 2, failed 27, total 56.
Unloading of 'SAPAPPL2_4' export package: ERROR
Export Monitor jobs: running 2, waiting 24, completed 2, failed 28, total 56.
Unloading of 'SAPAPPL2_3' export package: ERROR
Unloading of 'SAPCLUST' export package: ERROR
Export Monitor jobs: running 0, waiting 24, completed 2, failed 30, total 56.
Export Monitor jobs: running 0, waiting 24, completed 2, failed 30, total 56.
Export Monitor jobs: running 1, waiting 23, completed 2, failed 30, total 56.
Export Monitor jobs: running 2, waiting 22, completed 2, failed 30, total 56.
Export Monitor jobs: running 3, waiting 21, completed 2, failed 30, total 56.
Unloading of 'SAPDFACT' export package: ERROR
Export Monitor jobs: running 2, waiting 21, completed 2, failed 31, total 56.
Unloading of 'SAPDODS' export package: ERROR
Unloading of 'SAPDDIM' export package: ERROR
Export Monitor jobs: running 0, waiting 21, completed 2, failed 33, total 56.
Export Monitor jobs: running 0, waiting 21, completed 2, failed 33, total 56.
Export Monitor jobs: running 1, waiting 20, completed 2, failed 33, total 56.
Export Monitor jobs: running 2, waiting 19, completed 2, failed 33, total 56.
Export Monitor jobs: running 3, waiting 18, completed 2, failed 33, total 56.
Unloading of 'SAPPOOL' export package: ERROR
Export Monitor jobs: running 2, waiting 18, completed 2, failed 34, total 56.
Unloading of 'SAPSDIC' export package: ERROR
Export Monitor jobs: running 1, waiting 18, completed 2, failed 35, total 56.
Unloading of 'SAPNTAB' export package: ERROR
Export Monitor jobs: running 0, waiting 18, completed 2, failed 36, total 56.
Export Monitor jobs: running 1, waiting 17, completed 2, failed 36, total 56.
Export Monitor jobs: running 2, waiting 16, completed 2, failed 36, total 56.
Export Monitor jobs: running 3, waiting 15, completed 2, failed 36, total 56.
Unloading of 'SAPSDOCU' export package: ERROR
Export Monitor jobs: running 2, waiting 15, completed 2, failed 37, total 56.
Unloading of 'SAPSLDEF' export package: ERROR
Export Monitor jobs: running 1, waiting 15, completed 2, failed 38, total 56.
Unloading of 'SAPSLEXC' export package: ERROR
Export Monitor jobs: running 0, waiting 15, completed 2, failed 39, total 56.
Export Monitor jobs: running 1, waiting 14, completed 2, failed 39, total 56.
Export Monitor jobs: running 2, waiting 13, completed 2, failed 39, total 56.
Export Monitor jobs: running 3, waiting 12, completed 2, failed 39, total 56.
Unloading of 'SAPSLOAD' export package: ERROR
Export Monitor jobs: running 2, waiting 12, completed 2, failed 40, total 56.
Unloading of 'SAPSSEXC_1' export package: ERROR
Export Monitor jobs: running 1, waiting 12, completed 2, failed 41, total 56.
Unloading of 'SAPSPROT' export package: ERROR
Export Monitor jobs: running 0, waiting 12, completed 2, failed 42, total 56.
Export Monitor jobs: running 1, waiting 11, completed 2, failed 42, total 56.
Export Monitor jobs: running 2, waiting 10, completed 2, failed 42, total 56.
Export Monitor jobs: running 3, waiting 9, completed 2, failed 42, total 56.
Unloading of 'SAPUSER' export package: ERROR
Export Monitor jobs: running 2, waiting 9, completed 2, failed 43, total 56.
Unloading of 'SAPSSEXC_2' export package: ERROR
Export Monitor jobs: running 1, waiting 9, completed 2, failed 44, total 56.
Unloading of 'SAPSSRC' export package: ERROR
Export Monitor jobs: running 0, waiting 9, completed 2, failed 45, total 56.
Export Monitor jobs: running 1, waiting 8, completed 2, failed 45, total 56.
Export Monitor jobs: running 2, waiting 7, completed 2, failed 45, total 56.
Export Monitor jobs: running 3, waiting 6, completed 2, failed 45, total 56.
Unloading of 'SAPUSER1' export package: ERROR
Unloading of 'SASACONT1' export package: ERROR
Export Monitor jobs: running 1, waiting 6, completed 2, failed 47, total 56.
Export Monitor jobs: running 1, waiting 6, completed 2, failed 47, total 56.
Unloading of 'SEOCOMPODF' export package: ERROR
Export Monitor jobs: running 0, waiting 6, completed 2, failed 48, total 56.
Export Monitor jobs: running 1, waiting 5, completed 2, failed 48, total 56.
Export Monitor jobs: running 2, waiting 4, completed 2, failed 48, total 56.
Export Monitor jobs: running 3, waiting 3, completed 2, failed 48, total 56.
Unloading of 'SMD_HASH_TABLE' export package: ERROR
Export Monitor jobs: running 1, waiting 3, completed 2, failed 50, total 56.
Unloading of 'TST03' export package: ERROR
Export Monitor jobs: running 1, waiting 3, completed 2, failed 50, total 56.
Unloading of 'SOFFCONT1' export package: ERROR
Export Monitor jobs: running 0, waiting 3, completed 2, failed 51, total 56.
Export Monitor jobs: running 1, waiting 2, completed 2, failed 51, total 56.
Export Monitor jobs: running 2, waiting 1, completed 2, failed 51, total 56.
Export Monitor jobs: running 3, waiting 0, completed 2, failed 51, total 56.
Unloading of '_BI0_F0CCMARSH' export package: ERROR
Export Monitor jobs: running 2, waiting 0, completed 2, failed 52, total 56.
Unloading of '_BI0_F0CCMSAEXE' export package: ERROR
Export Monitor jobs: running 1, waiting 0, completed 2, failed 53, total 56.
Unloading of 'WDR_ADP_CONST_MP' export package: ERROR
Export Monitor jobs: running 0, waiting 0, completed 2, failed 54, total 56.
sample failing package log D010INC.log (they all look the same)
/usr/sap/SSM/SYS/exe/run/R3load: START OF LOG: 20100810161653
/usr/sap/SSM/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
/usr/sap/SSM/SYS/exe/run/R3load: version R7.01/V1.4 [UNICODE]
Compiled May 22 2010 00:12:41
/usr/sap/SSM/SYS/exe/run/R3load -ctf E /nfs/@soulman-t/cd/export/ABAP/DATA/D010INC.STR /nfs/@soulman-t/cd/export/ABAP/DB/DDLDB6_LRG.TPL D010INC.TSK DB6 -l D010INC.log
(RTF) ########## WARNING ###########
 Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases
/usr/sap/SSM/SYS/exe/run/R3load: job completed
/usr/sap/SSM/SYS/exe/run/R3load: END OF LOG: 20100810161653
/usr/sap/SSM/SYS/exe/run/R3load: START OF LOG: 20100810161653
/usr/sap/SSM/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
/usr/sap/SSM/SYS/exe/run/R3load: version R7.01/V1.4 [UNICODE]
Compiled May 22 2010 00:12:41
/usr/sap/SSM/SYS/exe/run/R3load -e D010INC.cmd -datacodepage 4102 -l D010INC.log -stop_on_error
(DB) INFO: connected to DB
(DB) INFO: Export without hintfile
(CNV) ERROR: There shall be only one Unicode in a database
/usr/sap/SSM/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/SSM/SYS/exe/run/R3load: END OF LOG: 20100810161655
end of logs -
Ken

Similar Messages

How to migrate from ascii to unicode (MaxDB 7.5)? loadercli: ERR -25347

Hi,
I use MaxDB 7.5.00.26. (Ok, I know that I should switch to 7.6, however, it is not possilble for some customer restriction for now, but should be possible quite soon).
We'd like to migrate a db from ascii to unicode. Based on the infos in the thread "Error at copying database using dumps via loadercli: error -25364" I tried the following:
Export sourcedb
1. Export catalog and data
C:\> loadercli -d db_asc -u dba,dba
loadercli> export db catalog outstream file 'C:\tmp1\20080702a_dbAsc.catalog' ddl
OK
loadercli> export db data outstream file 'C:\tmp1\20080702b_dbAsc.data' pages
OK
loadercli> exit
Import targetdb
1. Create a new empty DB with '_UNICODE=yes'
2. Set 'columncompression' to 'no'
C:\> dbmcli -d db_uni -u dba,dba param_directput columncompression no
ERR
-24979,ERR_XPNOTFOUND: parameter not found
Couldn't find this parameter e.g. in dbmgui (parameters general, extended and support)
3. Import catalog and data
C:\> loadercli -d db_uni -u dba,dba
loadercli> import db catalog instream file 'C:\tmp1\20080702a_dbAsc.catalog' ddl
OK
loadercli> import db data instream file 'C:\tmp1\20080702b_dbAsc.data' pages
ERR -25347
Encoding type of source and target database do not match: source = ASCII, target
= UNICODE.
loadercli> exit
What is wrong? Is a migration from ascii to unicode to be done somehow else?
Can I migrate a db from 7.5.00.26 to 7.6.03.15 in the same way or should it be done in another way.
It would be greate if you point me to a post etc. where these two migrations are explained in detail.
Thanks in advance - kind regards
Michael

Hi,
I can neither find "USEUNICODECOLUMNCOMPRESSION" nor "COLUMNCOMPRESSION". Could it be that there do exist from MaxDB version 7.6 on and not in 7.5?
Kind regards,
Michael
The complete parameter list (created by "dbmcli -d db_uni -u dbm,dbm param_directgetall > maxdb_params.txt") is:
OK
KERNELVERSION                         KERNEL    7.5.0    BUILD 026-123-094-430
INSTANCE_TYPE                         OLTP
MCOD                                  NO
RESTART_SHUTDOWN                      MANUAL
_SERVERDB_FOR_SAP                     YES
_UNICODE                              YES
DEFAULT_CODE                          ASCII
DATE_TIME_FORMAT                      INTERNAL
CONTROLUSERID                         DBM
CONTROLPASSWORD
MAXLOGVOLUMES                         2
MAXDATAVOLUMES                        11
LOG_VOLUME_NAME_001                   LOG_001
LOG_VOLUME_TYPE_001                   F
LOG_VOLUME_SIZE_001                   131072
DATA_VOLUME_NAME_0001                 DAT_0001
DATA_VOLUME_TYPE_0001                 F
DATA_VOLUME_SIZE_0001                 262144
DATA_VOLUME_MODE_0001                 NORMAL
DATA_VOLUME_GROUPS                    1
LOG_BACKUP_TO_PIPE                    NO
MAXBACKUPDEVS                         2
BACKUP_BLOCK_CNT                      8
LOG_MIRRORED                          NO
MAXVOLUMES                            14
_MULT_IO_BLOCK_CNT                    4
_DELAY_LOGWRITER                      0
LOG_IO_QUEUE                          50
_RESTART_TIME                         600
MAXCPU                                1
MAXUSERTASKS                          50
_TRANS_RGNS                           8
_TAB_RGNS                             8
_OMS_REGIONS                          0
_OMS_RGNS                             25
OMS_HEAP_LIMIT                        0
OMS_HEAP_COUNT                        1
OMS_HEAP_BLOCKSIZE                    10000
OMS_HEAP_THRESHOLD                    100
OMS_VERS_THRESHOLD                    2097152
HEAP_CHECK_LEVEL                      0
_ROW_RGNS                             8
_MIN_SERVER_DESC                      16
MAXSERVERTASKS                        21
_MAXTRANS                             292
MAXLOCKS                              2920
_LOCK_SUPPLY_BLOCK                    100
DEADLOCK_DETECTION                    4
SESSION_TIMEOUT                       900
OMS_STREAM_TIMEOUT                    30
REQUEST_TIMEOUT                       5000
_USE_ASYNC_IO                         YES
_IOPROCS_PER_DEV                      1
_IOPROCS_FOR_PRIO                     1
_USE_IOPROCS_ONLY                     NO
_IOPROCS_SWITCH                       2
LRU_FOR_SCAN                          NO
_PAGE_SIZE                            8192
_PACKET_SIZE                          36864
_MINREPLY_SIZE                        4096
_MBLOCK_DATA_SIZE                     32768
_MBLOCK_QUAL_SIZE                     16384
_MBLOCK_STACK_SIZE                    16384
_MBLOCK_STRAT_SIZE                    8192
_WORKSTACK_SIZE                       8192
_WORKDATA_SIZE                        8192
_CAT_CACHE_MINSIZE                    262144
CAT_CACHE_SUPPLY                      3264
INIT_ALLOCATORSIZE                    221184
ALLOW_MULTIPLE_SERVERTASK_UKTS        NO
_TASKCLUSTER_01                       tw;al;ut;2000*sv,100*bup;10*ev,10*gc;
_TASKCLUSTER_02                       ti,100*dw;30000*us;
_TASKCLUSTER_03                       compress
_MP_RGN_QUEUE                         YES
_MP_RGN_DIRTY_READ                    NO
_MP_RGN_BUSY_WAIT                     NO
_MP_DISP_LOOPS                        1
_MP_DISP_PRIO                         NO
XP_MP_RGN_LOOP                        0
MP_RGN_LOOP                           0
_MP_RGN_PRIO                          NO
MAXRGN_REQUEST                        300
_PRIO_BASE_U2U                        100
_PRIO_BASE_IOC                        80
_PRIO_BASE_RAV                        80
_PRIO_BASE_REX                        40
_PRIO_BASE_COM                        10
_PRIO_FACTOR                          80
_DELAY_COMMIT                         NO
_SVP_1_CONV_FLUSH                     NO
_MAXGARBAGE_COLL                      0
_MAXTASK_STACK                        1024
MAX_SERVERTASK_STACK                  100
MAX_SPECIALTASK_STACK                 100
_DW_IO_AREA_SIZE                      50
_DW_IO_AREA_FLUSH                     50
FBM_VOLUME_COMPRESSION                50
FBM_VOLUME_BALANCE                    10
_FBM_LOW_IO_RATE                      10
CACHE_SIZE                            10000
_DW_LRU_TAIL_FLUSH                    25
XP_DATA_CACHE_RGNS                    0
_DATA_CACHE_RGNS                      8
XP_CONVERTER_REGIONS                  0
CONVERTER_REGIONS                     8
XP_MAXPAGER                           0
MAXPAGER                              11
SEQUENCE_CACHE                        1
_IDXFILE_LIST_SIZE                    2048
_SERVER_DESC_CACHE                    74
_SERVER_CMD_CACHE                     22
VOLUMENO_BIT_COUNT                    8
OPTIM_MAX_MERGE                       500
OPTIM_INV_ONLY                        YES
OPTIM_CACHE                           NO
OPTIM_JOIN_FETCH                      0
JOIN_SEARCH_LEVEL                     0
JOIN_MAXTAB_LEVEL4                    16
JOIN_MAXTAB_LEVEL9                    5
_READAHEAD_BLOBS                      25
RUNDIRECTORY                          E:\_mp\u_v_dbs\EVERW_T3
_KERNELDIAGFILE                       knldiag
KERNELDIAGSIZE                        800
_EVENTFILE                            knldiag.evt
_EVENTSIZE                            0
_MAXEVENTTASKS                        1
_MAXEVENTS                            100
_KERNELTRACEFILE                      knltrace
TRACE_PAGES_TI                        2
TRACE_PAGES_GC                        0
TRACE_PAGES_LW                        5
TRACE_PAGES_PG                        3
TRACE_PAGES_US                        10
TRACE_PAGES_UT                        5
TRACE_PAGES_SV                        5
TRACE_PAGES_EV                        2
TRACE_PAGES_BUP                       0
KERNELTRACESIZE                       653
EXTERNAL_DUMP_REQUEST                 NO
_AK_DUMP_ALLOWED                      YES
_KERNELDUMPFILE                       knldump
_RTEDUMPFILE                          rtedump
_UTILITY_PROTFILE                     dbm.utl
UTILITY_PROTSIZE                      100
_BACKUP_HISTFILE                      dbm.knl
_BACKUP_MED_DEF                       dbm.mdf
_MAX_MESSAGE_FILES                    0
_EVENT_ALIVE_CYCLE                    0
_SHAREDDYNDATA                        10280
_SHAREDDYNPOOL                        3658
USE_MEM_ENHANCE                       NO
MEM_ENHANCE_LIMIT                     0
__PARAM_CHANGED___                    0
__PARAM_VERIFIED__                    2008-07-02 21:10:19
DIAG_HISTORY_NUM                      2
DIAG_HISTORY_PATH                     E:\_mp\u_v_dbs\EVERW_T3\DIAGHISTORY
_DIAG_SEM                             1
SHOW_MAX_STACK_USE                    NO
LOG_SEGMENT_SIZE                      43690
SUPPRESS_CORE                         YES
FORMATTING_MODE                       PARALLEL
FORMAT_DATAVOLUME                     YES
HIRES_TIMER_TYPE                      CPU
LOAD_BALANCING_CHK                    0
LOAD_BALANCING_DIF                    10
LOAD_BALANCING_EQ                     5
HS_STORAGE_DLL                        libhsscopy
HS_SYNC_INTERVAL                      50
USE_OPEN_DIRECT                       NO
SYMBOL_DEMANGLING                     NO
EXPAND_COM_TRACE                      NO
OPTIMIZE_OPERATOR_JOIN_COSTFUNC      YES
OPTIMIZE_JOIN_PARALLEL_SERVERS        0
OPTIMIZE_JOIN_OPERATOR_SORT           YES
OPTIMIZE_JOIN_OUTER                   YES
JOIN_OPERATOR_IMPLEMENTATION          YES
JOIN_TABLEBUFFER                      128
OPTIMIZE_FETCH_REVERSE                YES
SET_VOLUME_LOCK                       YES
SHAREDSQL                             NO
SHAREDSQL_EXPECTEDSTATEMENTCOUNT      1500
SHAREDSQL_COMMANDCACHESIZE            32768
MEMORY_ALLOCATION_LIMIT               0
USE_SYSTEM_PAGE_CACHE                 YES
USE_COROUTINES                        YES
MIN_RETENTION_TIME                    60
MAX_RETENTION_TIME                    480
MAX_SINGLE_HASHTABLE_SIZE             512
MAX_HASHTABLE_MEMORY                  5120
HASHED_RESULTSET                      NO
HASHED_RESULTSET_CACHESIZE            262144
AUTO_RECREATE_BAD_INDEXES             NO
LOCAL_REDO_LOG_BUFFER_SIZE            0
FORBID_LOAD_BALANCING                 NO

Migrate/upgrade to support unicode XML

environment:
DB: 9.2.0.4, 9.2.0.5
XMLTYPE on CLOB
we have a new requirement to support full unicode in XML and data. The Oracle9i Database Globalization Support Guide , example Example 5-4 Unicode Solution with Unicode Datatypes hits us perfectly, and it talks about putting data into NVARCHAR2 and NCLOB.
1. Is it possible to set up XMLTYPE to use NCLOB instead of CLOB (for the 9.2.0.5 platform)?
2. It looks like (in reading past forum threads) that there still are some issues in unicode with XMLtype. Do you have any recommendations?
(using shredded types in 9.2.0.n is out because of issues with support for w3c timezone specs for datetime ....)
thanks in advance,

Could you elaborate on this response? I am having trouble inserting an xml document into an xmltype database, and I'm using the AL32UTF8 character set. I receive:
ORA-19202: Error occurred in XML processing
LPX-00217: invalid character 169 (\u00A9)
Error at line 2
The input file has unicode encoded data (©). Here is the insert code:
Create OR Replace Function getClobDocument(
filename in varchar2,
charset in varchar2 default NULL)
return CLOB deterministic
is
file bfile := bfilename('JLEONXDB',filename);
charContent CLOB := ' ';
targetFile bfile;
lang_ctx number := DBMS_LOB.default_lang_ctx;
charset_id number := 0;
src_offset number := 1 ;
dst_offset number := 1 ;
warning number;
begin
if charset is not null then
charset_id := NLS_CHARSET_ID(charset);
end if;
targetFile := file;
DBMS_LOB.fileopen(targetFile, DBMS_LOB.file_readonly);
DBMS_LOB.LOADCLOBFROMFILE(charContent, targetFile,
DBMS_LOB.getLength(targetFile), src_offset, dst_offset, charset_id, lang_ctx,warning);
DBMS_LOB.fileclose(targetFile);
return charContent;
end;
INSERT INTO hdot VALUES(XMLType(getCLOBDocument('browningCUIM.xml','AL32UTF8')));

How to setup the connection between non-unicode client and unicode server?

hi.
we played the program in 4.6x that call a data from unicode server (ECC6.0) to non-unicode server. ( not played in the unicode server.)
When a program ended that English Character was normal, but Korean Chinease... was unknown text.
I think conversion from unicode to non-unicode is a main reason.
General Notes are issued for the unicode side rfc connection configuration.
but, i want to know how to setup into the non-unicode system to interface with unicode system.
I hope your great answer.

Hi,
For taht you have to deploy korean and chinese langauges seprately on non unicode system.Then try to connect to the unicode system.It will work for you.
Regadrs
Vijay kumar

Open dataset in UTF8. Problems between Unicode and non Unicode

Hello,
I am currently testing the file transfer between unicode an non unicode systems.
I transfered some japanese KNA1 data from non unicode system (Mandt,Name1, Name2,City) to a file with this option:
set local language pi_langu.
open dataset pe_file in text mode encoding utf-8 for output with byte-order mark.
Now I want to read the file from a unicode system. The code looks like this:
open dataset file in text mode encoding utf-8 for input skipping byte-order mark.
The characters look fine but they are shifted. name1 is correct but now parts of the city characters are in name2....
If I open the file in a non unicode system with the same coding the data is ok again!
Is there a problem with spaces between unicode an non-unicode?!

Hello again,
after implementing and testing this method, we saw that the conversion is always taken place in the unicode system.
For examble: we have a char(35) field in mdmp with several japanese signs..as soon as we transfer the data into the file and have a look at it the binary data the field is only 28 chars long. several spaces are missing...now if we open the file in our unicode system using the mentioned class the size is gaining to 35 characters
on the other hand if we export data from unicode system using this method the size is shrinking from 35 chars to 28 so the mdmp system can interprete the data.
as soon as all systems are on unicode this method is obselete/wrong because we don't want to cut off/add the spaces..it's not needed anymore..
the better way would be to create a "real" UTF-8 file in our MDMP system. The question is, is there a method to add somehow the missing spaces in the mdmp system?
so it works something like thtat:
OPEN DATASET p_file FOR OUTPUT IN TEXT MODE ENCODING UTF-8 WITH BYTE-ORDER MARK.
"MDMP (with ECC 6.0 by the way)
if charsize = 1.
*add missing spaces to the structure
*transfer strucutre to file
*UNICODE
else.
*just transfer struc to file -> no conversion needed anymore
endif.
I thought mybe somehow this could work with the class CL_ABAP_CONV_OUT_CE. But until now I had no luck...
Normally I would think that if I'am creating a UTF-8 file this work is done automatically on the transfer command

Fonts for printing - unicode or non-unicode

Hi, How could i find whether the fonts am using for scripts and smartforms are unicode compatible or not.
Regards,
Vijayalakshmi

Hello Kyle,
thank you very much.
I have think that I can install the j2ee engine unicode or non unicode. And I can install SAP EP with unicode or non unicode.
There is a cd from SAP its named "NON_Unicode_INST_Master_CD".
In this cd it gives a path "IM08_SOLARIS_64/SAPINST/UNIX/SUNOS_64".
And there is a sapinst. With this sapinst I can install a portal.
Is this portal then a unicode installation, although it is placed on the "NON_Unicode_INST_Master_CD"?
Regards,
Werner

Importing non-unicode data into unicode 10gR2 database

Hi:
I will have to import non-unicode data into unicode 10gR2 database. The systems the data is coming from are the following: CODA, Timberline, COMMS, CMS, LIMS. These are all RDBMS, sql-enabled systems. We are talking about pretty big amounts of data (a couple hundred GB combined).
Did anybody go through a similar exersize?
I know I'll have to setup nls_length_semantics to CHAR.
What other recommendations could you guys give?
TIA,
Greg

I think "nls_length_semantics" isn't mandatory at this point, and you must extract a little quantity of information from every source and do some probes injecting them into the Oracle10g database.

Peoplesoft convert Oracle non-unicode database to unicode database

I am following doc 1437384.1 to convert a Peoplesoft database from non-unicode database to unicode database
I use the following export statement (as user PS)
SET NO TRACE;
SET OUTPUT output_file.dat;
SET NO DATA;
EXPORT *;
And the following import statement (as user sysadm)
SET NO TRACE;
SET NO DATA;
SET INPUT output_file;
SET LOG log_file;
SET UNICODE ON;
SET STATISTICS OFF;
SET ENABLED_DATATYPE 9.0;
IMPORT *;
Before I do the datapump import, I am comparing the objects
SQL> select object_type, count(*) from dba_objects where owner = 'SYSADM' group by object_type order by 1 asc;
OBJECT_TYPE COUNT(*)
INDEX 33797
LOB 2775
TABLE 28829
TRIGGER 9
VIEW 21208
on oracsc63 (targetdb):
SQL> select object_type, count(*) from dba_objects where owner = 'SYSADM' group by object_type order by 1 asc;
OBJECT_TYPE COUNT(*)
INDEX 23748
LOB 2170
TABLE 19727
I don't have the same number of object. When I do the import this means that around 10000 tables will not have the UTF-8 format.
Any ideas how I can solve this? How has experience with this peoplesoft conversions?

Hello Jacques,
please check sapnote #808505 (Secondary connection to Oracle DB w/ different character set).
Regards
Stefan

Unicode and non-unicode

WHAT IS DIFFRENTS BETWEEN UNICODE AND NON UNICODE ?
BRIEFLY EXPLAIN ABOUT UNICODE?
THANKS IN ADVANCES

A 16-bit character encoding scheme allowing characters from Western European, Eastern European, Cyrillic, Greek, Arabic, Hebrew, Chinese, Japanese, Korean, Thai, Urdu, Hindi and all other major world languages, living and dead, to be encoded in a single character set. The Unicode specification also includes standard compression schemes and a wide range of typesetting information required for worldwide locale support. Symbian OS fully implements Unicode. A 16-bit code to represent the characters used in most of the world's scripts. UTF-8 is an alternative encoding in which one or more 8-bit bytes represents each Unicode character. A 16-bit character set defined by ISO 10646. A code similar to ASCII, used for representing commonly used symbols in a digital form. Unlike ASCII, however, Unicode uses a 16-bit dataspace, and so can support a wide variety of non-Roman alphabets including Cyrillic, Han Chinese, Japanese, Arabic, Korean, Bengali, and so on. Supporting common non-Roman alphabets is of interest to community networks, which may want to promote multicultural aspects of their systems.
ABAP Development under Unicode
Prior to Unicode the length of a character was exactly one byte, allowing implicit typecasts or memory-layout oriented programming. With Unicode this situation has changed: One character is no longer one byte, so that additional specifications have to be added to define the unit of measure for implicit or explicit references to (the length of) characters.
Character-like data in ABAP are always represented with the UTF-16 - standard (also used in Java or other development tools like Microsoft's Visual Basic); but this format is not related to the encoding of the underlying database.
A Unicode-enabled ABAP program (UP) is a program in which all Unicode checks are effective. Such a program returns the same results in a non-Unicode system (NUS) as in a Unicode system (US). In order to perform the relevant syntax checks, you must activate the Unicode flag in the screens of the program and class attributes.
In a US, you can only execute programs for which the Unicode flag is set. In future, the Unicode flag must be set for all SAP programs to enable them to run on a US. If the Unicode flag is set for a program, the syntax is checked and the program executed according to the rules described in this document, regardless of whether the system is a US or a NUS. From now on, the Unicode flag must be set for all new programs and classes that are created.
If the Unicode flag is not set, a program can only be executed in an NUS. The syntactical and semantic changes described below do not apply to such programs. However, you can use all language extensions that have been introduced in the process of the conversion to Unicode.
As a result of the modifications and restrictions associated with the Unicode flag, programs are executed in both Unicode and non-Unicode systems with the same semantics to a large degree. In rare cases, however, differences may occur. Programs that are designed to run on both systems therefore need to be tested on both platforms.
Refer to the below related threads
Re: Why the select doesn't run?
what is unicode
unicode
unicode
Regards,
Santosh

Cannot convert between unicode and non-unicode string datatypes

My source is having 3 fields :
ItemCode nvarchar(50)
DivisionCode nvarchar(50)
Salesplan (float)
My destination is :
ItemCode nvarchar(50)
DivisionCode nvarchar(50)
Salesplan (float)
But still I am getting this error :
Column ItemCode cannot convert between unicode and non-unicode string datatypes.
As I am new to SSIS , please show me step by step.
Thanks In Advance.

My source is having 3 fields :
ItemCode nvarchar(50)
DivisionCode nvarchar(50)
Salesplan (float)
My destination is :
ItemCode nvarchar(50)
DivisionCode nvarchar(50)
Salesplan (float)
But still I am getting this error :
Column ItemCode cannot convert between unicode and non-unicode string datatypes.
As I am new to SSIS , please show me step by step.
Thanks In Advance.
HI Subu ,
there is some information gap , what is your source ? are there any transformation in between ?
If its SQL server source and destination and the datatype is as you have mentioned I dont think you should be getting such errors ... to be sure check advance properties of your source and check metada of your source columns
just check simple oledb source as
SELECT TOP 1 ItemCode = cast('111' as nvarchar(50)),DivisionCode = cast('222' AS nvarchar(50)), Salesplan = cast(3.3 As float) FROM sys.sysobjects
and destination as you mentioned ... it should work ...
somewher in your package the source columns metadata is not right .. and you need to convert it or fix the source.
Hope that helps
-- Kunal
Hope that helps ... Kunal

Unicode and Non-Unicode Instances in one Transport Landscape

We have a 4.7 landscape that includes a shared global development system supporting two regional landscapes. The shared global development system is used for all ABAP/Workbench activity and for global customization used by both regional production systems. The two regional landscapes include primarily three instances - Regional Configuration, Quality Assurance, and Production. The transport landscape includes all systems with transport routes for global and regional.
A conversion to unicode is also being planned for the global development and one regional landscape. It is possible that we will not convert the other regional landscape due to pending discussions on consolidation. This means one of the regional landscapes will be receiving global transports from a unicode-based system.
All information I've located implies no actual technical constraints. Make sure you have the right R3trans versions, don't use non-Latin_1 languages, etc. Basic caveats for a heterogenous environment ....
Is anyone currently supporting a complete, productive landscape that includes unicode and non-unicode systems? If so, any issues or problems encountered with transports across the systems? (insignificant or significant)
Information on actual experiences will be greatly appreciated ....
Many thanks in advance.

Hi Laura,
Although i do not have the live / practical experience, but this is what i can share.
I have been working on a Non-Unicode to Unicode conversion project. While we were in the discussion phase there was one such possibility of a scenario that part of the landscapes would remain non-unicode. So based on the research i did by reading and directly interacting with some excellent SPA consultants, i came to know there are absolutely no issues in transporting ABAP programs from a Unicode system to non-unicode system. In a Unicode system the ABAP code has already been checked and rectified for higher syntax checks and these are downward compatible with the ABAP code on lower ABAP versions and non-unicode systems. Hence i beleive there should not be any issues, however as i mentioned this is not from practical experience.
Thanks.
Chetan

Migrating from Linux Mail to Exchange 2013

Is there any official documents of the Best Practices of migrating Linux Mail (Exim) to Exchange 2013?
I appreciate any help that I can receive. Thanks in advance.
My best regards.

Hi,
Basic on my research, I’m afraid that there is no tool for this kind of migration, we may need to start from PST file.
We can use Microsoft Exchange PST Capture to search for PST files on computers in your organization and then import those files to mailboxes in your organization, for your reference:
https://technet.microsoft.com/en-us/library/hh781036(v=exchg.141).aspx
Besides, I find an similar thread about Migrate Exim to Exchange:
https://social.technet.microsoft.com/Forums/office/en-US/0ff095c4-2334-4dd6-8d08-bbee1c98867e/migrating-from-linux-to-exchange-server-2010-question?forum=exchangesvradminlegacy
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Choosing unicode and non-unicode option in SAP Netweaver Mobile 7.1

Hi folks,
do we have the option of choosing a unicode or non-unicode format on installing SAP Netweaver mobile 7.1?
Can we communicate MI unicode system with non-unicode backend?
Let me know on where i can find more info related to this
Regards,
Kalyan

Hi Ankur,
you can also directly navigate to the mobile administrator using the web browser. The url is as follows:
http://host:port/sap/bc/webdynpro/sap/sdoe_administration?sap-language=EN
Host and port you have to adjust to your settings. These are the same settings you are using during synchronization on a client device.
Regards,
Stefan

Unicode or non-unicode RFCSDK

Has someone experience with connecting an unicode SAP-system with a non-unicode subsystem? Which version of the rfcsdk do I need to compile the subsystem, unicode or non-unicode?

Even though this post is really old, I thought I'd reply for the benefit of others.
Your best bet is to use the unicode version of RFC SDK. Then, irrespective of whether the SAP system is unicode or non-unicode, you only need to send unicode bytes. the SDK will take care of the conversion to the code page of the SAP system.

Unicode vs non-unicode

Hi All,
Can anyone please tell me what is the differenece between unicode and non-unicode SAP systems. I heard that all the new versions are unicode. What is the difference, purpose and significance of these?
Thanks
Cyrus

Hi Cyrus,
You are correct that all new SAP Applications and SAP NetWeaver technology will only be available based on unicode (example: SAP NetWeaver MDM, SAP NetWeaver Visual Composer). Unicode code pages enable a system to store and process almost every character symbol in the world.
This means that the applications run on and can process characters from a unicode code page as opposed to a single character set code page like Latin 1 (restricted to only western European Language characters). The Database and it's schemas are able to store all the unicode characters.
The Non-Unicode Single code page systems are supported by SAP for older applications for historical reasons - unicode was not available when they were released. These systems are restricted to only processing characters from their specific code page. This means their can be restrictions if they need to support language combinations that span multiple code pages - basically it is not possible. In addition some languages are not fully available at all for single code page systems like Thai. In addition the Euro symbol is not available.
Unicode is the future for all applications - SAP or otherwise. The significance at the moment is where customers who needs to convert to unicode to support additional business requirements like additional languages. Converting a system, although a simple process is not a trivial process in terms of time and resources.
For additional info check out the following sites:
http://service.sap.com/unicode@SAP
http://service.sap.com/i18N
http://www.unicode.org
I hope this helps,
Mike.

Migration unicode Linux to unicode AIX

Similar Messages

Maybe you are looking for