Hello Experts,

We are doing an EhP upgrade of ABAP only system from EhP 4 to EhP6 for SAP ECC 6.0 system. We have successfully completed all phases till Checks phase where during the phase step PREP_SPACECALC/TR_GET_SPCREQ_ADD. The SUM (SP 09 patch 2) tool is getting terminated unexpectedly with the error

"Unable to execute the SDT request ABAP operation check on hostname <host> instance 20
Checks of the ABAP upgrade request have failed
Error from unit observer
Tool died unexpectedly with."

The trace file DETECT.TRC has the below entries :

Dec 6, 2013 10:07:37 PM [Error]:                                                                    com.sap.sdt.dmt.DMTFactoryManager [Thread[main,5,main]]: Property file dmt.properties not found in class path

Dec 6, 2013 10:07:40 PM [Error]:                                                                  com.sap.sdt.jspm.JspmFactoryManager [Thread[main,5,main]]: Property file jspm.properties not found in class path

Dec 6, 2013 10:07:40 PM [Error]:                                                                    com.sap.sdt.dmt.DMTFactoryManager [Thread[main,5,main]]: Property file dmt.properties not found in class path

Dec 6, 2013 10:07:41 PM [Error]:                                                                  com.sap.sdt.jspm.JspmFactoryManager [Thread[main,5,main]]: Property file jspm.properties not found in class path

Dec 6, 2013 10:08:17 PM [Error]:                                                       com.sap.sdt.sapup.rapi.connector.R3upConnector [Thread[ABAP-3,5,main]]: Could not connect to <hostname>:4240. Could not connect to host <hostname> on port 4240.

java.net.ConnectException: Connection refused

java.net.ConnectException: Connection refused

Dec 7, 2013 5:06:50 AM [Error]:                                                    com.sap.sdt.server.ext.r3up.unit.R3upUnitObserver [Thread[SAPup,5,main]]: Tool closed connection unexpectedly.

Dec 7, 2013 5:06:50 AM [Error]:       com.sap.sdt.server.ext.r3up.unit.R3upUnitObserver.waitForToolStatus(R3upUnitObserver.java:559) [Thread[ABAP-5,5,main]]: Tool died unexpectedly with .

Dec 7, 2013 5:06:50 AM [Error]:                                                              com.sap.sdt.lup.ctrl.SDTRequestExecutor [Thread[ABAP-5,5,main]]: com.sap.sdt.server.ext.r3up.unit.R3upUnitException: Tool died unexpectedly with .

        at com.sap.sdt.server.ext.r3up.unit.R3upUnitObserver.waitForToolStatus(R3upUnitObserver.java:559)

        at com.sap.sdt.server.ext.r3up.unit.R3upUnitObserver.doUnitAction(R3upUnitObserver.java:382)

        at com.sap.sdt.server.ext.r3up.unit.R3upUnitObserver.executeUnit(R3upUnitObserver.java:113)

        at com.sap.sdt.dsu.abap.handler.SAPupUnitExecutor.doExecution(SAPupUnitExecutor.java:319)

        at com.sap.sdt.dsu.abap.handler.SAPupUnitExecutor.executeUnit(SAPupUnitExecutor.java:304)

        at com.sap.sdt.dsu.abap.handler.AbapUpgradeRequestHandler.check(AbapUpgradeRequestHandler.java:440)

        at com.sap.sdt.lup.ctrl.handler.SDTRequestHandlerMethodInvocator.doOperation(SDTRequestHandlerMethodInvocator.java:155)

        at com.sap.sdt.lup.ctrl.SDTRequestExecutor.invokeMethod(SDTRequestExecutor.java:225)

        at com.sap.sdt.lup.ctrl.SDTRequestExecutor.run(SDTRequestExecutor.java:329)

Dec 7, 2013 5:06:50 AM [Error]:               com.sap.sdt.dsu.abap.handler.SAPupUnitExecutor.executeUnit(SAPupUnitExecutor.java:312) [Thread[ABAP-5,5,main]]: Error from unit observer

Dec 7, 2013 5:06:50 AM [Error]:     com.sap.sdt.dsu.abap.handler.AbapUpgradeRequestHandler.check(AbapUpgradeRequestHandler.java:444) [Thread[ABAP-5,5,main]]: Checks of the ABAP upgrade request ABAP have failed

