Problems creating a partitioned primary key index.

I am creating a partitioned table and I noticed that when I use the constraint option of the create table the primary key is not partitioned. I then tried using the using index clause and specifying the create index local and that is giving errors. Here is my current syntax that is causing the errors:
create table redef_temp (
     USER_ID          VARCHAR2(32),
     GROUP_ID     VARCHAR2(32),
     JOIN_DATE     DATE DEFAULT SYSDATE NOT NULL,
     constraint primary key
     using index (create index pk_redef_temp
on redef_temp (USER_ID, GROUP_ID)
LOCAL STORE IN (IDX)))
tablespace data
partition by hash (user_id)
     (PARTITION ic_x_user_group_part_p1 tablespace DATA,
     PARTITION ic_x_user_group_part_p2 tablespace DATA,
     PARTITION ic_x_user_group_part_p3 tablespace DATA,
     PARTITION ic_x_user_group_part_p4 tablespace DATA)
PARALLEL ENABLE ROW MOVEMENT;
Thanks

The following works on 9.2.0.8 and 10.2.0.3:
create table redef_temp (
     USER_ID VARCHAR2(32),
     GROUP_ID VARCHAR2(32),
     JOIN_DATE DATE DEFAULT SYSDATE NOT NULL,
     constraint pk_redef_temp primary key (user_id, group_id)
     using index (
          create index pk_redef_temp
          on redef_temp (USER_ID, GROUP_ID)
          LOCAL tablespace test_8k
tablespace test_8k
partition by hash (user_id) (
     PARTITION ic_x_user_group_part_p1 tablespace test_8k,
     PARTITION ic_x_user_group_part_p2 tablespace test_8k,
     PARTITION ic_x_user_group_part_p3 tablespace test_8k,
     PARTITION ic_x_user_group_part_p4 tablespace test_8k
PARALLEL ENABLE ROW MOVEMENT
/Your syntax for the constraint definition was wrong, and your use of 'store in' for the index tablespace was wrong. I've had to change all tablespace names to 'test_8k'.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk

Similar Messages

Problem CREATE TABLE with PRIMARY KEY Still in Trouble ! Please Help!

Hi there !
I use the orcle 8i, and i don't know why i can't create table with any primary key EXample:
SQL> CREATE TABLE O_caisses
2 (No_caisse NUMBER(3) constraint caisses_pk PRIMARY KEY,
3 NB_BILLETS NUMBER(5)
4 )
5 /
CREATE TABLE O_caisses
ERROR at line 1:
ORA-18008: cannot find OUTLN schema
***********some Debuger show me this way: *********************
Well there r certain point u got to notice when creating a table with constraints.
1) U can create table with COLUMN level constraint.
2) U can create table with TABLE level constraint.
3) In COLUMN level constraint u can't give a constraint a name
but only mention the type of constraint.
4) In TABLE level constraint u can give a name to constraint.
Following are the examples of both
--COLUMN LEVEL
CREATE TABLE O_caisses
(No_caisse NUMBER(3) PRIMARY KEY,
NB_BILLETS NUMBER(5));
--TABLE LEVEL
CREATE TABLE O_caisses
(No_caisse NUMBER(3),
NB_BILLETS NUMBER(5),
constraint pk_caisse primary key (No_caisse));
********************And this is another one:*****************
SQL>grant create any outline to username;
BUT the problem is still present, i don't know what to do now !
Please could some body help me !
Thanks alot!
Luong.

The clue is in the error message: the OUTLN schema is missing.
This is something Oracle 8i introduced to help manage the CBO (or soemthing equally geeky and internal). For some reason your database no longer has this user. It ought to be created automatically during installation (or upgrade) but catproct may not have completed probably or some over zealous admin type has dropped it.
Solution is to re-install (or re-upgrade) as you cannot create this user on their own. Alas.
HTH, APC

Creating Primary Key Index

