Upgrade ECC 6.0 EHP4 Skip Create Index

[Former Member]

Hi Experts,

I have a question about upgrade to ECC 6.0 EHP4 (SUN/Solaris 10, Oracle 10g). Recently, we have finished succesfully the upgrade in QAS system, and after a tuning procedure in the Oracle database, we have found that a Index in table BSIS (BSIS~1) is not neccesary so we proceed to delete it. This Index was created during upgrade process (downtime) and take a long time to finish.

The question is, how can we skip this create index in the upgrade process in production system?

Thanks in advance.

Best Regards

Juan Carlos Barraza

[Former Member]

Hi Sunny,

I checked the note, but this is for SQL Server and I'm in Oracle database, so I think that it's not the same case.

Best Regards

Juan Carlos Barraza

[Former Member]

Hi Rafael,

Where I need to manipulate the table TATAF... in sahdown instance?

BEst Regards

Juan Carlos Barraza

[former_member311580]

Hello Juan Carlos,

No, You should manage TATAF in "live" instance (not shadow)

regards,

Rafa

[sunny_pahuja2]

Hi,

check SAP Note 1346662 - Avoid index creation errors in 7.0x upgrades

Thanks

Sunny

[former_member311580]

Hello Juan Carlos,

Although it's a good practise not to manipulate the tables during the upgrade, you can handle the table TATAF.

The SQL statement to create the indexes are stored in the TATAF table, this table is built during prepare.

A possible recipe to overcome this problem could be:

1)Stop SAPup from UaGui prior to phase PARCONV

2)Logon to SAP system to check whether corresponding background job

has been cancelled. if not, stop the background jobs.Also check whether

there is tp or R3trans is still running. if yes, kill the process.

3)Remove the entry for the secondary indexes from table and TATAF. Check also table TBATG to remove possible related entries. (Best, take backup of both tables before manipulate)

4)Start SAPup to do/repeat the PARCONV phase.

5)After upgrade, refer to note 334224 to create the indexes from database level.

But this should be used at your own risk. This is not supported to avoid the index creation during the upgrade.

Regards,

Rafa