ASSM and system, temp, undo tablespaces(10g)

Hi, all.
I created a database(10.2.0.2.0) by using DBCA.
SYSAUX and USERS tablespaces are set to "auto" in
SEGMENT_SPACE_MANAGEMENT column.
However, system, temp and temp tablespaces have the value of "Manual" in
SEGMENT_SPACE_MANAGEMENT column.
Can I change this Value, "Manual" to "Auto" ??
(system, temp, undo tablespace)
Best Regards.

Hi,
The document states that there are certain restrictions on Automatic Segment-space Management.
Firstly, you can specify this clause only for a permanent, locally managed tablespace.Secondly, you cannot specify this clause for the SYSTEM tablespace.
http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_7003.htm
Adith

Similar Messages

Tuning UNDO tablespace - 10g

Hi,
Currently my undo tablespace is 1GB (data file not set to autoextensible due to filesystem space constraint) and undo retention is 900 seconds.
I'm facing alot of snapshot too old errors.
I'm going to increase/tune tablespace size and also undo retention period. from the below query from gv$undostat, shud i set the maximun retention period of undo to the max query length? or only to the max query length there the ora-01555 error happens? how abt the tablespace sizing, how can i estimate.. please advise experts.
Tuned Undo # Unexpired # Expired ORA-1555 Out-Of-space Max Query
INST_ID BEGIN_TIME Retention Stolen Reused Error Error Length
1 07/21/2008 11:12 49564 0 438 0 0 1421
1 07/21/2008 11:22 2086 173 497 0 5 2022
1 07/21/2008 11:32 2602 64 65 0 3 1768
1 07/21/2008 11:42 3118 0 0 0 0 1847
1 07/21/2008 11:52 3632 3 12 0 0 385
1 07/21/2008 12:02 4146 2 17 0 0 572
Tuned Undo # Unexpired # Expired ORA-1555 Out-Of-space Max Query
INST_ID BEGIN_TIME Retention Stolen Reused Error Error Length
1 07/21/2008 12:12 4659 57 60 0 0 32
1 07/21/2008 12:22 5175 47 53 0 0 12
1 07/21/2008 12:32 5690 0 43 0 0 105
1 07/21/2008 12:42 6203 0 116 0 0 488
1 07/21/2008 12:52 6719 0 116 0 0 1088
1 07/21/2008 13:02 7231 0 330 0 0 1687
1 07/21/2008 13:12 7743 0 229 0 0 2290
1 07/21/2008 13:22 8248 13 393 0 0 666
1 07/21/2008 13:32 8713 278 420 0 0 459
1 07/21/2008 13:42 9180 170 288 1 0 1058
1 07/21/2008 13:52 9650 286 335 2 0 1657
1 07/21/2008 14:02 10141 51 273 2 0 733
1 07/21/2008 14:12 10610 85 584 0 0 1389
1 07/21/2008 14:22 10963 89 283 2 0 1716
1 07/21/2008 14:32 12022 32 264 0 0 1598
1 07/21/2008 14:42 10783 0 158 0 0 2918
1 07/21/2008 14:52 11902 0 134 1 0 3519
1 07/21/2008 15:02 13283 34 658 0 0 4121
1 07/21/2008 15:12 12044 0 322 0 0 4722
1 07/21/2008 15:22 2932 5 208 0 0 5322
1 07/21/2008 15:32 3497 45 398 0 0 6200
Tuned Undo # Unexpired # Expired ORA-1555 Out-Of-space Max Query
INST_ID BEGIN_TIME Retention Stolen Reused Error Error Length
1 07/21/2008 15:42 4071 8 489 0 0 6800
1 07/21/2008 15:52 4637 386 494 0 5 7402
1 07/21/2008 16:02 5209 200 812 0 1 7727
1 07/21/2008 16:12 5775 319 568 1 7 1138
1 07/21/2008 16:22 6345 3 1220 0 0 1740
1 07/21/2008 16:32 6858 0 5575 0 0 98
1 07/21/2008 16:42 7420 4 777 0 0 606
1 07/21/2008 16:52 7952 32 1344 0 0 604
1 07/21/2008 17:02 8293 0 6 0 0 43
576 rows selected.

