Bad Partition
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 7 of 7

Thread: Bad Partition

  1. #1
    Join Date
    Jan 2001
    Posts
    515

    Question Bad Partition

    We have a partitioned table. I added a data partition to the table under the wrong owner. the problem is that when I created the data parition it also created a index partition under the table owner. So when I go to drop the data parition it says that I can't because the index partition is owned by someone else. How do I solve this problem? I checked Metalink but did not find anything.

  2. #2
    Join Date
    Mar 2002
    Posts
    534
    hi,

    just wondering: how did you create a new partiton for a existing partitioned table under a wrong owner?

  3. #3
    Join Date
    May 2001
    Posts
    73
    Login as sys or system and drop the partition.
    OCP 7.3,8.0,8i,9i

  4. #4
    Join Date
    Feb 2000
    Location
    Washington DC
    Posts
    1,843
    Originally posted by rad_jen
    Login as sys or system and drop the partition.
    Do this as last resort , after Backing up table. Who owns the table ? It doesn't make sense to me table/partition owner and table/partition index owner is different.
    how did you create this partition with index under different ownership ?
    Reddy,Sam

  5. #5
    Join Date
    Jul 2003
    Posts
    323

    ownership

    Was searching this thread for a problem I face and picking up on this thread - we've got a production env. with a partitioned table which shows 2 owners for a range partitioned table in the DBA_TAB_PARTITIONS view - one is the schema owner and the other a user created with DBA privileges.

    Can any1 throw some light on how this can happen ?


    Regards,

    Last edited by cruser3; 05-16-2006 at 06:22 PM. Reason: change data

  6. #6
    Join Date
    Sep 2002
    Location
    England
    Posts
    7,333
    example?

  7. #7
    Join Date
    Jul 2003
    Posts
    323
    OK - was confused by seeing the DBA_TAB_PARTITIONS view and this thread - the same create table script was run under the 2 schema owners for some reason ! So that solves this !!


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width