An interesting error: "recursive partition table"

So I just found an old 8 Gb SD card I had forgotten about (and was overjoyed because I had just said "if only I had a bigger SD card". Why do good things happen to bad people?). Several months ago I'd used some Windows tool, I think, to make a live USB for ArchBang, which hadn't worked. I put it in my computer and ran `fdisk -l` and got this:
# fdisk -l
Disk /dev/sdd: 7948 MB, 7948206080 bytes
64 heads, 32 sectors/track, 7580 cylinders, total 15523840 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
Disk identifier: 0x0c7e5ddb
Device Boot Start End Blocks Id System
/dev/sdd1 * 0 1003519 501760 17 Hidden HPFS/NTFS
Disk /dev/sdd1: 513 MB, 513802240 bytes
64 heads, 32 sectors/track, 490 cylinders, total 1003520 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
Disk identifier: 0x0c7e5ddb
Device Boot Start End Blocks Id System
/dev/sdd1p1 * 0 1003519 501760 17 Hidden HPFS/NTFS
When I ran gparted (a graphical partition editor), it threw up "Invalid partition table: recursive partition on /dev/sdd". Gparted then treats the disk as unformatted, which is presumably its "fallback" behaviour.
This isn't actually a problem for me as I don't need any of the data on the card, but I thought it was a pretty interesting error, so I'd post it here for discussion. I can't work out what's going on, but it seems to me that someething is seriously bawsled up here! Perhaps there was a bug in the library the Windows utility used? I haven't found anything similar online, although this was interesting.
Today may be a day for me to read up on partition tables and the heads/disks/cylinders/sectors/tracks abstractions!

I get the same result when using dd to write the archlinux installer image to usb. It's nothing really. it can easily have a new partition table made with gparted. It's likely the tool you used in Windows also wrote the bootable image with a low level utility similar to dd. dd generally starts at the very beginning of a disk when pointed at the device and not a partition number. /dev/sdb instead of /dev/sdb1. Meaning it overwrites the first 512byte sector too(mbr) With whatever the image/ISO contains. I've never regarded it as an issue. Just kinda confusing to tools that expect data like a partition table to be present in a normal structure.

Similar Messages

Jdev 11g defect: Error creating partition table diagram

I'm running Jdev 11.1.1.0.2 on JDK 1.6.0_06
When attempting to drag partitioned table from DB connection onto a DB Diagram I'm getting the following exception. Anybody got similar experience?
Also every time I create new diagram or off-line DB JDev starts spinning at 40 - 50 % CPU and gets stuck, so I have to "kill" the process and restart it. After which it works fine. Could it be some JDK compatibility issue?
May 13, 2009 4:09:54 PM oracle.ide.db.transfer
SEVERE: Prepare failed
java.lang.NullPointerException
     at oracle.javatools.db.ora.OracleTableBuilder.getOracleTablePartitions(OracleTableBuilder.java:584)
     at oracle.javatools.db.ora.OracleTableBuilder.buildNonBaseProperties(OracleTableBuilder.java:406)
     at oracle.javatools.db.ora.OracleTableBuilder.fillInObject(OracleTableBuilder.java:76)
     at oracle.javatools.db.AbstractDBObjectBuilder.buildObject(AbstractDBObjectBuilder.java:36)
     at oracle.javatools.db.dictionary.DictionaryDBObjectBuilder.buildObject(DictionaryDBObjectBuilder.java:55)
     at oracle.javatools.db.AbstractSchemaObject.checkInitEx(AbstractSchemaObject.java:229)
     at oracle.javatools.db.AbstractSchemaObject.checkInit(AbstractSchemaObject.java:144)
     at oracle.javatools.db.AbstractSchemaObject.checkInit(AbstractSchemaObject.java:267)
     at oracle.javatools.db.AbstractSchemaObject.copyToImpl(AbstractSchemaObject.java:64)
     at oracle.javatools.db.Table.copyTo(Table.java:81)
     at oracle.javatools.db.AbstractDBObject.copyTo(AbstractDBObject.java:90)
     at oracle.jdevimpl.offlinedb.transfer.OffToOffPolicy.copyForTransfer(OffToOffPolicy.java:192)
     at oracle.jdevimpl.offlinedb.transfer.OnToOffPolicy.copyForTransfer(OnToOffPolicy.java:134)
     at oracle.ide.db.transfer.TransferManager.prepare(TransferManager.java:158)
     at oracle.ide.db.transfer.TransferManager.prepareAndTransfer(TransferManager.java:418)
     at oracle.ideimpl.db.transfer.TransferRunnable.run(TransferRunnable.java:79)
     at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:643)
     at java.lang.Thread.run(Thread.java:619)

