SAP upgrade issue

Apr 18, 2015 8:03:30 PM [Info ]: The detected system topology is ABAP_ONLY
Apr 18, 2015 8:03:30 PM [Info ]: Dialog eliminator inboxOpEliminator does not allow to omit dialog DefineTargetDialog
Apr 18, 2015 8:03:30 PM [Info ]: Dialog eliminator stackOpEliminator does not allow to omit dialog DefineTargetDialog
Apr 18, 2015 8:03:30 PM [Info ]: Dialog eliminator ContentLocationDialogEleiminator does not allow to omit dialog DefineTargetDialog
Apr 18, 2015 8:03:30 PM [Info ]: Dialog eliminator DownloadSMPEliminator allows to omit dialog DefineTargetDialog
Apr 18, 2015 8:55:43 PM [Info ]: Setting catalog key inbox.option to value true into shared input catalog.
Apr 18, 2015 8:55:43 PM [Info ]: Setting catalog key stack.option to value false into shared input catalog.
Apr 18, 2015 8:55:43 PM [Error ]: The provided Stack file or Directory: /oracle/***/sapdata1/TT_stack.txt, is not valid.
Apr 18, 2015 8:55:43 PM [Info ]: Dialog eliminator inboxOpEliminator does not allow to omit dialog DefineTargetDialog
Apr 18, 2015 8:55:43 PM [Info ]: Dialog eliminator stackOpEliminator does not allow to omit dialog DefineTargetDialog
Apr 18, 2015 8:55:43 PM [Info ]: Dialog eliminator ContentLocationDialogEleiminator does not allow to omit dialog DefineTargetDialog
Apr 18, 2015 8:55:43 PM [Info ]: Dialog eliminator DownloadSMPEliminator allows to omit dialog DefineTargetDialog
Apr 18, 2015 9:05:45 PM [Info ]: Setting catalog key inbox.option to value false into shared input catalog.
Apr 18, 2015 9:05:45 PM [Info ]: Setting catalog key stack.option to value true into shared input catalog.
Apr 18, 2015 9:05:45 PM [Error ]: The following problem has occurred during step execution: com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParserException: /oracle/***/sapdata1/TT_stack.txt is not a valid stack definition file.
Could not parse XML file /oracle/***/sapdata1/TT_stack.txt.
org.xml.sax.SAXException has occurred: Content is not allowed in prolog.
org.xml.sax.SAXParseException: Content is not allowed in prolog.
DETECT define_target define-target-dialog define-target-source com.sap.sdt.j2ee.services.servicesimpl.DefineTargetService class com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParserException

Hi Heng,
com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParserException: /oracle/***/sapdata1/TT_stack.txt is not a valid stack definition file.
Have you read the lines in log which you shared,It's completely an issue with your stack file generated or using.
SUM tool is clearly asking for stack.xml instead of stack.txt
Try to use stack.xml file here to proceed further for a successful upgrade.
Good luck !!

Similar Messages

SAP Upgrade issue ABAP-PI Proxy error

Hi Guys,
We have an issue in SAP R3 system after the recent SAP upgrade.
The proxy programs in R3 were using SAP Standard structure in their development.
Standard structure : SAPPLCO_LOG_ITEM_CODE (TYPE SAPPLCO_LOG)
And so after the upgrade, There seems to be a new field added in the above standard structure and hence causing mismatch between the proxy program developed internal structure to the SAP standard structure.
We come to understand that this Standard structure is being used from SAP PI, Software component SAP APPL.
So SAP PI has old SAP standard structure and SAP R3 has new standard structure with additional field.
Can you please suggest how to overcome this issue. We have also raised an OSS ticket to SAP.
Kind Regards
Rajesh.S

Hi Harald,
Thank You for the information. I was able to download SAP_APPL 6.06 content from SAP service market place. Here We have a doubt before importing the new SAP APPL content. In market place downloads under SAP_APPL 6.06 we were able to see few many database downloads with last changed at 3.04.2014.
Our EHP upgrade for SAP_APPL is 6.06 , SP level 0007. So we should download / import the highlighted content version (SAPAPPL60607) in the screenshot from market place or download / import the latest change under SAP_APPL 6.06 download patch ? Kindly let us know.
Best Regards,
Rajesh.S

SAP SCM Upgrade-Issue in STARTSAT_TRANS in execution phase

Hi Experts,
I am running sap upgrade of SCM 5.1 to SCM 7.0 EHP3.
My Environment is
OS : windows server 2008 R2
Source Kernel :720_ext_rel
DB: MS SQL server
In Execution phase i have encountered issue with MAIN_SWITCH/STARTSAP_TRANS phase and below are the error details and log.
       Checks after phase MAIN_SWITCH/STARTSAP_TRANS were negative!
