Rollback segment error ORA-1628

Hellow
Currently we are working on Oracle 8i database.The database contain spatial data around 10GB.We have a tablespace RBS containing 4 rollback segments. The issue is whenever we try to insert spatial data we get this error message (in the alert file)
ORA-1628: max # extents 121 reached for rollback segment R01
Failure to extend rollback segment 2 because of 1628 condition
FULL status of rollback segment 2 cleared.
I extended the size of RBS tablespace by adding another datafile, but still it doesn't help.
Also i found that RBS tablespace is marked as PERMANENT...it means the rollback data does not get flushed out periodically?Also Should this tablespace be temporary? How can i counter this problem?
Regards
Sam

Hi,
01628, 00000, "max # extents (%s) reached for rollback segment %s"
// *Cause: An attempt was made to extend a rollback segment that was
// already at the MAXEXTENTS value.
// *Action: If the value of the MAXEXTENTS storage parameter is less than
// the maximum allowed by the system, raise this value. => Alter your RBS and allow more than 121 extents to be created in this RBS.
Also i found that RBS tablespace is marked as PERMANENT.Yes, it's normal.
..it means the rollback data does not get flushed out periodically?No
Also Should this tablespace be temporary? No, this can't be
How can i counter this problem?Free advise: RTFM about Rollback Segments! Start here (8i doc) or read the Concepts book.
Regards,
Yoann.

Similar Messages

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

Rollback segment error

Hello experts,
My problem is as follows:
I need to perform a large transaction on one of my tables in my
database. I have to delete a large number of records using a
command as follows:
Delete from mytable where ordernumber like '2000%';
Each time i launch this command i have the following error:
ERROR at line 1:
ORA-01562: failed to extend rollback segment (id = 3)
ORA-01628: max # extents (30) reached for rollback segment R03
I know that i have a problem with my rollback segment. I have
thus created a large rollback segment so that my transaction can
use it.
I don't know how to tell my transaction use the large rollback
segment that i created.
(i know there is a command called set transation user rollback
segment large_rs1, i have tried it on sqlplus. it gives me
error: ORA-01453: SET TRANSACTION must be first statement of
transaction)
Please help
thanks in advance for a reply
Kind regards
Yogeeraj

First, you have to create a bigger rollback segment (i.e. RBBIG).
Then, before each query, you must type:
set transaction use rollback segment rbbig;
This will force the use of the specified rollback segment.
Hope this helps.

Rollback segment Error coming for 8 lacks Record while creating MV