Hi nfk,
Are the tables in the question reference-partitioned?
I am able to reproduce the exception when copying to project the online reference partitioned tables to offline , and I have logged a bug for it.
Please give the details of the tables like partition type if your scenario is different.
As for the other issue , I have not seen any performance issues with DB diagram ..I have tried on jdk1.6.0_06 and jdk160_11.if it is reproducible, please add your machine configuration.
Many Thanks,
Geetha
Edited by: user647112 on May 15, 2009 5:19 AM

Jumpstart: Fdisk Partition Table Invalid

Hi,
I'm jumpstarting a Sun server with Solaris 10.
But during the jumpstart I received the next error:
Error: fdisk partition table invalid (c0t1d0)
Has someone an idea how I can fix this?

the previous jumpstart code would overwrite the entire disk.
what if i just want to fresh install (initial_install) the already existing Solaris partition.
The following jumpstart profile produce the same error message : "ERROR: fdisk partition table invalid" :
install_type initial_install
fdisk rootdisk solaris maxfree
pool root_pool auto 4g 4g rootdisk.s0
...Here is the console log :
Processing profile
        - Saving Boot Environment Configuration
        - Selecting cluster (SUNWCall)
       - Selecting geographic region (N_America)
        - Selecting geographic region (S_Europe)
        - Selecting geographic region (W_Europe)
        - Selecting geographic region (N_Europe)
        - Selecting geographic region (E_Europe)
        - Selecting geographic region (C_Europe)
        - Selecting all disks
        - Configuring boot device
        - Using disk (c1d0) for "rootdisk"
        - Creating "maxfree" Solaris fdisk partition (c1d0)
        - Using existing Solaris fdisk partition (c1d0)
ERROR: fdisk partition table invalid (c1d0)
ERROR: System installation failed
Solaris installation program exited.
...Note that fdisk is able to read the partitions :
fdisk -W - /dev/rdsk/c1d0p0
* /dev/rdsk/c1d0p0 default fdisk table
* Dimensions:
*    512 bytes/sector
*     63 sectors/track
*    255 tracks/cylinder
*   30400 cylinders
* systid:
* Id    Act Bhead Bsect Bcyl    Ehead Esect Ecyl    Rsect       Numsect
6     128 1         1        0         254      63      6        63            112392
7     0     0         1        7          254      63     1023    112455     102414375
191 0    254      63       1023    254      63     1023    102526830 102382245
15    0    254      63       1023    254     63      1023    204909075 283482990

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.

Error in creating partition table in oracle spatial by ankur

Hi,
Am working on Oracle 10.2.0.3
Am not able to create partition table in Oracle
i have all the required columns in node and edge table ......the moment i try to create partition table using exec sdo_router_partition.partion_router i get the following error:
ERROR at line 1:
ORA-00947: not enough values
ORA-06512: at "MDSYS.SDO_ROUTER_PARTITION", line 1510
ORA-06512: at "MDSYS.SDO_ROUTER_PARTITION", line 661
ORA-06512: at line 1
Can someone help ??

hey i have found the solution myself :)

"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?

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?

Error in import of partitioned table

I have one partitioned table in one schema after taking export when I am trying
to import in other database without having the same partition it is giving error
ora-00959 tablespace "PART_FY06' does not exists.
How to resolve it?

Yes oracle is saying tablespace PART_FY06 does not exist. Create this tablespace. Export and Import are logical. For logical operation to get success, physical entities like tablespaces should exist.

Unrecognized partition table for drive 80 error??

Currently running leopard on a macbook pro.
Formatted w bootcamp and running Windows Vista Ultimate.
Installation went fine reformated drive to ntfs 45gigs.
But when booting into windows I get this error message
"unrecognized partition table for drive 80"
Then the system boots into vista as normal but that error message is annoying.
Tells me to fix bootmgr using fdisk. How do I do that?
Thanks.