Last error code set: Process C:\usr\sap\SCN\DVEBMGS51\exe/sapcontrol.exe exited with 2, see 'C:\usr\sap\SCN\SUM\abap\log\SAPup.ECO' for details<br/> System start failed
SAPup.ECo log details :
30.05.2014 02:05:28
StartWait
FAIL: Timeout
SAPup> Process with PID 15804 terminated with status 2 at 20140530020528!
SAPup> Starting subprocess in phase 'STARTSAP_TRANS' at 20140530020528
    ENV: DBMS_TYPE=mss
    ENV: JAVA_HOME=C:\j2sdk1.4.2_26-x64
    ENV: PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.PSC1;.MSC
    ENV: PATH=C:\usr\sap\SCN\DVEBMGS51\exe;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\j2sdk1.4.2_26-x64\bin;C:\Program Files (x86)\Java\jre6\bin;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\usr\sap\SCN\SYS\exe\nuc\NTAMD64
    ENV: SAPSYSTEMNAME=SCN
    ENV: dbs_mss_schema=scn
EXECUTING C:\usr\sap\SCN\DVEBMGS51\exe\sapcontrol.exe -format script -prot PIPE -host SCM51NUN -nr 51 -function GetProcessList
30.05.2014 02:05:28
GetProcessList
OK
0 name: msg_server.EXE
0 description: MessageServer
0 dispstatus: GREEN
0 textstatus: Running
0 starttime: 2014 05 30 01:46:21
0 elapsedtime: 0:19:07
0 pid: 4640
1 name: enserver.EXE
1 description: EnqueueServer
1 dispstatus: GREEN
1 textstatus: Running
1 starttime: 2014 05 30 01:46:21
1 elapsedtime: 0:19:07
1 pid: 5144
2 name: disp+work.EXE
2 description: Dispatcher
2 dispstatus: YELLOW
2 textstatus: Running but Dialog Queue info unavailable
2 starttime: 2014 05 30 01:46:22
2 elapsedtime: 0:19:06
2 pid: 6872
in MMC Dispatcher status is Yellow with text " Running but Dialog Queue info unavailable". Is this the cause of this issue?
If so, how to resolve this issue?
Please help me resolve this issue.
Thanks,
Krishna

