Upgradation SAP system

Pl give the procedure for
1) upgrade SAP system from ORA 9/ECC 5.0 to ORA 10g/ECC 6.0
2) full ECC6.0 installation (start from RAW OS; including swap/paging, env variables etc....)
Pl do the needful

Well if you want to do it the easy way then you could pay a consultant and watch how he does it. In the other hand if you want to learn and can´t contract a consultant then you could start looking for the SAP upgrade guide and all related documentation at service.sap.com/upgrade there you will find lots of helpful information and you will learn how to face that project.
For full installation then also look for the guide here service.sap.com/instguides and carefully follow the instructions.

Similar Messages

Process to Upgrade SAP HANA from SPS06 to SPS07 on distributed systems

Hi Experts,
We have a requirement to upgrade our SAP HANA system system from SPS06 to SPS07, but I have below queries on the same:
1) Do we need to consider any Notes before applying the upgrade for pre and post steps (as per my knowledge we have to consider post upgrade note: 1962472, are there any other too?)
2) As per my knowledge, we just need to stop SAP app systems and then backup of HANA system
3) Also we have a distributed environment in our landscape (three multiple hosts), what could be the upgrade approach, is it same as like single host environment (as /hana/shared will be the common to all distributed hosts)
Could anyone clarify my questions please.
Also for your information we have BW systems on top of HANA DB
Thanks very much in advance !
Kind Regards,
Arun Reddy
Message was edited by: Tom Flanagan

Hi John,
Thank you for the response, our source and target levels are (Source - 1.00.69.00.385196 Target - 1.00.74.03.392810)
I just wanted to ask you one more quick question here, can't we upgrade the above mentioned versions in one go? or we need to upgrade in two steps like, at first upgrading from 1.00.69.00.385196 to 1.00.73.00.389160 and then to target level 1.00.74.03.392810?
Also as you said in distributed environment we can upgrade as same like single host environment, so it same like below approach?
1) stopping the hana database
2) navigate to media path and then execute hdblcm in gui or command line
3) select option upgrading existing system
4) provide the passwords and system poped-up inputs
5) select the target levels of HANA components
6) once upgrade done successfully, then need to upgrade hana client in all app servers
if my above assumption is correct, then I have couple of questions like:
1) in which host we need to login and perform the upgrade? (as we are having three hosts- HANADB1, HANADB2, HANADB3) , is it okay we can do from any of the three hosts?
2) Also if upgrade stopped at middle due to errors, do we have option like to start the upgrade from the point where it stop? else we need to restore the lat successful backup and then again need to perform the upgrade from starting point?
Sorry for asking many questions, i have done the upgrade in single host environment, but not on distributed. So wanted to be make sure with all points to action the activity.
Thanks for your help and patience in advance !
Kind Regards,
Arun Reddy

Problem with unlock sap system during upgrade

Hello All,
I am performing EHP3 upgrade in CRM system. During Execution phase I har a error to solve. I did tried to unlock sap system with:
tp unlocksys DJ1 pf:/usr/sap/trans/bin/TP_DOMAIN_DJ1.PFL
Is it the right command in Windows?
Thanks

Dear,
I faced same issue and resolve it via below steps.
TP_ Return code: 0208 Error text: error in transport profile (parameter missing)
RZ10 --> Instance Profile --> Change Mode
DIR_TRANS=\usr\sap\trans\SUM\SUM\abap
DIR_PUT=\usr\sap\trans\SUM\SUM\abap
changed the Value
DIR_TRANS=\\HostName\sapmnt\trans
DIR_PUT=\\HostName\sapmnt\trans
Restart the SAP via sapmmc
Now APPLY the Pending SAP Note
again change the value of DIR_TRANS & DIR_PUT via RZ10 and Restart the sapmmc
tp locksys SID pf=\usr\sap\trans\bin\TP_DOMAIN_SID.PFL
tp lock_eu SID pf=\usr\sap\trans\bin\TP_DOMAIN_SID.PFL
ReTry....
Regards,

SAP System Message: Syntx error or generation error in a screen