Snapshot too old error's most useful solution is to raise the undo tablespace's size. I would raise it anyway, but i think you need to report your manager that you need to upgrade the system, indeed 900 seconds undo retention is not enough to your database.
Simple logic, growing database, growing sql queries, decreasing or steady hardware and sizes? IMPOSSIBLE.

MBRC and SYSTEM STATISTICS in Oracle 10g database.

Hi All,
I am performing database upgrade from Oracle 8i Solaris to Oracle 10g HP-UX using exp/imp method.
But i do have some doubts regarding MBRC and System statistics.
MBRC in Oracle 10g is automatically adjusted if MBRC parameter is not set, but i found value 128 as shown below.
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE    10.2.0.4.0      Production
TNS for HPUX: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
SQL> sho parameter multi
NAME                                 TYPE                             VALUE
db_file_multiblock_read_count        integer                          128Also i performed one simple full table scan to test it...but db file scattered read is performing on 128 blocks. So i dont think 128 is suitable and is automatic, i mean MBRC is not set accrodingly it always uses 128.
Does this MBRC value affects whole database performance?
Regarding SYSTEM STATISTICS i found below result:
SQL> select * from AUX_STATS$
SNAME                          PNAME                               PVAL1 PVAL2
SYSSTATS_INFO                  STATUS                                    COMPLETED
SYSSTATS_INFO                  DSTART                                    11-09-2009 04:59
SYSSTATS_INFO                  DSTOP                                     11-09-2009 04:59
SYSSTATS_INFO                  FLAGS                                   1
SYSSTATS_MAIN                  CPUSPEEDNW                     128.239557
SYSSTATS_MAIN                  IOSEEKTIM                              10
SYSSTATS_MAIN                  IOTFRSPEED                           4096
SYSSTATS_MAIN                  SREADTIM
SYSSTATS_MAIN                  MREADTIM
SYSSTATS_MAIN                  CPUSPEED
SYSSTATS_MAIN                  MBRC
SYSSTATS_MAIN                  MAXTHR
SYSSTATS_MAIN                  SLAVETHRNow whether NOWORKLOAD or WORKLOAD is better, and this server is still under building process....so how can i collect WORKLOAD stats as high load on this server can't be performed?? Is it really require to gather system statistics, what will happen with NOWORLOAD stats?
I have not seen single database where system stats are gathered in our organisation having more than 2000 databases.
-Yasser

Maybe this article written by Tom Kite helps:
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:499197100346264909

Undo Tablespace and Temporary Tablespace - autoextend ?

- In general, should I allow the Undo Tablespace to grow (autoextend)?
- In general, should I allow the Temporary Tablespace to grow (autoextend)?

The size of undo tablespace should always keeps in mind otherwiase you eill get ORA-1555 or out of space errors.
This paper is to help DBA’s in calculating the size of UNDO tablespace by using a simple formula.
It is tough to know about the number of transactions and subsequently number of rows changed per second.
So I suggest having a “big undo tablespace” to start with and based on load, after doing some calculations and resize your UNDO tablespace.
In my case one of the applications was going to production (live), and I had no idea that how many transactions will happen against this database. All what I was told that there will be optimum (transactional) activity on this database.
So I started with UNDO tablespace with size of 3GB and datafiles with autoextend “on” .
Note:
In production, you must be very careful in using this (autoextend on) as the space may grow to inifinity very fast. So my advice is either dont use this option, or use with "maxsize" or continuously monitor space (which is tough).
I month later, I noticed the activity from V$undostat.
Here is the step by step approach:
Step 1: Longest running query.
SQL> select max(maxquerylen) from v$undostat;
MAX(MAXQUERYLEN)
1793
This gives you ideal value for UNDO_RETENTION. To be on the safer size you should add few more seconds to get the right value. So in my case, the size of undo retention should be say 2000 secs.
Step 2: Size of UNDO tablespace.
Size of UNDO needed = UNDO_RETENTION x [UNDO block Generation per sec x DB_BLOCK_SIZE] + Overhead(30xDB_BLOCK_SIZE)
Out of these we know UNDO_RETENTION and DB_BLOCK_SIZE
All we need is to find out “UNDO Blocks per second”
Which can be easily fetched from v$undostat
SQL> SELECT (SUM(undoblks))/ SUM ((end_time - begin_time) * 24*60*60) "UPS"
2 FROM v$undostat;
UPS
8.11985583
V$undostat stores data for every 10 mins and begin/end times are start/end time of those intervals. We multiplied it with 24*60*60 because the difference between two dates will be in days and to get to seconds, we need it to multiply with 24hrs*60mins*60secs
So now we have all the values needed.
Undo size needed = [8.12 x 2000 x 8192] + [30 x 8192] = 133283840 bytes = 127.11 MB

