Migration to a new transportable tablespace partition table

Similar Questions

• Move the data from the partitions again tablespace - direct table filled by ETL

  Hello

  We have a large composite table date-range/hash partitioned table (using time partitioning 11.2.0.3 range)

  1 partition for each month and each such partition 4 under separate partitions.

  We want to move some data from most significant storage but also direct table and inserted in all the days as part of the data warehouse and large table want to ensure

  operations below result in errors in the data loading procedure

  Suppose also should not take long to run lines 40 million or more each month.

  Select *.

  Of user_tab_partitions

  Where table_name = 'CUSTOMER_TRANSACTION '.

  And nom_partition like 'SYS % '.

  1. (1) Alter table retailer_transaction and rename partition < nom_partition > CUST_PART_ < YYYYMM >
  1. (2) tablespace create dedicated for the month of the affected partition
  1. ((3) alter table retailer_transaction move tablespace subpartition < sys... > < partition_tablespace > created in 2) above

  ALTER table retailer_transaction change the default attributes for the partition < CUST_PART < YYYYMM > < tablespace in 2 above > tablespace)

  4 global index which would eventually rebuild afterwards due to the transition if movement makes no valid.

  Several local bitmap indexes that belong to partitions.

  Thoughts?

  Thank you

  I agree in a good store of data, everything should be according to the best practices ETL or guideline. I guess it is a FACT table, because it's big enough. A method that I can share (followed in the real world big DW) is "ELP" IE Partition Exchange loading. You can find the basic architecture of the Internet.

  The basic architecture is as

  The source (in your case partitioned) Table--> (unpartitioned) intermediate Table--> Table possible target (partitioned)--> the cleaning activities (and overtime).

  You can use any ETL tool for this (I won't mention any other reasons).

  Later, you can delete the original table and use that new table as your FACT table, your application will be available all the time. There are drawbacks as most uses of double-spaced, other than normal ETL these work will take certain amount of resources so that other ALS etc. In addition, if you load a few current days during these activities you plan / program accordingly.

  Your demo is also fine, but regular ETL may fail because you rename the partitions (some uses of ETL tool partition name, in case you ever ELP) also unusable global indexes can cause failure (you have local too?).

• 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))
  ;

• Why a transportable tablespace for the migration of the platform in the same endian format?

  RDBMS version: 10.2.0.4
  
  We intend to migrate our database to another platform. The two platforms are in BIG endian format. Search on Google, I came across the following link
  http://levipereira.files.WordPress.com/2011/01/oracle_generic_migration_version_1.PDF
  
  In this IBM paper, they migrate to AIX 6 of 5.9 on Solaris (SPARC). Both are BIG endian format. Since both are the same size endian can they use TRANSPORTABLE database? Why use RMAN COVERT DATAFILE (Transportable tablespace)?

  In this IBM paper, they migrate to AIX 6 of 5.9 on Solaris (SPARC). Both are BIG endian format. Since both are the same size endian can they use TRANSPORTABLE database? Why use RMAN COVERT DATAFILE (Transportable tablespace)?

  they use portable database - that they do not import data to the dictionary, not creating users--rather than use data conversion, they used convert datafile to avoid to convert all the data files (you will need to convert only cancel + system tablespace)-there are MOS Note: avoid Conversion Datafile during the transportable database [732053.1 ID].

  Basic steps to convert database:
  1. check the prerequisites
  2. identify the directories and external files with DBMS_TDB. CHECK_EXTERNAL.
  3. (coherent) stop and restart the database source in READ ONLY mode.
  4. use DBMS_TDB. CHECK_DB to ensure that the database is ready to be transported.
  5. run RMAN convert database command.
  6 copy the files converted into the target database. Note that this implies that you will need 2 x the storage on the database source for converted files.
  7 copy the parameter in the target database.
  8. set the configuration files as required (setting, listener.ora and tnsnames, etc.).
  9 start the new database!

  All other details are:
  http://docs.Oracle.com/CD/B19306_01/backup.102/b14191/dbxptrn.htm#CHDFHBFI

  Lukas

