12c: Using DBFS

Oracle 12c introduces HTTP/HTTPS, FTP and WebDAV access to DBFS via the "/dbfs" virtual directory in the XML DB repository.

12c: Plugging unplugging Database

1- Unplugging the PDB

To unplug a PDB, you first close it and then generate an XML manifest file. The XML file contains information about the names and the full paths of the tablespaces, as well as data files of the unplugged PDB. The information will be used by the plugging operation.

12c: Working with Oracle Multitenant

Working with Oracle Multitenant
Environment: Oracle Database 12c (12.1.0) Installed on Windows 7

Creating a CDB creates a service whose name is the CDB name. As a side effect of creating a PDB in the CDB, a service is created inside it with a property that identifies it as the initial current container. The service is also started as a side effect of creating the PDB. The service has the same name as the PDB. Although its metadata is recorded inside the PDB, the invariant is maintained so that a service name is unique within the entire CDB.

12c: Configure EM Database Express HTTP port

In case you want to change default port of 12c EM Database Express, you need to configure the port using the dynamic protocol registration method. After the HTTP port is configured, you use it to access Enterprise Manager Express.

1- C:\Users\inam.HOME>set oracle_home=D:\app\Inam\product\12.1.0\dbhome_1

2- Verify that the listener is started by executing the lsnrctl status command.

C:\Users\inam.HOME>lsnrctl status

LSNRCTL for 64-bit Windows: Version 12.1.0.1.0 - Production on 22-JUL-2013 09:54:41

Copyright (c) 1991, 2013, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for 64-bit Windows: Version 12.1.0.1.0 - Production
Start Date                18-JUL-2013 11:21:15
Uptime                    3 days 22 hr. 33 min. 27 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   D:\app\Inam\product\12.1.0\dbhome_1\network\admin\listener.ora
Listener Log File         D:\app\Inam\diag\tnslsnr\Inam-pc\listener\alert\log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521ipc)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=Inam-pc.HOME.domain)(PORT=1521)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=Inam-pc.HOME.domain)(PORT=5500))(Security=(my_wallet_directory=D:\APP
admin\or12c\xdb_wallet))(Presentation=HTTP)(Session=RAW))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
  Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "or12c.HOME.domain" has 1 instance(s).
  Instance "or12c", status READY, has 1 handler(s) for this service...
Service "or12cXDB.HOME.domain" has 1 instance(s).
  Instance "or12c", status READY, has 1 handler(s) for this service...
Service "pdbor12c.HOME.domain" has 1 instance(s).
  Instance "or12c", status READY, has 1 handler(s) for this service...
The command completed successfully
3- Log in to SQL*Plus as the SYSDBA user and verify that the DISPATCHERS parameter in the initialization parameter file includes the PROTOCOL=TCP attribute.
C:\Users\inam.HOME>set oracle_sid=or12c
C:\Users\inam.HOME>sqlplus / as sysdba

SQL*Plus: Release 12.1.0.1.0 Production on Mon Jul 22 09:55:31 2013
Copyright (c) 1982, 2013, Oracle.  All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL> show parameters dispatcher

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
dispatchers                          string      (PROTOCOL=TCP) (SERVICE=or12cX
                                                 DB)
max_dispatchers                      integer

4-  Execute the DBMS_XDB.setHTTPPort procedure to set the HTTP port for Enterprise Manager Express.

SQL> EXEC DBMS_XDB.setHTTPPort(8081);

PL/SQL procedure successfully completed.

5- D:\app\Inam\product\12.1.0\dbhome_1\BIN>lsnrctl status

LSNRCTL for 64-bit Windows: Version 12.1.0.1.0 - Production on 22-JUL-2013 10:32:24

Copyright (c) 1991, 2013, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for 64-bit Windows: Version 12.1.0.1.0 - Production
Start Date                22-JUL-2013 10:28:01
Uptime                    0 days 0 hr. 4 min. 26 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   D:\app\Inam\product\12.1.0\dbhome_1\network\admin\listener.ora
Listener Log File         D:\app\Inam\diag\tnslsnr\Inam-pc\listener\alert\log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521ipc)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=Inam-pc.HOME.domain)(PORT=1521)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=Inam-pc.HOME.domain)(PORT=8081))(Presentation=HTTP)(Session=RAW))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
  Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "or12c.HOME.domain" has 1 instance(s).
  Instance "or12c", status READY, has 1 handler(s) for this service...
Service "or12cXDB.HOME.domain" has 1 instance(s).
  Instance "or12c", status READY, has 1 handler(s) for this service...
Service "pdbor12c.HOME.domain" has 1 instance(s).
  Instance "or12c", status READY, has 1 handler(s) for this service...
The command completed successfully

5- In your Web browser enter the URL to access Enterprise Manager: http://inam-pc.HOME.domain:8081/em

Installing 12c RAC on Linux

Pre-Req
Familiarity with Oracle Virtual Machine
Understaning with Oracle RAC eg; 11gRAC. You can have the understanding by below posts.
Installing Oracle 11g RAC on Windows 2008
Installing 11gR2 RAC on Linux
Installing 11gR2 RAC on Solaris