dear sap basis gurus,
i am currently having problems signing on to our DEV server. i get this error message:
<SID>: SAP System Message
Syntx error or generation error in a screen.
it won't let me log on.
there were no changes made on the server (i.e., profile parameters) lately. it was working really fine after our support package level upgrade about 5 months ago.
have you encountered this problem before? please help me as there we have two imminent go-lives.
thank you very much in advance.
best regards,
albert

hello nick, ashok,
thank you very much for your responses.
i have already resolved this issue by just freeing up some space from our disks. not one of them was full though.
i hope i would no longer encounter the error message.
again, thank you.
best regards,
albert

Error while creating request list Unable to detect the SAP system directory

We are upgrading SAP BW (NW 7.0 EHP1) to SAP BW (NW 7.3)
source OS: Windows 2008 R2, source DB: MSSQL server 2008 R2 SP1 CU3
I had started the upgrade by running: STARTUP.BAT
I had started the DSUGui on the server (CI / DB on the same server) from: D:\usr\sap\BP1\upg\sdt\exe\DSUGui.bat
I ran both programs (run as administrators).
Once SAP Gui connects and was able to create userid/ password and when ready to start the initialization phase (click next)
gives me the error
Error while creating request list - see preceeding messages. Unable to detect the SAP system directory on the local host
I had tried STARTUP.BAT "jce_policy_zip=Z:\export-import\downloads\jce_policy-6' and still the same error.
I had started DSUGui.bat with trace and the trace file contents are
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[2.0.7.1006]/>
<!NAME[D:
usr
sap
bp1
upg
sdt
trc
server.trc]/>
<!PATTERN[server.trc]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %-100l [%t]: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Jan 11, 2012 10:14:58 AM [Error]:                          com.sap.sdt.engine.core.communication.AbstractCmd.log(AbstractCmd.java:102) [Thread[ExecuteWorker,5,main]]: Execution of command com.sap.sdt.engine.core.communication.CmdActionEvent@376433e4 failed: while trying to invoke the method java.io.File.getAbsolutePath() of an object returned from com.sap.sdt.dsu.service.req.DSURequestListBuilder.getSystemDir()
Jan 11, 2012 10:14:58 AM [Error]:                          com.sap.sdt.engine.core.communication.AbstractCmd.log(AbstractCmd.java:103) [Thread[ExecuteWorker,5,main]]: java.lang.NullPointerException: while trying to invoke the method java.io.File.getAbsolutePath() of an object returned from com.sap.sdt.dsu.service.req.DSURequestListBuilder.getSystemDir()
Jan 11, 2012 10:14:58 AM [Error]:                          com.sap.sdt.engine.core.communication.AbstractCmd.log(AbstractCmd.java:103) [Thread[ExecuteWorker,5,main]]: java.lang.NullPointerException: while trying to invoke the method java.io.File.getAbsolutePath() of an object returned from com.sap.sdt.dsu.service.req.DSURequestListBuilder.getSystemDir()
Jan 11, 2012 10:14:58 AM [Error]:                                                 com.sap.sdt.engine.core.communication.CmdActionEvent [Thread[ExecuteWorker,5,main]]: java.lang.NullPointerException: while trying to invoke the method java.io.File.getAbsolutePath() of an object returned from com.sap.sdt.dsu.service.req.DSURequestListBuilder.getSystemDir()
     at com.sap.sdt.dsu.service.req.DSURequestListBuilder.persistSystemInfo(DSURequestListBuilder.java:277)
     at com.sap.sdt.dsu.service.DSUService.createRequestList(DSUService.java:338)
     at com.sap.sdt.dsu.service.controls.DSUListener.actionNext(DSUListener.java:144)
     at com.sap.sdt.dsu.service.controls.DSUListener.actionPerformed(DSUListener.java:67)
     at com.sap.sdt.server.core.controls.SDTActionListener$Listener.actionPerformed(SDTActionListener.java:46)
     at com.sap.sdt.engine.core.communication.CmdActionEvent.actOnEvent(CmdActionEvent.java:43)
     at com.sap.sdt.engine.core.communication.CmdEvent.execute(CmdEvent.java:69)
     at com.sap.sdt.engine.core.communication.ExecWorker.handleCmd(ExecWorker.java:36)
     at com.sap.sdt.engine.core.communication.AbstractWorker.run(AbstractWorker.java:93)