• Adding a new partition to a partitioned table

  Hi all
  
  I try to add a new partition to an existing table in compartmentalized but I need the new partition of 'table' to go to tablespace DATA_2011 and partition "index" to go to INDEX_2011. I tried but it wrong on what follows.
  
  CREATE TABLE employees
  (employee_id number 4 NOT NULL,
  last_name VARCHAR2 (10),
  department_id NUMBER (2))
  PARTITION OF RANGE (department_id)
  (PARTITION employees_part1 VALUES LESS THAN (11) TABLESPACE DATA_2010,)
  PARTITION employees_part2 VALUES LESS THAN (21) TABLESPACE DATA_2010;
  PARTITION employees_part3 VALUES LESS THAN (31) TABLESPACE DATA_2010);
  
  CREATE INDEX employees_local_idx ON employees (employee_id) LOCAL
  (PARTITION TABLESPACE INDEX_2010 employees_part1,
  PARTITION employees_part2 TABLESPACE INDEX_2010,
  PARTITION employees_part3 TABLESPACE INDEX_2010);
  
  
  Here's what I'm trying to run but it fails...
  ALTER table employees add PARTITION "EMPLOYEES_PART4" VALUES LESS THAN (41) DATA_2011 index tablespace tablespace INDEX_2011;
  
  ERROR on line 1:
  ORA-14020: this physical attribute may not be specified for the partition table
  
  
  
  Succeeds what follows, but in this case the index partition "EMPLOYEES_PART4" is also assigned to DATA_2011 tablespace.
  
  ALTER table employees add PARTITION "EMPLOYEES_PART4" VALUES LESS THAN (41) tablespace DATA_2011;
  
  
  Any ideas... I am currently looking in the documentation to see if it would be possible?
  
  Thanks for your time...

  Hello

  ALTER table employees add PARTITION "EMPLOYEES_PART4" VALUES LESS THAN (41) tablespace DATA_2011;

  The foregoing is the corect order and therefore succeeded.

  but in this case the index partition "EMPLOYEES_PART4" is also assigned to DATA_2011 tablespace.

  You need rebuild the index of the partition with the name desired tablespace. /

  ALTER index rebuild partition tablespace

  Anand

• migration in partitioned table

  Hello world
  
  I need to migrate on a two table range-list partitioned table, one of them is partitioned list, the other is not. The largest contains 400 million lines (partitioned), the smallest contains 90 million lines. The database cannot insert all of the table at a time, so I started to migrate the tables into pieces. I have two options:
  
  1 create pieces using a date_field (IDO_ID)
  2. create the pieces with the help of a generated field (MIGR_RANK) using the list field (TAB_KOD) and a number generated randomly, which limits the lines to migrate a line no more than 1 million of partitioning
  
  My questions are the following:
  1. is it possible that the insert is slow due to the large number (about 750) list partitions? Can I use the 2. method, inserting only one partition? Or a kind of simple is enough for partitioning columns? How does the insert works in Oracle for a partitioned table? Especially in a range-list partitioned table?
  2. How can I adjust the database to migrate two tables in one step (if possible)?
  
  Thanks in advance,
  Gabor
  
  Published by: csiszgab on Sep 28, 2012 07:47

  Whenever you provide post your Oracle version 4-digit (result of SELECT * FROM V$ VERSION).
  >
  I need to migrate on a two table range-list partitioned table, one of them is partitioned list, the other is not. The largest contains 400 million lines (partitioned), the smallest contains 90 million lines. The database cannot insert all of the table at a time, so I started to migrate the tables into pieces. I have two options:
  >
  -Oracle is certainly able to process the entire table in one so why do you say otherwise?

  You can speed up insert PARALLEL aid (for the source and target tables), using the direct-path load (APPEND indicator) and NOLOGGING mode on the target table.
  >
  1. is it possible that the insert is slow due to the large number (about 750) list partitions? Can I use the 2. method, inserting only one partition? Or a kind of simple is enough for partitioning columns? How does the insert works in Oracle for a partitioned table? Especially in a range-list partitioned table?
  >
  Your "2" is not just insert in a partition. You said your target table was partitioned ' range-list' but your source is only 'list' partitioned. Therefore a partition target: data from the "one" won't a single list.

  Load using the entire table at once without (other than the partition key) index on the target table.

