Conversion of indexes during upgrade

Hello everybody
I am searching as well in SAP Notes but perhaps someone has had the same problem. During the upgrade of one R/3 4.6C system to NW there is a phase when the process tries to convert indexes to "non padded". I want to tell my colleague who is responsible for the basis work how he can circumvent this phase. I do not remember properly but I think that I have read something like "there will be a file with the names of the indexes generated. If you want to circumvent the conversion delete the entries and go on". Has somebody an idea where this is located ( the hint and/or file ) and if one can do this even after the process already had been started ?
Thank you very much
Martin Ketterer, Alfred Kaercher GmbH Germany

Hello,
the conversion to NOT PADDED during the upgrade is optional. There is a dialog during phase INITPUT_PRE where you decide on its usage. The actual conversion is then done during phase STOPSAP_IUPG. Note that you can specify a list of all indexes to beconverted in phase SPACECHK_INI.
Alternatively, it is also possible to run transaction DB2_IXFIX after the upgrade is finished (for details refer to SAP note 793204).
Best Regards,
Bernd Kohler.

Similar Messages

I am trying to upgrade EPM 8.9(8.49.23) to EPM 9.1 (8.53.08). During dataconversion step the AE process finished succssfully in few seconds. When i see the log it says "There are no conversions to run for upgrade path PF89 (18028,10003)". Please let me kn

I am trying to upgrade EPM 8.9(8.49.23) to EPM 9.1 (8.53.08). During dataconversion step the AE process finished succssfully in few seconds. When i see the log it says "There are no conversions to run for upgrade path PF89 (18028,10003)". Please let me know why it didnt do any conversion. Am i missing something?

yes, that app engine didnt inserted any rows. So now when i tried to drill down i found that there was no data in the "new demo" database on table UPG_DATACONV. That is the reason for all this.
When i applied required for upgrade patch in demo it said couple of patch already exists so those update i skipped. Now when i check upd877654 has a step which imports the data in this table. my change assistant told that the update is already available in my demo so i skipped. Now i am not sure what to do.
I tried reimporting the data and running the analyzer again. But worried that there can be any issues due to this.

How to adopt the index changes during upgrade

Hi All,
Please let me know how to adopt the standard index changes during upgrade. We are not able to change using SPDD.
Regards
Anil Kumar K

Hi Micheal,
I have posted one query can you answer for that also.
Actually we are facing a problem in activating the table COEP. It is saying duplicate field name exist for GEBER. But we have checked all the tables and structures.But no duplicates.
Please help us..
Regards
Anil Kumar K

Error during Upgrade from 4.6c to ECC 6.0

Hi All,
We are facing an error when upgrading from 4.6c to ECC 6.0. We are facing this error on the table COEP - runtime object inconsistancy. What we found is there is ERP upgrade has created new extra fields in the table. In log file the error is specified as : Duplicate Field name, But we not able to find the duplicate field name in the table. Please kindly help as early as possible. The upgrade process is stuck.
Regards
Anil Kumar K

Hi Anil,
Is this issue fixed? Can i know how you fixed it?
replied to your message Re: How to adopt the index changes during upgrade.
Thanks,
Somar

Guidelines to reduce downtime during upgradation R/3 to ECC6