Hi Jaun,
here is the DEV_W0 log
trc file: "dev_w0", trc level: 1, release: "720"
* ACTIVE TRACE LEVEL           1
* ACTIVE TRACE COMPONENTS      all, MJ
M sysno      51
M sid        SCN
M systemid   562 (PC with Windows NT)
M relno      7200
M patchlevel 0
M patchno    500
M intno      20020600
M make       multithreaded, ASCII, 64 bit, optimized
M profile    C:\usr\sap\SCN\SYS\profile\SCN_DVEBMGS51_SCM51NUN
M pid        2840
M
M kernel runs with dp version 139(ext=120) (@(#) DPLIB-INT-VERSION-139)
M length of sys_adm_ext is 376 bytes
M ***LOG Q0Q=> tskh_init, WPStart (Workp. 0 2840) [dpxxdisp.c   1381]
I MtxInit: 30000 0 0
M DpSysAdmExtCreate: ABAP is active
M DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
M DpIPCInit2: read dp-profile-values from sys_adm_ext
M DpShMCreate: sizeof(wp_adm) 22880 (1760)
M DpShMCreate: sizeof(tm_adm) 4976768 (24760)
M DpShMCreate: sizeof(wp_ca_adm) 56000 (56)
M DpShMCreate: sizeof(appc_ca_adm) 56000 (56)
M DpCommTableSize: max/headSize/ftSize/tableSize=500/16/776048/776064
M DpShMCreate: sizeof(comm_adm) 776064 (1528)
M DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
M DpShMCreate: sizeof(slock_adm) 0 (232)
M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
M DpShMCreate: sizeof(file_adm) 0 (80)
M DpShMCreate: sizeof(vmc_adm) 0 (1864)
M DpShMCreate: sizeof(wall_adm) (25648/42880/64/104)
M DpShMCreate: sizeof(gw_adm) 48
M DpShMCreate: sizeof(j2ee_adm) 2032
M DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000FD20050, size: 5970896)
M DpShMCreate: allocated sys_adm at 000000000FD20060
M DpShMCreate: allocated wp_adm_list at 000000000FD22A20
M DpShMCreate: allocated wp_adm at 000000000FD22C10
M DpShMCreate: allocated tm_adm_list at 000000000FD28580
M DpShMCreate: allocated tm_adm at 000000000FD285D0
M DpShMCreate: allocated wp_ca_adm at 00000000101E7660
M DpShMCreate: allocated appc_ca_adm at 00000000101F5130
M DpShMCreate: allocated comm_adm at 0000000010202C00
M DpShMCreate: system runs without slock table
M DpShMCreate: system runs without file table
M DpShMCreate: allocated vmc_adm_list at 00000000102C0390
M DpShMCreate: system runs without vmc_adm
M DpShMCreate: allocated gw_adm at 00000000102C0440
M DpShMCreate: allocated j2ee_adm at 00000000102C0480
M DpShMCreate: allocated ca_info at 00000000102C0C80
M DpShMCreate: allocated wall_adm at 00000000102C0D00
M DpCommAttachTable: attached comm table (header=0000000010202C00/ft=0000000010202C10)
M DpRqQInit: use protect_queue / slots_per_queue 0 / 2001 from sys_adm
M rdisp/queue_size_check_value : -> on,50,30,40,500,50,500,80
X EmInit: MmSetImplementation( 2 ).
X MM global diagnostic options set: 0
X <ES> client 0 initializing ....
X <ES> EsILock: use spinlock for locking
X Using implementation view
X <EsNT> Using memory model view.
M <EsNT> Memory Reset disabled as NT default
X ES initialized.
X mm.dump: set maximum dump mem to 192 MB
X mm.dump: set global maximum dump mem to 192 MB
X EsRegisterEmCheck: Register EmGetEsHandles at 0000000140D4F7D0
M DpVmcSetActive: set vmc state DP_VMC_NOT_ACTIVE
M ThStart: taskhandler started
M ThInit: initializing DIA work process W0
M
M Fri May 30 05:23:47 2014
M ThInit: running on host SCM51NUN
M
M Fri May 30 05:23:48 2014
M calling db_connect ...
B Loading DB library 'C:\usr\sap\SCN\DVEBMGS51\exe\dbmssslib.dll' ...
B
B Fri May 30 05:23:49 2014
B Library 'C:\usr\sap\SCN\DVEBMGS51\exe\dbmssslib.dll' loaded
B Version of 'C:\usr\sap\SCN\DVEBMGS51\exe\dbmssslib.dll' is "720.00", patchlevel (0.442)
C Callback functions for dynamic profile parameter registered
C Thread ID:2040
C Thank You for using the SLODBC-interface
C Using dynamic link library 'C:\usr\sap\SCN\DVEBMGS51\exe\dbmssslib.dll'
C dbmssslib.dll patch info
C    SAP patchlevel 0
C    SAP patchno 500
C    Last MSSQL DBSL patchlevel 0
C    Last MSSQL DBSL patchno         442
C    Last MSSQL DBSL patchcomment DBACOCKPIT Auto-injection fails (1901875)
C ODBC Driver chosen: SQL Server Native Client 10.0 native
C lpc:(local) connection used on SCM51NUN
C lpc:(local) connection used on SCM51NUN
C Driver: sqlncli10.dll Driver release: 10.50.4000
C GetDbRelease: 10.50.4000.00
C GetDbRelease: Got DB release numbers (10,50,4000,0)
B Connection 0 opened (DBSL handle 0)
M ThInit: db_connect o.k.
M ICT: exclude compression: *.zip,*.rar,*.arj,*.z,*.gz,*.tar,*.lzh,*.cab,*.hqx,*.ace,*.jar,*.ear,*.war,*.css,*.pdf,*.gzip,*.uue,*.bz2,*.iso,*.sda,*.sar,*.gif,*.png,*.swc,*.swf
I
I Fri May 30 05:23:53 2014
I MtxInit: 0 0 0
M SHM_PRES_BUF (addr: 0000000018410050, size: 4400000)
M SHM_ROLL_AREA (addr: 000007FFCB7C0050, size: 61440000)
M SHM_PAGING_AREA (addr: 0000000018850050, size: 32768000)
M SHM_ROLL_ADM (addr: 00000000098C0050, size: 632336)
M SHM_PAGING_ADM (addr: 000000000BA50050, size: 787488)
M ThCreateNoBuffer allocated 328144 bytes for 1000 entries at 0000000005600050
M ThCreateNoBuffer index size: 3000 elems
M ThCreateVBAdm allocated 17104 bytes (50 server) at 0000000002600050
X EmInit: MmSetImplementation( 2 ).
X MM global diagnostic options set: 0
X <ES> client 0 initializing ....
X Using implementation view
X ES initialized.
X mm.dump: set maximum dump mem to 192 MB
X mm.dump: set global maximum dump mem to 192 MB
X EsRegisterEmCheck: Register EmGetEsHandles at 0000000140D4F7D0
B db_con_shm_ini: WP_ID = 0, WP_CNT = 13, CON_ID = -1
B Table statistics is switched off.
B dbtbxbuf: Buffer TABL (addr: 00000000312B0160, size: 30000000, end: 0000000032F4C4E0)
B dbtbxbuf: Buffer TABLP (addr: 0000000032F50160, size: 10240000, end: 0000000033914160)
B dbsync[db_syinit]: successfully attached to shared memory, sync_adm_p = 0000000002620050
B dbsync[db_syinit]: Buffer synchronisation started with
B    sync_concept      = SEQ_NR
B    sendon            = 0
B    bufreftime        = 120
B    max_gap_wait_time = 60
B    ddlog_del_time    = 60
B    last_counter      = 228455
B    oldest_gap        = (2147483647,00000000000000)
B    time_of_last_sync = 20140530052350
B    MySysId           = 'SCM51NUN            51'
B dbexpbuf[EXP_SHB]: buffer EIBUF installed with
B    semkey             = 35
B    shmkey             = 54
B    wp_n               = 13
B    sclass             = 0
B    block_length       = 256
B    max_objects        = 2000
B    max_obj_size       = 1948608
B    pref_obj_size      = 0
B    est_large_obj_size = 512000
B    free_vec_lg        = 2001
B    hash_vec_size      = 4001
B    buffer_l           = 8388608
B    max_blocks         = 30450
B    free_blocks        = 30450
B    mutex_n            = 4001
B    max_mtx_wait_time = 17000
B    recovery_delay     = 500000
B    tracing            = 0
B    force_checks       = 0
B    protect_shm        = 0
B dbexpbuf[EXP_SHM]: buffer ESM   installed with
B    semkey             = 56
B    shmkey             = 65
B    wp_n               = 13
B    sclass             = 0
B    block_length       = 256
B    max_objects        = 2000
B    max_obj_size       = 907904
B    pref_obj_size      = 0
B    est_large_obj_size = 8192
B    free_vec_lg        = 33
B    hash_vec_size      = 4001
B    buffer_l           = 4194304
B    max_blocks         = 14189
B    free_blocks        = 14189
B    mutex_n            = 4001
B    max_mtx_wait_time = 17000
B    recovery_delay     = 500000
B    tracing            = 0
B    force_checks       = 0
B    protect_shm        = 0
B dbexpbuf[EXP_CUA]: buffer CUA   installed with
B    semkey             = 30
B    shmkey             = 47
B    wp_n               = 13
B    sclass             = 10
B    block_length       = 256
B    max_objects        = 1500
B    max_obj_size       = 661696
B    pref_obj_size      = 0
B    est_large_obj_size = 49152
B    free_vec_lg        = 193
B    hash_vec_size      = 3001
B    buffer_l           = 3072000
B    max_blocks         = 10342
B    free_blocks        = 10342
B    mutex_n            = 3001
B    max_mtx_wait_time = 17000
B    recovery_delay     = 500000
B    tracing            = 0
B    force_checks       = 0
B    protect_shm        = 0
B dbexpbuf[EXP_OTR]: buffer OTR   installed with
B    semkey             = 55
B    shmkey             = 64
B    wp_n               = 13
B    sclass             = 13
B    block_length       = 128
B    max_objects        = 2000
B    max_obj_size       = 907744
B    pref_obj_size      = 0
B    est_large_obj_size = 10240
B    free_vec_lg        = 81
B    hash_vec_size      = 4001
B    buffer_l           = 4194304
B    max_blocks         = 28373
B    free_blocks        = 28373
B    mutex_n            = 4001
B    max_mtx_wait_time = 17000
B    recovery_delay     = 500000
B    tracing            = 0
B    force_checks       = 0
B    protect_shm        = 0
I MPI: dynamic quotas disabled.
I MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
M rdisp/thwpsf_critical_path : -1 -> 0
M Semaphore recovery: keep semaphore data.
M logoff_check: no check.
M CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
M CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
G
G Fri May 30 05:23:54 2014
G RelWritePermissionForShm( pLocation = 120, pEnforce = 0 )
G GetWritePermissionForShm( pLocation = 99, pEnforce = 1 )
G RelWritePermissionForShm( pLocation = 100, pEnforce = 1 )
S *** init spool environment
S TSPEVJOB updates outside critical section: event_update_nocsec = 1
S initialize debug system
T Stack direction is downwards.
T debug control: prepare exclude for printer trace
T new memory block 00000000098696A0
S
S Fri May 30 05:23:55 2014
S spool kernel/ddic check: Ok
S using table TSP02FX for frontend printing
S 0 spool work process(es) found
S frontend print via spool service enabled
S printer list size is 150
S printer type list size is 50
S queue size (profile)   = 300
S hostspool list size = 3000
S option list size is 30
S      found processing queue enabled
S found spool memory service RSPO-RCLOCKS at 0000000015F100C0
S doing lock recovery
S setting server cache root
S found spool memory service RSPO-SERVERCACHE at 0000000015F10460
S    using messages for server info
S size of spec char cache entry: 165024 bytes (timeout 100 sec)
S size of open spool request entry: 1376 bytes
S immediate print option for implicitely closed spool requests is disabled
A ***GENER* Trace switched on ***
A
A ---PXA-------------------------------------------
A PXA INITIALIZATION
A PXA: Locked PXA-Semaphore.
A System page size: 4kb, total admin_size: 46436kb, dir_size: 45852kb.
A Attached to PXA (address 000007FFCF260050, size 800000K, 1 fragments of 753564K )
A PXA allocated (address 000007FFCF260050, size 800000K)
A abap/pxa = shared protect gen_local
A PXA: checking structure sizes: 752|216|16
A PXA INITIALIZATION FINISHED
A ---PXA-------------------------------------------
A
A ATRA: pfclock execution time = 1
A ABAP ShmAdm attached (addr=000007DFF8D7B000 leng=20955136 end=000007DFFA177000)
A >> Shm MMADM area (addr=000007DFF917BCD0 leng=257728 end=000007DFF91BAB90)
A >> Shm MMDAT area (addr=000007DFF91BB000 leng=16494592 end=000007DFFA176000)
A RFC Destination> destination SCM51NUN_SCN_51 host SCM51NUN system SCN systnr 51 (SCM51NUN_SCN_51)
A RFC Options> H=SCM51NUN,S=51,d=1,
A RFC FRFC> fallback activ but this is not a central instance.
A
A RFC rfc/signon_error_log = -1
A RFC rfc/dump_connection_info = 0
A RFC rfc/dump_client_info = 0
A RFC rfc/cp_convert/ignore_error = 1
A RFC rfc/cp_convert/conversion_char = 23
A RFC rfc/wan_compress/threshold = 251
A RFC rfc/recorder_pcs not set, use defaule value: 1
A RFC rfc/delta_trc_level not set, use default value: 0
A RFC rfc/no_uuid_check not set, use default value: 0
H HTTP> Parameter icf/ssocookie_mandatory set to 0
A Hotpackage version: 21
B dbtran INFO (init_connection '<DEFAULT>' [MSSQL:720.00]):
B   max_blocking_factor       = 50, min_blocking_factor         =   5,
B   max_in_blocking_factor    = 255, min_in_blocking_factor      = 10,
B   max_union_blocking_factor = 50, min_union_blocking_factor   =   5,
B   prefer_union_all          =   1, prefer_join                 =   1,
B   prefer_fix_blocking       =   0, prefer_in_itab_opt          =   0,
B   convert AVG               =   1, alias table FUPD            =   0,
B   escape_as_literal         =   0,
B   select *                  =0x00, character encoding          =SBCS / []:X,
B   use_hints                 = abap->1, dbif->0x1, upto->0
M
M Fri May 30 05:23:56 2014
M ThrCreateShObjects allocated 26878 bytes at 0000000002640050
Y dyWpInit
Y    ztta/dynpro_ara 800000
Y    ztta/cua_ara    250000
Y    ztta/diag_ara   250000
M rdisp/thsend_order : -1 -> 1
M ThISend: set thsend_order to 1
N SsfSapSecin: putenv(SECUDIR=C:\usr\sap\SCN\DVEBMGS51\sec): ok
N
N =================================================
N === SSF INITIALIZATION:
N ===...SSF Security Toolkit name SAPSECULIB .
N ===...SSF library is C:\usr\sap\SCN\DVEBMGS51\exe\sapsecu.dll .
N ===...SSF default hash algorithm is SHA1 .
N ===...SSF default symmetric encryption algorithm is DES-CBC .
N ===...SECUDIR="C:\usr\sap\SCN\DVEBMGS51\sec"
N ===...loading of Security Toolkit completed with rc 5 (SSF_SUP_NOTALLFUNCTIONS).
N ===   SAPSECULIB Version 5.4.28M-6
N =================================================
N
N Fri May 30 05:23:57 2014
N MskiInitLogonTicketCacheHandle: Logon Ticket cache pointer retrieved from shared memory.
N MskiInitLogonTicketCacheHandle: Workprocess runs with Logon Ticket cache.
M JrfcVmcRegisterNativesDriver o.k.
W =================================================
W === ipl_Init() called
W    ITS Plugin: Path dw_gui
W    ITS Plugin: Description ITS Plugin - ITS rendering DLL
W    ITS Plugin: sizeof(SAP_UC) 1
W    ITS Plugin: Release: 720, [7200.0.500.20020600]
W    ITS Plugin: Int.version, [33]
W    ITS Plugin: Feature set: [30]
W    ===... Calling itsp_Init in external dll ===>
W === ipl_Init() returns 0, ITSPE_OK: OK
W =================================================
N SignInit: Security Session Management cannot be used (ABAP parts are missing, note 1477428)
N VSI: WP init in ABAP VM completed with rc=0
E EnqId_Initialize: local EnqId initialization o.k.
M MBUF info for hooks: MS component UP
M ThISetEnqname: enq name = >SCM51NUN_SCN_51                         <
M ThActivateServer: STARTING => ACTIVE
L BtcSysStartRaise: Begin
L Raise event SAP_SYSTEM_START with parameter <SCM51NUN_SCN_51     >
L BtcSysStartRaise: End
S server @>SSRV:SCM51NUN_SCN_51@< appears or changes (state 1)
M
M Fri May 30 05:23:58 2014
M 30.05.2014 09:23:58.245 PID=2840, TID=2040 SapTimer info. v1.119 SynchCount:0 , OwnerPid: 3868, ErrsCount: 0, SapTime-WindowsUtcTime=-17 millisec (max=-17), Nosync=23 sec, SynchsPerDay=0.000000, MaxQpcTimeMinusWindowsTimeMismatch: +0 millisec, TotalTimeCorrection=+0 millisec, QpcTime-WindowsUtcTime=-17 millisec (*)
A
A Fri May 30 05:24:03 2014
A UpdateProfile (new settings): off,krn_impl,(no dyn check),(no logging),(no stat err),(local generation),(no commit)
A UpdateProfile (new exceptions): (tmp_err),(home_err),(local_err)
A UpdateProfile (new version): 0
A ***GENER* Trace switched off ***
B dbdynpdb2: no VERSION column found in table DYNPSOURCE
E
E Fri May 30 05:24:04 2014
E Enqueue Info: enque/use_pfclock2 = FALSE
E Enqueue Info: row condense enabled
G GetWritePermissionForShm( pLocation = 281, pEnforce = 0 )
G
G Fri May 30 05:24:05 2014
G RelWritePermissionForShm( pLocation = 277, pEnforce = 0 )
G GetWritePermissionForShm( pLocation = 281, pEnforce = 0 )
G RelWritePermissionForShm( pLocation = 277, pEnforce = 0 )
E EnqId_EN_ObjShMem_Check: status = ENQID_API_INITIAL_VALUE
E EnqId inscribed into initial ObjShMem: (EnqId_EN_ObjShMem_Check)
E ---SHMEM--------------------------------------------------------------------------------
E EnqId:          EnqTabCreaTime/RandomNumber    = 30.05.2014 05:23:34 1401441814 / 3208
E ReqOrd at Srv: TimeInSecs/ReqNumberThisSec    = 30.05.2014 05:24:05 1401441845 / 1
E ReqOrd at Cli: TimeInSecs/ReqNumberThisSec    = 30.05.2014 05:24:05 1401441845 / 1
E Status:         STATUS_OK
E ----------------------------------------------------------------------------------------
A EXCP> Attribute IS_RESUMABLE not found in class CX_ROOT.
B
B Fri May 30 05:24:06 2014
B table logging switched off for all clients
Thanks,
krishna

EHP Upgrade Issue - Java Stack

Hi,
Our Source System at NW 7.0 SP13 and we are upgrading the system to EHP1 SP03.
Upgrade failed at Downtime > DEPLOY_ONLINE_DEPL phase.
Error log:
Sep 9, 2009 10:11:51 PM [Error]:                       com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase.
Sep 9, 2009 10:11:51 PM [Error]:             com.sap.sdt.jspm.unattended.RequestController.addContextInfo(RequestController.java:178) [Thread[main,5,main]]: Deployment of queue sapjup-queue completed with error
JSPM version is 7.01.3.0.15. Current JSPM log directory is /usr/sap/XPD/JC00/j2ee/JSPM/log/log_2009_09_09_16_09_42.
Sep 9, 2009 10:11:51 PM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createAndLogRapiException(SAPJupJSPMRapiAdapter.java:698) [Thread[main,5,main]]: The deployment of the queue failed.
Sep 9, 2009 10:11:51 PM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.deploy.SAPJupJSPMDeployer.deployList(SAPJupJSPMDeployer.java:68) [Thread[main,5,main]]: Could not execute deployment of stack file /usr/sap/trans/EPS/in/XPD.xml.
Sep 9, 2009 10:11:51 PM [Error]:      com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.execute(PhaseTypeDeploymentManager.java:519) [Thread[main,5,main]]: Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action.
Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase UPGRADE/DEPLOYMENT_BASED_UPGRADE/DEPLOY_ONLINE_DEPL has been completed.
Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2009/09/09 22:09:42.
Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2009/09/09 22:11:51.
Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:02:08.248.
Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]: Phase status is error.
I went through the following link , proceeded with option 2, But still getting same error.
Portal Upgrade Issue
Please advise the resolution for the issue I have.
Thanks in advance
Regards
Srinivas
Edited by: Srinivas Dasari on Sep 10, 2009 5:48 AM
Edited by: Srinivas Dasari on Sep 10, 2009 5:48 AM

