on 08-22-2012 5:51 AM
Dear Experts,
In db02->space->segment->critical objects, we get below entries:
Owner | Name | Partition | Type | Tablespace | Size(MB) | Next Extent(MB) | Max Free(MB) | Alert Type |
SYS | _SYSSMU12$ | TYPE2 UNDO | PSAPUNDO | 1,423.125 | 64.000 | 16.00 | 1.00 | |
SYS | _SYSSMU13$ | TYPE2 UNDO | PSAPUNDO | 1,357.125 | 64.000 | 16.00 | 1.00 |
Please suggest what should we do in this situation
This seems that you have to add space in PSAPUNDO tablespace , since space critical undo objects exists in the undo tablespace . Add datafiles to the undo tablespace , so that such space critical objects do not show up.
Regards
Ratnajit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
what is the size of the database ?
These are undo segments which are re-used by oracle transactions. The segments are 1.4 GB and 1.3 GB which is fine . So suggest you to add datafiles to PSAPUNDO tablespace.
Or if you do not want to have these segments then do the following.
Stop the database and start again
Create a new undo tablespace say PSAPUNDO1
set the UNDO_TABLESPACE to this new tablespace .
Drop the PSAPUNDO tablespace.
create again PSAPUNDO tablespace .
Restart the database
set the UNDO_TABLESPACE to PSAPUNDO
drop PSAPUNDO1 tablespace.
Refer to link http://docs.oracle.com/cd/B19306_01/server.102/b14231/undo.htm
Regards
Ratnajit
User | Count |
---|---|
76 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.