SASCONT1 table growing of 3 GB

[benoit-schmid]

Hello,

After applying the support packages in our Solution Manager,

the table SASACONT1 has grown 3 GB.

1. Would you know what does this table contain?

2. Are there standard reports to clean/purge it?

Thanks in advance for your answer.

[aena_dtiddsap · Accepted solution]

Table SASCONT1 contains documents os Solution Manager.

Yo have and explanation of the growing size of the table and how to reduce the size with a report: http://scn.sap.com/community/it-management/alm/solution-manager/blog/2012/07/17/how-to-reduce-the-si...

Regards,

Nerea de Andrés

[benoit-schmid · Accepted solution]

Hello Nerea,

As we say in french, late answer is better than never.

Why has it grown especially during support packages?

Couldn't I use RDSMOPREDUCEDATA to purge this table?

Regards,

[Former Member · Accepted solution]

Hi,

as posted by Fabricius Zatti: It handles the content created for roadmaps and content delivered by ST-ICO as well, more specifically documents. 

In summary, both tables are directly related to the implementation area of Solution Manager and can grow a lot depending on the usage of this area and the amount of content created.

Reports from this post are only valid to clean SACONT1 table and. But if you need to clean table SASACONT1 there is no special report so, you can use report RDSMOPREDUCEDATA as per note Note 546685 - Archiving in Solution Manager (operation).

Regards.

[benoit-schmid · Accepted solution]

Hello,

I have purge old sessions up to 30.6.2012 with th report RDSMOPREDUCEDATA.

But nothing has been deleted in SASACONT1 Table.

Before the report execution:

SQL> select count(*) from sapsr3.sasacont1;

   1405948

After the report execution:

SQL>  select count(*) from sapsr3.sasacont1;

   1405948

Would you know why nothing has been purged in this table?

Thanks in advance for your answer.

[benoit-schmid]

Hello,

Would you know why it has only increased in size when SPS were applied?

	01.10.2012		5.308.416	0	81	0	1.024
	01.09.2012		5.308.416	0	81	0	1.024
	01.08.2012		5.308.416	0	81	0	1.024
	01.07.2012		5.308.416	0	81	0	1.024
	01.06.2012		5.308.416	0	81	0	1.024
	01.05.2012		5.308.416                3.080.192	81	47	1.024
	01.04.2012		2.228.224	0	34	0	1.024
	01.03.2012		2.228.224	0	34	0	1.024
	01.02.2012		2.228.224	0	34	0	1.024
	01.01.2012		2.228.224	0	34	0	1.024
	01.12.2011		2.228.224	0	34	0	1.024
	01.11.2011		2.228.224	0	34	0	1.024

Thanks in advance for your answer.

[JPReyes]

Would you know why it has only increased in size when SPS were applied?

As mentioned in the article mentioned above "the size of this table will be mainly determined by the roadmap documents contained in ST-ICO"

It makes sense that if you dont use roadmap documents then it will only increase when the templates included in package ST-ICO are imported via a Support Package,

Regard, Juan

[benoit-schmid]

Hello Juan,

What does contain the 1.5 Millon line if it is unused?

Thanks in advance for your answer.

[JPReyes]

You'll have to ask SAP that  ... the fact that is a funtionality that your company does not use does not mean that is not useful to some other clients.

Regards, Juan

[benoit-schmid]

Hello,

Concerning my other question would you have an answer:

I have purge old sessions up to 30.6.2012 with th report RDSMOPREDUCEDATA.

But nothing has been deleted in SASACONT1 Table.

Would you know why?

Thanks in advance for your answer.

[JPReyes]

Nope, I never had to use RDSMOPREDUCEDATA.before.

Regards, Juan

[benoit-schmid]

Hello,

Juan Reyes wrote:
Nope, I never had to use RDSMOPREDUCEDATA.before.
Regards, Juan

Would there be someone as kind as Juan who would have the answer?

Thanks in advance for your answer.

[Former Member]

This growth looks normal to me. same table is over 4gb in our system too and .

Regards

Amit

[benoit-schmid]

Hello,

Would you know what kind of information this table contains and if it is possible to purge it.

Thanks in advance for your answer.

[Former Member]

I am currently not aware of what kind of data is getting stored in these tables also i am not aware of archiving options for this table.

Try opening a message with SAP.

Regards

Amit Padmawar