Error during upgrade of BW to NW7.4

[Former Member]

Hi

We are currently upgrading BW 7.02 to NW 7.4. I got the following errro during MAIN_NEWBAS/PARCONV_UPG step:

ERROR:

Detected the following errors:

# /install/BX1/SUM/abap/log/PD990404.BX1:

3 ETP000 ALTER TABLE "/BI0/ASRSA_DS100"

3 ETP000 MODIFY ("TCTHIGH" VARCHAR2 (003999),

3 ETP000 "TCTLOW" VARCHAR2 (003999))

3 ETP000

2WETP000 15:00:09: Retcode 1: error in DDL statement for "/BI0/ASRSA_DS100 " - repeat

2EETP345 15:00:21: Retcode 1: SQL-error "1404-ORA-01404: ALTER COLUMN will make an index too large"

2EETP345 in DDL statement for "/BI0/ASRSA_DS100 "

2 ETP000 --------------- DB-ROLLBACK() ---------------

2EETP334 15:00:21: error in DDL, nametab for "/BI0/ASRSA_DS100" not activated

I checked  the table and it is empty

SQL> select count(*) from sapsr3."/BI0/ASRSA_DS100" ;

  COUNT(*)

----------

         0

I also validated the table definition and it is correct

SQL> desc sapsr3."/BI0/ASRSA_DS100"

Name                                      Null?    Type

----------------------------------------- -------- ----------------------------

TCTUSERNM                                 NOT NULL VARCHAR2(36)

TCTAUTH                                   NOT NULL VARCHAR2(36)

TCTADTO                                   NOT NULL VARCHAR2(24)

TCTIOBJNM                                 NOT NULL VARCHAR2(90)

TCTSIGN                                   NOT NULL VARCHAR2(3)

TCTOPTION                                 NOT NULL VARCHAR2(6)

TCTLOW                                    NOT NULL VARCHAR2(180)

TCTHIGH                                   NOT NULL VARCHAR2(180)

TCTOBJVERS                                NOT NULL VARCHAR2(3)

TCTSYSID                                  NOT NULL VARCHAR2(30)

RECORDMODE                                NOT NULL VARCHAR2(3)

TCTADFROM                                 NOT NULL VARCHAR2(24)

I am not sure why SUM tool trying to modify the field definition in the statement to

