Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...

ORA-01545: rollback segment 'string' specified not available

Answer Posted / guest

Cause: Either: 1) An attempt was made to bring a rollback
segment online that is unavailable during startup; for
example, the rollback segment is in an offline tablespace.
2) An attempt was made to bring a rollback segment online
that is already online. This is because the rollback segment
is specified twice in the ROLLBACK_SEGMENTS parameter in the
initialization parameter file or the rollback segment is
already online by another instance. 3) An attempt was made
to drop a rollback segment that is currently online. 4) An
attempt was made to alter a rollback segment that is
currently online to use unlimited extents. 5) An attempt was
made to online a rollback segment that is corrupted. This is
because the rollback is specified in
_corrupted_rollback_segments parameter in initialization
parameter file.

Action: Either: 1) Make the rollback segment available; for
example, bring an offline tablespace online. 2) Remove the
name from the ROLLBACK_SEGMENTS parameter if the name is a
duplicate or if another instance has already acquired the
rollback segment. 3) Bring the rollback segment offline
first. This may involve waiting for the active transactions
to finish, or, if the rollback segment needs recovery,
discover which errors are holding up the rolling back of the
transactions and take appropriate actions. 4) Same as 3). 5)
Remove the name from the _corrupted_rollback_segments parameter.

Please add more information about this Error

Is This Answer Correct ?    0 Yes 0 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

invalid quantity specification negative quantity are not allowed for this item please check this item definition quantity

3386


IMP-00070: Lob definitions in dump file are inconsistent with database.

1750


ORA-26094: stream format error: input column overflow

2815


ORA-26027: unique index string.string partition string initially in unusable state

6751


ORA-16516: The current state is invalid for the attempted operation.

8824


IMP-00064: Definition of LOB was truncated by export

6418


ORA-07497: sdpri: cannot create trace file 'string'; errno = string.

2809


IMP-00063: Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier

2734


ORA-26079: file "string" is not part of table string.string

1959


How to resolve QSM-01108 error. I have no OR conditions in my query, but do have 9 IN conditions. The error says the max limit is 2 while I have 257 number of disjuncts. However, if I remove even a single IN condition, the query is rewritten. I cannot change my query. How can I resolve this issue?

2723


ORA-26084: direct path context already finished

1952


Hi guys, I have four tables those are emp,dept,eliminate and uneliminate. i wrote small cursor..when i run, it display one error (ORA-01403 nodata found)... The query is: Declare cursor c1 is select e.ename emp_name from emp e,dept d where e.deptno=d.deptno group by deptno; r1 c1%rowtype; test_emp varchar2(200); begin for r1 in c1 loop begin select eliminate_emp into test_emp from eliminate t,uneliminate ut where t.number=ut.number and t.deptno=e.deptno and rownum<1; end; dbms_output.put_line(r1.emp_name); end loop; end; Thanks...

2601


NZE-28890: Entrust Login Failed

1884


ORA-26030: index string.string had string partitions made unusable due to:

1941


ORA-26082: load of overlapping segments on table string.string is not allowed

1770