Re: Unplug problem

From: Andy Sayer <andysayer_at_gmail.com>
Date: Mon, 29 Mar 2021 16:47:49 +0100
Message-ID: <CACj1VR6mYTpERmwVWEOtvvPQ22NSgf0jvW-KRzo2CTnSe0x2hA_at_mail.gmail.com>



You could try unplugging in an xml file, this will be super fast as it will just copy metadata. Then you can use a multicore friendly utility to zip up the data files.

This would be something nicer handled all by Oracle so might be worth filing an ER with support.

Thanks,
Andrew

On Mon, 29 Mar 2021 at 15:44, Mladen Gogala <gogala.mladen_at_gmail.com> wrote:

> I haven't checked, but the server probably doesn't allow tunneling. What
> purpose would it serve to block all the ports and allow tunneling?
> Tunneling can be explicitly disabled in /etc/ssh configuration. I am not a
> system admin and I don't have root password. No, my gripe was about Oracle
> ploggable database option being rather cumbersome when compared with other
> databases like MySQL or SQL Server. Unplugging into .pdb should be made
> much, much faster. Also, unplugged database should be allowed to be
> re-opened without dropping it. Dropping and re-plugging does funny things
> to standby.
>
> Regards
> On 3/28/21 10:24 PM, Laurentiu Oprea wrote:
>
> If from Server A you don't have direct access to Server B on 1521 but you
> have an intermediary Server C that has 1521 to B and you have 22 from A to
> C you can do ssh forwarding:
> https://www.ssh.com/ssh/tunneling/example
>
> maybe you have a jumpbox or something...I seen cases
>
> În lun., 29 mar. 2021 la 04:18, Mladen Gogala <gogala.mladen_at_gmail.com> a
> scris:
>
>> I was asked to refresh one of the development PDB tenants from the
>> corresponding production PDB. The platform is Linux x86_64 (OL 7.7) with
>> Oracle 19.10 (Jan 2021 RU). Unfortunately, due to security measures,
>> the only open port between the production server and the development
>> server is 22. That eliminates remote clone. The tenant size in
>> production is around 1TB. I opted for unplug pluggable database into
>> '/tmp/tenant.pdb'. That took almost 2 hours with very fast disk storage
>> (Pure array) and a powerful CPU. It was single threaded. Is there any
>> way I can use multiple threads? The .pdb archive is compressed and my
>> bottleneck was it being run on a single CPU. Is there any trick to do
>> that with RMAN? The production has 144 cores and I could easily afford
>> running 12 threads at a time. Unfortunately, I can't restore pluggable
>> database into another CDB using rman. This was like pulling teeth. I
>> couldn't get SQL*Net port (it isn't 1521) open so I had to unplug.
>> Fortunately, I knew what was I in for so I first did unplug to XML,
>> dropped the pluggable database with "keep datafiles" and plugged it back
>> in using XML. The whole thing is extremely awkward. The funny thing was
>> that "CREATE PLUGGABLE DATABASE TESTDB3 USING '/tmp/tenant.pdb'" used 2
>> cores. It was 4 times as fast as creating the PDB archive. Oracle's
>> multi-tenant leaves a lot to be improved. I hope that Oracle 21 might
>> address some of these issues.
>>
>> --
>> Mladen Gogala
>> Database Consultant
>> Tel: (347) 321-1217
>> https://dbwhisperer.wordpress.com
>>
>> --
>> http://www.freelists.org/webpage/oracle-l
>>
>>
>> --
> Mladen Gogala
> Database Consultant
> Tel: (347) 321-1217https://dbwhisperer.wordpress.com
>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Mon Mar 29 2021 - 17:47:49 CEST

Original text of this message