Issue resolved

ECC 6.0 EHP-4 upgrade Issue in phase MAIN SHDRUN/ALTNTAB FILL were negative

Hi Basis Expert,
while doing ECC 6.0 EHP-4 Upgrade in MAIN_SHDRUN/ALTNTAB_FILL phase we are getting the following issue please help us.
Checks after phase MAIN_SHDRUN/ALTNTAB_FILL were negative!
Last error code set: BATCH JOB RDDNT2MT FAILED: Error(s) found in the log(s), accumulated in "ALTNTFI.ELG".
We check the shadow instance is up and we can log in to the system. Check ST22 and SM21 notice no error.
Check the JOB RDDNT2MT (SM37) successfully running and all the job finish without any error.
Hope anybody can share a bit your experience on this issue. we try search the note and find the forum but no luck.
Thanks

Hi,
> 2EETG011 "No shadow system""(environment parameter)""auth_shadow_upgrade"
> 2EETG011 "No shadow system""DB-connect not against shadow tables !"
>
It looks from your log that shadow system is not able to connect to database. Please check your shadow system. Check below link as well:
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/ecc-6-upgrade-issue-in-phase-altntab_fill-1556272
Thanks
Sunny
Edited by: Sunny Pahuja on Oct 15, 2010 1:27 PM