Dec 7, 2013 5:06:50 AM [Error]:                    com.sap.sdt.lup.ctrl.SDTRequestExecutor.invokeMethod(SDTRequestExecutor.java:253) [Thread[ABAP-5,5,main]]: Unable to execute the SDT request ABAP operation check on hostname <hostname> instance 20

Please suggest us how to proceed.

Dear All,

    I am trying to upgrade from ECC 6.0 EHP5 to EHP7 using SUM 1.0 SP8  tool but getting below error :

Conflicts found.

      Check log file 'SPDA_CONFLCHK.LOG' for details.

      To resolve the conflicts the current step will be repeated and you

      must change your Add-on or Support Package selection or add

      Conflict Resolution Patches (CRT)

Error in 'SPDA_CONFLCHK.LOG'  :

2EETN219 The system found conflicts for add-on "LOCHRSAE" release "605" (see list):

3 ETN220 Support Package "SAPKE60460" of software component "SAP_HR" release "604"

4 ETN225 ... has conflicts with "LOCHRSAE" release "605" - piece list: "SAPK-60520INLOCHRSAE"

4 ETN225 ... has conflicts with "LOCHRSAE" release "605" - piece list: "SAPK-60518INLOCHRSAE"

3WETN230 Conflict resolution by including a CRT for "LOCHRSAE" release "605" and "SAPKE60460"

3 ETN220 Support Package "SAPKE60461" of software component "SAP_HR" release "604"

4 ETN225 ... has conflicts with "LOCHRSAE" release "605" - piece list: "SAPK-60520INLOCHRSAE"

4 ETN225 ... has conflicts with "LOCHRSAE" release "605" - piece list: "SAPK-60518INLOCHRSAE"

4 ETN225 ... has conflicts with "LOCHRSAE" release "605" - piece list: "SAPK-60512INLOCHRSAE"

4 ETN225 ... has conflicts with "LOCHRSAE" release "605" - piece list: "SAPK-60509INLOCHRSAE"

4 ETN225 ... has conflicts with "LOCHRSAE" release "605" - piece list: "SAPK-60508INLOCHRSAE"

3WETN230 Conflict resolution by including a CRT for "LOCHRSAE" release "605" and "SAPKE60461"

3 ETN220 Support Package "SAPKE60462" of software component "SAP_HR" release "604"

4 ETN225 ... has conflicts with "LOCHRSAE" release "605" - piece list: "SAPK-60520INLOCHRSAE"

4 ETN225 ... has conflicts with "LOCHRSAE" release "605" - piece list: "SAPK-60518INLOCHRSAE"

4 ETN225 ... has conflicts with "LOCHRSAE" release "605" - piece list: "SAPK-60512INLOCHRSAE"

4 ETN225 ... has conflicts with "LOCHRSAE" release "605" - piece list: "SAPK-60510INLOCHRSAE"

3WETN230 Conflict resolution by including a CRT for "LOCHRSAE" release "605" and "SAPKE60462"

1 ETN214X."**************************************************"

1 ETN251  End of phase: "'Conflict Check'"

1 ETN254      End date: "29.10.2013"

Already include this Support Packages to Path EPS/in

SAPK-60508INLOCHRSAE

SAPK-60509INLOCHRSAE

SAPK-605010INLOCHRSAE

SAPK-605012INLOCHRSAE

SAPK-605018INLOCHRSAE

SAPK-605020INLOCHRSAE

SAPKE60460

SAPKE60461

SAPKE60462

Then re-operation SUM tool but the conflicts still occurs.

Please find attached remaining log and guide me how can i resolve this issue

Regards,

Hello,

Soon after entering the downtime (Execution) phase I recieved the errror -

      Severe error(s) occured in phase MAIN_SWITCH/EU_SWITCH!
       Last error code set: tp failed with return code 237, check  /usr/sap/SBA/SUM/abap/log/TPSQLSTD.OUT

When I check the log I find :

EXECUTING /usr/sap/SBA/SUM/abap/exe/tp  pf=/usr/sap/SBA/SUM/abap/var/DEFAULT.TPP execdbscript SBA -x ../var/EU_SWITC.XQL DBEXECNONT

This is tp version 380.07.32 (release 740)                                                                                         

INFO:  XDNLevelTraceSetLocation: Trace set to: XDNTrace.038026.*                                                                   

