cancel
Showing results for 
Search instead for 
Did you mean: 

Exadata critical objects

nicola_blasi
Active Participant
0 Kudos

Hy

We have a BW system 7.31 Sp4 with oracle Exadata 11.2.0.3.

We have a problem in tablespace PSAPSR3 size 5,8tera with 323Gb free space.

Even though we added 32GB datafile ..after some period we have a critical objects problem on this tablespace.

How can we manage the tablespace to avoid this problem with so much free space available?

The problem happens above all in /BIC/* and /BI0/* tables.

Thanks

Bye

Nick

Accepted Solutions (1)

Accepted Solutions (1)

stefan_koehler
Active Contributor
0 Kudos

Hi Nicola,

323 GB free space and you get an ORA error like ORA-01652 / ORA-01653? An extra data file fixes the issue temporarily?

Exadata, ASM and AU size .. this sounds like the "classical" extent alignment / AU boundaries issue. It is described by Randolf Geist in one of his blog posts: ASM AU Size And LMT AUTOALLOCATE

Regards

Stefan

Answers (1)

Answers (1)

thiago_cavalheiro
Active Participant
0 Kudos

Hi Nick,

First thing you need to check is whether the objects in the tablespace are compressed - this is crucial for saving space.

Other than that, you can take some long timeframe AWR reports to check what are the top executions DML, to help identify what are the modules responsible for consuming the space. Refer to note:

590370 - Too many uncompressed request (f table partitions)

Best regards,

Thiago