Re: transportable tablespaces

I have a collegue who is working in a bank, when they first migrated to 8i they started to use transaportable tablespaces but after 1 month they had to get rid of it because it simply took too long to put it in read-only state (longest time was 7 hours)

Jonathan Lewis wrote:

> The document is wrong.
>
> Using current versions of Oracle. the
> 'make tablespace readonly'
> command waits until all transactions that started
> before the call have ended. It doesn't stop new
> transactions beginning, and it doesn't have to wait
> until there are no active transactions at all.
>
> Of course, any transactions that attempt to
> update the tablespace after the call will get
> an error message that the tablespace may
> not be updated.
>
> I think this is different from the original v7
> behaviour when the feature first appeared,
> but I can't remember when the change
> occurred..
>
>
> --
> Jonathan Lewis
> http://www.jlcomp.demon.co.uk
>
> Next Seminars
> UK July / Sept
> Australia July / August
> Malaysia September
> USA (MI) November
> http://www.jlcomp.demon.co.uk/seminar.html
>
> sg wrote in message <3D2B3127.5020503_at_europe.com>...
>

>>Does transportable tablespace really worthy in a 24x7 shop? well
>>actually I should really say if it works in 24x7 shop because we have to
>>first make tablespace read-only which is not possible if there are
>>transactions going in the database. (although the doc says there must
>>not be any transaction going in TABLESPACE which is not true)
>>Or am I missing any trick to make it read-only?
>>
>>
>>