• Transportable tablespaces and data files

  Hello

  I wonder if the following is possible.

  With the help of 11.2.0.3

  Export datapump job to export an entire table every day to dumpfile daily functioning

  Then, slide old partitions for example 1 day

  About destination databased days later (imgaeine 4) if need import current dumpfile and datafile for the affected tablespace that will import the deleted partition (that is, the 1st day

  Thank you

  I'm a little confused as to what you're asking, but since you're on 11.2.0.3 you have called transportable table mode.  You can export a single partition of a table using transportable tablespace data movement.  It helps a lot when you create a new storage space for each partition.  It also works if you do not have, but there are a lot of additional data you need to store.  Let me give you an example:

  table foo with:

  partition 1 - tablespace 1 - day 1

  partition 2 - tablespace 2 - day 2

  partition 3 - tablespace 3 - day 3

  partition 4 - tablespace 4 - day 4

  If you were to run this export:

  tables of user/password = foo:partition1 transportable expdp = always dumpfile = foo_part1.dmp...

  you would get a dumpfile with just partition1.  You must save the dumpfile and the data file if you ever need to restore.  To restore it, run a command like:

  Impdp username/password DB11G = dumpfile = foo_part1.dmp...

  It would be important only the partition, and it would create a table called foo_partition1.  You can then use the swap partition to put back in the table where you need restored.

  If all of these scores have been in the same table, you could do the same thing for export and import, but you would need to keep a copy of the dumpfile with a copy of the storage space for every day.  Then

  day 1 - would thus dumpfile datafile with just data from day 1

  day 2 - would thus dumpfile data file with data from day 1 and the day2

  day 3 - would thus dumpfile datafile on day 1, day 2 + data of the day 3

  etc.

  The reason for this is because the import checks that the tablespace that has the same features when it was exported.  It uses a checksum or something to verify this.  So, if you've added data to day 2, the data file would not be the same and the import fails.

  I hope this helps.

  Dean

• Incorrectly named tablespace in TABLE DDL

  I solved this problem before, but can't remember how I did it.  I have compressed and converted a partitioned table by moving the partitions of the table and the index partitions to an again deleted the old tablespace tablespace and renamed the new tablespace to the old nom_tablespace. When I now ask back the table through the DDL via sql developer the name of the tablespace or DBConsole is correct and bed "_ $supprimé$ $65 0. Everything is OK and queries etc seem to work correctly.

  Can someone advise me on how to rename it

  I use 11 GR 2 BP22

  CREATE TABLE 'JDST '. "" ORSTMOVE ".

  ('DEPT' VARCHAR2 (4 CHAR),

  VARCHAR2 (4 BYTE) "ST_GROUP."

  NUMBER (8.0) "SKU"

  DATE OF THE "ST_DATE."

  VARCHAR2 (1 BYTE) "ST_MOVEMENT."

  VARCHAR2 (8 BYTE) 'PLACE ', HE SAID.

  VARCHAR2 (1 BYTE) "ST_TYPE."

  VARCHAR2 (1 BYTE) "CONCEPT."

  VARCHAR2 (4 BYTE) "ORSTMOVE_FILLER."

  "ORDERNO" NUMBER (7.0).

  "ADJ" VARCHAR2 (1 BYTE),

  VARCHAR2 (3 BYTE) "GONE."

  'PLATEAU' NUMBER (5.0).

  "QTY" NUMBER (5.0).

  NUMBER (9.2) "GROSS_VAL."

  NUMBER (9.2) "COST_VAL."

  VARCHAR2 (3 BYTE) "BRCH."

  NUMBER OF "DIVISION."

  VARCHAR2 (20 BYTE) "UNIQUE_SKU_DATE".

  ) PCTFREE, PCTUSED, INITRANS 40 10 1 MAXTRANS 255 NOLOGGING

  STORAGE (INITIAL 65536

  USER_TABLES FLASH_CACHE, CELL_FLASH_CACHE DEFAULT DEFAULT)

  TABLESPACE ' _ $supprimé$ $65 0 '

  PARTITION BY RANGE OF RANGE ("ST_DATE") (NUMTOYMINTERVAL(1,'MONTH')) STORE IN ("ORSTMOVE_PART")

  (PARTITION "ORSTMOVE_P_P71" VALUES LESS THAN (TO_DATE (' 2011-12-01 00:00:00 ',' SYYYY-MM-DD HH24:MI:SS ',' NLS_CALENDAR = GREGORIAN ')) SEGMENT IMMEDIATE CREATION)

  PCTFREE 0 PCTUSED 40 INITRANS 1 MAXTRANS 255

  COMPRESSES FOR QUERY HIGH NOLOGGING

  STORAGE (INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645)

  PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1

  USER_TABLES FLASH_CACHE, CELL_FLASH_CACHE DEFAULT DEFAULT)

  TABLESPACE "ORSTMOVE_PART."

  PARTITION "ORSTMOVE_P_P73" VALUES LESS THAN (TO_DATE (' 2012-02-01 00:00:00 ',' SYYYY-MM-DD HH24:MI:SS ',' NLS_CALENDAR = GREGORIAN ')) SEGMENT IMMEDIATE CREATION

  PCTFREE 0 PCTUSED 40 INITRANS 1 MAXTRANS 255

  COMPRESSES FOR QUERY HIGH NOLOGGING

  After a little research, around the internet and support of Oracle I finally found the solution. Why there is not easy to find.   In any case I have that I'd share it in case someone hits the same question.

  ALTER table {table name} alter tablespace default attributes {valid tablespace name};