ERROR: Statement: RENAME "USMD0020?" TO "USMD0020"                                                                                 

ERROR: ERROR 1024: DB object does already exist                                                                                    

ERROR: SQL ERROR -601: USMD0020 in R3SBADATA type *FILE already exists. MSGID= Job=316145/SBAADM/QZSHSH  

Log  /usr/sap/sba/sum/abap/log/EU_SWITC.XUT  contains the following message:

************Beginning of data**************                                                                                       

tp_exec_statement: RENAME "USMD0020?" TO "USMD0020"                                                                                

TPERR- (row already exists)                                                                                                        

tp_exec_dbscript: 0 statement(s) successfully processed.                                                                           

                  1 statement(s) returned an error code.                                                                           

************End of Data********************                                                                                       

When I check the database I find that the table USMD0020 does in fact exist. In this case, is the solution to simply rename the table to another name and proceed?

Our platform is IBM iSeries if that is important.

Thanks,

Craig

Hello everyone!

Our company has recently upgraded its ECC6 to EhP7. Everything went without major issues, however, one piece in the custom-built accounts payable workflow quit working after the upgrade. A screen with underlying transaction FV63 is now missing two vital to the workflow buttons: Release and Reject. Can anybody point in direction how to address this shortfall? We did all required post-upgrade steps, including regeneration of the authorization profiles, but the buttons are still missing. Is this really a workflow issue or Basis/FI one? Were there any changes by SAP in the EhP7 pertaining to FV63? Attached screenshots illustrate the issue.

Thank you all in advance!

Hi,

I am trying to get the latest version of IDES Ecc 6.0 with NW component and want to install as a dual-stack.

I tried downloading the IDES version thru this link

Installations and Upgrades - E"SAP ERP"SAP ERP 6.0

And then I went to IDES

But when I am trying to install the steps are nothing! compared to this installation guide posted here.. Cause the installation doesn't even ask me for the IDES files (23 of them)

http://www.saptechies.org/sap-ecc6-ides-installation-windows-server-oracle-102-databa/

Where to download the latest version of IDES?

Hi Friends

recently we upgraded my SAP ECC 6.0.EHP3 system DB from mssql2005 to MSSQl2008r2, after that my sap system is working fine  but

when iam checking DB02 for Database Size History , that time iam getting warning message like No

No size history ,check job details

and SAP SQL Statistics is showing yash color symbol 

but all the jobs are working fine..

Please give me the reason for this.where i need to changes.

Hi,

We have completed all the upgrade activies required for 4.6C to ECC 6.0 EHP 5.

After upgrade, few SAP Directories are missing ( in AL11 ) in new upgraded system those are available in old system ( 4.6C ).

Please suggest, how can I get those missing SAP Directories in new upgrade system ?

Thanks and Regards:

Anugrah

Hi,

Can anyone give me some idea on this upgrade:

Details of Current Servers are:

OS:- Windows Server 2003 (32 Bit)

Database Version:- Oracle 9.2.0.8

SAP: SAP R/3 ENTERPRISE 47X110 (Non-Unicode)

Details of New Servers:

OS:- Windows Server 2008 R2 (64 Bit)

Database Version:- Oracle 11.2

SAP: SAP ERP 6.0 EHP6

Can anyone share best approach to complete this upgrade with optimized downtime.

If we want to install same current version of SAP in Windows 2008 64-bit, we do not have DVD available for 4.7. PAM also says not supported.

Please suggest Best approach.

Thanks,

Srikanth

Hi,

I've achieve to send myself an object (Sales order) with a note (text). I've received the mail with the note text in the mail and an an attachment with the  object. However the attachment object (sales order) is a notepad with an URL that links me to Netweaver Bussiness client. I log on and I can see the Sales Order in SAPGUI, but...

Is it possible to assign the sales order form instead an URL? I'd like to be able to send a note with an object to a customer thas has no SAP system.

Thanks.

How ADS works and configured, please help on these.Currently am working with ECC6.0, ABAP stack.

Hi,

We have a requirement to unistall on SAP ERP 6.0 EHP 6 system, 3rd party software components that is no more in use to clean up a bit the system.

I have identified the objects of the 3rd party software components and they are over 13,000 objects (Packages, Programs, DDIC, Classes, etc).