I could not get Upgrade started. Any help is appreciated
Thanks
Prathap

Did you get this solved?
I have the same problem

Error CNDP/005 when trying to log into a SAp System

Hello everyone,
when trying to log into a SAP System, i get the following dump:
Error analysis
    Short text of error message:
    Control Framework: Data stream error. Transaction terminated.
    Long text of error message:
     Diagnosis
         The data stream from the frontend could not be interprete
     System Response
     Procedure
         This error is very probably due to an error in the fronte
         software installation or an obsolete version. Inform your
         administrator.
     Procedure for System Administration
         The frontend should have at least the same version as the
         release. Install the correct frontend. If the error conti
         occur, inform SAP.
    Technical information about the message:
    Message class....... "CNDP"
    Number.............. 005
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
It occurs directly after inserting my User/Password and pressing enter.
My SAP GUI: Version 710, Patchlevel 11
The strange thing about that:
Last week i didn't have this error and i didn't change anything.
I already uninstalled, reinstalled and rebooted but it didn't work.
I would appreciate some help.

I upgraded to patchlevel 13, which solved the problem.

Upgrading SAP ESS and MSS after HR upgrade in ECC 6.0

Hello
I am new to SAP netweaver.
Our landscape has an ECC 6.0 system integrated with EP 7.0.
We recently upgraded our SAP HR from 600(SP 48) to 600(SP61) and EA HR component from 603(SP 22) to 603( SP 35).
After the upgrade we came to know that the portal users are facing some issues with Etime application on portal, i did a bit of searching and found that we have to upgrade SAP ESS, MSS and ERP5COM components. (http://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACKMISMATCHISSUES)
My questions are:
1) Can we directly apply SP's for ESS, MSS and other components as i cannot find any prerequisites required to be met before they have to applied?
2)If we have ESS SP 04 and the required version is ESS SP07, can we directly apply SP 07 or we have to first apply in a sequence SP05, SP06 and then move to SP07?
Thanks a lot!
Varun

