Re: extents allocation in parallel load

2002-05-15 Thread Gurelei
Tim, The tablespace is dictionary managed. --- Tim Gorman [EMAIL PROTECTED] wrote: I was hoping to see * column values from DBA_TABLESPACES, not just the default storage column values. This would show whether the tablespace in question was locally-managed (and SYSTEM or UNIFORM, if so) as

Re: extents allocation in parallel load

2002-05-15 Thread Tim Gorman
Well! I'm out of ideas. The only other thing I can think of is a recent ALTER TABLE which changed the INITIAL on the table since the load, but that's grasping (gasping?). Still, could you look at LAST_DDL_TIME on DBA_OBJECTS for the table, just to grasp that last straw? - Original Message

Re: extents allocation in parallel load

2002-05-15 Thread Gurelei
Tim, Thanks for all your help. I will check the LAST_DDL_TIME field (although I didn't know what INITIAL parameter can be modified) and will let you know if something comes out of it. Gene --- Tim Gorman [EMAIL PROTECTED] wrote: Well! I'm out of ideas. The only other thing I can think of is

extents allocation in parallel load

2002-05-14 Thread Gurelei
Hi, I'm confused by the way some of my extents are allocated in Oracle. I've talked to Oracle reps, I thing I've posted here before and jsut when I thought I got an understanring - ooops, everything is gone. So I'll give it another try. I have a table with initial set to 32K and next set to 1M.

Re: extents allocation in parallel load

2002-05-14 Thread Tim Gorman
SQL*Loader in direct-parallel mode (i.e. DIRECT=TRUE, PARALLEL=TRUE) first loads into a TEMPORARY segment. After the load completes, then the TEMPORARY segment is merged with the table segment. All of the direct (a.k.a. append) operations work this way when executed in parallel (i.e. INSERT /*+

Re: extents allocation in parallel load

2002-05-14 Thread Gurelei
Tim, Thanks for the explanation. The table I'm looking at has an initial size 32K while the new extents are all 16K. Why would this happen? thanks Gene --- Tim Gorman [EMAIL PROTECTED] wrote: SQL*Loader in direct-parallel mode (i.e. DIRECT=TRUE, PARALLEL=TRUE) first loads into a TEMPORARY

Re: extents allocation in parallel load

2002-05-14 Thread Tim Gorman
What does SELECT * FROM DBA_TABLESPACES show for the tablespace involved? - Original Message - To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] Sent: Tuesday, May 14, 2002 12:53 PM Tim, Thanks for the explanation. The table I'm looking at has an initial size 32K while

Re: extents allocation in parallel load

2002-05-14 Thread Gurelei
Tim, SQL select TABLESPACE_NAME, INITIAL_EXTENT/1024, NEXT_EXTENT/1024, PCT_INCREASE 2 from dba_tablespaces 3 where tablespace_name like 'TEMP%' 4 or tablespace_name = 'TREPD01'; TABLESPACE_NAMEINITIAL_EXTENT/1024 NEXT_EXTENT/1024 PCT_INCREASE

Re: extents allocation in parallel load

2002-05-14 Thread Tim Gorman
I was hoping to see * column values from DBA_TABLESPACES, not just the default storage column values. This would show whether the tablespace in question was locally-managed (and SYSTEM or UNIFORM, if so) as well... You don't need to include the temporary tablespace -- it's not relevant.