Similar Questions

• import a table that is partitioned into non partitioned table?

  Hello
  
  RDBMS 10 g
  
  It's my scenario:
  I took an export datapump of a schema containing partitioned tables.
  
  Now, I'm supposed to import this schema in another data base were partitioning option is not installed, so it must be converted to a table somehow unique bunch.
  
  What are my options to achieve this without having to install partitioning... ?
  
  Thank you!

  Extract the ddl, create the tables (not cut) at the front, and then import data only (or table_exists_action = add).

  Nicolas.

• 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.

• Partition table is corrupted how to fix?

  Hello, I get this error after I turned off my computer (by the button) because it had frozen it had been frozen for 3 hours and I decided to hold it down for 5 seconds (stop the power) and I turned it back and it started. Is there a solution? I get the error message: "Partition table is corrupt on disk \Device\Harddisk0. Repair action: repair of partition result table: failure. Error code = 0 x 490 time: Mrs 160572

  Hello

  With the publication of the description, I understand that you are having problems to start your Windows 7 computer and gets also a errors of Partition table is corrupt on disk \Device\Harddisk0 code = 0 x 490. I will certainly help you get this fixed number.

  I suggest you refer to the suggestions by Stephanie Podder replied on 27 November 2011 in the below mentioned thread and check if this is useful:

  http://answers.Microsoft.com/en-us/Windows/Forum/all/partition-repair-startup-repair-failed-error-code/3af92d1a-e7ef-451D-9adc-3f7ffe8bb9c4?page=1

  Important: Running chkdsk on the drive if bad sectors are found on the disk hard when chkdsk attempts to repair this area if all available on which data may be lost

  Hope this information is useful. Please come back to write to us if you need more help, we will be happy to help you.

• Change the Data Type of column on large partitioned Table Tablet

  Hello

  I was tasked to change a certain NUMBER of collar to a colonel VARCHAR2

  It is usually an easy task, but I ran into several challenges due to the size of the table, the second major problem is the compression of the table.

  To begin with, the Table and index are 4.4 to and hold around 11 lines billion. That the Table is compressed, not the index.

  The first option was to add a new collar of VCHAR, update from the Col de NUM, file and then drop the colonel NUM

  
  

  We ran this test in the Test environment and because discovered Compression Table that you can only mark the column is not used, and it can only be moved permanently from the Table if you unzip the whole Table and run «...» REMOVE the UNUSED COLUMNS'.

  The second way is to create a separate Table copy with the values of the source of neck, then write to null to the source of neck, change data Type when its empty and then update the source again with the copy Table values.

  The second option, that's what I'm testing, but I work with nearly 30 million lines by daily score, inserts take very long to fill.

  How can I make faster inserts between the Source and the copy Table?

  What other channels follow to accomplish the task above?

  Concerning

  Stephan

  Nowhere in your proposed solution was necessary for you to understand why the data source changes, its as simple that to take what is ons the table (all the facts in the original post) and offering the best way on the basis of previous experience or oracle skills acquired over time.

  If you spent so much time and thought to help with a solution that you did on WHY complain, you could have provided some feasible solutions already.

  No thanks to your information irrelevant and unnecessary, I've implemented a solution already.

  1 export the Source Table

  2. create a 'replica Table' using the DDL source using a temporary table name

  3. import all Partitions in the Table new

  4. before the Cut-Over, synchronize the changes from the Source to the replica Table

  5 rename the Source

  5 rename the Table of replica for the Original Source Table name

  6. slide the original Source Table

• 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.

• 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.

