Home » RDBMS Server » Backup & Recovery » Clone problem due to mountpoint space constraints
Clone problem due to mountpoint space constraints [message #237485] Mon, 14 May 2007 11:24 Go to next message
WolfBrother
Messages: 10
Registered: June 2006
Location: Austin, TX
Junior Member
I used the search feature but didn't find a solution.

I clone a production instance on a weekly basis for the developers to have a production-test environment.


The initSID.ora on Dev (target)

db_file_name_convert=('/u01/oradata/SIDp/','/u01/oradata/SIDd/',
'/u02/oradata/SIDp/','/u02/oradata/SIDd/',
'/u03/oradata/SIDp/','/u04/oradata/SIDd',
'/u04/oradata/SIDp/','/u03/oradata/SIDd/',
'/u05/oradata/SIDp/','/u05/oradata/SIDd/',
'/u11/oradata/SIDp/','/u11/oradata/SIDd/')


Due to space constraints on the dev mountpoing /u03, what I tried to do was:

db_file_name_convert=('/u01/oradata/SIDp/','/u01/oradata/SIDd/',
'/u02/oradata/SIDp/','/u02/oradata/SIDd/',
'/u03/oradata/SIDp/filea.dbf','/u03/oradata/SIDd/filea.dbf',
'/u03/oradata/SIDp/fileb.dbf','/u03/oradata/SIDd/fileb.dbf',
'/u03/oradata/SIDp/filec.dbf','/u04/oradata/SIDd/filec.dbf',
'/u03/oradata/SIDp/filed.dbf','/u04/oradata/SIDd/filed.dbf',
'/u04/oradata/SIDp/','/u04/oradata/SIDd/',
'/u05/oradata/SIDp/','/u05/oradata/SIDd/',
'/u11/oradata/SIDp/','/u11/oradata/SIDd/')

That is - specify selected files that reside in the /u03 mountpoint on the PRD instance to restore to the /u04 mountpoint on the dev system.

Doing so got these errors
RMAN-05001: auxiliary filename /u03/oradata/SIDp/filea.dbf conflicts with a file used by the target database
RMAN-05001: auxiliary filename /u03/oradata/SIDp/fileb.dbf conflicts with a file used by the target database
RMAN-05001: auxiliary filename /u03/oradata/SIDp/filec.dbf conflicts with a file used by the target database
RMAN-05001: auxiliary filename /u03/oradata/SIDp/filed.dbf conflicts with a file used by the target database

I worked around it by using soft links to link the existing files to the /u04 mountpoint and cloned the system using the original initSID.ora.

The manuals never specified that we couldn't do the above.

Can we not?


Re: Clone problem due to mountpoint space constraints [message #237490 is a reply to message #237485] Mon, 14 May 2007 11:35 Go to previous messageGo to next message
Mohammad Taj
Messages: 2412
Registered: September 2006
Location: Dubai, UAE
Senior Member

Hi,
Can we not?

I don't think it is possible.i never tried it before.

you should make free space on /u03 mountpoint.

Regards
Taj
Re: Clone problem due to mountpoint space constraints [message #237495 is a reply to message #237490] Mon, 14 May 2007 11:46 Go to previous message
WolfBrother
Messages: 10
Registered: June 2006
Location: Austin, TX
Junior Member
Mohammad Taj wrote on Mon, 14 May 2007 11:35
Hi,
Can we not?

I don't think it is possible.i never tried it before.

you should make free space on /u03 mountpoint.

Regards
Taj


Taj, apologies for not supplying sufficient information.

Short of adding additional disks (which is not do able at present and may not be possible due to box size) the dev box is at max space available.

If I could get the db_file_name_convert parm to work, I could "sprinkle" the files around and at sometime in the future easily bring them back to /u03.

This is a scripted clone and I'm trying to not have to use the set newname command.


[Updated on: Mon, 14 May 2007 11:47]

Report message to a moderator

Previous Topic: Back Database
Next Topic: unable to see DMLs in v$logmnr_contents
Goto Forum:
  


Current Time: Fri Dec 02 20:31:26 CST 2016

Total time taken to generate the page: 0.08153 seconds