Steps to restore a RAC database

Hi all

Can someone provide the steps to restore a 4 database RAC node to another node 4 CARS?

Database version: 11.2.0.2

OPERATING SYSTEM: AIX 6.1

If you are in the same version of the OS, there is not much difference between a CAR and a NON-Rac environment when restoring, you can check MOS notes RMAN Duplicate Database of RAC ASM with RAC ASM (Doc ID 461479.1)

Tags: Database

Similar Questions

How to use backups RMAN to restore a RAC database to single instance on another host?

How to use backups Rman to restore a RAC database to single instance on another host?

I tried to copy these inline for you:

------------

Backups RMAN disk HowTo restore database RAC to single Instance on another node (Doc ID 415579.1)

Down

Problem with the restoration of the database

Hello world
I have a strange problem while restoring the database with rman. The problem is that the data are not restored at all.
Let me show you what I do step by step:
1. create the test table:
$ sqlplus / as sysdba
SQL * more: Production of release 11.2.0.1.0 Thu Apr 17 22:51:58 2014
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production
With partitioning, OLAP, Data Mining and Real Application Testing options
SQL > create table test (ID);
Table created.
SQL > insert into values test (1);
1 line of creation.
SQL > commit;
Validation complete.
2. backup the current database:
rman target $ /.
Recovery Manager: release 11.2.0.1.0 - Production Fri Apr 17 22:56:44 2014
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORACLE (DBID = 1672007929)
RMAN > backup database;
From 17 April 14 backup
using the control file of the target instead of recovery catalog database
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID = 6 type of device = DISK
channel ORA_DISK_1: starting full datafile from backup set
channel ORA_DISK_1: specifying datafile (s) in the backup set
Enter a number of file datafile = 00001 name=/u01/app/oracle/oradata/oracle/system01.dbf
Enter a number of file datafile = name=/u01/app/oracle/oradata/oracle/sysaux01.dbf 00002
Enter a number of file datafile = name=/u01/app/oracle/oradata/oracle/undotbs01.dbf 00003
Enter a number of file datafile = 00005 name=/u01/app/oracle/oradata/oracle/example01.dbf
Enter a number of file datafile = name=/u01/app/oracle/oradata/oracle/users01.dbf 00004
channel ORA_DISK_1: from room 1 to 17 April 14
channel ORA_DISK_1: finished piece 1 to 17 April 14
piece handle=/u01/app/oracle/flash_recovery_area/ORACLE/backupset/2014_04_17/o1_mf_nnndf_TAG20140417T230734_9o1j980f_.bkp tag = TAG20140417T230734 comment = NONE
channel ORA_DISK_1: complete set of backups, time: 00:00:57
channel ORA_DISK_1: starting full datafile from backup set
channel ORA_DISK_1: specifying datafile (s) in the backup set
including the current control in the backup set file
including current SPFILE in the backup set
channel ORA_DISK_1: from room 1 to 17 April 14
channel ORA_DISK_1: finished piece 1 to 17 April 14
piece handle=/u01/app/oracle/flash_recovery_area/ORACLE/backupset/2014_04_17/o1_mf_ncsnf_TAG20140417T230734_9o1jc09s_.bkp tag = TAG20140417T230734 comment = NONE
channel ORA_DISK_1: complete set of backups, time: 00:00:01
Backup finished on 17 April 14
3. change the data in the test table
$ sqlplus / as sysdba
SQL * more: Production of release 11.2.0.1.0 Thu Apr 17 23:10:16 2014
Copyright (c) 1982, 2009, Oracle. All rights reserved.

Connected to:
Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production
With partitioning, OLAP, Data Mining and Real Application Testing options
SQL > select * from test;
ID
----------
1
SQL > update test set ID = 2;
1 line update.
SQL > commit;
Validation complete.
4. restore the database
RMAN target /.
Recovery Manager: release 11.2.0.1.0 - Production Fri Apr 17 23:11:15 2014
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORACLE (DBID = 1672007929)
RMAN > shutdown immediate;
using the control file of the target instead of recovery catalog database
database closed
dismounted database
Instance Oracle to close
RMAN > bootable media.
connected to the database target (not started)
Oracle instance started
mounted database
Total System Global Area 835104768 bytes
Bytes of size 2217952 fixed
629147680 variable size bytes
197132288 of database buffers bytes
Redo buffers 6606848 bytes
RMAN > restore database;
From restoration to April 17, 14
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID = 156 type device = DISK
channel ORA_DISK_1: from the restore backup set data file
channel ORA_DISK_1: specifying datafile (s) to restore from backup set
channel ORA_DISK_1: restore datafile 00001 to /u01/app/oracle/oradata/oracle/system01.dbf
channel ORA_DISK_1: restore datafile 00002 to /u01/app/oracle/oradata/oracle/sysaux01.dbf
channel ORA_DISK_1: restore datafile 00003 to /u01/app/oracle/oradata/oracle/undotbs01.dbf
channel ORA_DISK_1: restore datafile 00004 in /u01/app/oracle/oradata/oracle/users01.dbf
channel ORA_DISK_1: restore datafile 00005 to /u01/app/oracle/oradata/oracle/example01.dbf
channel ORA_DISK_1: backup /u01/app/oracle/flash_recovery_area/ORACLE/backupset/2014_04_17/o1_mf_nnndf_TAG20140417T230734_9o1j980f_.bkp piece reading
channel ORA_DISK_1: room handle=/u01/app/oracle/flash_recovery_area/ORACLE/backupset/2014_04_17/o1_mf_nnndf_TAG20140417T230734_9o1j980f_.bkp tag = TAG20140417T230734
channel ORA_DISK_1: restored the backup part 1
channel ORA_DISK_1: restore complete, duration: 00:00:55
Restoration finished in 17 April 14
RMAN > restore database;
To go back to April 17, 14
using channel ORA_DISK_1
starting media recovery
media recovery complete, duration: 00:00:03
Finished recover at April 17, 14
RMAN > sql 'alter database open;
SQL statement: alter database open
5. check if the data has been restored
sqlplus / as sysdba
SQL * more: Production of release 11.2.0.1.0 Thu Apr 17 23:14:39 2014
Copyright (c) 1982, 2009, Oracle. All rights reserved.

