Similar Questions

• Retrieve VMFS partition table... help.

  Hi all

  This morning, when I boot ESXi 4.0.0 I found lost a VMFS volume. By default, my drive has two partitions. I tried to recover the second partition with the instructions on the forum, but it was still not working.

  fdisk- lu/dev/disks/t10. ATA___ST3500418AS___9VM6Z8Y1

  Disk/dev/disks/t10. ATA___ST3500418AS___9VM6Z8Y1: 500,1 GB, 500107862016 bytes
  255 heads, 63 sectors/track, 60801 cylinders, total of 976773168 areas
  Units is 1 * 512 sectors is 512 bytes

  Device boot start end blocks Id system
  / dev/Disks/T10. 63 8386622 4193280 6 FAT16 ATA___ST3500418AS___9VM6Z8Y1p1
  Partition 1 does not stop the limit of cylinder
  / dev/Disks/T10. ATA___ST3500418AS___9VM6Z8Y1p2 8386623 976773167 484193272 + fb VMFS

  
  fdisk u /disks/dev/t10. ATA___ST3500418AS___9VM6Z8Y1

  The number of cylinders for this disk is set to 60801.
  There is nothing wrong with that, but it is higher than 1024,
  and could in certain setups cause problems with:
  (1) software that runs at startup (for example, the old versions of LILO)
  (2) start and partitioning software to other operating systems
  (e.g. BACK FDISK, OS/2 FDISK)

  Command (m for help): d
  Partition number (1-4): 2

  Command (m for help): w
  The partition table has been changed!

  The call ioctl() to re-read the partition table

  u Fdisk/dev/disks/t10. ATA___ST3500418AS___9VM6Z8Y1

  The number of cylinders for this disk is set to 1409485.
  There is nothing wrong with that, but it is higher than 1024,
  and could in certain setups cause problems with:
  (1) software that runs at startup (for example, the old versions of LILO)
  (2) start and partitioning software to other operating systems
  (e.g. BACK FDISK, OS/2 FDISK)

  Command (m for hELP): n
  Control action
  extended e
  p primary partition (1-4)
  p
  Partition number (1-4): 2
  First of the sector (by default 8386623-976773167, 8386623): using default 8386623
  Last sector or size + or + sizeM or + sizeK (8386623-976773167, by default 976773167): using default value 976773167

  Command (m for help): t
  Partition number (1-4): 2
  HEX code (type L to list codes): fb
  Changed the type of partition 2 to fb (VMFS)

  Command (m for help): x

  Expert command (m for help): b
  Partition number (1-4): 2
  New beginning of data (by default, 8386623-976773167, 8386623): 8386688

  Expert command (m for help): w
  The partition table has been changed!

  Calling ioctl() to re-read the partition table.

  I have VL connection and go to the Configuration > storage > refresh the volume does not return.

  Please help me!.

  This seems really odd. Do you have all the partitions on these 4 discs when you first installed ESXi?

  What version of ESXi you originally installed (3.5 or 4.0) in the case where that this system has been upgraded?

  Please after the release of fdisk-lu for all 4 disks in the system.

  André

• Satellite L630-00V - need to partition table

  Hello to you guys...

  So I really screwed up here, I did my girlfriend buy a laptop (Toshiba Satellite L630) and also a new hard drive to replace the one on the inside because they have slow (5400 RPM)

  I've used ghost to clone the drive inside the laptop to the new one I mounted in a housing that is connected via USB to the computer.

  Although I double checked everything and that the destination drive was the good the bad thing happened, the blank disc has been cloned on the full.

  I don't think that all my data are deleted, because there were at least 70 GB of commands on the computer (3 recovery partitions and Windows 7 one) and I doubt enough that it can all be erased within 5 seconds.

  I used GetBackData for NTFS witch scanned the hard drive for about 05:30 (Yes, 5 hours and a half) and well found a lot of files... If right now I copy all partitions said based on another hard drive...

  I'll have to do the scan a 2nd time to get Fat32 partitions...

  Something that would be useful for me is to have the partition table of a released factory Toshiba L630-00v (500 GB HDD) *.

  
  
  
  

  Beginning and end clusters would be really useful, I would be able to rebuild my much easier partition table

  
  And oh, no idea how to get the OEM Windows 7 cd to a new facility? They were paying for a copy of windows with their computer, their must be a way to install it...

  Thank you very much! ;)

  Hello

  > And oh, no idea how to get the OEM Windows 7 cd to a new facility? They were paying for a copy of windows with their computer, their must be a way to install it.

  Now, you can get money from Toshiba Recovery disk.

  For European models:

  https://backupmedia.Toshiba.EU/landing.aspx

  American models:

  https://www.CSD.Toshiba.com/cgi-bin/TAIS/support/JSP/serviceUnitVerification.jsp?orderType=SFF

  > my girlfriend did buy a laptop (Toshiba Satellite L630) and also a new hard drive to replace the one on the inside because they have slow (5400 RPM)

  What happens if put you the old hard drive to make a recovery disk and replace it with a new one, then... Then you will be able to restore the factory settings on the new hard drive with a recovery disk. Or you have not previously burned?