• Conversion of non partitioned in partitioned table

  
  Hi gurus,

  I need to convert the partition table not in the partition.  More flexible way is to use the DBMS_REDEFINITION package for this.
  I do not have access to run this package, when I asked the EXECUTE permission for my dev
  CUSTOMER rejected suggestion that
  "DBMS_REDEFINITION is a method very slow migration that has never been used before here for these migrations.
  so I do not recommend using it as it can trigger bugs and unexpected side effects.

  
  is this true?

  What will be the alternative method, I can go away?

  Please suggest

  S

  I don't think DBMS_REDEFINITION has bugs.  However, you (and the client) should be familiar with the steps involved.

  Other that that, you will need to create a partitioned table and insert data to the existing table.  You can speed up integration through parallel direct-path insert.

  You will also need to build indexes on the new (partitioned) table.  Define constraints if necessary.  Run grants to other patterns, if necessary.

  Hemant K Collette

• Adding a Partition to a range-Hash partitioned Table

  Hello

  I created the composite partition table (RANGE-HASH).  Oracle: 11.2, OS: HP UX

  CREATE TABLE 'XYZ '. "" TABLE_XYZ.

  (

  ----

  VARCHAR2 (54) "PROFILE" DEFAULT "000000000000000000' ENABLE NON-NULL"

  NUMBER (21.7) "CREATED_ON" DEFAULT 0 ENABLE NOT NULL,.

  ----

  )

  PARTITION BY RANGE

  (

  CREATED_ON

  )

  SUBPARTITION BY HASH

  (

  VIEW PROFILE

  )

  SUBPARTITION TEMPLATE

  (

  SUBPARTITION SP1 TABLESPACE PSAPISU,

  SUBPARTITION TABLESPACE PSAPISU SP2,

  SUBPARTITION SP3 TABLESPACE PSAPISU,

  SUBPARTITION SP4 TABLESPACE PSAPISU,

  SUBPARTITION SP5 TABLESPACE PSAPISU,

  SUBPARTITION SP6 TABLESPACE PSAPISU,

  SUBPARTITION SP7 TABLESPACE PSAPISU,

  SUBPARTITION SP8 TABLESPACE PSAPISU,

  SUBPARTITION SP9 TABLESPACE PSAPISU,

  SUBPARTITION SP10 TABLESPACE PSAPISU,

  SUBPARTITION SP11 TABLESPACE PSAPISU,

  SUBPARTITION SP12 TABLESPACE PSAPISU,

  SUBPARTITION SP13 TABLESPACE PSAPISU,

  SUBPARTITION SP14 TABLESPACE PSAPISU,

  SUBPARTITION SP15 TABLESPACE PSAPISU,

  SUBPARTITION SP16 TABLESPACE PSAPISU,

  SUBPARTITION SP17 TABLESPACE PSAPISU,

  SUBPARTITION SP18 TABLESPACE PSAPISU,

  SUBPARTITION SP19 TABLESPACE PSAPISU,

  SUBPARTITION SP20 TABLESPACE PSAPISU,

  SUBPARTITION SP21 TABLESPACE PSAPISU,

  SUBPARTITION SP22 TABLESPACE PSAPISU,

  SUBPARTITION SP23 TABLESPACE PSAPISU,

  SUBPARTITION SP24 TABLESPACE PSAPISU,

  SUBPARTITION SP25 TABLESPACE PSAPISU

  )

  (

  CREATED_ON_OCP01 PARTITION VALUES LESS THAN (20090101000000).

  CREATED_ON_OCP02 PARTITION VALUES LESS THAN (20090401000000).

  CREATED_ON_OCP03 PARTITION VALUES LESS THAN (20090701000000).

  CREATED_ON_OCP04 PARTITION VALUES LESS THAN (20091001000000).

  CREATED_ON_OCP05 PARTITION VALUES LESS THAN (20100101000000).

  CREATED_ON_OCP06 PARTITION VALUES LESS THAN (20100401000000).

  CREATED_ON_OCP07 PARTITION VALUES LESS THAN (20100701000000).

  CREATED_ON_OCP08 PARTITION VALUES LESS THAN (20101001000000).

  CREATED_ON_OCP09 PARTITION VALUES LESS THAN (20110101000000).

  CREATED_ON_OCP10 PARTITION VALUES LESS THAN (20110401000000).

  CREATED_ON_OCP11 PARTITION VALUES LESS THAN (20110701000000).

  CREATED_ON_OCP12 PARTITION VALUES LESS THAN (20111001000000).

  CREATED_ON_OCP13 PARTITION VALUES LESS THAN (20120101000000).

  CREATED_ON_OCP14 PARTITION VALUES LESS THAN (20120401000000).

  CREATED_ON_OCP15 PARTITION VALUES LESS THAN (20120701000000).

  CREATED_ON_OCP16 PARTITION VALUES LESS THAN (20121001000000).

  CREATED_ON_OCP17 PARTITION VALUES LESS THAN (20130101000000).

  CREATED_ON_OCP18 PARTITION VALUES LESS THAN (20130401000000).

  CREATED_ON_OCP19 PARTITION VALUES LESS THAN (20130701000000).

  CREATED_ON_OCP20 PARTITION VALUES LESS THAN (20131001000000).

  CREATED_ON_OCP21 PARTITION VALUES LESS THAN (20140101000000).

  CREATED_ON_OCP22 PARTITION VALUES LESS THAN (20140401000000).

  CREATED_ON_OCP23 PARTITION VALUES LESS THAN (20140701000000).

  CREATED_ON_OCP24 PARTITION VALUES LESS THAN (20141001000000).

  CREATED_ON_OCP25 PARTITION VALUES LESS THAN (20150101000000).

  PARTITION CREATED_ON_OCPMAX VALUES LESS THAN (MAXVALUE)

  )

  TABLESPACE "PSAPISU" ENABLE LINE MOVEMENT;

  Now, I am trying to add the new partition but becomes under errors:

  ALTER TABLE SAPISU. ADD PARTITION VALUES LESS THAN (20150401000000) CREATED_ON_OCP26 ZTMD_300_VERS_MANAGE

  *

  ERROR on line 1:

  ORA-14074: partition bound must gather greater than that of the last partition

  ERROR on line 1:

  ORA-14018: partition bound list contains too few elements

  I tried the SYNTAX mentioned by Oracle DOC, still getting error. Partitioned table and index management

  Could if it you please let me know, what is the exact syntax that I should follow?

  See you soon

  Sameer

  CREATED_ON_OCPMAX PARTITION SPLIT THAN (MAXVALUE)

  That don't mean to 'divide' the MAXVALUE partition.

  You cannot split a partition that contains the values of A, B, C, D, MAXVALUE to MAXVALUE; that makes no sense. ERROR on line 1:

  ORA-14080: partition cannot be split along the specified high limit

  That exception is to say you can't use MAXVALUE upper limit. You must use a value that is actually IN the partition.

  Go back and look at the definition of your partitions:

  CREATED_ON_OCP25 PARTITION VALUES LESS THAN (20150101000000).

  PARTITION CREATED_ON_OCPMAX VALUES LESS THAN (MAXVALUE)

  See which ends with: "VALUES LESS THAN (MAXVALUE)? MAXVALUE is not IN the score; This is the upper limit of the partition.

  Divide certain value > '20150101000000' and LESS THAN MAXVALUE;

  So if you try to create a partition for OCP26 you can use '20160101000000'.

  CREATE TABLE PART_TEST2)
  VARCHAR2 (54) DEFAULT PROFILE "000000000000000000' ENABLE NOT NULL,
  CREATED_ON NUMBER (21.7) DEFAULT 0 ENABLE NOT NULL
  )
  PARTITION BY RANGE (CREATED_ON)
  (
  CREATED_ON_OCP24 PARTITION VALUES LESS THAN (20141001000000).
  CREATED_ON_OCP25 PARTITION VALUES LESS THAN (20150101000000).
  PARTITION CREATED_ON_OCPMAX VALUES LESS THAN (MAXVALUE)
  )

  ALTER table split partition created_on_ocpmax part_test2
  to (20160101000000) into (partition, partition CREATED_ON_OCPMAX created_on_ocp26)

