Move a partition

Win 8.1 Pro
I had to replace my hard drive in my laptop. I chose a larger SSD drive as its replacement. System Image backup worked and restored the old disk onto the new one. The laptop (Lenovo) has a hidden partition at the end of the old drive (Lenovo_Recovery).
When I replaced a drive in the past with a larger drive, I just went to disk management and extended the drive. However, in this case , the extension went to the hidden partition.
My question:
1. How can I extend the primary "C" partition which comes before the hidden partition?
2. Can I move the hidden partition to the end of the drive? How?
Thanks
John Lenz

I found and purchased Partition Manager. I applied the move & resize.
John Lenz

Similar Messages

How to move a partitioned table

Hi,
i have a partitioned table where i am inserting records using direct-path and deleting records( no conventional load) . Now coz of deletions there are many blocks that are free below High Water Mark. so it thought of moving table from one tablespace to another tablespace. And when i treid to do that it gave an error and i found that i cant mov a partitioned table. i can move only partitions. and the table has 60 partitions. So can anyone help me in this? ANy other way to reclaim those free space below HWM? i am in 9i R2
Thanks in advance

Did you try "shrink" command??
Rgrds,
Paulo Portugal.

Copy / Move / Migrate partition within VHD to another VHD(X)?

I inherited a VM with a single VHD that contains three partitions 100 MB System, 250 GB C:, 750 GB D:. The C: drive has 40 GB maybe on it and is wasted space mostly. I wanted to move the 750 GB partition to its own VHD and then shrink the original VHD.
Is there an easy way to move a partition from one VHD to another? I know I can move the entire VHD to another but can I do a portion based on partition?

Hi Brian,
How are things going ?
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How do I move a partition on my mac hard drive, to an external hard drive so that i can run windows when the external hard drive is connected

How do I move a partition on my mac hard drive, to an external hard drive so that i can run windows when the external hard drive is connected

Are you talking about a Bootcamp partition? You can't boot Windows from an external drive.

How do I move a partition using Windows 7?

I have a relatively new computer that runs on Windows 7 (W7). This is my first experience with a Windows OS newer than XP. On systems running XP and older operating systems I was in the habit of using OEM tools for partition management.
This particularly included Partition Magic and GParted. I have a strong preference for partitioning the hard drive into multiple partitions in order to separate the software, from the user data, and the temporary storage files. I'm also in the
habit of running more than one operating system partition. This would include both different operating systems as well as as different instances of the same operating system.
It looks to me like W7 includes more and possibly better partition management software than XP and earlier versions of Windows. One of the fundamental tasks is the need to move partitions around on a drive. Partition management software typically
has resizing capability. I'm accustomed to using such tools where you can either reduce or enlarge the size of the partition. The parameters that you need to supply include the amount of free space that you want to end up with both before and after
an existing partition. It looks like the W7 tools only allow you to specify the size that want when the operation is complete. They do NOT seem to allow you to precisely specify where the resulting partition ends up being located. It sort
of sounds like the resulting partition is always going to start at the same location, which means that these tools don't let you relocate the partition. If so that is most unfortunate and represents a serious deficiency.
Is there something I'm missing? In that, is it possible to move partitions? If W7 cannot do it are there recommended OEM tools with such capability? In that, is there a substitute for Partition Magic?

Hi,
In Windows 7, you can use Disk Management to locate your disk partition. In addition, you can also use Diskpart command in CMD console to allocate the partition.
Please refer to the conents of the link below for more details:
http://support.microsoft.com/kb/300415
Roger Lu
TechNet Community Support

How To Move Recovery Partition in between System & Data Partition To Extend System Partition?

