A Tale of Two Databases
In my role at EMC, I get to meet and work with many customers who have large scale deployments of Oracle. They tell me that one of the tedious aspects of the job is the need to keep production running without interruption, while also maintaining a non-production environment for testing and development. The fact of the matter is that DBAs are Oracle experts, but not experts on creating copies on the SAN. Often times in large companies, the Oracle DBA has to submit requests in queue to receive copies of a particular database. This “queue” is often managed by the Storage Administrator. This is an inefficient workflow for a number of reasons including:
- The Oracle DBA has to wait to receive the copy. The longer the wait, the more outdated the non-production environment becomes.
- The Storage Administrator frequently has higher priority work than creating copies for the DBA.
- Using native tools, automating the copy job can create inflexibility. Even if the Storage Administrator automates the Oracle copy job, the DBA will need them to intervene to make changes when additional DB’s or other changes are made