Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: RAC, Duplicate Database - All Logfiles Assigned to Thread 1?
Ok, got an answer from Metalink....
Although, I'm still not sure that they understood the question, basically, it looks like you have to duplicate to a single instance (can be a RAC instance brought in non-RAC mode with all other instances shut down) and then bring it all back up in RAC mode. At that point, you still might have to fix the logfile assignment (again, not clear on this as support focused on the control files as an issue more than the log files).
For the details, here's the tar thread:
06-APR-05 18:00:41 GMT ACTION
Hi Jesse,
UPDATE
ISSUE CLARIFICATION
SOLUTION / ACTION PLAN
You will not be able to create controlfiles if any of your RAC instance
is up.
This restriction is documented in the SQL Reference manual under the
CREATE
CONTROLFILE statement.
Create controlfile is a single node operation. Duplicate to a single
node,
shutdown and bring the database up in RAC mode.
If the other nodes instances are at nomount or mount then this is not
exclusive mode because the SGA's share the same controlfile and
datafiles.
The other instance needs to be down and you need to disable
cluster_database=
true to false.
Change back after the duplication.
The value for your RAc parameters should be THREAD = 1. If not then
the duplicate via RMAN might fails with error ORA-1608. If you want to
duplicate
the RAC database to another node, you need to use thread 1, not thread
2, because by
default, the database start to use thread 1.
Example:
dtb2_2.INSTANCE_NUMBER=1
dtb2_2.THREAD = 1
Regards
Ray
STATUS
06-APR-05 18:12:26 GMT New info : DAVISJJ1 : That may help clear up some of the other troubles I ran
into when doing this, but in the end the control files were created ok
(actually, they already existed in the development setup, so they were just
updated/restored by RMAN), but how will this help to assign LOGFILES to
specific threads? That's what ended up being the biggest problem, the
LOGFILES, not the CONTROL FILES.
...and you're right, I've struggled to find any documentation regarding
RMAN's
ability (or lack thereof) to duplicate RAC to RAC.
Thanks.
06-APR-05 18:20:01 GMT ACTION
Jesse,
Currently you cannot use thread 2 when duplicating into a RAC environment.
Don't know currently where developement is at with this issue. The fact
currently is that
the create controlfile is a single node function which is thread 1 and
RAC is a multiple node
with multiple thread which has presented this problem.
Logfiles cannot be assign to multiple threads at this time.
Regards
Ray
STATUS
06-APR-05 11:35:25 : CHANGES MADE VIA MetaLink
NOT YET FORWARDED TO OUR INTERNAL SYSTEMS :
New info : DAVISJJ1 : Ok, I understand. Thanks. I would like to
officially
request that development considers adding this capability (or, in
general,
better support for RAC in RMAN). At the very least, built-in scripts to
handle
the shutting down of the aux instances, the rac=false config, etc.
would be
great.
For now, I will use the method that you have described.
Thanks.
Received on Wed Apr 06 2005 - 13:44:02 CDT
![]() |
![]() |