MODIFY ("TCTHIGH" VARCHAR2 (003999),

Did anyone see this before? Any help?

Thanks

[james_wong]

Hello Nader,

Need help with an upgrade problem? Check out accelerate finding upgrade solutions:

http://wiki.scn.sap.com/wiki/x/6g3FGQ

For this issue, you can refer to SAP UPG Wiki page:

PARCONV_UPG - Software Logistics - SCN Wiki

Regards,

James

[ahmer_syed]

Dear All,

Thank you for helpful Post.

Same problem we have faced in our QAS BI EHP7 Upgrdae.

We are upgrading BI system to EHP4 - EHP7. In SUM 5.6 Execution Phase "MAIN_NEWBAS/PARCONV_UPG" following error occurred:

SQL-error "1404-ORA-01404: ALTER COLUM will make an index too large"

error in DDL, nametab for "/BI0/ACCA_00100" not activated

We have deleted the index and then repeat the phase it works.

drop index SAPSR3."/BI0/ACCA_O0100~0";

Before development lock and downtime following note may be the solution:

1879618 - Pre-upgrade measures for upgrade/update to 7.4

Best regards,

Ahmer

[Former Member]

I am glad that it helped. Thanks

[Former Member]

Note 1879618 did solve the problem.

Of course you have to restart SUM from the beginning because you have to implement the note before the Dev-Lock.

Thanks Nader for the solution!

Regards

Michael

Below some buzzwords for serach engines:

/BI0/ATCA_DS0100

/BI0/ATCA_DS0200

-2001-POS(41)

Key too long:TCTHIGH

Key too long:NODENAME

Key too long:TCTIOBJVAL

nametab not activated

2EETP345

/BI0/SD_SALE_GR1

/BI0/STCTIOBJVAL

[former_member185954]

Hello Nader,

I googled ora-1450 and found the following sap link, where a similar issue as yours is described.

Regards,

Siddhesh

[Former Member]

Hi

Although on MaxDB I have a similar error during BW Upgrade (same table, likely error cause, also more tables affected).

Did SAP respond already on the issue?

Regards

Michael

[Former Member]

Michael,

You on MAXDB and Nader on Oracle. Seems like a SAP delivery problem to me.

I guess you have already read the collective suggestions above although it won't help you when you move on to your next system 😞

KR,

Amerjit

[Former Member]

Hi everyone

My apology for the delay. I did not wait for SAP to respond, and they did not respond till now yet. However, I deleted the index for the table and the upgrade finished successfully. I only did that because the corresponding table had 0 lines.

This OSS note should help 1879618 - Pre-upgrade measures for upgrade/update to 7.4

[former_member189797]

Hello Nader,

The error seems to be coming, because of the new field attributes have so long field length that the index on the table exceeds the oracle limit. Table seems to be related to BW so you could check with
BW colleagues about the use of the table and if they suggest then you could drop the index and this
shall allow you to continue with the upgrade.

Thank you.

Best Regards,
Gaurav Pandey

[Former Member]

Thanks, I also think 1879618 will help.

I'll update as soon as I have a result.

[former_member182657]

Hi Nader,

Try to drop the index & then increase the length of column,but for this i suggest you to raise SAP OSS before performing the steps as i doubt you would not be able to create index after that .(Here i could be wrong so i still suggest you to raise OSS in parallel ).

Regards,

[Former Member]

Of course I opened an OSS message to SAP.

My previous plan was not complete ... I wanted to say that I want to:

• Drop the index
• Proceed with the upgrade
• After the upgrade is finished, I will revert back the field definition to 180 instead of 3999
• Recreate the index

Even though this will work, I still need a solution from SAP because I am not planning to do that in production.

[former_member182657]

Yes Of course you need to wait for SAP revert before performing the action in PRD system

I am not planning to do that in production.

[Former Member]

Hello Nader,

The error message you are getting is telling your clearly what the problem is (concatenated index will exceed 255).

What is odd is the:

MODIFY ("TCTHIGH" VARCHAR2 (003999)

MODIFY ("TCTLOW" VARCHAR2 (003999)

Please run the following SQL (post output here) which will describe all indexes on the table in question. From that you will be able to determine which index(es) is/are impact by the ALTER COLUMN.

Select table_owner, table_name, index_name, column_name, COLUMN_LENGTH

FROM dba_ind_columns

Where table_owner='SAPSR3' AND table_name='/BI0/ASRSA_DS100'

Order by table_owner, table_name, index_name, column_position ;

There is a way forward with this but in such circumstances  I would open a message with SAP anyway (to understand why).

Kindest Regards,

Amerjit

[Former Member]

Thanks Amerjit

The error message is clear that it is attempting to modify 2 fields to a very high value

TCTLOW   NOT NULL VARCHAR2(180)

TCTHIGH  NOT NULL VARCHAR2(180)

What are you suggesting as a workaround?

[Former Member]

I am thinking of dropping the index, finish the upgrade then recreate it.

[Former Member]

Hello Nader;

As you have already confirmed that the table is empty, yes you can drop the index.

Please post the output of the SQL I gave you in the earlier reply anyway. Just curious to see which index the fields are part of.

I'd also do a "where used" check of the fields in your production system to see if other tables may be impacted by the DDIC change.

The above will get you moving forward and then SAP can tell you why this is occurring.

Close out this thread if you are happy with the answer(s).

Good luck.

Amerjit

[former_member182657]

Hi Nader,

error in DDL, nametab for "/BI0/ASRSA_DS100" not activated

Could you check for the activation of /BI0/ASRSA_DS100 with SE11,if not active then try to re-activate the same & retry the phase again,If still issue persists please provide complete index details on /BI0/ASRSA_DS100

select INDEX_NAME, OWNER, TABLE_NAME from dba_indexes where TABLE_NAME=/BI0/ASRSA_DS100 ;

As per log shared issue could be related with index

SQL-error "1404-ORA-01404: ALTER COLUMN will make an index too large" 

Regards,

[Former Member]

Hello Gaurav

The instance is locked for upgrade at this point. Here's the output of the select command:

SQL> select INDEX_NAME, OWNER, TABLE_NAME from dba_indexes where TABLE_NAME = '/BI0/ASRSA_DS100' ;

INDEX_NAME           OWNER     TABLE_NAME

----------           -----     -----------------

/BI0/ASRSA_DS100~0   SAPSR3    /BI0/ASRSA_DS100