Instead of manually deleting each of these objects (which is quite tedious you will guess), is there are more simple way to unistall these software components?

Thanks in advance

Hi Experts,

I am facing one issue during sales return process.

We have created sales return order, posted the return delivery and created the debit memo through sales module.

Now we are trying to update the excise register RG23A Part I and Part II for return quantity. We have passed the excise JV through T code : J1IH with reference to debit memo document, value is updating properly in RG23A Part II register but quantity is not getting updated in RG23A Part I register.

Can anybody guide me how to update the quantity in RG23A Part I register.

Thanks in advance,

chandu.

Hi,

We are using SUM tool to upgrade ECC 6.0 to EHP5 and we have finished

upto Check phase and now during summary we can see that it has finished

with warning:

++++++++++++++++++++++++++++++++++++++++++++

WARNING: Errors occurred during CHECK OF UPDATE TASK. For more

information, see the log file of the background job RSVBCHCK.PRD. The

following is the content of the summery error log file: The following

messages can be ignored in certain circumstances.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~CHECK OF UPDATE TASK ERRORS and RETURN CODE in RSVBCHCK.PRD

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~1 ETH010XRSVBCHCK: Check of open update requests

2EETG050 Update records still exist - Please process

A2EEMCEX 151 Entries for application "13" still exist in the extraction

queue ->

A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table ->

Long text" ""MC02M_0CGRSETUP""300"

A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table ->

Long text" ""MC02M_0HDRSETUP""300"

A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table ->

Long text" ""MC02M_0ITMSETUP""300"

A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table ->

Long text" ""MC02M_0SCLSETUP""300"

A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table ->

Long text" ""MC02M_0SCNSETUP""300"

A2EEMCEX 141 Struct. appl. "02" cannot be changed due to setup table ->

Long text" ""MC02M_0SGRSETUP""300"

A2EEMCEX 141 Struct. appl. "04" cannot be changed due to setup table ->

Long text" ""MC04P_0ARBSETUP""300"

A2EEMCEX 141 Struct. appl. "04" cannot be changed due to setup table ->

Long text" ""MC04P_0COMSETUP""300"

A2EEMCEX 141 Struct. appl. "04" cannot be changed due to setup table ->

Long text" ""MC04P_0MATSETUP""300"

A2EEMCEX 141 Struct. appl. "17" cannot be changed due to setup table ->

Long text" ""MC17I00CSESETUP""300"

A2EEMCEX 141 Struct. appl. "17" cannot be changed due to setup table ->

Long text" ""MC17I00ITMSETUP""300"

A2EEMCEX 141 Struct. appl. "17" cannot be changed due to setup table ->

Long text" ""MC17I00NTFSETUP""300"

A2EEMCEX 141 Struct. appl. "17" cannot be changed due to setup table ->

Long text" ""MC17I00TSKSETUP""300"

A2EEMCEX 141 Struct. appl. "17" cannot be changed due to setup table ->

Long text" ""MC17I30HDRSETUP""300"

A2EEMCEX 141 Struct. appl. "17" cannot be changed due to setup table ->

Long text" ""MC17I30OPRSETUP""300"

++++++++++++++++++++++++++++++++++++++++++++

It says that we can proceed by ignoring this error, but need your opinion

before we proceed as we dont want to land into trouble by ignoring such

warning

Rableen Singh

If there are many objects to be activated, the activation can take several hours (for example, if many packages are included).

To analyze why the activation phase is taking so long, you must first examine whether the upgrade is still running or it has hung :

Performance Analysis :

1. Check if log files in (DIR_PUT)/tmp are getting updated.

If the logs are still updated, the activation phase is still running. Several minutes may elapse between individual updates to the file.

2. Check in shadow system, transaction SM50.

At the start of the activation, it analyzes the topological inter-dependencies of the objects to be activated. This operation is only executed with one process and can also take some hours. Many entries are read from tables DD03L and DD04L.

3. After the topological inter-dependency calculation, the individual objects are activated. This step is executed with several processes (if several processes were configured).

The number of processes used are defined by parameters:

1. Parameter "parallel uptime processes" for the strategy "downtime-minimized",
2. Parameter "number of batch processes“ for strategy "resource-minimized" 
3. Parameters can be modified using “SAPup set stdpar". You need to stop SAPup first to change the parameters, then restart SAPup and continue the upgrade.