Hi,
Iam trying to create a Primary Index on Large table and Iam using the Parallelism to make it fast. I have used the following script to create a Primary key Index.
CREATE UNIQUE INDEX FLX_ARCH.FUND_SEC_RESULT_STAT_ARCH_PK
ON FLX_ARCH.FUND_SEC_RESULT_STAT_ARCH
(FUND_SEC_RESULT_MAP_INST,RATES_RULE_ID,BASE_LOCAL_FLAG,EFFECTIVE_DATE)
TABLESPACE FLX_PERF_I
parallel;
Index created.
Elapsed: 01:43:37.37
Index got created in 1 hour 43 minutes. But when Iam adding constarint to those columns, it is taking almost 12hours with or without parallelism.
ALTER TABLE FLX_ARCH.FUND_SEC_RESULT_STAT_ARCH
ADD CONSTRAINT FUND_SEC_RESULT_STAT_ARCH_PK
PRIMARY KEY
(FUND_SEC_RESULT_MAP_INST,RATES_RULE_ID,BASE_LOCAL_FLAG,EFFECTIVE_DATE)
parallel
Would you please let me know what could be the problem and how can we add the Primary constraint fast.
Your early response is much appreciated.
Thanks and Regards
Suresh. D

Would you please let me know what could be the problem and You have presented no details that indicate any problem exists.
how can we add the Primary constraint fast. Fast is relative.
If I asked you to make my snail fast, could you do so?
ALTER SESSION SET SQL_TRACE=TRUE;
ALTER TABLE FLX_ARCH.FUND_SEC_RESULT_STAT_ARCH
ADD CONSTRAINT FUND_SEC_RESULT_STAT_ARCH_PK
PRIMARY KEY
(FUND_SEC_RESULT_MAP_INST,RATES_RULE_ID,BASE_LOCAL_FLAG,EFFECTIVE_DATE)
parallel
ALTER SESSION SET SQL_TRACE=FALSE;
now find the trace file within ./udump folder
tkprof <trace_file.trc> trace_results.txt explain=<username>/<password>
By inspecting the trace file you will be able to see where time is being spent.
With this knowledge, you may or may not be able to determine the bottleneck & therefore improve it

Creating an unique index instaed of using primary key index

Hi ,
I heard in a debate sometimes it's better to create a unique index on a column and using it instaed of using primary key index in oracle.I couldn't understand what the reason propely.
Can anyone please help me in thsi topic if it is a valid one .
Thanks in advance

Hi,
They are exactly NOT identical.
1. Unique key can have NULL values where primary keys can't.
2. Primary key is fundamentally those keys which do not change. I mean updating a primary key is not a good idea.
SQL> drop table test;
Table dropped.
SQL> create table test ( a number(2));
Table created.
SQL> ed
Wrote file afiedt.buf
1* create unique index test_idx on test(a)
SQL> /
Index created.
SQL> ed
Wrote file afiedt.buf
1* insert into test values(NULL)
SQL> /
1 row created.
SQL> drop table test;
Table dropped.
SQL>
SQL> create table test ( a number(2) primary key);
Table created.
SQL> insert into test values(NULL);
insert into test values(NULL)
ERROR at line 1:
ORA-01400: cannot insert NULL into ("HR"."TEST"."A")
SQL>Cheers,
Edited by: Avinash Tripathi on Nov 24, 2009 11:17 AM

Problem with capturing Primary Key Index

Hi
I am capturing certain tables and in the mean process i observed that all the indexes are getting captured except the primary key index.
Any Suggestions on this?
Thanx,
Suji

Hi,
I was unable to reproduce this behavior on OWM 10.1.0.8. It appears that you have a SR open for this issue, so I would suggest to continue with that process.
Regards,
Ben

Concept about Primary Key index

