Often we run into situation where we wanted to identify if there are any Oracle DB level events enabled that are writing to a trace file. One easy way to identify events enabled at the system level is by running the following command. If you want to identify events/trace enabled at the session level, set
List all events enabled in Oracle DB Read More »
Most of Pure FlashArray customers are used to the snapshot functionality that helps them in taking either a crash-consistent or application-consistent snapshot in a flash (literally and figuratively) irrespective of the database size. While this helps them in protecting the database from any accidental changes or creating clones for development and test usage but cannot
RMAN Backups using mount host on Flasharray Read More »
To create a physical standby database, DBAs generally take an RMAN backup of the primary database, transfer them to the standby system and recover/duplicate them to create the standby database. Based on the size of the database and the distance between the sites where the standby database is created, the backup/restore, as well as transfer, can
Physical Standby database creation using FlashRecover Snapshots Read More »
A lot of customers have requested the steps to clone an Oracle database on ASM hosted on Pure FlashArray, on to the same database host like cloning QA database into DEV on the same host. The problem is, cloning an ASM lun and mounting it onto the same host would result in two luns with
Cloning Oracle Database on ASM with Pure FlashArray on to same host Read More »
In Linux, ASMLib provides the wrapper for managing the ASM disks. To identify the underlying physical device that the ASM disk point to, you can use the oracleasm querydisk command. The querydisk option will list the major and minor numbers that can be used to match the physical device. The following example was run on
Identify the ASM device from ASMLib Read More »