SAP upgrade - questions for report painter and query

Hi Experts,
I have two quwstions of SAP upgrade.
My requirement is: SAP upgrade from 4.6B to ECC 6.0 with non-unicode.
1.Does SAP upgrade influence the report painter? If influence, could you tell me what should I do for this case.
2. We have so many queries (SQ01) in our system and many of them haven't been run for a long time. we need a tool to get the runtimes of queries in a certain durition.
For example: From 2008/01/01 to 2008/03/31,I want to know how many queries had been run/ query name/ runtimes of each query.
Best regards,

> 1.Does SAP upgrade influence the report painter? If influence, could you tell me what should I do for this case.
You can check
Note 1155524 - ReportWriter: Upgrade Issues ECC6.0 -Common Customer Issues
> 2. We have so many queries (SQ01) in our system and many of them haven't been run for a long time. we need a tool to get the runtimes of queries in a certain durition.
Such a tool was RBE (Reverse Business Engineer) - which is out of support.
You can try to get that information from ST03. If that is not enough there's no other way than booking an SLO service to find out the queries that have not been used (http://service.sap.com/slo).
Markus

Problem realted to SAP upgrade

Hi all,
Can someone help me identifing the issues realted to SAP upgrade(eg - 4.7 to 5.00)
Regards,
Kartavya