• after image restore, backup partition table is different

  Hello

  He is a 2012 Macbook mid Pro with El Capitan and Bootcamp.

  After repeated with Bootcamp (Windows 10 Pro) problems I started using Image of Terabyte for Linux in order to safeguard this Macbook. Forums terabyte that people know that the Image of Linux (such as Image for Windows) is able to create a reliable backup, but also to restore - restore an entire disk image or restoring individual partitions.

  I followed their instructions precisely and activated the two options "restore first Beach" and "TPG hidden OS" (as one terabyte official, Member of the forum wrote) when restoring a partition.

  Unfortunately, it did not work! Bootcamp was no longer visible in the start screen or wasn't visible, but not start.

  What I found was that I had to keep the two options (see above) with DISABILITIES.

  Then I could restore some partition images - and 10 Windows in Bootcamp is bootable.

  Well, it was the long introduction.  I'm sorry.

  Now my question is:

  Is this something that has changed my partition table?

  Before restoring an Image for backup of Linux for the first time, I had this partition table:

  localhost: ~ root # fdisk/dev/disk0

  Disk: geometry / dev/disk0: 60801/255/63 [976773168 sectors]

  Signature: 0xAA55

  From end

  #: cyl hd s - cyl hd s id [Start - size]

  ------------------------------------------------------------------------

  1: EA 1023 254 63 - 1023 254 63 [1-409639]

  2: AF 1023 254 63 - 1023 254 63 [409640-857906448] HFS +.

  3: AB 1023 254 63 - 1023 254 63 Boot Darwin [858316088-1269536]

  * 04:07 1023 254 63-1023 254 63 [859586560-117186560] HPFS/QNX / TO THE

  BUT:

  After failed attempts to restore and work finally restore my partition table operation is different:

  Fdisk/dev/disk0

  Disk: geometry / dev/disk0: 60801/255/63 [976773168 sectors]

  Signature: 0xAA55

  From end

  #: cyl hd s - cyl hd s id [Start - size]

  ------------------------------------------------------------------------

  1: EA 0 0 2 - 1023 255 63 [1-409639]

  2: AF 25 102 15 - 1023 255 63 [409640-857906448] HFS +.

  3: AB 1023 0 57 - 1023 255 63 Boot Darwin [858316088-1269536]

  * 04:07 1023 199 8-1023 255 63 [859586560-117186560] HPFS/QNX / TO THE

  Everything seems to work fine, but I wonder if the different appearance of the partition table can be a problem?

  For example, compare:

  1: EA 1023 254 63 - 1023 254 63]

  3 o

  409639]

  TO

  1: EA 0 0 2 - 1023 255 [63 3 o 409639]

  It's the output of 'diskutil list ':

  localhost: ~ root # diskutil list

  / dev/disk0 (internal, physical):

  #: NAME SIZE TYPE IDENTIFIER

  0: GUID_partition_scheme * GB 500,1 disk0

  1: disk0s1 EFI EFI 209.7 MB

  2: Apple_HFS Macintosh HD 439,2 GB disk0s2

  3: disk0s3 Apple_Boot Recovery 650.0 MB HD

  4: Microsoft database BOOTCAMP 60.0 GB disk0s4

  And the output of 'TPG - r - vv show/dev/disk0':

  See the TPG: / dev/disk0: mediasize = 500107862016; SectorSize = 512; blocks = 976773168

  See the TPG: / dev/disk0: MBR suspicious to sector 0

  See the TPG: / dev/disk0: Pri GPT to sector 1

  See the TPG: / dev/disk0: GPT Sec at sector 976773167

  start index size summary

  0 1 MBR

  1 1 Pri GPT header

  2 32 table GPT Pri

  34 6

  40 409600 1 part TPG - C12A7328-F81F-11D2-BA4B-00A0C93EC93B

  409640 857906448 2 part TPG - 48465300-0000-11AA-AA11-00306543ECAC

  858316088 1269536 3 part TPG - 426F6F74-0000-11AA-AA11-00306543ECAC

  859585624 936

  859586560 117186560 4 part TPG - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7

  976773120 15

  976773135 32 table dry GPT

  976773167 1 dry GPT header

  Out of 'gdisk/dev/disk0:

  localhost: ~ root # gdisk/dev/disk0

  GPT fdisk (gdisk) version 1.0.1

  WARNING: Open with shared lock devices will not have their

  table partition automatically reloaded!

  Scanning partition table:

  MBR: hybrid

  BSD: absent

  APM: absent

  TPG: present

  Found a valid GPT with hybrid MBR; using GPT.

  Command (? for help): p

  Disk/dev/disk0: 976773168 sectors, GiB 465.8

  Logical sector size: 512 bytes

  Identifier (GUID) of disc: 38A2E667-6E00-4C0F-BD78-C95979E3CFAE

  Partition table contains up to 128 entries

  First usable sector is 34, last usable area is 976773134

  The partitions will be aligned with the boundaries of sector 8

  Space is free total 957 sectors (478,5 KiB)

  Starting number (sector) end (sector), Code name of size

  409639 40 1 MiB EF00 EFI 200.0

  2 409640 858316087 409.1 giB AF00 Macintosh HD

  3 858316088 859585623 619.9 MiB AB00 Recovery HD

  4 859586560 976773119 55.9 giB 0700 BOOTCAMP

  Any ideas?

  Another question:

  Is it possible to save the table to partition like that?

  DD if = / dev/sda of = gptandmbr bs = 512 count = 34

  Thank you very much

  NEUMAC

  In Fdisk, the CHS numbers are arbitrary on modern disks. They are the time of BIOS and old disks with CHS geometry. Puts BCA from Mac 0-1023 (1024 cylinders), 0-255 (256 heads) and 0-63 (64 sectors). Modern disks far exceed those numbers and would drain them. Must match what is the triplet of start/end/size and it fits in GPT and MBR. You can put arbitrary 0,0,0 for CHS and you will see all issues on GPT disks.

  Please do not use TBIL to restore W10 to circa 1970-80 disks.