Performance in this phase mostly due to poor DB performance

For example, the runtime of interdependency analysis is largely determined by accesses to DD03L, DD04L and DD40L. This step may take several hours. If access to these tables are not optimized, runtime will be longer.

Sometimes it’s necessary to involve a DB expert checking the performance problem.

Some Known Errors :

1. Out of Memory Errors like TSV_TNEW_PAGE_ALLOC_FAILED

The error TSV_NEW_PAGE_ALLOC_FAILED means that more memory was requested because the program needed to expand an internal table, but it was not

available.

When Extended Memory is used up, the process will go into PRIV mode as it starts using Heap Memory  (or vise-versa).  No other user will be able to use this wp while it is in PRIV mode.  If there is enough heap for it to finish, you will not see the error TSV_NEW_PAGE_ALLOC_FAILED and the wp will be freed.

To fix this issue you just need to increase the abap heap limits on the system.

The parameters to control these memory areas are:

a)  em/initial_size_MB

     This is the EM area shared by all work process

b)  ztta/roll_extension

     This is the EM area for a single work process

c)  abap/heap_area_total

     This is the heap area shared by all work process

d)  abap/heap_area_dia

     This is the heap area for a single DIA work process

e)  abap/heap_area_nondia

     This is the heap area for a single non DIA work process

Please check the following Notes which describe this issue :

     020527  Runtime error TSV_TNEW_PAGE_ALLOC_FAILED

     1260912 - Memory overflow note: Dump TSV_TNEW_PAGE_ALLOC_FAILED

     1387739 - Out of memory errors during shadow system operation

You can use it as a reference to adjust the parameters abap/heap_area_total, abap/heap_area_dia and abap/heap_area_nondia.

If you need more than 6 GB for heap you may need to reduce the dataset that the transaction is being run on.

A Few Notes that Describe Common Activation Issues :

1. 1387739 - Out of memory errors during shadow system operation
2. 1674812 - Performance improvement for ACT_UPG
3. Oracle: 556764 Upgrade hangs in phase ACT_<REL>
4. DB2: 545281 DB2/390: Performance of DD activation

If you face an error during the ACT_UPG phase of your upgrade, you can find the list of objects in the ACTUPG.ELG file (default upgrade directory : /usr/sap/put/log).

For example, the errors may look something like this :

During the analysis, one should bear in mind that errors can also be caused by errors that occur during the activation of dependent objects. This means that the error messages for several objects may have one common cause.

Finding the cause of the Activation Error

For the purpose of analysis, you should first inspect which request/group of requests the object was a part of. You can check this in transaction se03 as follows :

i) Run transaction se03

ii) Select the 'Search Objects in Requests'

iii) Enter the object to be inspected and select the appropriate object type

iv) Select the checkbox for "Also Search for Subobjects (not for generic entry)"

v) For the status, select both the 'Modifiable' and 'Released' options

vi) Execute

The result will show you the transport request/group of requests this object belonged to.

Based on the kind of transport request it was a part of, you can classify what kind of object it is.

Possible results :

• The object occurs in an SAPKCCC* request                                                                   : Customer object
• The object occurs in an SAPKCCG request                                                                    : Generated object
• The object is contained in an SAPKCCR object list or was adjusted in transaction SPDD   : Modified object
• The object is contained in an SAP object list for an add-on or Support Package                 : Delivered object
• The object is not contained in any request but is activated as a dependent object              : Depenent object

Common Error Scenarios

Scenario 1 :

Object A uses object B, if B does not exist, A cannot be activated

There are two possibilities :

• The object shows in the activation log and could not be activated. Usually, this object will have a specific activation error associated with it. In this case, you must proceed to analyze the activation error in detail. You may need help from BC-DWB-DIC expert and can raise an OSS message in this component.

•   The object does not show in the activation log. In this case, you must first determine what type of object it is.
  • Generated objects : DDIC objects were used in the generating program of the source release that are no longer delivered in the target release. In this case you must find the object in the source release and ask the owner of the component how to proceed
  • Customer objects : Check if the object exists in the SAPKCCC request or why it does not exist there. Check if it exists in the source system.
  • SAP Object : The object used is an SAP object. You may be using an object deleted by SAP in the new release. You will need to adapt your own development. For the upgrade to continue, you can ignore this error.