Did you check out the Upgrade tools available at the <a href="https://websmp108.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000497720&">SAP Service Market place</a>
~Suresh

SAP Upgrade - Features

Hi,
We are working in a sap upgrade project ECC 5.0 to ECC6.0. We have found a issue in the features ( PE03) after the upgrade of the dev system. The modifications done to the features has now been overwritten by sap.
eg: The dates maintained in the Feature GBCHG - decision tree nodes are not the same before and after upgrade.
1. Are changes to features captured in SPAU/SPDD or what is the way to find out which/what features need to be adjusted again ?
2. Are there any other sap hr objects configurations which needs to be taken care similar to features?
Thanks
Jagruthi

@ Jagruthi:
Hmmm, have you checked the overall structure of the Feature in QA using PE03. A lot of implementations change the way a structure is used to assist their configuration.
When you are in PE03 click on Attributes to look at the author of the changes for the Feature. This is seen on the Administrative Data box (bottom of the page). Notice if Last Changed is a User Name of a company user instead of SAP.
Also when you're in this view, review the actual structure to determine if the same Structure and fields match what you have in DEV.
I really doubt SAP has changed the Feature from ECC 5 to ECC 6. It is much more likely someone has reconfigured the Feautre a long time back.
Cheers, Al

Upgradation issue related to ecc5.0 to 7nw

