This is a short article on converting existing non-container (non-cdb) 12c database as pluggable database (pdb) to existing container database (cdb).
Version of Non-CDB database = 188.8.131.52
Version of CDB database = 184.108.40.206
Following steps will plug-in non-cdb database into cdb as pdb and also will upgrade the version to 220.127.116.11
My non-cdb database name is deo12c
My cdb database name is deocdb
Performance schema, as name suggest is a tool for monitoring MySQL performance. It was implemented staring from MySQL 5.5 and improved further in MySQL 5.6. Performance Schema includes set of tables that gives information on how database is performing. It provides a way to inspect internal execution of the server at run time. Performance schema monitors every “event” the server does that takes time and has been instrumented so that timing information can (more...)
Oracle has come up with new feature called multitenant database. Using this feature we can have many pluggable databases plugged into single container database.
This article explains pluggable databases architecture and how to create them.
I am not covering administration part. Viewers can check the documentation mentioned in reference section to check administrative part for managing pluggable databases.
One of the high-profile new features of Oracle 12c Enterprise Edition(EE) is the multitenant option (more...)
Replication is one of the basic and most essential feature available in MySQL. Replication allows you to maintain additional copy of database on another server and keep itself updated with latest changes in master databases. Having another copy of data (other than backup) is always a good option. In case of any issues on master server we can always failover to slave and make it a master. This provides high availability. You can have (more...)
What is GTID ?
GTID stands for Global Transaction Identifier. This is a new feature introduced in 5.6 version.
I have given a link in reference section of this article which explains the concept of GTID.
Global transaction identifier is a unique transaction ID assigned to every transaction that happens in MySQL database. This ID has specific importance in maintaining replication slave. Using this ID we can easily track which transactions has been applied to (more...)
MySQL utilities are set of scripts provided for DBAs for general database administration. These are basically command line utilities which can be used to perform various tasks.
Following is the listing of MySQL utility version 1.3 that I installed in my environment
advait.desktop$ ls -lL /usr/local/bin/mysql*
-rwxr-xr-x 1 root root 10546 Mar 26 00:34 /usr/local/bin/mysqlauditadmin
-rwxr-xr-x 1 root root 13443 Mar 26 00:34 /usr/local/bin/mysqlauditgrep
-rwxr-xr-x 1 root root 10142 Mar 26 00:34 /usr/local/bin/mysqldbcompare
I am exploring another database storage solution “MySQL” to understand practical applications of using MySQL in our environment.
This is one of the many articles that I will be writing on MySQL. This article gives you brief steps to installing MySQL on Linux.
Nothing different than what is provided in MySQL documentation except that this is less elaborate with only required steps compared to MySQL documentation.
This is how you can do the installation:-
Why noSQL ?
From past few years (after 2009) we are seeing high trend towards noSQL databases. Many big enterprises are exploring option for moving services to noSQL databases and many already did.
Its not that existing Oracle databases cannot support the system. We have many rich features and products from Oracle which can be made to work together to support huge internet applications. But there are many vantage points to consider when we are designing (more...)
What it used to be
After Oracle 9.2, there has been a significant changes in redo behavior. Before 10g, Oracle used to have a single log buffer for writing redo information which eventually gets written to online redo logs in round robin fashion. Of course if your database is (more...)
One of the parameter we configure in physical standby setup is about how much amount of time LGWR on primary should wait for physical standby to respond.
When changes happens on primary side, those redo changes are shipped on physical standby database. If physical standby database is down or if (more...)