Don Granaman wrote:
With compress=N, you will get essentially the same mish-mash of extents you
had previously -
Hmmm, that's hair-splitting, but if you reimport into a tablespace from
which all objects have been dropped and that you have coalesced, you
will have the same number of extents
Absolutely! I should have read more closely!
Don Granaman
[Orasaurus]
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Monday, July 01, 2002 1:41 AM
For the reported problem, (1) is the only option as (2) is not possible with
7.3.x database.
-
I don't believe LMTs are supported in 7.3.x...
--- Don Granaman [EMAIL PROTECTED] wrote:
With compress=N, you will get essentially the same mish-mash of
extents you
had previously - unless you are importing into a LMT.
You have basically two options:
1) Pre-create the objects with a
LMTs came with 8i (8.1.5 afaik)
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Monday, July 01, 2002 3:18 PM
I don't believe LMTs are supported in 7.3.x...
--- Don Granaman [EMAIL PROTECTED] wrote:
With compress=N, you will get
Thanks everyone for your advice.
If I want to retrofit to 7.3.4 I have to create the tables sans storage
clause then import import the data .
Otherwise wait until the database upgrade.
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Robert Monical
INET: [EMAIL
No, you do not have to wait for 8i or 9i
You are almost there to get what you want.
What you need to do prior to import is build all the tables without any
storage cluase in the CREATE TABLLE|INDEX syntax. It will default to the
tablespace settings. And them import with IGNORE=Y option (since
With compress=N, you will get essentially the same mish-mash of extents you
had previously - unless you are importing into a LMT.
You have basically two options:
1) Pre-create the objects with a storage clause specifying the extent sizes
you want - with initial and next the same size. Then
Deshpande, Kirti£¬
hi, check oracle undocumented parameter: _system_trigger_enabled=false. If this is
set, then all database event trigger will be disabled.
Good luck
Good luck!
chaos
[EMAIL PROTECTED]
zhu chao
DBA of Eachnet.com
86-021-32174588-667
ÔÚ
For the reported problem, (1) is the only option as (2) is not possible with
7.3.x database.
- Kirti
-Original Message-
Sent: Sunday, June 30, 2002 9:28 PM
To: Multiple recipients of list ORACLE-L
With compress=N, you will get essentially the same mish-mash of extents you
had
And how will it be of help in this export/import issue ?
Sorry, I did not follow what you mentioned.
- Kirti
-Original Message-
Sent: Sunday, June 30, 2002 10:48 PM
To: Multiple recipients of list ORACLE-L
Deshpande, Kirti£¬
hi, check oracle undocumented parameter:
10 matches
Mail list logo