Your brain is getting full. You should stop studying so much. See what it
does to you?
-Original Message-
Yep, I didn't remember the exact clause in the exchange
partition syntax.
Tanel.
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: [EMAIL
Probably he needs to set: pga_aggregate_target :)
Regards,
Waleed
-Original Message-
Sent: Monday, December 29, 2003 11:59 AM
To: Multiple recipients of list ORACLE-L
Your brain is getting full. You should stop studying so much. See what it
does to you?
-Original Message-
Yes, that's why I went to a memory improvement training few weeks ago ;)
Tanel.
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Monday, December 29, 2003 6:59 PM
Your brain is getting full. You should stop studying so much. See what
it
does
Hope it improved your hit ratio :)
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Monday, December 29, 2003 1:59 PM
Yes, that's why I went to a memory improvement training few weeks ago ;)
Tanel.
- Original Message -
To: Multiple
The need to set primary and unique constraints to
NOVALIDATE when doing an exchange partition.
(It still doesn't help with problems of parent/child
tables when dropping partitions though).
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk
The educated person is not the person
who can
Thanks, I haven't hit this problem before.
Actually, in my post I recommended to use novalidate option for exchanging
required partition back from temporary transport table, that way Oracle
won't check the contents in the partition (should be used only when this
partition doesn't change in the
So your 'novalidate' referred to the
without validation
clause of exchange; I thought you
were referring to the workaround
for uk/pk exchanges where even if you
did
including indexes without validate
on the exchange, Oracle still did a
horrendous check of the UK and PK
constraints by
Yep, I didn't remember the exact clause in the exchange partition syntax.
Tanel.
So your 'novalidate' referred to the
without validation
clause of exchange; I thought you
were referring to the workaround
for uk/pk exchanges where even if you
did
including indexes without
Title: Exporting a partition with transport tablespace
Make sure that you use novalidate and exchange
indexes as well - that way Oracle won't make unnecessary work.
Also, you should export the metadata at the time
when required partitions are exchanged to "transport tables&quo
Good news !
That bug has been fixed in 9.2.0.4
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk
The educated person is not the person
who can answer the questions, but the
person who can question the answers -- T. Schick Jr
One-day tutorials:
Jonathan,
Which exact behaviour were you talking about?
Tanel.
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Saturday, December 27, 2003 11:34 PM
Good news !
That bug has been fixed in 9.2.0.4
Regards
Jonathan Lewis
Title: Exporting a partition with transport tablespace
Hi list,
is it possible to export a partition with the transportable tablespace feature ?
My partition is over 8 Go.
Here my statements , thank you in advance !
SQLexec sys.dbms_tts.transport_set_check('HISTO_DOSSIER_P1_MD_TAB',FALSE
PROTECTED]
Date: 2003/12/22 Mon AM 10:34:25 EST
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: Exporting a partition with transport tablespace
Hi list,
is it possible to export a partition with the transportable tablespace
feature ?
My partition is over 8 Go.
Here my
contained in transportable set
Title: Exporting a partition with transport tablespace
Hi list,
is it possible to export a partition with the transportable tablespace feature ?
My partition is over 8 Go.
Here my statements , thank you in advance !
SQLexec sys.dbms_tts.transport_set_check
Title: Exporting a partition with transport tablespace
No it's not. However, you could simply exchange the
partition with a table and then export the tablespace.
For instance,
ALTER TABLE HISTO_DOSSIEREXCHANGE PARTITION
part1 WITH TABLE HISTO_DOSSIER_part1;
Then export the tablespace. Make
Title: RE: Exporting a partition with transport tablespace
Yes, my partitions are in separate tablespaces
so do I have to export all the tablespaces concerned ?
wich solution do you use ? each partition is over 8 Go so should I use common export command to backup only one tablespace
Title: Exporting a partition with transport tablespace
You could create new table in
transportable tablespace, exchange data with the partition you want to export, move
transportable tablespace file to the destination system, exchange data back
from the table into desired partition
17 matches
Mail list logo