Hello, I have recently purchase an ASUS S400CA Ultra Notebook and the hard drive has 1)EFI Partition & 3) Recovery Partitions with one of the recovery partitions being in between C:/ System & D:/Data partition. I am wanting to delete the D:/Data
partition to extend and maximize the C:/ System partition, but I am not familiar with how to do so with this recovery partition in between them.
Is there a way that I can move or copy the recovery partition that is in between C:/ & D:/ to the other side of D:\, delete the old recovery partition location and D:/ partition, then extend C:/ without destroying the recovery partition or any links,
etc. for the recovery partitions???
I do not want to delete any recovery partitions, only my D:/data partition because my C:/system partition is too small and I don't want to have to manually balance
my data & programs between the 2 partitions!
I just need to find a way that will allow me to move or copy this recovery partition that is in between C:/ & D:/ to the other side(right) of D:\, so I can delete its old recovery
partition location and the D:/ partition, then extend C:/ without destroying the recovery partition and / or any links, etc. for the recovery partitions???
I tried to provide a picture / screen shot of Disk Management, but the site wouldn't allow it because it needed to verify my account that I've had here for a long time! Go
figure!

Hi,
To verify your account, please refer to
http://social.msdn.microsoft.com/Forums/en-US/5a35b6c8-7a1a-4dc9-9b28-be69c55afb96/verify-your-account-13?forum=reportabug
Meanwhile, please upload the screenshot.
Regards,
Kelvin Xu
TechNet Community Support

Tablespace move in partitioned tables

I moved partitioned tables in new tablespace dedicated for 2006 data, do i need to move table relaed indexes in new tablespace also.?

No,
global Indexes will be invalid and have to be rebuild. If you have local Indexes you only have to rebuild the affected partitions. Nothing else to do.
Dim

How to move a partition to the top of Disk Utility pile?

I had Lion and SL installed in two separte partitions. But since I didnt like Lion I decided to erase Lion's partition and then fuse the free left space with the SL partition so I could have more HD space. The thing is disk utility only alows to expanded downwards from the down border of the partition. As you can see I've got tons of free space above Macintosh HD 2. 224GB. I want to move Macintosh HD 2 up so then I can expand it to "catch" all that free space. Do I make any sense? I don't want 2 Partitions, just one! With SL. But I can't expand it up only down
Please help guys Its killing me... didnt find any solution to this particular problem here.
Thanks in advanced
- Tiago

Like Neil said, you have to clone your SL off to a external drive, option boot from it, format the internal drive again so it's one partition, then reverse clone SL back onto it.
Doing it all on the same drive is rather risky and might not be possible if the second partition is larger with data than the first. A clone on a external drive will also give bootable backup in case all heck breaks loose.
Important thing is that the entire drive is erased, (select the Toshiba, Western Digital, or Seagate internal "media" on the far left side) as there is a hidden Lion Recovery partition that also needs to be removed.
So you really have 3 (actually 4 counting EFI partition) partitions on your boot drive if Lion is installed so you need to reduce that to two (SL and the hidden EFI, Disk Utility creates)
It's easier than it sounds really, make sure all other drives, media is removed so there are no accidents.
1: get a blank external drive, use Disk Utility to Erase Security Option > Zero All Data and format 1 partition, Option: GUID OS X Extended in the Partition Tab.
2: free Carbon Copy Cloner to clone internal SL to external (default settings are fine for first clone)
3: hold option boot the external SL drive, use Disk Utility (on the external drive!) to erase the whole internal drive media
4: use CCC to reverse clone onto the internal drive
5: use free Onyx and run ALL maintainence and cleaning aspects and reboot at the end when finished (cleans up caches, makes your machine run faster)
http://www.titanium.free.fr/
You can learn all how to do that in my huge thread here
https://discussions.apple.com/message/16276201#16276201

How to move recovery partition to sd and where are the bios upates?

Hi,
Im a newbie. Firstly how do I move the recovery partition to my micro sd? Secondly, when I try to find support drivers, bios updates etc, the encore doesn't appear as an option, it only list notebooks!
Tia
Olly