Scenario 2 :

Duplicate/identical fields

• An object cannot be activated due to duplicate/identical fields
  • The table uses structures, Includes or append structures and the field occurs in several of these structures
  • The table may have been modified in the source release, for example, a field is created. But this field is delivered again with the target release. In this case, the modification adjustment in transaction SPDD is incomplete
  • Action : You need to delete the duplicate fields. Before that you can make a copy of the tables if they contain data. This needs to be activated and saved. You need to log in the shadow instance to delete the duplicate fields in transaction SE11
    
• An index cannot be activated because the same fields are already included in another index
  • One of the two indices is a customer index. In some cases, the customer is asked to create secondary indexes in the source release, this index is delivered with the new release. This will cause a conflict. The customer index is then superfluous.
  • Action : As indices have no influence on table entries, you can ignore these errors and continue the upgrade. After the upgrade, you can delete the duplicated index

For information on the Performance during the Activation phase, and some known errors that occur during this phase, you can check the following Document :

http://scn.sap.com/docs/DOC-50054

Hi SAP experts,

We are applying Service Pack to our system but we found we have some SPAU objects in red in our QA system. We didn't have same SPAU objects in DEV but suddenly same objects show up in QA.

Any idea why we are getting these objects only in QA and not in DEV and how to correct this?

Thanks,

Sunny Thakur

Dear ALL ,

I am performing an SAP update ECC6 EHP5 to EHP7 and I got stuck at Preprocessing phase with the following error:

Checks after phase MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_INC were negative!

Last error code set: Detected 10 errors summarized in 'SHDALLIMP.ELG'<br/> Calling 'D:\SUM\abap\exe/tp' failed with return code 8, check D:\SUM\abap\log\SAPup.ECO for details

ERROR: Detected the following errors due to error summary in SHDALLIMP.ELG:

1. D:\SUM\abap\log\SAPK-60523INLOCHRSAE.PRO:

3WETW000   Key field is not in NTAB.

3WETW000 different nametabs for table T7AEPBS22 (field OPR).

4 ETW000       Field is not in NTAB.

4 ETW000      table T7AEPBS22: entry in DB is 28 bytes smaller than in file.

4 ETW000      ... ignoring such differences.

2EETW000 key field T7AEPBS22-ITEXT contained the value 'Actions                  ': key field T7AEPBS22-ITEXT missing, key is truncated.

2EETW000 key field T7AEPBS22-SUBTY contained the value '8G': key field T7AEPBS22-SUBTY missing, key is truncated.

2EETW000 key of table T7AEPBS22 (0000000Actions                  8G) only valid up to offset 14 (in bytes). It's better to skip it.

2EETW000 key field T7AEPBS22-SUBTY contained the value '0450': key field T7AEPBS22-SUBTY missing, key is truncated.

2EETW000 key of table T7AEPBS22 (0002001                         0450) only valid up to offset 14 (in bytes). It's better to skip it.

3WETW000   Key field is not in NTAB.

3WETW000 different nametabs for table T7AEPBS22 (field OPR).

4 ETW000       Field is not in NTAB.

Choose action:

*Repeat phase MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_INC to continue at the point it stopped

*Exit program

Initialize phase MAIN_SHDIMP/SUBMOD_SHDIMP/SHADOW_IMPORT_INC to restart it from the beginning

INT *

Please help me solve this issue

Best Regards,

Hi Experts,

We are planning for ECC5.0 to ECC6.0 EhP6 Upgrade, I need some information about Disk space and RAM how much required, I checked with some documents was mentioned % wise, I can't explain thorugh my client, client expecting GB size.

1. Hardware upgrade,

2. Non-Unicode conversation,

3. DB Upgrade,

4. SAP EhP6 Upgrade,

5. DR Server Preparations,

6. Oracle DATA Guard Configurations.

Please provide what are the things its required  above activities related. I mentioned My Environments information's.

If provide above activities related documents, links, some ideas, I will give you some points.

Thanks & Regards,

Dear All,

please help me to install sap with sybas (sap version ehp7)

Regards,

Tamal

Hi Friends,

we are using SAP ECC6.0 EHP 3 with MSSQL 2005 ,

In my production server today we found DDIC_TYPE_INCONSISTENCY , COMPUTE_BCD_OVERFLOWdump  ...how t0 fix this dumps.