ORA-15177: cannot operate on system aliases (DBD ERROR: OCIStmtExecute)

Environment: 11gR2 (11.2.0.3) , Windows 2008R2

Using ASMCDM , dropping a folder/directory gives below error. 
ASMCMD> rm moherac
ORA-15032: not all alterations performed
ORA-15177: cannot operate on system aliases (DBD ERROR: OCIStmtExecute)

INS-20802 Grid Infrastructure Configuration Failed - 11gR2 on Windows

Yesterday while installing Oracle RAC 11gR2 (11.2.0.3) on one of the client side got the below error.

INS-20802 Grid Infrastructure Configuration Failed

Although all the cluvfy verification passed successful already, above error occurred after the 84% of installation on the step of Grid Infrastructure Configuration. Before this error remote operations went smooth and all GI folders copied on the remote host successfuly. I did not cancel the installation and decided to investigate first to know the cause.

ORA-00214: control file version inconsistent with file version

SQL> startup
ORACLE instance started.

Total System Global Area 1068937216 bytes
Fixed Size                  2262048 bytes
Variable Size             624954336 bytes
Database Buffers          436207616 bytes
Redo Buffers                5513216 bytes
ORA-00214: control file '+DGDUP/control01.ctl' version 1960 inconsistent with file '+DGDUP/control02.ctl' version 1956

ORA-01624: log %s needed for crash recovery of instance %s (thread %s)

SQL> alter database drop logfile group 3;
alter database drop logfile group 3
*
ERROR at line 1:
ORA-01624: log 3 needed for crash recovery of instance migdb (thread 1)
ORA-00312: online log 3 thread 1: 'D:\APP\INAM\ORADATA\MIGDB\REDO03.LOG'

Migrating non-ASM database to ASM - 11gR2

Requirement: Migrate a database from Non-ASM to ASM.
Environment: Oracle 11gR2 (11.2.0.3) , non-ASM Database: migdb (in Archivelog mode), Diskgroup on ASM: +DGDUP

Change RAC database Name using NID

Scenario: A RAC database "HOMEDB" name is needed to be changed to "HOMEATT"
Environment: 2 node Oracle RAC 11gR2 11.2.0.3 (Windows 2008R2)

Restore RMAN RAC database backup to other RAC enviornment

Scenerio:
We have a disk backup of a 2 nodes RAC database (homedb) and want to restore it to other RAC environment 2 nodes.
Environment:
Source: Oracle RAC 11gR2 11.2.0.3 (Windows 2008R2) , Diskgroups:  +HOMEDBDATA & +HOMEDBFLASH, Instances: homedb1,homedb2

Destination:  Oracle RAC 11gR2 11.2.0.3 (Windows 2008R2) only software installed. No database existing. Diskgroups: +DBDATA & +DBFLASH

FRM-40733 PL/SQL built in DBMS_error_code failed

On client side developer faced the below issue (11gR2 database) and requested for the investigations.

I got the below after research

ORA-02114 - Undocumented error

One of the developer on client side got the error, ORA-02114.

after research I found below.

Snapshot Standby Database - 11gR2

Prerequsite:
Configuring Oracle 11gR2 Data Guard - Physical Standby (without DG Broker) 

Brief:

Snapshot Standby is a new feature introduced in 11g that allows the standby database to be opened in read-write mode for real time testing. When switched back into standby mode, all changes made whilst in read-write mode are lost. This is achieved using flashback database, but the standby database does not need to have flashback database explicitly enabled to take advantage of this feature. Using the Flashback Database technology restore point is guaranteed to which the database can be later flashed back to.

Setting up active dataguard - Oracle 11g

Prerequsite:

Configuring Oracle 11gR2 Data Guard - Physical Standby (without DG Broker)

Once a standby database is configured, it can be opened in read-only mode to allow query access. This is often used to offload reporting to the standby server, thereby freeing up resources on the primary server. When open in read-only mode, archive log shipping continues, but managed recovery is stopped, so the standby database becomes increasingly out of date until managed recovery is resumed.

Converting a Failed Primary Into a Standby Database Using Flashback Database

Brief: After a failover occurs, the original primary database can no longer participate in the Data Guard configuration until it is repaired and established as a standby database in the new configuration. To do this, you can use the Flashback Database feature to recover the failed primary database to a point in time before the failover occurred, and then convert it into a physical or logical standby database in the new configuration.

Configuring Oracle 11gR2 Data Guard - Physical Standby

Brief: Data Guard is an Oracle feature that primarily provides database redundancy. This is done by having a standby (physical copy) database, preferably in another location and on separate disk. This standby database is maintained by applying the changes from the primary database to it. Standby databases can be maintained with either Redo (Physical standby) or SQL (Logical standby).

Restrict development tools on Production

Environment: Oracle 11gR2 Database on Windows 2008R2
Purpose: Implementing business rules to restrict development tools on production. Developers may work on production through these development tools  on-demand.

Keep history of Oracle Source code in DB

You can build a history of PL/SQL code changes by setting up an AFTER CREATE schema (or database) level trigger. This will allow you to easily revert to previous code if required.