Connected to:
Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production
With partitioning, OLAP, Data Mining and Real Application Testing options
SQL > select * from test;
ID
----------
2
Summary:
Data has not changed. Provided the ID is 1, but after the success of data recovery is not restored (ID is always 2).
Can someone help me? What I am doing wrong?
Database is Oracle 11 g with archivelog active
Ol6 2.6.39 Linux OS - 300.17.2.el6uek.x86_64

RMAN > restore database;

To go back to April 17, 14

using channel ORA_DISK_1

starting media recovery

media recovery complete, duration: 00:00:03

Finished recover at April 17, 14

RMAN > sql 'alter database open;

SQL statement: alter database open

5. check if the data has been restored

sqlplus / as sysdba

SQL * more: Production of release 11.2.0.1.0 Thu Apr 17 23:14:39 2014

Copyright (c) 1982, 2009, Oracle. All rights reserved.

Connected to:
Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production
With partitioning, OLAP, Data Mining and Real Application Testing options

SQL > select * from test;

ID
----------
2

Summary:

Data has not changed. Provided the ID is 1, but after the success of data recovery is not restored (ID is always 2).

Can someone help me? What I am doing wrong?

Database is Oracle 11 g with archivelog active

the recovery was successful, but achieved your goal.

There are several options to reach your goal to recover your database to a particular State that is point in time.

1 restore the file of control as noted above. you restore the control file must not be aware of the generated once archivelog that you update your table. IE backup controlfile prior you updatedyour table.

2. do not apply archivelog all during recovery. You can use SNA, SEQUENCE, RESTORE POINT option of the recover command. This option requires that you open your database with resetlog.

read: scene of Flashback and the database Point-in - time recovery

After a restore successful your database (before the recover command), you can "alter database open read-only" to check and confirm the values in the table.

HTH

Tobi

Installation of the node2 RAC database

Hello
I installed grid infrastructure, Oracle RAC cluster db software.
Then in the node 1 installed listener and created / the set up db using dbca.
I have sucessfully created database and db info written in/etc/oratab.
Question: should I create an another data base using dbca in node 2? for example, if istalled node1 PROD1 db, should install PROD2 instance in node2?
What are the next steps after the installation of database in node1?
Thank you

Hello

Check if the ORACLE_HOME parameter is correctly set

On srv01

Export ORACLE_HOME =

export ORACLE_SID = PROD11

export ORACLE_BASE =

Or you can add PROD11 entered oratab copying PROD1 and the same mounting on srv01 PROD11

then run

. oraenv

The above sets the env

Then connect as

sqlplus / as sysdba

To connect via the application, please refer to the

Ref: How to integrate a database of the RAC 10 g / 11 GR 1 material with 11 GR 2 clusterware (SCAN) (Doc ID 1058646.1)

Ref: 11.2 Scan and node TNS Listener of installation examples (Doc ID 1070607.1)

Ref: How to solve the problem of connectivity with the name SCAN 11 GR 2 (Doc ID 975457.1)

Kind regards

Vautrin - Oracle

10g R2 no RAC-database unique Instance to upgrade to 11g R2-2 node RAC database

Hi all
I have a requirement for my client.
We have a three databases with replication between them activated by MV & MV connects to the 10 g R2 database.
This must be upgraded to Database 11g R2 with a 2 RAC node.
Please tell us how to get started and go.
Also please notify once upgraded to database 11g R2, how replication can be achieved.
Thank you
Vijayaraghavan.K

> We have to first upgrade to 11 g R2 Instance unique and then move on RAC - node 2

You must install the grid Infrastructure for Cluster and RAC database software in the new cluster.

Then upgrade the database as a single instance database.

Then, convert it to the RAC

See http://docs.oracle.com/cd/E11882_01/rac.112/e17264/install_rac.htm#TDPRC185 for the conversion of the measures.

Hemant K Collette

Company of Mgr 12 lost connection to the RAC databases after the restart of the EM