• Create index partition in the partition table tablespace

  Hello
  
  I am running a work custom that
  
  * Creates a tablespace by day
  * Creates the daily table partition in the created tablespace
  * Removes the days tablepartition X
  * Removes the storage space for this partition of X + 1 day.
  
  The work above works perfectly, but it has problems with the management of the index for these partitioned tables. In the old database (10g - single node), all indexes and partitions exist in a BIG tablespace and when I imported the table creation script in the new database, I changed all the partitions table & index to go in their respective space.
  
  For example:
  
  Table_name... Nom_partition... Index_Part_name... Tablespace_name
  ============...================............====================...........=================
  TABL1... TABL1_2012_07_16... TABL1_IDX_2012_07_16... TBS_2012_07_16
  TABL1... TABL1_2012_07_15... TABL1_IDX_2012_07_15... TBS_2012_07_15
  
  
  But now, when the job is run, it creates the index in the tablespace TBS_DATA default.
  
  Table_name... Nom_partition... Index_Part_name... Tablespace_name
  ============...================.............====================...........=================
  TABL1... TABL1_2012_08_16... TABL1_IDX_2012_08_16... TBS_DATA
  TABL1... TABL1_2012_08_15... TABL1_IDX_2012_08_15... TBS_DATA
  
  
  I can issue alter index rebuild to move the index to its tablespace default, but how can I make sure that the index is created in the designated tablespace?
  
  NOTE: the partition/tablespace management work that I run only creates the partition of the table and not the index.
  
  
  The new env is a cluster of CARS of 2 nodes 11 GR 2 on Linux x86_64.
  
  
  Thanks in advance,
  aBBy.

  try something like this

  ALTER table tab_owner.tab_name add the partition v_new_part_nm
  values less (to_date('''|| v_new_part_dt_formatted ||'') ((', "DD-MON-YYYY)) tablespace ' | part_tbs
  update the index (ind1_name (partition ind_partition_name tablespace ind_part_tbs)
  ind2_name (partition tablespace ind_part_tbs ind_partition_name))
  ;

• Query on partitioned Table

  I have two partition
  upto_mar_2011, upto_jun_2011
  table_name: order
  1 > if I run the query as below
  Select * command where order_date = to_date (' 23/03/2011 ',' dd/mm/yyyy');
  
  Oracle will automatically search the data in the Partition upto_mar_2011
  or he fetches the data in the entire table.
  
  2 > or I give the query in the form below
  Select * enforcement of partition (upto_mar_2011) where order_date = to_date (' 23/03/2011 ',' dd/mm/yyyy');
  
  Is there a difference between this two query

  OraFighter wrote:

  Is this enough to write as below

  Select * command where order_date = to_date (' 23/03/2011 ',' dd/mm/yyyy')
  or order_date = to_date (' 23/05/2011 ',' dd/mm/yyyy');

  and CBO fetch data, only the partition where it is available.
  Wheather it is spread in a two or three partition
  It will ignore all other partitions automatically

  Fix. 'S called it the size of partition. It is the approach you use to application code. Requests should not be concerned with partitioning - should not need to know the names and other physical attributes of the table physical partition it uses.

  You can also see the size of the partition when looking at such a SQL statement execution plan.

  The only code that will focus on names of partition and the physical aspects of the table's code maintenance. For example, you maintain that a sliding window of 32 days of the date was the partitioned table. This code must determine which partitions are older than 32 days and drop them. And then to add new partitions for future treatment. Copy the following code deals with the physical layer and not the logical layer.

  It is important to keep the two apart and not to mix the physical things in the logical layer which is using the app. He's mixing means that changes to optimize performance and to take advantage of the new features which may not be at the physical layer, as it will break the application layer code.

• 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

• How to encrypt a USB, when I get the message "(GPT) GUID Partition Table partitioning scheme is required? '."

  I just tried to encrypt a USB drive with my Mac book (latest version) and got the message "A GUID Partition Table (GPT) partitioning schΘma required." What does this mean and suggestions on how to proceed?

  The drive must be formatted for Mac. Start in the Recvery mode. Erase the drive using disk utility (select the top icon which represents the entire disk and click clear. Partition scheme must be Mac OS (Extended) first partition GUID, which is the default value.

  If you want to install a system on it follow these steps:

  How to reinstall OS X on your Mac - Apple Support

• Qosmio x 500 - 14W - invalid partition table

  Hay guys,

  I wanted to start my Toshiba Quosmio x 500 - 14W PQX33E (Product Code), but the only thing I found on my desk: invalid partition table.

  In another Forum I found a threat, which means I have to restart my computer. So I tried a Reboot Cd, but found nothing. Then I tried to call the Call Center of Toshiba, but they are closed...

  For me, is the Toshiba Service miserably and I hope that some guys from the Forum can help me.

  Thank you
  Paul

  Hello

  You must install the operating system once more.
  Invalid partition table means that something is wrong with the HARD drive and the operating system cannot start.
  So if you n t have a recovery disk, you must order one:
  http://backupmedia.Toshiba.EU/landing.aspx

  PS: I made good experience with the Toshiba service comparing the service with another laptop from the manufacturer I have to say that s OK and I meet a lot of people who said that other manufacturers are not really better
  Which; s my opinion

• 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.

• invalid partition table

  invalid partition table is displayed on my screen, pl help out me...

  Exactly what happened before you saw the error message?