Re: Cannon create table with Primary Key in tablespace

From: Jonathan Gennick <jonathan_at_gennick.com>
Date: 2000/04/14
Message-ID: <3912a7b4.25355148@netnews.worldnet.att.net>#1/1

How much space do you have left in DEV_DATA? Is that your default tablespace? In your commands below, you do not specifically assign either the table or the index to a tablespace, so both would be created in your default tablespace. It's possible that after the initial extent is allocated for the table that you no longer have any room for the index needed to enforce the primary key. This is the first thing that comes to mind as a possible reason for what you are experiencing.

Jonathan

---

jonathan_at_gennick.com
http://gennick.com
Brighten the Corner Where You Are

On Thu, 13 Apr 2000 18:26:37 -0700, "Joe Seefeldt" <joezaloom_at_hotmail.com> wrote:

>Am I stupid? Probably.
>
>I create a simple table, with a PK:
>
>create table categories (
> category_id int PRIMARY KEY,
> cat_name varchar2(40),
> cat_desc varchar2(64)
>)
>
>or
>
>create table categories (
> category_id int ,
> cat_name varchar2(40),
> cat_desc varchar2(64),
> PRIMARY KEY (category_id)
>)
>
>and I get the error message: ORA-01658: unable to create INITIAL extent for
>segment in tablespace DEV_DATA
>
>I remove the reference to PK, i.e:
>
>create table categories (
> category_id int ,
> cat_name varchar2(40),
> cat_desc varchar2(64)
>)
>
>and it is successful. What am I missing?
>
>thanks,
>js
>
Received on Fri Apr 14 2000 - 00:00:00 CDT