This last weekend, we restarted our main production RAC database (name = prod, instances = prod1 and prod2) and our certification test RAC database (name = cert, instances = cert1 and cert2).
These databases have been put up and work OK as a target in MS 12 c for a few months. However, I was not able to connect to these databases into EM yesterday, so I rebooted the server database repository EM both of EM application server.
As of today, I can connect to the web console of EM successfully, and I can bring up our databases not CARS. But if I try to put in place either of our CARS (prod or cert) databases, or if I try to put in place a specific instance prod1, prod2 or cert1, cert2, I get errors like this:
IO error: the network adapter could not establish the connection
The connection descriptor was (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = tcp) (HOST = nhaoranla - oracle.nha.local)(PORT=1521))) (CONNECT_DATA = (SID = cert1) (SERVER = DEDICATED)))
The server nhaoranla where cert1 database instance. We use the standard port 1521 for all targets.
Two CARS of prod and cert authorities are running, and user applications are able to connect to the two bodies.
I have not changed anything in EM. The only difference with last week's restart.
I tried to restart the server applications EM once again, but that solves nothing, I get the same error.
Any suggestions or bugs that are known for this problem would be appreciated.

Figured out what the problem was... TCP error message indicated it was looking for nhaoranla - oracle.nha.local , but I nhaoranla-oracle in/etc/hosts on the server to OEM applications.

Lesson learned... If you add databases to the OEM through node discovery, initially, it could work, but it will fail when you restart your server OEM if you don't have good (complete) entries in/etc/hosts.

IF database-> RAC database: estimate of the size of the SGA for each instance

Hello!
Let's say that there is a single instance with SGA 100 G size DB (assume this size is optimal for this database).
If this database is intended to be converted to a RAC database with 2 instances (suppose DB workload will be spread over multiple instances).
How to estimate the needs of SGA size for each instance in the RAC database?
It takes 50G + General cool CARS (say 15%) for each instance?
(Do not consider situation when one of the instances has failed, and all the charge redirects to an instance having survived)
I'd be grateful if someone has offered or provided useful references.
---
Kind regards
Kyrylo

As a general rule, I would size the SGA on new nodes to 120% of the SGA to single instance. Yes, this means that you will more than double the size of the SGA. You will need additional space to hold the load memory Cache Fusion. And the buffer Cache are possibly a little more space to store additional versions of blocks that seem to accompany the many implementations of CARS. Now, it's just a rule of thumb, so it has a high degree to be very wrong.

You'll want to consider two big things... (1) the service being used. Will you take advantage of the services to perform the partitioning application? If so, instances can see various workloads that can lead to requests for different resources. (2) you will support a kind of failover (TAF or manual failover) applications? If so, then the LMS must be sufficiently sized to support the additional workload.

See you soon,.
Brian

Try to clone RAC database with RMAN database RAC but becomes lower than ORA-01503