Dropping Undo Tablespace

Hi,
I am running Oracle 9.2 on Solaris. I have Automatic undo management turned on and have a Undo tablespace by name UNDOTBS. It has a single datafile and has AUTOEXTEND feature turned on. My UNDO_RETENTION was set to 4 hours.
Presently, the size of UNDOTBS has grown to around 40G and has filled up the file system in which it resides. I need to clean up the file system. In order to do this, I followed the below procedure.
SQL> create undo tablespace UNDOTBS1 datafile '/u04/oradata/proddb/undo_00.dbf' size 1024M autoextend off;
SQ> alter system set undo_tablespace=undotbs1 scope=both;
SQL> alter system set undo_retention=3600 scope=both;
Now, i checked the alert log and it is offlining all the UNDO segments of the first undo tablespace UNDOTBS. It is taking time and has been more than 1.5 hours. I have a couple of questions here,
1. As i have issued "alter system undo_tablespace=undotbs1 scope=both", all the new transactions will use the new UNDOTBS1. No new transactions will be using the first undo tablespace UNDOTBS right?
2. Since, i have issued "alter system undo_retention=3600 scope=both", all the transactions in first undo tablespace UNDOTBS will be rolled back after 2 hours, no matter if it is commited or not. After this period, i am safe to drop the first undo tablespace using "drop tablespace UNDOTBS including contents and datafiles;". Did i get it right?
Any information will be of a great help.
THanks,
Harris.

Hi,
Thank you all for the replies. It has been two days since i switched the undo_tablespace to use the new tablespace(undotbs1) but my alert log is still being flooded with " Undo tablespace 1 moved to pending switch out state". I tried the following to see if there are any rows returne from the above query and it did 3 rows, showing some undo segments with the following output
SQL> select a.name, b.status from v$rollname a, v$rollstat b where a.name in (select segment_name from dba_segments where tablespace_name='UNDOTBS') and a.usn=b.usn;
Name Status
_SYSSMU15$      UNKNOWN
_SYSSMU33$      UNKNOWN
_SYSSMU9$        PENDING OFFLINE
I have seen gone through the metalink id: 341372.1 that speaks about this SWITCH-OUT state. How can i make sure what old transactions are still using the Undo segments in first undo tablespace and how can i go about killing them. Could anyone please let me know that i could use the following queries to find the correct sessions that are using the Old Undo tablespace.
SQL> select ADDR, XIDUSN,STATUS, START_TIME from v$transaction;
SQL> SELECT
a.usn,
a.name,
b.status,
c.tablespace_name,
d.addr,
e.sid,
e.serial#,
e.username,
e.program,
e.machine,
e.osuser
FROM
v$rollname a,
v$rollstat b,
dba_rollback_segs c,
v$transaction d,
v$session e
WHERE
a.usn=b.usn AND
a.name=c.segment_name AND
a.usn=d.xidusn AND
d.addr=e.taddr AND
b.status='PENDING OFFLINE';
Just wanted to make sure that the second query lists the PENDING OFFLINE segments of the first tablespace right?
This is a prod. box, so wanted to confirm with you guys before proceeding.
Thanks,
Harris.

