ROLLBACK SEGMENT VERSION 7.3

We have an oracle 7.3 database on solaris(sparc) 2.6.
In the midddle of the transactions, the following error message
occured:
ORA 1578 Data block corrupted(file #2, block#8274)
ORA-1110 Datafile 2:'/user1/oradb/rbstbl.dbf'
(this datafile corresponds to the rollback segment table space).
Action Taken:
1. Tried to make the rollback segments offline, but out of 11, 2
rollback
segments could not be taken offline. The status for these 2
was 'pending
offline'.
2. Made the table space and datafile offline.
3. Created new rollback segments with new datafile and rollback
segments,
duly commenting the same in init.ora.
4. The status for these 2 rollback segments has now changed
to 'needs
recovery'. This status is preventing us from taking any further
action.
We would like to drop the old table space.
We need you kind help in getting out of this loop!
We don't have any backup and the archivlog was not activated.
HELP is there any way to solve this problem?????
Thank for your help

Oracle XML Team wrote:
: Jerome Sigua (guest) wrote:
: : My company has version 7.3.4 and my group is thinking of
using
: : XML for some data transfers between us and our vendors. From
: : what I could see from this web site, it looks like we would
: need
: : to move to ver 8i in order to do so. Is there any way of
: : leveraging ver 7 to do XML? I'm sure we'll move up to ver 8
: : sometime in the future but I don't know if we will within our
: : timeline(next 3-4 months) for the next phase of the project
: I'm
: : working on.
: : TIA
: : Jerome Sigua
: As long as you have the appropriate JDBC 1.1 drivers for 7.3.4
: you should be able to use the XML SQL Utility to extract data
in
: XML.
: Oracle XML Team
: http://technet.oracle.com
: Oracle Technology Network
For JDBC drivers, please take a look at
http://technet.oracle.com/tech/java/sqlj_jdbc/
Take a look at : Oracle 7 JDBC OCI and JDBC Thin Drivers
Oracle Technology Network
http://technet.oracle.com
null

Similar Messages

R0 Rollback Segment in Import of 10gR2 into 11gR2 Database

I have a new install of Oracle Database Server Enterprise Edition 11.2.0.3.6 on AIX 7.1.
I used the DBCA to create two databases and used export datapump and import datapump to upgrade two 10gR2 database to 11gR2.
One of the import logs includes the following messages:
Processing object type DATABASE_EXPORT/ROLLBACK_SEGMENT
ORA-39083: Object type ROLLBACK_SEGMENT failed to create with error:
ORA-02221: invalid MAXEXTENTS storage option value
Failing sql is:
CREATE ROLLBACK SEGMENT "R0" TABLESPACE "SYSTEM" STORAGE(INITIAL 131072 NEXT 131072 MINEXTENTS 2 MAXEXTENTS 2147483645)
I verified that the source database has R0 with maxextents of 2147483645.
I can copy and modify the CREATE ROLLBACK statement and lower the value assigned to MAXEXTENTS, or use MAXEXTENTS UNLIMITED, then run the command in the target database.
In light of the fact that the DBCA did not create R0 in my two 11gR2 databases, I want to know if I still need to create R0 in the one that showed the error in the import log. Has anyone else noticed the disappearance of R0?
Here are the rollback segments that exist in the 11gR2 database at this time:
SQL> Select SEGMENT_NAME, OWNER, TABLESPACE_NAME, INITIAL_EXTENT, NEXT_EXTENT, MIN_EXTENTS, MAX_EXTENTS, PCT_INCREASE, STATUS
from SYS.DBA_ROLLBACK_SEGS;
SEGMENT_NAME OWNER TABLESPACE_NAME INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS MAX_EXTENTS PCT_INCREASE STATUS
SYSTEM SYS SYSTEM 114688 57344 1 32765 ONLINE
_SYSSMU1_3638931391$ PUBLIC UNDOTBS1 131072 65536 2 32765 ONLINE
_SYSSMU2_3033359625$ PUBLIC UNDOTBS1 131072 65536 2 32765 ONLINE
_SYSSMU3_2670780772$ PUBLIC UNDOTBS1 131072 65536 2 32765 ONLINE
_SYSSMU4_286801445$ PUBLIC UNDOTBS1 131072 65536 2 32765 ONLINE
_SYSSMU5_1738828719$ PUBLIC UNDOTBS1 131072 65536 2 32765 ONLINE
_SYSSMU6_3548494004$ PUBLIC UNDOTBS1 131072 65536 2 32765 ONLINE
_SYSSMU7_700714424$ PUBLIC UNDOTBS1 131072 65536 2 32765 ONLINE
_SYSSMU8_2755301871$ PUBLIC UNDOTBS1 131072 65536 2 32765 ONLINE
_SYSSMU9_2087597455$ PUBLIC UNDOTBS1 131072 65536 2 32765 ONLINE
_SYSSMU10_3267518184$ PUBLIC UNDOTBS1 131072 65536 2 32765 ONLINE
11 rows selected.
Thanks,
Bill

Srini,
Both the 10gR2 and 11gR2 versions of the database are using automatic undo management.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL> show parameter undo
NAME TYPE VALUE
_undo_autotune boolean TRUE
undo_management string AUTO
undo_retention integer 14400
undo_tablespace string UNDOTBS1
SQL>
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> show parameter undo
NAME TYPE VALUE
undo_management string AUTO
undo_retention integer 14400
undo_tablespace string UNDOTBS1
SQL>
Do you know anything about Oracle no longer automatically creating R0 in 11gR2?
Thanks,
Bill

Cannot drop old undo tablespace. Cause: active rollback segment

dear all.
db: oracle 10.2.0.1
os: rhel as version 5 64 bits.
This is a testing database. And my database is online and open. But i can free the external usb disk that contains my ols undotbs.
I want to drop old undo tablespace but this is not possible.
1.- In order to open my database i had my datafile( '/mnt/hdext/back_plelds/undotbs02.dbf') offline drop, and then i can to open my database.
2.- When i try to delete my old undo tablespace im getting this error:
SQL> drop tablespace undotbs1 including contents and datafiles;
drop tablespace undotbs1 including contents and datafiles
ERROR at line 1:
ORA-01548: active rollback segment '_SYSSMU1$' found, terminate dropping
tablespace
3.- My default undo_tablespace is another that i was created before step 1.
SQL> sho parameter undo_ta
NAME TYPE VALUE
undo_tablespace string UNDOTMP
SQL>
Well i search in metalink ORA-01548 code error and in 18947.1 doc whows me that the solution is:
Action: Shut down instances that use the active rollback segments in the
tablespace and then drop the tablespace.
4.- I try to shutdown but im getting:
SQL> shutdown immediate;
ORA-00376: file 10 cannot be read at this time
ORA-01110: data file 10: '/mnt/hdext/back_plelds/undotbs02.dbf'
SQL>
This /mnt/hdext is an external USB disk and i have all permissions. I exported tables without any problem and i can read all files.
i search un metalink again ora codes (ORA-00376 ORA-01110) and the doc id: 427801.1 shows in the solution:
Drop the old undo tablespace instead of making it offline.
but when i try to drop the tablespace it shows the error describe in the step 2.
Facts:
- my tablespace UNDOTBS1 is ONLINE. I put in offline and this is not the solution.
- This is the status of my rollback segments:
SQL> select segment_name, status from dba_rollback_segs where
2 tablespace_name='UNDOTBS1';
SEGMENT_NAME STATUS
_SYSSMU1$                      NEEDS RECOVERY
_SYSSMU2$                      NEEDS RECOVERY
_SYSSMU3$                      NEEDS RECOVERY
_SYSSMU4$                      NEEDS RECOVERY
_SYSSMU5$                      NEEDS RECOVERY
_SYSSMU6$                      NEEDS RECOVERY
_SYSSMU7$                      NEEDS RECOVERY
_SYSSMU8$                      NEEDS RECOVERY
_SYSSMU9$                      NEEDS RECOVERY
_SYSSMU10$                     NEEDS RECOVERY
_SYSSMU11$                     OFFLINE
SEGMENT_NAME STATUS
_SYSSMU12$                     OFFLINE
12 rows selected.
SQL>
- I have the note (Unable to drop und tablespace In this article describe the problem but this is not the same. The difference is that i cannot drop the rollback segment that describe in step 2.
SQL> drop rollback segment "_SYSSMU1$";
drop rollback segment "_SYSSMU1$"
ERROR at line 1:
ORA-30025: DROP segment '_SYSSMU1$' (in undo tablespace) not allowed
in metalink the doc id: 173696.1 shows the solution:
Action:     Check the undo segment name and reissue statement if necessary.
i cannot drop the rollback_segment
What can i do ???
thanks a lot.

in step 4 did you try with shutdown abort?
If its still does not work then create another new table space with new file and then swtich to that tablespace http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/undo.htm#sthref1504Khurram

Urgent: Error ORA-01555 "snapshot too old rollback segment too small"

I get this error when I do a "SELECT" on a few very large tables for a report. Isn't there a way out? Our DBA says our rollback segment size cannot be increased anymore. All I care of is the SELECT statement to finish executing. It is okay for me to have some inconsistency in the data (dirty reads). What is the easiest way to solve this problem? I CANNOT breakup the SELECT statement into multiple statements.
Thanks in advance

Oracle cannot be configured to give you dirty reads.
Setting your transaction to be READ ONLY probably won't help too much-- the problem here is that when you go to SELECT a particular row, Oracle discovers that the value in the row has changed since the start of your query and the old value is not present in the rollback segments.
How are your rollback segments configured? Perhaps you don't need to allocate additional space to them-- perhaps you can simply increase their OPTIMAL size.
What version of Oracle are you on? If you are on 9i or above, I would strongly consider moving to automatic UNDO management, which vastly simplifies rollback (undo) administration.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

How to online datafile of rollback segment of NO archive log available

I set offline datafile of rool back segement and rename it
but when I try to online , get error to recover
I try to recover but unfortunately all archive log was deleted ( kind of cron job in unix aotu delete these file)
Pls advice how can I set this data file online without the archive log ( while databse still up and running) Oracle version is 8i not possible to drop datafile by sql.
in roll back segment I have 3 data files as below and the rb04.dbf is offline
usr/Systems/1354RM_1_7.1_Master/databases/dbsnml/data/rbs01.dbf
/usr/Systems/1354RM_1_7.1_Master/databases/dbsnml/data/rbs03.dbf
/usr/Systems/1354RM_1_7.1_Master/databases/dbsnml/data/rbs04.dbf
sequence of what I did is below:
SQL> alter database datafile '/usr/Systems/1354RM_1/databases/dbsnml/data/rbs04.dbf' offline;
Database altered.
SQL> alter tablespace RBS rename datafile '/usr/Systems/1354RM_1/databases/dbsnml/data/rbs04.dbf' to '/usr/Systems/1354RM_1_7.1_Master/databases/dbsnml/data/rbs04.dbf';
Tablespace altered.
SQL> alter database datafile '/usr/Systems/1354RM_1_7.1_Master/databases/dbsnml/data/rbs04.dbf' online;
alter database datafile '/usr/Systems/1354RM_1_7.1_Master/databases/dbsnml/data/rbs04.dbf' online
ERROR at line 1:
ORA-01113: file 13 needs media recovery
ORA-01110: data file 13:
'/usr/Systems/1354RM_1_7.1_Master/databases/dbsnml/data/rbs04.dbf'
SQL> recover datafile '/usr/Systems/1354RM_1_7.1_Master/databases/dbsnml/data/rbs04.dbf';
ORA-00279: change 71449081 generated at 12/23/2008 20:18:05 needed for thread 1
ORA-00289: suggestion :
/usr/Systems/1354RM_1_7.1_Master/OSRES/data/warm_repl/WarmArchive/arch_1_455922.
arc
ORA-00280: change 71449081 for thread 1 is in sequence #455922
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'/usr/Systems/1354RM_1_7.1_Master/OSRES/data/warm_repl/WarmArchive/arch_1_455922
.arc'
ORA-27037: unable to obtain file status
HP-UX Error: 2: No such file or directory
Additional information: 3

SQL> alter tablespace RBS rename datafile '/usr/Systems/1354RM_1/databases/dbsnml/data/rbs04.dbf' to '/usr/Systems/1354RM_1_7.1_Master/databases/dbsnml/data/rbs04.dbf';Did you rename the file at OS level after you issued above command? Oracle will not rename the file at OS level.
Other than that, if you plan to change rollback segment tablespace, better create a new one and create new rollback segment in new tablespace and drop the old one.

Does a single transaction, spreeds accross multiple rollback segments?

Hi,
Does a single transaction, spreeds accross multiple rollback segments?
What if , there is not enough space in the allocated rollback segment?
Thanks
Naveen.

With the additional note/ caveat that, assuming you're using a moderately recent version of Oracle and using automatic UNDO management, which you really, really ought to be doing, Oracle is constantly adding, removing, and expanding the rollback segments, making it all but impossible for a rollback segment to be too small unless it (along with all the other active redo segments) exceed the size of your UNDO tablespace.
Justin

Failed to extend Rollback Segment

Version of the database is
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
I have a rollback tablespace that is 99%used and wen I am tryng to use DML statements to the database it is throwing the following error.
ORA-01562:FAILED TO EXTEND ROLLBACK SEGMENT 2
ORA-01650:UNABLE TO EXTEND ROLLBACK SEGMENT RBS01 BY 128 IN TABLESPACE
R
May I know how do I proceed now? Do I have to extend the tablespace or add a new datafile to the tablespace?

PK wrote:
Version of the database is
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
I have a rollback tablespace that is 99%used and wen I am tryng to use DML statements to the database it is throwing the following error.
ORA-01562:FAILED TO EXTEND ROLLBACK SEGMENT 2
ORA-01650:UNABLE TO EXTEND ROLLBACK SEGMENT RBS01 BY 128 IN TABLESPACE
R
May I know how do I proceed now? Do I have to extend the tablespace or add a new datafile to the tablespace?
01562, 00000, "failed to extend rollback segment number %s"
// *Cause: Failure occurred when trying to extend rollback segment
// *Action: This is normally followed by another error message that caused
//        the failure. You may take the rollback segment offline to perform
//         maintainence. Use the alter rollback segment offline command
//         to take the rollback segment offline.
bcm@bcm-laptop:~$ oerr ora 1650
01650, 00000, "unable to extend rollback segment %s by %s in tablespace %s"
// *Cause: Failed to allocate an extent of the required number of blocks for
//          a rollback segment in the tablespace.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
//          files to the tablespace indicated.

ORA-1650: unable to extend rollback segment

Hi,
We have 20 RBS's and in our production instance we got very frequent alerts related to ORA-1650: unable to extend rollback segment continuously. When I looked for select STATUS from v$rollstat; I could see most of them are with FULL status. after couple of hours they disappeared and status became online.
How to avoid these type of alerts?
REgards

What version of Oracle?
If you are 9ir2 or later, you should be going to automatic undo management. Though it won't help your 'we cannot add space' restriction. That's not an Oracle problem, that's a corporate issue.
This problem may be caused by poor transaction design with too many processing doing too infrequent commits. That's not an Oracle problem either, that's a corporate/development issue.
So...you don't have an Oracle problem.
You can't stop the 1650s from occurring if you are unwilling to add space or address application issues. However, you can set up an email filter so that any emails containing ORA-01650 in the header or body get automatically sent to the trash.
<sarcasm>
If you can't solve a problem, then just ignore it!
</sarcasm>

Rollback segments - database logging

Got a problem...
We are trying to move data from one database to another using: INSERT INTO table1 (SELECT a,b,c FROM table2@db2). The problem we are having is that the amount of data being moved with this in sert command is too great - we are getting an error indicating that our rollback segment is not large enough - ORA-01562: failed to extend rollback segment number 4.
Unfortunately, we are not going to be able to increase the size of the rollback segment any further than we already have. Is there a way to disable the database logging that occurs?
I tried using INSERT INTO table1 dbms_disable_logging (SELECT a,b,c FROM table2@db2), but noticed no difference - same error.
Any ideas?
Thank you,
Dan

We use select..into all the time in an unlogged mode for speed and rollback space reasons.
We replicate fifty million row tables with a minimal amount of rollback segment (<50MB).
In unlogged mode we can replicate 50 million rows in under forty minutes - that's smokin!
Oracle version 8 or greater introduced this concept. I am running 8.1.6.
You need to alter the table to disable logging and then perform the select into.
The table alter only takes seconds.
ALTER TABLE IDMDBO.DIM_PLANS NOLOGGING
Then do the select into and then turn logging back on (if so desired).
You can also disable logging at the table space level.
Keep in mind there are only a few database operations that can be performed unlogged and select..into is one of them.
There is currently no way to carte blanche disable transaction logging - hopefully this will be coming soon!
Cheers.
- Brendan Sullivan
null

ORA-01555: snapshot too old: rollback segment number 8 with name

Hi,
Database version is Oracle8i Enterprise Edition Release 8.1.7.4.0
I am struggling to fix this error, since I have not worked on 8I DATABASE.
We getting this kind of error very frequently in one of the 8i database.
ORA-01555: snapshot too old: rollback segment number 8 with name "ROLLBACK08" too small
How do i fix this permantely.
I have verified the RBS configured in the db.
SEGMENT_NAME TABLESPACE_NAME OWNER STATUS
SYSTEM SYSTEM SYS ONLINE
ROLLBACK0 SYSTEM SYS OFFLINE
ROLLBACK02 RBS1 SYS ONLINE
ROLLBACK03 RBS1 SYS ONLINE
ROLLBACK04 RBS1 SYS ONLINE
ROLLBACK05 RBS1 SYS ONLINE
ROLLBACK06 RBS1 SYS ONLINE
ROLLBACK07 RBS1 SYS ONLINE
ROLLBACK08 RBS1 SYS ONLINE
ROLLBACK09 RBS1 SYS ONLINE
ROLLBACK10 RBS1 SYS ONLINE
ROLLBACK01 RBS1 SYS ONLINE
SQL> SELECT t1.name, t2.extents, t2.rssize, t2.optsize, t2.hwmsize, t2.xacts, t2.status FROM v$rollname t1, v$rollstat t2 WHERE t2.usn = t1.usn ;
NAME EXTENTS RSSIZE OPTSIZE HWMSIZE XACTS STATUS
SYSTEM 7 770048 770048 0 ONLINE
ROLLBACK02 2 41934848 262144000 41934848 0 ONLINE
ROLLBACK03 3 62906368 262144000 62906368 1 ONLINE
ROLLBACK04 3 62906368 262144000 62906368 0 ONLINE
ROLLBACK05 2 41934848 262144000 41934848 0 ONLINE
ROLLBACK06 3 62906368 262144000 62906368 1 ONLINE
ROLLBACK07 3 62906368 262144000 62906368 1 ONLINE
ROLLBACK08 3 62906368 300146688 62906368 0 ONLINE
ROLLBACK09 3 62906368 262144000 62906368 1 ONLINE
ROLLBACK10 3 62906368 262144000 62906368 1 ONLINE
ROLLBACK01 3 62906368 300146688 62906368 0 ONLINE
NAME0     USER0          RSSIZE Wraps Extents Shrinks     OPTSIZE     COMM0
ROLLBACK01          62906368     19     3     0 300146688 lookup
ROLLBACK02          41934848     0     2     0 262144000 lookup
ROLLBACK03 OPS$RTRADM     62906368     20     3     0 262144000 lookup 50
ROLLBACK04          62906368     34     3     0 262144000 lookup
ROLLBACK05 OPS$RTRADM     41934848     28     2     0 262144000 No Command
ROLLBACK06 OPS$RTRADM     62906368     21     3     0 262144000 lookup 50
ROLLBACK07 OPS$RTRADM     62906368     25     3     0 262144000 lookup 50
ROLLBACK08          62906368     32     3     0 300146688 lookup
ROLLBACK09 OPS$RTRADM     62906368     20     3     0 262144000 Select
ROLLBACK10 OPS$RTRADM     62906368     24     3     0 262144000 lookup 50
SYSTEM               770048     0     7     0     lookup
Can someone help ... who to set the RBS size here... i dont want this error happens here.. what i need to look or check.

lm**** wrote:
Hi,
Database version is Oracle8i Enterprise Edition Release 8.1.7.4.0
I am struggling to fix this error, since I have not worked on 8I DATABASE.
We getting this kind of error very frequently in one of the 8i database.
ORA-01555: snapshot too old: rollback segment number 8 with name "ROLLBACK08" too small
How do i fix this permantely. upgrade to supported Oracle version since V8.1.7 has not been supported this Century.

Rollback segment in locally manage tablespace

Is it possible to create rollback segment in
locally manage tablespace in oracle 8i(8.1.6)
kuljeet pal singh

Srini,
Both the 10gR2 and 11gR2 versions of the database are using automatic undo management.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL> show parameter undo
NAME TYPE VALUE
_undo_autotune boolean TRUE
undo_management string AUTO
undo_retention integer 14400
undo_tablespace string UNDOTBS1
SQL>
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> show parameter undo
NAME TYPE VALUE
undo_management string AUTO
undo_retention integer 14400
undo_tablespace string UNDOTBS1
SQL>
Do you know anything about Oracle no longer automatically creating R0 in 11gR2?
Thanks,
Bill

Rollback Segment

I have a UNIX script through which i call a procedure. In that procedure i have two statements
EXECUTE IMMEDIATE 'ALTER ROLLBACK SEGMENT R01 SHRINK';
EXECUTE IMMEDIATE 'SET TRANSACTION USE ROLLBACK SEGMENT R01';
The procedure gives me the error insufficent insufficent privileges. But when i execute these statements in SQL*Plus (with same username password) they are running fine.
Any Help ??

Which is the exact Oracle message error do you have ?
What is your Oracle version ?
if you get
"ORA-01650 unable to extend rollback segment ... by ... in tablespace ...", you could extend one of your rollback segment tablespace datafile with:
ALTER DATABASE DATAFILE .... RESIZE ... or add a new datafile to the tablespace:
ORA-01650 unable to extend rollback segment string by string in tablespace string
Cause: Failed to allocate an extent for rollback segment in tablespace.
Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.
Message was edited by:
Pierre Forstmann

Export backup failing with ORA-1555snapshot too old: rollback segment ERROR

DB version =8.1.7.4
OS=Solaris =5.10.
I know this is outdated. But still we are supporting this version of database.
We are facing ORA-1555 error daily when we are running the export backup of database. Consistent parameter is set to N .
I needed to know why export uses rollback segments during export operation. even though CONSISTENT parameter is N.
Thanks,
Edited by: ahshivap on Dec 12, 2012 5:19 AM

Hi,
Consistent=y just mean the tables are consistent with each other. Oracle still has to guarantee that each individual table is at least consistent with itself. That's your issue.
Regards,
Harry

ORA-01555: snapshot too old: rollback segment number

I getting error while i am taking export one of the table.
EXP-00056: ORACLE error 1555 encountered
ORA-01555: snapshot too old: rollback segment number with name "" too small
ORA-22924: snapshot too old
Export terminated successfully with warnings.
can someone advise me

1) What version of Oracle?
2) Is UNDO_MANAGEMENT set to AUTO? Or are you still using manual undo management?
3) What is your UNDO_RETENTION? How quickly are you generating UNDO? How big is your UNDO tablespace?
4) How long does the export run?
5) Did you specify CONSISTENT=Y in the export? If so, is that necessary?
6) What else is going on? Is it possible to run the export during a quieter period?
Justin

USING DEFAULT LOCAL ROLLBACK SEGMENT

Hi,
DB Version is 10.2.0.4
Recently Noticed a MV refresh taking various time to complete. The MV refresh starts at 9pm and completes some time at 1am or 12am are sometimes very fast at 10pm. The number of records are almost same. There are no locks in the db during that time.. Opening the MV script i could see
REFRESH COMPLETE
WITH ROWID
USING DEFAULT LOCAL ROLLBACK SEGMENT
DISABLE QUERY REWRITE ASUsing default local rollback segment - is that allocation of rollback segment causes this
Referred the manul
http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_6002.htm - where it says this clause is not valid if the DB is in automatic undo mode.
thanks,
baskar.l

Rollback segment is a concept from Oracle 8i where it last showed up. This clause is preserved only for upward compatibility, but it is obsolete.
On the other hand, why do you worry about rebuilding the complete MV? either way you perform a full refresh, not a fast refresh.
If you are concerned with the time it takes to be full-refreshed find out if it is possible to have it in fast-refresh mode, tune the underlying query and make sure there are no other concurrent processes negatively affecting the I/O throughput.
~ Madrid
http://hrivera99.blogspot.com

ROLLBACK SEGMENT VERSION 7.3

Similar Messages

Maybe you are looking for