Database upgrade during SAP upgrade

Hi Experts,
we are using 4.6C based on oracle db 8.0.5.
I have some questions here:
1. if we want ot upgrade both sap and oracle, which one should be upgrade first? sap or oracle?
2. if we only want to upgrade oracle, which tool should we use? BRTOOLS? use brtools to backup and restore DB or with load based system copy(exp/imp)? Could you tell me more about the way to upgrade db only?
3. as I checked 4.6C doesn't support oracle 11g, is it right?
thank you for all.
Freshman

Hi,
In your case, you need to carry out upgrade in 3 step to upgrade your db and SAP.
1) Upgrade kernel to EXT kernel and then do the upgrade to Oracle 10g using tools as described earlier.
2) Do the SAP Application upgrade to target release.
3) Upgrade your database again to oracle 11g.
Thanks
Sunny

Similar Messages

Role of Time Mgmt functional consultant during SAP Upgrade from 4.7 to ECC6

Hi,
Could anyone explain the role of a time management functional consultant during SAP upgrade from R/3 4.7 to ECC6.0. Please provide me if you got any documentation.
Thanks,
Sunny

"After you upgrade to SAP ERP 6.0, you can enhance the functionality of your application without performing a further
upgrade thanks to a new deployment technology u2013 the SAP enhancement package for SAP ERP. The enhancement
packages simplify the way you manage and deploy new software functions for SAP ERP." - that is the real benefit of ECC 6.0
There aren't any major changes to PTM functionalities from 4.7 to 6.0. I hope your system is already using IT 2006 instead of IT 0005. Under functional role, you are required to configure/test any functional upgrade and manage data.
Regards
Yash

SPDD Adjustment for Database indexes during the Upgrade

Hi Experts,
I am currently upgrading our Existing ERP 6.0 SP13 to ERP 6.0 ehp 4.0 with SP 03 and NW 701. I am kind of lost on the SPDD modifications Adjustment. We have 4 objects are in the SPDD modifications under "Without Medications Assistant. All of them are related to Database tables, where our developers created indexes for SAP Delivered Database table object. All of them are YELLOW. If select one of them and go to "Adopt Medications", it brings a Dialog window with
"Database table BKPF. Adjust all objects selected subtree?" --> I clicked on YES
I get the following
Database Table BKPF Table Index Z01
background
The object has been modified without using the Modification Assistant.
Therefore no support is available from the system for transferring your
modifications.
Procedure
   *[Subtree icon]* Before you adjust your modifications, you can select multiple
objects or a subtree.
*[Check Mark icon]*   If you have selected multiple objects, you can skip the processing
of this object.
You can use the "Processor/Status" function to add other processors.
If you have modified an object where multiple versions are possible,
then the last version that contains changes has been stored in "version
management".
    *[Pencil icon]* Otherwise, use your own notations to transfer the modifications to
the new version of the object.
    *[Check Mark icon]* After an object is inserted in a transportable change request, the
red traffic light icon is replaced by the green checkmark in the tree.
If you do not want any modifications to be adopted, choose the "Reset
to Original" function.
I clicked on the Pencil icon [PENCIL CHANGE] -> it takes me to that object where I DO NOT have any options to adopt the objects....
I am bit of confused, I should get an option to adopt this object, so I can keep the current version and SAP doesnt over write it after upgrade and delete my indexes.
Please tell me what I am doing wrong here.
Thanks in Adamancy
Kumar
Edited by: Kumar Subramaniam on Jun 9, 2009 7:43 PM

OSS note 1658376 (Table index displayed in transaction SPDD after deletion) is relevant for this and check the below link as well.
http://www.sapdiary.com/index.php?option=com_content&view=article&id=22738:sap-network-blog-extension-index-in-spdd&catid=81:data-services&Itemid=81
Regards,
Gokul

SCC4 - Protection against SAP upgrade

Hello guys,
i have a question regarding to the "Protection against SAP upgrade" flag in SCC4 for the client settings.
I know that this flag will make a client unusable in case of an upgrade (for example from ERP2004 to ERP2005), but what is about applying support packages?
Is this flag also valid for support packages?
The documentation about this parameter does not make a statement to this point:
> If this flag is set, the client is no longer supplied with data during SAP upgrades. After an SAP upgrade, it is not possible to work actively in the client. The flag can only be set for a test client or an SAP reference client (Early Watch).
Does SAP understand "applying support packages" as an upgrade?
Answers will be rewarded.
Regards
Stefan

No.
Applying SP is not SAP upgrade.
-Pinkle

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

Best practice to secure database during patching/upgrade-Vault disabled

I have a highly confidential system and to protect the data in the DB, I intend to use Oracle Vault. In my company, we have centralized services and therefore, the oracle Unix owner and sysdba are owned by this group, not the application dba that "knows" the system (me).
The problem I have is what would be the best way to protect my data from the sysdba user during the window that Vault is disabled?
I thougth maybe I could un-mount and file protect the tablespace from the Unix oracle user during the upgrade process, but the tablespace could be outdated when I remount it after the patch. I am not sure how I might patch it seperatley. I am thinking I might export and drop the schema during the patching, then load it back in when vault is enabled again. This will work for a year or so, but I envision the databases getting too large to do this efficiently.
Does anyone have any thoughts on how I might protect the data in this scenario?
Edited by: user4714217 on Oct 20, 2008 11:06 AM for clarity

Hi,
I did not understood your question properly, but the thing which I understood is like you do not want any other user to access the database when your security vault is disabled.
At that time you can
1) Start the database in restrict mode (only a sysdba can do it).
2) Change the password/lock the user till the time your patching activity is going (any user with dba role can do it, so might be not so useful)
Regards
Anurag Tibrewal

Business continuity during planned SAP upgrades

What techniques are SAP customers employing to accommodate SAP upgrades and at the same time ensure 24/7/365 business continuity?
Thanks for sharing your experiences.
Fred

Hi Fred,
have you checked out the nZDM capabilities offered by SUM (details see here)? Additionally, you can find a good summary in this solution brief, where all other possibilities are summarized.
Hope this helps.
Bernhard

Upgrade fails in the phase STARTSAP_TBUPG during the upgrade of CRM 4 to 5

Hello,
Upgrade failed with the below message in the upgrade phase STARTSAP_TBUPG during the upgrade of CRM 4.0 to CRM 5.0
Error Message:
SYSTEM START failed, code -1
             -1: 'startsap.exe' returned an error
             See file 'D:\usr\sap\put\log\R3up.ECO' for details.