hi experts
These regarding what type questionears we need to put for upgard from ecc5.0 to 7nw ?
the clent having all hcm module ie om,pa,tm,payroll india and ess/mss, e-rec and interstated in upgrade
I need to put some question bank regarding this..
Since this is my first upgrationg project i donot have any idea about this i would higly appriciate you all if you explain this things and quiestionaries..
Reply soon..
Thanks in advance....
Thanks
Nisha

before upgrade you have to run the pre-requiste checker. It will check the system and tell you exactly whether this system can be upgraded. Once that is done you can download the sap quick sizer from service marketplace to chekc the hardware scope of the upgrade. Else you have th implimentation experience then there will be extra 10 to 15,000 tables added in new version and also the changes in program and also you need space for shadow instance.
Check the DB files area and if the data is 4-5 years old you can archive the data if the company policy support. Keep suffiecinebt space in SAP Application drive and also the DB files drive. See the virtual memory properly see also the RAM 16 GB minimum if you can keep will be better. If it is more excellent and also the CPU's. If you have more CPU capacity the processing will be faster you can define more parallel processes during upgrade. So, these are the few hardware related things to take care of.
About documentation refer the sap upgrade guide and all the sapnoten download which are mentioned in the upgrade guide. It is excellent. I have used these guides and sapnotes while upgrade and it was ok.
During the upgrade you may face some problems this is normal and you should look the logs which are there in the upgrade directory \usr\sa\put\.....
be careful in analyzing the errors and all the pr-requistites which you have to do before upgrade mentioned in the guide. If you follow these properly you will have very less issues. During phase act_640 you may have to do some dictionery adjustments which depends on the dictonery objects you can take help from the developer for this.
There is one tool to restore the variants that is ASU(application specific upgrade).
Then your variants will not be lost. Go to sap site http://service.sap.com/upgrade and checkout all upgrade related documents. You are done.
It will be a smooth upgrade.
Rgds and Good luck.

SAP upgradation ?

hii
What will be the major work for MM consultant in SAP upgradation (4.5 to ECC 6.0).
What is the latest version of SAP??
Explain in more detail about MM consultant roles and responsibilities n SAP upgradation (4.5 to ECC 6.0).
Thanks

Normally upgradation project is basis driven project. Basis guys will prepare the system taking into consideration of all the aspects of the system. This itself is project called upgrade. Upgrading project mostly involves testing with the existing system with the new system. SAP already released the release notes for this Upgrading ECC 6.0{example 4.6C to ECC 6.0}. (1).Functional consultant have to do unit test/Integration test/Regression test in new system based on the business process documents prepared for your present system. (2).Functional consultant mostly encounter Interface issues (If exist)/Authorization issues/Enhanced naming issues/Usage issues. (3).Example:In older version you have to do external configuration for CIN. However .In ERP 2005, It is already in built. Hence Knowledge of CIN will be more than sufficient to manage the CIN issues. (4). More over Functional consultant must be very confident in the business process. Unless you will receive many UAT issues. (5). Whenever Functional consultant do unit test and Integration test, use user id to.When you do regression testing, get the user id from user copy all the roles from the user id and create new id. Using this new id you do the Regression testing. This will avoid many problems. (6). Another Important, big issue is patch work information. For example After release of 46C, SAP released many patches for 46C.However these patches are all not updated in to your present 46C system. These patches are already in built in ECC 6.0, hence you will get diff.result when you do testing. If such a case, advices the user about the patch work, and proceed. In most of my cases, SAP enjoyed with 46C without patch scenario, but in ECC6.0 they started to complain, b'cas the new patches.
Check this link for further details:
Re: upgrade from 4.7 to 6.0
Edited by: Afshad Irani on Aug 9, 2010 11:35 AM