• Adding Partition for a partitioned Table

  Hello
  I have a partitioned table with 7 existing Partitions that follow this structure:
  
  PARTITION 'TRANSACTIONS_JAN2012' VALUES (TO_DATE () LOWER
  "2012-02-01 00:00:00 ', ' SYYYY-MM-JJ HH24:MI:SS»(, ' NLS_CALENDAR = GRÉGORIEN ')"
  ) PCTFREE, PCTUSED 10 0 INITRANS 1 MAXTRANS 255 NOLOGGING (INITIAL STORAGE
  1073741824 THEN 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0
  FREELISTS 1 FREELIST GROUPS 1 USER_TABLES DEFAULT FLASH_CACHE
  DEFAULT CELL_FLASH_CACHE) TABLESPACE "FTSV1" NOCOMPRESS
  
  I am trying to add a new Partition:
  ALTER table movements Add partition
  (partition TRANSACTIONS_JTS VALUES LESS THAN (TO_DATE (' 2012-03-01 00:00:00 ',' SYYYY-MM-DD HH24:MI:SS ',' NLS_CALENDAR = GREGORIAN ')));
  
  But get this error:
  SQL error: ORA-00902: invalid data type
  00902 00000 - "invalid data type".
  
  Any help is greatly appreciated.
  
  Thanks in advance,
  Johnny

  Hi Johnny,.

  Looks like you have one to several "Partition", delete this as well as the unnecessary parentheses.

  ALTER TABLE transactions
      ADD PARTITION transactions_jts
      VALUES LESS THAN
          (TO_DATE(' 2012-03-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'));
  

  Concerning
  Peter

