Oracle dbca | An unexpected error has been detected by HotSpot Virtual Machine

Environment Details:
OS: Linux 5.8
Database Version: 11.2.0.3.0
User: oracle
Issue: When the dbca is invoked for creating database, we get the below mentioned error and it is gets terminated.

54-oracle@linuxhost01=> dbca
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  SIGSEGV (0xb) at pc=0x0000003373279b60, pid=10441, tid=139987634067168
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_30-b03 mixed mode)
# Problematic frame:
# C  [libc.so.6+0x79b60]  strlen+0x10
#
# An error report file with more information is saved as hs_err_pid10441.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
Abort

Solution: Set the LD_BIND_NOW parameter to 1 and then invoke dbca, it will work fine

55-oracle@linuxhost01=> export LD_BIND_NOW=1

56-oracle@linuxhost01=> dbca

Oracle Error with Explain Plan | ORA-00904: "OTHER_TAG": invalid identifier

Environment Details:
OS: Linux 5.8
Database Version: 11.2.0.3.0
Issue: ERROR: an uncaught error in function display has happened; please contact Oracle support
Please provide also a DMP file of the used plan table PLAN_TABLE 

ORA-00904: "OTHER_TAG": invalid identifier

When we generate the explain plan and try to get the explain plan details from plan_table we get the above mentioned error.
The reason may be the plan table has been corrupted. We need to recreate the plan table using the script utlxplan.sql from $ORACLE_HOME/rdbms/admin and it will work fine.

ASM Diskgroup Not Compatible For Database Usage | Oracle RAC 11g

ASM Diskgroup Not Compatible For Database Usage

Environment Details:
OS: Linux 5.8
Database Version: 11.2.0.3.0
User: oracle

When we try to create a new database in a 11g RAC Environment, we are getting the error Diskgroup "+DATA_ " is not compatible for database usage. Database compatible attribute of diskgroup should be the same or lower than the database compatible initialization parameter value. Database compatible parameter is set to "11.2.0.0.0" and the diskgroup database compatibility attribute is set  to "11.2.0.2".

Check the value of the compatibility attribute from ASM instance by querying the V$ASM_DISKGROUP view.

SQL> SELECT INSTANCE_NAME FROM V$INSTANCE;

INSTANCE_NAME
----------------
+ASM1

SQL>SELECT GROUP_NUMBER, NAME, COMPATIBILITY, DATABASE_COMPATIBILITY FROM V$ASM_DISKGROUP;

GROUP_NUMBER NAME            COMPATIBIL DATABASE_C
------------ --------------- ---------- ----------
           1 DATA_LINUX1     11.2.0.3.0 11.2.0.2.0
           2 DBFS_DG         11.2.0.3.0 11.2.0.2.0
           3 RECO_LINUX1     11.2.0.3.0 11.2.0.2.0

To Resolve the same we need to go the location $ORACLE_HOME/assistants/dbca/templates and edit the template we were trying to use(In our case its General_Purpose.dbc)

Search for the word "compatible" in the file and than change the attribute from 11.2.0.0.0 to 11.2.0.3.0

<InitParamAttributes>
      <InitParams>
         <initParam name="db_name" value=""/>
         <initParam name="dispatchers" value="(PROTOCOL=TCP) (SERVICE={SID}XDB)"/>
         <initParam name="audit_file_dest" value="{ORACLE_BASE}/admin/{DB_UNIQUE_NAME}/adump"/>
         <initParam name="compatible" value="11.2.0.3.0"/>
 
Then run dbca to create the database.

Oracle 12c Pluggable Database Creation Method 2: from Non CDB to CDB

How to Create Oracle Pluggable database

Method 2: Create new PDB from by plugging non-CDB into CDB. We are using DBMS_PDB package in this post, which is applicable only to the databases created in 12C and higher versions.

Environment Details:

OS: Sun Solaris 5.10

Database Version: 12C

CDB Database Name: CDB12C

Root Database Name: CDB$ROOT
Source Database Name: ORCLDB

PDB Database Name: PDB2
User: oracle

1. Connect to the Non-CDB database and shut it down, then open it in READ ONLY Mode.

2. Execute the below procedure which will generate a xml file that will be used to create the new PDB Database.

EXEC DBMS_PDB.DESCRIBE ('/u01/app/oracle/pdb2.xml');

3. Connect to target CDB database with a user having "CREATE PLUGGABLE DATABASE" privilege.

4. Set the PDB_FILE_NAME_CONVERT parameter to the new location where the datafiles for the pdb database will be created. 

5. Use the function DBMS_PDB.CHECK_PLUG_COMPATIBILITY to check the compatibility and  query the pdb_lug_in_violations view to view the violations. If there is any major issues, proceed accordingly

BEGIN

  IF DBMS_PDB.CHECK_PLUG_COMPATIBILITY('/u01/app/oracle/pdb2.xml','pdb2') THEN
    dbms_output.put_line('TRUE');
  ELSE
    dbms_output.put_line('FALSE');
  END IF;
END;
/

SELECT MESSAGE, ACTION FROM PDB_PLUG_IN_VIOLATIONS;

6. Plug in the database orcldb as pluggable database pdb2, Once the database is created, it will be in MOUNTED Mode.

   CREATE PLUGGABLE DATABASE pdb2 USING '/u01/app/oracle/pdb2.xml';

7. Create a service using netca for the new database(pdb2) and connect to it as sys user using this service. Run the noncdb_to_pdb.sql script before opening the pdb database. This script will delete all the unnecessary metadata from the system tablespace of the newly created PDB database.

8. Finally OPEN the pluggable database.

  

Oracle 12c Pluggable Database Creation Method 1: using command line

How to Create Oracle Pluggable database

Method 1: Create new PDB from PDB$SEED pluggable database using command line.

Environment Details:

OS: Sun Solaris 5.10

Database Version: 12C

User: oracle

CDB Database Name: CDB1

Root Database Name: CDB$ROOT

Seed Database Name: PDB$SEED (Template database, always in READ ONLY Mode)

PDB Database Name: PDB1

1. Connect to the root database with the user having "CREATE PLUGGABLE DATABASE" system privilege. In this case we have used SYS user.

2. Issue the below to create the pluggable database in the container database.

CREATE PLUGGABLE DATABASE pdb1

ADMIN USER pdbadmin IDENTIFIED BY pdbadmin1 ROLES=(CONNECT)

FILE_NAME_CONVERT =  ('/u01/oradata/ora12c/pdbseed','/u01/oradata/ora12c/pdb1');

3. When the pluggable database is created it is in MOUNTED Mode, we need to OPEN the database to use it.

ALTER PLUGGABLE DATABASE pdb1 OPEN;