I need some help with this also. The Toshiba utility Create Recovery Media won't back the recovery partition up to an SD card. It wants a USB drive. Why in the world would a tablet back up to a USB device when it only has an SD card?. I've seen some extremely laborious processes to create another kind of recovery partition. I'm out of space on my 32GB Encore and I need to get the recovery partition off of the C: drive. Help anyone...??? Thanks!

Move non-partition to Partition with order by cluse

Hi,
I have non partition table of around 9GB and want to convert it into Partiiton table. Following is the des:
SQL> select num_rows,blocks from dba_tables where table_name='DEMAND_DRAFT_STATUS';
NUM_ROWS     BLOCKS
21720123    1228647
SQL> select index_name,index_type from dba_indexes where table_name='DEMAND_DRAFT_STATUS';
INDEX_NAME                     INDEX_TYPE
SYS_C0011138                   NORMAL
IDX_DEMD_DRFT_STAT_INSERTED_BY BITMAP
IDX_DEMD_DRFT_STAT_UPDATED_BY BITMAP
SQL> select clustering_factor from dba_indexes where index_name='SYS_C0011138';
CLUSTERING_FACTOR
        387978241
SQL> select column_name,column_position from dba_ind_columns where index_name='SYS_C0011138';
COLUMN_NAME
COLUMN_POSITION
ISSU_BR_CODE
              1
ISSU_BANK_CODE
              2
ISSU_EXTN_CNTR_CODE
              3
COLUMN_NAME
COLUMN_POSITION
DD_NUM
              4
ISSUE_DATE
              5
DD_CRNCY_CODE
              6
COLUMN_NAME
COLUMN_POSITION
OT_TYPE
              7
PRODUCT_CODE
              8
CURRENCY_CODE
              9