hi all........
Here we implemented SAP R/3 4.6 in the year 2005.
Now we are planning to upgrade our system to ECC6 unicode .
We are planning to upgrade our Production and Development system to SAP
ERP6 EHP4.As part of the upgradation; we had setup a test system with the
following details:
Sun Fire 480R (UltraSparc III + 1.05GHz x 4 processor)
Memory 16 GB and Storage : Sun CSM 200 SATA HDD
SAP R/3 4.71, single code pages 1100, Oracle 9.2.0.8.0, Solaris 9
Test system with 1.2TB data copied from Production System.
We have upgraded the test system using CU&UC method ( Upgrade Guide SAPERP6.0 EHP4 SR1 Abap ). It took 2 days downtime for full upgradation and 8 days for Unicode conversion.
Requirement :
To Upgrade the current systems without any additional hardware to SAP
ERP6 EHP4 Unicode.
As a part of the above, the cluster has to be upgraded to Sun cluster
3.2, and operating system to Solaris10 (5.10)
We are having the following queries:
1. With only 1.3 TB data, we feel, the down time of 10 days is not
realistic.Though we had not deviated from the above mentioned upgrade
guide, what could be the reasons for this down time of 10 days?what arethe affecting factors? Kindly suggest the ways by which we can get
reduced downtime . The referred Notes are (784118, 855772, 952514,
936441, 954268, 864861 ) still we are unable to pin point the reason. Abreak up of this down time is given below for reference.
2. Are there any alternate approved upgradation methods to reduce
downtime in our present set up? (details of present set up is given below)
3. How to calculate the down time with reference to(sapnote:857081) to in
our setup
Current Production System Details :
System : Sun Fire V890
Processor : 1.5GHz UltraSPARC IV+ processors -- 8no.s
Memory : 64 GB
Storage : Sun Storagetek 6180: HDD FCAL(16 no.s x 450 GB)
15,000-rpm 4 Gb/sec 4GB data cache (Storage connected to server using FC
cable)
SAP : R/3 4.71 single code pages 1100
Database : Oracle 9.2.0.8 data-size is around 1.3 TB
OS : Solaris 9 (5.9)
Cluster : Sun cluster 3.1
Network : 1GB ethernet (1000BASE-SX)
Architecture : Application and database server on Same system
SAP Development system specification same as the above with 187 GB data
size. PRD and DEV systems are on cluster; PRD failover to DEV system.
The time taken for test upgrade - brief details:
1. Kernel upgraded 6.20 to 6.40 (2hours)
2. Oracle Upgrade to 10.2.0.4.0 (3.30 hours)
3. SAP UPGRADE Preparation-Apply support packages (18 hours)
4. Downtime Phase and Pre-Processing and Finalization Phase (20 hours)
5. Unicode Conversion-Taking DB Export 109GB(Almost 10% of total DB
size)(98 hours)
6. Installation of unicode system using export (95 hours)
Looking forward to hear from you.
Best Regards,
Rajeesh K.P

Hi .......
i am very sorry for late reply...............................
The time taken for test upgrade - brief details:
1. Kernel upgraded 6.20 to 6.40 (2hours)
2. Oracle Upgrade to 10.2.0.4.0 (3.30 hours)
3. SAP UPGRADE Preparation-Apply support packages (18 hours)
4. Downtime Phase and Pre-Processing and Finalization Phase (20 hours)
5. Unicode Conversion-Taking DB Export 109GB(Almost 10% of total DB
size)(98 hours)
6. Installation of unicode system using export (95 hours)
2 days downtime means the sum of time used for above 4 activities ..........................
as you suggested we can do the same 4 different down times......................
Unicode Conversion-Taking DB Export 109GB(Almost 10% of total DB size) is taking a continuous down time
of 98 hours (4.5 days ) (Activity 5)+ installation of Unicode system using the Unicode export is taking 95 hours 4.5 days
(Activity 6)
i think the we have to do activity 5 & 6 in a single stretch with out users, so it will take a continuous down time of 9 Days
With this in mind I have a few questions for you to clear a little bit more all the problem.
Q:1 Did you use more parallel jobs during Downtime than default? and I mean real Downtime where the SAP system is taken down
No.we have used default number (3 ) of parallel jobs during downtime
Did the system allow you to use ICNV (incremental converssion) for some tables?
yes we may use ICNV
Can you separate the Unicode conversion to a different weekend? or is a must for some business reason?
Yes , we can separate the Unicode conversion to a different weekend , it will not affect our business
Did you save the post download Report so you can see what are the most time consuming phases?
i am not so clear about this question , we have made an activity chart with time duration as per the test upgrade. Or how we can save the post download report from the system
Looking forward to hear from you.
Best Regards,
Rajeesh K.P

Adjust parameter DB2COMM, informed during upgrade EHP4

During upgrade ECC6 to EHP4 DB2 9.5 AIX 5.3, in phase extraction - PREP_INIT / CHECKPROF_INI, the message appeared:
"The following DB2 registry parameters are marked as overwritten:
DB2COMM
Only in well founded exceptions the setting of a DB2 registry variable should deviate from the implicit setting of DB2_WORKLOAD=SAP! Please check if this is the case for the parameters listed above!"
Checking db2set-all: DB2COMM = TCPIP [0]. I understand should be DB2COMM = TCPIP <DB2_WORKLOAD>.
How can I set this parameter?
I tried running db2set DB2COMM = TCPIP <DB2_WORKLOAD> without success.
tks

Hello Emerson,
Could you try,
db2set -i db2instancename DB2COMM=TCPIP <DB2_WORKLOAD>
Try to refer the link -
http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=%2Fcom.ibm.db2.udb.admin.doc%2Fdoc%2Fr0002025.htm
Thanks

Table Maintenance, during upgrades

