Try logging into ASM instance and query V$ASM_DISK i.e
export ORACLE_SID=+ASM1
sqlplus “/ as sysdba”
select name,path,mount_status,header_status from V$ASM_DISK;
with regards to naming convention, I think naming convention should follow /dev/[a-z]* naming convention instead of /dev/multipath/[a-z]*
It could be this or it could be that as the name of multipath device is also ending with sdb2,sdb3 and we are also excluding the disk ending with sdb2,sdb3. I am not too sure on this.
I think best way would be to actually first query V$ASM_DISK output.
First I believe that you should check ASM instance and see if you are able to see the disks on Node 1. From above output it looks that you connected to node 1 DB instance and not asm instance. This can also be seen from crs_stat output which shows that asm instance is up on node 1.
Secondly name multipath device as multipatha,multibathc instead of /multipath/sdb1 etc
1)In RAC all instances will show same data from asmcmd. To use asmcmd, you need to export ORACLE_SID to +ASM4 by logging on 4th instance.
2)When you create database using DBCA, oracle automatically add’s database to the OCR. In case you wish to add instance, then use DBCA instance management option to add instance which will also register the database. In case you created db/added instance manually, then you need to use srvctl command for same
Apologies for late reply. You will have to write a OS script and then register it OS defined metrics. You can also have it as User defined metric with query on V$BACKUP view.
I would say it’s a question which never came to my mind. This is my understanding from the captcpu.sql notes.
Catcpu.sql inturn calls a script called catbundle.sql which is located under $ORACLE_HOME/rdbms/admin
This script will load sql files in database by looking in bundledata_CPU.xml for file information for particular patch. It will be creating a dynamic apply sql file and run it.
<I>I have one doubt if i will not copy the online redo log then how it will get generated.</I>
>> When you open the database with resetlogs , it will create the redo logs.
Secondly did you copy the archived logs after you ended the backup (Also had to issue switch logfile). I did a test setup and you need to issue following
<br />
SQL> recover database using BACKUP CONTROLFILE until cancel;<br />
ORA-00279: change 542839 generated at 11/25/2008 02:38:29 needed for thread 1<br />
ORA-00289: suggestion :<br />
/u01/app/oracle/product/10.2.0/db_1/flash_recovery_area/TEST/archivelog/2008_11_<br />
25/o1_mf_1_3_%u_.arc<br />
ORA-00280: change 542839 for thread 1 is in sequence #3<br />
<br />
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}<br />
You need to give the archived log name here and then say “Cancel” and open the database
<br />
<br />
/u01/app/oracle/oradata/TEST/o1_mf_1_3_4lqgzpsg_.arc<br />
ORA-00279: change 543072 generated at 11/25/2008 02:48:54 needed for thread 1<br />
ORA-00289: suggestion :<br />
/u01/app/oracle/product/10.2.0/db_1/flash_recovery_area/TEST/archivelog/2008_11_<br />
25/o1_mf_1_4_%u_.arc<br />
ORA-00280: change 543072 for thread 1 is in sequence #4<br />
ORA-00278: log file '/u01/app/oracle/oradata/TEST/o1_mf_1_3_4lqgzpsg_.arc' no<br />
longer needed for this recovery<br />
<br />
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}<br />
/u01/app/oracle/oradata/TEST/o1_mf_1_4_4lqgzsbq_.arc<br />
ORA-00279: change 543074 generated at 11/25/2008 02:48:57 needed for thread 1<br />
ORA-00289: suggestion :<br />
/u01/app/oracle/product/10.2.0/db_1/flash_recovery_area/TEST/archivelog/2008_11_<br />
25/o1_mf_1_5_%u_.arc<br />
ORA-00280: change 543074 for thread 1 is in sequence #5<br />
ORA-00278: log file '/u01/app/oracle/oradata/TEST/o1_mf_1_4_4lqgzsbq_.arc' no<br />
longer needed for this recovery<br />
<br />
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}<br />
cancel<br />
Media recovery cancelled.<br />
SQL> alter database open resetlogs;<br />
<br />
Database altered.<br />
How are you trying to clone the database? Are you using RMAN or user managed backups..And could you let us know the steps you have performed and also the error being faced by you..
You do not need the redo log for recovery. You will require only the datafiles and the archived logs. You will be required to do incomplete recovery in this case. In case you are using RMAN, you can do following
run
{
set until time “to_date(’24-nov-2008 16:00:00′, ‘dd-mon-rrrr hh24:mi:ss’)”;
restore database;
recover database;
}
20 November, 2008 at 8:21 am
in reply to: asm tool#2032
asmtool or asmtoolg(Gui version) helps to stamp the new disks on windows for using as ASM Disks. You can use asmtoolg utility present in %ORACLE_HOME%bin directory which will provide GUI for stamping the disks.
As per Oracle docs
asmtoolg shows the devices available on the system. Unrecognized disks are labeled as a "Candidate device." Unformatted partitions are labeled as "Oracle raw device file." Stamped ASM disks are labeled as "Stamped ASM disk," and unstamped ASM disks are labeled as "Unstamped ASM disks." The tool also shows disks that are recognized by Windows as a file system (such as NTFS). These disks are not available for use as ASM disks, and cannot be selected.
You can find the above information and also steps to use asmtoolg at below link
This blog reflect our own views and do not necessarily represent the views of our current or previous employers.
The contents of this blog are from our experience, you may use at your own risk, however you are strongly advised to cross reference with Product documentation and test before deploying to production environments.
Recent Comments