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 …
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 …
While thin provisioning enables higher capacity volumes without the guilt of actually wasting the space, we still see storage admins creating volumes close to what the DBAs have asked for and hence there is always a need for expanding the volume when the current volume reaches its capacity. When it comes to ASM, lot of DBAs prefer to …
Online resizing of Oracle volumes on Pure FlashArray Read More »