• Eve not synchronized because test on primary transportable tablespace etc.

  This environment is the new generation environment, do not yet use.
  
  DB version is 11.2.0.3 in linux, RAC nodes are configured primary/secondary two and storage are stored to the DSO.
  
  primary DB was tested by data migration using transportable tablespace methods. If the imported data files was put in a local file system that I have to go eventually to the ASM.
  
  So the standby db felt that data files must be in the local file system and it got struck down.
  
  Here is the journal pending error:
  ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
  ORA-01110: data file 4: ' / stage/index.341.785186191'
  
  and the names of data files are all in the local file system in standby mode: / stage /... /.
  
  However in the primary data file, the names are in the ASM instance:
  +DAT/PRD/datafile/arindex.320.788067609
  
  How do I resolve this situation?
  
  Thank you

  user569151 wrote:
  so after the fall of the standby db, I use rman duplicate from active command?

  Yes, after the fall of database

  (1) starting in Nomount
  (2) check the configuraiton of net work
  (3) make sure password file exist
  (4) now run RMAN duplciate of Active database.
  That should be fine.

• Why not all the partition tables

  Hello
  
  In our project we propse to all partition tables (even if they are small, in MBs) in order to use the feature partiion exchange.
  But our DBAs say that maintenance will be a problem if create us partitions for each table. We said, only tablespace is fine for all partitions that we thought to maintain storage different is a problem.
  But always DBA are not approved.
  I just want to know what are the disadvantages of partitioning. Why DBA are generally against the idea of creating partitions. If we use the same storage space for all of the partitions is there any side down for creating partitions for each table?
  Is there is disadvantage?
  
  
  
  Thank you
  Pramod Garre

  Pramod Garre wrote:
  We plan to use range partitioning (in the quarters).
  There is a duty to remove a quarter of the table data, then refresh with new data as and when the user update some recored of frontend.this should arrive in real-time.

  Looks like you are having the app trigger partition management... which doesn't seem a good idea.
  It also looks like you really don't have justification for partitioning on a few tables. Far from being the "all" tables you inquired. And even that looks like your concept of the use of these scores may be wrong.

  Why not work with your databases instead of look at foreigners for the justification to fight them. Sounds to me like they are doing exactly what they were hired to do.

  We thought instead of delete and insert, if we use excahnge partitions, it will be real quick as Exchange just updated partition in the dictionary.
  On these lines, do you think that it be the disadvantages of the use of partitioning?

  Note: Delete and Insert works OK (2 minutes) compared to the swap partition (20 ms).

  And Yes, each table has PK.

  Thank you
  Pramod Garre