I have a partitioned table as follow:
CREATE TABLE TEST
(TEST_KEY NUMBER(10,0) NOT NULL
,FOREIGN_KEY NUMBER(10,0) NOT NULL
,PARAM_ID NUMBER(10,0)
,PARAM_VALUE VARCHAR2(256)
PARTITION BY HASH (operation_key) PARTITIONS 15
STORE IN (TEST_R1_TS, TEST_R2_TS, TEST_R3_TS, TEST_R4_TS, TEST_R5_TS)
CACHE
I also created a partitioned index for the TEST_KEY to be used as primary key index.
CREATE INDEX TEST_PK_IDX ON PARAMETER_1(TEST_KEY) LOCAL
STORE IN (TEST_i1_ts, TEST_i2_ts, TEST_i3_ts, TEST_i4_ts, TEST_i5_ts);
When I try to run alter table to add primary key, I got index not exist error?
SQL> alter table TEST add (constraint test_pk primary key (test_key) using index test_pk_idx);
alter table parameter_1 add (constraint pa1_pk primary key (parameter_key) using index pa_pk_idx)
ERROR at line 1:
ORA-01418: specified index does not exist
BUT, I could find my index in the USER_INDEXES table...
SQL> select index_name from user_indexes where index_name like '%TEST_PK%';
INDEX_NAME
TEST_PK_IDX
Why? Help is very appreciated.
Thank you in advanced.

check the names of the tables in the script you give ... they are different for the table and the index. When you add the constraint the table name and column name mysteriously change in the error message, so I think that you aren't showing us what actually happened.

Primary key index not working in a select statment

Hi ,
I'm doing a :
select *
from my_table
where B = v1 and
A = v2 ;
where A and B are the primary key of the table, in that table the primary key index is there and the order of the primary key definition is A first and then B.
While testing this statment in my database the Explain Plan shows that it is using the index ok but when
runninng in client database it is not using it becasue of the order (i think), is this something configurable that I need to ask to my DBA ?
The solution I found was to do the select with a hint wich fix the problem , but I'm curious about why is working in my dadabase and not in the client database
thanks in advance .
oracle version 11g

This is the forum for SQL Developer (Not for general SQL/PLSQL questions). Your question would be better asked in the SQL and PL/SQL forum.
Short answer: The execution plan used will depend on optimizer settings and table/index statistics. For example if the table has very few rows it may not bother using the index.

SOS: javax.ejb.CreateException: Create failed because primary key is null

Hello,
I am desperately trying to get my application server to create a record through CMP 2. My app server is JRun 4.
Here is the client:
package com.parispano.tests;
import java.util.Date;
import java.util.Properties;
import javax.naming.Context;
import javax.naming.InitialContext;
import com.parispano.account.entity.Account;
import com.parispano.account.entity.AccountHome;
public class ClientEJBDeuxTemp {
public static void main(String[] args) {
    System.out.println("\nBegin account DemoClient...\n");
    try {
      // Create A Demo object, in the server
      // Note: the name of the class corresponds to the JNDI
      // property declared in the DeploymentDescriptor
      // From DeploymentDescriptor ...
      // beanHomeName demo.DemoHome
      Context ctx = getInitialContext();
      AccountHome ahome = (AccountHome) ctx.lookup("AccountEJBHome");
      //System.out.println("Creating Demo\n");
      Account account = ahome.create("toto","toto", "toto","toto","toto","toto","toto","toto","toto","toto","toto",new Date(),new Date());
    catch (Exception e) {
      System.out.println(":::::::::::::: Error :::::::::::::::::");
      e.printStackTrace();
    System.out.println("\nEnd DemoClient...\n");
static String user     = "admin";
static String password = "admin";
static String url      = "ordi:2908";
   * Gets an initial context.
   * @return                  Context
   * @exception               java.lang.Exception if there is
   *                          an error in getting a Context
static public Context getInitialContext() throws Exception {
    Properties p = new Properties();
    p.put(Context.INITIAL_CONTEXT_FACTORY, "jrun.naming.JRunContextFactory");
    p.put(Context.PROVIDER_URL, url);
    if (user != null) {
      System.out.println ("user: " + user);
      p.put(Context.SECURITY_PRINCIPAL, user);
      if (password == null)
        password = "";
      p.put(Context.SECURITY_CREDENTIALS, password);
    return new InitialContext(p);
}and here is the exception I get:
javax.ejb.CreateException: Create failed because primary key is null
I don't understand why I get this as the primary key is "toto" and therefore is not null.
Here is the DD:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
    <display-name>Account EJB</display-name>
    <enterprise-beans>
      <entity>
        <display-name>Account EJB</display-name>
        <ejb-name>AccountEJB</ejb-name>
        <home>com.parispano.account.entity.AccountHome</home>
          <remote>com.parispano.account.entity.Account</remote>
        <local-home>com.parispano.account.entity.AccountLocalHome</local-home>
        <local>com.parispano.account.entity.AccountLocal</local>
        <ejb-class>com.parispano.account.entity.AccountEJB</ejb-class>
        <persistence-type>Container</persistence-type>
        <prim-key-class>java.lang.String</prim-key-class>
        <reentrant>False</reentrant>
        <cmp-version>2.x</cmp-version>
        <abstract-schema-name>account</abstract-schema-name>
        <cmp-field>
        <description>Login</description>
        <field-name>login</field-name>
        </cmp-field>
        
        <cmp-field>
          <description>Password</description>
          <field-name>password</field-name>
        </cmp-field>
        <cmp-field>
          <description>Surname</description>
          <field-name>surname</field-name>
        </cmp-field>
        <cmp-field>
          <description>First Name</description>
          <field-name>firstName</field-name>
        </cmp-field>
        <cmp-field>
          <description>Address One</description>
          <field-name>addressOne</field-name>
        </cmp-field>
        <cmp-field>
          <description>Address Two</description>
          <field-name>addressTwo</field-name>
        </cmp-field>
        <cmp-field>
          <description>Postcode</description>
          <field-name>postcode</field-name>
        </cmp-field>
        <cmp-field>
          <description>City</description>
          <field-name>city</field-name>
        </cmp-field>
        <cmp-field>
          <description>Country</description>
          <field-name>country</field-name>
        </cmp-field>
        <cmp-field>
          <description>Telephone</description>
          <field-name>telephone</field-name>
        </cmp-field>
        <cmp-field>
          <description>Email</description>
          <field-name>email</field-name>
        </cmp-field>
        <cmp-field>
          <description>Inscription Date</description>
          <field-name>inscriptionDate</field-name>
        </cmp-field>
        <cmp-field>
          <description>Last Visit Date</description>
          <field-name>lastVisitDate</field-name>
        </cmp-field>
          <primkey-field>login</primkey-field>
      </entity>
    </enterprise-beans>
</ejb-jar>Can anyone tell me why I am getting this exception please?
Thanks in advance,
Julien Martin.

Yes, I have set the PK. Actually this is happening when the number of columns are more than 63 columns. After I reduce the number of column, it is working fine.
Is it the actual problem???
fyi, I'm using jboss as the Application Server...

Problem in generating the Primary Key

Hi All ,
I am trying to persist an object and also generating the primary key using a default sequence . But the problem is that the Primary key is getting incremented by 2 instead of 1 . My code looks like this :
import java.util.HashMap;
import javax.persistence.EntityManager;
import javax.persistence.EntityManagerFactory;
import javax.persistence.EntityTransaction;
import javax.persistence.Persistence;
import javax.persistence.PersistenceContext;
import javax.persistence.PersistenceContextType;
import javax.persistence.PersistenceUnit;
public class entityCaller {
//     @PersistenceContext(unitName="testApp" ,type=PersistenceContextType.EXTENDED)
     EntityManager em;
//     @PersistenceUnit(unitName="testApp")
     EntityManagerFactory emf ;
     public void persistEntity( String Name , int Age ) {
          EntityManagerFactory emf =
          Persistence.createEntityManagerFactory("testApp", new HashMap());
          em = emf.createEntityManager();
          EntityTransaction entityTransaction = em.getTransaction();
     Tab1 oBJTab1 = new Tab1();
//      oBJTab1.setId(Age);
     oBJTab1.setVal(Name);
          try{
               System.out.println("Making object");
               em.persist(oBJTab1);
               System.out.println("Done");
               System.out.println("Making object2");
               System.out.println("Entered the Values");
          }catch (Exception e) {
               e.printStackTrace();
          }finally{
          em.close();
     public static void main(String[] args) {
          entityCaller caller = new entityCaller();
          caller.persistEntity("DoAgain7",2);
My persistence.xml looks like this :
<?xml version="1.0" encoding="UTF-8"?>
<persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.0" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
<persistence-unit name="testApp">
<provider>oracle.toplink.essentials.ejb.cmp3.EntityManagerFactoryProvider</provider>
<class>Tab1</class>

<properties>

<property name="toplink.jdbc.driver" value="oracle.jdbc.driver.OracleDriver"/>
<property name="toplink.jdbc.url" value="jdbc:oracle:thin:@127.0.0.1:1521:XE"/>
<property name="toplink.jdbc.user" value="system"/>
<property name="toplink.jdbc.password" value="jlkklkj"/>


</properties>
</persistence-unit>
</persistence>
Please provide me with some pointer as to know where the things are going wrong.

If you generated your original schema using toplink.ddl-generation, then later dropped it and created it then you should keep in mind the sequence table does not get dropped. This can lead to an initially 'empty' database with a PK sequence starting at '2' if you have one persistence unit and one entity. Can you steadily duplicate this or did you just notice that your persist started with an key of '2'? Just a thought.

How to see wether the index is a primary key index or not

hi,
can anybody let me know how to get wether the index is made on the primary key (i.e primary key index)
can we do by querying the user_constriants table.
plz let me know..

Maran.Viswarayar wrote:
Vijay,
Was that different from Anurag's reply?Yes it was. Anurag didn't include the index_name in his query.
It is possible for the index name to be different from the constraint_name, so if you listed just the primary key constraint names you might decide that a given index was not a "primary key" index because you couldn't find a constraint with the matching name.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk
To post code, statspack/AWR report, execution plans or trace files, start and end the section with the tag {noformat}{noformat} (lowercase, curly brackets, no spaces) so that the text appears in fixed format.
"Science is more than a body of knowledge; it is a way of thinking"
Carl Sagan

Drop/recreate primary key index

Any suggestions for dropping/recreating a primary key index? The index has to be dropped/recreated and not rebuilt due to ORA-600s.
Do I simply disable/re-enable the primary key constraint? The database is 10g.
Edited by: nickw2 on Apr 1, 2009 5:06 PM

ORA-600 errors are a handful, I usually check metalink or ask ORacle support for help.
Anyways, If you want to recreate the primary key index, have you tried dropping the primary key constraint and adding it back?
ALTER TABLE tablename
DROP CONSTRAINT pk_name;
ALTER TABLE tablenames
ADD CONSTRAINT pk_name PRIMARY KEY (column_name);

Creating Primary key Index as Local Partitioned Index.

CREATE TABLE T1(
x NUMBER,
y NUMBER
)PARTITION BY LIST(x)
PARTITION P1 VALUES (1),
PARTITION P2 VALUES (2),
PARTITION Pmax VALUES (default)
ALTER TABLE T1 ADD CONSTRAINT T1_PK PRIMARY KEY(Y) LOCAL;
Error starting at line 1 in command:
ALTER TABLE T1 ADD CONSTRAINT T1_PK PRIMARY KEY(Y) LOCAL
Error report:
SQL Error: ORA-01735: invalid ALTER TABLE option
01735. 00000 - "invalid ALTER TABLE option"
*Cause:
*Action:
Can you please help me how to achieve this in Oracle 10g R2?

LOCAL keyword is invalid with ALTER TABLEDepends:
SQL> create table t1 (x number, y number)
partition by list (x)
   (partition p1
       values (1),
    partition p2
       values (2),
    partition pmax
       values (default))
Table created.
SQL> alter table t1 add constraint t1_pk primary key(x, y) using index local
Table altered.

Having a problem with creating/using a primary key on a view

I have a problem with a primary key on a view
I created the view and primary key as follows:
CREATE OR REPLACE FORCE VIEW "MDD"."ROCK_LU" ("DESCRIPTION",
UNIQUE ("DESCRIPTION") RELY DISABLE,
CONSTRAINT "ROCK_LU_PK" PRIMARY KEY ("DESCRIPTION") RELY DISABLE) AS
SELECT DESCRIPTION
FROM MRMC_LU
WHERE ROCK = 'T';
The view with the primary key appears to have been created as there were no error messages. (The above was from the sql tab in sql developer.)
When I try to create the foreign key on my mdd_hr table - I get an error
/* hr_name - foreign key */
ALTER TABLE mdd_hr add CONSTRAINT hr_name_fk FOREIGN KEY (hr_name) REFERENCES rock_lu(description);
Error report:
SQL Error: ORA-02270: no matching unique or primary key for this column-list.
When I lookup the index in sql developer, rock_lu_pk is not there.
All my other foreign keys work - but I don't understand what I am doing wrong with this one. Please help.
glenn
Background - as to why I want to use a view as a lookup table.
The MRMC_LU table that the view is created from is structured like:
DESCRIPTION - MINERAL - ROCK - MODIFIER - COMMODITY
ANHYDRITE - T - T - T
APLITE - T - - T
GRAPHITE - T - - - T
GREYWACKE - - T
DESCRIPTION is a list of all names of minerals, rocks, modifiers and commodities. T is entered in each valid field. Often a description name is used for both a mineral and a rock or a mineral and a commodity or any other combination. Because this database is just starting up, it was more efficient to create one table that could be updated (and thereby automatically update the MINERAL_LU, ROCK_LU, MODIFIER_LY, COMMODITY_LU views) rather than create and maintain four separate but similar tables. A primary key cannot be generated for the MRMC_LU table as there are nulls in each column
except DESCRIPTION.
Perhaps there is a smarter way to do this?

http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96540/statements_85a.htm#2065512
You can specify constraints on views and object views. You define the constraint at the view level using the out_of_line_constraint clause. You define the constraint as part of column or attribute specification using the inline_constraint clause after the appropriate alias.
Oracle does not enforce view constraints. However, operations on views are subject to the integrity constraints defined on the underlying base tables. This means that you can enforce constraints on views through constraints on base tables.
Restrictions on View Constraints
View constraints are a subset of table constraints and are subject to the following restrictions:
You can specify only unique, primary key, and foreign key constraints on views. However, you can define the view using the WITH CHECK OPTION clause, which is equivalent to specifying a check constraint for the view.
Because view constraints are not enforced directly, you cannot specify INITIALLY DEFERRED or DEFERRABLE.
View constraints are supported only in DISABLE NOVALIDATE mode. You must specify the keywords DISABLE NOVALIDATE when you declare the view constraint, and you cannot specify any other mode.
You cannot specify the using_index_clause, the exceptions_clause clause, or the ON DELETE clause of the references_clause.
You cannot define view constraints on attributes of an object column.
Rgds.

How to Create primary key index with duplicate rows.

Hi All,
While rebuilding an index on a table , I am getting error that there are duplicate rows in a table.
Searching out the reason led me to an interesting observation.
Please follow.
SELECT * FROM user_ind_columns WHERE table_name='SERVICE_STATUS';
INDEX_NAME     TABLE_NAME     COLUMN_NAME     COLUMN_POSITION     COLUMN_LENGTH     CHAR_LENGTH     DESCEND
SERVICE_STATUS_PK     SERVICE_STATUS     SUBSCR_NO_RESETS     2     22     0      ASC
SERVICE_STATUS_PK     SERVICE_STATUS     STATUS_TYPE_ID     3     22     0     ASC
SERVICE_STATUS_PK     SERVICE_STATUS     ACTIVE_DT     4     7     0     ASC
SERVICE_STATUS_PK     SERVICE_STATUS     SUBSCR_NO     1     22     0     ASC
SELECT index_name,index_type,table_name,table_type,uniqueness, status,partitioned FROM user_indexes WHERE index_name='SERVICE_STATUS_PK';
INDEX_NAME     INDEX_TYPE      TABLE_NAME     TABLE_TYPE     UNIQUENESS     STATUS     PARTITIONED
SERVICE_STATUS_PK     NORMAL     SERVICE_STATUS     TABLE     UNIQUE     VALID     NO
SELECT constraint_name ,constraint_type,table_name,status,DEFERRABLE,DEFERRED,validated,index_name
FROM user_constraints WHERE constraint_name='SERVICE_STATUS_PK';
CONSTRAINT_NAME     CONSTRAINT_TYPE     TABLE_NAME      STATUS     DEFERRABLE     DEFERRED     VALIDATED     INDEX_NAME
SERVICE_STATUS_PK     P     SERVICE_STATUS     ENABLED     NOT DEFERRABLE     IMMEDIATE VALIDATED     SERVICE_STATUS_PK
1. Using index scan:
SELECT COUNT (*)
FROM (SELECT subscr_no, active_dt, status_type_id, subscr_no_resets
FROM service_status
GROUP BY subscr_no, active_dt, status_type_id, subscr_no_resets
HAVING COUNT (*) > 1) ;
no rows returned
Explain plan:
Operation     OBJECT Name     ROWS     Bytes     Cost     OBJECT Node     IN/OUT     PStart     PStop
SELECT STATEMENT Optimizer MODE=CHOOSE          519 K          14756
FILTER
SORT GROUP BY NOSORT          519 K     7 M     14756
INDEX FULL SCAN     ARBOR.SERVICE_STATUS_PK     10 M     158 M     49184
2. Using Full scan:
SELECT COUNT (*)
FROM (SELECT /*+ full(s) */ subscr_no, active_dt, status_type_id, subscr_no_resets
FROM service_status s
GROUP BY subscr_no, active_dt, status_type_id, subscr_no_resets
HAVING COUNT (*) > 1) ;
71054 rows returned.
Explain Plan:
Operation     Object Name     Rows     Bytes     Cost     Object Node     In/Out     PStart     PStop
SELECT STATEMENT Optimizer Mode=CHOOSE          1           24123
SORT AGGREGATE          1
VIEW          519 K          24123
FILTER
SORT GROUP BY          519 K     7 M     24123
TABLE ACCESS FULL     ARBOR.SERVICE_STATUS     10 M     158 M     4234
Index SERVICE_STATUS_PK is a unique and composite primary key VALID index. And the constraint is ENABLED and VALIDATED still having duplicate rows in table.
How it is possible?
Is it an Oracle soft Bug??
Regards,
Saket Bansal

saket bansal wrote:
Values are inserted as single rows inserts through an GUI interface.And you still claim to have over 71K duplicate records, without the GUI getting any kind of errors?
That does not add up and can only be explained by a "bug".
I tried inserting a duplicate record but failed.
SQL> insert into service_status (select * from service_status where rownum <2);
insert into service_status (select * from service_status where rownum <2)
ERROR at line 1:
ORA-00001: unique constraint (ARBOR.SERVICE_STATUS_PK) violatedAre you really sure there is no other way data in this table is populated/manipulated in bulk?

The primary key index to be created in a different tablespace.

Hi,
I have a user PROD. It has been assigned a default tablespace PROD_TBS.
There is a seperate table space for all the indexes in the schema , PROD_IDX.
I wish to create a table TEST as follows,
CREATE TABLE TEST
(TEST_ID NUMBER(1),
NAME VARCHAR2 (10) );
There should be a primary key on column test_id but such that the corresponding unique index created by default because of the primary key should be created in tablespace PROD_IDX.
How to do this ?

Alternative solution:
CREATE TABLE TEST
(TEST_ID NUMBER(1),
NAME VARCHAR2 (10),
constraint test_pk primary key (test_id)
using index tablespace prod_idx
);Cheers, APC
blog: http://radiofreetooting.blogspot.com

Problems creating a partitioned primary key index.

Similar Messages

Maybe you are looking for