Re: Why never finished deploying oracle data guard physical standy by

Also, setting db_file_name_convert and log_file_name_convert on the standby side might go a long way toward the problem resolution.

On Mon, May 22, 2023, 11:48 richard goulet <rjgoulet_at_comcast.net> wrote:

> Ref:
>
> Hello my oracle friends 😄,
> One of my customers wanna delopy oracle data guard physical standby by rman
> duplicate using my current oracle 11.2.0.4.0 with single instance, after a
> series of the tedious DG parameters configuration both on primary and
> physical standby database I started using rman duplicate to push memory
> script from primary to physical standby.
>
> Yes, my current oracle 11.2.0.4.0 has the volume size of *2.0 t* for data
> files, the hardware resource is as below:
> Logic CPUs: 64c, Physical Memory: 512 GB, Disk IO for the read and write
> speed is probably a bit of bottleneck.
>
> Firstly, I use the following shell script to deploy it.
>
>
> But after *3.5 hours*, the log file of rman duplicate has the following
> error:
>
> ......
>
> executing command: SET NEWNAME
>
>
>
> Your issue is that the target system does not have the same filesystem layout as the original. You have 2 options:
> 1) get your sysadmin to fix the target filesystem to match the original, alternatively if you have access then do the required.
> 2) use the setnewname command to change the original to match the target:
> EX: 'setnewname datafile 1 to '/oracle/oradata/<whatever>/datafile/system01.dbf';
>
> Mladen Gogala

--
http://www.freelists.org/webpage/oracle-l