Performance problem on MaxDB.

[Former Member]

Hi,

In Oracle 10.2g before database migration to MaxDB 7.8 data loading to Z-Table (Customized tables) use to take 15min. But in MaxDB 7.8 it is taking now 3 hrs. We never created secondary indexes on Oracle for Z-Table. But after creating the secondary index on MaxDB data loading is taking 7 min. Does it mean that MaxDB is not able to manage partial Key?

And also we were not able to find any difference on the Oracle system as far as table/view definition, so our conclusion is Oracle algorithm/calculation to access data work differently than MaxDB.

Please let us know if there are any parameters for to manage the partial key? And also without creating the secondary indexes on Z-Tables it is possible to get the same performance as with Oracle?

Thanks,

Narendra

[former_member184473]

Hello Narendra,

Check if you have the recommended parameters:

[1111426 - Parameter check for liveCache/MaxDB instances|http://service.sap.com/sap/support/notes/1111426]

Regards,

Eduardo Rezende

[Former Member]

Hello Eduardo,

We have already followed the note 1111426 and run dbanalyzer for parameter recommendation and we have already done those parameter changes.

But I want to know why we want to create secondary index on MaxDB for Z* Tables as we never use to create the secondary indexes on Oracle 10.2g database.

Thanks,

Narendra

[former_member184473]

Hello Narendra,

You can use transaction SE11 which keep the consistency between the ABAP and database dictionaries.

Regards,

Eduardo

[Former Member]

Hello Eduardo,

I didnu2019t get you u201Ctransaction SE11 which keep the consistency between the ABAP and database dictionariesu201D

As I told we never use to create manually the secondary index on Oracle database. But without creating the secondary index on MaxDB 7.8 it takes 3 hrs for data loading. If I create a secondary index on MaxDB then it takes 7min. But we donu2019t want to create manually the secondary index on the Z* tables. Is there any requirement for MaxDB we have to have secondary index for Z* tables?

We don;t know how indexing works on MaxDB.

Thanks,

Narendra

[former_member184473]

Hello Narendra,

Instead of creating manually the index (directly in the database) you can use transaction SE11 which will create it in both dictionaries (ABAP and DB).

Check the following website:

http://maxdb.sap.com/doc/7_8/44/bc67c695dc1579e10000000a114a6b/frameset.htm

Regards,

Eduardo

[Former Member]

Hello Eduardo,

I know how to create the indexes and also we have set the MaxDB parameter Automatic Recreation of Bad Indexes to ON.

My question is simple why after creating the secondary index on Z* tables data loading performance improved in MaxDB. As we never use to create the secondary index on Z* tables in Oracle Database. Is it requirement of MaxDB to have secondary index on Z*tables?

Thanks,

Narendra