I'm trying to clone a RAC database of RMAN target database is also CARS, so for every thing wen fine but getting "ORA-01503.
Please find below, please help me solve this problem.
connect sys/p0ck3t@pcard1 target;
auxiliary connection;
Connect the rmancat/rmanamex@rmandb catalog;
Run {}
SQL "alter session set optimizer_mode = RULE ';"
until ' to_date (' may 1, 2015 06:30 ',' Lun ' DD YYYY HH24:MI:SS);
allocate auxiliary channel t1 type disk;
allocate auxiliary channel t2 type disk;
allocate auxiliary channel t3 type disk;
the value of newname for datafile 4 to "+ DATA/pcardtst/datafile/users.304.723229675";
the value of newname for datafile 3 to "+ DATA/pcardtst/datafile/sysaux.395.723228961";
the value of newname for datafile 2 to "+ DATA/pcardtst/datafile/undotbs1_1.dbf";
the value of newname for datafile 1 to "+ DATA/pcardtst/datafile/system.328.723229027";
the value of newname for datafile 5 to "+ DATA/pcardtst/datafile/undotbs2.409.723228957";
the value of newname for datafile 6 to "+ DATA/pcardtst/datafile/pwrcrd_usr01.dbf";
the value of newname for datafile 7 to "+ DATA/pcardtst/datafile/pwrcrd_undotbs01.dbf";
the value of newname for datafile 8 to "+ DATA/pcardtst/datafile/pwrcrd_undotbs02.dbf";
the value of newname for datafile 9 to "+ DATA/pcardtst/datafile/pwrcrd_data_par01.dbf";
the value of newname for datafile 10 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_par01.dbf";
the value of newname for datafile 11 in "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part01_01.dbf";
the value of newname for datafile 12 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part01_02.dbf";
the value of newname for datafile 13 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part01_03.dbf";
the value of newname for datafile 14 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part01_04.dbf";
the value of newname for datafile 15 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part01_01.dbf";
the value of newname for datafile 16 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part01_02.dbf";
the value of newname for datafile 17 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part02_01.dbf";
the value of newname for datafile 18 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part02_02.dbf";
the value of newname for datafile 19 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part02_03.dbf";
the value of newname for datafile 20 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part02_04.dbf";
the value of newname for datafile 21 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part02_01.dbf";
the value of newname for datafile 22 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part02_02.dbf";
the value of newname for datafile 23 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part03_01.dbf";
the value of newname for datafile 24 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part03_02.dbf";
the value of newname for datafile 25 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part03_03.dbf";
the value of newname for datafile 26 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part03_01.dbf";
the value of newname for datafile 27 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part03_02.dbf";
the value of newname for datafile 28 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part04_01.dbf";
the value of newname for datafile 29 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part04_02.dbf";
the value of newname for datafile 30 to "+ DATA/pcardtst/datafile/pwrcrd_data_bo_part04_03.dbf";
the value of newname for datafile 31 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part04_01.dbf";
the value of newname for datafile 32 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_bo_part04_02.dbf";
the value of newname for datafile 33 to '+ DATA/pcardtst/datafile/pwrcrd_data_fe_part01_01.dbf;
the value of newname for datafile 34 at "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part01_02.dbf";
the value of newname for datafile 35 to "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part01_03.dbf";
the value of newname for datafile 36 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part01_01.dbf";
the value of newname for datafile 37 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part01_02.dbf";
the value of newname for datafile 38 at "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part02_01.dbf";
the value of newname for datafile 39 to "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part02_02.dbf";
the value of newname for datafile 40 to "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part02_03.dbf";
the value of newname for datafile 41 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part02_01.dbf";
the value of newname for datafile 42 at "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part02_02.dbf";
the value of newname for datafile 43 at "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part03_01.dbf";
the value of newname for datafile 44 to "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part03_02.dbf";
the value of newname for datafile 45 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part03_01.dbf";
the value of newname for datafile 46 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part03_02.dbf";
the value of newname for datafile 47 to "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part04_01.dbf";
the value of newname for datafile 48 to "+ DATA/pcardtst/datafile/pwrcrd_data_fe_part04_02.dbf";
the value of newname for datafile 49 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part04_01.dbf";
the value of newname for datafile 50 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_fe_part04_02.dbf";
the value of newname for datafile 51 to "+ DATA/pcardtst/datafile/pwrcrd_data_batch01.dbf";
the value of newname for datafile 52 at "+ DATA/pcardtst/datafile/pwrcrd_data_batch02.dbf";
the value of newname for datafile 53 to '+ DATA/pcardtst/datafile/pwrcrd_data_batch03.dbf;
the value of newname for datafile 54 to "+ DATA/pcardtst/datafile/pwrcrd_data_batch04.dbf";
the value of newname for datafile 55 to "+ DATA/pcardtst/datafile/pwrcrd_data_batch05.dbf";
the value of newname for datafile 56 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_batch01.dbf";
the value of newname for datafile 57 to "+ DATA/pcardtst/datafile/pwrcrd_ndx_batch02.dbf";
the value of newname for datafile 58 at "+ DATA/pcardtst/datafile/pwrcrd_ndx_batch03.dbf";
the value of newname for datafile 59 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part01_01.dbf";
the value of newname for datafile 60 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part01_01.dbf";
the value of newname for datafile 61 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part02_01.dbf";
the value of newname for datafile 62 at "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part02_01.dbf";
the value of newname for datafile 63 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part03_01.dbf";
the value of newname for datafile 64 at "+ DATA/pcardtst/datafile/pwrcrd_data_index_part03_01.dbf";
the value of newname for datafile 65 at "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part04_01.dbf";
the value of newname for datafile 66 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part04_01.dbf";
the value of newname for datafile 67 to '+ DATA/pcardtst/datafile/pwrcrd_data_hist_part05_01.dbf;
the value of newname for datafile 68 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part05_01.dbf";
the value of newname for datafile 69 at "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part06_01.dbf";
the value of newname for datafile 70 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part06_01.dbf";
the value of newname for datafile 71 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part07_01.dbf";
the value of newname for datafile 72 at "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part07_01.dbf";
the value of newname for datafile 73 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part08_01.dbf";
the value of newname for datafile 74 at "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part08_01.dbf";
the value of newname for datafile 75 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part09_01.dbf";
the value of newname for datafile 76 to '+ DATA/pcardtst/datafile/pwrcrd_index_hist_part09_01.dbf;
the value of newname for datafile 77 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part10_01.dbf";
the value of newname for datafile 78 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part10_01.dbf";
the value of newname for datafile 79 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part11_01.dbf";
the value of newname for datafile 80 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part11_01.dbf";
the value of newname for datafile 81 to '+ DATA/pcardtst/datafile/pwrcrd_data_hist_part12_01.dbf;
the value of newname for datafile 82 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part12_01.dbf";
the value of newname for datafile 83 at "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part13_01.dbf";
the value of newname for datafile 84 to "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part13_01.dbf";
the value of newname for datafile 85 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part14_01.dbf";
the value of newname for datafile 86 to '+ DATA/pcardtst/datafile/pwrcrd_index_hist_part14_01.dbf;
the value of newname for datafile 87 to "+ DATA/pcardtst/datafile/powercard_users.375.723228963";
the value of newname for datafile 88 to "+ DATA/pcardtst/datafile/powercard_users.396.723228959";
the value of newname for datafile 89 to "+ DATA/pcardtst/datafile/powercard_users.399.723228959";
the value of newname for datafile 90 to "+ DATA/pcardtst/datafile/powercard_users.393.723228961";
the value of newname for datafile 91 to '+ DATA/pcardtst/datafile/mig_pc_delivery.309.723228955;
the value of newname for datafile 92 to "+ DATA/pcardtst/datafile/powercard_index_par.403.723228961";
the value of newname for datafile 93 to "+ DATA/pcardtst/datafile/powercard_users.381.723228963";
the value of newname for datafile 94 to "+ DATA/pcardtst/datafile/powercard_index_hist_part01.275.723229411";
the value of newname for datafile 95 at "+ DATA/pcardtst/datafile/powercard_data_fe_part01.364.723229607";
the value of newname for datafile 96 to "+ DATA/pcardtst/datafile/powercard_data_hist_part05.380.723228963";
the value of newname for datafile 97 to '+ DATA/pcardtst/datafile/powercard_data_hist_part10.310.723228959;
the value of newname for datafile 98 in "+ DATA/pcardtst/datafile/powercard_data_hist_part14.268.723229465";
the value of newname for datafile 99 to "+ DATA/pcardtst/datafile/powercard_index_hist_part08.367.723229607";
the value of newname for datafile 100 to "+ DATA/pcardtst/datafile/powercard_index_hist_part09.385.723229087";
the value of newname for datafile 101 to "+ DATA/pcardtst/datafile/powercard_index_hist_part11.286.723229559";
the value of newname for datafile 102 to "+ DATA/pcardtst/datafile/powercard_index_hist_part13.355.723229615";
the value of newname for datafile 103 to "+ DATA/pcardtst/datafile/powercard_data_batch.330.723228961";
the value of newname for datafile 104 to "+ DATA/pcardtst/datafile/powercard_data_hist_part13.335.723229485";
the value of newname for datafile 105 to "+ DATA/pcardtst/datafile/powercard_index_bo_part03.285.723229567";
the value of newname for datafile 106 to "+ DATA/pcardtst/datafile/powercard_index_bo_part01.351.723229617";
the value of newname for datafile 107 to "+ DATA/pcardtst/datafile/powercard_index_fe_part04.261.723229627";
the value of newname for datafile 108 to "+ DATA/pcardtst/datafile/powercard_index_hist_part02.264.723229465";
the value of newname for datafile 109 to "+ DATA/pcardtst/datafile/powercard_data_bo_part01.284.723229573";
the value of newname for datafile 110 to "+ DATA/pcardtst/datafile/powercard_data_hist_part01.406.723229497";
the value of newname for datafile 111 to "+ DATA/pcardtst/datafile/powercard_data_hist_part07.291.723229557";
the value of newname for datafile 112 to "+ DATA/pcardtst/datafile/powercard_data_hist_part08.371.723229615";
the value of newname for datafile 113 to "+ DATA/pcardtst/datafile/powercard_data_hist_part09.346.723228973";
the value of newname for datafile 114 to "+ DATA/pcardtst/datafile/powercard_data_hist_part12.401.723229447";
the value of newname for datafile 115 to "+ DATA/pcardtst/datafile/powercard_index_fe_part02.262.723229625";
the value of newname for datafile 116 to "+ DATA/pcardtst/datafile/powercard_data_fe_part04.374.723229627";
the value of newname for datafile 117 to "+ DATA/pcardtst/datafile/powercard_data_bo_part03.276.723229585";
the value of newname for datafile 118 to "+ DATA/pcardtst/datafile/powercard_data_bo_part04.350.723229633";
the value of newname for datafile 119 to "+ DATA/pcardtst/datafile/powercard_index_bo_part04.317.723229633";
the value of newname for datafile 120 to "+ DATA/pcardtst/datafile/powercard_data_hist_part03.400.723229511";
the value of newname for datafile 121 in '+ DATA/pcardtst/datafile/powercard_index_hist_part12.369.723229605;
the value of newname for datafile 122 to "+ DATA/pcardtst/datafile/powercard_index_hist_part05.373.723229641";
the value of newname for datafile 123 to "+ DATA/pcardtst/datafile/powercard_data_par.319.723229635";
the value of newname for datafile 124 to "+ DATA/pcardtst/datafile/powercard_users.402.723228957";
the value of newname for datafile 125 to "+ DATA/pcardtst/datafile/powercard_index_batch.356.723229609";
the value of newname for datafile 126 to "+ DATA/pcardtst/datafile/powercard_index_bo_part02.256.723229647";
the value of newname for datafile 127 to "+ DATA/pcardtst/datafile/powercard_index_hist_part07.320.723229641";
the value of newname for datafile 128 to "+ DATA/pcardtst/datafile/powercard_index_hist_part04.258.723229615";
the value of newname for datafile 129 to "+ DATA/pcardtst/datafile/powercard_data_bo_part02.366.723229651";
the value of newname for datafile 130 to "+ DATA/pcardtst/datafile/powercard_data_hist_part06.348.723228965";
the value of newname for datafile 131 to "+ DATA/pcardtst/datafile/powercard_data_hist_part02.307.723229525";
the value of newname for datafile 132 to "+ DATA/pcardtst/datafile/powercard_index_fe_part01.370.723229647";
the value of newname for datafile 133 to "+ DATA/pcardtst/datafile/powercard_index_fe_part03.352.723229619";
the value of newname for datafile 134 to "+ DATA/pcardtst/datafile/powercard_index_hist_part06.266.723229659";
the value of newname for datafile 135 to "+ DATA/pcardtst/datafile/powercard_index_hist_part10.329.723229027";
the value of newname for datafile 136 to "+ DATA/pcardtst/datafile/powercard_index_hist_part03.337.723229651";
the value of newname for datafile 137 to "+ DATA/pcardtst/datafile/powercard_index_hist_part14.263.723229627";
the value of newname for datafile 138 to "+ DATA/pcardtst/datafile/stpmw_data01.dbf";
the value of newname for datafile 139 to "+ DATA/pcardtst/datafile/undotbs1_2.dbf";
the value of newname for datafile 140 to "+ DATA/pcardtst/datafile/undotbs1_3.dbf";
the value of newname for datafile 141 to "+ DATA/pcardtst/datafile/undotbs1_4.dbf";
the value of newname for datafile 142 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part05_03.dbf";
the value of newname for datafile 143 to "+ DATA/pcardtst/datafile/powercard_data_hist_part05.426.851242407";
the value of newname for datafile 144 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part11_02.dbf";
the value of newname for datafile 145 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part12_02.dbf";
the value of newname for datafile 146 to "+ DATA/pcardtst/datafile/pwrcrd_data_hist_part05_04.dbf";
the value of newname for datafile 147 in "+ DATA/pcardtst/datafile/pwrcrd_index_hist_part05_02.dbf";
the value of newname for tempfile 1 to "+ DATA/pcardtst/tempfile/temp1.dbf";
the value of newname for tempfile 2 to "+ DATA/pcardtst/tempfile/temp2.dbf";
the value of newname for tempfile 3 to "+ DATA/pcardtst/tempfile/temp3.dbf";
the value of newname for tempfile 4 to "+ DATA/pcardtst/tempfile/pwrcard_temp01.dbf";
the value of newname for tempfile 5 to "+ DATA/pcardtst/tempfile/pwrcard_temp02.dbf";
the value of newname for tempfile 6 to "+ DATA/pcardtst/tempfile/pwrcard_temp03.dbf";
the value of newname for tempfile 7 to "+ DATA/pcardtst/tempfile/pwrcard_temp04.dbf";
duplicate target database in the pcardtst log file
GROUP 10 ('+ DATA/pcardtst/onlinelog/group_10_01') size 512 M,
GROUP 10 ('+ DATA/pcardtst/onlinelog/group_10_02') size 512 M,
GROUP 11 ('+ DATA/pcardtst/onlinelog/group_11_01') size 512 M,
GROUP 11 ('+ DATA/pcardtst/onlinelog/group_11_02') size 512 M,
GROUP 12 ('+ DATA/pcardtst/onlinelog/group_12_01') size 512 M,
GROUP 12 ('+ DATA/pcardtst/onlinelog/group_12_02') size 512 M,
GROUP 13 ('+ DATA/pcardtst/onlinelog/group_13_01') size 512 M,
GROUP 13 ('+ DATA/pcardtst/onlinelog/group_13_02') size 512 M,
GROUP 14 ('+ DATA/pcardtst/onlinelog/group_14_01') size 512 M,
GROUP 14 ('+ DATA/pcardtst/onlinelog/group_14_02') size 512 M,
GROUP 7 ('+ DATA/pcardtst/onlinelog/group_7_01') size 512 M,
GROUP 7 ('+ DATA/pcardtst/onlinelog/group_7_02') size 512 M,
GROUP 8 ('+ DATA/pcardtst/onlinelog/group_8_01') size 512 M,
GROUP 8 ('+ DATA/pcardtst/onlinelog/group_8_02') size 512 M,
GROUP 9 ('+ DATA/pcardtst/onlinelog/group_9_01') size 512 M,
GROUP 9 ('+ DATA/pcardtst/onlinelog/group_9_02') size 512 M;
output channel t1;
output channel t2;
output channel t3;
}
But gettting error below
DATA FILE
"+ DATA/pcardtst/datafile/system.635.878984933".
CHARACTER SET WE8ISO8859P1
output channel: t1
output channel: t2
output channel: t3
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of Db in dual at 06/05/2015 14:26:01
RMAN-06136: the auxiliary database ORACLE error: ORA-01503: CREATE CONTROLFILE failed
ORA-01167: two files are the same file/group number or the same file
ORA-01517: Member of journal: '+ DATA/pcardtst/onlinelog/group_10_02.
ORA-01517: Member of journal: '+ DATA/pcardtst/onlinelog/group_10_01.
Complete recovery manager.
Kind regards.
Younus

