cancel
Showing results for 
Search instead for 
Did you mean: 

Add new infoobject to LARGE ODS

0 Kudos

I am adding new infoobject to existing ODS. This ODS has over 100million records. It takes forever to add the infoobject.

I think the issue is SAP does not allow nulls so actually drops all the data and reloads with the new field populated with spaces.

In our environment the problem is noramally not an issue in DEV since there is limited data but when transporting through the landscape the transport takes forever since in other environments we have lots of data.

I proved it is not just a transport issue by doing it directly in a system with over 100million records - still took forever and no transport involved.

Anyone else had a similar problem with large ODS's and any workarounds?

Thanks.

Accepted Solutions (0)

Answers (3)

Answers (3)

0 Kudos

Charan - I think you miss the point.

Olivier - we are using Oracle. I know I can always manually do it in SE14 etc but our security is so tight I could only do this in DEV. We need to capture change in a transport and move through landscape. I suppose SAP always drops and reloads data in the background during the activation step. Most people (eg Charan) don't realise this since it noramally happens very fast but on very large ODS it takes a LONG time.

Former Member
0 Kudos

SE14 will do the same...

it is the RDBMS which does that internally; I did once this with a huge table in Oracle with and without logging the operation; the perf is way much better.... on the other hand it's bit risky therefore we usually plan this accordingly (week-end) and just wait until this is finished....

another option is to extract the whole ODS into PSA; delete it remove secondary indexes, add the IObj and then reload the ODS from PSA and rebuild indexes; this is actually the most secure way, again you'll need to be patient...

Finally you could perhaps logically partition your ODS in order to avoid having such monster in your DB although 100 mio is still OK; it really becomes a problem when above 500 mio records...

Olivier.

Former Member
0 Kudos

Hi,

that's a RDBMS issue.... I would ensure to have a proper backup of your database and schedule this activity offline. You'll switch of logging for this, it should be faster...

Which RDBMS are you using?

that's one of the alternatives...

hope this helps...

Olivier.

Former Member
0 Kudos

Hi,

ODS is nothing but a flat table you can add info object to it and transport it, if you want history data for this object then only you need to delete data and reload it, else it will be filled from the day it is added and activated.