Hello,
1) If a developer modified the ESS/MSS package, you need to ask the developer before you apply the patches. In this case, you find the "local version is modified" text in the corresponding package.
2) Java Patches are cumulative, which means that higher Patch contains all corrections of lower Patches.([SAP Note 1249886|https://service.sap.com/sap/support/notes/1249886])
Laszlo

How to execute one sap gui script in different SAP system component versions.

Hi Experts,
I am having a task to write a script which can be executed in different SAP systems , explained as below.
I have created a script to do password reset for mass users in one system (TC6) & it's working fine. But when i load same script in other system(QR5) to do the same activity , the system unable to execute the same script.
One thing i found that by comparing in the two systems that the screen-ids in QR5 system is different than TC6 system.
My question
1-> why it is different even though the scripting language is same.
2-> How can i overcome it & make a common script for all the systems.
Please help me to resolve this.
Thanks in Advance,
Khagendra

Hi Holger & Stefan,
Sorry for late response first.
Now i have attached the recorded program-me for two systems for SU01 (simple user maintenance) with highlighted the text. I have highlighted both for easy understanding .
In system QR5 (upgraded one)
session.findById("wnd[0]").maximize
session.findById("wnd[0]/tbar[0]/okcd").text = "/nsu01"
session.findById("wnd[0]").sendVKey 0
session.findById("wnd[0]/usr/ctxtSUID_ST_BNAME-BNAME").text = "test"
session.findById("wnd[0]").sendVKey 0
session.findById("wnd[0]/tbar[1]/btn[18]").press
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpADDR/ssubMAINAREA:SAPLSUID_MAINTENANCE:1900/txtSUID_ST_NODE_PERSON_NAME-NAME_LAST").text = "rest"
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpADDR/ssubMAINAREA:SAPLSUID_MAINTENANCE:1900/txtSUID_ST_NODE_PERSON_NAME-NAME_LAST").setFocus
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpADDR/ssubMAINAREA:SAPLSUID_MAINTENANCE:1900/txtSUID_ST_NODE_PERSON_NAME-NAME_LAST").caretPosition = 4
session.findById("wnd[0]").sendVKey 0
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpADDR/ssubMAINAREA:SAPLSUID_MAINTENANCE:1900/txtSUID_ST_NODE_PERSON_NAME-NAME_FIRST").text = "user"
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpADDR/ssubMAINAREA:SAPLSUID_MAINTENANCE:1900/txtSUID_ST_NODE_PERSON_NAME-NAME_FIRST").setFocus
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpADDR/ssubMAINAREA:SAPLSUID_MAINTENANCE:1900/txtSUID_ST_NODE_PERSON_NAME-NAME_FIRST").caretPosition = 4
session.findById("wnd[0]").sendVKey 0
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpADDR/ssubMAINAREA:SAPLSUID_MAINTENANCE:1900/txtSUID_ST_NODE_COMM_DATA-SMTP_ADDR").text = "[email protected]"
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpADDR/ssubMAINAREA:SAPLSUID_MAINTENANCE:1900/txtSUID_ST_NODE_COMM_DATA-SMTP_ADDR").setFocus
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpADDR/ssubMAINAREA:SAPLSUID_MAINTENANCE:1900/txtSUID_ST_NODE_COMM_DATA-SMTP_ADDR").caretPosition = 21
session.findById("wnd[0]").sendVKey 0
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpLOGO").select
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpLOGO/ssubMAINAREA:SAPLSUID_MAINTENANCE:1101/cmbSUID_ST_NODE_LOGONDATA-USTYP").setFocus
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpLOGO/ssubMAINAREA:SAPLSUID_MAINTENANCE:1101/cmbSUID_ST_NODE_LOGONDATA-USTYP").key = "A"
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpLOGO/ssubMAINAREA:SAPLSUID_MAINTENANCE:1101/pwdSUID_ST_NODE_PASSWORD_EXT-PASSWORD").text = "********"
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpLOGO/ssubMAINAREA:SAPLSUID_MAINTENANCE:1101/pwdSUID_ST_NODE_PASSWORD_EXT-PASSWORD2").text = "********"
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpLOGO/ssubMAINAREA:SAPLSUID_MAINTENANCE:1101/pwdSUID_ST_NODE_PASSWORD_EXT-PASSWORD2").setFocus
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpLOGO/ssubMAINAREA:SAPLSUID_MAINTENANCE:1101/pwdSUID_ST_NODE_PASSWORD_EXT-PASSWORD2").caretPosition = 9
session.findById("wnd[0]").sendVKey 0
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpACTG").select
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpACTG/ssubMAINAREA:SAPLSUID_MAINTENANCE:1106/cntlG_ROLES_CONTAINER/shellcont/shell").modifyCell 0,"AGR_NAME","Z:T5_UK_WIPRO_DEV_NONBASIS"
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpACTG/ssubMAINAREA:SAPLSUID_MAINTENANCE:1106/cntlG_ROLES_CONTAINER/shellcont/shell").currentCellColumn = "AGR_NAME"
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpACTG/ssubMAINAREA:SAPLSUID_MAINTENANCE:1106/cntlG_ROLES_CONTAINER/shellcont/shell").pressEnter
session.findById("wnd[0]").sendVKey 11
In system DR0 (Not upgraded)
session.findById("wnd[0]").maximize
session.findById("wnd[0]/tbar[0]/okcd").text = "/nsu01"
session.findById("wnd[0]").sendVKey 0
session.findById("wnd[0]/usr/ctxtUSR02-BNAME").text = "test"
session.findById("wnd[0]/usr/ctxtUSR02-BNAME").caretPosition = 4
session.findById("wnd[0]").sendVKey 0
session.findById("wnd[0]/tbar[1]/btn[18]").press
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpADDR/ssubMAINAREA:SAPLSZA5:0900/txtADDR3_DATA-NAME_LAST").text = "test"
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpADDR/ssubMAINAREA:SAPLSZA5:0900/txtADDR3_DATA-NAME_LAST").setFocus
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpADDR/ssubMAINAREA:SAPLSZA5:0900/txtADDR3_DATA-NAME_LAST").caretPosition = 4
session.findById("wnd[0]").sendVKey 0
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpADDR/ssubMAINAREA:SAPLSZA5:0900/txtADDR3_DATA-NAME_FIRST").text = "user"
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpADDR/ssubMAINAREA:SAPLSZA5:0900/txtADDR3_DATA-NAME_FIRST").setFocus
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpADDR/ssubMAINAREA:SAPLSZA5:0900/txtADDR3_DATA-NAME_FIRST").caretPosition = 4
session.findById("wnd[0]").sendVKey 0
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpADDR/ssubMAINAREA:SAPLSZA5:0900/txtSZA5_D0700-SMTP_ADDR").text = "[email protected]"
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpADDR/ssubMAINAREA:SAPLSZA5:0900/txtSZA5_D0700-SMTP_ADDR").setFocus
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpADDR/ssubMAINAREA:SAPLSZA5:0900/txtSZA5_D0700-SMTP_ADDR").caretPosition = 21
session.findById("wnd[0]").sendVKey 0
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpLOGO").select
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpLOGO/ssubMAINAREA:SAPLSUU5:0101/cmbUSLOGOND-USTYP").setFocus
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpLOGO/ssubMAINAREA:SAPLSUU5:0101/cmbUSLOGOND-USTYP").key = "A"
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpLOGO/ssubMAINAREA:SAPLSUU5:0101/pwdG_PASSWORD1").text = "********"
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpLOGO/ssubMAINAREA:SAPLSUU5:0101/pwdG_PASSWORD2").text = "********"
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpLOGO/ssubMAINAREA:SAPLSUU5:0101/pwdG_PASSWORD2").setFocus
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpLOGO/ssubMAINAREA:SAPLSUU5:0101/pwdG_PASSWORD2").caretPosition = 9
session.findById("wnd[0]").sendVKey 0
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpACTG").select
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpACTG/ssubMAINAREA:SAPLSUU5:0106/tblSAPLSUU5TC_AGR/ctxtUSAGR-AGR_NAME[1,5]").text = "Z:T5_UK_WIPRO_DEV_NONBASIS"
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpACTG/ssubMAINAREA:SAPLSUU5:0106/tblSAPLSUU5TC_AGR/ctxtUSAGR-AGR_NAME[1,5]").setFocus
session.findById("wnd[0]/usr/tabsTABSTRIP1/tabpACTG/ssubMAINAREA:SAPLSUU5:0106/tblSAPLSUU5TC_AGR/ctxtUSAGR-AGR_NAME[1,5]").caretPosition = 26
session.findById("wnd[0]").sendVKey 0
session.findById("wnd[0]").sendVKey 11
From the above it's clear that the screen IDs in both the systems are different as the program-me name is different for the same TA (SU01) in both the systems.
Now can you please advise how i will go with both to handle in one script (I can't put a check condition to call different scripts for the specific systems as in my landscape there are more that 100 systems).
Please help me on this.
Thanks in Advance,
Khagendra

Physical Memory Upgrade [SAP, Oracle parameter changes]

Hello Guru,
Good day!
I'm not sure if I'm in the correct forum, please bare with me if I'm not.
We are actually planning to increase our Production [Physical Memory] server from its current size 15360GB including [oracle, SAP & OS] to 44GB memory. Do you have any idea how can we calculate to the most needed SAP / DB parameter should be increase after we allocate the 44GB in preparation for Go-Live. Below are details of my systems [oracle version, kernel, R/3 System, OS version, SAP parameter and DB parameter.
Reason for memory upgrade: will create two client in one system with a different number of users and different plant e.g. America / Canada
======================================================================
SAP R/3 Version: SAP 4.6C
Oracle Version: 10.2.0.4.0
OS Level: AIX 5.3
orapaa> oslevel -g
Fileset                                 Actual Level        Maintenance Level
bos.rte                                 5.3.8.0             5.3.0.0
Physical Memory
Real,MB   15360
======================================================================
kernel release               46D
kernel make variant       46D_EXT
compiled on                  AIX 1 5 0056AA8A4C00
compiled for                  64 BIT
compile time                  Aug 17 2007 10:57:49
update level                  0
patch number                  2337
source id                     0.2337
======================================================================
orapaa> prtconf
System Model: IBM,9117-MMA
Machine Serial Number: 06DDD01
Processor Type: PowerPC_POWER6
Processor Implementation Mode: POWER 6
Processor Version: PV_6_Compat
Number Of Processors: 4
Processor Clock Speed: 4208 MHz
CPU Type: 64-bit
Kernel Type: 64-bit
LPAR Info: 9 SWT_AMR_SADCB335_SAP_HA_PRI
Memory Size: 15360 MB
Good Memory Size: 15360 MB
Platform Firmware level: Not Available
Firmware Version: IBM,EM340_095
Console Login: enable
Auto Restart: true
Full Core: false
======================================================================
Our current used SAP parameter
Profile parameters for SAP buffers     Parameters Name               Value     Unit
Program buffer
                    abap/buffersize               850000     Kb
CUA buffer
                    rsdb/cua/buffersize               10000
Screen buffer
                    zcsa/presentation_buffer_area     20000000 Byte
Generic key table buffer
                    zcsa/table_buffer_area          100000000 Byte
Single record table buffer
                    rtbb/buffer_length               60000
Export/import buffer
                    rsdb/obj/buffersize               40000      kB
Table definition buffer
                    rsdb/ntab/entrycount          30000
Field description buffer
                    rsdb/ntab/ftabsize               60000     kB
Initial record buffer
                    rsdb/ntab/irbdsize               8000     kB
Short nametab (NTAB)
                    rsdb/ntab/sntabsize          3000     kB
Calendar buffer
                    zcsa/calendar_area          500000     Byte
Roll, extended and heap memory     EM/TOTAL_SIZE_MB          6144     MB
                    ztta/roll_area               6500000     Byte
                    ztta/roll_first               1     Byte
                    ztta/short_area               1400000     Byte
                    rdisp/ROLL_SHM               16384     8 kB
                    rdisp/PG_SHM               16384     8 kB
                    rdisp/PG_LOCAL               150     8 kB
                    em/initial_size_MB               4092     MB
                    em/blocksize_KB               4096     kB
                    em/address_space_MB          4092     MB
                    ztta/roll_extension               2000000000     Byte
                    abap/heap_area_dia          2000000000     Byte
                    abap/heap_area_nondia          2000000000     Byte
                    abap/heap_area_total          2000000000     Byte
                    abap/heaplimit               40000000     Byte
                    abap/use_paging               0
======================================================================
Oracle Parameter
Oracle Parameter Name     Value     Unit
SGA_MAX_SIZE          6192     MB
PGA_AGGREGATE_TARGET     400     MB
DB_CACHE_SIZE           0
SHARED_POOL_SIZE     960     MB
LARGE_POOL_SIZE          16     MB
JAVA_POOL_SIZE           32     MB
LOG_BUFFER          14246912
db_block_buffers          655360
Thanks and regards,
Mike

I feel the best way to get the parameters which needs to be adjusted is to go for EarlyWatch Check after increasing the Physical Memory of your SAP system, as we cannot say how and which parameters needs to be checked and changed.. as there is some dependiblity also between the parameters...
All the best !

How to change the hostname was set/defined in SAP system?

Dear Expert,
My customer met a problem about that:
he defined his host name with small characters(lower case) "abc" when he installed the SAP system (Windows2003(x64)-Solman70SR4).
But in SM21, the title of sm21, the hostname was recognize as upper case "ABC".
in SM51, the hostname was also recognized as upper case "ABC"
in STMS, the tab of 'transport tool', it is recognized as lower case "abc" in TRANSDIR.
in SM59, it is recognized as upper case "ABC" in internal connections, but recognized as lower case "abc" in ABAP connections, such as TMSADM@<DB>.DOMAIN.<sid>
While in Java URL, it is recognized as lower case "abc". With my test, the Java URL is not case sensitive for the HOSTNAME part in HTTP link as I tested to change the hostname both in upper case and lower case in etc\hostname file, the URL both are working. (not sure if this is due to the test is with intranet or not).
Based on SAP note 611361, it seems that:
"Hostnames must be considered "case sensitive". That means
hostnames shall be used in the same case (upper or lower) in all
SAP configurations as well as in the network configuration (DNS
or etc/hosts). You must ensure consistent name resolving of the
hostname from hostname to IP address and back from the IP address
to the the same hostname (case sensitive match). See also note
129997."
Please help to suggest.
Many thanks in advance,
Perry Song

Section 4.13 "Checking the Consistency of the Host Name" in [This Upgrade Guide|https://websmp208.sap-ag.de/~sapidb/011000358700000353422008E] has a good explaination of what & how to check your hostname / parameter configuration.
on a windows box, another way to get the TCP/IP name is to type 'hostname' from a CMD window.

Impact of upgrading SAP 4.6C to ECC6.0 to Java application

Hi,
Currently, my Java application is:
1. using SAP 4.6C as backend
2. using Java 1.4
3. using SAP Enterprise Connector in SAP Netweaver Developer Studio 7.0.15 to generate the BAPI proxies
4. using JCo 2.1.8
If now the backend SAP system is going to be upgraded from 4.6C to ECC6.0, will there be any changes required on my Java application i.e.
1. Is the BAPI proxies generation process with SAP Enterprise Connector remain unchanged?
2. Are the BAPI structures remain the same that do not require any Java code change when calling BAPI?
3. Is the JCo version remains unchanged?
4. Is there any Java code changes required?
Thanks!

Hi,
1. Is the BAPI proxies generation process with SAP Enterprise Connector remain unchanged?
Yes. No change required except minor changes.
2. Are the BAPI structures remain the same that do not require any Java code change when calling BAPI?
Well you will have to check if the BAPI import/export/tables/changing parameters have undergone any change. If not then no change required.
3. Is the JCo version remains unchanged?
Yes. This shouldnt be an issue.
4. Is there any Java code changes required?
Well if your 4.6c system was non-unicode, ECC 6.0 would be unicode. So the RFC where you would have mentioned that a Unicode(java) system is interacting with Non-unicode(4.6c) system will require a change. This is applicable to both RFC's in SAP & Java.
Thanks,
Best regards,
Prashant

Steps to upgrade SAP B1 8.8 PL10 to 8.81 PL05

Hi All,
Please could someone guide me how to upgrade my system from 8.8 PL10 to 8.81 PL05. I have the downloaded file available with me with a "upgrade" application button. Should I directly click on "upgrade" button in the 8.81 PL05 folder and follow accordingly, or we need to uninstall certain elements of existing 8.8 PL10 version?
Thanking you in advance!!!!
Golden

Hi Golden,
For more information regarding upgrade SAP Business One application to version 8.81 please refer to the "Administrator's Guide 8.81 SQL" (chapter: 5 u2013 Upgrading SAP Business One), which can be found on the Documentation Resource Centre on the Portal.
http://service.sap.com/smb/sbo/documentation -> Documentation Resource Center for Release Family 8.8 -> System Administration
Regards,
Ladislav Meszaros
SAP Business One Forum Team

Error in PHASE PREP_EXTRACT/PREIMP: Upgrade SAP R/3 4.7 to SAP ECC 6.0 EHP4

Hello,
I'm currently in upgrading a SAP R/3 4.7 system to a SAP ECC 6.0 EHP4.
Therefore I followed the Upgrade Guide from marketplace - installation- and upgrade guides - SAP ERP - SAP ERP 6.0 - SAP Enhancement Package 4 for SAP ERP 6.0 - Upgrade Guide SAP ERP including EHP4 SR1 - Unix on MaxDB.
I downloaded media from marketplace/swdc - Installations and Upgrades - SAP Application Components - SAP ERP - SAP ERP ENHANCE PACKAGE - EHP4 FOR SAP ERP 6.0 / NW7.01 - Upgrade.
I'm starting upgrade with upgrade master DVD 51036889_1 and      51036889_2.
Now upgrade breaks down in phase PREP_EXTRACT/PREIMP with error:
Severe error(s) occured in phase PREP_EXTRACT/PREIMP!
Last error code set: Single errors (code <= 8) found in logfile 'PREIMP.ELG'
PREIMP.ELG says:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
R3trans preimport and RETURN CODE in R710VPE.REX
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETW169 no connect possible: "maybe someone set invalid values for DIR_LIBRARY ('/usr/sap/REX/SYS/exe/run') or dbms_type ('ADA')"
Kernel is stored in /usr/sap/REX/SYS/exe/run and database is ADA (maxdb).
File R710VPE.REX says:
4 EPU201XBEGIN OF SECTION BEING ANALYZED
4 ETW000 R3trans version 6.13 (release 640 - 17.02.10 - 13:07:00).
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time   : 07.03.2011 - 15:28:36
4 ETW000 control file: /usr/sap/REX/upg/abap/tmp/PREIMPTRANS.CTL
4 ETW000 > import
4 ETW000 > file='/usr/sap/REX/upg/abap/bin/R710VPE.SAP'
4 ETW000 > safeandslow=yes
4 ETW000 > buffersync =yes
4 ETW000 > commit     =1048576
4 ETW000 > importtruncated =yes
4 ETW000 R3trans was called as follows: R3trans -w /usr/sap/REX/upg/abap/tmp/R710VPE.REX -u 1 /usr/sap/REX/upg/abap/tmp/PREIMPTRANS.CTL
4 ETW000 active unconditional modes: 1
2EETW169 no connect possible: "maybe someone set invalid values for DIR_LIBRARY ('/usr/sap/REX/SYS/exe/run') or dbms_type ('ADA')"
4 EPU202XEND OF SECTION BEING ANALYZED
Can anybody help me out here?
Regards,
Julia

Hello,
I run 'R3trans -x' command, but there was no problem - connection to database was working.
Problem was following:
Before starting the sdt service on host, I set environment variables JAVA_HOME and LD_LIBRARY_PATH for sidadm. That's not neccessary and that was the problem. Without setting these variables it is working now.
Thanks,
Julia

DB Copy (MSSQL) between two SAP systems with different level and Components

Hi,
we have a SAP system release mysap 2004 SR1 and for "the upgrade project to SAP ECC 6.0 " we installed a new mysap 2004 in a new hardware (sap03) where we have also solution manager running. The new installed Mysap 2004 SR1 is alos running fine in the new hardware.
Now we would like to do DB copy from the old system (sap02) to the the new system sap03 and then we will do the upgrade to SAP ECC 6.0.
After I compared the two systems I have following questions:
1) there are 4 Software Components which are not in the new system (sap03). This are:
PI
FIN_BLERP
BP_INSTRASS
Is this necesary for the DB copy or we do not need this to be able to do the DB copy?
2) The Software Components Level is not the same. Should we have the same level to do the DB Copy?
Thanks in advance
Best regards
HanseAtik

Hi Juan, hi Clas,
just to be clear and to not stuck on the the way:
The systems are as follow:
1) the source system:
                     - Windows Server 2003,
                     - MSSQL Server 2005 with 32 bit.
                     - Mysap 2004 SR1
2) Target system:
                   - Windows Server 2003
                   - MSSQL Server 2005, with 64 bit.
                   - Mysap 2004 SR1 (with less Support package level and no PI, FIN_Basis, BP_BLERP and BP_INTASS coponents)
I hope this will work. could you post the link the DB Copy guide we are talking about?
By this way we will be sure that we are talking about the same DB Copy. Otherwise any mistake in this step will cost more work and time.
Thanks in advance
Best regards
HanseAtik

Add web element in Crystal report for SAP system

Hi all,
I have added web element in Crystal report for SAP system (BI or R/3) . But it does not show the control. It shows only scipt.It does not render the HTML.
But if I add the webelement for Excel sheet ,It shows the control.
How can I add web element for SAP System? Can't we use web controls in SAP system ?
Help me in this regard.

Hi All,
i have the same issue on crystal report add-ins. Have you able to solve this without upgrading our sap business one to the latest version or patch level? Please see details below.
OS: MS Windows 7 SP1
SAP Business One 8.82 pl7
Crystal report 2011
Crystal report integration package installed under B1_SHare/Client
But still the problem persist on the workstation.
Please help me solve this problem.
Thank you,
ana

Upgradation SAP system

Similar Messages

Maybe you are looking for