Frequently facing critical object proplem

[Former Member]

Dear All,

We are using ERP 6 EHP5 with Oracle 11G and windows 2008 on VMware environment.

We are scheduling every month cost-run report and It would be completed time one days or more than 35 hrs.So that time we facing critical objects alert and also background job had been canceled immediately.

We are facing frequently this problem. Please any body give us good solution.

Temp solution:

If I extended 3 or 4 GB for the particular table space then it will complete the job successfully.

Note :

We don't have more space in our storage.

Normally our database's all table space size less than 60 %.

Our database size is 2 TB.

Please see the below alert screen

Owner	Name	Partition	Type	Tablespace	Size(MB)	Next Extent(MB)	Max Free(MB)	Alert Type
SAPR3	CKIS~0	INDEX	PSAPBTABI	13,150.14	1,280.00	3,071.99	2
SAPR3	CKIT~0	INDEX	PSAPBTABI	13,117.65	1,280.00	3,071.99	2
SAPR3	CNVCLU	TABLE	PSAPBTABI	25,400.02	1,280.00	3,071.99	2
SAPR3	COEP~0	INDEX	PSAPBTABI	19,237.47	1,280.00	3,071.99	2
SAPR3	EDI40	TABLE	PSAPCLUD	31,298.34	2,047.93	3,999.99	2
SAPR3	ARFCSDATA	TABLE	PSAPBTABD	19,132.05	1,280.00	1,278.46	1
SAPR3	CKIS	TABLE	PSAPBTABD	73,547.31	2,047.93	1,278.46	1
SAPR3	CKMLPRKEPH~0	INDEX	PSAPSTABI	5,199.48	640	615.51	1
SAPR3	CMFP	TABLE	PSAPBTABD	24,030.02	1,280.00	1,278.46	1
SAPR3	COEP	TABLE	PSAPBTABD	88,310.13	2,047.93	1,278.46	1
SAPR3	COEP~1	INDEX	PSAPBTABI	34,534.56	2,047.93	3,071.99	1
SAPR3	TST03	TABLE	PSAPBTABD	59,365.88	2,047.93	1,278.46	1

Thank you

Mahendran

[Former Member]

Dear Nick Loy,

Thanks for your valuable guidance.

I request you to give me some screen shots or guide .so that it would be helpful for us.

Thank you

Mahendran

[ACE-SAP]

Hello

It's been while I did not see the old tablesapce layout (=>355771 - Oracle: Explanation of the new tablespace layout )

You can easily save 25 Gb by deleting table CNVCLU as explained in the here under note

719989 - SLO: Deleting data from CNVCLU after conversion

Table TST03 is quite big, make sure you have scheduled the report to cleanup TemSe

48400 - Reorganization of TemSe and Spool

Data from table EDI40 could be archived/reorganized

40088 - EDI/IDoc: Deleting and reorganizing IDocs

You can easily save space by activating index compression on the biggest index.

This will save space and increase index access speed.

1109743 - Use of Index Key Compression for Oracle Databases

You can also activate advanced (OLTP) compression on the biggest tables

1436352 - Oracle 11g Advanced Compression for SAP Systems

Best regards

[Former Member]

Dear All,

My system was analysed by SAP team and they told me to change DMTS to LMTS.

Note 214995

Please need your suggestion and  help one this.

Thank you

Mahendran

[Former Member]

DMTS to LMTS conversion need a database/tablespace export and import.

Better you do with compression so that you can get other benefits as well.

For one of our system we followed the same to achieve both, scenario is below:

1) Extend storage (Add 60% of additional storage to your system)

2) Create new tablespaces in new storage (New tablespaces will be created as LMTS by default)

3) Migrate the data from old to new tablespace with compression option ON

4) Swap the tablespace names

5) Drop old tablespaces and then the old storage

Above activity will migrate all of your tablespaces to LMTS and it compress your database (you will get a good benefits in terms of storage cost saving, performance improvements etc.).

Regards,

Nick Loy