Hi Eric,.

Let's not your syntax for log files. Check out the docs:

http://docs.Oracle.com/CD/B28359_01/backup.111/b28270/rcmdupdb.htm#BRADV89956

You need only name the Group once followed a list separated by commas of the logfile members.

Concerning

Thomas

Restore/recovery of database HRCS90 question: psimage2.dbf

People,
Hello. On December 2, 2013, I backed up my instance of database with RMAN with Oracle Linux 5 HRCS90. the backup of the database to run correctly. 2 files 'full_0doqhbqc_13_1' and 'full_0eoqhce9_14_1' are saved in the /backup_database_instance_HRCS90 directory.

Because my HRCS90 database has been damaged, I need to restore the database to HRCS90 until the time 02-Dec_13 when it is saved.
First, do not use SET up to THAT. I have run the commands below:
RMAN > CONNECT TARGET;
RMAN > RESTORE database;
The system is in place the error message as below:
RMAN-06956: create the data file failed; Retry after the withdrawal of the /u01/oradata/HRCS90/psimage2.dbf of the OS.

So, I delete the /u01/oradata/HRCS90/psimage2.dbf file and do not have a copy of it.
I run RESTORE DATABASE and the psimage2.dbf file is re-created.
The output from the RESTORE DATABASE command is:
Restoration complete, duration: 00:15:54
Finished restore at February 1, 14.
Then I run the following command:
RMAN > RECOVER DATABASE;
Its release: WARNING: media recovery until all SNA 1947113. Finished recover at February 3, 14.
Second time, because I need the database prior to 12/02/2013 when she has been saved, I run the command below:
RMAN > RUN {SET until TIME ' to_date (February 12, 2013: 00:04:56 ',' DD-MM-YYYY: HH24:MI:SS') ";} RESTORE THE DATABASE ;}
The commands run correctly and restore complete above.