I previously had Vista installed under the beta with Tiger and there was no issues at all regarding boot times or error messages. (Boot times being quite nippy considering)
I did reformat the hard drive space partitioned in side Vista installation as NTFS. As I am only a switcher for a year or so I imagine there may be something I am missing but given the text when I try to boot into Vista, it looks to be the boot loader that is erroring and that looks the same as a GRUB loader failing.
I just do not get why a BETA product would work fine, then after a fresh installation of the new Mac OSX 10.5 with the final version of boot camp I would receive errors like this.
I have reclaimed the hard drive space and split the disk again but the same error persists. Previously I was showing off my Macbook to work mates showing how it handled Windows as well as the user friendly OSX. Now all I can show them is a 5 minute loading screen full of non booting Vista as they look at me like some kind of idiot. (Which depending on who you ask is possibly correct)

How to find partitioned tables whose loading may fail with ORA-14400 error

Hi,
We have several partitioned tables. Sometimes, when partitions are not created for that month, we get this error
ORA-14400 inserted partition key does not map to any partition
May I know if there is any script or sql which I can use to find out tables which may fail for loading if DBA won't create partitions in next 2 weeks?
Thank You
Sarayu K.S.

Sure, you can:
1.Look in DBA_TAB_PARTITIONS by partition_name if you use a particular naming convention, where owner = <your_owner> and table_name = <your_table_name> and partition_name = <your_expected_partition_name>
2. Without going by partition name, you could use dba_tab_partitions and instead check that there is a partition for your table with a high_value you are expecting to use. Be aware that the high_value is a long datatype, so you will likely need to convert it to a varchar2.
3. Before your big load, you could also insert one row into the destination table with the new partition key that will be used, and trap errors with an exception handler. Roll it back if it succeeds.
4. Many partitions could be created in advance to avoid the constant monitoring of new partitions.
5. Or you could also look into switching to interval partitioning if you are on 11g and get out of the business of having to create partitions manually.

Error: Windows Cannot Be Installed to This Disk. The Selected Disk Has an MBR Partition Table.

Error: Windows Cannot Be Installed to This Disk. The Selected Disk Has an MBR Partition Table.
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.
I found one solution to this problem on hp forum but my laptop has boot legacy and does not disable the efi boot order.
HP Model# HP 1000-1140TU Notebook PC
Serial# 5cg2481dbg
Product# c8c94pa#uuf
This is solution which is found on hp forum
SolutionThe resolution to this issue depends on the the hard disk volume size:
Follow these steps if the hard disk volume size is less than 2.19 TB:
Temporarily disable the EFI Boot Sources setting in the BIOS:
Restart the computer, and then press F10 to enter the BIOS.
Navigate to Storage > Boot Order , and then disable the EFI Boot Sources .
Select File > Save Changes > Exit .
Install the Windows operating system.
Enable the EFI Boot Sources setting in the BIOS:
Restart the computer, and then press F10 to enter the BIOS.
Navigate to Storage > Boot Order , and then enable the EFI Boot Sources .
Select File > Save Changes > Exit .
Follow these steps if the hard disk volume size is greater than 2.19 TB:
Install the HP BIOS Update UEFI utility from the HP Web site:
Click here to access the document "HP BIOS Update UEFI" .
NOTE:The HP BIOS Update UEFI utility is installed by default on some HP computers.
Follow the steps in the Microsoft document titled "How to Configure UEFI/GPT-Based Hard Drive Partitions" (in English) to create a GPT partition.
Click here to access the document "How to Configure UEFI/GPT-Based Hard Drive Partitions" .
NOTEne or more of the links above will take you outside the Hewlett-Packard Web site. HP does not control and is not responsible for information outside the HP Web site.

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?

Error in reading table TFK056A with interest key

While posting interest I am getting the following error "Error in reading table TFK056A with interest key". I have configured my interest keys well. Please assist.

Hi Panashesean,
The reason for this error could be you have in the line items an interest key (ikey) which is missing in table TFK056A. Though you have a different interest key in the master record the system will consider the line item first.
Interest Key Documentation states:
"If more than one interest key is defined for a line item, these interest keys are normally prioritized as follows:
1. Interest key in line item
2. Interest key that is defined for transactions identified as additional receivables
An interest can depend on the operative company code in the rule for
additional receivables.
3. Interest key in dunning level
4. Interest key in contract account master record"
You need to remove the interest key in the line item for the system to use the master record ikey OR or define (ikey) in table TFK056A.
I hope this works.
regards,
David

