ORA 2168: Create table with FREELISTS=000 and FREEGROUPS=00

[Former Member]

Hi All,

We are operating R/3 4.6C (SAPKB46C46), with HP-UX 11.23. Oracle

10.2.0.2. We started an upgrade (4.6C->6.0 sr2) on development system

(DR2). During the import phase (TOOLIMPD3) the Prepare was stopped with

Oracle error ORA 2168. The upgrade prepare wanted to create

QCM8PAT03_SDA table with FREELIST=000 and FREEGROUP=00, but it

couldn't. It seems the ASSM doesn't allow these values of the

parameters.

In SAP note 627246 is written that we should apply SAP Basis

packages.After point in time restore of beginning of the upgrade we

started to import 4.6C basis patches 47-52. During the phase

IMPORT_PROPER we got the same oracle error (invalid value of freelist)

when the package manager wanted to create different kind of indexes.

Kind Regards,

Ferenc

[Former Member · Accepted solution]

Hi,

Please check the following note from service marketplace.

It shows some code changes in one of the ABAP report.

Try to change that report.

Note 627246 - Error when you create new objects. ORA-02168

Regards,

Payal

[Former Member · Accepted solution]

Hi,

Thanks a lot.

In fact we've also found this note before. Also Note 868159 - Partitioning, LMTS and ASSM in Release 46C. First I implemented 868159, after 627246.

It is strange that upgrade guides don't write the EXACT order:

1.) 4.6C Basis Patch import (I think in level 05.2006 is ok)

2.) Oracle 9.2->10.2

3.) Upgrade 4.6C-> ECC6.0

If we had been done just 2), 3) (without 1))we got the error message, and in this point you are not able to do anything just to restore database, and implement notes after 1) and 3)

It seems old R/3 basis doesn't work with Oracle 10.2. Does it a SAP note about it?

Regards,

Ferenc

[Former Member · Accepted solution]

Hi,

You can check it on www.service.sap.com/pam (Product Availability Matrix).

THought I have checked for your OS and SAP version and Oracle 10.2 can work on that.

So it is feasible.

Regards,

Payal

[fidel_vales · Accepted solution]

Hi,

If you applied the notes <b>after</b> getting the error you will not solve the problem.

The statements to create the table/indexes are already generated and stored on the table DDSTORAGE. You should check this table with SE16 and modify all entries with FREELISTS or FREEGROUPS

[stefan_koehler]

Hi Ferenc,

> It seems the ASSM doesn't allow these values of the parameters.

No that is not correct. If you are using LMTs with ASSM - it is valid to use the freelist/freegroup parameter, but they are ignored by oracle.

How do you migrate? With sapinst (and automatic migration monitor) or manual with migration monitor or distribution monitor?

Maybe the table is included in some <TABART>.SQL files ... so you can modify the syntax.

If i have a look at your first posting the syntax for freelists / freelist groups is wrong. For the right syntax have a look here:

http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/clauses009.htm

Regards

Stefan