Then I run the command below:
SQL > ALTER DATABASE OPEN RESETLOGS;
His output: failure to change the db command. File 121 was created in the future of incomplete recovery. Data file 121: u01/oradata/HRCS90/psimage2.dbf.
RMAN > RECOVER NOREDO of DATABASE;
Its release: recover command failed. Data file 121 must be restored.

121 data file is the u01/oradata/HRCS90/psimage2.dbf file. I have made sure the directory/u01/oradata/HRCS90/has rwx for all users and groups permissions.

RESTORE DATABASE SET up THAT do not recreate the file psimage2.dbf RESTORE DATABASE while recreate the file psimage2.dbf.
I deleted the psimage2.dbf file and cannot resume. I can't find the ORA-1248 by DBPITR article using a current controlfile (Doc ID 1558515.1).
My question is:
Any folk can tell me how to RESTORE/RECOVERY of database HRCS90 with the VALUE up to THAT in other way for example using the file command?
or how to fix psimage2.dbf file that has been deleted by me?
Thanks in advance.

Congratulations! Your database is open so not required recovery (recovery database noredo).

I'm glad that it worked for you. Since you open this database with reset logs, it is recommended that you take a Level0 backup costs.

HTH
Anuj

EBS R12.1.3 on the 12 c RAC database

