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)

Similar Messages

How's this partition table for my server?

How's this partition table for my server? Web/DNS/DHCP/Mail Server.
hdd1: ~8gb total
/boot - 100mb
swap - 1gb
/ - rest of drive
hdd2: ~155gb total
/var - whole drive
This is a Compaq ProLiant 5500 server with 10 drives. Will most things be installed inside /var or what?

Zetsumei wrote:Web/DNS/DHCP/Mail Server.
Web = /srv
DNS = /var
DHCP = /var
Mail = Depends which package you use. I use postfix and told it to use /srv
I would half your swap, reduce /var and put the extra space into /srv
Also create a separate /tmp and /home to prevent accidental or deliberate DoS attacks by filling your / partition
Here's what I use on my Web / DNS / FTP server:
Filesystem Size Used Avail Use% Mounted on
/dev/xvda 493M 176M 317M 36% /
/dev/xvdc 31M 674K 29M 3% /boot
/dev/lvmData-home 62M 26M 34M 44% /home
/dev/lvmData-usr 2.0G 848M 1.1G 45% /usr
/dev/lvmData-tmp 496M 20M 451M 5% /tmp
/dev/lvmData-srv 1.5G 769M 667M 54% /srv
/dev/lvmData-var 496M 231M 241M 49% /var
/dev/lvmData-pacman 384M 303M 82M 79% /var/cache/pacman
/dev/lvmData-backup 5.5G 4.6G 565M 90% /mnt/backup

Use global temp table for DML error logging

our database is 11.2.0.4 enterprise edition on solaris 10
we are wondering if anyone has an opinion of or has done this before, to use a global temp table for DML error logging. We have a fairly busy transactional database with 2 hot tables for inserts. The regular error table created with dbms_errlog has caused many deadlocks which we don't quite understand yet. we have thought using global temp table for the purpose, and that seemed to work, but we can't read error from the GTT, the table is empty even reading from the same session as inserts. Does anyone have an idea why?
Thanks

The insert into the error logging table is done with a recursive transaction therefore it's private from your session which is doing the actual insert.
Adapted from http://oracle-base.com/articles/10g/dml-error-logging-10gr2.php
INSERT INTO dest
SELECT *
FROM source
LOG ERRORS INTO err$_dest ('INSERT') REJECT LIMIT UNLIMITED;
99,998 rows inserted.
select count(*) from dest;
COUNT(*)
    99998
SELECT *
FROM err$_dest
WHERE ora_err_tag$ = 'INSERT';
1400    "ORA-01400: cannot insert NULL into ("E668983_DBA"."DEST"."CODE")"        I    INSERT    1000        Description for 1000
1400    "ORA-01400: cannot insert NULL into ("E668983_DBA"."DEST"."CODE")"        I    INSERT    10000        Description for 10000
1400    "ORA-01400: cannot insert NULL into ("E668983_DBA"."DEST"."CODE")"        I    INSERT    1000        Description for 1000
1400    "ORA-01400: cannot insert NULL into ("E668983_DBA"."DEST"."CODE")"        I    INSERT    10000        Description for 10000
rollback;
select count(*) from dest;
COUNT(*)
        0
SELECT *
FROM err$_dest
WHERE ora_err_tag$ = 'INSERT';
1400    "ORA-01400: cannot insert NULL into ("E668983_DBA"."DEST"."CODE")"        I    INSERT    1000        Description for 1000
1400    "ORA-01400: cannot insert NULL into ("E668983_DBA"."DEST"."CODE")"        I    INSERT    10000        Description for 10000
1400    "ORA-01400: cannot insert NULL into ("E668983_DBA"."DEST"."CODE")"        I    INSERT    1000        Description for 1000
1400    "ORA-01400: cannot insert NULL into ("E668983_DBA"."DEST"."CODE")"        I    INSERT    10000        Description for 10000

[SOLVED] Deleted partition table on drive, how to rescue?

Hello,
I accidentally dd'd the first 512 bytes using:
dd if=/dev/zero of=/dev/sdb bs=512 count=1
and the partition table is now gone. Is there ANY way to re-create the partition table and rescue the still existing partition? I read up on parted's manual, and found the following commands:
mklabel - to create a new label on the disk (but does it also create a new partition table?)
rescue - to try and rescue the partition around the given START and END
My hard drive is 500GB and has only 1 partition on it, in NTFS file format.
Any help would be much appreciated.
Silentz0r
Last edited by silentz0r (2011-03-27 16:17:36)

