Re: Lost Records

In article <CA20pq.M68_at_dcs.ed.ac.uk> pgk_at_dcs.ed.ac.uk (Paul Knights) writes:
>Hello
>
>Thanks everybody who mailed about the problem I had with trace files - all
>the timing data always appeared as zero after I TKPROF'd the trace files.
>The TIMED_STATISTICS parameter needs to be set to TRUE in INIT.ORA.
>
>My new problem hopefully has an equally simple solution. I've written
>several programs to insert test data into various test tables. The problem
>I'm getting is that there seems to be an upper limit to the number of records
>I can insert in any one table.
>
>For example, for the following table structure
>
> Name Null? Type
> ------------------------------- -------- ----
> A NUMBER(38)
> B NUMBER(38)
> DUMMY CHAR(200)
> DUMMY2 CHAR(200)
>
>I can only get 1956 records into it. All other INSERT commands have no effect.
>If I add extra fields the maximum number of records possible decreases.
>
>The problem occurs for all tables.
>
>I've tried issuing EXEC SQL COMMIT WORK after each INSERT but this had no
>effect.
>
>Any advice would be gratefully received.
>
>Thanks
>
>Paul

Check the default storage parameters for the tablespace you're creating the table in (I assume you're defaulting to those). You should be getting some sort of error code - are you loading with a C program or what? I would guess that you're probably filling up all the extents allowed by the storage parameters - maxextents would be the most relevant one and the easiest to change. (The error would be something like "unable to create extent in tablespace xxxxx, maxextents exceeded".)

        The other possibility would be that you're exceeding your resource quota on the tablespace in question.

				Ruth Larson
				rlarson_at_nswc-wo.nswc.navy.mil