Experts,
How do we handle table maintenance generator screens and t-codes during upgrades (for Z tables)? Do they come up in the SPAU list post upgrade or is there anything to do in SPDD during ACT_<version> stage?
Tx, in adv.

Hi,
Shaji is correct. Table maintenances are corrected after the upgrade is applied by the BASIS team. You will just have to re-test those table maintenances.
If you are also doing Unicode Conversion as well. Then you need to make sure to set Unicode Checks Active for the function pool related to your table maintenance.
i.e you have in table maintenance stored in function group ZMYFUNC. Then you need to go to the "generated" function pool SAPLZMYFUNC and set Unicode Checks Active.
Unless your table maintenances have lots of custom logic in them, you generally would not encounter any errors at all.

Data conversion ECC 6.0 Upgrade

Hi SAP Guru's.
My Client is intend to do a ECC6.0 Upgrade from 4.6. My goal is find out is there any data conversion requirement is needed for the project. My Client is doing a technical upgrade and then a full upgrade. Can anybody guide me what are the possible data conversions we can expect for the upgrade.
Thanks
SN

Dear Sankara,
When it is a technical upgrade from a lower version to ECC6.0, many objects like includes, Function modules, reports, OSS notes, DDIC objects, BDC/Print programs, SAP scripts, screens will get affected due to the upgradation. So we need to check with all these objects.
We will encounter short dumps while executing certain programs. This may be due to the usage of obsolete function modules or Unicode errors.
The BDCs in the upgraded version will become defective as many of its screen field names will be changed during version change.
Program texts of many programs will be lost. They have to be restored.
In case of tables, enhancement category has to be provided.
There is a possibility of losing the variants during upgradation. So care should be taken to retain them before upgradation.
ECC6.0 is case sensitive, so many of the interface programs will fail to transfer (FTP) files between systems. These objects have to be changed so that the commands passed to the external system be UPPERCASE.
So a developer should be aware of the following:
Unicode programming is followed in ECC6.0. So we need to be aware of it to rectify certain Unicode errors which are likely to occur.
You have to run the transactions SPAU & SPDD to check for list of standard & custom objects that needs modification in the upgraded version.
Check the below link to find more details on usage of SPAU & SPDD transactions
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
Should be aware of the objects that have become obsolete in ECC6.0. They have to be replaced by appropriate ones.For eg.:
--> The WS_* function modules have been replaced by GUI_* FMs in ECC6.0 as WS_* FMs have become obsolete from 4.7
-->Tables like TVARV & TTREX have been replaced by TVARVC & TTREXN respectively in ECC6.0.
In case of tables, we need to specify the Enhancement category.
Due to upgradation, we will lose out some variants. So we should take a back-up before proceeding with the upgradation.
In case of BDC programs, some field names will be changed. So they have to be named appropriately.
Please check with the below links for more details:
SAP Upgrade guide:
http://www.thespot4sap.com/upgrade_guide_v2.pdf#search=%22upGRADE%20STEPS%20-%20SAP%22
From ABAP's perspective, the following link helps you:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca
For technical upgrade inputs:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/07/upgradeFROMR3TOmySAPERP-PARTII&
https://wiki.sdn.sap.com/wiki/display/profile/UPGRADEFROMR3TOmySAPERP-PARTIII
Do award points if you found them useful.
Regards,
Rakesh
P.S. you can send me a mail at my mail id [email protected] for any specific details

Error while runnning autoconfig on apps tier during upgrade

