Skip to Content
0

SAP BOE BI 4.2 SP4, Data Base CMS Table CMS_InfoObjects7 is TOO BIG

Sep 18, 2017 at 12:44 PM

291

avatar image
Former Member

Hi,

I am having an issue after installing SAP BOE BI 4.2 SP4, the problem is that the InfoObjects7 table is too big (having more than 15 000 000 rows) and 20Gb for the CMS DB.

Anyone have the same problem ?

Regards

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Denis Konovalov
Sep 18, 2017 at 12:50 PM
0

That is highly in-usual.
How many objects is in your repository ?
If this is brand new install and no pre-existing content present - try to re-initialize the CMS DB.

Show 6 Share
10 |10000 characters needed characters left characters exceeded
Former Member

@Denis, In adminTools i got 11388 rows (select count(*) from ci_infoobjects) with the same query in SybaseCentral (select count(*) from dba.cms_infoobjects7 I got 23327867 rows. The problem is figured in both new install and update. Regards

0

Please clarify on what do you mean by problem is seen in new install and update ?
With new install - do you create new CMS DB or connect to existing one ?
If this happens when you're creating new CMS DB - then this is something your DB doing , have you checked with DBA ?
If this is only with existing CMS DB's - maybe you have lots of schedules or a lot of CR repo objects.

You should investigate this with SAP support, under BI-BIP-ADM component.

0
Former Member

With new install - I create new CMS DB, the default SQL Anywhere DB on the install so I did not administrate any DB.
I have no Schedule reports.

0

Definitely should investigate this via support incident. This shouldn't happen with default, new CMS DB.

0
Former Member
Denis Konovalov

Ok Thank you, I sent a support incident for this issue. I will let you know the answer .

Regards

0

CMS_InfoObjects7 will have entries for all the infoobjects (CI_Infoobjects, CI_Appobjects * CI_Systemobjects). As Denis suggested please open an incident and work with SAP support.

Thanks

Mani

0
Joe Peters Sep 18, 2017 at 07:07 PM
0

The number of rows in cms_infoobjects7 will be approximately close to the sum total of rows in the CMS. Try the following query in AdminTools:

select count(si_id) from ci_infoobjects,ci_appobjects,ci_systemobjects

If the result of this query is significantly less than the size of cms_infoobjects7, then I think there is some corruption in the repository. A reposcan might fix it.

If the results are close, then you've got a boatload of objects somewhere. Unfortunately the CMS Query syntax does not support GROUP BY, which makes debugging a little harder. I would first try a "select count(si_id)" from ci_infoobjects, ci_appobjects, and ci_systemobjects separately. That should reveal at least which virtual table is the problem. Once you have that, try 'select top 100000 si_id,si_kind from ... order by si_kind". Eyeballing the result should reveal the si_kind of the unwanted objects.

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Sep 21, 2017 at 01:53 PM
0

Support SAP answered by this SAP Note: https://launchpad.support.sap.com/#/notes/0002500438

but this does not minimise the size of DB CMS.

If I do understand well, we need to wait for the next patch that will fix this issue. for new we should disable APS_search.

Regards

Share
10 |10000 characters needed characters left characters exceeded