Shrinking of rollback segments may result in ORA-1555s. If you need to shrink
them, do so during a slow time.
Not shrinking rollback segments may result in ORA-1562 unable to extend rbs.
"Satav, Pawan" wrote:
> Hi,
> Can anyone point pros/cons of shrinking a rollback
Hi,
Can anyone point pros/cons of shrinking a rollback segment ? (other
than performance overheads associated with extent allocation and
reallocation)
Optimal is not set for my rollback segments. Recently I shrunk a
rollback segments which had more than 100 extents allocated to it
1.) Correct, except that the DBA can always shrink it manually.
2.) Well, that's true, but a rollback segment w/ optimal set could
conceivably grow to fill the tablespace as well. It depends on the size
of the rollback tablespace and the size(s) of your transaction(s). The
reason that
1) rollback segment will
not shrink.
Correct, assuming you do not shrink it manually.
2) It will keep growing till
tablespace fills up.
Correct assuming that you have a SQL statement that causes the rollback
segment to grow in such a way and that you have no constraints on the
Hi,
A simple rollback segment question. If I do not set a optimal then can I assume following
1) rollback segment will not shrink.
2) It will keep growing till tablespace fills up.
3) And there will be no 'snapshot too old' errors?
ThanksA Joshi <[EMAIL PROTECTED]> wrote
Hi all
I am getting ORA-01555 in my database and the solution is to create
huge rollback segments but my doubt is how to calculate the size of this
huge rollback segments . Now I have 24 G of space in rollback segment
tablespace .But still i am getting the error.The
ed to
another
segment, hence the need to perform these actions at a quiet time. When an
rbs
is taken offline, all transactions currently using the rbs are allowed to
complete (either commit or rollback). As these transactions are processing,
the
status of the segment is 'Pending Offline'.
Mike,
When an RBS is taken offline, the undo information is not transfered to another
segment, hence the need to perform these actions at a quiet time. When an rbs
is taken offline, all transactions currently using the rbs are allowed to
complete (either commit or rollback). As these transactions
Daniel,
Thank-you very much for your clear answer. Very helpful. When a RBS is taken
off-line, does it transfer the rollback information to another segment?
Thanks,
Mike
-Original Message-
Sent: Monday, December 22, 2003 1:44 PM
To: Multiple recipients of list ORACLE-L
There is no
datafiles appropriately. Don't go to small or you run
the risk of transactions failing due to "unable to extend" errors.
Daniel Fink
Michael Milligan wrote:
> The datafile for our rollback segments gre huge because of an improper
> setting. Even setting optimal and shrink, etc
The datafile for our rollback segments gre huge because of an improper
setting. Even setting optimal and shrink, etc., won't help because the
segments are scattered. Do I have to create a new tablespace? Can I change
the datafile a rollback segment writes to and then take the other offline?
Subject: Re: ** can two processes use the
same rollback extent
[EMAIL PROTECTED]
IIRC, a segment will not wrap into an extent that has an active transaction
in it, but rather allocate a new extent. So the answer is...it depends.
Daniel Fink
A Joshi wrote:
Hi,
One rollback segment can be used by multiple transactions/processes
but what about the extents? Is it safe to
Yes Jonathan:
I think that 400 byte concept came from one of the TPC benchmarks during
Oracle 7 (or ORacle 6) days where the average undo size for a transcation
was around 380+ bytes. So they had rounded that to 400 bytes and a maximum
of 5 blocks will be linked to the freelist in the undo segment
A single block can only be 'owned' by one transaction
at a time, but when a transaction commits, it may put
its last undo block into that segment's 'free pool' list if there
is a lot of free space left in the block so that it can be made
available for new transactions . (Gaja Vaidyanatha quoted
4
of list ORACLE-L
Sent: Wednesday, December 03, 2003 9:09
AM
Subject: ** can two processes use the
same rollback extent
Hi,
One rollback segment can be used by multiple
transactions/processes but what about the extents? Is it safe to assume that
only one
Hi,
One rollback segment can be used by multiple transactions/processes but what about the extents? Is it safe to assume that only one transaction/process can use one extent? What is a good way to size the extent for warehousing tasks? Or guess the rollback generated and size needed.
Thank
duce the chance
of
a 1555.
Daniel Fink
Michael Milligan wrote:
> I have a client where rollback segments were set up RBS01-RBS05, all in a
> tablespace called RBS. The person who set it up set %INCREASE at 50%.
Well,
> I shrank the segments to themselves down to less than 500MB total fro
still scattered throughout the tablespace, preventing
me from resizing the datafile.
Thanks,
Mike
-Original Message-
Sent: Monday, November 17, 2003 2:44 PM
To: Multiple recipients of list ORACLE-L
Michael Milligan wrote:
>
> I have a client where rollback segments were set up
The high water mark for the rollback segments is preventing you from shrinking the files.
Use "alter rollback segment storage ( optimal ) "
to set an optimal size for the segment, then use 'alter rollback segment shrink'
to shrink the rollback.
You may want to unset the op
slow time to reduce the chance of
a 1555.
Daniel Fink
Michael Milligan wrote:
> I have a client where rollback segments were set up RBS01-RBS05, all in a
> tablespace called RBS. The person who set it up set %INCREASE at 50%. Well,
> I shrank the segments to themselves down to less th
Michael Milligan wrote:
>
> I have a client where rollback segments were set up RBS01-RBS05, all in a
> tablespace called RBS. The person who set it up set %INCREASE at 50%. Well,
> I shrank the segments to themselves down to less than 500MB total from
> 4.6GB! But in using
I have a client where rollback segments were set up RBS01-RBS05, all in a
tablespace called RBS. The person who set it up set %INCREASE at 50%. Well,
I shrank the segments to themselves down to less than 500MB total from
4.6GB! But in using ALTER DATABASE DATAFILE . . . RESIZE . . . it won'
AIL PROTECTED] wrote:
> >
> > I have a problem loading data from flat file using SQL*Loader. The problem is
> > unable to extend rollbacksegment. Is there a way to assign BIG rollback segment to
> > SQL*Loader transaction? If not what is the work around to load huge volume
[EMAIL PROTECTED] wrote:
>
> Dear Gurus,
>
> I have a problem loading data from flat file using SQL*Loader. The problem is unable
> to extend rollbacksegment. Is there a way to assign BIG rollback segment to
> SQL*Loader transaction? If not what is the work around to load h
Dear Gurus,
I have a problem loading data from flat file using SQL*Loader. The problem is unable
to extend rollbacksegment. Is there a way to assign BIG rollback segment to SQL*Loader
transaction? If not what is the work around to load huge volume of data without using
TRUNCATE option?
Thanks
til I disabled parallel rollback
(fast_start_parallel_rollback parameter IIRC).
Tanel.
- Original Message -
From:
AK
To: Multiple recipients of list ORACLE-L
Sent: Tuesday, August 26, 2003 1:49
AM
Subject: no rollback ??
There is one log running process in db here
Maybe your rollback is done in background, because
a session crashed or was killed?
Tanel.
- Original Message -
From:
AK
To: Multiple recipients of list ORACLE-L
Sent: Tuesday, August 26, 2003 1:49
AM
Subject: no rollback ??
There is one log running
pond to ORACLE-L
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
cc:
Subject: no rollback ??
There is one log running process in db here and I waiting for it to finish since last 3 hours. when I see sql_address in v$session for this session
There is one log running process in db here and I
waiting for it to finish since last 3 hours. when I see sql_address in v$session
for this session and then find sql in v$sqlarea its a update statement . But
then there is no entry in v$transaction . How'z it possible that there no
rol
s clear that RBSnn were created in an undo tablespace titled RBS.
To remove system managed undo segments (_SYSSMUn$) one must drop the undo tablespace
itself.
But, in your case, you will first have to:
1. Create a new, normal tablespace, say, rollback_ts, to hold new rollback segments
(do n
If you are now running in manual undo mode and have created rollback segments, you can
remove the undo segments. Verify that the segments are offline and you are not using
them. Then drop the undo tablespace. This is the only way to get rid of them.
[EMAIL PROTECTED] wrote:
>
> yes
PROTECTED] wrote:
>
> I use manual managed undo tablespace but there are some system named rollback
> segments on that
> tablespace ( I did not created them ) and they can not be dropped.
> What are they , how can I drop them.
> --
> Please see the official ORACLE-L FAQ:
select segment_name, tablespace_name from dba_rollback_segs;
SQL> select a.usn, a.name, b.status
2 from v$rollname a,
3 v$rollstat b
4 where a.usn = b.usn;
--- [EMAIL PROTECTED] wrote:
> I use manual managed undo tablespace but there are some system named rollback
> s
The scenario you describe is not consistent with manual undo. Was the database
created/started with automatic undo and you have switched to manual?
[EMAIL PROTECTED] wrote:
>
> I use manual managed undo tablespace but there are some system named rollback
> segments on that
> tab
tat b
4 where a.usn = b.usn;
--- [EMAIL PROTECTED] wrote:
> I use manual managed undo tablespace but there are some system named rollback
> segments on that
> tablespace ( I did not created them ) and they can not be dropped.
> What are they , how can I drop them.
> --
&
I use manual managed undo tablespace but there are some system named rollback
segments on that
tablespace ( I did not created them ) and they can not be dropped.
What are they , how can I drop them.
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: <[EM
Hi!
You can't anymore.
Either:
1) remove set transaction commands from your scripts
2) if can't remove 'em, set undo_suppress_errors=true in spfile/init.ora
that your scripts wont error out
3) use old fashioned rollback segments - set undo_management=manual in
paramet
when we were using oracle8i , whe had some process which use "set transaction use
rollback segment".
and now we use undo tablespace and we have still same porocesses .
how can set a rollbback segment for process with undo tablepsace
--
Please see the official ORACLE-L
Can anyone point me to an article or white paper that goes into detail on
this. When I RTFM, it just says use Undo TBS, don't worrry about it and all
your problems will be solved.
We are upgrading from Oracle8 to 9i and currently have Rollback segments in
4 tablespaces spread over 4 disk
third party applications, if
developers haven't coded their apps to use a large rollback segment for
certain transactions (which I find is the case with most developers ;-) )
then the only option is to turn off all but the large rollback seg.
Cheers
Lee
-Original Message-
Sent: 16 July
I
think that's probably the case with most third party applications, if developers
haven't coded their apps to use a large rollback segment for certain
transactions (which I find is the case with most developers ;-) ) then the only
option is to turn off all but the large ro
Yes you are right, sorry but I made a mistake, since we are
using Baan IVc4 which works against Oracle we have no means to interfere with
its transactions when they are commited to Oracle and we can not modify them so
that it uses a specific rollback segment, so the only way for us to
set
transaction use rollback segment only works if it's the first statement in
your transaction, an easy way to make sure this is the case is to issue a commit
directly before issuing this statement.
I
believe this has been a feature of Oracle since way back in version 7 (Correc
Which database version are you using? as long as I know, at
least on Oracle 8.0.6 you can not specify which rollback segment a particular
transaction should use. We disable all rollback segments and only enable those
which we know won't make big updates / deletes
Ave !
Is there any reason not to
keep maxextents always unlimited :) Extentsize should
be reasonable of
course.
Br.
Jorma
-Original Message-From: ext venkat Rama
[mailto:[EMAIL PROTECTED]Sent: 16 July, 2003 07:34To:
Multiple recipients of list ORACLE-LSubject: Rollback
Segs
Hi Friends,
I have 150Gb database with 30 rollback segs with optimal settings!! for normal operations no problems!! But we are doing massive updates for some of big tables!! So we are using vb programs and connecting to the database thru odbc dsn. My first question is how to set transaction use
can anyone please help?
errors like below when any of the redo or rollback raw LVs are created using stripe:
CREATE TABLESPACE RBS DATAFILE '/dev/vgrbs/rrbs01.dbf' SIZE 8000M REUSE AUTOEXTEND OFF
MINIMUM EXTENT 512K DEFAULT STORAGE ( INITIAL 512K NEXT 512K MINEXTENTS 8 MAXEXTENTS
blocks will not be reused as often. This could
cause space management problems if there is not enough space in the tablespace or
other processes are causing rollback segments to shrink.
The short version is that frequent commits = additional housekeeping (impact
can't be known exactly
sibly
related to rollback.
I said I was not aware of this and would look into it but I had never heard
of this before and couldn't find any information on this so of course I'm
sending mail to the list. Both items sound bogus to me. I've really never
heard where committing more freque
Thanks KG, for your reply. Well, it whets my appetite for more.
This surprises me. All the documentation I have read so far tells me that
multiple transactions cannot be write to the same rollback segment data
block.
My first question was basically "well, if many transactions can write
Rajesh:
I am not sure which document you are referring here. If that documentation
says more than one transaction can not use a rollback segment data block
means, I would say the documentation is incorrect in this case. But this
can not happen concurrently. IT can happen serially.
Each rollback
>From the docs : Many active transactions can write concurrently to a single
rollback segment--even the same extent of a rollback segment; however, each
data block in a rollback segment's extent can contain information for only
a single transaction.
1) Now, when oracle writes to the las
Hi,
When you create a RBS the creation entry will be there in the alert.log
Senthil.
-Original Message-
[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 12:40 PM
To: Multiple recipients of list ORACLE-L
Is there any way to find out created time stamp for a rollback segment
apart from
>
>Is there any way to find out created time stamp for
>a rollback segment
>apart from looking into alert.log.
>
>TIA
>Kranti
>
If you think of some column in a dictionary table, I don't think so. Auditing is
another solution, besides scanning the alert.log file
Is there any way to find out created time stamp for a rollback segment
apart from looking into alert.log.
TIA
Kranti
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you have
received it in error, please notify the
urrent to
this was an RMAN backup and DBMS_STATS.GATHER_TABLE_STATS(...) which was being run on
the same schema being backed up via the user level export. There was no other end user
access to the schema data. Since exp got the error I assume it was reading from the
rollback segments but why?
s) in that schema prior to starting the export? Heavy
DML, may be?
This could be a case of 'delayed block cleanout'. Export triggered the cleanout and
wanted to
access the rollback segments.
If no table data was modified after export started reading that table, then there is
Steve,
You may have to dig a little further...
What happened to those table(s) in that schema prior to starting the export? Heavy
DML, may be?
This could be a case of 'delayed block cleanout'. Export triggered the cleanout and
wanted to
access the rollback segments.
If no
backup and
DBMS_STATS.GATHER_TABLE_STATS(...) which was being run on the same
schema being backed up via the user level export. There was no other end
user access to the schema data. Since exp got the error I assume it was
reading from the rollback segments but why? I'm suspecting dbms_stat
HELP...
Has anyone encountered rollback problems while running dbms_stats?
-Original Message-
Sent: Thursday, May 29, 2003 10:15 AM
To: Multiple recipients of list ORACLE-L
Oh yeah, for the export consistent=N
-Original Message-
Sent: Thursday, May 29, 2003 9:14 AM
To: '[
user level export. There was no other end user
access to the schema data. Since exp got the error I assume it was reading from the
rollback segments but why? I'm suspecting dbms_stats. We have ample RBS. Is there any
significant undo generated by dbms_stats or RMAN which could create this pr
current to
this was an RMAN backup and DBMS_STATS.GATHER_TABLE_STATS(...) which was being run on
the same schema being backed up via the user level export. There was no other end user
access to the schema data. Since exp got the error I assume it was reading from the
rollback segments bu
alter rollback segment XXX storage (optimal null);
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk
The educated person is not the person
who can answer the questions, but the
person who can question the answers -- T. Schick Jr
One-day tutorials:
http://www.jlcomp.demon.co.uk
Sometimes the extents should be larger (fewer larger extents, then many
small extents).
- Original Message -
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Saturday, April 05, 2003 1:30 AM
> Yes, your assumption is right. Create new rollback
>
was changed back to READ-ONLY.
Due to whatever reason (I could not gather whether
there (were/were not) any long-running queries), the
clean out did not occur on some of the objects, and
this caused the ORA-1555, as his current query was
trying to build a read-consistent image from the
rollback s
Yes, your assumption is right. Create new rollback
segments without the OPTIMAL clause, bring them
online, take the old ones offline, blow the old ones
away, document the new ones in your init.ora, remove
the old ones from your init.ora. See whether this
solves your problem. My guess is that you
I USA
-Original Message-
Sent: Friday, April 04, 2003 12:54 PM
To: Multiple recipients of list ORACLE-L
Rich,
The overcommiting is a definite suspect and is worth
looking into. ALso, do you by chance have OPTIMAL set
on your rollback segments? If so, I'd suggest you
remove the OPTI
In general, you don't need to do this in
recent versions of Oracle. Oracle knows
that all the data in the tablespace MUST
have been committed before the tablespace
was switched to read-only (you can only
switch a tablspace to readonly when there
are no active transactions that started before
th
Rich,
The overcommiting is a definite suspect and is worth
looking into. ALso, do you by chance have OPTIMAL set
on your rollback segments? If so, I'd suggest you
remove the OPTIMAL clause and try again. In my
experience, I have had my share of hassles with
OPTIMAL. Even when it was
dified".
2. Create a new rollback tablespace. You can do this quickly. Ask the
report users to hold off running reports for a few minutes, then offline the
current rollback tablespace. It won't go off until all current transactions
complete.
3. Modify the application. In my expe
"Jesse, Rich" wrote:
>
> Hey all,
>
> Fighting with a lot of ORA-1555s lately on 8.1.7.4 on HP/UX. Most of them
> are now coming from long-running Business Objects (B.O.) queries against our
> OLTP DB. I think I need to recreate the RBS tablespace (currently 1MB
> extents in LMT), but until I c
Hey all,
Fighting with a lot of ORA-1555s lately on 8.1.7.4 on HP/UX. Most of them
are now coming from long-running Business Objects (B.O.) queries against our
OLTP DB. I think I need to recreate the RBS tablespace (currently 1MB
extents in LMT), but until I can get time to do that, I'd like to
're looking for here is the 'XACTS' column to be zero for the rollback segment
you want to take offline.
Once you see it is not in use, shrink it: 'alter rollback segment RBSNAME shrink;'.
Then take it offline. If it is taking up too much space, maybe drop and recreated it
wi
You can take the rollback segment offline. It will not impact any currently
running transactions and no new transactions will be assigned to it. Oracle
will not let you drop a rollback segment while there are any active transactions
writing undo to the rollback segment. IIRC, the v
s Williams
DBA, 40%OCP, 100% DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
-Original Message-
Sent: Friday, March 14, 2003 3:54 PM
To: Multiple recipients of list ORACLE-L
I have recently found that one temporary rollback segment in system
tablespace is having more then 600 extnets . It look
I have recently found that one temporary rollback
segment in system tablespace is having more then 600 extnets . It looks like
previous dba created this rollback segment at the time of db creation and forgot
to take it offline .
Now how do I find it this rollback segment is being
used
And what Pete said does work.
Here is a report from my testing of undo mode switching (AUM <-> MUM). Rollback
tablespace was already created.
SQL> create rollback segment rbs01 tablespace rollback;
create rollback segment rbs01 tablespace rollback
*
ERROR at line 1:
ORA-01552: cannot u
Mike, et.al,
Mea Culpa. Please ignore my previous post. I failed to properly
context switch from my Automatic Undo mode.
IIRC, as of 7.3, the requirement for a second rollback segment in
SYSTEM was removed, with minor exceptions. I think the one that is
biting you is that a second RBS
Title: RE: Create rollback segment under ORACLE 9ir2 failed
I see other people have already answered your question, but would it be presumptuous of me to ask why you are using ROLLBACK segments instead of an UNDO tablespace?
> -Original Message-
> From: mike mon [mailto:
Mike
The only way this would have worked under 8i is if you had already
created a dummy rollback segment in the SYSTEM tablespace. Something
like this should work (before or after the CREATE TABLESPACE
rollback_space)
SQL> connect / as sysdba;
SQL> CREATE ROLLBACK SEGMENT dummy;
Mike,
Check the setting for undo_management. It needs to be set to MANUAL.
mike mon wrote:
I am create database on ORACLE 9iR2 and fail on create
rollback segment.
SQL> create tablespace rollback_space datafile
2 '/u4/oradata/TRAN/rbs01TRAN.dbf'
size 800M
I am create database on ORACLE 9iR2 and fail on create
rollback segment.
SQL> create tablespace rollback_space datafile
2 '/u4/oradata/TRAN/rbs01TRAN.dbf'
size 800M
3 default storage (
4 initial 256k
5 next
years since I tested an 8.0.x db, but I do
not recall seeing any changes in rollback segments from 7.3 to 8.1.
Have you converted from Dictionary to Locally managed RBS
tablespaces? When you upgraded, did you change any of the settings, like
OPTIMAL, for the rollback segments? Were they
were made.
-Original Message-
Sent: Monday, March 10, 2003 5:39 PM
To: Multiple recipients of list ORACLE-L
Did any of the rollback segment storage parameters (i.e. INITIAL, NEXT,
PCTINCREASE, MINEXTENTS, MAXEXTENTS, OPTIMAL) or the number of rollback
segments change between 8.0.5 and 8.1.7
Did any of the rollback segment storage parameters (i.e. INITIAL, NEXT,
PCTINCREASE, MINEXTENTS, MAXEXTENTS, OPTIMAL) or the number of rollback
segments change between 8.0.5 and 8.1.7? Changes to any of these variables
could impact the space available for storing inactive undo blocks for
read
Kevin,
The ORA-01555 errors are almost certainly symptoms, not the actual
problem. It has been a few years since I tested an 8.0.x db, but I do
not recall seeing any changes in rollback segments from 7.3 to 8.1.
Have you converted from Dictionary to Locally managed RBS
tablespaces? When
Evening;
Has anyone noticed any difference on the way Oracle uses Rollback Segments
on 8.1.7.4 versus 8.0.5 ??
Ever since upgrading to 8.1.7.4 from 8.0.5 on our Solaris servers we have
noticed more SNAPSHOT TOO OLD errors than we used to.
Are there any suggestions as to rollback tuning that
Hi to all,
Thanks for the comments, but none of them worked for me,
I tried putting a comment in the init.ora file to the rollback segments line
to recreate the controlfile. No success.
I did get a message telling me that there was a 'MISSING000' datafile in
$ORACLE_HOME/dbs, and tri
Title: Which rollback segment is currently active?
Hi,
If you
want to drop one of the the RBS, First you have to check in the application
level. Which user that used the rollback segment.
select
username,name,used_ublk, start_time,sum(waits),sum(gets), sum(waits)*100/sum(gets)from
v
Title: Which rollback segment is currently active?
select rs.usn, xacts
active_transactions, gets, waits, writes, name from v$rollstat rs,
v$rollname rnwhere rs.usn = rn.usn
This
may help...
-Original Message-From: Nguyen, David M
[mailto:[EMAIL PROTECTED]]Sent: Tuesday, February
David
This query will show sessions using rollback segments:
select s.username, s.sid, rn.name, rs.extents
,rs.status, t.used_ublk, t.used_urec
,do.object_name
fromv$transaction t
,v$session s
,v
Title: Which rollback segment is currently active?
Check
v$rollstat for xact > 0.
-Original Message-From: Nguyen, David M
[mailto:[EMAIL PROTECTED]]Sent: Tuesday, February 04, 2003 6:24
PMTo: Multiple recipients of list ORACLE-LSubject: Which
rollback segment is curren
Title: Which rollback segment is currently active?
I have three rollback segments which all show ONLINE. I want to drop one of them but I need to know which one should I drop. How do I find out which one is good to drop?
SVRMGR> select segment_name,owner,tablespace_name,status f
search?hl=en&ie=ISO-8859-1&q=max_rollback_segments>
> &ie=ISO-8859-1&q=max_rollback_segments
> you can find a lot of information on this parameter. Oracle needs to
> allocate a finite amount of memory to manage rollback segments, so there
> must be a upper boundary som
Shuan - If you go to
http://www.google.com/search?hl=en
<http://www.google.com/search?hl=en&ie=ISO-8859-1&q=max_rollback_segments>
&ie=ISO-8859-1&q=max_rollback_segments
you can find a lot of information on this parameter. Oracle needs to
allocate a finite amount of mem
: Can
not place rollback segment online
Dear all DBAs,
i'm using Oracle 8.0.5 on Linux 6.4 kernel
2.2.14.
when i try to place the rollback segment
online,
it show error as below:
SQL> ALTER ROLLBACK SEGMENT "RB28"
ONLINE;ALTER ROLLBACK SEGMENT &quo
Dear all DBAs,
i'm using Oracle 8.0.5 on Linux 6.4 kernel
2.2.14.
when i try to place the rollback segment
online,
it show error as below:
SQL> ALTER ROLLBACK SEGMENT "RB28"
ONLINE;ALTER ROLLBACK SEGMENT "RB28" ONLINE*ERROR at line
1:ORA-01599: failed to
you've read the controlfile. Then when you
open the database the tablespace stays offline & you can drop it and it's
contents thereby cleaning up the data dictionary. Yes, you can't do that with
the rollback segments on line either, which is why you need to comment them
we don't want the database looking for them.
3) Startup mount the database.
4) alter database datafile offline drop;
5) repeat 4 as mant times as necessary;
6) alter database open;
7) create rollback segment sys1 tablespace system;
8) alter rollback segment sys1 onlin
1 - 100 of 634 matches
Mail list logo
