Links
Home
Oracle DBA Forum
Frequent Oracle Errors
TNS:could not resolve the connect identifier specified
Backtrace message unwound by exceptions
invalid identifier
PL/SQL compilation error
internal error
missing expression
table or view does not exist
end-of-file on communication channel
TNS:listener unknown in connect descriptor
insufficient privileges
PL/SQL: numeric or value error string
TNS:protocol adapter error
ORACLE not available
target host or object does not exist
invalid number
unable to allocate string bytes of shared memory
resource busy and acquire with NOWAIT specified
error occurred at recursive SQL level string
ORACLE initialization or shutdown in progress
archiver error. Connect internal only, until freed
snapshot too old
unable to extend temp segment by string in tablespace
Credential retrieval failed
missing or invalid option
invalid username/password; logon denied
unable to create INITIAL extent for segment
out of process memory when trying to allocate string bytes
shared memory realm does not exist
cannot insert NULL
TNS:unable to connect to destination
remote database not found'>ora-02019
exception encountered: core dump
inconsistent datatypes
no data found
TNS:operation timed out
PL/SQL: could not find program
existing state of packages has been discarded
maximum number of processes exceeded
error signaled in parallel query server
ORACLE instance terminated. Disconnection forced
TNS:packet writer failure
see ORA-12699
missing right parenthesis
name is already used by an existing object
cannot identify/lock data file
invalid file operation
quoted string not properly terminated
-none-

-none-

2005-01-07       - By -not available-

Reply:     <<     241     242     243     244     245     246     247     248     249     250     >>  

MAXEXTENTS
Default value
Derived from tablespace default storage or DB_BLOCK_SIZE initialization
parameter

Maximum
Unlimited

I was thinking that "Unlimited " actually corresponds to 2 billion. In any
case it is a lot and probably more than enough for most shops.

HTH -- Mark D Powell --


-- --Original Message-- --
From: oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected)]On Behalf Of Roger Xu
Sent: Friday, January 07, 2005 3:53 PM
To: Jonathan Lewis; Oracle-L@(protected) Org (E-mail)
Subject: RE: automatic extent allocation


So the suggestion would be to move it to its
own tablespace with uniform extent allocation?
What is Oracle 9i 's limit as far as the number
of extents in a table? Thanks.
-- --Original Message-- --
From: Jonathan Lewis [ mailto:jonathan@(protected)]
Sent: Friday, January 07, 2005 2:33 AM
To: Roger Xu; Oracle-L@(protected) Org (E-mail)
Subject: Re: automatic extent allocation




In the first place, I would consider moving the
object out of the current tablespace (or move
everything else out of the tablespace) because
it sounds like nothing else should be sharing that
tablespace. (Consider the problem of recovering
the entire tablespace because one of the other tables
gets a corrupt block - if you can 't take advantage
of rman block level recovery).

Secondly, at 3GB per month, I would consider
partitioning the table at something like one partition
per month - thus making your question moot.


It sounds like your object is still using 64MB
extents - it would be interesting to see if there
is another step size when you hit a total of 64GB,
or whether you keep going at 50 extents per month.

I suspect the problems you __might__ get from having
2,000 extents are much less significant than the problems
you __might__ get if you have a 100GB segment by the end
of next year.


Regards

Jonathan Lewis

http://www.jlcomp.demon.co.uk/faq/ind_faq.html
The Co-operative Oracle Users ' FAQ

http://www.jlcomp.demon.co.uk/seminar.html
Public Appearances - schedule updated Dec 23rd 2004
--
http://www.freelists.org/webpage/oracle-l