Oracle12c DB Service failover Behavior change

-bash-4.1$ srvctl stop instance -h

Stops the database instance.

Usage: srvctl stop instance -db {-node | -instance } [-stopoption ] [-force] [-failover]
-db Unique name for the database
-node Node name
-instance “” Comma separated instance names
-stopoption Options to instance shutdown command (e.g. NORMAL, “TRANSACTIONAL LOCAL”, IMMEDIATE, or ABORT)
-force Forcibly stop the instance and any running services.
-failover Allow the running services to fail over to another instance
-help Print usage
-bash-4.1$
-bash-4.1$
-bash-4.1$ srvctl stop instance -d blrdb -s ndb1 -f
PRKO-2002 : Invalid command line option: -s
-bash-4.1$
-bash-4.1$ srvctl stop instance -d blrdb -i ndb1 -f
Invalid instance name(s): ndb1
-bash-4.1$
-bash-4.1$ srvctl stop instance -d blrdb -i blrdb1 -f
-bash-4.1$ srvctl start instance -d blrdb -i blrdb1
-bash-4.1$
-bash-4.1$
-bash-4.1$ srvctl stop instance -d blrdb -i blrdb1 -failover
-bash-4.1$
-bash-4.1$ srvctl start instance -d blrdb -i blrdb1

tfactl – Diagnostic data Collection for troubleshooting the issue of GI, ASM, and RAC

Diagnostic data is needed for troubleshooting the issue.

Execute the action plan described in [ DOC ID 2041228.1 ] “SRDC – Data Collection for Grid Infrastructure, Storage Management, and RAC” and upload the information collected to ensure rapid resolution.

Use the following command to run TFA:
$GI_HOME/tfa/bin/tfactl diagcollect -from “MMM/dd/yyyy hh:mm:ss” -to “MMM/dd/yyyy hh:mm:ss”

Date and time format example: “Jul/1/2014 21:00:00”
Specify the “from time” to be 4 hours before and the “to time” to be 4 hours after the time of error.

/u01/app/12.1.0.2/grid/tfa/bin/tfactl diagcollect -from “Sep/3/2016 12:00:00” -to “Sep/4/2016 08:00:00”

/u01/app/12.1.0.2/grid/tfa/bin/tfactl diagcollect -from “Sep/4/2016 01:00:00” -to “Sep/4/2016 02:28:00”

CLSU-00100: operating system function: opendir failed with error data: 2

CLSU-00100: operating system function: opendir failed with error data: 2

[root@localhost ~]# /u01/app/12.1.0.2/grid/bin/crsctl check crs
Oracle Clusterware infrastructure error in CRSCTL (OS PID 33435): ADR home path /u01/app/oracle/diag/crs/localhost/crs does not exist; ADR initialization will try to create it

CRS-4639: Could not contact Oracle High Availability Service

http://www.oracle-scn.com/asm-not-starting-after-changing-the-hostname-or-ip-address-of-the-server/
https://mehmeteser.wordpress.com/2013/02/21/rename-host-has/
http://www.toadworld.com/platforms/oracle/b/weblog/archive/2016/01/23/how-to-fix-quot-cant-open-scr-home-dir-scls-scr-getval-quot-error

hostname csm-clstrnode1

crsctl start crs

ORA-15087: disk ‘string’ is formatted as an ext2/ext3 or OCFS2 file system

Problem:
ORA-15087: disk ‘string’ is formatted as an ext2/ext3 or OCFS2 file system

Document:
Cannot See ASM Disks From Asmca when using udev rules on rhel 6 (Doc ID 1911888.1)

SOLUTION
Clear the header by writing 25 MB of null, after clearing the header ASMCA and KFOD can able to see the devices
For example:

# dd if=/dev/zero of= bs=1M count=25

How to find raw partition from asm disk ?

If your ASM is using RAW devices then its pretty easy to find out by just looking into your /etc/sysconfig/rawdevices (hope your DBA had made some comments as to which RAW devices is for which).

If you are using ASMLib then its kinda hard to find out the exact mapping of your ORACLEASM stamped device to the Linux Physical Device.

To make it simple, here are the steps to find the Physical Device that is mapped to your ASMLib disk:
Run the following as a root:
1. /etc/init.d/oracleasm listdisks — lists all the disks that are in your ASM
2. /etc/init.d/oracleasm querydisk -d disk_name_that_you_wan_to_find_physical_device (this name is from the above result)
3. Note the values in braces [ n1, n2] from the above command result
4. do ls -al /dev/ |grep n1 |grep n2 — n1 and n2 are the values from the above step you noted

That gives you the device number its mapped to.

#/etc/init.d/oracleasm querydisk -d TIER2_DATA01
Disk “DG1_DISK1” is a valid ASM disk on device [253, 26]

#ls -l /dev |grep 253 |grep 26
brw-rw—- 1 root root 253, 26 Nov 3 12:03 dm-26

From the above dm-26 is the physical device that DG1_DISK1 ASM Disk is mapped to

http://sanoralife.blogspot.in/2012/02/how-to-find-mapping-of-asm-disk-to.html
https://blogs.oracle.com/AlejandroVargas/entry/mapping_asm_disks_to_physical