Skip to Content

Exadata critical objects

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

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Nov 18, 2014 at 05:37 PM

    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

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 18, 2014 at 04:52 PM

    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

    Add comment
    10|10000 characters needed characters exceeded