9 rows selected.
SQL> desc DEMAND_DRAFT_STATUS
Name                                                                                                              Null?    Type
ISSU_BR_CODE                                                                                                      NOT NULL VARCHAR2(6)
ISSU_BANK_CODE                                                                                                    NOT NULL VARCHAR2(6)
ISSU_EXTN_CNTR_CODE                                                                                               NOT NULL VARCHAR2(2)
DD_NUM                                                                                                            NOT NULL VARCHAR2(16)
ISSUE_DATE                                                                                                        NOT NULL DATE
DD_CRNCY_CODE                                                                                                     NOT NULL VARCHAR2(3)
OT_TYPE                                                                                                           NOT NULL VARCHAR2(2)
PRODUCT_CODE                                                                                                      NOT NULL VARCHAR2(5)
CURRENCY_CODE                                                                                                     NOT NULL VARCHAR2(3)
DD_STATUS                                                                                                                  CHAR(1)
DD_STATUS_DATE                                                                                                             DATE
DD_AMT                                                                                                                     NUMBER(20,4)
DD_REVAL_DATE                                                                                                              DATE
PRNT_ADVC_FLG                                                                                                              CHAR(1)
PRNT_RMKS                                                                                                                  VARCHAR2(50)
PAYEE_BR_CODE                                                                                                              VARCHAR2(6)
PAYEE_BANK_CODE                                                                                                            VARCHAR2(6)
PAYING_BR_CODE                                                                                                             VARCHAR2(6)
PAYING_BANK_CODE                                                                                                           VARCHAR2(6)
ROUTING_BR_CODE                                                                                                            VARCHAR2(6)
ROUTING_BANK_CODE                                                                                                          VARCHAR2(6)
INSTRMNT_TYPE                                                                                                              VARCHAR2(6)
INSTRMNT_ALPHA                                                                                                             VARCHAR2(6)
INSTRMNT_NUM                                                                                                               VARCHAR2(16)
PUR_NAME                                                                                                                   VARCHAR2(80)
PAYEE_NAME                                                                                                                 VARCHAR2(80)
PRNT_OPTN                                                                                                                  CHAR(1)
PRNT_FLG                                                                                                                   CHAR(1)
PRNT_CNT                                                                                                                   NUMBER(3)
DUP_ISS_CNT                                                                                                                NUMBER(3)
DUP_ISS_DATE                                                                                                               DATE
RECTIFED_CNT                                                                                                               NUMBER(3)
PAID_EX_ADVC                                                                                                               CHAR(1)
ADVC_RCV_DATE                                                                                                              DATE
BC_FLG                                                                                                                     CHAR(1)
ENTERED_BY                                                                                                                 CHAR(1)
CAUTIONED_STAT                                                                                                             CHAR(1)
CAUTIONED_REASON                                                                                                           VARCHAR2(50)
PAID_ADVC_FLG                                                                                                              CHAR(1)
INVT_SRL_NUM                                                                                                               VARCHAR2(16)
PRNT_REM_CNT                                                                                                               NUMBER(2)
INSERTED_BY                                                                                                                NUMBER(10)
UPDATED_BY                                                                                                                 NUMBER(10)
INSERTED_ON                                                                                                                DATE
UPDATED_ON                                                                                                                 DATE
DEL_FLG                                                                                                                    CHAR(1)
LCHG_TIME                                                                                                                  DATE
RCRE_TIME                                                                                                                  DATE
BUSINESS_DATE                                                                                                              DATEFollowing questions:
1) I want to Range partition by ISSUE_DATE (there is no issue), but i'm thinking of reordering the column of index i.e 'SYS_C0011138' (which is also primary key). For example low cardinality columns i will place first and high selective column i would place at last in order. Is that a good idea?
2) While creating Partition table i want to give insert /*+ parallel 10 */ into partitiontable select * from DEMAND_DRAFT_STATUS order by CURRENCY_CODE,DD_CRNCY_CODE,PRODUCT_CODE,OT_TYPE,ISSU_BANK_CODE,ISSU_EXTN_CNTR_CODE,ISSUE_DATE,ISSU_BR_CODE,DD_NUM;
Why i'm doing this because index is going to be created on CURRENCY_CODE,DD_CRNCY_CODE,PRODUCT_CODE,OT_TYPE,ISSU_BANK_CODE,ISSU_EXTN_CNTR_CODE,ISSUE_DATE,ISSU_BR_CODE,DD_NUM columns so clustering factore os that index would be good(this is primary key index btw). Is it good?
3) Once partition is done i want to compress the old partitions, but i'm bit worried that i wont get enough compress ratio if i create partition table with ORDER by clause. whats your thought?
Please give recommendation
Regards

