Re: table_space problem

In article <1993Mar20.195803.1352_at_hermes.dlogics.com> dlm_at_hermes.dlogics.com writes:
>In article <1993Mar19.211419.26420_at_netnews.whoi.edu>,
>dhiltz_at_whsun1.wh.whoi.edu (David Hiltz) writes:
>> In article <Mar18.173015.71143_at_yuma.ACNS.ColoState.EDU>
 ciuffoli_at_lamar.ColoState.EDU (Carlos Ciuffoli) writes:
>>>ERROR:
>>>ORA-01547: failed to allocate extent of size 956 in tablespace 'TEMPUSERS'
>>>
>> ERROR:
>> ORA-01547: failed to allocate extent of size 3596 in tablespace 'SYSTEM'
>
>First of all: <soap box> you should not place user data in the SYSTEM
>tablespace. it is only for the data dictionary tables. do not ask oracle to
>compete with users for space. </soap box>

 I don't. The data from the error messages above (the one referencing  SYSTEM) is in another tablespace, but the temporary tablespace is still in  SYSTEM which is what I think its complaining about. I plan to make a new  tablespace and assign that as the temporary tablespace. I think this will  solve my problem. Will let you know.

>Now then: default storage parameters have the above side-effect when tables
>are extended. oracle out-of-the-box defaults to 50% growth factor. that is,
>each new extent will be 150% of the latest extent size. if you add just one
>row to a table whose last extent is full, you may run out of space in the
>tablespace for the gigundo new extent (that's ORA-1547).

 This error resulted from a query not an insert or update.

[stuff deleted]
>another solution is to add more data files to the tablespace in question.
>and you do have separate tablespaces for SYSTEM, user data, indexes, and
>temporary tables, don't you?

 I have my users do all there work outside of SYSTEM (like I said above).  I don't know of any advantage for creating indexes in seperate tablespaces  from where other objects are created (such as a user's default tablespace).

    David Hiltz
    NMFS/NOAA, MA
    dhiltz_at_whsun1.wh.whoi.edu
    ######&_at_&###### Received on Mon Mar 22 1993 - 01:21:25 CET