Second Undo Tablespace in Oracle10g v.2...

Hi ,
Having connected as sys i created another undo tablespace ... except for the first one created by default....
SQL> CREATE UNDO TABLESPACE INFO_UNDO_TBL DATAFILE 'C:\oracle\product\10.2.0\oradata\INFO\INFO_UNDO_DFL.ORA' SIZE 10M;
Tablespace createdI have two questions...
1) When i issue the command:
SQL> SHOW PARAMETER UNDO_TABLESPACE;
NAME                                 TYPE        VALUE
undo_tablespace                      string      UNDOTBS1It does not refer the new undo tablespace..... I suppose that i have to write:
sql> alter system set undo_tablespace=UNDOTBS1,INFO_UNDO_TBL scope =BOTH... or something like this....Is that correct....??????
2)The Oracle Doc (Concepts) points out.....
"In automatic undo
management mode, each Oracle instance is assigned one (and only one) undo
tablespace."
That means i cannot issue the command "alter system set undo_tablespace=UNDOTBS1,INFO_UNDO_TBL" (if it is correct) since the default undo tablespace runs in AUTO mode.....????
SQL> SHOW PARAMETER UNDO_MANAGEMENT;
NAME                                 TYPE        VALUE
undo_management                      string      AUTOMany thanks....
Sim

Hi ,
I dont think you can have two undo tablespaces assigned for a database.This is what you get in the alert log files even if you are deceived by the statement "System Altered"
SQL> alter system set undo_tablespace='UNDOTBS1,UNDOTBS2' scope=spfile;
System altered.
SQL> sho parameter undo
NAME TYPE VALUE
undo_management string AUTO
undo_retention integer 900
undo_tablespace string UNDOTBS1,UNDOTBS2
Alert log extract..............
Errors in file j:\oracle\product\10.2.0\admin\orcl10g\udump\orcl10g_ora_1724.trc:
ORA-30012: undo tablespace 'UNDOTBS1,UNDOTBS2' does not exist or of wrong type
Errors in file j:\oracle\product\10.2.0\admin\orcl10g\bdump\orcl10g_reco_1808.trc:
ORA-30012: Message 30012 not found; No message file for product=RDBMS, facility=ORA
Tue Oct 02 15:37:41 2007
Errors in file j:\oracle\product\10.2.0\admin\orcl10g\bdump\orcl10g_smon_1760.trc:
ORA-30012: Message 30012 not found; No message file for product=RDBMS, facility=ORA
Instance terminated by USER, pid = 1724
ORA-1092 signalled during: alter database open...
Regards,
-Praveen
http://myracle.wordpress.com

How to Shrink UNDO Tablespace

Hello,
We had a UNDO Tablespace of 22Gb but it is using just 2GB. How to shrink undo tablespace. we are using clustered 3 node production database 10.2.0.4
Is there is way that we can shrink UNDO Tablespace or do i need to create a UNDO tablespace and assign the undo tablespace to DB and drop the old UNDO?
How to ensure that transactions are done and free to drop the old UNDO?
Is it something we need to restart all the three nodes as each node has its own UNDO Tablespace.
Need Help on this issue.
would appreciate your quick response.
Thanks

if i am in your place i will do the following:
<pre class="jive-pre">1-Query DBA_DATA_FILES to determine the name of the datafiles of the UNDO</pre>
2. Create a new UNDO tablespace.
<pre class="jive-pre">CREATE UNDO TABLESPACE undo_ts2 DATAFILE '/directory/undo_ts2_01.dbf' SIZE xxxM;</pre>
3. Modify the database parameter to use the new UNDO tablespace.
<pre class="jive-pre"> ALTER SYSTEM SET undo_tablespace=undo_ts2 SCOPE=BOTH; </pre>
4-The Drawback:
<pre class="jive-pre">New transactions will begin using the new undo tablespace. After some time passes (at least the number of seconds specified by the UNDO_RETENTION initialization parameter), you can drop the old UNDO tablespace. The downside to this approach is that for a short time period, your database will have two UNDO tablespaces</pre>
Regards
Mohamed

