Content Server (MAXDB 7.6) DB size appears incorrect

[former_member204618]

Hi all,

I've read a lot of forum threads about various ways of finding out the size of tables in KB.  However I have a slight problem.

My DB shows the following in the Data Area :-

Description of Value	in KB	in Pages	in %
Total Size	293,601,504	36,700,188	100
Used Area	244,719,752	30,589,969	83
Permanent used Area	244,715,488	30,589,436	83
Temporary Used Area	240	30	0
Free Area	48,881,752	6,110,219	17

However when I look at the size of the tables I see this :-

Table Name	Total Size in KB	Size w/out BLOBS in KB	BLOBS in KB	Description
DOCUMENTS0001	2,386,056	2,386,048	8
COMPONENTS0001	1,195,672	1,195,672	0
CONTREP	8	8	0

The above was taken from DBACOCKPIT in Solution Manager and DB59 > Assistant.  This matches what's shown in Database Manager also.

I have checked system tables sysinfo.schemasize and sysinfo.tablesize and these seem to match the entries from above.

What am I missing here?  These numbers don't translate into the Used Area!

Is there a better way of determining why it seems to think the database is 233GB when the used tables only account for maybe 4GB?

Also whilst looking at sysinfo.tablesize it shows the following :-

SCHEMANAME	TABLENAME	USEDSIZE	ROWCOUNT
SAPR3	CONTREP	8	1
SAPR3	DOCUMENTS0001	2395760	4259205
SAPR3	COMPONENTS0001	?	?
SAPR3	PLAN_TABLE	8	2
SAPR3	/MAXDB/UPDSTATS	8	0

For some reason I get ? in the USEDSIZE and ROWCOUNT fields for COMPONENTS0001.

Any help much appreciated.

Thanks

Craig

[former_member204618 · Accepted solution]

UPDATE

Having found this thread I read the mentioned SAP Note http://service.sap.com/sap/support/notes/1315198

Which lead me to run db_execute CHECK TABLE <table_name> WITH SHARE LOCK

So I left this running over the weekend and had to kill it early this morning as it didn't finish.

How do I get this to complete and how to know whether its doing anything?

Thanks

Craig

[Former Member · Accepted solution]

Hi Craig,

for me it sounds that you delete in the past some repositories. MaxDb removes deleted table entries asynchronously. If you stopp the database while the asynchronous delete is still active it can happen that deelted data won#t be removed anymore.

To get the system 'clean' again there are no administration commands. You have to open a customer ticket on component Bc-DB-SDB. This issue now can only be fixed by the support team.

Regards, Christiane

[Former Member · Accepted solution]

Hi Craig,

I cannot find a custoerm ticket with no 000020163434.

Reghards, Christiane

[former_member204618 · Accepted solution]

Sorry getting stressed it's 0000304269.

Cheers

Craig