Size of partition table...

ok, I'm under the impression that the partition table is at the very beginning of an SSD/HDD sector 0, byte 0, etc.... exactly how big IS the actual partition table?
if I placed this question in the wrong category, mods feel free to move it...

CPUnltd wrote:
ok, so the MBR holds the partition table (and the MBR is the first 512B of the disk... correct?
just wanna make sure, because I'm planning to test a theory...
Correct. The actual partition table doesn't start until the 446th byte

Similar Messages

Displaying the sizes of every table in a database

Hello All,
I need to get the table sizes for each and every table in a database.
I would have checked it manually but there are many number of tables.
I am using SQL Server 2008 R2.
Thanks and Regards, Readers please vote for my posts if the questions i asked are helpful.

Hi,
Please make habit of searching net before posting or if you dont know how to write a query. A simple search would lead you to
http://stackoverflow.com/questions/7892334/get-size-of-all-tables-in-database
SELECT
t.NAME AS TableName,
s.Name AS SchemaName,
p.rows AS RowCounts,
SUM(a.total_pages) * 8 AS TotalSpaceKB,
SUM(a.used_pages) * 8 AS UsedSpaceKB,
(SUM(a.total_pages) - SUM(a.used_pages)) * 8 AS UnusedSpaceKB
FROM
sys.tables t
INNER JOIN
sys.indexes i ON t.OBJECT_ID = i.object_id
INNER JOIN
sys.partitions p ON i.object_id = p.OBJECT_ID AND i.index_id = p.index_id
INNER JOIN
sys.allocation_units a ON p.partition_id = a.container_id
LEFT OUTER JOIN
sys.schemas s ON t.schema_id = s.schema_id
WHERE
t.NAME NOT LIKE 'dt%'
AND t.is_ms_shipped = 0
AND i.OBJECT_ID > 255
GROUP BY
t.Name, s.Name, p.Rows
ORDER BY
t.Name
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

How can I create my own tag name while creating a partition table.

I have X4500 running Solaris 10. I have formatted a disk and created partition table as given below.
Specify disk (enter its number): 0
selecting c0t0d0
[disk formatted]
/dev/dsk/c0t0d0s0 is part of active ZFS pool zpool1. Please see zpool(1M).
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
fdisk - run the fdisk program
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> partition
PARTITION MENU:
0 - change `0' partition
1 - change `1' partition
2 - change `2' partition
3 - change `3' partition
4 - change `4' partition
5 - change `5' partition
6 - change `6' partition
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the disk
!<cmd> - execute <cmd>, then return
quit
partition> print
Current partition table (original):
Total disk sectors available: 1953508749 + 16384 (reserved sectors)
Part Tag Flag First Sector Size Last Sector
0 usr wm 34 4.00GB 8388641
1 usr wm 8388642 2.00GB 12582945
2 usr wm 12582946 200.00GB 432013345
3 usr wm 432013346 175.00GB 799014945
4 usr wm 1166180386 375.43GB 1953508748
5 usr wm 799014946 175.00GB 1166016545
6 usr wm 1166016546 80.00MB 1166180385
8 reserved wm 1953508749 8.00MB 1953525132
partition>
I am unable to specify my own tag name. How can I change the tag name to one of my interest.
I need to create 3 partitions as told below
partitions:
/earth
/mars
/work
/earth and /work should be roughly equal in size, /mars should be twice the size of the others, if that is possible. If not 3 partitions of equal size will do.
Please, help me .
Thank you.

Exactly 1TB? Slightly under/slightly over?
Traditional Solaris disk labels are in VTOC format, but this format cannot describe disks larger than 1TB. So EFI labels must be used on disks larger than 1TB. Setup is slightly different.
Are these physical disks or LUNs from a SAN array? If they are array LUNS, it is often the case that they don't have a Sun label of any type. So...
#1 Apply a Solaris label
If the LUNS don't have a label (when selected in 'format', it gives a warning that no label is present and offers to apply a label immediately). When run non-interactively, format assumes "yes" for any questions. So all you'd have to do is select every disk to have it apply labels to any unlabled disk. Run 'format' once and find the highest number (maybe it's 50 for you). Create a text file that looks like this:
disk 1
disk 2
disk 3
disk 50Then feed that to format like this:
# format -f /tmp/disklist or whatever you've named the file.
#2 Apply the partition layout to all disks you want.
You asked if you should do the same procedure, but I don't see that you've actually done anything above other than print out the existing layout. Take one of your 48 drives and partition it the way you want manually (set the slices to the sizes that you want). Then you can copy the layout of that disk to others. You only want to do this between disks/LUNs of the same size. As an example, if you've explicitly partitioned c1t0d0 and you want to apply this to c1t1d0, do this:
# prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t1d0s2Repeat for all of your other disks.
Darren

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.

Can I use gpt to recreate/unerase a partition table? (Rebuild the GPT/GUID partition table?) I don't want to do FILE recovery.

(Yes, I've googled a bunch and read threads like this one already.)
Can I use gpt or some other app to recreate/unerase a partition table? That is, how can I rebuild a disk's GPT/GUID partition table?) I don't want to do FILE recovery.
What happened: Instead of erasing a single partition off a disk with many partitions, the entire partition table was erased (using Disk Utility, w/o deleting the underlying files). Somehow the "Erasing a disk deletes all data on all its partitions." warning message was missed.
I have a copy of the output of df, with the number of blocks in each partition, from just prior to the erasure, so I should be able to recreate the GPT/GUID partition table. Editing the GPT with a hex editor is not feasible. Simply recreating the partitions with Disk Utility will overwrite the key filesystem tables on each partition, and I don't want to do that, plus Disk Utility doesn't allow me to specify exact partition sizes anyway.
Surely there's an app for rebuilding the partition table (other than emacs' hexl-mode!) for recreating/unerasing a partition table when the partition sizes and orders are known? I've looked at the advertising for a bunch of recovery software and none of them clearly indicate that they will do what I want.
I guess I can try using gpt on a copy of the reformatted drive I've made with dd, and see what happens. But perhaps someone knows of a tool that should do what I need, or knows if gpt is that tool or not.
There are answers and tools that will do FILE recovery - search for files and recover the ones that aren't fragmented or deleted. As far as I can find, they just look for files on the disk, and don't pay much, if any attention to the filesystem info or directory heirarchy, which in this case is valuable. Of course I could send it in to DriveSavers, or the like. But none of that seems necessary, and the scavenging file recovery apps won't do the job well,
E.g. some are mentioned here:
I don't want to do FILE recovery.
Thanks for any help.
The links in this post are to pages describing the underlined term, e.g. the man pages for df and gpt.
dd output includes:
Filesystem
512-blocks
Used Available Capacity Mounted on

Aperture has the ability to work with files in their existing location. They are called "referenced masters." When you import images, you should select the "In their current location" in the "Store Files:" drop down box. Have a read of the documentation for full specifics. Unsure how you can resolve your duplication; might be some work but next time have a read of the manual first
Information for versions is stored in the Aperture database (library file). The masters can be inside the library file itself, or they can be somewhere else.

How to find out the Non Partitioned Tables used 2Gb on oracle

Hi team
how to find out the Non Partitioned Tables used > 2Gb on oracle where not is sys & system
regards

heres 1 I made earlier
set pagesize 999
set linesize 132
col owner format a25
col segment_name format a60
select owner,segment_name,segment_type,(bytes/1024/1024)"MB size"
from dba_segments
where owner not in ('SYS','SYSTEM','XDB','MDSYS','SYSMAN') -- edit for taste
and segment_type = 'TABLE'
having (bytes/1024/1024) > 2000
group by bytes, segment_Type, segment_name, owner
order by 4 asc

Creating index on large partitioned table

Is anyone aware of a method for telling how far along is the creation of an index on a large partitioned table? The statement I am executing is like this:
CREATE INDEX "owner"."new_index"
ON "owner"."mytable"(col_1, col_2, col_3, col_4)
PARALLEL 8 NOLOGGING ONLINE LOCAL;
This is a two-node RAC system on Windows 2003 x64, using ASM. There are more than 500,000,000 rows in the table, and I'd estimate that each row is about 600-1000 bytes in size.
Thank you.

you can know the progress from v$session_longops.
select
substr(SID ||','||SERIAL# ,1,8) "sid,srl#",
substr(OPNAME ||'>'||TARGET,1,50) op_target,
substr(trunc(SOFAR/TOTALWORK*100)||'%',1,5) progress,
TIME_REMAINING rem,
ELAPSED_SECONDS elapsed
from v$session_longops
where SOFAR!=TOTALWORK
order by sid;
hth

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

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

Best practice for replicating Partitioned table

Hi SQL Gurus,
Requesting your help on the design consideration for replicating a partitioned table.
1. 4 Partitioned tables (1 master table with foreign key constraints to 3 tables) partitioned based on monthly YYYYMM
2. 1 table has a XML column in it
3. Monthly switch partition to remove old data, since it is having foreign key constraint; disable until the switch is complete
4. 1 month partitioned data is 60 GB
having said the above, wanted to create a copy of the same tables to a different servers.
I can think of
1. Transactional replication, but then worried about the XML column,snapshot size and the alter switch will make the same thing
on the subscriber or row by row delete.
2. Logshipping with standby with every 15 minutes, but then it will be for the entire database; because I have other partitioned monthly table which is of 250 GB worth.
3. Thinking about replicating the Partitioned table as Non Partitioned, in that case how the alter switch will work. Is it possible to ignore delete when setting up the replication.
3. SSIS or Stored procedure method of moving data on a daily basis.
4. Backup and restore on a daily basis, but this will not work when the source partition is removed.
Ganesh

Plz refer to
http://msdn.microsoft.com/en-us/library/cc280940.aspx

Partition Table Looks Different Between OSX and Windows 7

Hey all,
I recently replaced the hard drive on my 2007 iMac, going from the 320GB drive to a 1 TB drive. It actually worked! The previous drive was failing in very odd ways, though booting into the Windows side (more on dual boot later) always seemed to work, and S.M.A.R.T. always reported that the physical drive seemed OK.
The previous drive (320 GB) had around 200GB devoted to OSX and 100GB partitioned off for a working Windows 7 installation (custom installed x64 Win7 Ultimate). I had the Windows system image backed up to my NAS, and had a Windows system bootable disc to restore that image.
After replacing the drive (and almost crying that I had actually done it right), I first restored OSX from a Time Machine backup, and let it take the full 1TB of space as Journalled HFS+. Then, I used Disk Utility to shrink OSX down to 500GB, and created a second partition (formatted to NTFS) with the remaining 500GB.
Now, restoring a Windows system image is an odd thing, as it tries to do a lot of partition work as opposed to simply restoring the Windows install to a partition. I tried Macrium Reflect first (made a backup in that, too), and it looked like it was going to let me restore to the second partition. It completed the restore...and the entire hard drive was hosed. Partitions had been moved, renamed, resized, and nothing was bootable. I had to use Recovery from an external USB thumb drive to go back to the single, full-drive install of OSX.
Then I tried again. Made the second NTFS partition and used the basic Windows System Restore disk to restore from the standard system image I had on the NAS. I was not expecting this to work. But it did. Windows started showing up in Startup Manager when "option" was pressed on bootup, and both OSX and Windows booted properly and ran fine. This is where I (finally) get to the supreme oddities:
OSX Disk Utility still reports two 500GB partitions, one for OSX and one for Windows.
In OSX the Windows partition shows as having NO DATA on it. Not sure what would happen if I tried to write a file to it when mounted, but there is no data on it when viewed from OSX (I was always able to see the Windows files when I mounted that partition on the previous drive).
The Windows partition does not show up as a valid bootable system in System Prefs --> Startup Disk (naturally, I suppose, since OSX doesn't think there is anything there).
From the WINDOWS side, Windows still sees the old partition table: 200GB for the "unknown" HFS partition, and then the rest of the space can be devoted to Windows (started as 100GB, but I was ablt to expand it to use the remaining ~750GB!). Windows thinks it can have 750GB of space even though I know its partition is only 500GB in size!
Windows cannot see the OSX HFS partition data using HFSExplorer. It CAN see the HFS partition on the attached backup drive (the drive I use for Time Machine).
GParted (a partition program on a Linux bootabld CD-ROM) shows the same partitions as OSX Disk Utility (2x500GB), and also thinks the Windows NTFS partition is empty (all space reports as "unused").
Did I mention both OSX and Windows work fine???
There are, of course, two other partitions on the drive: the first partition is the 200MB one I always see (EFI/GUID portion?), and then between the HFS and NTFS partitions is the 600MB recovery partition (which also shows at option-pressed boot time). OSX, GParted, and Windows see all four partitions, and in the same order. It is just that Windows sees the wrong sizes, and OSX cannot see any data in the Windows partition.
Surely this is all going to break spectacularly at some point, isn't it? What if I ever did write a file to the Windows side from OSX, or what if OSX starts taking more space than the 200GB Windows thinks is the max for that partition? What if I try to make Windows use more than 500GB because it thinks it has almost 800GB to use? What if I defrag the Windows drive?
I had no idea a partition table could look this goofy and yet still have everything be bootable and workable. Is there something I can do to get everything in sync? Basically, I am assuming I need to get Windows to do some low-level kung fu in Disk Manager in order to properly get everything lined up with the "right" partitions as reported by both GParted and OSX Disk Utility. But how do I do that?
By the way, any ideas that totally nuke the drive and start from scratch are completely fine (if it seems like they are doing something different enough that I'd give it a try). I have good backups of both OSX and Windows and have restored them about a half dozen times already as I dealt with the previous failing hard drive and with trying to get dual-boot working again. Not to mention, this iMac is now my secondary machine to the new Mac Mini I got a couple weeks back when I wasn't sure how much more life I was going to get from this 6+ year old iMac.
Thanks for listening to me ramble about this very odd issue, and a huge THANK YOU in advance to anyone who has ideas to help.
Thanks,
sutekh138

Update:
I am pretty sure the issue is a simple GPT/MBR discrepancy.
I installed rEFIt and used it's partitioning tool (gptsync built in) upon bootup. It was able to show the GPT table and the MBR table, but it thinks the second partition of the drive (the Mac OSX bootable partition) is "extended" in the MBR table and says "will not touch this disk."
However, it does look like an MBR sync should be straightforward, as there four partitions in the GPT table and four in the MBR (and MBR allows a max of four, AFAIK). I just need gptsync to relax some rules. I found a link to a supposedly newer version of gptsync compiled for OSX, so I will try that later.
First, I will try Partition Wizard, a free tool I found for the Windows side. It has a "Repair MBR" option that I would have tried last night if I weren't running a new Windows Image Backup in case all of this goes haywire. *smile* The PW tool also has an option to change the MBR over to GPT entirely. That might work, but then I am not sure Windows 7 will boot (from what I read, x64 Win7 running on EFI-enabled hardware should work, but who knows).
Anyway, I will try the following things, in order, until something works, when I get home tonight:
From Windows, run Partition Wizard and try "Repair MBR".
From OSX, download recent gptsync and try to run it.
From Windows, use Partition Wizard to do a full MBR --> GPT conversion.
Nuke the Windows partition in OSX Disk Utility, expand the HFS partition to take up the whole drive, and then add a Windows-bootable partition via Boot Camp-ish command line commands (diskutil). Because if nothing else works, I have to assume I just created the partitions wrong in the first place such that a Windows restore miraculously works, but the partition weirdness is just a timebomb waiting to happen.
Finally, if none of the above work, I'll just get things back to the way they now work and wait for the timebomb to (possibly never) go off. *smile*
I'll update this thread if I get something figured out, in case anyone else stumbles upon it...
Thanks,
sutekh138

Compression getting disabled when performing Update on partitioned tables

Hi All,
I am on Oracle Database 11g Enterprise Edition Release 11.2.0.3.0.
My question is related to Oracle Compression.
I have a sub-partitioned table enabled with Basic Compression. In enabled compressed state, I am updating few columns of this table(Normal Update command and Merge as well) but the end result shows increase in the table size and the compression is still in ENABLED state. Post that, if I compress the sub-partition explicitly the table comes back to its original size.
Is it a bug? I read a white paper on 11g itself, that compression remains enabled in case of all DML operations, then why this behaviour?
Thanks,
Ishan

Ishan,
taking a look at http://docs.oracle.com/cd/E11882_01/server.112/e25494/tables.htm#CJAGFBFG It seems that the distinction between OLTP and basic compression is sometimes a little bit vague ("Operations that permit compression include: ..."), but I can also find the statement "Rows inserted without using direct-path insert and updated rows are uncompressed." So I would say it's not a bug but a limitation of the feature. Updates just don't mix well with compression.
Martin

How to get the size of the table

Hi All,
How to get the size of the table in Oracle 10g?
Is there any script which needs to be run?
Regards,
Apoorv

Hi All,
Sorry but somehow the table user_segments is not populated in my case. But we have another table SYS.ALL_TABLES whose structure is given below. Would I be able to calculate the table size based on the columns given below:
ColumnName     Data Type
OWNER     VARCHAR2 (30 Byte)
TABLE_NAME     VARCHAR2 (30 Byte)
TABLESPACE_NAME     VARCHAR2 (30 Byte)
CLUSTER_NAME     VARCHAR2 (30 Byte)
IOT_NAME     VARCHAR2 (30 Byte)
STATUS     VARCHAR2 (8 Byte)
PCT_FREE     NUMBER
PCT_USED     NUMBER
INI_TRANS     NUMBER
MAX_TRANS     NUMBER
INITIAL_EXTENT     NUMBER
NEXT_EXTENT     NUMBER
MIN_EXTENTS     NUMBER
MAX_EXTENTS     NUMBER
PCT_INCREASE     NUMBER
FREELISTS     NUMBER
FREELIST_GROUPS     NUMBER
LOGGING     VARCHAR2 (3 Byte)
BACKED_UP     VARCHAR2 (1 Byte)
NUM_ROWS     NUMBER
BLOCKS     NUMBER
EMPTY_BLOCKS     NUMBER
AVG_SPACE     NUMBER
CHAIN_CNT     NUMBER
AVG_ROW_LEN     NUMBER
AVG_SPACE_FREELIST_BLOCKS     NUMBER
NUM_FREELIST_BLOCKS     NUMBER
DEGREE     VARCHAR2 (10 Byte)
INSTANCES     VARCHAR2 (10 Byte)
CACHE     VARCHAR2 (5 Byte)
TABLE_LOCK     VARCHAR2 (8 Byte)
SAMPLE_SIZE     NUMBER
LAST_ANALYZED     DATE
PARTITIONED     VARCHAR2 (3 Byte)
IOT_TYPE     VARCHAR2 (12 Byte)
TEMPORARY     VARCHAR2 (1 Byte)
SECONDARY     VARCHAR2 (1 Byte)
NESTED     VARCHAR2 (3 Byte)
BUFFER_POOL     VARCHAR2 (7 Byte)
ROW_MOVEMENT     VARCHAR2 (8 Byte)
GLOBAL_STATS     VARCHAR2 (3 Byte)
USER_STATS     VARCHAR2 (3 Byte)
DURATION     VARCHAR2 (15 Byte)
SKIP_CORRUPT     VARCHAR2 (8 Byte)
MONITORING     VARCHAR2 (3 Byte)
CLUSTER_OWNER     VARCHAR2 (30 Byte)
DEPENDENCIES     VARCHAR2 (8 Byte)
COMPRESSION     VARCHAR2 (8 Byte)
DROPPED     VARCHAR2 (3 Byte)

How to adjust the memory size of partition?

I have the mac os partition and bootcamp partition in my air now. And I installed win7 into the bootcamp for 190G. So I want to adjust the size of bootcamp and enlarge the mac os partition, and create a new partition for using time machine. Can I make it without losing any data?

Keeping no backups is a disaster waiting to happen so it is good that you are planning to use TimeMachine, but putting your backup on a partition of the drive you are backing up is almost like having no backup plan. There are lots of reasons you'd need to restore from a backup and many (if not most) would also leave your TM backup unusable. If your hard drive dies you'd have no TM backup. If your partition table is damaged you'd have no backup. If your computer were stolen you'd have no backup. If fire or flood destroyed your computer you'd have no backup. Buy an external hard drive and use that for TM backups and you can leave your computer's hard drive alone.

GATHER_TABLE_STATS on partitioned table

Hello All,
I am using Oracle 11g R2.
I am having a partitioned table, this table can have up to 30 partitions based on my retention policy and each partition is 1 day of data. each partition have like 3 millions records.
I am gathering the statistics of my current partition as below:
DBMS_STATS.GATHER_TABLE_STATS (SCHEMA_NAME, TABLE_NAME, PARTITION_NAME, ESTIMATE_PERCENT => DBMS_STATS.AUTO_SAMPLE_SIZE, METHOD_OPT=> 'FOR ALL COLUMNS SIZE AUTO');I noticed that when the table have 6 or 7 partitions the above gather statistics was taking like 20 mins. now I have 20 partitions on the table it is taking 45 minutes.
What is the reason ? should not be the same ? as I am gathering the statistics for only 1 partition ? and all partitions have the same number of records?
Regards,

What is the default ? granularity=>'ALL' or granularity=>'PARTITION' in the belowAUTO
GRANULARITY - The value determines granularity of statistics to collect (only pertinent if the table is partitioned).
'ALL' - gathers all (subpartition, partition, and global) statistics
'AUTO'- determines the granularity based on the partitioning type. This is the default value.
'DEFAULT' - gathers global and partition-level statistics. This option is obsolete, and while currently supported, it is included in the documentation for legacy reasons only. You should use the 'GLOBAL AND PARTITION' for this functionality. Note that the default value is now 'AUTO'.
'GLOBAL' - gathers global statistics
'GLOBAL AND PARTITION' - gathers the global and partition level statistics. No subpartition level statistics are gathered even if it is a composite partitioned object.
'PARTITION '- gathers partition-level statistics
'SUBPARTITION' - gathers subpartition-level statistics.
Regards
Girish Sharma
Edited by: Girish Sharma on Mar 11, 2013 7:39 PM
http://docs.oracle.com/cd/E11882_01/appdev.112/e25788/d_stats.htm#ARPLS059
Added doc link.

Size of partition table...

Similar Messages

Maybe you are looking for