Undo Tablespace Retention gurantee

Hi,
From what I have read about undo Tablespaces ,If Undo Management is AUTO,and Retention is se to say 15 min and retention gurantee is disabled ,Unexpired transactions can be overwritten by the database,If such is the case then undo tablespace should never get filled up.
But I have observed despite these settings,Undo tablespace filling issue still occurs.
Please help me understand this.
Thanks.

Either
1. Your undo tablespace datafile is small (inadequate for the volume of transactions)
OR
2. Oracle is using autotuneundo which causes it to retain Undo for longer than undo_retention period and use the undo tablespace datafile to the fullest.
See Oracle Support notes
"Oracle 10G new feature - Automatic Undo Retention Tuning [ID 311615.1] "
"Bug 5387030 - Automatic tuning of undo_retention causes unusual extra space allocation [ID 5387030.8] "
"Bug 5387030"
Hemant K Chitale

Undo tablespace growing fast

Hello All
We are having issues with undo tablespace growing... the oracle version is 10.2.0.1.0
the table is holding around 400000000 records and this table is also partitioned by range
any reason for this undo tablespace growing by at an high rate
regards
Kedar

Undo tablespaces are special tablespaces used solely for storing undo information. You cannot create any other segment types (for example, tables or indexes) in undo tablespaces. Each database contains zero or more undo tablespaces. In automatic undo management mode, each Oracle instance is assigned one (and only one) undo tablespace. Undo data is managed within an undo tablespace using undo segments that are automatically created and maintained by Oracle.
Every Oracle Database must have a method of maintaining information that is used to roll back, or undo, changes to the database. Such information consists of records of the actions of transactions, primarily before they are committed. These records are collectively referred to as undo.
Undo records are used to:
Roll back transactions when a ROLLBACK statement is issued
Recover the database
Provide read consistency
Analyze data as of an earlier point in time by using Oracle Flashback Query
Recover from logical corruptions using Oracle Flashback features
When a ROLLBACK statement is issued, undo records are used to undo changes that were made to the database by the uncommitted transaction. During database recovery, undo records are used to undo any uncommitted changes applied from the redo log to the datafiles. Undo records provide read consistency by maintaining the before image of the data for users who are accessing the data at the same time that another user is changing it.
You confuse TEMP with UNDO tablespace.
Best Regards,
Francisco Munoz Alvarez
www.oraclenz.com

Undo tablespace recovery from RMAN backup

Hi,
Lets's assume we have RMAN backup and archivelog backups, and now
my undo tablespace's disk crashed ,how can i recover?
Can i recover while database is up?
Thanks,
Kumar.

to recover UNDO tablespace from RMAN backup you must shutdown the database and start it in the MOUNT state to recover the missing files as follows
rman target /
RUN
STARTUP MOUNT;
ALLOCATE CHANNEL ch3 TYPE Disk;
RESTORE datafile 'c:\u01\prod3\undo01.dbf';
RECOVER datafile 'c:\u01\prod3\undo01.dbf';
ALTER DATABASE OPEN;
RELEASE CHANNEL ch3;
hope this will help you

Can't create new undo tablespace while undo tablespace is crushed

We currently encounter an emergent error on our productive database. The undo tablespace on this database looks like crushed. And insert /update operations can't be executed because of the undo tablespace error.
we tried to create a new undo tablespace to replace this broken tablespace, but the database reports ORA-00376 and ORA-00376 error.
We have already deleted rollback segments which status is "NEED RECOVERY".
Now we run our database in manual undo tablespace management mode. and add a new datafile into current broken undo tablespace. Then create a new rollback segment for public user. Now, user can insert /update data. But we are not sure if this method would occur any other problems.
I really appreciate if you have any good suggestions.

Hi,
Actually ORA-00376 is the following cause and take action.
cause: An attempt was made to read from a file that is not readable. Most likely the file is offline.
Action: Check the state of the file. Bring it online.
Again setup ur DB automatic UNDO MANAGEMENT and check status of the ur undo tablespace. and bring it online.
and create another undo tablespac and switching the undo tablespace.
Regards..