• Disable LOGGING for partition table based on the automatic INTERVAL

  Hello
  
  I created a database table of paritioned range interval with NOLOGGING as the default attribute for the table as well as the tablespace definition.
  
  When ORACLE automatically creates a new partition for this table, it activates the LOGGING for this automatic partition even if the table definition says anything else.
  
  How can I go about changing this behavior? Is it still possible?
  
  FYI my platform is 11 GR 1 (11.1.0.7) material on SUN SOLARIS 10 SPARC.
  
  Any help will be appreciated.

  Right, so refer to a new feature of Oracle 11 g partitioning called 'partitioning interval. "

  +"+
  + The interval partitioning: A new strategy of partitioning in Oracle Database 11g, +.
  + Interval partitioning extends the functionality of the method range to define equipartitioned +.
  + ranges using a definition of the interval. Rather than specify individual +.
  + going to explicitly, Oracle will create any partition automatically as needed.
  + every time the data of a partition are inserted for the first time. Interval +.
  + a lot of partitioning improves maneuverability of a partitioned table. For +.
  example, + a partitioned table interval could be set so that Oracle creates a +.
  + new partition for each month in a calendar year; a partition is then automatically +.
  + created for "September 2007" as soon as the first record in this month is inserted.
  + in the database. +
  + The techniques available for a partitioned table interval are interval, interval-+.
  + List, range-Hash, and interval range. +
  +"+

  In order to disable interval partitioning on the transactions table, use:
  
  ALTER TABLE transactions SET INTERVAL ();
  

  http://download.Oracle.com/docs/CD/B28359_01/server.111/b32024/part_admin.htm

  Disable partitioning interval on this table, create a procedure to run every day we'll say, to create a new partition and chop the old partition of the appropriate table. I presume that the automatic partitioning interval creates the partition with the logging by default option without checking the parameters in the table. I have seen no information on this in the Oracle documentation.

  Hope that helps.

  Ogan

• Satellite P750 PSAY1A: how to create the recovery Toshiba on the new HARD drive partition

  Hello

  I have an old Toshiba Satellite P750 (PSAY1A-01Y022). I just upgraded my memory from 4 GB to 8 GB and am preparing to take my 500 GB HARD drive 1 TB. I had to order the disk online and wait to happen.

  I always try to understand how to create the arrival of my new HARD drive Toshiba Recovery Partition. I do the same thing for an old book, I handled based on something similar to it's original factory State.

  I have reflected on the recovery partition, but does not know how it was created. It is not NTFS. Does anyone have experience in the creation of a Toshiba Recovery on a new HARD drive Partition?

  And the help is very appreciated.

  Thanks and regards,
  Dinesh

  Recovery partition can be created when you use the original Toshiba Recovery disk and install recovery image. Before the partitions to boot OS install will be automatically created, recovery image copied on a recovery and then partition as last step recovery image installation starts.

  A sort of migration of files from one to the other HARD disk is not solution.

  Only for laptop with factory will work and the usable recovery partition.