Re: tablespace

A primary key constraint clause requires a unique index. If there was none on the column(s) before then the newly created index will be created in the default tablespace of the owner of the table. It will also use the default storage parameters assigned to that tablespace (or use server defaults) if none have been defined for the tablespace.

You should use more that one DBWR process if your system is very busy with UPDATES and INSERTS and the dynamic performance views indicate that DBWR-writing-to-disk is a bottleneck. You will only see a benefit of course if you actually have more than one disk, and the rest of the system is not the cause of DBWR to write too-slowly to disk (e.g. other processes on the system, disk contention from other programs writing to the disk etc).

David P.

Oracle Certified DBA.

\ \ wrote:
>
> Hi all,
>
> Could anyone tell me:
> 1) What happens if a tablespace clause is left off of a primary key
> constraint clause?
> 2) When should more than one DB writer process be used and how many should
> be used?
>
> TIA
> ART
  Received on Wed Apr 05 2000 - 00:00:00 CDT