rp0428 wrote:
>
whats your thought?
>
Your post raises nothing but questions about WHY you are doing any of this. We can't suggest appropriate solutions without knowing what the problems are or what goals you are trying to achieve.
>
I have non partition table of around 9GB and want to convert it into Partiiton table
>
Ok - but WHY? Are you currently having problems? What are they? Is performance poor? For what type of queries or operations? Is management a problem - can't easily roll-off old data?
>Well its management decision to partitions the table which are expected to have high size in future. There reference of 6GB i gave only for explanation, actually we have 2-3 tables which are 500+GB and will grow.
Its a DWH environment where daily incremental load happens. So we came out of decision to have tables(which have daily incremental load) partitioned on monthly basis. And keep last quatat partitions on Cell Flash cache(its exadata)
CLUSTERING_FACTOR
387978241
>
Yep - that is a high factor for 1.2 million blocks. But are you sure it is correct? It's 17 times greater than the number of rows in the table. That suggests that to read the entire table using the index every block has to be read 17 times. That doesn't make sense - odds are the table and index stats you provided are not current.
Yes thats seems to be correct figure. I'll check once again and post..
>
And it has this quote from Tom Kyte's book Expert Oracle Database Architecture
>
we could also view the clustering factor as a number that represents the number of logical i/o’s against the table, that would be performed to read the entire table via the index.
>
Even assuming that index has a high clustering factor the next question is:
So what? That would only be relevant if you are using that index to access the entire table or large numbers of blocks.
Is there a problem you are having that you can identify the clustering factor as the main culprit?
If it ain't broke, don't fix it.
>Yes that correct but clustering factor worry me much after seeing its value which is very high as compared to # of blocks.
1) I want to Range partition by ISSUE_DATE (there is no issue), but i'm thinking of reordering the column of index i.e 'SYS_C0011138' (which is also primary key). For example low cardinality columns i will place first and high selective column i would place at last in order. Is that a good idea?
>
Range partitioning by a date can be useful so lets just assume it is in your case; maybe you are thinking about dropping old data. Is your primary key going to be global or local? That will affect performance if you drop old partitions; the global index has to be maintained but the local one doesn't.
I'm not going to drop any partitions of old data as of now but will compress them because they wont anticipate DMLS.(but might be select)
Now the question is about Primary key > wll it be Local of Global? Well i thought of having this Key as Local(because one of my primary key column will contain the partition key as well).
Reasons
1) better manageability( like if i want to compress old partitions, then having a gloabl parimary key index would become unusable state)
2) Might increase in select search criteria (assumption)
But having this as local will it impact any performance?
The primary key does include the partitioning column so it could be a local index. But the partitioning column is not the leading column so this would be a local nonprefixed index. Is that what you need or do you need prefixed index?
Have you researched the difference and determined which one you need for your use case?
No. My partition Key would not be in leading column of Primary key. But is there any difference if i not keep partition key as leading column of primary key?
See Local Partitioned Indexes in the VLDB and Partitioning Guide
http://docs.oracle.com/cd/B28359_01/server.111/b32024/partition.htm
Is rearranging the key columns a good idea? Hard to say without knowing your usage pattern.
Why are you reordering the primary key columns? Why are you putting low cardinality columns first?Well i have read some where quite lot times that having Low cardinality columns as leading coluns would increase performance and later we can get better compression ratios. Let me know if i'm wrong.
You shouldn't be doing either of these without a solid reason. What are the reasons? How do you know that, for your usage pattern, you won't make things worse?
>
2) While creating Partition table i want to give insert /*+ parallel 10 */ into partitiontable select * from DEMAND_DRAFT_STATUS order by CURRENCY_CODE,DD_CRNCY_CODE,PRODUCT_CODE,OT_TYPE,ISSU_BANK_CODE,ISSU_EXTN_CNTR_CODE,ISSUE_DATE,ISSU_BR_CODE,DD_NUM;
Why i'm doing this because index is going to be created on CURRENCY_CODE,DD_CRNCY_CODE,PRODUCT_CODE,OT_TYPE,ISSU_BANK_CODE,ISSU_EXTN_CNTR_CODE,ISSUE_DATE,ISSU_BR_CODE,DD_NUM columns so clustering factore os that index would be good(this is primary key index btw). Is it good?
>
That should give a good initial clustering factor for the index unless a lot of DML is done.
>
3) Once partition is done i want to compress the old partitions, but i'm bit worried that i wont get enough compress ratio if i create partition table with ORDER by clause. whats your thought?
>
You are probably correct since having the low cardinality data first will break things up more. But you are still trying to solve a problem that you don't know even exists. How much space will each partition take if uncompressed? How much if compressed?
At a minimum you should perform a tests for a realistic subset of data (a sample issue date).
1. Create an unordered uncompressed table (new tablespace to make size data more accurate).
2. Create an unordered compressed table
3. Create an ordered uncompressed table
4. Create an ordered compressed table
Yes i have tries to simulate this for 9GB table(only) and size of unordered compressed table is 1.2GB and size of ordered compressed table is 1.9GB out of 9B(uncompressed)
Then you will have a good idea what the space savings might be.
I suggest you first document the issues and problems you are having and list specific goals for any architecture changes.
For partiioning I would focus on identifying the goals, the partition key(s), and the numbers and types (global or local) for the primary key and other indexes.
Application team have already identified the Partitions key on tables which are supposed to be partitioned And they say most of the queries are on those date columns. Secondly as i explained having partition we will keep old partition in compressed state and new partitions in Cell flash cache.
For the primary key index (that includes the partitioning key) determine if you need a prefixed or nonprefixed index.
again whats the difference if i dont have partition key column in leading column of index?
Based on your usage patterns determine the indexes and columns that are the most important for querying. The clustering factor might be ideal for the primary key but totally screwed up for the indexes and queries that really count. You can't get an ideal clustering factor for every index.
The data order for the initial load can be in the order that gives you the best clustering factor for the main index you need it for. That assumes that you actually need the index for a purpose that the clustering factor can help with.Thanks a lot your explanation was helpful.
This setup for tables (i.e. having high # of columns in primary key for example 6-7 out of 15 columns approx in a table) is common for mostly all of the tables which are going to be partition.
And most of the columns in parimary key have 2-3 distinct values out of 1Million rows, so was about to think that i should put them ahead while creating a new primary key (Local) on newly created partition.
While doing this i also take into consideration that i load the data in ORDER BY clause (i.e. order by all columns of PK) to get excellent CF and moreover we could benefit from Storage Index on Exadata. and thanks for inputs too highly appreciated

Best Method to Move Partitioned Data to Another Server

Hi,
In our company we have a monthly maintenance to move one partition from many partitioned tables to another server. I want to know what is the following:
1- Best way to do this task and to move table partitions to another database on another server?
2- When I delete table partition, do I need to analyze the table or rebuild the indexes?
Appreciate your prompt response.
Thanks

2- When I delete table partition, do I need to analyze the table or rebuild the indexes?What do you mean by delete table partition? If you mean truncate or drop parition then you should use "UPDATE GLOBAL INDEXES" clause in order to avoid rebuilding global indexes as shown in the below examle:
create table TAB1 ( Value number(10))
partition by range(value)
partition p1 values less than (10),
partition p2 values less than (20),
partition p3 values less than (30),
partition p4 values less than (40),
partition p5 values less than (50)
insert into tab1
select rownum
from dual connect by rownum < 50;
commit;
create index tab1_indx1 on tab1(value);
sql> select index_name, status
2 from user_indexes
3 where index_name = 'TAB1_INDX1';
INDEX_NAME                     STATUS
TAB1_INDX1                     VALID
sql> alter table tab1 drop partition p2 UPDATE GLOBAL INDEXES;
Table altered.
sql> select index_name, status
2 from user_indexes
3 where index_name = 'TAB1_INDX1';
INDEX_NAME                     STATUS
TAB1_INDX1                     VALID
sql> alter table tab1 drop partition p3;
Table altered.
sql> select index_name, status
2 from user_indexes
3 where index_name = 'TAB1_INDX1';
INDEX_NAME                     STATUS
TAB1_INDX1                     UNUSABLEMohamed Houri

Parent partition of subpartitions that move to a new TS

PLATFORM_NAME: Solaris[tm] OE (64-bit)
VERSION: 11.2.0.2.0
In our system we have several tables that are partitioned by range. Some of these tables are then sub-partitioned by list. Well initially we were creating a new tablespace every month and creating the new monthly partition on the new tablespace. Well I got annoyed by this, so I decided to move all of the partitions/subpartitions to a single tablespace. And this went smooth, at first, in my dev region. I moved all of the segments to the new tablespace, but then I noticed something odd...
Example:
CREATE TABLE me.sub_partitioned_table
my_range_partitioned_column date,
my_list_partitioned_column varchar2(30)
PARTITION BY RANGE (my_range_partitioned_column)
SUBPARTITION BY LIST (my_list_partitioned_column)
SUBPARTITION TEMPLATE
(SUBPARTITION value4 VALUES (4),
SUBPARTITION value23 VALUES (23),
SUBPARTITION value60 VALUES (60),
SUBPARTITION "DEFAULT" VALUES (DEFAULT)
PARTITION P_HIST VALUES LESS THAN (TO_DATE(' 2007-09-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLESPACE P_HIST
( SUBPARTITION P_HIST_value4 VALUES (4) TABLESPACE MONTHLY_PARTITION,
SUBPARTITION P_HIST_value23 VALUES (23) TABLESPACE MONTHLY_PARTITION,
SUBPARTITION P_HIST_value60 VALUES (60) TABLESPACE MONTHLY_PARTITION,
SUBPARTITION P_HIST_DEFAULT VALUES (DEFAULT) TABLESPACE MONTHLY_PARTITION ),
...... and there are a lot more partitions/subpartitions
So I create all of my alter table move subpartition statements, and the execute as they should. If I do:
select tablespace_name from dba_tab_subpartitions where table_name = 'SUB_PARTITIONED_TABLE' and table_owner = 'ME', I see that all of my subpartitions are on the new, single tablespace. BUUUUUUT, if I do:
select tablespace_name from dba_tab_partitions where table_name = 'SUB_PARTITIONED_TABLE' and table_owner = 'ME', I see all of the old tablespace names are still listed for my partitions.
My question is, can this be changed? Did I screw something up? Is this a bug? If I try to alter the table and move the partition I get an error because I'm trying to move something that isn't a segment. Any help would be appreciated. Hopefully this makes sense. If you need clarification on anything, please let me know.
Thanks!

I found my answer...
ALTER TABLE ME.sub_partitioned_table MODIFY DEFAULT ATTRIBUTES FOR PARTITION MONTHLY_PARTITION TABLESPACE NEW_BIG_TS;

T530 - Move boot "SYSTEM_DRV" partition?

Hi all,
I just bought a WD Blue 1TB drive to replace the stock 320GB HDD in my T530. I have Win7 installed on a 256GB mSATA SSD. However, when I swap the drives out, BIOS recognizes both drives but the laptop doesn't boot - from the HDD or the SSD.
I suspect this is related to the mysterious "SYSTEM_DRV" partition on my 320GB HDD. I've contemplated changing the partition tables and copying this partition to a similar-sized partition on the SSD but I have a bad feeling about messing with partition editors when I'm not exactly positive what I'm doing. I have a set of recovery discs from when I first set up the computer, but AFAIK this will restore the laptop to "factory settings" i.e. a configuration that doesn't boot from the installed SSD.
I haven't really tried anything drastic because I figured I'd consult the forum before doodling with my partitions or trying a fresh install of Windows. Is there any way I can (safely) move this partition so it can boot entirely from the mSATA SSD?
-edit: it should also be noted that I tried to reimage the drive using DriveImage XML, but it doesn't recognize the "SYSTEM_DRV" partition, otherwise that would have seemed failsafe. Is there a tool I need to use that isn't "warm", like a bootable disc?
Solved!
Go to Solution.

no need for gratitude. we're here to help!
T530: i7-3630QM, 4 GB DDR3-1600, NVS 5400M, 2x 500GB 7200RPM, 9-cell, HD+ 1600x900, Backlit US, WinXP Pro
L430: i3-2370M, 4 GB DDR3-1600, HD 3000, 320GB 7200RPM, 6-cell, HD 1366 x 768, Win7 Home Premium 64-bit

Small problem in table move

The base table was created in a DMT and all the partitions were created in LMT.
Now i want the table also to be in LMT.
When attempted a move with alter table tablename move tablespace it's giving an error.
SQL> ALTER TABLE HOLDINGDBO.POSITION_STAGE MOVE TABLESPACE HOLDING_GEN;
ALTER TABLE HOLDINGDBO.POSITION_STAGE MOVE TABLESPACE HOLDING_GEN
ERROR at line 1:
ORA-14511: cannot perform operation on a partitioned object.

ORA-14511: cannot perform operation on a partitioned object.Of course it can't. The move clause targets a segment. Alas, the top level object (table) here, does not have any segment. Hence you can't move a partitionned table as a whole.
Instead just look at the alter table move partition statement in TFM.
e.g.:ALTER TABLE HOLDINGDBO.POSITION_STAGE MOVE PARTITION POS_OLD TABLESPACE HOLDING_PTS_OLD;Regards,
Yoann.

After table partition, some transactions hang

I am running SAP 4.6 and Oracle 10.2
I recently used online reorg to partition table DFKKOP (over 100 million records) into two parts. One partition was for "closed" orders, and the other was for "open" orders (less than 2% of the rows).
Since most of the queries against this table were against open orders, access times improved dramatically (one query went from 20 minutes to 20 seconds).
Unfortunately, while it was on a test system, our developers discovered that this caused transactions FPL9 and CIC0 to hang. To prove that it was the partition causing the hang, we used our "snapback" ability to return the database to the point in time prior to the partition (we did this twice), and the problem disappeared. Other than these hangs, the database seemed to work normally.
Does anyone have an idea why this might be happening? BTW - I had "row movement enabled", so that's not it. I have found nothing in SAP notes or on this forum.
Thanks.

>
Sandeep Pasumarti wrote:
> i am also thinking of partitioning a large table - custom table - that we use instead of glpca.. it is 40gb..would you happen to have a how-to approach in doing that? how did you handle the abap dictionary side? - or do you just do on oracle...thanks!
>
> ps i was thinking on doing something fiscal year.. or acct number range...not sure how i could partition FY for years moving forward...meaing fy 2002 is one partition, 2003 is another, etc...
Hi Sandeep,
Partitioning is a really cool feature - but it must be valued against your primary goal you want to achieve.
it has an influence WICH partitioning method you have to use AND wich partitioning keys you have to find.
If you see it like a triangle you can have these goals:
Performance
Administration Availability
you will hardly achieve all three (wich means you generate some overhead for the other goals).
It may that you are in a corner of one goal - see the location of (*)
Our goal was improve write performance (in the 1st place):
We did it on a SAP BW system on our own Z tables wich were growing bigger and bigger ( several hundreds of GBytes). As we debugged how BW itself managed the partitions we used this and a little ABAP to maintain the partitions for our own tables.
Our's was range partitioning with an Identifier (INT4) used as a sequence to flagg present and historical calculations as a partition key. We could now TRUNCATE the partitions instead of DELETE (the UNDO generation blew up our batch time window for computations of figures).
And yes we benefit from partion pruning - as far you had a lot of full table scans wich are now turned into partition scans. Index accesses benefit not that muxch from paritioning - but it reallly depends on your application HOW it uses the data.
All your queries should use the partition key as a criteria (in your case FISCYEAR) - otherwise you make things worse.
Be aware that you have to use the right data type (imagine a range partiton on a Varchar2 column
like the NUMBER data type in SAP tables) and evaluate it carefully against the partiton type you choose.
There are some pitfalls like moving partition keys (wich you have to avoid ).
There is the overhead of creating / dropping/ merging partitions and who is responsible for it (in our case
the application and not an SAP admin).
Maintain all indexes as local
You can use BRSPACE to partition the table , with your 40 Gybte SE14 could be also used as you can define the partitions (hopefully you are at least on a 6.20 system).
For our system it was essential
1) to fully understand the concept of partitioining (seems obvious, but guess where things most fail)
2 that it is supported by standard SAP tools (as in SE14 or BRSPACE)
3) to write an interface to handle the partitioning without involving a DBA
(imagine you have a process chain that uses your partition table and you have to provide a new partition while running the chain).
We run it now for more than a year and it was a good decision to move to partitioning.
Now we will extend the feature and use it for archivals on a partition basis.
Bye
yk

Move a partition

Similar Messages

Maybe you are looking for