R3up.ECO:
SAPup> Starting subprocess startsap.exe with id 5844 at 20080402142258
EXECUTING D:\usr\sap\put\exe\startsap.exe name=SID nr=00 SAPDIAHOST=Hostname
Environment: dbms_type=mss
Environment: dbs_mss_schema=cdu
STARTSAP failed
Details are written to D:\usr\sap\put\tmp\startSID.log
Process with ID 6276 terminated with status -1
startSID.log
running D:\usr\sap\put\exe\sapstart.exe name=SID nr=00 SAPDIAHOST=Hostname -wait
SAPSTART finished successfully on Host_SID_00, but at least one process doesn't run correctly:
     msg_server.exe, MessageServer, Running, 2008 04 02 14:22:58, 0:03:19
     disp+work.exe, Dispatcher, Running, Message Server connection ok, Dialog Queue time: 0.00 sec, 2008 04 02 14:22:58, 0:03:19
     igswd.exe, IGS Watchdog, Stopped, 2008 04 02 14:22:58, 0:00:00
D:\usr\sap\put\exe\sapstart.exe=>sapparam(1c): No Profile used.
It is trying to start the shadow instance and failing by ending all the work process
DEV_DISP:
trc file: "dev_disp", trc level: 1, release: "700"
sysno      01
sid        SID
systemid   560 (PC with Windows NT)
relno      7000
patchlevel 0
patchno    150
intno      20050900
make:      multithreaded, ASCII, optimized
pid        5348
Wed Apr 02 17:22:10 2008
kernel runs with dp version 234(ext=109) (@(#) DPLIB-INT-VERSION-234)
length of sys_adm_ext is 364 bytes
SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (01 5348) [dpxxdisp.c   1245]
     shared lib "dw_xml.dll" version 150 successfully loaded
     shared lib "dw_xtc.dll" version 150 successfully loaded
     shared lib "dw_stl.dll" version 150 successfully loaded
     shared lib "dw_gui.dll" version 150 successfully loaded
     shared lib "dw_mdm.dll" version 150 successfully loaded
rdisp/softcancel_sequence : -> 0,5,-1
Wed Apr 02 17:22:22 2008
WARNING => DpNetCheck: NiHostToAddr(www.doesnotexist0100.qqq.nxst) took 12 seconds
Wed Apr 02 17:22:40 2008
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 18 seconds
***LOG GZZ=> 2 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5373]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: start server >HOSTNAME_SID_01                      <
DpShMCreate: sizeof(wp_adm)          22968     (1044)
DpShMCreate: sizeof(tm_adm)          3642120     (18120)
DpShMCreate: sizeof(wp_ca_adm)          18000     (60)
DpShMCreate: sizeof(appc_ca_adm)     6000     (60)
DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528040/528048
DpShMCreate: sizeof(comm_adm)          528048     (1048)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm)          0     (96)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm)          0     (72)
DpShMCreate: sizeof(vmc_adm)          0     (1296)
DpShMCreate: sizeof(wall_adm)          (22440/34344/56/100)
DpShMCreate: sizeof(gw_adm)     48
DpShMCreate: SHM_DP_ADM_KEY          (addr: 05560040, size: 4281040)
DpShMCreate: allocated sys_adm at 05560040
DpShMCreate: allocated wp_adm at 05561B30
DpShMCreate: allocated tm_adm_list at 055674E8
DpShMCreate: allocated tm_adm at 05567518
DpShMCreate: allocated wp_ca_adm at 058E0820
DpShMCreate: allocated appc_ca_adm at 058E4E70
DpShMCreate: allocated comm_adm at 058E65E0
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 05967490
DpShMCreate: allocated gw_adm at 059674D0
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 05967500
DpShMCreate: allocated wall_adm at 05967508
MBUF state OFF
DpCommInitTable: init table for 500 entries
ThTaskStatus: rdisp/reset_online_during_debug 0
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 1024 kByte.
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
<ES> 2039 blocks reserved for free list.
ES initialized.
WARNING => System running without ICM - check rdisp/start_icman [dpxxdisp.c   12553]
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG Q0K=> DpMsAttach, mscon ( HOSTNAME) [dpxxdisp.c   11867]
DpStartStopMsg: send start message (myname is >HOSTNAME_SID_01                      <)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: Initalizing shared memory of size 40000000 for monitoring segment.
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1050]
DpMsgAdmin: Set patchno for this platform to 150
Release check o.K.
Wed Apr 02 17:23:20 2008
my types changed after wp death/restart 0x1f --> 0x1e
my types changed after wp death/restart 0x1e --> 0x1c
my types changed after wp death/restart 0x1c --> 0x18
my types changed after wp death/restart 0x18 --> 0x10
my types changed after wp death/restart 0x10 --> 0x0
DP_FATAL_ERROR => DpWPCheck: no more work processes
DISPATCHER EMERGENCY SHUTDOWN ***
increase tracelevel of WPs
NiWait: sleep (10000ms) ...
NiISelect: timeout 10000ms
NiISelect: maximum fd=1477
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Wed Apr 02 17:23:30 2008
NiISelect: TIMEOUT occured (10000ms)
dump system status
Workprocess Table (long)               Wed Apr 02 11:53:30 2008
========================
No Ty. Pid      Status Cause Start Err Sem CPU    Time Program          Cl User         Action                    Table
0 DIA     6916 Ended         no      1   0        0
1 DIA     7724 Ended         no      1   0        0
2 DIA     6044 Ended         no      1   0        0
3 DIA     4300 Ended         no      1   0        0
4 DIA     6992 Ended         no      1   0        0
5 DIA     2412 Ended         no      1   0        0
6 DIA      432 Ended         no      1   0        0
7 DIA     8168 Ended         no      1   0        0
8 DIA     5420 Ended         no      1   0        0
9 DIA     9712 Ended         no      1   0        0
10 UPD     4320 Ended         no      1   0        0
11 ENQ     3476 Ended         no      1   0        0
12 BTC     2676 Ended         no      1   0        0
13 BTC     6816 Ended         no      1   0        0
14 BTC     9636 Ended         no      1   0        0
15 BTC     8356 Ended         no      1   0        0
16 BTC     7004 Ended         no      1   0        0
17 BTC     7284 Ended         no      1   0        0
18 BTC    10048 Ended         no      1   0        0
19 BTC     4560 Ended         no      1   0        0
20 BTC     4196 Ended         no      1   0        0
21 SPO     4268 Ended         no      1   0        0
Dispatcher Queue Statistics               Wed Apr 02 11:53:30 2008
===========================
--------++++--
+
Typ
now
high
max
writes
reads
--------++++--
+
NOWP
0
1
2000
1
1
--------++++--
+
DIA
3
3
2000
3
0
--------++++--
+
UPD
0
0
2000
0
0
--------++++--
+
ENQ
0
0
2000
0
0
--------++++--
+
BTC
0
0
2000
0
0
--------++++--
+
SPO
0
0
2000
0
0
--------++++--
+
UP2
0
0
2000
0
0
--------++++--
+
max_rq_id          7
wake_evt_udp_now     0
wake events           total     3, udp     3 (100%), shm     0 ( 0%)
since last update     total     3, udp     3 (100%), shm     0 ( 0%)
Dump of tm_adm structure:               Wed Apr 02 11:53:30 2008
=========================
Term    uid man user    term   lastop mod wp ta   a/i (modes)
Workprocess Comm. Area Blocks               Wed Apr 02 11:53:30 2008
=============================
Slots: 300, Used: 1, Max: 0
--------++--
+
id
owner
pid
eyecatcher
--------++--
+
0
DISPATCHER
-1
WPCAAD000
NiWait: sleep (5000ms) ...
NiISelect: timeout 5000ms
NiISelect: maximum fd=1477
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Wed Apr 02 17:23:35 2008
NiISelect: TIMEOUT occured (5000ms)
DpHalt: shutdown server >HOSTNAME_SID_01                      < (normal)
DpJ2eeDisableRestart
DpModState: buffer in state MBUF_PREPARED
NiBufSend starting
NiIWrite: hdl 2 sent data (wrt=110,pac=1,MESG_IO)
MsINiWrite: sent 110 bytes
MsIModState: change state to SHUTDOWN
DpModState: change server state from STARTING to SHUTDOWN
Switch off Shared memory profiling
ShmProtect( 57, 3 )
ShmProtect(SHM_PROFILE, SHM_PROT_RW
ShmProtect( 57, 1 )
ShmProtect(SHM_PROFILE, SHM_PROT_RD
DpWakeUpWps: wake up all wp's
Stop work processes
Stop gateway
killing process (1860) (SOFT_KILL)
Terminate gui connections
wait for end of work processes
wait for end of gateway
[DpProcDied] Process lives (PID:1860 HANDLE:1448)
waiting for termination of gateway ...
NiWait: sleep (1000ms) ...
NiISelect: timeout 1000ms
NiISelect: maximum fd=1477
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Wed Apr 02 17:23:36 2008
NiISelect: TIMEOUT occured (1000ms)
[DpProcDied] Process died (PID:1860 HANDLE:1448)
DpStartStopMsg: send stop message (myname is >HOSTNAME_SID_01                      <)
NiIMyHostName: hostname = 'HOSTNAME'
AdGetSelfIdentRecord: >                                                                           <
AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 4 (AD_STARTSTOP), ser 0, ex 0, errno 0
DpConvertRequest: net size = 189 bytes
NiBufSend starting
NiIWrite: hdl 2 sent data (wrt=562,pac=1,MESG_IO)
MsINiWrite: sent 562 bytes
send msg (len 110+452) to name                    -, type 4, key -
DpStartStopMsg: stop msg sent
NiIRead: hdl 2 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 2
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER          , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 2 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 2
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER          , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 2 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 2
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER          , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 2 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 2
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER          , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 2 received data (rcd=274,pac=1,MESG_IO)
NiBufIIn: NIBUF len=274
NiBufIIn: packet complete for hdl 2
NiBufReceive starting
MsINiRead: received 274 bytes
MSG received, len 110+164, flag 1, from MSG_SERVER          , typ 0, key -
DpHalt: received 164 bytes from message server
NiIRead: hdl 2 recv would block (errno=EAGAIN)
NiIRead: read for hdl 2 timed out (0ms)
DpHalt: no more messages from the message server
DpHalt: send keepalive to synchronize with the message server
NiBufSend starting
NiIWrite: hdl 2 sent data (wrt=114,pac=1,MESG_IO)
MsINiWrite: sent 114 bytes
send msg (len 110+4) to name           MSG_SERVER, type 0, key -
MsSndName: MS_NOOP ok
Send 4 bytes to MSG_SERVER
NiIRead: hdl 2 recv would block (errno=EAGAIN)
NiIPeek: peek successful for hdl 2 (r)
NiIRead: hdl 2 received data (rcd=114,pac=1,MESG_IO)
NiBufIIn: NIBUF len=114
NiBufIIn: packet complete for hdl 2
NiBufReceive starting
MsINiRead: received 114 bytes
MSG received, len 110+4, flag 3, from MSG_SERVER          , typ 0, key -
Received 4 bytes from MSG_SERVER
Received opcode MS_NOOP from msg_server, reply MSOP_OK
MsOpReceive: ok
MsSendKeepalive : keepalive sent to message server
NiIRead: hdl 2 recv would block (errno=EAGAIN)
Wed Apr 02 17:23:37 2008
NiIPeek: peek for hdl 2 timed out (r; 1000ms)
NiIRead: read for hdl 2 timed out (1000ms)
DpHalt: no more messages from the message server
DpHalt: sync with message server o.k.
detach from message server
***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c   12213]
NiBufSend starting
NiIWrite: hdl 2 sent data (wrt=110,pac=1,MESG_IO)
MsINiWrite: sent 110 bytes
MsIDetach: send logout to msg_server
MsIDetach: call exit function
DpMsShutdownHook called
NiBufISelUpdate: new MODE -- (r-) for hdl 2 in set0
SiSelNSet: set events of sock 1356 to: ---
NiBufISelRemove: remove hdl 2 from set0
SiSelNRemove: removed sock 1356 (pos=2)
SiSelNRemove: removed sock 1356
NiSelIRemove: removed hdl 2
MBUF state OFF
AdGetSelfIdentRecord: >                                                                           <
AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
blks_in_queue/wp_ca_blk_no/wp_max_no = 1/300/22
LOCK WP ca_blk 1
make DISP owner of wp_ca_blk 1
DpRqPutIntoQueue: put request into queue (reqtype 1, prio LOW, rq_id 9)
MBUF component DOWN
NiICloseHandle: shutdown and close hdl 2 / sock 1356
NiBufIClose: clear extension for hdl 2
MsIDetach: detach MS-system
cleanup EM
EsCleanup ....
EmCleanup() -> 0
Es2Cleanup: Cleanup ES2
***LOG Q05=> DpHalt, DPStop ( 5348) [dpxxdisp.c   10461]
Good Bye .....
Please help me in resolving this issue
Thanks,
Vadi

Hi Suhas,
Have checked the hostname and it is correct.
I am getting the below output When i run r3trans -x
This is r3trans version 6.14 (release 700 - 04.03.08 - 16:43:00).
r3trans finished (0000).
I could see the below error message in dev_W21
ExecuteAndFlush return code: 0x80040e14 Stmt: [if user_name() != 'sid_shd' setuser 'sid_shd']
C sloledb.cpp [ExecuteAndFlush,line 6470]: Error/Message: (err 15157, sev 0), Setuser failed because of one of the following reasons: the database principal 'cdu_shd' does not exist, its corresponding server principal does not have server access, this type of database principal cannot be impersonated, or you do not have permission.
C Procname: [ExecuteAndFlush - no proc]
C setuser 'cdu_shd' failed -- connect terminated
C failed to establish conn. 0
Thanks,
Vadi

SAP ERP 6.0 EHP4 upgrade from SAP R/3 4.7 1.10

Dear Experts,
Our client is going to upgrade current landscape SAP R/3 4.7 1.10 to ERP 6.0 EHP4. The Source system O/s is AIX 5.3 and database is db2 8.1. Client procuring new hardware for the target release ERP 6.0 landscape and the O/s is going to be AIX 7.1 and databse would be db2 9.7 FP3.
As part of the upgrade we are going to do initial upgrade in the mock server and vendor is going to provide mock server with AIX 7.1 O/S. Current database size is 100GB, hence we are going to copy the production server data into the mock server using export and import method,
Here my doubt is can i install db9.7 directly and do the import (using compitable kernel)?, insteady of installing source database version 8.1 and later upgrading to db2 9.7 . Please clarify me whether can i go head and install the db2 9.7 and do the system copy using R3load.
Thanks and Regards,
Seshu

Seshu Mannepalli wrote:
> As part of the upgrade we are going to do initial upgrade in the mock server and vendor is going to provide mock server with AIX 7.1 O/S. Current database size is 100GB, hence we are going to copy the production server data into the mock server using export and import method,
>
> Here my doubt is can i install db9.7 directly and do the import (using compitable kernel)?, insteady of installing source database version 8.1 and later upgrading to db2 9.7 . Please clarify me whether can i go head and install the db2 9.7 and do the system copy using R3load.
Hello,
You can go ahead for IMPORT with DB 9.7.
We completed an OS/DB Migration Project (which involves system copy using EXPORT/IMPORT) and we utilized direct newer version of DB2 on the target during IMPORT.
But please confirm whether the kernel of your release would work fine with DB 9.7 or not. Otherwise, there is no problem in going for higher version of DB2 here.
Small question - Why you want to test the Mock Upgrade on DB2 version which is different than the current version on production server ? Or are you planning to upgrade your current DB2 8 to DB2 9.7 BEFORE the SAP Upgrade on all the servers - then the testing is OK I think (however OS is still the different - Or may be you will go for system copies for this too !)
Thanks

Put Together A Data Archiving Strategy And Execute It Before Embarking On Sap Upgrade

A significant amount is invested by organizations in a SAP upgrade project. However few really know that data archiving before embarking on SAP upgrade yields significant benefits not only from a cost standpoint but also due to reduction in complexity during an upgrade. This article not only describes why this is a best practice but also details what benefits accrue to organizations as a result of data archiving before SAP upgrade. Avaali is a specialist in the area of Enterprise Information Management. Our consultants come with significant global experience implementing projects for the worlds largest corporations.
Archiving before Upgrade
It is recommended to undertake archiving before upgrading your SAP system in order to reduce the volume of transaction data that is migrated to the new system. This results in shorter upgrade projects and therefore less upgrade effort and costs. More importantly production downtime and the risks associated with the upgrade will be significantly reduced. Storage cost is another important consideration: database size typically increases by 5% to 10% with each new SAP software release – and by as much as 30% if a Unicode conversion is required. Archiving reduces the overall database size, so typically no additional storage costs are incurred when upgrading.
It is also important to ensure that data in the SAP system is cleaned before your embark on an upgrade. Most organizations tend to accumulate messy and unwanted data such as old material codes, technical data and subsequent posting data. Cleaning your data beforehand smoothens the upgrade process, ensure you only have what you need in the new version and helps reduce project duration. Consider archiving or even purging if needed to achieve this. Make full use of the upgrade and enjoy a new, more powerful and leaner system with enhanced functionality that can take your business to the next level.
Archiving also yields Long-term Cost Savings
By implementing SAP Data Archiving before your upgrade project you will also put in place a long term Archiving Strategy and Policy that will help you generate on-going cost savings for your organization. In addition to moving data from the production SAP database to less costly storage devices, archived data is also compressed by a factor of five relative to the space it would take up in the production database. Compression dramatically reduces space consumption on the archive storage media and based on average customer experience, can reduce hardware requirements by as much as 80% or 90%. In addition, backup time, administration time and associated costs are cut in half. Storing data on less costly long-term storage media reduces total cost of ownership while providing users with full, transparent access to archived information.

Maybe this article can help; it uses XML for structural change flexiblity: http://www.oracle.com/technetwork/oramag/2006/06-jul/o46xml-097640.html

Work process dies during an Upgrade in Shadow Instance

Hi all,
Systemconfiguration: Windows 2003 Server SP2 - Oracle 10.2.0.2
during the Upgrade PHASE SET "SETSYNC_EULCK_START_D1 after STARTSAP_IMP nothing more happends on the system. No errors in den SAPup.log etc.
The reason:
I can`t start the shadow Instance. During the start process in mmc the dispatcher + work process died...
Has anyone an Idea....there are som
Here is the dev_w0 logfile:
It might be great if anyone can help me!!!
The errors in a row:
1 - C     SQL error 942: 'ORA-00942: table or view does not exist'
B ***LOG BZA=> table SVERS      does not exist on database            [dblink#5 @ 1299] [dblink 1299 ]
2 -
C *** ERROR => ORA-1403 when accessing table SAPUSER
[dbsloci.c    11535]
C OCI-call failed with -1=OCI_ERROR
C     SQL error 942: 'ORA-00942: table or view does not exist'
3 -
B ***LOG BZA=> table SVERS      does not exist on database            [dblink#5 @ 1299] [dblink 1299 ]
M ***LOG R19=> ThInit, db_connect ( DB-Connect 004096) [thxxhead.c   1440]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   10504
trc file: "dev_w0", trc level: 1, release: "700"
ACTIVE TRACE LEVEL           1
ACTIVE TRACE COMPONENTS      all, MJ
B
B Sat Jun 07 12:29:47 2008
B create_con (con_name=R/3)
B Loading DB library 'E:\usr\sap\put\exe\dboraslib.dll' ...
B Library 'E:\usr\sap\put\exe\dboraslib.dll' loaded
B Version of 'E:\usr\sap\put\exe\dboraslib.dll' is "700.08", patchlevel (0.152)
B New connection 0 created
M sysno      50
M sid        CDP
M systemid   562 (PC with Windows NT)
M relno      7000
M patchlevel 0
M patchno    155
M intno      20050900
M make:      multithreaded, Unicode, 64 bit, optimized
M pid        3656
M
M kernel runs with dp version 235000(ext=110000) (@(#) DPLIB-INT-VERSION-235000-UC)
M length of sys_adm_ext is 576 bytes
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 3656) [dpxxdisp.c   1312]
I
I Sat Jun 07 12:29:49 2008
I MtxInit: 30000 0 0
M DpSysAdmExtCreate: ABAP is active
M DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
M DpShMCreate: sizeof(wp_adm)          12928     (1616)
M DpShMCreate: sizeof(tm_adm)          5652128     (28120)
M DpShMCreate: sizeof(wp_ca_adm)          24000     (80)
M DpShMCreate: sizeof(appc_ca_adm)     8000     (80)
M DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552064/552080
M DpShMCreate: sizeof(comm_adm)          552080     (1088)
M DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
M DpShMCreate: sizeof(slock_adm)          0     (104)
M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
M DpShMCreate: sizeof(file_adm)          0     (72)
M DpShMCreate: sizeof(vmc_adm)          0     (1864)
M DpShMCreate: sizeof(wall_adm)          (41664/36752/64/192)
M DpShMCreate: sizeof(gw_adm)     48
M DpShMCreate: SHM_DP_ADM_KEY          (addr: 0000000010A80050, size: 6336352)
M DpShMCreate: allocated sys_adm at 0000000010A80050
M DpShMCreate: allocated wp_adm at 0000000010A82150
M DpShMCreate: allocated tm_adm_list at 0000000010A853D0
M DpShMCreate: allocated tm_adm at 0000000010A85430
M DpShMCreate: allocated wp_ca_adm at 0000000010FE92D0
M DpShMCreate: allocated appc_ca_adm at 0000000010FEF090
M DpShMCreate: allocated comm_adm at 0000000010FF0FD0
M DpShMCreate: system runs without slock table
M DpShMCreate: system runs without file table
M DpShMCreate: allocated vmc_adm_list at 0000000011077C60
M DpShMCreate: allocated gw_adm at 0000000011077CE0
M DpShMCreate: system runs without vmc_adm
M DpShMCreate: allocated ca_info at 0000000011077D10
M DpShMCreate: allocated wall_adm at 0000000011077D20
M rdisp/queue_size_check_value : -> off
M ThTaskStatus: rdisp/reset_online_during_debug 0
X EmInit: MmSetImplementation( 2 ).
X MM global diagnostic options set: 0
X <ES> client 0 initializing ....
X Using implementation view
X <EsNT> Using memory model view.
M <EsNT> Memory Reset disabled as NT default
X ES initialized.
M
M Sat Jun 07 12:29:50 2008
M ThInit: running on host drfeelgood
M
M Sat Jun 07 12:29:51 2008
M calling db_connect ...
C CLIENT_ORACLE_HOME is not set as environment variable or
C DIR_CLIENT_ORAHOME is not set as profile parameter.
C    assuming using instant client with unspecified location.
C
C Sat Jun 07 12:29:53 2008
C Oracle Client Version: '10.2.0.1.0'
C
C Sat Jun 07 12:29:55 2008
C Client NLS settings: AMERICAN_AMERICA.UTF8
C Logon as OPS$-user to get SAPSR3SHD's password
C Connecting as /@CDP on connection 0 (nls_hdl 0) ... (dbsl 700 130308)
C Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
C    0 UTF8                                                      1 00000000138A2020 000000000A91EC10 00000000138C59C8
C Attaching to DB Server CDP (con_hdl=0,svchp=00000000138C5888,srvhp=00000000138C7CB8)
C
C Sat Jun 07 12:30:20 2008
C Starting user session (con_hdl=0,svchp=00000000138C5888,srvhp=00000000138C7CB8,usrhp=000000000A91F428)
C
C Sat Jun 07 12:30:26 2008
C Now '/@CDP' is connected: con_hdl=0, nls_hdl=0, session_id=55.
C *** ERROR => ORA-1403 when accessing table SAPUSER
[dbsloci.c    11535]
C Disconnecting from connection 0 ...
C Closing user session (con_hdl=0,svchp=00000000138C5888,usrhp=000000000A91F428)
C Now I'm disconnected from ORACLE
C Try to connect with default password
C Connecting as SAPSR3SHD/<pwd>@CDP on connection 0 (nls_hdl 0) ... (dbsl 700 130308)
C Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
C    0 UTF8                                                      1 00000000138A2020 000000000A91EC10 00000000138C59C8
C Starting user session (con_hdl=0,svchp=00000000138C5888,srvhp=00000000138C7CB8,usrhp=000000000A91F428)
C
C Sat Jun 07 12:30:27 2008
C Now 'SAPSR3SHD/<pwd>@CDP' is connected: con_hdl=0, nls_hdl=0, session_id=52.
C Database NLS settings: AMERICAN_AMERICA.UTF8
C DB instance CDP is running on DRFEELGOOD with ORACLE version 10.2.0.2.0 since JUN 07, 2008, 00:35:17
B Connection 0 opened (DBSL handle 0)
B Wp Hdl ConName          ConId     ConState     TX PRM RCT TIM MAX OPT Date     Time   DBHost
B 000 000 R/3              000000000 ACTIVE       NO YES NO 000 255 255 20080607 122951 DRFEELGOOD
C build_stmt: reallocating stmt buffer: 256 -> 2000 characters
C
C Sat Jun 07 12:30:30 2008
C OCI-call failed with -1=OCI_ERROR
C     SQL error 942: 'ORA-00942: table or view does not exist'
B ***LOG BZA=> table SVERS      does not exist on database            [dblink#5 @ 1299] [dblink 1299 ]
M ***LOG R19=> ThInit, db_connect ( DB-Connect 004096) [thxxhead.c   1440]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   10504]
M
M Info for wp 0
M
M    pid = 3656
M    severity = 0
M    status = 0
M    stat = WP_RUN
M    waiting_for = NO_WAITING
M    reqtype = DP_RQ_DIAWP
M    act_reqtype = NO_REQTYPE
M    rq_info = 0
M    tid = -1
M    mode = 255
M    len = -1
M    rq_id = 65535
M    rq_source =
M    last_tid = 0
M    last_mode = 0
M    semaphore = 0
M    act_cs_count = 0
M    csTrack = 0
M    csTrackRwExcl = 0
M    csTrackRwShrd = 0
M    mode_cleaned_counter = 0
M    control_flag = 0
M    int_checked_resource(RFC) = 0
M    ext_checked_resource(RFC) = 0
M    int_checked_resource(HTTP) = 0
M    ext_checked_resource(HTTP) = 0
M    report = >                                        <
M    action = 0
M    tab_name = >                              <
M    attachedVm = no VM
M
M *****************************************************************************
M *
M * LOCATION    SAP-Server drfeelgood_CDP_50 on host drfeelgood (wp 0)
M * ERROR       ThInit: db_connect
M *
M * TIME        Sat Jun 07 12:30:30 2008
M * RELEASE     700
M * COMPONENT   Taskhandler
M * VERSION     1
M * RC          13
M * MODULE      thxxhead.c
M * LINE        10724
M * COUNTER     1
M *
M *****************************************************************************
M
M PfStatDisconnect: disconnect statistics
M Entering TH_CALLHOOKS
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   724]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 261]
M Entering ThSetStatError
M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M Entering ThReadDetachMode
M
M Sat Jun 07 12:30:31 2008
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workproc 0 3656) [dpnttool.c   333]

Hi Markus,
thks for your advise. I already updated the Oracle Client to version 10.2.0.2.
The upgrade from CRM 5.0 to CRM 6.0 - 2007 is still running, but theres nothing happens in PHASE SETSYNC_EULCK_D1. This Phase comes after the EU_Imports 1-7.
In the log directory there ist also nothing the indicates about errors.
Here is the last SAPUp.log entries
************************* SAPup started in UPGRADE mode *************************
This is SAPup version 7.00/2 patch level 24.103.
This is UNICODE SAPup!
Reading Parameter File "E:\usr\sap\put\bin\DBSYNC.PAR" at 20080607162600
Condition level 1, total => TRUE '#if ( "ORA" == "ORA" )' => TRUE
Reading Parameter File "E:\usr\sap\put\bin\R3CURENV.LST" at 20080607162600
...begin dialogue at 20080607162603
...end dialogue at 20080607162607
...STARTED at 20080607162607.
Reading Parameter File "E:\usr\sap\put\bin\TRATTR.LST" at 20080607162607
Reading Parameter File "E:\usr\sap\put\bin\TRGROUP.LST" at 20080607162607
Reading Parameter File "E:\usr\sap\put\bin\R3CURENV.LST" at 20080607162607
Reading Parameter File "E:\usr\sap\put\bin\DBSWTC.PAR" at 20080607162607
Condition level 1, total => FALSE '#if "ORACLE" == "SAPDB"' => FALSE
Condition level 1, total => FALSE '#elseif "ORACLE" == "DB2-z/OS"' => FALSE
Condition level 1, total => FALSE '#elseif "ORACLE" == "DB2/400"' => FALSE
Condition level 1, total => FALSE '#elseif "ORACLE" == "DB6"' => FALSE
Condition level 1, total => FALSE '#elseif "ORACLE" == "INFORMIX"' => FALSE
Condition level 1, total => FALSE '#elseif "ORACLE" == "MSSQL"' => FALSE
Condition level 1, total => TRUE '#elseif "ORACLE" == "ORACLE"' => TRUE
Condition level 1, total => FALSE '#if "Windows NT X86_64" ~= "Linux"' => FALSE
Condition level 1, total => FALSE '#elseif "Windows NT X86_64" ~= "Windows NT INTEL"' => FALSE
Condition level 1, total => FALSE '#elseif "Windows NT X86_64" ~= "Windows NT IA64"' => FALSE
Condition level 1, total => TRUE '#elseif "Windows NT X86_64" ~= "Windows NT X86_64"' => TRUE
...begin dialogue at 20080607162610
...end dialogue at 20080607162615
...begin dialogue at 20080607162615
...end dialogue at 20080607162637
UPGRADEPHASE SETSYNC_EULCK_START_D1
...started at 20080607162637
Setting syncpoint EU_LOCKED=STARTED in E:\usr\sap\put\mig\SYNC.DAT
At the usr sap put tmp directory, that shows the current activitiy of the upgrade, there also nothing happens.
if i have to start the shadow instance in the mmc manually at this time of the upgrade phase....at this time it doesnt work, but i dont find anything in the upgrade documentation.
Cheers Mario

Load_systab ERR_EXECUTE during MAXDB upgrade

Hello,
I performed MAXDB upgrade from 7.7.04.028 to 7.8.01.014.
During the upgrade I received the following message:
load_systab
-24964,ERR_EXECUTE: error in program execution
768,/sapdb/EFL/db/bin/sdbsysload -R /sapdb/EFL/db -d EFL -u superdba,*
Installing tables for instances
----------Command----------------
DROP PACKAGE SYS_DDL_PACKAGE
-----------Error-----------------
Unexpected error -9205
But I could see that the version was updated and I could start the system. So I applied the patch to upgrade to 7.8.02.024.
If I execute load_systab from dbmcli, I still get the same message, and in Database Studio -> Diagnosis files-> Database error, the following entry appear:
620: Thread      0xE91 Task    570 2011-09-08 15:59:52 ERR SYSERROR   51080: AK Catalog information not found:ãu20ACu20ACãu20ACu20ACãu20ACu20ACãu20ACu20ACãu20ACu20ACãu20ACu20ACãu20ACu20AC
Could you please help me, and tell me how this affects my system?
Thank you in advance

Hello,
1. Are you SAP customer?
    Did you download 7.8.02.024 version?
    7.8.02.024. is not released for free download at www.sdn.sap.com/irj/scn/maxdb-downloads
   MAXDB 7.8.02.25 Server Package released for SAP customers.
2. If you are SAP customer => Did you create the SAP message where this issue was reported?
Regards, Natalia Khlopina

Unable to upgrade the SAP Basis 701

Hi Experts
I am planning to Upgrade Solman 7.0 to Solman 7.0 Ehp1, for that i need to upgrade my basis support pack from 700 to 701.
I have downloaded the SAP_BASIS 701 SAPK-701DHINSAPBASIS support pack from service market place. When i try to update this using saint i am getting a error saying "OCS package SAPK-701DHINSAPBASIS does not match the current software component vector" and showing the "
BBPCRM,* Component BBPCRM,* must not be installed "
When i check the prequest
Main Components
Component Release Value
BBPCRM         *         F
SAP_BASIS 700        T
Already i have installed BBPCRM,
BBPCRM     500     0011     SAPKU50011     BBPCRM     BBP/CRM Supp. Pack.
Please help resolve this issue
Thanks & Regards

Hi, you can use this roadmap I've made for upgrading to EHP1 from SP17 or lower. Please remark that its a prerquisite that Your java stack is on SP17 (solman SP17 = NW Java sps16). Also, You should include SP04/SP20 for Solman while upgrading via SAINT (ABAp Wise) and JSPM (JAVA wise).
BR Kurt
*Pre upgrade 1 *
Make a complete offline backup of Your whole system (DB + files)
Pre upgrade 2
release workbench/customizing request:
Pre upgrade 3
Lock all users exept from system users and exclusive users
- In TC=su10 click on "Authorization data"
- Scroll down and in "Additional selection criteria" check the "Locked users only" box
- Click on "Execute" (F8)
- Make at note of the locked users
- Go one step back, and click on "Authorization data" once again
- Scroll down and in "Additional selection criteria" check the "Unlocked users only" box
- Click on "Execute" (F8)
- Select all users by clicking the green icon in upper left corner
- Deselect the system users and own user:
- Click on "Transfer" in upper left corner
- Click on "Lock" icon
Pre upgrade 4
Check system (transport tool, ST22, SM21, SM13, SM50)
- In STMS run the check TP tool
- Look for ABAP dump in ST22
- Look for errors in SM21
- Look for update errors in SM13
Pre upgrade 5
- Extending datafiles/tablespace in database manually if needed
Pre upgrade 6
Setting all jobs to scheduled during the upgrade phase
In productive client , tc=SE38, run the program "BTCTRNS1".
This will take all currently Scheduled and Released jobs and move them into a "special" status
Upgrade part 1
Upgrade the Java stack + kernel to Solution Manager SPS17 (NW sps16) if not already upgraded.
- Logon to with OS user <sapsid>adm
- Open JSPM by db.clicking the go.bat file in the directory:
usr\sap\<SAPSID>\DVEBMGS<instance>\j2ee\JSPM
- Logon to JSPM (SDM) using the same password as J2EE_ADMIN
- Choose "deploy SPS stack"
- Follow the guidelines from JSPM
Remark:
First the JSPM application is updated, which requires restart of the JSPM
second: The kernel files is updated, which requires restart of the SAP system
Third: all other Java packages is deployed, which requires restart of the Java Engine cluster a couple of times during that phase - all controlled by the JSPM application + manual interaction via the Cluster administrator (stop/start of clusterressources).
During use of JSPM, refer to Note 891983 - JSPM: Central SAP Note SAP NetWeaver 2004s AS Java regarding troubleshooting if needed
Upgrade part 2
Upgrade SPAM to latest version 03x
- Login to client 000 with user (SAP_ALL, SAP_NEW) u2013 not SAP* and DDIC
- tc=SPAM
- Choose "Support Package", "Load packages", "from application server"
- Choose "Support package", "Import SPAM/SAINT_Update" and follow the guidelines
- Confirm after deploying the supportpackage
Upgrade part 3
Upgrade product definitions in Solution manager according to note 1169247
- tc=SE30
- Run the report: RS_SMSY_PPMS_XML_UP_DOWNLOAD
- Set checkmark with an uppercase "X" in option field: "Upload"
- Point to the downloaded .XML file
- Click "ok"
Upgrade part 4
Adding .DLL files to support NW7.01 use of Visual Studio 2005 Compiler According to note 684106
- on SAP servers execute downloaded vcredist_x64.exe file from directory:
- on SAP servers copy file: dbghelp.dll. to the directories:C:
windows\system32 and C:
windows\syswow64 on all SAP servers
Note, check before copying dbghelp.dll whether the relevant file exists in the directories \windows\system32 and \windows\syswow64, and replace the file only if the version that is made available here is more current than the version that is already available. You can use the Windows Explorer to determine the file version (right-click and choose "Properties -> Version").
Upgrade part 5
Upgrade to SAP kernel 7.01, kernel 55
- Logon to the SAP server
- Stop SAP instances via the MMC console
- Navigate to Kernel directory:
usr\sapmnt\<SAPSID>\SYS\exe\uc
- Make a copy of current kernel by copying the folder: NTAMD64
- Copy new kernelfiles (701_55 into the directory: :
usr\sapmnt\<SAPSID>\SYS\exe\uc \NTADM64
- Click "yes", when prompted to overwrite existing files
- Go to SAP MMC console and start the SAP system again
- make sure all instances goes into "green" status in SAP MMC console
- tc=Session_Manager, choose "system", "Status", press "Shift+F5" to show the kernel info
Upgrade part 2
Upgrade the ABAP stack to Solution Manager SPS20/EHP1 including supportpackages
- tc=SAINT
- Choose "Extras" --> "Settings" --> "Import queue" tab
- define 5 parallel R3trans processes
- click "Confirm" (green checkmark)
- Call transaction SAINT and choose "Start" and "Load".
- Choose the right pushbutton to load the stack configuration (SW-Center Stack-XML).
- Alternatively,the SAINT queue can be buildt manually.
Select the following components and choose "Continue".
PI_BASIS 701
SAP_ABA 701
SAP_BASIS 701
SAP_BW 701
BI_CONT 704
CRMUIF 500
ST-A/PI 01L_CRM570
ST-PI 2008_1_700
ST-SER 701_2008_2
If all necessary conditions for importing the add-ons are met,
the system will display the relevant queue. The queue consists
of installation packages, upgrade packages, Support Packages
and Conflict Resolution Transports (CRTs).
- To start the installation process, choose "Continue".
- The system prompts you to enter a password. This password is
provided below:
Before the installation, you will be asked to enter a password for
each component you selected. This password is (in bold):
Component      Package name                Password
CRMUIF 500        SAPK-500AGINCRMUIF      D855FD497D
PI_BASIS 701      SAPK-701DHINPIBASIS     3DD62AEC78
SAP_ABA 701    SAPK-701DHINSAPABA    3DC721976A
SAP_BASIS 701 SAPK-701DHINSAPBASIS 3EC433FE19
SAP_BW 701      SAPK-701DHINSAPBW       3ED240976A
BI_CONT 704       SAPK-704DHINBICONT       14158187D7
BI_CONT 704       SAPK-704IHINBICONT        1415818AD7
Upgrade part 6
Implement notes after upgrade
- login to productive client
- tc=SNOTE
- Press "Download SAP Note" (CTRL+F8).
- Type notenumbers: 1250122, 1270420, 1256049, 1243425, 1236420 and 1269582 and press "Copy" (F8) and "Execute" (F8).
- Mark notenumber: 1250122 and press "Implement SAP Note" (CTRL+F1). REMARK: this note should be implemented in pair with note: 1270420.
- Mark notenumber: 1256049 and press "Implement SAP Note" (CTRL+F1). REMARK: this note should be implemented in pair with note: 1243425.
- Mark note 1236420 and press "Implement SAP Note" (CTRL+F1).
- Mark note 1269582 and press "Implement SAP Note" (CTRL+F1).
Upgrade part 7
Increase EventTimeout to avoid deployment errors in Java stack for SPS20/EHP1
- Log on to Server
- Open config Tool by clicking: config.bat in the directory:
- In the navigation area choose: Cluster-data --> Global server configuration --> Managers --> ServiceManager
- in the Global properties panel, set the Custom value of the EventTimeout property to 120
- choose "Save"
- Restart the Central Instance
Upgrade part 8
Upgrade the Java stack to Solution Manager SPS20/EHP1 including supportpackages
- Logon to SAP server
- Open JSPM by db.clicking the go.bat file in the directory:
usr\sap\<SAPSID>\DVEBMGS<instance>\j2ee\JSPM
- Logon to JSPM (SDM) using the same password as J2EE_ADMIN
- Choose "deploy SPS stack"
- Follow the guidelines from JSPM
Remark:
First the JSPM application is updated, which requires restart of the JSPM
Second: all other Java packages is deployed, which requires restart of the Java Engine cluster a couple of times during that phase - all controlled by the JSPM application + manual interaction via the Cluster administrator (stop/start of clusterressources).
During use of JSPM, refer to Note 891983 - JSPM: Central SAP Note SAP NetWeaver 2004s AS Java regarding troubleshooting if needed
Upgrade part 9
Update LM-SERVICE.SCA and LM-TOOLS.SCA to latest patch level
- Logon to SAP server
- Open JSPM by db.clicking the go.bat file in the directory:
usr\sap\<SAPSID>\DVEBMGS<instance>\j2ee\JSPM
- Logon to JSPM (SDM) using the same password as J2EE_ADMIN
- Copy the files to directory:
usr\sap\trans\EPS\in
- Choose "deploy single package"
- Follow the guidelines from JSPM
Post upgrade 1
Temporarely adjust the time out values for the HTTP service
- login to the productive client
- tc=SMICM
- navigate in the menu to GOTO -> SERVICES
- Set the checkmark for HTTP
- navigate in the menu to SERVICE -> CHANGE
- set the time out values for "Keep Alive" and "Max. Processing Time" to about 6000
Post upgrade 2
Restoring all jobs to the status before the upgrade phase
- In productive client, tc=SE38, run the program "BTCTRNS2".
This will restore all jobs to their previous status
Post upgrade 3
- Logon to productive client via SAPGUI
- TC= SOLMAN_SETUP
- Follow the setup wizard. If You allready have done configuration in Your system, do not use "Initial Setup"
Post upgrade 4
Generation of objects
- tc=SGEN
- Mark "Generate all objects of selected software components" and click "Continue"
- Click on "Select all components" and click "Continue"
- Click on "Select all" applications servers and click "Continue"
- Click on "Start job directly (in background)"
Post upgrade 5
Checking diverse tc/functionality
- Login to productive client
- tc=DSWP
- Choose "Operation", "Change management", "Maintenance optimizer". Is it posible to create new maintenance transaction?
- Choose "Solution landscape". Is it possible to browse the landscape?
- tc=ST22. Is there any dumps?
- tc=SM21. Any error in log?
- tc= SOLUTION_SETUP. Does it work?
Post upgrade 6
Unlock all users exept from already locked user preupgrade
- In TC=su10 click on "Authorization data"
- Scroll down and in "Additional selection criteria" check the "Locked users only" box
- Click on "Execute" (F8)
- Click on "Transfer" in upper left corner
- Click on "Unlock" icon

Shadow system during system upgrade

Hi All,
I am new to upgrade.I would like to know about Shadow System, how it will be created, what happens during the switch between the shadow and original system.
I had read the following blog which helped me to get clarity in the introduction part.
SUM: introduction to shadow system
Appreciate if anyone can explain and share some document on this.
Cheers,
Febin Roy

Hi Febin,
If you are working on SAP upgrade project you will come across to this term – shadow system or instance and system switch.The background upgrades process. Basically by upgrade we want to get the newest functions that provider offers in its software product that we are currently using. For sure we want to get this done without an interruption to existing, running system. In reality there is always some interruption. We are just trying to minimize it as much as possible. So does the SAP. The background of shadow system is to minimize system downtime during the upgrade.
Shadow system is basically copy of system that is going to be upgraded. This copies system is a bit limited to original one. It has only technical repository (SAP Basis objects) of objects and you cannot run your business processes on it. More over technical repository is upgraded into version of final release of to be upgraded system. Technically speaking it is used for modification adjustments (famous transactions SPAU and SPDD) and activation of objects. All the support packages and add-ons are imported into this instance as well. By them you get you system to the higher release. Let me mention also that shadow system run in the same database as its original system. They are running in parallel.
During preparation of shadow instance you are still running your original SAP system where all the business processes are being executed normally. At the moment when shadow instance is prepared we do its switch from shadow to original system. This is called system switch when you kind of “exchange” original system with shadow one. By that time shadow system becomes upgraded system.
Regards,
Deva

Running R/3 4.7 on a Windows Server 2008 System during an upgrade

Dear all,
I am plannung an upgrade project from R/3 4.7x200 to ERP6.0. The system is running on MaxDB. It's a single stack ABAP System.
Currently the system is running on a 32 bit Windows Server 2003. During the project we want to go to a new x86 64bit hardware with OS Windows Server 2008.
In order to use the speed of the new hardware also during the upgrade I want to move the systems to the new HW before starting the upgrade.
The problem is that runnning R/3 4.7 on Windows Server 2008 is not supported by SAP. On the other hand running the target release ERP6.0 on Windows Server 2008 is officially supported by SAP. This information comes from the PAM.
From the past I know that SAP allowed to run unsupported DB, OS and Release combinations during an upgrade project but I didn't find any information which fits to my situation.
Does anyone have experience with this constellation? Is there an official statement concerning this request?
Thanks for you support!
Regards
Bernd

> So I opened the OSS Message (0000594749) to the component you mentioned but the support answered that this would be a consultant task to support me in this area (?!?)....
I know one person who works for/in this component who did this several times to me too.
> They asked me to open a thread here in SDN.
That person did that too.
> I send the message back to SAP and stated that I disagree with the statement that the confirmation of platform support is consulting...but until now I have no feedback.
Just insist on a statement. If you still get the message back, contact the CIC (support dot emea at sap dot com) since you seem to be located in the UK according to your business card) and ask them to give you a different message processor.
> So I hoped someone already has some official statement from SAP.
Those special support statements are valid for a specific installation only so even if someone would have it for their installation it may not be valid for yours.
> We would be running Production with release 4.7 on Windows 2008 for 3 weeks or so...and I will need official support for that, just for the case something goes wrong...
I don't think this should be a problem. Technically the kernel supports it (according to the note) and also the database.
Markus

Database upgrade during SAP upgrade

Similar Messages

Maybe you are looking for