We are running EBS version 12.1.3 on RAC cluster for node 3 11 GR 2 and works well. We are currently working on upgrading our RAC database to 12 c.
Looking at the Oracle support, I can see there are notes related to stamps of interoperability thus recommended on 12 c init parameters.
I can't find any other relevant document where there are performance problems and possible solutions.
I'm sure that the people would have taken this path... ghoulish someone please provide input as to what measures we should take to make sure that we don't encounter unforeseen problems.
Know your opinion.
TO THE

I'm not aware of important performance issues at the top of the 12.1.0.1 of database with R12, and I believe that if you apply all the patches in the following docs, then you should be good. If you have specific concerns, please do not hesitate to share with us.

With the help of Oracle 12 c version 1 Real Application Clusters with Oracle E-Business Suite Release 12 (Doc ID 1490850.1)

Interoperability note EBS 12.0 or 12.1 with RDBMS 12cR1 (Doc ID 1524398.1)

12.1.0.1 database with Oracle E-Business Suite certified

https://blogs.Oracle.com/stevenChan/entry/12_1_0_1_db

Thank you

Hussein

Freezing of the Oracle RAC databases

Hi all
We use oracle database 11g version 11.2.0.1.0 RAC database standard edition having two active instances.
Recently, we have been confronted with a database, freezing problem, the regular orders program has not run in DB.
Can anyone suggest me how to find the reason of this problem and what needs to be monitored side DB for a few days?
Thanks in advance.

John, but this assumes that actually perform the jobs - would not quite the case.

My meat with the question (as Konda explained), is owner of problem. Developers who seem to refuse to have their process not running problem, he blames on the database and now awaits the DBA to own the problem simply because of their opinion without merit (and a little ignorant) as the database "frozen".

It is unfair to expect the DBA through all kinds of hoops to find the 'problem' in a bottom-up analysis of the problem.

A fundamental question for developers should be, prove it. Showed the code to run (work performed). And then a question why there is no instrumentation in their code just to say what's happened...

How to find the list of users in the rac database?
Friends,

