Re: DMT and LMT

From: Hanne Iren Midttun <hannem_at_tihlde.org>
Date: Fri, 21 Mar 2003 00:57:32 +0100
Message-ID: <Pine.LNX.4.21.0303210031560.14985-100000@colargol.tihlde.org>

Hi, and thanks for your answar. comments inline

On Thu, 20 Mar 2003, Norman Dunbar wrote:

> Hi Hanne,
>
> you wrote :
>

>> Right now we have an 9i release 2 export
>> with DMT. We have created an 9i release 2 test database to import the
>> data, but it failes because we have createt our test database with
>> LMT..

>
> I don't think the fact that you have LMT while the data was exported
> from a DMT is the cause of the failure. I have many customers running
> DMT or LMT and some running both, who regularly send us export files. I
> can import them quite happily into a 9i R2 LMT database.
>
> What errors are being thrown by import ?

ORA-12913  

>> OK - I can fix this, but how to make an enviroment witch can handle
>> the fact that we can get our data from really strange databases? This
>> is the challange. 

>
> By 'starange databases' you do mean 'from other Oracle databases' don't
> you ?

Yes. Different versions and configuration. (I guess I sounded a little bit sour. I was hoping to be able to use transportable tablespace. And now I am stucked with import that takes 10 hours..)

>> I was thinking the best sollution was to have a 9i relase 2 database in
>> our test enviroment (since Oracle is backward compatible this database
>> would handle all the exp files we get - no matter the version they are
>> exported from?) with a DMT system tablespace (then we could handle
>> both DMT and LMT?) Some comment?   

>
> LMT can handle imports from DMT or LMT or both, it makes no difference.
>
> Now, while typing the above, I had a thought. If your 9i database is
> created with LMT SYSTEM tablespace, then you will not be allowed to
> create any DMTs. I wonder if you are doing FULL exports/imports and
> having the import create the tablespaces and because the sending
> database is DMT, the creation is failing because DMTs are not allowed on
> a database with an LMT SYSTEM tablespace ?

Partly correct. The system tablespace was LMT, and the import was full=y, but the tablespace was createt before the import was started.  

> If this is the case then I suggest the following *may* help :
>
> pre-create your tablespaces as LMT

Tried and failed

> pre-create

Not really sure what you are saying? Typo? :-)

> import users not the entire database

Didn't think of it. (Now we are recreating the database with a DMT system tablespace. I guess I hit the delete button to fast..)

> ask your users/customers to send you user exports rather than
> full exports.

We are lucky to get full exports from them...  

>> English is not my native tounge

>
> Nor mine - I'm Scottish :o)
> Your English is *far* better than my Norwegian !

How did you know I was from Norway? (BTW I guess I have better oppertunety to learn english then you had to learn norwegian :-D)

regards Hanne

--
Hanne Midttun
http://www.tihlde.org/~hannem

English is not my native tounge

Received on Thu Mar 20 2003 - 17:57:32 CST