Problem in partitioning table

Hi, I'm geeting an error while i execute the following query.
Create Table Sample_Orders
(Ord_No Number,
Order_Date Date)
Partition By Range(Order_Date)
Partition SO99Q1 Values Less Than To_Date(‘01-APR-1999’, ‘DD-MON-YYYY’),
Partition SO99Q2 Values Less Than To_Date(‘01-JUL-1999’, ‘DD-MON-YYYY’));
Partition SO99Q1 Values Less Than To_Date(‘01-APR-1999’, ‘DD-MON-YYYY’)),
ORA-00911: invalid character
Thanks in advance

If only it was easy to find this type of information on the internet through searching.
http://www.psoug.org/reference/partitions.html
your syntax is wrong, i can tell you where, but i think you'll learn more by reading than by having me tell you.

Similar Messages

  • Problems with partition tables

    Hi all,
    I've got some problems with partition tables. The script at the bottom run but when I wanna insert some values it returns me an error
    (ORA-06550: line 1, column 30: PL/SQL: ORA-06552: PL/SQL: Compilation unit analysis terminated
    ORA-06553: PLS-320: the declaration of the type of this expression is incomplete or malformed
    ORA-06550: line 1, column 7: PL/SQL: SQL Statement ignored)
    and I can't understand why!
    There's something incorrect in the script or not?
    Please help me
    Thanks in advance
    Steve
    CREATE TABLE TW_E_CUSTOMER_UNIFIED
    ID_CUSTOMER_UNIFIED VARCHAR2 (27) NOT NULL ,
    START_VALIDITY_DATE DATE NOT NULL ,
    END_VALIDITY_DATE DATE ,
    CUSTOMER_STATUS VARCHAR2 (255)
    PARTITION BY RANGE (START_VALIDITY_DATE)
    SUBPARTITION BY LIST (END_VALIDITY_DATE)
    PARTITION M200909 VALUES LESS THAN (TO_DATE('20091001','YYYYMMDD'))
    (SUBPARTITION M200909_N VALUES (NULL), SUBPARTITION M200909_NN VALUES (DEFAULT)),
    PARTITION M200910 VALUES LESS THAN (TO_DATE('20091101','YYYYMMDD'))
    (SUBPARTITION M200910_N VALUES (NULL), SUBPARTITION M200910_NN VALUES (DEFAULT)),
    PARTITION M200911 VALUES LESS THAN (TO_DATE('20091201','YYYYMMDD'))
    (SUBPARTITION M200911_N VALUES (NULL), SUBPARTITION M200911_NN VALUES (DEFAULT)),
    PARTITION M200912 VALUES LESS THAN (TO_DATE('20100101','YYYYMMDD'))
    (SUBPARTITION M200912_N VALUES (NULL), SUBPARTITION M200912_NN VALUES (DEFAULT)),
    PARTITION M201001 VALUES LESS THAN (TO_DATE('20100201','YYYYMMDD'))
    (SUBPARTITION M201001_N VALUES (NULL), SUBPARTITION M201001_NN VALUES (DEFAULT)),
    PARTITION M201002 VALUES LESS THAN (TO_DATE('20100301','YYYYMMDD'))
    (SUBPARTITION M201002_N VALUES (NULL), SUBPARTITION M201002_NN VALUES (DEFAULT)),
    PARTITION M210001 VALUES LESS THAN (MAXVALUE))
    (SUBPARTITION M210001_N VALUES (NULL), SUBPARTITION M210001_NN VALUES (DEFAULT))
    ;

    Hi Hoek,
    the DB version is 10.2 (italian version, then SET is correct).
    ...there's something strange: now I can INSERT rows but I can't update them!
    I'm using this command string:
    UPDATE TW_E_CUSTOMER_UNIFIED SET END_VALIDITY_DATE = TO_DATE('09-SET-09', 'DD-MON-RR') WHERE
    id_customer_unified = '123' and start_validity_date = TO_DATE('09-SET-09', 'DD-MON-RR');
    And this is the error:
    Error SQL: ORA-14402: updating partition key column would cause a partition change
    14402. 00000 - "updating partition key column would cause a partition change"
    *Cause:    An UPDATE statement attempted to change the value of a partition
    key column causing migration of the row to another partition
    *Action:   Do not attempt to update a partition key column or make sure that
    the new partition key is within the range containing the old
    partition key.
    I think that is impossible to use a PARTITION/SUBPARTITION like that: in fact the update of "END_VALIDITY_DATE" cause a partition change.
    Do u agree or it's possible an update on a field that implies a partition change?
    Regards Steve

  • Problem regarding partitioning tables

    hi all....good afternoon
    I have a table of huge number of records and thats why I want to do partitioning of that table.
    The column upon which I have to make the partition is of varchar2(7) type which contains the data in the format '2009APR', '2010JAN' etc etc..
    Now I have to fetch out the first 4 characters of the datas (i.e only the year) and then I can partition the table based on the years.
    How can I do that....plss help.
    The database is in 10g..
    create table test123
    (name varchar2(10),
    age number,
    DOB varchar2(7),
    gender varchar2(1)
    );

    user12780416 wrote:
    hi all....good afternoon
    I have a table of huge number of records and thats why I want to do partitioning of that table.
    The column upon which I have to make the partition is of varchar2(7) type which contains the data in the format '2009APR', '2010JAN' etc etc..
    Now I have to fetch out the first 4 characters of the datas (i.e only the year) and then I can partition the table based on the years.
    How can I do that....plss help.
    The database is in 10g..
    create table test123
    (name varchar2(10),
    age number,
    DOB varchar2(7),
    gender varchar2(1)
    );I suggest you instead of this varchar column with date column like dat.And use this column as partition key.For example.
    create table test123
    (name varchar2(10),
    age number,
    DOB varchar2(7),
    gender varchar2(1),
    dat date
    partition by  range (dat)
      partition part1 values LESS THAN (TO_DATE(' 2009-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')),
      partition part2 values LESS THAN (TO_DATE(' 2009-04-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')),
      partition part3 values LESS THAN (TO_DATE(' 2009-07-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')),
      partition part4 values LESS THAN (TO_DATE(' 2009-10-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN')),
      partition part5 values LESS THAN (TO_DATE(' 2010-01-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
      )

  • Problem with partitioning - disk permanently falls back to old p-table

    Hey Guys!
    I'm quite desperate and can't find answers for the following problem - maybe some of you already had a similiar problem.
    I want to reuse a SSD that I used on a different machine as primary system drive. It's partition-table:
    # fdisk -l /dev/sda
    Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x0004f0e5
    Device     Boot  Start       End   Sectors  Size Id Type
    /dev/sda1  *      2048    499711    497664  243M 83 Linux
    /dev/sda2       501758 250068991 249567234  119G  5 Extended
    /dev/sda5       501760 250068991 249567232  119G 8e Linux LVM
    There is a LVM volume group with two volumes (root and swap) on sda5. No matter how I try to destroy the LVM setup and the partitioning, it is always "reseted" to this setup.
    I tried: lvremove, vgremove, pvremove, fdisk, cfdisk, gdisk, cgdisk, dd from /dev/null, testdisk - with and without reboots, from arch-linux booted from usb and from an ubuntu-live-cd. No matter what, the partitioning does not change.
    Why I want to reformat it? I want to use the drive as cache for zfs-on-linux.
    It feels like the drive is somehow write-protected.
    Has anyone suggestions what to try next?

    Thanks @ROOKIE
    Sadly didn't work either - see below. Underneath I added results of smart-tests - maybe I miss something.
    $ sudo lsblk
    NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
    sda      8:0    0 119.2G  0 disk
    |-sda1   8:1    0   243M  0 part
    |-sda2   8:2    0     1K  0 part
    `-sda5   8:5    0   119G  0 part
    sdc      8:32   1   7.4G  0 disk
    |-sdc1   8:33   1   512M  0 part
    `-sdc2   8:34   1   6.9G  0 part
    sdd      8:48   1   7.4G  0 disk
    |-sdd1   8:49   1   512M  0 part /boot
    `-sdd2   8:50   1   6.9G  0 part
    sr0     11:0    1  1024M  0 rom 
    zram0  254:0    0  75.1M  0 disk [SWAP]
    zram1  254:1    0  75.1M  0 disk [SWAP]
    zram2  254:2    0  75.1M  0 disk [SWAP]
    zram3  254:3    0  75.1M  0 disk [SWAP]
    $ sudo blkdiscard -v /dev/sda
    /dev/sda: Discarded 128035676160 bytes from the offset 0
    $ sudo blkdiscard -v /dev/sda
    /dev/sda: Discarded 128035676160 bytes from the offset 0
    $ sudo fdisk /dev/sda
    Welcome to fdisk (util-linux 2.26.1).                                                                                                                                                                                   
    Changes will remain in memory only, until you decide to write them.
    Be careful before using the write command.
    Command (m for help): o
    Created a new DOS disklabel with disk identifier 0x591d429c.
    Command (m for help): w
    The partition table has been altered.
    Calling ioctl() to re-read partition table.
    Syncing disks.
    $ lsblk
    NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
    sda      8:0    0 119.2G  0 disk
    |-sda1   8:1    0   243M  0 part
    |-sda2   8:2    0     1K  0 part
    `-sda5   8:5    0   119G  0 part
    sdc      8:32   1   7.4G  0 disk
    |-sdc1   8:33   1   512M  0 part
    `-sdc2   8:34   1   6.9G  0 part
    sdd      8:48   1   7.4G  0 disk
    |-sdd1   8:49   1   512M  0 part /boot
    `-sdd2   8:50   1   6.9G  0 part
    sr0     11:0    1  1024M  0 rom 
    zram0  254:0    0  75.1M  0 disk [SWAP]
    zram1  254:1    0  75.1M  0 disk [SWAP]
    zram2  254:2    0  75.1M  0 disk [SWAP]
    zram3  254:3    0  75.1M  0 disk [SWAP]
    $ sudo blkdiscard -v /dev/sda
    /dev/sda: Discarded 128035676160 bytes from the offset 0
    $ lsblk
    NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
    sda      8:0    0 119.2G  0 disk
    |-sda1   8:1    0   243M  0 part
    |-sda2   8:2    0     1K  0 part
    `-sda5   8:5    0   119G  0 part
    sdc      8:32   1   7.4G  0 disk
    |-sdc1   8:33   1   512M  0 part
    `-sdc2   8:34   1   6.9G  0 part
    sdd      8:48   1   7.4G  0 disk
    |-sdd1   8:49   1   512M  0 part /boot
    `-sdd2   8:50   1   6.9G  0 part
    sr0     11:0    1  1024M  0 rom 
    zram0  254:0    0  75.1M  0 disk [SWAP]
    zram1  254:1    0  75.1M  0 disk [SWAP]
    zram2  254:2    0  75.1M  0 disk [SWAP]
    zram3  254:3    0  75.1M  0 disk [SWAP]
    I checked smart too now:
    $ sudo smartctl -t long /dev/sda
    smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.19.3-3-ARCH] (local build)
    Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
    === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
    Sending command: "Execute SMART Extended self-test routine immediately in off-line mode".
    Drive command "Execute SMART Extended self-test routine immediately in off-line mode" successful.
    Testing has begun.
    Please wait 1 minutes for test to complete.
    Test will complete after Fri Apr 17 12:22:27 2015
    Use smartctl -X to abort test.
    $ sudo smartctl -H /dev/sda
    smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.19.3-3-ARCH] (local build)
    Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    $ sudo smartctl -a /dev/sda
    smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.19.3-3-ARCH] (local build)
    Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
    === START OF INFORMATION SECTION ===
    Model Family:     JMicron based SSDs
    Device Model:     KINGSTON SNV425S2128GB
    Serial Number:    07WA50010371
    Firmware Version: D100309a
    User Capacity:    128,035,676,160 bytes [128 GB]
    Sector Size:      512 bytes logical/physical
    Rotation Rate:    Solid State Device
    Form Factor:      2.5 inches
    Device is:        In smartctl database [for details use: -P show]
    ATA Version is:   ATA8-ACS (minor revision not indicated)
    SATA Version is:  SATA 2.6, 3.0 Gb/s
    Local Time is:    Fri Apr 17 12:31:57 2015 CEST
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    General SMART Values:
    Offline data collection status:  (0x00) Offline data collection activity
                                            was never started.
                                            Auto Offline Data Collection: Disabled.
    Self-test execution status:      (   0) The previous self-test routine completed
                                            without error or no self-test has ever
                                            been run.
    Total time to complete Offline
    data collection:                (   30) seconds.
    Offline data collection
    capabilities:                    (0x1b) SMART execute Offline immediate.
                                            Auto Offline data collection on/off support.
                                            Suspend Offline collection upon new
                                            command.
                                            Offline surface scan supported.
                                            Self-test supported.
                                            No Conveyance Self-test supported.
                                            No Selective Self-test supported.
    SMART capabilities:            (0x0003) Saves SMART data before entering
                                            power-saving mode.
                                            Supports SMART auto save timer.
    Error logging capability:        (0x01) Error logging supported.
                                            General Purpose Logging supported.
    Short self-test routine
    recommended polling time:        (   1) minutes.
    Extended self-test routine
    recommended polling time:        (   1) minutes.
    SMART Attributes Data Structure revision number: 16
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
      1 Raw_Read_Error_Rate     0x000b   100   100   050    Pre-fail  Always       -       0
      2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
      3 Unknown_Attribute       0x0007   100   100   050    Pre-fail  Always       -       0
      5 Reallocated_Sector_Ct   0x0013   100   100   050    Pre-fail  Always       -       0
      7 Unknown_Attribute       0x000b   100   100   050    Pre-fail  Always       -       0
      8 Unknown_Attribute       0x0005   100   100   050    Pre-fail  Offline      -       0
      9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       12054
    10 Unknown_Attribute       0x0013   100   100   050    Pre-fail  Always       -       0
    12 Power_Cycle_Count       0x0012   100   100   000    Old_age   Always       -       5448
    168 SATA_Phy_Error_Count    0x0012   100   100   000    Old_age   Always       -       0
    175 Bad_Cluster_Table_Count 0x0003   100   100   010    Pre-fail  Always       -       29
    192 Unexpect_Power_Loss_Ct  0x0012   100   100   000    Old_age   Always       -       0
    194 Temperature_Celsius     0x0022   052   100   020    Old_age   Always       -       52 (Min/Max 29/52)
    197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
    240 Unknown_Attribute       0x0013   100   100   050    Pre-fail  Always       -       0
    170 Bad_Block_Count         0x0003   100   100   010    Pre-fail  Always       -       144 329 118
    173 Erase_Count             0x0012   100   100   000    Old_age   Always       -       6399 10521 7887
    SMART Error Log Version: 1
    ATA Error Count: 153 (device log contains only the most recent five errors)
            CR = Command Register [HEX]
            FR = Features Register [HEX]
            SC = Sector Count Register [HEX]
            SN = Sector Number Register [HEX]
            CL = Cylinder Low Register [HEX]
            CH = Cylinder High Register [HEX]
            DH = Device/Head Register [HEX]
            DC = Device Command Register [HEX]
            ER = Error register [HEX]
            ST = Status register [HEX]
    Powered_Up_Time is measured from power on, and printed as
    DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
    SS=sec, and sss=millisec. It "wraps" after 49.710 days.
    Error 153 occurred at disk power-on lifetime: 11818 hours (492 days + 10 hours)
      When the command that caused the error occurred, the device was active or idle.
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      40 51 00 28 66 d3 eb  Error: UNC at LBA = 0x0bd36628 = 198403624
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      c8 00 08 28 66 d3 eb 08  36d+21:07:12.000  READ DMA
      ec 00 00 00 00 00 a0 08  36d+21:07:12.000  IDENTIFY DEVICE
      ef 03 45 00 00 00 a0 08  36d+21:07:12.000  SET FEATURES [Set transfer mode]
      ec 00 00 00 00 00 a0 08  36d+21:07:12.000  IDENTIFY DEVICE
      c8 00 08 28 66 d3 eb 08  36d+21:07:12.000  READ DMA
    Error 152 occurred at disk power-on lifetime: 11818 hours (492 days + 10 hours)
      When the command that caused the error occurred, the device was active or idle.
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      40 51 00 28 66 d3 eb  Error: UNC at LBA = 0x0bd36628 = 198403624
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      c8 00 08 28 66 d3 eb 08  36d+21:07:12.000  READ DMA
      c8 00 08 20 66 d3 eb 08  36d+21:07:12.000  READ DMA
      c8 00 08 18 66 d3 eb 08  36d+21:07:12.000  READ DMA
      c8 00 08 10 66 d3 eb 08  36d+21:07:12.000  READ DMA
      c8 00 08 08 66 d3 eb 08  36d+21:07:12.000  READ DMA
    Error 151 occurred at disk power-on lifetime: 11818 hours (492 days + 10 hours)
      When the command that caused the error occurred, the device was active or idle.
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      40 51 00 00 66 d3 eb  Error: UNC at LBA = 0x0bd36600 = 198403584
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      c8 00 00 00 66 d3 eb 08  36d+21:07:12.000  READ DMA
      c8 00 00 00 65 d3 eb 08  36d+21:07:12.000  READ DMA
      c8 00 00 00 64 d3 eb 08  36d+21:07:12.000  READ DMA
      c8 00 00 00 63 d3 eb 08  36d+21:07:12.000  READ DMA
      c8 00 00 00 62 d3 eb 08  36d+21:07:12.000  READ DMA
    Error 150 occurred at disk power-on lifetime: 6211 hours (258 days + 19 hours)
      When the command that caused the error occurred, the device was active or idle.
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      40 51 00 a8 f6 75 eb  Error: UNC at LBA = 0x0b75f6a8 = 192280232
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      c8 00 08 a8 f6 75 eb 08      04:55:01.600  READ DMA
      ec 00 00 00 00 00 a0 08      04:55:01.600  IDENTIFY DEVICE
      ef 03 45 00 00 00 a0 08      04:55:01.600  SET FEATURES [Set transfer mode]
      ec 00 00 00 00 00 a0 08      04:55:01.600  IDENTIFY DEVICE
      c8 00 08 a8 f6 75 eb 08      04:55:01.500  READ DMA
    Error 149 occurred at disk power-on lifetime: 6211 hours (258 days + 19 hours)
      When the command that caused the error occurred, the device was active or idle.
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      40 51 00 a8 f6 75 eb  Error: UNC at LBA = 0x0b75f6a8 = 192280232
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      c8 00 08 a8 f6 75 eb 08      04:55:01.500  READ DMA
      c8 00 08 a0 f6 75 eb 08      04:55:01.500  READ DMA
      c8 00 08 98 f6 75 eb 08      04:55:01.500  READ DMA
      c8 00 08 90 f6 75 eb 08      04:55:01.500  READ DMA
      c8 00 08 88 f6 75 eb 08      04:55:01.500  READ DMA
    SMART Self-test log structure revision number 1
    Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
    # 1  Extended offline    Completed without error       00%     12054         -
    # 2  Extended offline    Completed without error       00%     11117         -
    # 3  Short offline       Completed without error       00%     11116         -
    # 4  Extended offline    Completed without error       00%     11100         -
    # 5  Short offline       Completed without error       00%      6804         -
    # 6  Short offline       Completed without error       00%      2818         -
    # 7  Short offline       Completed without error       00%      2750         -
    # 8  Short offline       Completed without error       00%      2744         -
    # 9  Short offline       Aborted by host               00%      2521         -
    #10  Short offline       Completed without error       00%      2448         -
    #11  Short offline       Completed without error       00%      2290         -
    #12  Short offline       Completed without error       00%      2120         -
    #13  Short offline       Completed without error       00%      2021         -
    #14  Short offline       Completed without error       00%      1936         -
    #15  Short offline       Completed without error       00%      1859         -
    #16  Short offline       Completed without error       00%      1823         -
    #17  Short offline       Completed without error       00%      1727         -
    #18  Short offline       Completed without error       00%      1687         -
    #19  Short offline       Completed without error       00%      1580         -
    #20  Short offline       Completed without error       00%      1292         -
    #21  Short offline       Completed without error       00%      1245         -
    Selective Self-tests/Logging not supported

  • Problem of full table scan on a partitioned table

    hi all
    There is a table called "si_sync_operation" that have 171040 number of rows.
    I partitioned that table into a new table called "si_sync_operation_par" with 7 partitoins.
    I issued the following statements
    SELECT * FROM si_sync_operation_par.
    SELECT * FROM si_sync_operation.
    The explain plan show that the cost of the first statement is 1626 and that of the second statments is 1810.
    The "cost" of full table scan on partitioned table is lower than the that of non-partitioned table.That's fine.
    But the "Bytes" of full table scan on partitioned table is 5761288680 and that of the non-partitioned table is 263743680.
    Why full table scan on partitioned table access more bytes than non-partitioned table?
    And how could a statment that access more bytes results a lower cost?
    Thank u very much

    As Hemant metioned bytes reported are approximate number of bytes. As far as Cost is concerned, according to Tom its just a number and we should not compare queries by their cost. (search asktom.oracle.com for more information)
    SQL> drop table non_part purge;
    Table dropped.
    SQL> drop table part purge;
    Table dropped.
    SQL>
    SQL> CREATE TABLE non_part
      2        (id  NUMBER(5),
      3         dt    DATE);
    Table created.
    SQL>
    SQL> CREATE TABLE part
      2        (id  NUMBER(5),
      3         dt    DATE)
      4         PARTITION BY RANGE(dt)
      5         (
      6         PARTITION part1_jan2008 VALUES LESS THAN(TO_DATE('01/02/2008','DD/MM/YYYY')),
      7         PARTITION part2_feb2008 VALUES LESS THAN(TO_DATE('01/03/2008','DD/MM/YYYY')),
      8         PARTITION part3_mar2008 VALUES LESS THAN(TO_DATE('01/04/2008','DD/MM/YYYY')),
      9         PARTITION part4_apr2008 VALUES LESS THAN(TO_DATE('01/05/2008','DD/MM/YYYY')),
    10         PARTITION part5_may2008 VALUES LESS THAN(TO_DATE('01/06/2008','DD/MM/YYYY'))
    11       );
    Table created.
    SQL>
    SQL>
    SQL> insert into non_part select rownum, trunc(sysdate) - rownum from dual connect by level <= 140;
    140 rows created.
    Execution Plan
    Plan hash value: 1731520519
    | Id  | Operation                     | Name | Rows  | Cost (%CPU)| Time     |
    |   0 | INSERT STATEMENT              |      |     1 |     2   (0)| 00:00:01 |
    |   1 |  COUNT                        |      |       |            |          |
    |*  2 |   CONNECT BY WITHOUT FILTERING|      |       |            |          |
    |   3 |    FAST DUAL                  |      |     1 |     2   (0)| 00:00:01 |
    Predicate Information (identified by operation id):
       2 - filter(LEVEL<=140)
    SQL>
    SQL> insert into part select * from non_part;
    140 rows created.
    Execution Plan
    Plan hash value: 1654070669
    | Id  | Operation         | Name     | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | INSERT STATEMENT  |          |   140 |  3080 |     3   (0)| 00:00:01 |
    |   1 |  TABLE ACCESS FULL| NON_PART |   140 |  3080 |     3   (0)| 00:00:01 |
    Note
       - dynamic sampling used for this statement
    SQL>
    SQL> commit;
    Commit complete.
    SQL>
    SQL> set line 10000
    SQL> set autotrace traceonly exp
    SQL> select * from non_part;
    Execution Plan
    Plan hash value: 1654070669
    | Id  | Operation         | Name     | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT  |          |   140 |  3080 |     3   (0)| 00:00:01 |
    |   1 |  TABLE ACCESS FULL| NON_PART |   140 |  3080 |     3   (0)| 00:00:01 |
    Note
       - dynamic sampling used for this statement
    SQL> select * from part;
    Execution Plan
    Plan hash value: 3392317243
    | Id  | Operation           | Name | Rows  | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
    |   0 | SELECT STATEMENT    |      |   140 |  3080 |     9   (0)| 00:00:01 |       |       |
    |   1 |  PARTITION RANGE ALL|      |   140 |  3080 |     9   (0)| 00:00:01 |     1 |     5 |
    |   2 |   TABLE ACCESS FULL | PART |   140 |  3080 |     9   (0)| 00:00:01 |     1 |     5 |
    Note
       - dynamic sampling used for this statement
    SQL>
    SQL> exec dbms_stats.gather_table_stats(user, 'non_part');
    PL/SQL procedure successfully completed.
    SQL> exec dbms_stats.gather_table_stats(user, 'part');
    PL/SQL procedure successfully completed.
    SQL>
    SQL>
    SQL> select * from non_part;
    Execution Plan
    Plan hash value: 1654070669
    | Id  | Operation         | Name     | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT  |          |   140 |  1540 |     3   (0)| 00:00:01 |
    |   1 |  TABLE ACCESS FULL| NON_PART |   140 |  1540 |     3   (0)| 00:00:01 |
    SQL> select * from part;
    Execution Plan
    Plan hash value: 3392317243
    | Id  | Operation           | Name | Rows  | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
    |   0 | SELECT STATEMENT    |      |   140 |  1540 |     9   (0)| 00:00:01 |       |       |
    |   1 |  PARTITION RANGE ALL|      |   140 |  1540 |     9   (0)| 00:00:01 |     1 |     5 |
    |   2 |   TABLE ACCESS FULL | PART |   140 |  1540 |     9   (0)| 00:00:01 |     1 |     5 |
    SQL>After analyzing the tables, notice that the Bytes column has changed value

  • Error while creating partition table

    Hi frnds i am getting error while i am trying to create a partition table using range
    getting error ORA-00906: missing left parenthesis.I used the following statement to create partition table
    CREATE TABLE SAMPLE_ORDERS
    (ORDER_NUMBER NUMBER,
    ORDER_DATE DATE,
    CUST_NUM NUMBER,
    TOTAL_PRICE NUMBER,
    TOTAL_TAX NUMBER,
    TOTAL_SHIPPING NUMBER)
    PARTITION BY RANGE(ORDER_DATE)
    PARTITION SO99Q1 VALUES LESS THAN TO_DATE(‘01-APR-1999’, ‘DD-MON-YYYY’),
    PARTITION SO99Q2 VALUES LESS THAN TO_DATE(‘01-JUL-1999’, ‘DD-MON-YYYY’),
    PARTITION SO99Q3 VALUES LESS THAN TO_DATE(‘01-OCT-1999’, ‘DD-MON-YYYY’),
    PARTITION SO99Q4 VALUES LESS THAN TO_DATE(‘01-JAN-2000’, ‘DD-MON-YYYY’),
    PARTITION SO00Q1 VALUES LESS THAN TO_DATE(‘01-APR-2000’, ‘DD-MON-YYYY’),
    PARTITION SO00Q2 VALUES LESS THAN TO_DATE(‘01-JUL-2000’, ‘DD-MON-YYYY’),
    PARTITION SO00Q3 VALUES LESS THAN TO_DATE(‘01-OCT-2000’, ‘DD-MON-YYYY’),
    PARTITION SO00Q4 VALUES LESS THAN TO_DATE(‘01-JAN-2001’, ‘DD-MON-YYYY’)
    ;

    More than one of them. Try this instead:
    CREATE TABLE SAMPLE_ORDERS
    (ORDER_NUMBER NUMBER,
    ORDER_DATE DATE,
    CUST_NUM NUMBER,
    TOTAL_PRICE NUMBER,
    TOTAL_TAX NUMBER,
    TOTAL_SHIPPING NUMBER)
    PARTITION BY RANGE(ORDER_DATE) (
    PARTITION SO99Q1 VALUES LESS THAN (TO_DATE('01-APR-1999', 'DD-MON-YYYY')),
    PARTITION SO99Q2 VALUES LESS THAN (TO_DATE('01-JUL-1999', 'DD-MON-YYYY')),
    PARTITION SO99Q3 VALUES LESS THAN (TO_DATE('01-OCT-1999', 'DD-MON-YYYY')),
    PARTITION SO99Q4 VALUES LESS THAN (TO_DATE('01-JAN-2000', 'DD-MON-YYYY')),
    PARTITION SO00Q1 VALUES LESS THAN (TO_DATE('01-APR-2000', 'DD-MON-YYYY')),
    PARTITION SO00Q2 VALUES LESS THAN (TO_DATE('01-JUL-2000', 'DD-MON-YYYY')),
    PARTITION SO00Q3 VALUES LESS THAN (TO_DATE('01-OCT-2000', 'DD-MON-YYYY')),
    PARTITION SO00Q4 VALUES LESS THAN (TO_DATE('01-JAN-2001', 'DD-MON-YYYY')))In the future, if you are having problems, go to Morgan's Library at www.psoug.org.
    Find a working demo, copy it, then modify it for your purposes.

  • How to fix a faulty partition table, How to fix a faulty partition table

    I have a 400gb partition on my 500gb HD, the remaining 100gb was split up in 3 partitions. I deleted 2 of these partitions, restarted and now Disk Utility claims my 400gb drive is now 53gb, accessing files has become impossible.
    I can still see all the files listed but am unable to open them or copy them, I get a -36 error.
    I have thrown Disk Utility, DiskWarrior, TechTool Pro and some lesser known tools at it but none of them wants to repair the volume.
    Sounds to me like a busted partition table, after all that was all that was altered, in theory I should be able to access my files. Does anyone have any suggestions on how to fix this?

    Problem solved, I used iPartition to resize the partition back to its original size after which I could copy all data off.

  • "Windows cannot be installed to this disk. The selected disk has an MBR partition table. On EFI systems, windows can only be installed to GPT disks." Error

    Hey Im getting the following error when trying to install windows from a USB. 
    "Windows cannot be installed to this disk. The selected disk has an MBR partition table. On EFI systems, windows can only be installed to GPT disks."
    I installed the windows 8 (64bit) iso using boot camp to a usb.  I was able to do this after changing the info.plist to allow me to place the iso on the usb.  After I make the partition and start the install, I get the above error.  I formatted the partition in the installation but I keep getting this error.  I've repreated the entire process but i keep getting this errror and the disk utility says my partition is a Windows NT File System (NTFS) so im not sure what's going on.  If you can help me that would be greatly appreciated

    I am having the same problem. Windows is trying to install. It identifies the various partitions but says that I cannot install Windows on the Boot Camp partition or any other. I select Drive options (advanced) and Format the Boot Camp drive, but it makes no difference.
    This is the Windows error:
    Windows cannot be installed to this disk. The selected disk has an MBR partition table. On EFI systems, Windows can only be installed to GPT disks.
    Windows cannot be installed to this disk. This computer's hardware may not support booting to this disk. Ensure that the disk's controller is enabled in the computer BIOS menu.
    I am not sure what Csound1 is suggesting with that post above. There are some involved suggestions over here <https://discussions.apple.com/message/23548999#23548999> about using Disk Utility to delete the Boot Camp partition and create new ones - is that the idea?

  • Is my partition table corrupt? Why does Boot Camp hate me?

    Hi folks
    I have an iMac (27-inch, Mid 2010) (iMac11,3, with Boot ROM IM112.0057.B01).
    I replaced the internal SuperDrive with an SSD, which is now my primary boot device:
    iMac:/ michthom$ diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *250.1 GB   disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:                  Apple_HFS SSD                     248.1 GB   disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
    iMac:/ michthom$ sudo gpt -r -vv show disk0
    Password:
    gpt show: disk0: mediasize=250059350016; sectorsize=512; blocks=488397168
    gpt show: disk0: PMBR at sector 0
    gpt show: disk0: Pri GPT at sector 1
    gpt show: disk0: Sec GPT at sector 488397167
          start       size  index  contents
              0          1         PMBR
              1          1         Pri GPT header
              2         32         Pri GPT table
             34          6       
             40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
         409640  484620800      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
      485030440    1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
      486299976    2097159       
      488397135         32         Sec GPT table
      488397167          1         Sec GPT header
    So far so good.
    I want to use the original internal HDD both to run Windows in Boot Camp mode, and to have a partition for my bulk data that doesn't need to be on the SSD.
    I reformatted the HDD as a single HFS+ partition, GUID partition table.
    I used BCA to create a Windows USB boot device from the Windows 8.1 media after following the hacking in this link.
    When the iMac restarted after creating the 250Gb Windows partition on the internal HDD, I got the "no boot device" screen.
    I restarted holding Option/Alt and booted from EFI Boot on the USB stick. Windows installer started, at least. Serial number accepted, on to picking a location.
    The installation balked when I tried to select the BOOTCAMP partition, with the warning that the disk was formatted as MBR - eh? Why?
    So, the current state of the internal HDD must be wrong somehow, but I don't see how to fix it (confidently) and would like someone to point me in the right direction (please!)
    iMac:/ michthom$ diskutil list
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *1.0 TB     disk1
       1:                        EFI EFI                     209.7 MB   disk1s1
       2:                  Apple_HFS Internal                751.9 GB   disk1s2
       3:       Microsoft Basic Data BOOTCAMP                248.0 GB   disk1s3
    iMac:/ michthom$ sudo gpt -r -vv show disk1
    gpt show: disk1: mediasize=1000204886016; sectorsize=512; blocks=1953525168
    gpt show: disk1: Suspicious MBR at sector 0
    gpt show: disk1: Pri GPT at sector 1
    gpt show: disk1: Sec GPT at sector 1953525167
           start        size  index  contents
               0           1         MBR
               1           1         Pri GPT header
               2          32         Pri GPT table
              34           6        
              40      409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
          409640  1468478336      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
      1468887976      263256        
      1469151232   484372480      3  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
      1953523712        1423        
      1953525135          32         Sec GPT table
      1953525167           1         Sec GPT header
    gdisk has this to say:
    iMac:/ michthom$ sudo gdisk /dev/disk1
    Password:
    GPT fdisk (gdisk) version 0.8.10
    Warning: Devices opened with shared lock will not have their
    partition table automatically reloaded!
    Partition table scan:
      MBR: hybrid
      BSD: not present
      APM: not present
      GPT: present
    Found valid GPT with hybrid MBR; using GPT.
    Command (? for help): x
    Expert command (? for help): o
    Disk size is 1953525168 sectors (931.5 GiB)
    MBR disk identifier: 0x4F5BB38B
    MBR partitions:
    Number  Boot  Start Sector   End Sector   Status      Code
       1                     1       409639   primary     0xEE
       2                409640   1468887975   primary     0xAF
       3            1469151232   1953523711   primary     0x0B
    Expert command (? for help): p
    Disk /dev/disk1: 1953525168 sectors, 931.5 GiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): 3E1D7EF9-F86E-4552-8F40-BE9754C3C73F
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 1953525134
    Partitions will be aligned on 8-sector boundaries
    Total free space is 264685 sectors (129.2 MiB)
    Number  Start (sector)    End (sector)  Size       Code  Name
       1              40          409639   200.0 MiB   EF00  EFI System Partition
       2          409640      1468887975   700.2 GiB   AF00  Internal
       3      1469151232      1953523711   231.0 GiB   0700  BOOTCAMP
    Any help / pointers gratefully accepted!
    Mike

    Thanks to Loner T and some more reading, I think I'm now sorted out.
    I found that marking the first partition on the USB stick as Active made no difference - my only option was to boot from the "EFI boot" option at startup (when holding down the alt/option key).
    So to get the Windows installer to behave, I used gdisk to write a new protective MBR before rebooting to the USB stick, as shown below.
    With the protective MBR in place (rather than hybrid), the Windows installer was happy to reformat the chosen partition and the installation began.
    I'll try to report back once all is installed and working, but once again I owe my sanity to the generosity and patience of strangers!
    Mike
    bash-3.2# gdisk /dev/disk0
    GPT fdisk (gdisk) version 0.8.10
    Warning: Devices opened with shared lock will not have their
    partition table automatically reloaded!
    Partition table scan:
      MBR: hybrid
      BSD: not present
      APM: not present
      GPT: present
    Found valid GPT with hybrid MBR; using GPT.
    Command (? for help): x
    Expert command (? for help): o
    <snipped>
    Number  Boot  Start Sector  End Sector  Status      Code
      1                    1      409639  primary    0xEE
      2                409640  1468887975  primary    0xAF
      3            1469151232  1953523711  primary    0x0B
    Expert command (? for help): p
    <snipped>
    Number  Start (sector)    End (sector)  Size      Code  Name
      1              40          409639  200.0 MiB  EF00  EFI System Partition
      2          409640      1468887975  700.2 GiB  AF00  Internal
      3      1469151232      1953523711  231.0 GiB  0700  BOOTCAMP
    Expert command (? for help): v
    No problems found. 264685 free sectors (129.2 MiB) available in 3
    segments, the largest of which is 263256 (128.5 MiB) in size.
    Expert command (? for help): x
    <snipped>
    n create a new protective MBR
    <snipped>
    Expert command (? for help): n
    Expert command (? for help): w
    Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
    PARTITIONS!!
    Do you want to proceed? (Y/N): y
    OK; writing new GUID partition table (GPT) to /dev/disk0.
    Warning: Devices opened with shared lock will not have their
    partition table automatically reloaded!
    Warning: The kernel may continue to use old or deleted partitions.
    You should reboot or remove the drive.
    The operation has completed successfully.
    bash-3.2# gdisk /dev/disk0
    GPT fdisk (gdisk) version 0.8.10
    Warning: Devices opened with shared lock will not have their
    partition table automatically reloaded!
    Partition table scan:
      MBR: protective
      BSD: not present
      APM: not present
      GPT: present
    Found valid GPT with protective MBR; using GPT.
    Command (? for help): x
    Expert command (? for help): o
    Disk size is 1953525168 sectors (931.5 GiB)
    MBR disk identifier: 0x00000000
    MBR partitions:
    Number  Boot  Start Sector  End Sector  Status      Code
      1                    1  1953525167  primary    0xEE
    Expert command (? for help): p
    <snipped>
    Number  Start (sector)    End (sector)  Size      Code  Name
      1              40          409639  200.0 MiB  EF00  EFI System Partition
      2          409640      1468887975  700.2 GiB  AF00  Internal
      3      1469151232      1953523711  231.0 GiB  0700  BOOTCAMP

  • Mid 2010 iMac upgraded SSD, can't seem to install windows via bootcamp. Windows can't be installed on this storage device. The chosen harddisk contains a MBR-partition-table. Windows can only be installed on GPT-harddisks on EFI-systems error

    I have windows 8.1 on DVD & on USB CF Reader/Card. I've followed the full steps in bootcamp, but when it restarts and its time to select the bootcamp partition to install windows (after alt rebooting to the efi startup) I get the "Windows can't be installed on this storage device. The chosen harddisk contains a MBR-partition-table. Windows can only be installed on GPT-harddisks on EFI-systems" error.
    I've scoured the internet trying different solutions that seem to work for everyone else, but to no avail. I've reformatted from that screen, doesn't help. I've removed bootcamp partition and manually partitioned using disk util, leaving it empty once partition-wise, and filling it with a blank partition the second time. I've done a full back up and clean re-install of Yosemite, and nothing seems to be working.
    Thats when I switched to DVD install, as I heard sometimes you can't install with a CF card. When I alt-boot, I can see EFI-windows and windows, but if I select EFI-windows, same problem as before, and if I select windows, I get the black screen of "no bootable device please insert boot disk and press any key."
    I've been stuck w/o bootcamp for over 2 years now. Anyone, please help?
    Mid 2010 iMac running 256gb SSD, Yosemite 10.10.1 trying to install windows 8.1

    I am having the same problem. Windows is trying to install. It identifies the various partitions but says that I cannot install Windows on the Boot Camp partition or any other. I select Drive options (advanced) and Format the Boot Camp drive, but it makes no difference.
    This is the Windows error:
    Windows cannot be installed to this disk. The selected disk has an MBR partition table. On EFI systems, Windows can only be installed to GPT disks.
    Windows cannot be installed to this disk. This computer's hardware may not support booting to this disk. Ensure that the disk's controller is enabled in the computer BIOS menu.
    I am not sure what Csound1 is suggesting with that post above. There are some involved suggestions over here <https://discussions.apple.com/message/23548999#23548999> about using Disk Utility to delete the Boot Camp partition and create new ones - is that the idea?

  • How do I get my mac partition to use GUID partition Table Scheme?

    I just bought the upgrade for Mountain Lion on my Macbook pro (Mac OS X 10.6.8). I went to install it and i had partitioned my internal harddrive with bootcamp to run windows 7. I went to select the Macintosh partition and it says that disk does not use the GUID partition Table scheme, and it will not let me select it for the upgrade. It says I have to use Disk Utility but I cant seem to figure out how to get it so I can upgrade it to mountain lion. Please help and thank you for your time
    P.S. - Let me know if you need more information to get to the conclusion to this problem.

    Bonjour is built-in to OS X. No download is needed.
    Safari has a Bonjour browser which you can activate by opening Safari Preferences, selecting Advanced and enabling one of the Bonjour entries to add a Bookmark. If you then select the Bookmark, all devices on your local network that are advertising themselves with Bonjour will be shown.
    With regards to the Air not finding the printer attached via USB, you can open System Information and select USB in the left column. The top right pane will show all the USB busses on the Air and if the printer and its USB cable are working correctly, then the printer should be listed under one of the USB busses. Do you see it? If not, try another USB printer cable.

  • Partition Table Query taking Too Much Time

    I have created partition table and Created local partition index on a column whose datatype is DATE.
    Now when I Query table and use index column in the where clause It is scaning all the table (Full scan) . The quey is :
    Select * From mytable
    where to_char(transaction_date, 'DD-MON-YY') = '01-Aug-07';
    I have to use to_char function not to_date due to Front end application problem.

    Before we go too far with this, if you manually query with TO_DATE on the variable instead of TO_CHAR on the column, does the query actually use the index?
    The TO_CHAR on the column will definitely stop Oracle from using any index on the column. If the query will use the index if you TO_DATE the variable, as I see it, you have three options. First, fix the application problem that won't let you use TO_DATE from the application. Second, change the application to call a function returning a ref cursor, get the date string as a parameter to the function, and do the TO_DATE in the function.
    Third, you could consider creating a function-based index on TO_CHAR(transaction_date, 'dd-Mon-yy'). This would be the least desirable option, particularly if you would also be selecting records based on a range of transaction_dates, since it loses a lot of information that the optimizer could use in devising an efficient query plan. It could also change your results for a range scan.
    John

  • How to import partitioned tables in different tablespace

    Hi everyone,
    I try to import the partitioned tables in different tablespace.
    Consider the following situation:
    I have a dump file which is created by using "Export" utility. Some data are in partitioned tables, some of them are in non-partitioned tables. Also, all tables are located in "MYTBS" tablesapce. I try to import all data from this dump file to another database. I didn't get error messages when importing the data from non-partitioned tables. However, I got error message when importing the data from partitioned tables. The error message is: tablespace 'MYTBS' does not exist.
    I just want to how I can solve this problem other than create 'MYTBS' tablespace for my new database.
    Thanks in advance.
    Angel

    Hi,
    I got the following error message:
    IMP-00017: following statement failed with ORACLE error 959:
    "CREATE TABLE "FACILITYCONNECTION",....., "CONNECTIONTYPE" "
    "NUMBER(1, 0) NOT NULL ENABLE) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 25"
    "5 PARALLEL ( DEGREE DEFAULT INSTANCES 1) NOLOGGING STORAGE( PCTINCREASE 0) "
    "TABLESPACE "MYTBS" PARTITION BY RANGE ("CONNECTIONTYPE" ) (PARTITION "
    ""EXT" VALUES LESS THAN (1) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 S"
    "TORAGE(INITIAL 65536) TABLESPACE "MYTBS" NOLOGGING, PARTITION "FAC" VA"
    "LUES LESS THAN (2) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 STORAGE(I"
    "NITIAL 65536) TABLESPACE "MYTBS" NOLOGGING )"
    IMP-00003: ORACLE error 959 encountered
    ORA-00959: tablespace 'MYTBS' does not exist
    Thanks.
    Angel

  • Problem removing partition using CCC please help

    Yesterday I tried using CCC to clone my hard drive to a 2TB Lacie external hard drive I purchased at local Apple store. All I did was follow CCC instructions but after 3 attempts and communicating with CCC help I've given up. But I have a problem in that I partitioned my HD into 2 and cannot delete the bottom partition to regain the 120GB there. I'm trying to copy and paste here but so far can only copy this:
      Disk Description : Hitachi HTS545025B9SA02 Media  Total Capacity : 250.06 GB (250,059,350,016 Bytes)
      Connection Bus : SATA  Write Status : Read/Write
      Connection Type : Internal  S.M.A.R.T. Status : Verified
      Partition Map Scheme : GUID Partition Table
    I'll try to describe as best I can. The Partition Layout:
    pulldown is greyed out but says "Current"
    The top partition is called Macintosh HD and is mostly blue. When I put my pointer on it this comes up; "This is the startup partition. You can't erase it. Size 124.6GB. Available Space: 30.03 GB"
    The bottom partition is called Macintosh HD2 and is almost all white. When I place the pointer over it; "Size 124.47 GB. Space Available 118.74 GB"
    On the right hand side of the screen there are instructions, "To erase and partition the selected disk, choose a layout from the Partition Layout pop up menu, select options for each partition and click Apply."
    I can't do this because the pop up menu is greyed out.
    I can change the size of the partition which doesn't help.
    I tried simply clicking on the Macintosh HD2 partition and clicking the "-" box but could not unmount the partition.
    "Options", "Revert", and "apply" all are greyed out
    I can highlite Macintosh HD2 on the left hand side and click erase to erase any data on it, but don't hinkthat's a very good idea.
    I just want to restore the HD to it's original single partition and try another shot at cloning, maybe with SUPERDUPER. Any  help would be greatly appreciated.
    Thank you.
    Keith

    Sounds like you have your firewall turned on, which is good.
    Check the online help files for iChat and firewall. You will find guidance to create a special ports setting that will clear up your problems. The specific ports to set in a new configuration will be listed. (With iChat frontmost, select Help > iChat Help.)

  • Problem defining partition for storing value 0 with new data

    Hi forumers,
    I've a problem with partitioning and need some advices.
    I've a table that will be partitioned by column Process_N which have values from 0 to 50000:
    Process_N between 1 and 29999 represents old data;
    Process_N >= 30000 represents new data;
    Process_N = 0 means the row is not processed yet and so these value represents new data too.
    Can I have a partition for old values (from 1 to 29999) and another partition to store new values (0 + values >= 30000) ? Hou can I define that ?
    Thank you in advance.
    Best Regards,
    Helena

    Helena,
    What's your oracle version? I think it will be better to create 3 partitions usign RANGE partitions (< 1, 2-29999, >=30000 <=50000). Is there a specific reason you want to include 0 and values greater than 29000 in one partition? What the significant difference between 0 and 30000 specially as both represent new data?
    CREATE TABLE my_part_table (
       process_n NUMBER NULL,
       my_data VARCHAR2 (1 BYTE) NULL,
       my_other_data VARCHAR2 (30 BYTE) NULL,
       data_state NUMBER NULL
    TABLESPACE test_data
    PARTITION BY RANGE (process_n)
       (PARTITION partition_0
           VALUES LESS THAN (1)
           TABLESPACE test_data,
       PARTITION partition_2_29999
          VALUES LESS THAN (30000)
          TABLESPACE test_data,
       PARTITION partition_30000
          VALUES LESS THAN (50001)
          TABLESPACE test_data);Regards

Maybe you are looking for