• partition table

  When we need to use the partition table?

  Partitioning defined

  The concept of divide and conquer has been around since the time of Sun Tzu (500 BC). Recognizing the wisdom of this concept, Oracle applied to management of large tables and indexes. Oracle has continued to evolve and refine its capabilities of partitioning since its first implementation of the Oracle 8 range partitioning. Oracle 8i and 9i, Oracle has continued to add features and new methods of partitioning. The current version of Oracle 9i Release 2 continues this tradition by adding new features to the list partitioning and partitioning method new range-list.

  When the partition

  There are two main reasons to use partitioning in an environment of VLDB (very large database). These reasons are related to improving the management and performance.

  Partitioning offers:

  • Management at the level of individual partition for data loads, creating indexes and reconstruction, and backup/restore. This may cause more quickly down, because only actively managed individual partitions are not available.
  • Performance of the queries increased by selecting only the relevant partitions. This process of weeding out the partitions that do not contain the data required by the application via a technique called the size of the partition.

  Use the partitioning:

  • When a table reaches a size "large". Large being defined according to your environment. Greater than 2 GB should always be considered for partitioning of tables.
  • What performance benefits outweigh the extra management issues related to partitioning.
  • When the archive data is on a calendar and repetitive. For example, data warehouses are usually given for a certain period of time (rolling window). Old data is then output to archive.