No more optical drive and windows 8 issue: "Windows cannot be installed on this disk as it has an MBR partition table."

I have an Early 2011 13" MBP going strong with an SSD and original HDD installed in the optical drive. However, having had success with windows 7 on my old HDD I was planning to install Windows 8.1 (from .iso) on my SSD. However, for the past day or so it's been a nightmare.
I tried the official procedure but by editing the bootcamp info.plist so I could boot from USB (you can't install windows from an external optical drive apparently) partitioning as bootcamp wanted too.
I then tried it a number of different ways using disk utility etc and with an empty space
However, I always seem to end up with the error "“Windows cannot be installed on this disk. The selected disk has an MBR partition table. On EFI systems, Windows can only installed on GPT disks“
I read some interesting stuff here http://www.royhochstenbach.com/installing-windows-8-1-on-a-2013-mac-pro/
He points out that
"Windows 7 and 8 in x64 support EFI. Normally if you install Windows on a Mac and use the installation DVD, it boots into regular BIOS mode, thus can be installed on an MBR partition. I tried the same, but since the Mac Pro doesn’t have an optical drive I had to use an external drive. And apparently the Mac boots external optical drives in EFI mode too. The Bootcamp wizard is aware of this, and creates a GPT partition on a non-superdrive Mac but an MBR partition on a superdrive Mac."
This means Bootcamp is essentially making the wrong type of partition?
My real question is? How do I install it windows 8? I'm really on my last legs!
I really don't want to have to open this thing up and reinsert my optical drive as its really really difficult to get out of the enclosure (would probably have to break it).
A huge thanks in advance!

Hi,
Have you tried that suggestion?
You also could use this commands to check and install again:
Inside windows installer, hit Shift+F10 to get a command prompt, then run diskpart and type List disk to displays a list of disks and information about them, such as their size, amount of available free space, whether the disk is a basic or dynamic disk,
and whether the disk uses the master boot record (MBR) or GUID partition table (GPT) partition style.
and then select the target disk. Zap the drive (with the clean command), create GPT table (new gpt), create the GPT-EFI special partitions.
Step-by-step instructions is here for reference:
HOW TO: Use the Diskpart.efi Utility to Create a GUID Partition Table Partition on a Raw Disk in Windows
http://support.microsoft.com/kb/297800?wa=wsignin1.0
Then reboot so the firmware finds those partitions and adds the disk to the EFI-native boot order (Windows installer checks this).
Karen Hu
TechNet Community Support

Issue with updating partitioned table

Hi,
Anyone seen this bug with updating partitioned tables.
Its very esoteric - its occurs when we update a partitioned table using a join to a temp table (not non-temp table) when the join has multiple joins and you're updating the partitoned column that isn't the first column in the primary key and the table contains a bit field. We've tried changing just one of these features and the bug disappears.
We've tested this on 15.5 and 15.7 SP122 and the error occurs in both of them.
Here's the test case - it does the same operation of a partitioned table and a non-partitioned table, but the partitioned table shows and error of "Attempt to insert duplicate key row in object 'partitioned' with unique index 'pk'".
I'd be interested if anyone has seen this and has a version of Sybase without the issue.
Unfortunately when it happens on a replicated table - it takes down rep server.
CREATE TABLE #table1
    (   PK          char(8) null,
        FileDate        date,
        changed         bit
CREATE TABLE partitioned (
PK         char(8) NOT NULL,
ValidFrom     date DEFAULT current_date() NOT NULL,
ValidTo       date DEFAULT '31-Dec-9999' NOT NULL
LOCK DATAROWS
PARTITION BY RANGE (ValidTo)
( p2014 VALUES <= ('20141231') ON [default],
p2015 VALUES <= ('20151231') ON [default],
pMAX VALUES <= (MAX) ON [default]
CREATE UNIQUE CLUSTERED INDEX pk
ON partitioned(PK, ValidFrom, ValidTo)
LOCAL INDEX
CREATE TABLE unpartitioned (
PK         char(8) NOT NULL,
ValidFrom     date DEFAULT current_date() NOT NULL,
ValidTo       date DEFAULT '31-Dec-9999' NOT NULL,
LOCK DATAROWS
CREATE UNIQUE CLUSTERED INDEX pk
ON unpartitioned(PK, ValidFrom, ValidTo)
insert partitioned
select "ET00jPzh", "Jan 7 2015", "Dec 31 9999"
insert unpartitioned
select "ET00jPzh", "Jan 7 2015", "Dec 31 9999"
insert #table1
select "ET00jPzh", "Jan 15 2015", 1
union all
select "ET00jPzh", "Jan 15 2015", 1
go
update partitioned
set    ValidTo = dateadd(dd,-1,FileDate)
from   #table1 t
inner join partitioned p on (p.PK = t.PK)
where p.ValidTo = '99991231'
and    t.changed = 1
go
update unpartitioned
set    ValidTo = dateadd(dd,-1,FileDate)
from   #table1 t
inner join unpartitioned u on (u.PK = t.PK)
where u.ValidTo = '99991231'
and    t.changed = 1
go
drop table #table1
go
drop table partitioned
drop table unpartitioned
go

wrt to replication - it is a bit unclear as not enough information has been stated to point out what happened. I also am not sure that your DBA's are accurately telling you what happened - and may have made the problem worse by not knowing themselves what to do - e.g. 'losing' the log points to fact that someone doesn't know what they should.   You can *always* disable the replication secondary truncation point and resync a standby system, so claims about 'losing' the log are a bit strange to be making.
wrt to ASE versions, I suspect if there are any differences, it may have to do with endian-ness and not the version of ASE itself.   There may be other factors.....but I would suggest the best thing would be to open a separate message/case on it.
Adaptive Server Enterprise/15.7/EBF 23010 SMP SP130 /P/X64/Windows Server/ase157sp13x/3819/64-bit/OPT/Fri Aug 22 22:28:21 2014:
-- testing with tinyint
1> use demo_db
1>
2> CREATE TABLE #table1
3>     (   PK          char(8) null,
4>         FileDate        date,
5> --        changed         bit
6> changed tinyint
7>     )
8>
9> CREATE TABLE partitioned (
10>   PK         char(8) NOT NULL,
11>   ValidFrom     date DEFAULT current_date() NOT NULL,
12>   ValidTo       date DEFAULT '31-Dec-9999' NOT NULL
13>   )
14>
15> LOCK DATAROWS
16>   PARTITION BY RANGE (ValidTo)
17>   ( p2014 VALUES <= ('20141231') ON [default],
18>   p2015 VALUES <= ('20151231') ON [default],
19>   pMAX VALUES <= (MAX) ON [default]
20>         )
21>
22> CREATE UNIQUE CLUSTERED INDEX pk
23>   ON partitioned(PK, ValidFrom, ValidTo)
24>   LOCAL INDEX
25>
26> CREATE TABLE unpartitioned (
27>   PK         char(8) NOT NULL,
28>   ValidFrom     date DEFAULT current_date() NOT NULL,
29>   ValidTo       date DEFAULT '31-Dec-9999' NOT NULL,
30>   )
31> LOCK DATAROWS
32>
33> CREATE UNIQUE CLUSTERED INDEX pk
34>   ON unpartitioned(PK, ValidFrom, ValidTo)
35>
36> insert partitioned
37> select "ET00jPzh", "Jan 7 2015", "Dec 31 9999"
38>
39> insert unpartitioned
40> select "ET00jPzh", "Jan 7 2015", "Dec 31 9999"
41>
42> insert #table1
43> select "ET00jPzh", "Jan 15 2015", 1
44> union all
45> select "ET00jPzh", "Jan 15 2015", 1
(1 row affected)
(1 row affected)
(2 rows affected)
1>
2> update partitioned
3> set    ValidTo = dateadd(dd,-1,FileDate)
4> from   #table1 t
5> inner join partitioned p on (p.PK = t.PK)
6> where p.ValidTo = '99991231'
7> and    t.changed = 1
Msg 2601, Level 14, State 6:
Server 'PHILLY_ASE', Line 2:
Attempt to insert duplicate key row in object 'partitioned' with unique index 'pk'
Command has been aborted.
(0 rows affected)
1>
2> update unpartitioned
3> set    ValidTo = dateadd(dd,-1,FileDate)
4> from   #table1 t
5> inner join unpartitioned u on (u.PK = t.PK)
6> where u.ValidTo = '99991231'
7> and    t.changed = 1
(1 row affected)
1>
2> drop table #table1
1>
2> drop table partitioned
3> drop table unpartitioned
-- duplicating with 'int'
1> use demo_db
1>
2> CREATE TABLE #table1
3>     (   PK          char(8) null,
4>         FileDate        date,
5> --        changed         bit
6> changed int
7>     )
8>
9> CREATE TABLE partitioned (
10>   PK         char(8) NOT NULL,
11>   ValidFrom     date DEFAULT current_date() NOT NULL,
12>   ValidTo       date DEFAULT '31-Dec-9999' NOT NULL
13>   )
14>
15> LOCK DATAROWS
16>   PARTITION BY RANGE (ValidTo)
17>   ( p2014 VALUES <= ('20141231') ON [default],
18>   p2015 VALUES <= ('20151231') ON [default],
19>   pMAX VALUES <= (MAX) ON [default]
20>         )
21>
22> CREATE UNIQUE CLUSTERED INDEX pk
23>   ON partitioned(PK, ValidFrom, ValidTo)
24>   LOCAL INDEX
25>
26> CREATE TABLE unpartitioned (
27>   PK         char(8) NOT NULL,
28>   ValidFrom     date DEFAULT current_date() NOT NULL,
29>   ValidTo       date DEFAULT '31-Dec-9999' NOT NULL,
30>   )
31> LOCK DATAROWS
32>
33> CREATE UNIQUE CLUSTERED INDEX pk
34>   ON unpartitioned(PK, ValidFrom, ValidTo)
35>
36> insert partitioned
37> select "ET00jPzh", "Jan 7 2015", "Dec 31 9999"
38>
39> insert unpartitioned
40> select "ET00jPzh", "Jan 7 2015", "Dec 31 9999"
41>
42> insert #table1
43> select "ET00jPzh", "Jan 15 2015", 1
44> union all
45> select "ET00jPzh", "Jan 15 2015", 1
(1 row affected)
(1 row affected)
(2 rows affected)
1>
2> update partitioned
3> set    ValidTo = dateadd(dd,-1,FileDate)
4> from   #table1 t
5> inner join partitioned p on (p.PK = t.PK)
6> where p.ValidTo = '99991231'
7> and    t.changed = 1
Msg 2601, Level 14, State 6:
Server 'PHILLY_ASE', Line 2:
Attempt to insert duplicate key row in object 'partitioned' with unique index 'pk'
Command has been aborted.
(0 rows affected)
1>
2> update unpartitioned
3> set    ValidTo = dateadd(dd,-1,FileDate)
4> from   #table1 t
5> inner join unpartitioned u on (u.PK = t.PK)
6> where u.ValidTo = '99991231'
7> and    t.changed = 1
(1 row affected)
1>
2> drop table #table1
1>
2> drop table partitioned
3> drop table unpartitioned

Local index vs global index in partitioned tables

Hi,
I want to know the differences between a global and a local index.
I'm working with partitioned tables about 10 millons rows and 40 partitions.
I know that when your table is partitioned and your index non-partitioned is possible that
some database operations make your index unusable and you have tu rebuid it, for example
when yo truncate a partition your global index results unusable, is there any other operation
that make the global index unusable??
I think that the advantage of a global index is that takes less space than a local and is easier to rebuild,
and the advantage of a local index is that is more effective resolving a query isn't it???
Any advice and help about local vs global index in partitioned tables will be greatly apreciatted.
Thanks in advance

here is the documentation -> http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14220/partconc.htm#sthref2570
In general, you should use global indexes for OLTP applications and local indexes for data warehousing or DSS applications. Also, whenever possible, you should try to use local indexes because they are easier to manage. When deciding what kind of partitioned index to use, you should consider the following guidelines in order:
1. If the table partitioning column is a subset of the index keys, use a local index. If this is the case, you are finished. If this is not the case, continue to guideline 2.
2. If the index is unique, use a global index. If this is the case, you are finished. If this is not the case, continue to guideline 3.
3. If your priority is manageability, use a local index. If this is the case, you are finished. If this is not the case, continue to guideline 4.
4. If the application is an OLTP one and users need quick response times, use a global index. If the application is a DSS one and users are more interested in throughput, use a local index.
Kind regards,
Tonguç

An interesting error: "recursive partition table"

Similar Messages

Maybe you are looking for