Monday, June 29, 2015

gDBClone script Database Clone/Snapshot Management Script

gDBClone script Database Clone/Snapshot Management Script. A Simple Approach to Managing Test and Development Environments Leveraging ACFS Snapshots on your environment

The diagram below illustrates a typical test and dev environment that can be created and managed with the gDBClone command.

Monday, June 15, 2015

Using on ZFSSA:ZFSSAADM - Copy On Write (COW) on ZFS Storage Appliance (ZFSSA)

Database cloning with Copy On Write (COW) on ZFS Storage Appliance (ZFSSA). The method that I will demonstrate is the method of using the API ZFSSAADM for database cloning for data on ZFSSA. ZFSSAADM is an API which is part of the 12c Oracle software.

What we have is the following setup

  • An Oracle database 12c server 
    • With NFS mount point to the ZFS Storage Appliance Operational 
  • Direct NFS for databases Oracle ZFS Storage Appliance Simulator [Server IP]

    Validate my environment and settings

    Validate if it is a CDB database

Tuesday, March 31, 2015

sysresv - System Resource Verifier utility for ipc resource Database

Is there a solution to identified the memory semaphores for an database.
Normal we use:

ipcs -as|grep oracle

But from the ORACLE_HOME/bin there is a sysresv that will detect this for a database instance.
Use the sysresv utility to display the status of an Oracle instance and identify the operating system resources it uses, such as the memory and semaphore parameters


Thursday, May 1, 2014

Queryable Patch Inventory or DBMS_QOPATCH

New in Oracle 12c is queryable Opatch. Oracle offers a set of tables and a PL/SQL packages to query the Oracle Inventory.Prior to Oracle 12c, it was not easy to List Oracle patches. Now from Oracle 12c and beyond, you can use the DBMS_QOPATCH package to list all patches.

Using DBMS_QOPATCH; Oracle Database 12c has a PL/SQL - SQL interface for viewing patch information using a select statement instead a OS ORACLE opach command. This new interface view all the patch information available as part of the ,OPatch lsinventory -xml command conform the the OS Oracle opatch command. The package DBMS_QOPATCH accesses the Oracle Universal Installer (OUI) patch inventory in real time to provide patch and patch meta information.

Friday, March 7, 2014

EM database Control Using EMCA fails when Service Name contains Hyphen.

When using "emca -config dbcontrol db -repos create -cluster" on a RAC Database the installation of EM database Control fails. Investigation of the logs will see an error in the emca_repos_config_.log

Thursday, December 12, 2013

Oracle 12c - Oracle-Supplied -

The installation of an Oracle database is done by executing serveral scripts. Those scripts perform operations such as creating data dictionary views and installing options. Oracle has now introduced multiple database [PDB's] inside one database [CDB]. For maintenacne and a new strategy Oracle's best way is to run SQL scripts and SQL statements is done by using It can run them in the root and in specified PDBs in the correct order, and it generates log files that you can view to confirm that the SQL script or SQL statement did not generate unexpected errors.
It also starts multiple processes and assigns new scripts to them as they finish running scripts previously assigned to them.

Example of the Statement
perl /u02/app/oracle/product/12.1.0/dbhome_1/rdbms/admin/ -n 1 -l /u02/app/oracle/admin/CDB1/scripts -b catalog /u02/app/oracle/product/12.1.0/dbhome_1/rdbms/admin/catalog.sql = Perl Module for creating - upgrading CATalogs for CONtainer databases

Tuesday, December 10, 2013

Creating pluggable databases with and without OMF structure; [CDB=OMF storage structure]

For creating a pluggable database you have to consider how to create the pluggable database, and what are you current CDB settings. In this post i have played with and without OMF and difference file structures inside ONE CDB database. Mostly pluggable database will be created from the seed database. What is needed when you want the oracle files of the pluggable database on an other file structure storage. What will you use, and when should you use what. After the createing of a pluggable database, you need possible extra steps inside the pluggable database to keep your optimalisize storage environment. Think about the steps that are needed with a single none CDB, those steps would also be needed on a pluggable database by or after the creating steps. When you don't think about this, the change is that you get a spaghetti mixture of files inside your environment.

Lets play;