Thanks everyone for your help, I have managed to solve this. Here's what I did:
(I had no backup of the MBR)
I used:
parted /dev/sdb
sdb was my broken drive, and did the following:
(parted) print
Error: /dev/sdb: unrecognised disk label
(parted) mklabel
(parted) mklabel msdos
(parted) rescue
Start? 0
End? 976773168 // This was just a random guess.
Information: A ntfs primary partition was found at 32.3kB -> 500GB. Do you want to add it to the partition table?
Yes/No/Cancel? yes
(parted) quit
Information: You may need to update /etc/fstab.
And everything works now.
For the record, I am making MBR backups for all my drives while I'm typing this.
Hope this helps someone in the future! Marked as solved.

FAT32 Partitions on GUID Partition Table External Drive Not Seen in Vista

I have an interesting predicament. I have repartitioned my external hard drive to have 5 partitions: 2 HFS+ and 3 FAT32. The external drive has a GUID Partition Table. The drive was formatted and partitioned using Disk Utility.
When I boot into Windows Vista using Boot Camp, Vista will ONLY mount the first Windows compatible partition. For example, if I have two partitions disk2s2 and disk2s3 (both FAT32), Vista only mounts disk2s2.
The described partition setup worked well with Master Boot Record, minus the bug with Time Machine choking every so often.
Any ideas on how I can get Vista to recognize these partitions?

Hi Karl87,
according to the german computer magazine c't there is a limitation/flaw in the Master Boot Record (MBR:
Only the first four partitions are shown in the MBR and since one of these entrys is taken by the needed hidden EFI-partition and the next two entrys are taken by the OSX partition, there is only one of your three FAT partitions shown.
This limitation to four partition entries is quite old.
See here for further informations: http://en.wikipedia.org/wiki/Masterbootrecord
To my knowledge there is no solution for this.
Regards
Stefan

Unknown type TABLE for element Error

This question i am posting on behalf of one of my friend
In RF transaction, created a screen that contains table control. The table control has created using wizard
If we run the transaction with in SAPGui its working fine. After creating Internet service, and publish and run thru internet explorer its giving the following said Error
" Unknow type TABLE for element IT_PRODUCT"
I checked the controls statement for table view , its there in the code Here IT_PRODUCT is tableview for tablecontrol
Any Info ?
a®

Solved.
The problem is because , the table control had been created thru "Table Control Wizard" , solved by creating the table control using SE51 has resolved the issue.
Strange ?
May be because wizard unncessary creating lot of HTML code while publishing
a®

Table for COFC error messages

Hi,
There are 1000+ orders are in error when we check thru COFC . As it's a tedious job to check error message for each error record, Is there any table to get error text messages for all error records?
Thanks in advance
Murali

Hi,
what you see in COFC is nothing else than the AFRC.table entries. Nevertheless the message itself is not stored in AFRC itself.
Process COFC-records by marking all of them and tick "save", the ones that can be posted nor are posted only the "real" errors remain.
You can schedule a job running CORUPROC report, to do this automatically.
Best regrads, Christian

[SOLVED] The best partition table for Archlinux?

Hi.
I am very confused whit the partition table which I sould use.
So, which partition table is the best? Which you use?
Have a nice day
Last edited by feler (2008-10-19 10:41:20)

I am a fan of reiserfs so I use it for everything except boot (where I use ext2).
I strongly advice you to use ReiserFS for your /var/ because it is the fastest when dealing with small files, which greatly improves pacman performance.
For everything else - it depends on what type of files does your system mostly hold...

Vista, unrecognized partition table use fdisk to fix?

I have a NTFS Vista partition and when I boot into it I get a lot of white type on black screens telling me there is an unknown partition located and to use fdisk to fix.
Vista comes up and works fine but I'd like to get rid of those screens.
Any ideas appreciated ...
Thanks ... Ken

Two yrs going back to RC1 in Oct '06 and I've never seen, nor do I have any idea, what you did or have, and whether you have altered or touched the GPT or EFI partitions or USB device.
And I've got 4 internal NTFS drives, most with two partitions, some flash devices, FireWire 800, along with native SATA external.
And never even seen fdisk mentioned.
Maybe you should click on properties and schedule chkdsk for every partition you can and look in Computer -> Manage.

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

Create a GPT partition table and format with a large volume (solved)

