Here I will be explaining how to perform disaster recovery of a database server where server has been lost because of hardware failure and needs everything to be prepared from scratch. This would require that a same type of server has been provisioned which has matching resources as we had on the actual production server. Before moving forward,
Oracle Installation guides, Linux Administration tips for DBAs, Performance Tuning tips, Disaster Recovery, RMAN, Dataguard and ORA errors solutions.
No contents from my website can be published anywhere else without my permission. Test every solution before implementing in the production environment.
Thursday, January 8, 2015
Wednesday, January 7, 2015
Converting a non-CDB database to a PDB
Here I would explain how do we convert a non-CDB (non-container database) to a PDB (pluggable database) in an existing CDB (container database) on the same host as well as on a different host. For this example, I used Oracle 12.1.0.2 software version and this example assumes that there is already a container database with name “mycdb”
Upgrading Grid Infrastructure 11g to 12c
In this post I will be
demonstrating the steps to upgrade Oracle Grid Infrastructure (GI) 11g
(11.2.0.4) to Grid Infrastructure 12c (12.1.0.2). Since ASM runs from GI home,
ASM would be upgraded automatically while the upgrade of GI. First release
version of 12c was 12.1.0.1 and for this example, I would be using 12.1.0.2. As
we know that
Monday, January 5, 2015
PRCA-1057 Failed to retrieve the password file location used by ASM asm
PRCA-1057 : Failed to retrieve the password file location used by ASM asm PRCR-1097 : Resource attribute not found: PWFILE
After upgrading your grid infrastructure 11g to 12c, you will notice that executing command “srvctl config asm” returns abovementioned error messages.
Sunday, January 4, 2015
Upgrading Oracle 11g Database to 12c using DBUA
For manual upgrade guide from 11g to 12c or 12.1.0.1 to 12.1.0.2, click here
Here I would be discussing how to upgrade Oracle 11g (11.2.0.4) database to 12c (12.1.0.2) on the same server. This upgrade process was done on Linux 6 (x86_64). I used DBUA (Database Upgrade Assistant) to perform this upgrade. DBUA
Here I would be discussing how to upgrade Oracle 11g (11.2.0.4) database to 12c (12.1.0.2) on the same server. This upgrade process was done on Linux 6 (x86_64). I used DBUA (Database Upgrade Assistant) to perform this upgrade. DBUA
Tuesday, December 30, 2014
PRCR-1065: Failed to stop resource ora.asm
Error PRCR-1065 and CRS-2529 can be returned while
stopping the ASM using srvctl command on Grid Infrastructure 11.2 and above as
can be seen in the following.
[grid@salman1 ~]$ srvctl stop asm PRCR-1065 : Failed to stop resource ora.asm |
Monday, December 29, 2014
Oracle Database 12c Patch/Upgrade from 12.1.0.1 to 12.1.0.2
For manual upgrade guide from 11g to 12c, click here. Same guide can also be followed to manually upgrade from 12.1.0.1 to 12.1.0.2.
Before going through this upgrade guide, you may be interested to view the guide to patch/upgrade standalone Grid Infrastructure from 12.1.0.1 to 12.1.0.2.
Before going through this upgrade guide, you may be interested to view the guide to patch/upgrade standalone Grid Infrastructure from 12.1.0.1 to 12.1.0.2.
Sunday, December 21, 2014
ORA-38500 While Enabling Real-Time Redo Apply
If you are trying to enable real time
redo apply whereby LGWR process of primary database writes directly to the
standby redo log file of the standby database, you might face ORA-38500 error
message. Following is an example of this error message.
SQL> ALTER DATABASE RECOVER MANAGED STAND |
Thursday, December 18, 2014
Grid Infrastructure 12c Patch/Upgrade from 12.1.0.1 to 12.1.0.2
In this post, I will be demonstrating the steps to upgrade/patch the Grid Infrastructure (GI) 12.1.0.1 to 12.1.0.2. Since ASM runs from GI home, ASM would be upgraded while upgrade of GI home. As we know that Oracle now provides full installation binaries for patchset releases so the binaries are required to be downloaded from MOS. You would need to download Patch
Wednesday, December 10, 2014
Error: "Message 279 not found" while starting Listener
One of my customers has Oracle 11.2.0.4 on windows
2008 R2 (x64). After reboot of this database server, listener did not come up
automatically and even manually starting the listener was returning following
error at the command prompt.
Subscribe to:
Posts (Atom)
Popular Posts - All Times
-
This error means that you are trying to perform some operation in the database which requires encryption wallet to be open, but wallet is ...
-
Finding space usage of tablespaces and database is what many DBAs want to find. In this article I will explain how to find out space usage ...
-
ORA-01653: unable to extend table <SCHEMA_NAME>.<SEGMENT_NAME> by 8192 in tablespace <TABLESPACE_NAME> This error is q...
-
You may also want to see this article about the ORA-12899 which is returned if a value larger than column’s width is inserted in the col...
-
This document explains how to start and stop an Oracle cluster. To start and stop Grid Infrastructure services for a standalone installatio...
-
If database server CPU usage is showing 100%, or high 90%, DBA needs to find out which session is hogging the CPU(s) and take appropriate ...
-
If you want to know how we upgrade an 11g database to 12c using DBUA, click here . For upgrading 12.1.0.1 to 12.1.0.2 using DBUA, ...
-
By default AWR snapshot interval is set to 60 minutes and retention of snapshots is set to 8 days. For better and precise investigation of...
-
SWAP space recommendation from Oracle corp. for Oracle 11g Release 2 If RAM is between 1 GB and 2 GB, SAWP should be 1.5 times the s...
-
This article explains how to install a 2 nodes Oracle 12cR1 Real Application Cluster (RAC) on Oracle Linux 7. I did this installation on O...