• VMFS partition table corruption? Need help to retrieve data

  My House ESXi 5.1 was installed on HP Microserver G7. Hypervisor on USB-flash, datastore on Adaptec 3405.

  After some problems of power electro Microserver is will not start and I have chosen to build the new server on Microserver Gen8. I moved Adaptec and disks in the new box, installed new ESXi 5.5 U1 (HP image) on USB and after reboot did not store data :-(.

  After some research, I found that ESXi is not see any partition table on this raid array:

  
  

  partedUtil getptbl /vmfs/devices/disks/mpx.vmhba2:C0:T0:L0

  unknown

  728422 255 63 11702108160

  BUT! I tried to start the server of linux liveCD with vmfs-tools 0.2.5 installed partition mounted with vmfs-fuse and able to see the data! But cannot copy all important vmdk (see below).

  debugvmfs is also show me some useful information:

  Volume Version: 14

  Version: 54

  Label: STORE

  Mode: public

  UUID: 4f2ac538-58c181cf-arms-441ea13ee615

  Creation date: 2012-02-02 23:17:44

  Block size: 1 MiB

  Subblock size: 8 KiB

  Size of header of the FDC: 64 KiB

  County of FDC Bitmap: 64

  and it's very strange

  debugvmfs/dev/sda1 see the lvm.extent [0]

  Device: / dev/sda1

  UUID: 4f2ac4da-8de4b166-a-441ea13ee615 848

  LUN: 0

  Version: 5

  Name:

  Size: 459.99 GiB

  NUM. Segments: 22319

  First Segment: 0

  Last Segment: 22318

  
  

  because I don't know that I don't create scopes.

  
  

  Also, there are two vmdk files on more than 256 GB data store and it cannot copy because of the limitation of vmdk-tools :-(.

  
  

  I tried to do a magic (like this - partedUtil setptbl "/ vmfs/devices/disks/mpx.vmhba2:C0:T0:L0" GPT "1 2048 11702099429 AA31E02A400F11DB9590000C2911D1B8 0""), but without success;-(.)

  
  

  All the suggestions, guys?
  

  Finally!

  Found that was an "Intel VT - d" enabled in the BIOS. After disable it everything is cool.

  It looks like Adaptec 3405 working wrong with it. Will try to change it to P222.

• Compression is disabled when performing the update on partitioned tables

  
  Hi all

  I'm on Oracle Database 11 g Enterprise Edition Release 11.2.0.3.0.

  My question is related to the Compression of the Oracle.

  I have an infra partitioned table enabled with Compression of the base. Active compressed State, I update some columns in this table (command Update Normal and merger as well) but the end result shows the increase in the size of the table and the compression is still in the ACTIVE State. After that, if I compress the secondary partition explicitly the table back to its original size.

  Is this a bug? I read a whitepaper on 11g itself, compression is turned on in the case of all DML operations, so why this behavior?

  Thank you

  Ishan

  Ishan,

  take a look at http://docs.oracle.com/cd/E11882_01/server.112/e25494/tables.htm#CJAGFBFG , it seems that the distinction between OLTP and compression of base is sometimes a bit vague ("operations that allow compression include:...") "), but I also find the statement"insert rows inserted without using direct-path access and updated rows are uncompressed. "So I would say it's not a bug but a limitation of the service. Updates just to not mix well with compression.

  Martin

• Scans of partition take longer than a full table on a non-partitioned table scan?

  Hello

  I have a PART_TABLE range partitioned table that has 10 million documents and 10 partitions having 1 million records each. Partition is based on a column named ID, which is a sequence of 1 to 10 million.

  I created another P2_BKP table (do a select * from part_table) which has the same group of data than that of PART_TABLE, except that this table is not partitioned.

  Now, I run the same query on the tables to get a range of data. Precisely, I'm reading only the data present in 5 partitions of the partitioned tables that requires theoretically less reading than when done on non partitioned tables.

  Yet the query seems to take more time on a table that is partitioned only when running on a non-partitioned table. No reason precisely why is this the case?

  Here's the query I am trying to run on the tables and their Plans to explain corresponding.

  ASK A

  =========

  Select * from P2_BKP where id < 5000000;

  ----------------------------------------------------------------------------

  | ID | Operation | Name | Lines | Bytes | Cost (% CPU). Time |

  ----------------------------------------------------------------------------

  |   0 | SELECT STATEMENT |        |  6573K |   720 M | 12152 (2) | 00:02:26 |

  |*  1 |  TABLE ACCESS FULL | P2_BKP |  6573K |   720 M | 12152 (2) | 00:02:26 |

  ----------------------------------------------------------------------------

  QUERY B

  ========

  Select * from part_table where id < 5000000;

  -------------------------------------------------------------------------------------------------------

  | ID | Operation | Name | Lines | Bytes | Cost (% CPU). Time | Pstart. Pstop |

  -------------------------------------------------------------------------------------------------------

  |   0 | SELECT STATEMENT |            |  3983K |   436 M | 22181 (73) | 00:04:27 |       |       |

  |   1.  RANGE OF PARTITION ITERATOR.            |  3983K |   436 M | 22181 (73) | 00:04:27 |     1.     5.

  |*  2 |   TABLE ACCESS FULL | PART_TABLE |  3983K |   436 M | 22181 (73) | 00:04:27 |     1.     5.

  -------------------------------------------------------------------------------------------------------

  016f62a3-35cf-4f4e-B812-95774e4d662f wrote:

  Now, I run the same query on the tables to get a range of data. Precisely, I'm reading only the data present in 5 partitions of the partitioned tables that requires theoretically less reading than when done on non partitioned tables.

  Yet the query seems to take more time on a table that is partitioned only when running on a non-partitioned table. No reason precisely why is this the case?

  Have you actually run the queries, or you assume that they will take different amounts of time because the execution plans show different numbers?

  It is clear from the output of the execution plan that the statistics are not very good, since Oracle should have estimated about 5 M of lines for each request. That said, however, Oracle should have used the counties of partition block level to estimate the cost of the analysis of the 5 score - and we could expect them to a total of less space than a full copy.

  Of course, it is possible that your partitioned table has been the subject of many DML involving the line movement and line of chaining; It is possible he has been the subject of many lots of parallel or direct path loads inserts leaving much free space in each partition. It is also possible that you have created the copy in a tablespace that table of default compression!

  What are the stats for the original table partition level?   (select nom_partition, num_rows, blocks of user_tab_partitions where table_name = 'T1' partition_position order)

  Concerning

  Jonathan Lewis

• Unusable index Partitioned table

  Oracle Version: 11.2.0.2
  OS: Linux RHEL 5
  
  I'm having a problem with the index on a partitioned table interval. This is the scenario:
  
  There are 3 indices (A, B, C) on a table. A is created on two columns (1,2), B is on the column (2), C is the column (3). Table is partitioned on column 2 apart. A and B are partitioned indexes. When I drop a partition without a clause to update index, Index C will unusable. After seeing this, I gave up the C rating and create it as a local partitioned index, then all indexes are in condition of use after the drop partition statement. Is - this mandatory on a range partitioned table all indexes on the table must be locally partitioned inorder to have indexes in usable state after the drop statement of partition (without the update index clause)? Also there will be a negative impact for all indexes on the table like locally partitioned indexes?

  >
  Is - this mandatory on a range partitioned table all indexes on the table must be locally partitioned inorder to have indexes in usable state after the drop statement of partition (without the update index clause)?
  >
  Yes - it should be obvious by looking at a simple example.

  You have an OVERALL index and drop a partition but say Oracle are NOT updating the overall index.

  How this index may be usable for anything? It is not accurate. There was GARBAGE everywhere that gets in the way of Oracle find the entries of the "good". There are the index keys in the branch blocks that belong to the partition that has been deleted. Oracle cannot use these keys to determine how the blocks of branch, he needs to find.
  >
  Also there will be a negative impact for all indexes on the table like locally partitioned indexes?
  >
  Who knows? There are maybe or maybe not.

  As with many things Oracle "it depends."

  It depends on what types of queries that you ran.

  It depends on the filter predicates used for query.

  It depends on if the maintenance simple score (add/drop/split) are important to you.

  For the maintenance of the partition only all index LOCAL is the best.

  For full table scan, an index is not intended to be used.

  For a query that needs all THE records for a COMPANY_ID given in a table partitioned by DATE an OVERALL index could be better. Oracle also use 100 index LOCAL (if there are 100 partitions) to get the same data.

  It depends on.

• modifies an existing large partitioned table to automatically add the partitions

  Hello world
  
  According to me, it is not possible to modify an existing large partitioned table, to add partitions automatically as you insert it into this one. What would be the best way to do this? Dbms_redefinition? DEC + copy dependant rename?
  
  Any ideas?
  
  Thank you.
  
  current version:
  Oracle Database 11 g Enterprise Edition Release 11.2.0.3.0 - 64 bit Production
  With partitioning, Real Application Clusters, Automatic Storage Management, OLAP,.
  Options of Data Mining and Real Application Testing

  >
  According to me, it is not possible to modify an existing large partitioned table, to add partitions automatically as you insert it into this one. What would be the best way to do this? Dbms_redefinition? DEC + copy dependant rename?

  Any ideas?
  . . .
  I guess what I'm looking for is
  ALTER TABLE XXX INTERVAL DEFINED (NUMTOYMINTERVAL(1,'MONTH'));

  The following problem, I see is my required interval varies 01 hours of daylight at the time month 01 day 01 01 of the following month.
  >
  The best way to do it is to change your way of thinking.

  Do not be afraid to break the Oracle actually trying things. Just ALTER the table.

  drop table part_test cascade constraints;
  
  create table part_test(id number, entry_date date)
  partition by range (entry_date)
  (
  partition old_years values less than (to_date('01/01/2013 01:00:00', 'mm/dd/yyyy hh24:mi:ss')),
  partition jan_2013 values less than (to_date('02/01/2013 01:00:00', 'mm/dd/yyyy hh24:mi:ss'))
  )
  
  insert into part_test values(1, to_date('01/01/2013 00:00:00', 'mm/dd/yyyy hh24:mi:ss'));
  
  insert into part_test values(2, to_date('01/01/2013 02:00:00', 'mm/dd/yyyy hh24:mi:ss'));
  
  alter table part_test set interval(numtoyminterval(1,'MONTH')); 
  
  insert into part_test values(2, to_date('02/01/2013 02:00:00', 'mm/dd/yyyy hh24:mi:ss'));
  
  SQL> set serveroutput on
  SQL> select partition_name, high_value
    2  from dba_tab_partitions
    3  where table_name = 'PART_TEST';
  
  PARTITION_NAME
  ------------------------------
  HIGH_VALUE
  --------------------------------------------------------------------------------
  
  OLD_YEARS
  TO_DATE(' 2013-01-01 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIA
  
  JAN_2013
  TO_DATE(' 2013-02-01 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIA
  
  SYS_P225
  TO_DATE(' 2013-03-01 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIA
  
  SQL>
  

  Note the limit of the score for SYS_P225 that was created? It includes the same ' time 1' of the highest range partition that existed before the ALTAR.

• A slower loading into partitioned table as the non partitioned table - why?

  Hello
  
  Using oracle 11.2.0.3.
  
  Have a large fact table and do some comparative tests on the loading of large amounts of data histroical (several hundred GB) in fact range partitioned to date table.
  
  Although I understand if use exhange partition loading may be faster to load a partitioned table, trying to figure out why a standard sql insert takes 3 x long to load a table partitioned compared to an identical table but not partitioned. Identical EVERYHING in terms of columsn and the sql that the insert and second partitioned sql execution to
  ensure caching with no impact.
  
  Local partitioned table a partitioned bitmap index as compared to the non-partitioned table that has standardnon-partioned bitmap indexes.
  
  Any ideas/thoughts?
  
  Thank you

  One would expect that the queries that cannot no partition pruning may be slowed down, Yes.

  An easy way to see this is to imagine that you have a partitioned local index b-tree and a query that needs to scan all partitions of the index to find a handful of lines that interest you (of course, this is not likely to be exactly what you see probably but we hope informative of the source of the problem). Let's say that each partition of the index has a height of 3, so for each partition, Oracle has read 3 blocks to reach the correct terminal node. So to analyze each of the N index partitions, you need block index 3 * N bed. If the index is not partitioned, perhaps the height of the index would go up to 4 or 5 If, in that case not partitioned, you must read 4 or 5 blocks. If you have hundreds or thousands of partitions, it can easily be hundreds of times more work to analyze all the index partitions individual he would to analyze one unpartitioned index.

  Partitioning is not a magical option "go faster". It is a compromise - you optimize certain operations (such as those that can partition pruning) at the expense of operations that do not partition size.

  Justin

• Invalid or corrupted partition table esxi 4.1

  Saludos a todos,

  I have a problem with updated esxi 4.1

  (1) hize los raid desde cero con 1 totally controladora del servidor are only estos wont tenian esx 3.5

  (2) do los HBA 'fibra puertos '.

  (3) comenze the instalacion of esxi 4.1

  Instale esxi 4.1 en unos servidores dell 2950 instalacion comienza normal sin errores despues of the instalacion me of that review the HCG en vmware.com

  y if the small supports esxi 4.1 version

  entonces sale me una opcion reparar y disco y reparar el disco después pulled me this message

  Invalid or corrupted partition table, your server has been put into audit mode you have recreated the partitiond on your disk manually

  depues of esto el Server pide el reboot y el Server inicializa pero normal al puro final al da UN error con letras rojas pero too rapido para despues el Server levanta although tighter is configura y todo normal sin problemas, pero if is reincia el server is pierde config 'tcp/ip', 'dns' etc.

  hecho el proceso instalacion achieve several veces y da el mismo problema

  tambien trate recreear las recording manualmente por consoled pero no lo prevalence

  his las particiones than veo desde estas consoled her

  
  Device boot start end blocks Id system
  /dev/disks/NAA.6001ec90ea001c00156f951906d29aa6p1 5 900 917504 5 extended
  /dev/disks/NAA.6001ec90ea001c00156f951906d29aa6p4 * 1 4 4080 4 FAT16 < 32M
  5 254 255984 6 FAT16 /dev/disks/NAA.6001ec90ea001c00156f951906d29aa6p5
  255 504 255984 6 FAT16 /dev/disks/NAA.6001ec90ea001c00156f951906d29aa6p6
  /dev/disks/NAA.6001ec90ea001c00156f951906d29aa6p7 505 614 fc 112624 VMKcore
  615 900 292848 6 FAT16 /dev/disks/NAA.6001ec90ea001c00156f951906d29aa6p8

  Saludos,

  Hola Warrenjc:

  What controladora disco tiene ese servidor?

  Probaria an instalar ESXi in a nightclub RAID sin unico y falla test TR an instalarlo UN USB en. Of este modo can detectar el fallo viene por controladora Quebec City if no este soportada.

  A greeting.

• Collection of statistics on partitioned and non-partitioned tables

  Hi all
  My DB is 11.1
  
  I find that the collection of statistics on partitioned tables are really slow.
  

  TABLE_NAME                       NUM_ROWS     BLOCKS SAMPLE_SIZE LAST_ANALYZED PARTITIONED COMPRESSION
  ------------------------------ ---------- ---------- ----------- ------------- ----------- -----------
  O_FCT_BP1                        112123170     843140    11212317 8/30/2011 3:5            NO                    DISABLED
  LEON_123456                      112096060     521984    11209606 8/30/2011 4:2           NO                   ENABLED
  O_FCT                           115170000     486556      115170 8/29/2011 6:3            YES         
  
  SQL> SELECT COUNT(*)  FROM user_tab_subpartitions
    2  WHERE table_name =O_FCT'
    3  ;
  
    COUNT(*)
  ----------
         112

  I used the following script:

  BEGIN
    DBMS_STATS.GATHER_TABLE_STATS(ownname          => user,
                                  tabname          => O_FCT',
                                  method_opt       => 'for all columns size auto',
                                  degree           => 4,
                                  estimate_percent =>10,
                                  granularity      => 'ALL',
                                  cascade          => false);
  END;
  /

  It costs 2 minutes for the first two tables to gather statistics respectively, but more than 10 minutes for the partitioned table.
  Time of collection of statistics represents a large part of the time of the whole lot.
  Most of the work of the lot are at full load, which case all partitions and subpartitions will be affected and we cannot collect just specified partitions.
  
  Does anyone have experiences on this subject? Thank you very much.
  
  Best regards
  Leon
  
  Published by: user12064076 on August 30, 2011 01:45

  Hi Leon

  Why don't collect you statistics to the partition level? If your data partitions will not change after a day (score range date for ex), you can simply do to the partition level

  GRANULARITY-online 'SCORE' for partition level and
  GRANULARITY-online 'SUBPARTITION' for subpartition level

  You collect global stats whenever you can not require.

  Published by: user12035575 on August 30, 2011 01:50

• importing into a partitioned table of interval 11g

  as I took export utility simple partition table 8i exp not rained so 100 k lines in there.
  
  and imported with the import utility in the interval of 11g partitioned based on the date column.
  
  There were imported, but did not what I expected...
  
  If we execute the simple insert for partition interval 11g command, it create new partition automatically according to the strategy of partition.
  
  Here's the demo...
  
  created range partitioned table on the date with shift interval column...
  
  CREATE TABLE TEST.xxx_HIST
  (
  xxx_DATE DATE NOT NULL,
  P_ROLL_CONVENTION CHAR (2),
  R_ROLL_CONVENTION CHAR (2),
  P_COMPOUNDING_IND CHAR (2),
  R_COMPOUNDING_IND CHAR (2),
  P_CALC_METHOD CHAR (2),
  R_CALC_METHOD CHAR (2),
  P_SPREAD_AMT NUMBER (28,12).
  R_SPREAD_AMT NUMBER (28,12).
  
  )
  partition by range (xxx_DATE)
  interval (numtoyminterval(3,'MONTH'))
  store (security)
  (
  values of pQ1 lower partition (to_date('2010-01-01','yyyy-mm-dd'))
  ) IN PARALLEL.
  
  
  -IMPORTED FROM ROWS IN THE TABLE...
  
  ======================================================================
  Connected to: Oracle Database 11 g Enterprise Edition Release 11.1.0.7.0 - 64 bit Production
  With partitioning, OLAP, Data Mining and Real Application Testing options
  
  Export file created by EXPORT: V08.01.07 direct
  
  CAUTION: objects have been exported by SYSTEM, not by you
  
  . import of xx_ARCH in TEST objects
  . . import of 141749 lines imported from the table 'xxx_HIST '.
  Import completed successfully without warnings.
  ========================================================================
  
  
  
  -HE HAS A LOT OF DATES OF DIFF IN THERE...
  
  
  
  SQL > SELECT COUNT (DISTINCT xxx_DATE) TEST.xxx_HIST;
  
  COUNT (DISTINCT xxx_DATE)
  -----------------------------
  1371
  
  
  28-MARCH 06
  10 FEBRUARY 06
  9 FEBRUARY 05
  20 FEBRUARY 02
  3 JUNE 02
  10 MAY 04
  26 DECEMBER 03
  31 JANUARY 03
  
  xxx
  ---------
  21 JULY 08
  31 OCTOBER 05
  25 APRIL 08
  28 APRIL 08
  12 OCTOBER 06
  DECEMBER 21 07
  28 DECEMBER 04
  
  
  -BUT STILL ALL DUMPED INTO A PARTITION
  
  
  SQL > SELECT nom_partition FROM DBA_TAB_PARTITIONS WHERE TABLE_OWNER = 'TEST ';
  
  NOM_PARTITION
  ------------------------------
  PQ1
  
  It all dumped in a partition...
  
  fact partition interval 11g creates the partition automatically in function whose lines if imported... when we import lines in there...? or am I missing something?
  
  any idea guys?

  Seems to be a poor strategy for me because if I am not mistaken, there is no way to specify the order of the imported lines. If you import a line with the date max as your first row... bang, you get a range partition created for you and the rest falling.

  I think you'd be better import these data into a table in step and then by a

  insert into new_fancy_partition_table
  select *
  from old_8_temporary_imported_table
  order by date_column asc
  

  Or create the partitions manually.

  I just realized that you specify a partition in your create table statement (missed that on cursory inspection). And I think you misunderstand how the interval works... it's for values LARGER than the existing partitions ONLY...

  http://download.Oracle.com/docs/CD/E11882_01/server.112/e10592/statements_7002.htm#SQLRF01402

  "
  INTERVAL clause

  Use this clause to set the interval of partitioning the table. Range partitions are partitions based on a digital range interval or datetime. * They extend from range partitioning by commanding the database to automatically create partitions of the specified range or interval when the data inserted in the table exceed all the partitions.* range
  "

  Published by: Tubby on August 16, 2010 18:32

  Additional document link.

• Partitioned Tables and indexes

  Hello
  
  
  I have a question on the table and index partitioning. My scenario is:
  
  Charge 2 mio records in table T once a month. Loaded records are added to existing records, and once loaded data is never changed.
  At some point, I want to delete the older recordings, so I intend to this partition table.
  
  T table looks like:
  

  create table t (id       number(10) not null  constraint t_pk primary key,
                  period   number(10) not null,
                  contract number(10) not null,
                  attr     number(10) not null);
  
  create unique index t_ux1 on t(contract,period);
  
  create index t_ix2 on t(period);

  My plan is to partition T over the period, and I'm trying to read through the concepts
  http://download.Oracle.com/docs/CD/B19306_01/server.102/b14220/partconc.htm#g471747
  
  
  My question is now, how to manage the indexes, the t_pk, the t_ux1 and the t_ix2. Concepts of say,
  
  «1. If the table partitioning column is a subset of index keys, use a local index.»
  
  "2. If the index is unique, use a global index. If this is the case, you are finished. »
  
  
  So, that's how I read it
  -t_pk is unique, so this should be global
  -t_ux1 of columns is a subset, unless I have misunderstood (?), which should be local
  -index t_ix2 column is the same as the partitioning column, so it must be local
  
  Is this right, this t_ux1 should be a local partioned index, even if the period is the second column in the index?
  
  If true, what will happen when a partion fell?
  
  
  I am new in this area, so please feel the comment as you wish.
  
  
  Concerning
  Peter
  
  
  BANNER
  ----------------------------------------------------------------
  Oracle Database 10 g Enterprise Edition release 10.2.0.3.0 - 64bi
  PL/SQL version 10.2.0.3.0 - Production
  CORE Production 10.2.0.3.0
  AMT for IBM/AIX RISC System/6000: Version 10.2.0.3.0 - production
  NLSRTL Version 10.2.0.3.0 - Production

  Peter Gjelstrup wrote:

  My question is now, how to manage the indexes, the t_pk, the t_ux1 and the t_ix2. Concepts of say,

  «1. If the table partitioning column is a subset of index keys, use a local index.»

  "2. If the index is unique, use a global index. If this is the case, you are finished. »

  So, that's how I read it
  -t_pk is unique, so this should be global
  -t_ux1 of columns is a subset, unless I have misunderstood (?), which should be local
  -index t_ix2 column is the same as the partitioning column, so it must be local

  Is this right, this t_ux1 should be a local partioned index, even if the period is the second column in the index?

  A partitioned index locally can only be defined as unique if the partition key is part of the columns in the index. Imagine what the database would have to do if this is not the case: in order to verify if a newly added or updated value violates the uniqueness, it will have to travel all the partitions in a serialized operation - means that no one else could do the same thing at the same time. Since he is a killer of serious scalability in terms of locking and contention, this is not allowed.

  So: Your T_UX1 index can be defined as a unique index that is local because it contains the partition key. Although the index is not prefixed ("Prefix" means that it is divided by the left side of the columns in the index) which means that there may be access patterns where all partitions should be scanned or the optimizer cannot use a method of size of effective partition according to the way the index is reached.

  Your T_PK index cannot be set as local because it must be unique (you can not use a local non-unique index in this case), but does not contain your partition key. It must be a global index. An overall index can be partitioned as well (different from the underlying table) but it doesn't have to be.

  Depends on how you access your data you have not T_IX2 index when partitioning by this key because it corresponds to the partition key and therefore could not actually be used by the mechanism of partition pruning that limit your query to the scores of individuals.

  If you have more than one MAS environment where running queries are used longer, you should be fine with the index the in general (because they could be analyzed in parallel in parallel operations), but if you have an OLTP environment, then you should avoid local no prefix indexes due to the potential problem that you need to analyze all partitions.

  Be borne in mind that with partitioning adds an important layer of complexity to other areas: in particular the options available to the optimizer and analyze cost optimizer statistics. Depends on how you access your statistical data must be maintained on several levels now (level of score and at the global level, in the case of subpartitioning may be still at this level). If your data is important and you rely on "global" level statistics (these are always the case when the optimizer at the time analysis cannot limit access to a single partition) then in the pre - 11 g databases analyze these "global" level statistics can take a lot of time and resources, since actually , you need data several times (once for the partition and even global level).

  Presenting this partitioning may mean other potential problems in terms of execution that change (not for the better sometimes) plans and how to effectively collect statistics. Note that g 11 addresses the issue of 'statistics' by introducing the so-called "extra" global statistics. Greg Rahn wrote a [blog note | http://structureddata.org/2008/07/16/oracle-11g-incremental-global-statistics-on-partitioned-tables/] on this nice feature.

  >

  If true, what will happen when a partion fell?

  Since you're already on 10g, you can specify the database to update the scores of the local index using the UPDATE of the INDEX clause, while 9i could maintain only an overall index and it is up to you to rebuild the local index partitions after the partition DDL on the table (according to the DDL operation).

  Kind regards
  Randolf

  Oracle related blog stuff:
  http://Oracle-Randolf.blogspot.com/

  SQLTools ++ for Oracle (Open source Oracle GUI for Windows):
  http://www.sqltools-plusplus.org:7676 /.
  http://sourceforge.NET/projects/SQLT-pp/

  Published by: Randolf Geist on Sep 30, 2008 16:39

  Added statistics / optimizer warning when you use the partitioning