OraFAQ Forum: Server Administration

Home » RDBMS Server » Server Administration » ora-01681

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

ora-01681 [message #214038]

Sat, 13 January 2007 20:20

fnguy
Messages: 39
Registered: January 2006

Member

This error in the event log. Oracle 7.3.4.5.0 on aix. Can someone tell me what I need to do. I've googled it and one response was to drop the rollback segment and recreate. I just want to verify first.

Thanks.

ALTER ROLLBACK SEGMENT "R02" STORAGE ( MAXEXTENTS 560)
Tue Jan 9 16:32:05 2007
ORA-1681 signalled during: ALTER ROLLBACK SEGMENT "R02" STORAGE ( MAXEXTENTS ...
Tue Jan 9 16:34:07 2007

Report message to a moderator

Re: ora-01681 [message #214039 is a reply to message #214038]

Sat, 13 January 2007 20:32

BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal

Senior Member

01681, 00000, "max # extents (%s) reached in LOB segment in tablespace %s"
// *Cause: A LOB segment tried to extend past max extents.
// *Action: If maxextents for the tablespace is less than the the system
// maximum, you can raise that. Otherwise, raise pctincrease for the
// tablespace

I have NO idea where/why RBS would be part of the solution or elimination of the error.

EXACTLY what SQL resulted in the error generation?

Report message to a moderator

Re: ora-01681 [message #214040 is a reply to message #214039]

Sat, 13 January 2007 20:56

fnguy
Messages: 39
Registered: January 2006

Member

Customer tells me they were following this procedure. I found the error I posted in the alert log:

1. From the START menu, select PROGRAMS….ORACLE ENTERPRISE…..DBA MANAGEMENT PACK…..STORAGE MANAGER
2. Logon as sys….password….production
3. Open the branch for TABLESPACES
4. Open the branch for RBS
5. Open the branch for ROLLBACK SEGMENTS
6. Highlight the segment R02
7. On the right pane, select the STORAGE tab
8. Increase the value in the field MAXIMUM VALUE by 10% of the existing value.
9. Click the APPLY button
10. Exit the program

Report message to a moderator

Re: ora-01681 [message #214042 is a reply to message #214038]

Sat, 13 January 2007 21:42

BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal

Senior Member

Back in ancient times (Pre-V8 or so), Oracle was limited to certain number of extents based upon block size being used.
I suspect that this instance has just smacked into the limit.
I suspect that your options are either limited or VERY painful to execute; such as rebuilding DB with a larger blocksize.
IMO, the REAL solution is to upgrade/migrate to a supported version
Until you do, You're On Your Own.

Report message to a moderator

Re: ora-01681 [message #214064 is a reply to message #214042]

Sun, 14 January 2007 09:51

fnguy
Messages: 39
Registered: January 2006

Member

Ouch. The term "No longer supported" doesn't seem to fit this customers understanding of software. Well, maybe I should say in the past they didn't seem to understand. Perhaps they will now.

Report message to a moderator

Re: ora-01681 [message #214287 is a reply to message #214064]

Mon, 15 January 2007 12:39

joy_division
Messages: 4963
Registered: February 2005
Location: East Coast USA

Senior Member

I think v7 was desupported in 1999.

Report message to a moderator

Previous Topic:	REDO LOG status
Next Topic:	Oracle Express Server 6.3.0 hang

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Feb 22 15:35:41 CST 2025