Hello,
I'm having trouble creating a GPT partition table for a large volume (~6T). It is a RAID 5 (hardware) with 3 hard disk drives having a size of 3T each (thus the resulting 6T volume).
I tried creating a GPT partition table with gdisk but it just fails at creating it, stopping here (I've let it run for like 3 hours...):
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/md126.
I also tried with parted but I get the same result. Out of luck, I created a GPT partition table from Windows 7 and 2 NTFS partitions (15G and the rest of space for the other) and it worked just fine. I then tried to format the 15G partition as ext4 but, as for gdisk, mkfs.ext4 will just never stop.
Some information:
fdisk -l
Disk /dev/sda: 256.1 GB, 256060514304 bytes, 500118192 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 label type: dos
Disk identifier: 0xd9a6c0f5
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 104861695 52429824 83 Linux
/dev/sda2 104861696 466567167 180852736 83 Linux
/dev/sda3 466567168 500117503 16775168 82 Linux swap / Solaris
Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.
Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: dos
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdd1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.
Disk /dev/sde: 320.1 GB, 320072933376 bytes, 625142448 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 label type: dos
Disk identifier: 0x5ffb31fc
Device Boot Start End Blocks Id System
/dev/sde1 * 2048 625139711 312568832 7 HPFS/NTFS/exFAT
Disk /dev/md126: 6001.1 GB, 6001143054336 bytes, 11720982528 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes
Disk label type: dos
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/md126p1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.
WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.
gdisk -l on my RAID volume (/dev/md126):
GPT fdisk (gdisk) version 0.8.7
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/md126: 11720982528 sectors, 5.5 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 8E7D03F1-8C3A-4FE6-B7BA-502D168E87D1
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 11720982494
Partitions will be aligned on 8-sector boundaries
Total free space is 6077 sectors (3.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 34 262177 128.0 MiB 0C01 Microsoft reserved part
2 264192 33032191 15.6 GiB 0700 Basic data partition
3 33032192 11720978431 5.4 TiB 0700 Basic data partition
To make things clear: sda is an SSD on which Archlinux has been freshly installed (sda1 for root, sda2 for home, sda3 for swap), sde is a hard disk drive having Windows 7 installed on it. My goal with the 15G partition is to format it so I can mount /var on the HDD rather than on the SSD. The large volume will be for storage.
So if anyone has any suggestion that would help me out with this, I'd be glad to read.
Cheers
Last edited by Rolinh (2013-08-16 11:16:21)

Well, I finally decided to use a software RAID as I will not share this partition with Windows anyway and it seems a better choice than the fake RAID.
Therefore, I used the mdadm utility to create my RAID 5:
# mdadm --create --verbose /dev/md0 --level=5 --raid-devices=3 /dev/sdb1 /dev/sdc1 /dev/sdd1
# mkfs.ext4 -v -m .1 -b 4096 -E stride=32,stripe-width=64 /dev/md0
It works like a charm.

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

Booting os x from *partitioned* external firewire drive?

Hi all,
my internal hard disk (on a 12" powerbook G4 867 mhz running osx tiger 10.4.10) has started acting weird (many people are reporting failing hard drives, and I'm assuming mine is failing too), so I'm preparing for replacing it with a new hard drive.
I've backed up the drive to an external firewire drive (LaCie portable 80 GB firewire drive "Design by F.A. Porsche") using Carbon Copy Cloner with the option 'make bootable' selected.
PROBLEM: I can't boot OS X using my clone on the external drive.
I'VE TRIED:
1. holding down Command-Option-Shift-Delete while booting to bypass the internal drive. (This didn't work: I saw an os 9 icon blinking/alternating with a question mark for a while, and then the computer booted from the internal hard disk.)
2. holding down Option to select the external drive in Startup Manager. (Didn't work either: Startup Manager opened fine, but only showed my internal drive volume. I tried clicking the 'rescan' button, but it couldn't find my external drive.)
3. SELECTING THE EXTERNAL DRIVE under Startup Disk in System Preferences. Note that the external drive volume *did show up* there. So under some conditions at least, the external volume is identified as a bootable volume. (This didn't work either, though: When I shut down the computer and booted up with the external drive connected, it still booted up from the internal drive.)
POSSIBLE EXPLANATION?
My external drive is partitioned into three partitions of different formats:
1. "Mac OS X Extended (Journaled)"
2. "Mac OS X Extended (Journaled)"
3. "MS-DOS File System (FAT32)"
The bootable volume is the first partition with the os x format.
Could my problem be caused by this partitioning of my external drive?
Either way, what to do?? I hope some of you savvy people out there can help me out.
Cheers,
Philip

Hi Philip,
My problem has been fixed, & I imagine it's the same for you...:
With the excellent help from Dave Nanian at shirtpocket.com - the developer of 'SuperDuper!' (thanks Dave - you rock!), the problem (as Michael suggested) is to do with the Partition Scheme of the drive.
If your drive was like my portable LaCie Porsche drive, it was FAT32-formatted for PC out of the box. This format has an underlying MBR (master boot record) partition-scheme. When re-partitioning a drive in 'Disk Utility', the original partition-scheme sticks, so if you simply re-partition the drive to Mac OS Extended, it will still have an MBR partition scheme... which Macs cannot boot from!
For a Power PC Mac to be able to boot from an external firewire drive, the drive MUST have an APM (Apple Partition Map) Partition Scheme underlying the Mac OS Extended partitions. To do this, click on the 'Options' button in 'Disk Utility' when on the 'Partition' page before partitioning. You will see the options:
GUID Partition Table (for Intel Macs... (n.b. Power PC's cannot boot from a GPT drive))
Apple Partition Map (to create a bootable drive for a Power PC Mac)
Master Boot Record (to create a bootable PC drive)
So.... to make your external drive bootable for your Powerbook G4, choose 'Apple Partition Map' in the 'Options' page prior to partitioning.
Special note about Intel Macs: Contrary to info supplied by Apple, an Intel Mac CAN boot from an APM-partitioned drive (this is why the OSX installer can be univerally bootable!), BUT, the problem is that the OSX installer will NOT let you install OSX-intel on an APM-partitioned drive....
You can, however, clone an Intel-Mac-OSX internal drive that has a GPT partition-scheme (using CCC or SuperDuper) to an external drive with APM, & the Intel Mac will still be able to boot from that clone...
The only real use for doing this, though, is if you want a multi-partitioned backup drive with separate bootable partitions for OSX-PPC & OSX-Intel machines. (Remember that a PPC machine cannot boot from a GTP-partion-scheme drive, hence the need to use APM in this instance seeing as the Partition Scheme applies to the entire drive (it can't be different for each partition.)
Good luck - let us know how you get on!
Jason

[SOLVED] RAID0 Array - Unknown Partition Table

I recently reinstalled my Arch system with a RAID0 array, and I've noticed something different this time around during boot.
When the mdadm hook is initialized it will stop the array, check it, then start it. Once it's started it will say,
md0: unknown partition table
And continue to the next array.
I believe this is fine since the system doesn't stall or anything during bootup. The concern I have is when the system then tries to activate the RAID arrays. It will show,
Activating RAID Arrays [FAIL]
I've looked this up, http://bbs.archlinux.org/viewtopic.php?id=90415 and apparently it's nothing to be worried about. However, it didn't do that when I had my system installed not 20 minutes before (up to date).
I've created the mdadm configuration file as such,
rm /mnt/etc/mdadm.conf
mdadm --examine --scan >> /mnt/etc/mdadm.conf
Apparently, this message can be removed so it doesn't show fail on startup by commenting out the part in /etc/rc.sysinit where it assembles the RAID, lines 121-123. I'm still uneasy with it though, I'm just looking for some further insight on this subject.
Why doesn't my md0 device have a partition table and what is the system doing that causes the assembly to fail?
Edit - It might be important to note that I'm trying to make 3 partitions of the following size,
/ 10GB
/home ~4TB
/boot 50MB
Thanks!
Last edited by nerditup (2010-06-14 04:39:35)

Update: This behaviour is normal.
The partition table for a RAID array is not specified anywhere because the partition table is setup on the actual devices. In my case I have two partition tables set on /dev/sda and /dev/sdb, therefore /dev/md0 doesn't need any partition table.
The code,
#If necessary, find md devices and manually assemble RAID arrays
if [ -f /etc/mdadm.conf -a "$(/bin/grep ^ARRAY /etc/mdadm.conf 2>/dev/null)" ];
then
status "Activating RAID arrays" /sbin/mdadm --assemble --scan
fi
will check mdadm.conf for any arrays that are setup and try to assemble them. Since the arrays are assembled already by the mdadm hook, then the --assemble parameter will return an error. This is the reason for the [FAIL] message.
Since this is understood and not an actual "error", it is safe to comment out these lines in rc.sysinit. In fact, these lines are useless and should be taken out completely.
The reason why it didn't show up last time was because I didn't properly setup my mdadm.conf file on the previous install. This process made sure they were loaded, but if you follow the wiki and properly setup the mdadm.conf file then you don't need this line of code at all in your rc.sysinit.
Last edited by nerditup (2010-06-14 04:39:21)

Insert statement does not insert all records from a partitioned table

Hi
I need to insert records in to a table from a partitioned table.I set up a job and to my surprise i found that the insert statement is not inserting all the records on the partitioned table.
for example when i am using select statement on to a partitioned table
it gives me 400 records but when i insert it gives me only 100 records.
can anyone help in this matter.

INSERT INTO TABLENAME(COLUMNS)
(SELECT *
FROM SCHEMA1.TABLENAME1
JOIN SCHEMA2.TABLENAME2a
ON CONDITION
JOIN SCHEMA2.TABLENAME2 b
ON CONDITION AND CONDITION
WHERE CONDITION
AND CONDITION
AND CONDITION
AND CONDITION
AND (CONDITION
HAVING SUM(COLUMN) > 0
GROUP BY COLUMNS

Unrecognized partition table for drive 80 error??

Similar Messages

Maybe you are looking for