Hi,
Error while runnning autoconfig on apps tier during upgrade from 11.5.9 to 11.5.10.2
below is the error message.
Enter the APPS user password :
The log file for this session is located at: /u01/app/tinst/tinstappl/admin/TINST_dba5/log/05031134/adconfig.log
AutoConfig is configuring the Applications environment...
AutoConfig will consider the custom templates if present.
Using APPL_TOP location : /u01/app/tinst/tinstappl
Classpath : /u01/app/tinst/tinstcomn/util/java/1.6/jdk1.6.0_18/jre/lib/rt.jar:/u01/app/tinst/tinstcomn/util/java/1.6/jdk1.6.0_18/lib/dt.jar:/u01/app/tinst/tinstcomn/util/java/1.6/jdk1.6.0_18/lib/tools.jar:/u01/app/tinst/tinstcomn/java/appsborg2.zip:/u01/app/tinst/tinstcomn/java
Using Context file : /u01/app/tinst/tinstappl/admin/TINST_dba5.xml
Context Value Management will now update the Context file
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/jdbc/OracleDriver
at oracle.apps.ad.util.DBUtil.registerDriver(DBUtil.java:153)
at oracle.apps.ad.util.DBUtil.<init>(DBUtil.java:102)
at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.getDBConnection(FileSysDBCtxMerge.java:759)
at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.initializeParams(FileSysDBCtxMerge.java:147)
at oracle.apps.ad.tools.configuration.FileSysDBCtxMerge.setParams(FileSysDBCtxMerge.java:128)
at oracle.apps.ad.context.CtxValueMgt.mergeCustomInFiles(CtxValueMgt.java:1762)
at oracle.apps.ad.context.CtxValueMgt.processCtxFile(CtxValueMgt.java:1579)
at oracle.apps.ad.context.CtxValueMgt.main(CtxValueMgt.java:709)
Caused by: java.lang.ClassNotFoundException: oracle.jdbc.OracleDriver
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
... 8 more
ERROR: Context Value Management Failed.
Terminate.
The logfile for this session is located at:
/u01/app/tinst/tinstappl/admin/TINST_dba5/log/05031134/adconfig.log
Please let me know your suggestions to resolve this issue.
Regards,
Sreenivasulu.

Hi,
DB tier autoconfig was successfully completed.
We have already checked the above mentioned metalink ID's, but still the issue is same.
Can you please advice any other solutions.
Regards,
Sreenivasulu.

Error in transaction KEA0 during upgrade

Dear All,
During upgrading the custmer system from 4.7 to ECC 6.0 we found some error in the transaction KEA0 while trying to activate the cross client for an operating concern.
The activation logs says that there are the syntax errors in the gereted subroutine pool: RK2O0100.
I however corrected the error and activated the code but again when I am trying to execute the same it gave me the same error and when I go to the sub routine pool I found that the changes are again undone and the previos version is activated. This happens repeatedly that the code is corrected and activated by me and says no error and ones I log off and login again it says the same error.
Help will be appriciated.
Thanks iin advance....
Abhi...

Dear Raymond,
Thankds for your help..........
I tring to run RKEAGENV it shows the error message with STOP button saying that the field WTGBTR not contained in the nametab for table CE1E_B1 and when Io run RKEAGENF it gives a short dump saying that entry for CE10100 is not allowed for TTABS.....
Please help.

Disck Space not enough during upgrade CUCM 9.1(2)SU1 to 9.1(2)SU2a

Hi,
I face an issues during upgrade my current CUCM 9.1(2)SU1 to 9.1(2)SU2a, it show with this error message "There is not enough disk space in the common partition to perform the upgrade, for steps to resolve this condition please refer to CUCM 9.1(1) release notes or view defect CSCuc63312 in bug toolkit on Cisco.com". I had check the bug id and got 2 way to do it:-
1. reduce the amount of traces on the system, but I not ready want to do this
2. install a COP file name: ciscocm.free_common_space_v1.0.cop.sgn
If I select option 2, will it have any risk? Is it mean 9.1(2) - inactive version will be clear out from disk space or it will clear out 2 version - active and inactive version from disk space?
I need have some advice on this before I perform.
Thanks.

Hi,
As per the following link
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/9_1_1/CUCM_BK_R6F8DBD4_00_release-notes-for-cucm-91/CUCM_BK_R6F8DBD4_00_release-notes-for-cucm-91_chapter_011.html
You will not be able to switch to the previous version after the COP file is installed. For example, if you are upgrading from Cisco Unified Communications Manager 9.0(1) to Cisco Unified Communications Manager 9.1(1) and the previous version is Cisco Unified Communications Manager 8.6, the COP file clears the space by removing the 8.6 version data that resides in the common partition. So after you apply the COP file, you will not be able to switch to the 8.6 version."
Additionally, regarding the first option, if you do not want to reduce the tracing levels you can still delete some old traces using RTMT which gives you an option of deleting the traces from the server as well as transferring / downloading them to your pc simultaneously by checking the 'delete from server' option on last page of log file collection option.
HTH
Manish

Encounter a problem during upgrade sap r/3 4.7 to ecc6

Hi expert:
i encounter a problem during upgrade sap r/3 4.7 to ecc6
in START_SHDI_FIRST step.
here is the error msg~
MSSCRESPDEFN.LOG
Msg 2812, Level 16, State 62, Server Jack, Line 6
Could not find stored procedure 'dbo.sap_upg_getrelease'.
setuser
i checked MS SQL DB and found out that i only got 'erp.sap_upg_getrelease' but not dbo owner.
can any one tell me how to solve this problem?~
thanks.
Regards
Jack Lee