OS: OEL 6.3 64-bit
DB: 11 GR 2 (11.2.0.3)
2 node rac ASM.

in node 1, I connected as sys.
and in the second node, I logged as hr
When I try to check user names in v$ session in node1... I have not found the hr user name...
How can I check the list of user name for all users who are connected to the rac database?
If I check in the session of each node v$ I come, but how can I check any node for all the loggedin user names. ?

Thank you
use gv$ session

INST_ID select lets you know which instance.

Multiple RAC databases on IM even using different subnets for Public i / face
Hello. We are setting up a 2 cluster nodes. This group will be the host of several RAC databases. For security reasons, our network team want to create separate subnets for the application traffic to each RAC specific database on the cluster.

For example, request 1 to 2 application servers that will connects to database PROD1 RAC via a single subnet, application 2-3 application servers etc which will be connected to the database RAC PROD2 via a different subnet,.

In addition, the network team want to configure a subnet separate management DBA etc. will use to administer all the RAC databases and infrastructure in the cluster.

Version 11.2.0.2 grid infrastructure. The database versions vary from 10.2.0.x to 11.2.0.2. All databases will use RAC.

We want to take advantage of the features of earphone SCAN to support connectivity to databases on the cluster. 2199620 [https://cn.forums.oracle.com/forums/thread.jspa?threadID=2199620] thread suggests that 11 GR 2 supports several subnets, that seems to be exactly the functionality we need. Please can you confirm how it works and tell us any documentation (standard docs, whitepapers, MOS, etc.) which could help us to configure it.

Document referenced in thread 2199620 was not exactly what we were looking for and didn't translate too well in Google Translate.

Any guidance is appreciated. Thanks, Rich.

Similar topics:

https://CN.forums.Oracle.com/forums/thread.jspa?MessageID=9846298? (Double SCAN on multi cluster hosted)
https://CN.forums.Oracle.com/forums/thread.jspa?threadID=2199620 (scan earphone in VLAN OAM)

Published by: 887449 on 26-Sep-2011 01:41
Hello

With Oracle 11.2, you can have multiple public networks accessing your Oracle RAC.
You must set the init.ora new LISTENER_NETWORKS setting so users are load-balanced on their network. Services are related to the networks so users who connect with network 1 will use a different service as network 2. Each network will have its own VIP.

Impossible to use both network SCAN function because SCAN will work into a single network and on GRID 11.2 you cannot config more than a SCAN.

So, you can have a public network (for example, 10.10.10.0) with SCAN/VIP and another public network (e.g. 192.168.217.0) you will only use VIP on TNSNAMES.ora.

You configure a Service (A) on the network (10.10.10.0) and one other Service (B) on the network (192.168.217.0).

In the example above using (A) Service you will configure SCAN (scan host) and using Service (B), you must configure all address VIP.

Kind regards
Levi Pereira

Published by: Levi Pereira Sep 26, 2011 18:03

ORA-20600 error when trying to add the RAC database
I get the following error when trying to add the RAC database in grid control. Any idea?.

ORA-20600: the specified target is being deleted

This database does not exist in the target. But, I still cannot add.
Check metalink Note: unable to add Rac Database grid control get error Ora-20600 [1218797.1 ID]

You will have to wait a while and check the status.

Grid Control 11g of the problems with the basic policy of RAC database
We have a group of three nodes 11 GR 2 (rac1, rac2, rac3) and a policy based RAC database 11 GR 2 (ORCL) with cardinality 2 (ORCL_1 and ORCL_2) on this group. Used to monitor the Control 11g Grid infrastructure. Founded political RAC databases are linked to the pools of the server and not to the cluster nodes, therefore, restart the cluster database instances can run on both on 3 nodes in the cluster. For example, if ORCL_1 is running ORCL_2 and rac1 rac2 Sir after a full reboot ORCL_1 and ORCL_2 can be run on rac2 and rac3 respectively. Binding of the pool with two special nodes will be as if we use database RAC database administrator and not the policy based.

Now the problem is that Grid Control registers the services in database with the node that is running the instance due to which, once the instances are started on a different node, she complained authorities are declining. We don't have to then reconfigure database instances and say Grid Control that they are now on another node. However, this removes the history of AWR for these instances.

Is there a solution to this problem?

Kind regards

Kashif.
Hi koko,.

to work around this problem (I think that there is no "automatic" support in the current version of EM for switching hosts databases), you can create an ACTION_SCRIPT for your database cluster resource that is running the relocate_targets command emcli (so an emcli should be placed on all nodes of your and recorded with Super Administrator privileges). So every time you start your database resource, this script command / move the target to the current host without losing any historical information.

Best regards
Robert

Edit: You can find an example of the command emcli in this document written by Rob Zoeteweij: http://oemgc.files.wordpress.com/2011/02/manage-node-failover-in-an-active-passive-setup-using-oracle-enterprise-manager-grid-control1.pdf
In this scenario is an active/passive environment, but the command itself appies to your situation, too.

Published by: Robert Hanuschke on August 1, 2011 13:11

Steps to restore a RAC database

Similar Questions

Maybe you are looking for