Hi All,
i am creating a materialized View and it gives us 8 lacks record but when we creates in production its fails due to rollback segment does not have enough space to handle it and it did not create the MV.
can anyone help me out to resolve this issue for the below query while creating MV.
SELECT DISTINCT NVL
((ROUND ((jt_date_completed - jt_date_requested) * 24, 2)
0
) AS actual_hrs_to_complete,
NVL ((ROUND ((jt_date_responded - jt_date_requested) * 24, 2)
0
) AS actual_hrs_to_respond,
peo1.peo_name AS agent_name,
peo1.peo_user_name AS asagent_soe_id,
le.lglent_desc AS ap_system,
' ' AS assign_work_request_comment,
DECODE (jt.jt_bill_id,
138802, 'CLIENT BILLABLE',
138803, 'CONTRACTED',
138804, 'INTERNAL BILLABLE',
NULL, ' '
) AS billable,
bl.bldg_name_cc AS building, bl.bldg_id_ls AS building_id,
DECODE (bl.bldg_active_cc,
'Y', 'ACTIVE',
'INACTIVE'
) AS building_status,
DECODE (jt.jt_wrk_cause_id,
141521, 'STANDARD WEAR AND TEAR',
141522, 'NEGLIGENCE',
141523, 'ACCIDENTAL',
141524, 'MECHANICAL MALFUNCTION',
141525, 'OVERSIGHT',
141526, 'VANDAL',
141527, 'STANDARD',
141528, 'PROJECT WORK',
6058229, 'TEST',
NULL, ' '
) AS cause_type,
' ' AS comments, peo3.peo_name AS completed_by,
jt.jt_requestor_email AS contact_email,
jt.jt_requestor_name_first
|| ' '
|| jt.jt_requestor_name_last AS contact_name,
jt.jt_requestor_phone AS contact_phone,
cc.cstctrcd_apcode AS corp_code,
cc.cstctrcd_code AS cost_center,
jt.jt_date_closed AS date_closed,
jt.jt_date_completed AS date_completed,
jt.jt_date_requested AS date_requested,
jt.jt_date_responded AS date_responded,
jt.jt_date_response_ecd AS date_response_ecd,
jt.jt_date_scheduled AS date_scheduled,
DECODE (jt.jt_def_id,
139949, 'WTG VENDOR RESPONSE',
139950, 'WAITING ON PARTS',
139951, 'LABOR AVAILABILITY',
139952, 'DEFERRED- HI PRI WORK',
139953, 'WTG APPROVAL',
139954, 'FUNDING REQUIRED',
139955, 'ACCESS DENIED',
139956, 'WTG MATERIAL',
NULL, ' '
) AS deferral_reason,
jt.jt_description AS description,
jt.jt_date_resched_ecd AS ecd,
fmg.facility_manager AS facility_manager,
fl.floors_text AS FLOOR, gl.genled_desc AS general_ledger,
' ' AS kiosk_date_requested, ' ' AS kiosk_dispatch_confirmed,
' ' AS kiosk_dispatched,
eqp.equip_customer_code AS linked_equipment_alias,
eqp.equip_id AS linked_equipment_id,
eqp.equip_text AS linked_equipment_name,
DECODE (jt_originator_type_id,
1000, 'PROJECT MOVE REQUEST',
138834, 'CUSTOMER INITIATED CORRECTION',
138835, 'CUSTOMER INITIATED REQUEST',
138836, 'CORRECTIVE MAINTENANCE',
138837, 'CONFERENCE ROOM BOOKING',
138838, 'PROJECT INITIATED REQUEST',
138839, 'PLANNED PREVENTIVE MAINTENANCE',
138840, 'SELF INITATED REQUEST',
NULL, ' '
) AS originator_type,
' ' AS payment_terms, priority_text AS priority_code,
swoty.sworktype_text AS problem_type,
prop.property_name_cc AS property,
jt.jt_cost_quote_total AS quote_total,
par.levels_name AS region,
DECODE (jt.jt_repdef_id,
141534, 'ADJUSTED SETTING',
141535, 'TRAINING FOR END',
141536, 'NEW REQUEST',
141537, 'NO REPAIR REQUIR',
141538, 'REPLACED PARTS',
141539, 'REPLACE EQUIPMEN',
1000699, 'NEW REQUEST',
NULL, ' '
) AS repair_definitions,
jt.jt_repairdesc AS repair_description,
jt.jt_requestor AS requestor, ' ' AS requestor_cost_center,
jt.jt_requestor_email AS requestor_email,
jt.jt_requestor_name_first AS requestor_name,
jt.jt_requestor_phone AS requestor_phone,
' ' AS response_time, rm.room_name_cc AS room,
p1.peo_provider_code1 AS service_provider,
p1.peo_address_1 AS service_provider_address,
peocity.city_text service_provider_city,
p1.peo_provider_code1 AS service_provider_code,
peocity.city_country_name AS service_provider_country,
peocur.currency_text AS service_provider_currency,
p1.peo_name AS service_provider_description,
p1.peo_dispatch_method AS serv_prov_dispatc_hmethod,
p1.peo_rate_double AS serv_prov_double_time_rate,
p1.peo_email AS service_provider_email,
p1.peo_emergency_phone AS serv_prov_emergency_phone,
p1.peo_fax AS service_provider_fax_number,
p1.peo_home_phone AS service_provider_home_phone,
p1.peo_rate_hourly AS service_provider_hourly_rate,
p1.peo_title AS service_provider_job_title,
p1.peo_method_id AS service_provider_method,
p1.peo_cell_phone AS service_provider_mobile_phone,
p1.peo_pager AS service_provider_pager,
p1.peo_rate_differential AS service_provider_rates,
p1.peo_rate_differential AS ser_prov_shift_differential,
peocity.city_state_prov_text AS serv_prov_state_province,
DECODE (p1.peo_active,
'Y', 'ACTIVE',
'INACTIVE'
) AS service_provider_status,
p1.peo_url AS serv_prov_web_site_address,
p1.peo_phone AS service_provider_work_phone,
p1.peo_postal_code AS serv_prov_zip_postal_code, ' ' AS shift,
' ' AS skill,
DECODE (jt.jt_bigstatus_id,
138813, 'NEW',
138814, 'PENDING',
138815, 'OPEN',
138816, 'COMPLETED',
138817, 'CLOSED',
138818, 'CANCELLED',
NULL, ' '
) AS status,
lev.levels_name AS subregion, ' ' AS trade,
p1.peo_ls_interface_code1 AS vendor_id,
p1.peo_fax AS vendor_purchasing_fax,
p1.peo_vendor_site_code AS vendor_sitecode,
jt.jt_id AS vendor_ticket, p1.peo_name AS vendor_companyname,
jt.jt_requestor_vip AS vip, wo.wo_id AS work_order_no,
jt.jt_id AS work_request,
jt.jt_class_id AS work_request_class,
woty.worktype_text AS work_type, ' ' AS wr_cost,
jt.jt_description AS wr_description,
' ' AS wr_dispatch_method,
DECODE (jt.jt_bigstatus_id,
138813, 'NEW',
138814, 'PENDING',
138815, 'OPEN',
138816, 'COMPLETED',
138817, 'CLOSED',
138818, 'CANCELLED',
NULL, ' '
) AS wr_status,
ctry.country_name AS country
FROM citi.jobticket jt,
citi.property prop,
citi.bldg bl,
citi.bldg_levels bldglvl,
citi.LEVELS lev,
citi.LEVELS par,
(SELECT crstools.stragg (peo_name) facility_manager,
bldgcon_bldg_id
FROM citi.bldg_contacts, citi.people
WHERE bldgcon_peo_id = peo_id
AND bldgcon_contype_id IN (40181, 10142)
GROUP BY bldgcon_bldg_id) fmg,
citi.floors fl,
citi.room rm,
citi.general_ledger gl,
citi.legal_entity le,
citi.cost_center_codes cc,
citi.equipment eqp,
citi.worktype woty,
citi.subworktype swoty,
citi.work_order wo,
citi.jt_workers jtwo,
citi.priority,
citi.country ctry,
citi.people p1,
citi.people peo3,
citi.people peo1,
citi.city peocity,
citi.currency peocur
WHERE jt.jt_bldg_id = bl.bldg_id
AND bl.bldg_id = bldglvl.bldg_levels_bldg_id
AND bldglvl.bldg_levels_levels_id = lev.levels_id
AND lev.levels_parent = par.levels_id(+)
AND prop.property_id = bl.bldg_property_id
AND bl.bldg_active_ls <> 'N'
AND jt.jt_floors_id = fl.floors_id(+)
AND jt.jt_room_id = rm.room_id(+)
AND jt.jt_bldg_id = fmg.bldgcon_bldg_id(+)
AND jt.jt_genled_id = gl.genled_id(+)
AND gl.genled_lglent_id = le.lglent_id(+)
AND jt.jt_cstctrcd_id = cc.cstctrcd_id(+)
AND jt.jt_equip_id = eqp.equip_id(+)
AND jt.jt_id = jtwo.jtw_jt_id(+)
AND jt.jt_worktype_id = woty.worktype_id(+)
AND jt.jt_sworktype_id = swoty.sworktype_id(+)
AND jt.jt_wo_id = wo.wo_id
AND jt.jt_priority_id = priority_id(+)
AND jt.jt_date_requested >= ADD_MONTHS (SYSDATE, -12)
AND bl.bldg_country_id = ctry.country_id
AND jtwo.jtw_peo_id = p1.peo_id(+)
AND p1.peo_city_id = peocity.city_id(+)
AND jt.jt_completed_by_peo_id = peo3.peo_id(+)
AND p1.peo_rate_currency_id = peocur.currency_id(+)
AND jt.jt_agent_peo_id = peo1.peo_id(+);
Regards
shyam~

Hi,
Its ora-1555? IS your undo_retention sufficient?
Since you are developer the only option you have is to tune the query?
Am curious to know like I create materialized view so that I do not have to run complex query on the master database / or to prevent the access to master database more than once to get the same data?
Like to know which is your case because your query seem to be too complex to be the case for former. Do you think this materialized view would be used frequently in your application?
Regards
Anurag Tibrewal.

Concurrent request is failing with error "ORA-01562: "

We have Abort in production with rollback segment error as below.
Unexpected error found while deleting in staging table . 1100ORA-01562: failed to extend rollback segment number 258
This is RAC instance having 4 db nodes
Details for UNDO as follows:
SQL> SELECT tablespace_name, SEGMENT_NAME, INITIAL_EXTENT, NEXT_EXTENT, MAX_EXTENTS from dba_rollback_segs where SEGMENT_NAME='_SYSSMU258$';
TABLESPACE_NAME SEGMENT_NAME INITIAL_EXTENT NEXT_EXTENT MAX_EXTENTS
APPS_UNDOTS1 _SYSSMU258$ 131072 32765
TABLESPACE_NAME STATUS Extent Count Total Blocks SPACEINGB
APPS_UNDOTS1 ACTIVE 36 6744 .051452637
APPS_UNDOTS1 UNEXPIRED 513854 8967456 68.4162598
APPS_UNDOTS1 EXPIRED 237 2016 .015380859
Tablespace Used MB Free MB Total MB Pct. Free
APPS_UNDOTS1 70656 0 70656 0
Can you tell me how to troubleshoot error like "*ORA-01562: failed to extend rollback segment" or "snapshot too old error*"
Can you help on this issue. because this issue appeared very frequently on PROD instance.
Thanks in advance.

Can you tell me how to troubleshoot error like "*ORA-01562: failed to extend rollback segment" or "snapshot too old error*"ORA-1562 and ORA-1650 Unable to Extend Rollback Segment [ID 1066542.6]
ORA 01555 "snapshot too old: rollback segment number %s with name \"%s\" too small" [ID 1555.1]
Master Note for ORA-1555 Errors [ID 1307334.1]
TROUBLESHOOTING GUIDE (TSG) - ORA-1555 [ID 467872.1]
ORA-01555: "Snapshot too old" - Overview [ID 10630.1]
ORA-01555 "Snapshot too old" - Detailed Explanation [ID 40689.1]
Can you help on this issue. because this issue appeared very frequently on PROD instance.Please log a SR for production issues.
Thanks,
Hussein

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.

Rollback segemnt error

Hi,
I am working in oracle8i. I am receiving the error in Rollback segment.
ORA-1650: unable to extend rollback segment ROLUS12 by 256 in tablespace RBS
How to resolve the error. we have already 21 GB space for rollback segment. Is there any way to recover the used space from the RBS tablespace.
Rgds..

user537350 wrote:
Hi,
I have added 4 gb now. But is there any way to recover the space used by rollback tablespace.
Rgds...Shrink the rollback segment and then resize the rollback tablespace datafiles.
http://download-west.oracle.com/docs/cd/A87860_01/doc/server.817/a85397/statem16.htm#2052313

Unable to extend rollback segment 0

I'm migrating a 7.3.4 database to 8.0.5 using MIG80 and i get messages:
ora-01562 Unable to extend rollback segment 0
ora-01528 max # extents <121> reached for rollback segment system
My tablespace system's original size is 120M, now I have it grown to 400M, also have my rbs tablespace grown to 200M, I'm using MULTIPLIER=30, i've migrated 2 databases same sized but this time does'n work.
Can you help me?
I4m kind of hurry, i have to migrate 7 databases by august 25.
Thanks

Dear friend
Create rollback segment with large
in size.
sql> set transaction use rollback segment 'Name of the roll'
suresh
null

Oracle error: Ora-01555 : snapshot too old: rollback segment number 1......

System Error: Unknown Database error (type qqdb_ResourceException) on WMS_WH1: Execute failed for SQL statement ............... error from database is: ORA-01555: snapshot too old: rollback segment number 1 with name "_SYSSMU1$" too small...
Any ideas ? Please help.
Thank you.

You either have
- an UNDO tablespace that is way too small (rollback segments that are too small); or
- an application that does way too many COMMITs (common with apps ported from SQL Server)
From the added info, I would guess that the Java program has a major loop and does processing on each of the values it gets in that loop. At the end of each turn in the loop, it does a commit. Then it tries to look at the next record in the master list. After a while (say around 388 loops ;-) ) it dies.
The reason is that when it looks for information in the master query, it needs to rebuild that information to the moment that query was initiated. It uses rollback (AKA undo) to rebuild that. But rollback is not guaranteed to exist after a commit (unless forced) and once a commit happens, that area can be reused. When it is reused, the information is no longer there to rebuild the row, and that raises an ORA-01555
Edited by: Hans Forbrich on Sep 11, 2009 3:44 PM

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

Error while creating the rollback segment (Oracle 8i & OS Win NT)

hi
I am using Oracle 8i and when i am creating the new rollback segment for my database i have got following error message
ORA-01593 Rollback segment optimal size (30 blks) is smaller than the computed initial size (2560 blks)
CREATE ROLLBACK SEGMENT "RBS11" TABLESPACE "RBS1"
STORAGE ( INITIAL 120K NEXT
120K OPTIMAL
240K MINEXTENTS 2
MAXEXTENTS 100)
Note:- db_block size is 8k
Tablespace RBS1 is the Locally managed Tablespace having datafile of 50m and uniform size of 10m
But Given statement processed while i am using Tablespace RBS (winch is data dictionary managed)
Plz, suggest me to cause of that error and solution

You said 120K optimal and initial is 120K with minextents of 2. The optimal size then will be smaller than the initial allocation for the rbs.
ORA-01593: rollback segment optimal size (string blks) is smaller than the computed initial size (string blks)
Cause: Specified OPTIMAL size is smaller than the cumulative size of the initial extents during create rollback segment.
Action: Specify a larger OPTIMAL size.

Error rollback segment while exporting a table

I am getting error while exporting a table, can someone advise me how i can handle this issue.
EXP-00056: ORACLE error 1555 encountered
ORA-01555: snapshot too old: rollback segment number with name "" too small
ORA-22924: snapshot too old
Thanks

Hi, I have the same problem...
I have a table with a blob type (14740 records)
I have increase the PCTVERSION to 100 (= maximum)
undo_retention = 604800 (7 days)
undo tablespace = 2 Gb
exporting with parameter CONSISTENT=n
Still I got the message
EXP-00056: ORACLE error 1555 encountered
ORA-01555: snapshot too old: rollback segment number with name "" too small
ORA-22924: snapshot too old
When exporting the table
What do I have to do more ?????

ORA-01555: snapshot too old: rollback segment number 3 with name "_SYSSMU3$

A Materalized view is scheduled to update every 12 hours . When it has tried to update it has thrown the error ...
ORA-12008: error in materialized view refresh path
ORA-01555: snapshot too old: rollback segment number 3 with name "_SYSSMU3$"
too small
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 803
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 860
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 841
ORA-06512: at line 1

Hi,
Can you increase the size of the UNDO Tablespace ?
For more information, you can find on this link below:
http://forums.oracle.com/forums/search.jspa?threadID=&q=ORA-01555&objID=c84&dateRange=all&userID=&numResults=15
Cheers

ORA-01581: attempt to use rollback segment...

We've started getting "ORA-01581: attempt to use rollback segment (31) new extent (3) which is being allocated" messages in our production database over the last couple of days. Of course, each time we get these the rollback segment number is different, and we are getting these randomly from different applications that connect to the same database. We are using automatic undo management, so the rollback segments are not really under our control. The action in the Oracle docs for this error message doesn't give any specific actions that we should take, but we continue to get these.
We started to get these about the same time as we ran out of available sessions on the database (sessions = 1500 and we had 1500 open sessions). Could these be related? Could there be some open session that may be causing the rollback segment issue? Would a restart of the database fix this? Of course the max sessions issue was cleaned up two days ago but the rollback segment issue is a lingering problem.
Any help would be appreciated. We couldn't find anything for this online and Oracle hasn't responded to our service request yet.
Thanks,
Bobby

As I understand it, you can not explicitly set the size for the undo segments in automatic undo management mode. From the Concepts guide:
"In automatic undo management mode, the system controls exclusively the assignment of transactions to undo segments, and controls space allocation for undo segments."
It looks like we are also using the default storage options that are set when the UNDO tablespace was created. Here is the DDL used to create this tablespace:
CREATE SMALLFILE UNDO TABLESPACE "UNDOTBS" DATAFILE '/alpha/oradata/prod01/undotbs01.dbf' SIZE 750M REUSE AUTOEXTEND ON NEXT 25600K MAXSIZE 2000M , '/alpha/oradata/prod01/undotbs03.dbf' SIZE 2000M REUSE AUTOEXTEND ON NEXT 51200K MAXSIZE 2000M , '/alpha/oradata/prod01/undotbs04.dbf' SIZE 2000M REUSE AUTOEXTEND ON NEXT 104K MAXSIZE 2000M , '/alpha/oradata/prod01/undotbs02.dbf' SIZE 2000M REUSE AUTOEXTEND ON NEXT 25600K MAXSIZE 2000M

System Error:Database access error,rollback segment number with name "" too small

Hi Experts,
In SXMB_MONI XML messages for File2File scenario are failing
with the below message:
Database access error
com.sap.aii.utilxi.misc.api.ResourceException: ORA-01555: snapshot too
old: rollback segment number with name "" too small ORA-22924: snapshot
too old at com.sap.aii.utilxi.blob.api.AIIBlob.getByteArray
(AIIBlob.java:85) at
com.sap.aii.utilxi.blob.api.AIIBlobImpl.getByteArray
(BlobServices.java:156)
I have refered this link http://scn.sap.com/thread/3147106
Kindly suggest,
Gagan.

This may be due memory issue on the server. refer the note/thread as
http://scn.sap.com/thread/3456694
3807 - Error messages regarding rollback and undo segments
Regards
Ramg

Rollback segment error ORA-1628

Similar Messages

Maybe you are looking for