It's the kernel for the shadow the correct?.
Regards,
Alfredo.

MAIN_SHDRUN/ACT_UPG ends during upgrade

During upgrade from CRM 6.0 to 7.0 EHP1 MAIN_SHDRUN/ACT_UPG phase ends.
In ACTUPG.ELG file I see:
******* LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DDIC ACTIVATION ERRORS and RETURN CODE in SAPACCI702.CRT
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1EEDO519X"Table" "CRMST_QUERY_OPP_BTIL" could not be activated
1 ETP111 exit code
I read SAPACCI702.CRT:
3 DDT012XAktiviere Tabelle "CRMST_QUERY_OPP_BTIL"
3 DDT402 Append-Struktur "ZCRMST_QUERY_OPP_BTIL" an Tabelle "CRMST_QUERY_OPP_BTIL" angefügt
2WDDT191 Erweiterungskat. "3" möglich, aber Include oder Subtyp ist noch unklassif.
1EDDT963 Feld "PROD_HIERARCHY" in Tabelle "CRMST_QUERY_OPP_BTIL" ist doppelt (Bitte überprüfen)
3 DDT013 Tabelle "CRMST_QUERY_OPP_BTIL" wurde nicht aktiviert
3 DDT014XAktiviere abhängige Tabelle "CRMST_QUERY_OPP_BTIL"
3 DDT402 Append-Struktur "ZCRMST_QUERY_OPP_BTIL" an Tabelle "CRMST_QUERY_OPP_BTIL" angefügt
2WDDT191 Erweiterungskat. "3" möglich, aber Include oder Subtyp ist noch unklassif.
3 DDT038 Aktivierung abhängige Tabelle "CRMST_QUERY_OPP_BTIL" erfolgreich
Oh... in german language... it's a problem for me. How can I check this structure? how?
Have you got any suggest?
Regards.

Hi Ganimede,
i have the similar kind of error can you please explain the steps for deleting the entry you have specified...
would be greate if you coulkd reply earliest
Thanks and Regards
Amar Ghuge

How to track changes made to the standard objects by SAP during upgrade ?

Hi All,
Can any one of you please let me know if there is any straight forward method to find any change made to the standard objects by SAP in different versions ?
Like for eg, during upgrade from 4.6c to ECC 6.0.
Thanks in advance.

> For eg , if SAP has made any change in the standard transaction IE02, in ECC 6.0 how will we come to know those changes?
There are two sources for that:
The "Solution Browser" (http://solutionbrowser.erp.sap.fmpmedia.com/) which lists the differences between source and destination release and the release notes (http://service.sap.com/releasenotes). You'd need to read here all those from 4.6 to ERP 6.0 (so 4.7, ECC 5.0 and ERP 6.0) to find out the behaviour changes.
Markus

Can we activate Classic General Ledger in ECC6.0 during upgrade from 4.6C

Dear SAP Gurus,
Greetings
My Client's technical team had upgraded their system from 4.6C to ECC6.0 and they had activated classic GL instead of New GL. And they had also activated classic withholding tax in place of Extended Withholding tax.
They are facing some error during posting of transactions (like generation of excise invoices, posting of WHT transactions, etc.) I told that it can be a reason of not activating New GL.
Is my understanding correct...?? Can we activate classic GL during upgrade from 4.6C to ECC6.0...??
In case of a new client built (with ECC6.0), can we activate the classic GL instead of the New GL..??
Does the system will work correctly in the long run if they had activated classic GL and classic WHT...??
Please clarify. Thanks in advance for your time and efforts
Regards,
Chaps
P.S. Points will be awarded for answers !!

Hi,
I think that you should read long text of OSS note 999614 carfully and you are
aware of the fact that you will have additional migration efforts in
case you need to migrate to new G/L later on.
In case you are convinced that this is the best way please feel free
to deactivate new G/L as described in note 999614.
Please make sure that you deactivate new G/L in all clients of your
new system in case there were already client copies done.
Yes this is possible and I would not automatically assume that
error during posting of transactions are due to New GL not being activated.
Note 756146 documents the issue and possible repercussions
of using Classic GL.
In the case of a new installation the new G/L accounting
is active by default in ERP. In principle, the use
of the classic GL is also possible for new customers, however,
SAP does not recommend it since this requires an additional
migration expense in later years.
Regards,
Aidan

Conversion of indexes during upgrade

Similar Messages

Maybe you are looking for