Profiles apply to SYS and SYSTEM users

dear all.
is possible configure the security policies (profiles), i mean password length, history, failed login attempts for SYS and SYSTEM users in oracle 10g.
What will happen if both users blocked ?? the service would be affected ???
what would you recommend me ?
thanks for your answers and apologize my english, is not very well.

Check here:
SYS account cannot be locked out by setting the failed_login_attempts limit in the profile.
is it possible to lock out SYS using FAILED_LOGIN_ATTEMPTS in a profile
http://www.petefinnigan.com/ramblings/failed_login_attempts.htm
-Anantha

Partial Recovery - Skip UNDO Tablespace

Hi,
I was performing a partial database recovery using skip tablespace option using RMAN. I was wondering if I can skip undo tablespace.
I was not able to conclude whether I can do that? If not, why?
As per my understanding,
1. Datafiles are restored - If they have any uncommited data, then archive logs which will be applied for media recovery, will have the undo data to perform those roll backward.
2. While performing media reccovery using archive logs, it will generate it's own undo data.
Why do we need the stale undo data (generated till datafiles restoration point)?
Thanks,
Janak Agrawal

Soli,
Thread that you have specified, talks about datafiles which does not have any uncommitted data (As the database was normally shutdown). In this case, we can drop and recreate the undo tablespace.
But I am talking about a past point-in-time recovery using RMAN, where the datafiles which will be restored may have the uncommitted data. To rollback these uncommited trnasactions, will we have data in next archivelogs, which will be used for media recovery or the data (needed to rollback) will have only in undo tablespace. Let me give you an example.
At 9 am I want to restore the datbase till 8.15 AM. Full backup is available till 8 AM and then from 8 to 8:15 arvhive logs are available. While doing recovery, datafiles will be restored till 8 AM. If at 8 AM there is some uncommitted data in datafiles, will it require data from undo tablespace to rollback or first archive log after 8 AM w'd take care of roll back? If archive logs can take care of rollback, why can't I skip the undo tablespace while doing recovery?
Santosh,
As you mentioned, UNDO data will require for read-consistency. But the same data will be available in archive logs (which will require after datafiles restore) which can generate their own UNDO data.
Please clarify. I am sorry if I am missing anything here.
Thanks,
Janak Agrawal

Will going to 166 FSB raise system temp?

Before I changed mobo and CPU from one KT4 (without built in LAN) to another KT4 (with built in LAN, the first one didn't have that) with an XP2600+) my CPU temp was around 40 and system temp around 34 when idle. Now my system temp is at 40 idle while my CPU creeps down towards 38 (but only with the case open, the cooler that came with it has to go - exchanged for a Zalman flower cooler). Is the reason for this increase in system temp that I now run 166 FSB while I was running 133 on the other board, or should I have a look at the northbridge cooler?
Thanks a lot in advance! 8)

Mystery solved! It was because of the new CPU cooler (which is now going into the server with the "old" KT4 mobo). My one week old Zalman Flower cooler has a large fan that's placed an inch or so from the cooler itself, and that fan also increases air circulation for the northbridge. So now I'm back to 32 degrees system temperature and 41 degrees idle CPU temp (because I have reduced fan speed to reduce noise), which sounds good enough for me. 8)

Temp and undo tablespace

Once we created a new temporary or undo tablespace we can make then the default one.My question is regardless of how many undotablespaces or temporary tablespaces the database has the only one used are the assigned as the defualt.Is this right?
Thanks in advnance

Hi, if you user AUM (automatic undo )you can have only one UNDO TS per instance, set by UNDO_TABLESPACE parameters.
For TEMPORARY tablespace you can have several, each user is assigne an TEMPORAY TS by create user....TEMPORARY TABLESPACE name or modified by alter user.

ASSM and system, temp, undo tablespaces(10g)

Similar Messages

Maybe you are looking for