SAP Upgrade Templates

Hi
Can any one send me the templates that are used for an SAP Upgrade project.The kind of templates i need for Change request,Project issue,Upgrade Checks and other......
If you have any other templates regarding Upgrade project, kindly mail to my e-mail id:[email protected]
Thanks in Advance
T.Ram

Hi,
Please follow the below mentioned link. You will get clear understanding about the upgrade here..
https://wiki.sdn.sap.com/wiki/display/HOME/ERP2005+Upgrade
Incase of any specific requirement, please get back.
Regards,
Imran

Things to be aware while doing SAP Upgrade on IBM AIX

Hi,
We are migrating from HP Unix platform to IBM AIX through our new project.
Could you please let me know the risks of doing SAP Upgrade on IBM AIX Platform and things to be aware while doing SAP Upgrade on IBM AIX.
Regards,
Farhana

Hi,
You need to refer to respective system copy guide and upgrade guide to know about pre-requisites before doing migration and upgrade on AIX platform.
Practically there are no major issues seen on AIX platform during migration as well as during upgrade.
Hope this helps.
Regards,
Deepak Kori

Impact of SAP upgrade on CIN

Hi All,
We have SAP upgrade starting in few days from SAP 4.6c to ECC 6.0.
In SAP 4.6c CIN was an add-on whereas as per my understanding this comes now included in SAP_APPL package. Can you please let me know if we need to perform any additional activity during SAP upgrade with regards to CIN.
Thanks.

Hi,
1. Can we complete BOBJ go-live for Oracle DB based reporting area first then install SAP integration kit?
>> Yes you could but what about installing the SAP Integration Kit already but not using it for now ?
The SAP Integration Kit does deliver a set of drivers but also integrations into InfoView and the Central Management Console around the authentication for users.
2. Or itu2019s recommended to install SAP integration kit now during BOBJ PRD server build phase so later when Oracle based BOBJ reporting is live; Installation of SAP integration kit doesnu2019t cause any issue.
>> It is pretty much up to you on how you would like to handle it. both options are possible.
Ingo

Upgrade issues OBIEE 10g to 11g along with OBIA upgrade

Hi,
I have to upgrade OBIEE 10.1.3.4.1 to OBIEE 11.1.1.5 along with OBIA 7.9.6.1 to 7.9.6.5(Informatica 8.6.1 to 9.0.1) at my client location and I have very little knowledge on it. and want to know/have help documents for upgrade.
And if anyone in the forums involved in upgrade please list the errors/issues occured during upgrade and after upgrade.
1. OBIEE 10g to 11g upgrade issues??
2. OBIA OBIA 7.9.6.1 to 7.9.6.5 upgrade issues along with 10g to 11g??
3. Informatica 8.6.1 to 9.0.1 upgrade issues??
4. DAC upgrade issues??
any response for my questions is appreciated.
Thanks
Jay.
Edited by: Jay on Apr 11, 2012 9:11 AM

HI Jay,
We cannot explained thread list here, If you get any errors plz post me,will try to help out.
This is oracle document link - This document has given step by step with screen shots upgration for 10g to 11g ,Please refer the below link.
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm
http://obieemanu.blogspot.in/2011/05/rpd-upgration-from-10g-to-11g.html
http://docs.oracle.com/cd/E21764_01/upgrade.1111/e10125/ua_command_line.htm#ASMAS149
Award points it is useful.
Thanks,
satya

Report generation toolkit upgrade issues

I have created multiple vi's in that utilize the previous report generation toolkits specifically using the Generate Report Get Data to Modify.vi and the Generate Report Set Modified Data.vi. Obviously the report reference has now changed in 8.6's version of the report generation toolkit and these vi's do not exist in the 8.6 library anymore. What vi's do I need to replace these functions with to make this code work. Can anyone tell me what the work around is to solving this problem. This is a picture of the code.
BJD1613
Lead Test Tools Development Engineer
Philips Respironics
Certified LV Architect / Instructor
Attachments:
code.JPG ‏92 KB

Hi BJD1613,
The Report Generation VIs on the LabVIEW Palettes mutate properly. However, you may run into upgrade issues if VIs distributed with LabVIEW, but not available in the Palettes are used in the code. Hence, I would caution against using them for the same reason.
In this case, the specific references do exist in the report generation classes; however, since they are private, they cannot be accessed by VIs outside the respective classes. A temporary workaround for now is mentioned in the following KB 4OOCSJ4M Getting References in Report Generation Toolkit 1.1.3 with LabVIEW 8.6.
This was reported to R&D (CAR# 123064) for further investigation

SAP upgrade issue

Similar Messages

Maybe you are looking for