Skip to main content

How to Install and Create Oracle 18c Database in Silent Mode Using ASM


<<Back to DB Administration Main Page

Step by Step How to Install and Create Oracle 18c Database in Silent Mode Using ASM

Installing oracle database is a lengthy process and therefore I have divided this post in 3 sections 
Section 1: Installing and Configuring GI for Standalone Server.
Step by Step instruction has been provided in post Step By Step How to Install Oracle 18c Grid Infrastructure for a Standalone Server in Silent Mode
Section 2: Installing Oracle 18c Database software in silent mode.
Section 3: Creating Oracle Database in silent mode
Once you have completed the section 1 you are ready to proceed with section 2 below.
Section 2: Installing Oracle 18c Database software in silent mode.
  • Download the software
Download the oracle database software for your OS from here
  • Transfer the oracle database binary to the server
Transfer the binary on the server where you want to install the database using winscp
  • Unzip the binaries

As oracle user unzip the software binary.
Note: Ensure to unzip the binary directly in the oracle home where you want to install the oracle software
$ unzip LINUX.X64_180000_db_home.zip -d /u01/dbatst1/18c/dbp1
  • Create OS Groups and Users
login as root user, create required OS groups and users
#groupadd oinstall
#groupadd tst1dba
#groupadd dba
#useradd -g oinstall -G dba,tst1dba dbatst1
  • Create the required directories and change the ownership and permission
login as root user, Create required directories and change ownership and permission of the directory to the oracle installation user
#mkdir -p /u01/dbatst1/18c/dbp1
#chown -R dbatst1:oinstall /u01/dbatst1
#chmod -R 775 /u01/dbatst1
  • Prepare the Response file
The template of response file is present in software. Navigate to the directory where you have unzipped the binaries and locate db_install.rsp. Backup the template before you modify it
$cp /u01/dbatst1/stage/install/response/db_install.rsp  /u01/dbatst1/stage/install/response/db_install.rsp.orig
Modify the following in db_install.rsp file (adopt the value according to your environment)
oracle.install.option=INSTALL_DB_SWONLY
UNIX_GROUP_NAME=oinstall
INVENTORY_LOCATION=/u01/oraInventory
ORACLE_BASE=/u01/dbatst1
oracle.install.db.InstallEdition=EE
oracle.install.db.OSDBA_GROUP=tst1dba
oracle.install.db.OSOPER_GROUP=tst1dba
oracle.install.db.OSBACKUPDBA_GROUP=tst1dba
oracle.install.db.OSDGDBA_GROUP=tst1dba
oracle.install.db.OSKMDBA_GROUP=tst1dba
oracle.install.db.OSRACDBA_GROUP=tst1dba
Note: Starting from 18c It is not required to specify ORACLE_HOME in the response file for Database installation, because the its installed in the same directory where you extract the binary

  • Perform Installation PreReqCheck
$/u01/dbatst1/18c/dbp1/runInstaller -silent -executePrereqs -responseFile /u01/dbatst1/18c/dbp1/install/response/db_install.rsp
Note:- Ensure to fix Error/Warning before you proceed ahead. I recommend you, not to use ignorePrereqFailure if you don't know the consequence. I am ignoring some warnings because I don't have enough memory in my server
NOTE: If you have role separation  (which I have in my case)  and you have installed oracle grid infrastructure/ASM as diffract OS Group and User than oracle software user then GI owner (in this example oragrid) must be the member of the primary group of oracle software owner (dbatst1)
# usermod -a -G tst1dba oragrid
  • Execute silent DB Software installation

$ /u01/dbatst1/18c/dbp1/runInstaller -silent -ignorePrereqFailure -responseFile /u01/dbatst1/18c/dbp1/install/response/db_install.rsp
Launching Oracle Database Setup Wizard...
[WARNING] [INS-13014] Target environment does not meet some optional requirements.
   CAUSE: Some of the optional prerequisites are not met. See logs for details. /u01/orainventory/logs/InstallActions2019-02-15_03-31-29PM/installActions2019-02-15_03-31-29PM.log
   ACTION: Identify the list of failed prerequisite checks from the log: /u01/orainventory/logs/InstallActions2019-02-15_03-31-29PM/installActions2019-02-15_03-31-29PM.log. Then either from the log file or from installation manual find the appropriate configuration to meet the prerequisites and fix it manually.
The response file for this session can be found at:
 /u01/dbatst1/18c/dbp1/install/response/db_2019-02-15_03-31-29PM.rsp
You can find the log of this install session at:
 /u01/orainventory/logs/InstallActions2019-02-15_03-31-29PM/installActions2019-02-15_03-31-29PM.log
As a root user, execute the following script(s):
        1. /u01/dbatst1/18c/dbp1/root.sh
Execute /u01/dbatst1/18c/dbp1/root.sh on the following nodes:
[test1]


Successfully Setup Software with warning(s).
  • Execute root.sh
login as root user and run root.sh
# /u01/dbatst1/18c/dbp1/root.sh
Check /u01/dbatst1/18c/dbp1/install/root_test16_2019-02-15_15-41-42-327743926.log for the output of root script

Section 3: Creating Oracle Database in silent mode
  • Prepare the Response file for DBCA
Backup the original response file before modifying it
$cp /u01/dbatst1/18c/dbp1/assistants/dbca/dbca.rsp  /u01/dbatst1/18c/dbp1/assistants/dbca/dbca.rsp_orig
Modify the following parameters only and keep everything else untouched.
gdbName=TST1T
sid=TST1T
databaseConfigType=SI
createAsContainerDatabase=true
templateName=/u01/dbatst1/18c/dbp1/assistants/dbca/templates/TPL_DB_18C.dbt
sysPassword=*******
systemPassword= **********
automaticMemoryManagement=false
NOTE: The content of the response file "/u01/dbatst1/18c/dbp1/assistants/dbca/templates/TPL_DB_18C.dbt" used in this example is provided below
  • Run DBCA in Silent Mode to Create the Database
$ dbca -silent -createDatabase -responseFile /u01/dbatst1/18c/dbp1/assistants/dbca/dbca.rsp
Prepare for db operation
4% complete
Registering database with Oracle Restart
5% complete
Creating and starting Oracle instance
6% complete
7% complete
9% complete
Creating database files
12% complete
Creating data dictionary views
13% complete
16% complete
18% complete
19% complete
20% complete
21% complete
23% complete
Oracle JVM
28% complete
33% complete
39% complete
40% complete
Oracle Text
41% complete
42% complete
44% complete
Oracle Multimedia
54% complete
Oracle OLAP
58% complete
Oracle Spatial
59% complete
65% complete
Oracle Label Security
72% complete
Oracle Database Vault
79% complete
Creating cluster database views
80% complete
86% complete
Completing Database Creation
88% complete
89% complete
Executing Post Configuration Actions
100% complete
Database creation complete. For details check the logfiles at:
 /u01/dbatst1/cfgtoollogs/dbca/TST1T.
Database Information:
Global Database Name:TST1T
System Identifier(SID):TST1T
Look at the log file "/u01/dbatst1/cfgtoollogs/dbca/TST1T/TST1T.log" for further details.

============================================================
Template File "TPL_DB_18C.dbt" Content
============================================================
<?xml version = '1.0'?>
<DatabaseTemplate name="TPL_DB_18C.dbt" description="SI on ASM " version="18C">
   <CommonAttributes>
      <option name="OMS" value="true"/>
      <option name="JSERVER" value="true"/>
      <option name="SPATIAL" value="true"/>
      <option name="IMEDIA" value="true"/>
      <option name="ORACLE_TEXT" value="true">
         <tablespace id="SYSAUX"/>
      </option>
      <option name="SAMPLE_SCHEMA" value="false"/>
      <option name="CWMLITE" value="true">
         <tablespace id="SYSAUX"/>
      </option>
      <option name="APEX" value="false"/>
      <option name="DV" value="true"/>
   </CommonAttributes>
   <Variables/>
   <CustomScripts Execute="false"/>
   <InitParamAttributes>
      <InitParams>
         <initParam name="audit_file_dest" value="/u01/dbatest1/admin/TESTA/adump"/>
         <initParam name="compatible" value="18.0.0"/>
         <initParam name="remote_login_passwordfile" value="EXCLUSIVE"/>
         <initParam name="undo_tablespace" value="UNDOTBS1"/>
         <initParam name="diagnostic_dest" value="/u01/dbatest1"/>
         <initParam name="db_block_size" value="8" unit="KB"/>
         <initParam name="open_cursors" value="1000"/>
                         <initParam name="log_archive_dest_1" value="'LOCATION=+DATA'"/>
         <initParam name="log_archive_format" value="TESTA_%T_%R_%S.arc"/>
         <initParam name="archive_lag_target" value="1800" />
         <initParam name="backup_tape_io_slaves" value="TRUE" />
         <initParam name="control_file_record_keep_time" value="31"/>
         <initParam name="db_create_file_dest" value="+DATA"/>
         <initParam name="db_name" value="TEST"/>
         <initParam name="db_domain" value="test"/>
         <initParam name="thread" value="0"/>
         <initParam name="memory_max_target" value="2048" unit="MB" />
         <initParam name="memory_target" value="1280" unit="MB" />
         <initParam name="java_pool_size" value="300" unit="MB"/>
         <initParam name="db_create_online_log_dest_2" value="+DATA"/>
         <initParam name="recyclebin" value="off" />
         <initParam name="db_create_online_log_dest_1" value="+DATA"/>
         <initParam name="db_block_checking" value="MEDIUM"/>
         <initParam name="processes" value="1000"/>
         <initParam name="db_block_checksum" value="FULL"/>
         <initParam name="db_recovery_file_dest" value="+DATA"/>
         <initParam name="audit_trail" value="DB"/>
         <initParam name="db_recovery_file_dest_size" value="20" unit="GB"/>
      </InitParams>
      <MiscParams>
         <databaseType>MULTIPURPOSE</databaseType>
         <maxUserConn>20</maxUserConn>
         <percentageMemTOSGA>40</percentageMemTOSGA>
         <customSGA>false</customSGA>
         <dataVaultEnabled>false</dataVaultEnabled>
         <archiveLogMode>true</archiveLogMode>
         <initParamFileName>/u01/dbatest1/admin/TESTA/pfile/init.ora</initParamFileName>
         <characterSet>AL32UTF8</characterSet>
         <nationalCharacterSet>AL16UTF16</nationalCharacterSet>
      </MiscParams>
      <SPfile useSPFile="true">/u01/dbatest1/18c/dbp1/dbs/spfileTEST.ora</SPfile>
   </InitParamAttributes>
   <StorageAttributes>
         <ControlfileAttributes id="Controlfile">
         <maxDatafiles>1024</maxDatafiles>
         <maxLogfiles>192</maxLogfiles>
         <maxLogMembers>3</maxLogMembers>
         <maxLogHistory>1</maxLogHistory>
         <maxInstances>32</maxInstances>
         <image name="&lt;OMF_CONTROL_0>" filepath="+DATA"/>
         <image name="&lt;OMF_CONTROL_1>" filepath="+DATA"/>
         <image name="&lt;OMF_CONTROL_2>" filepath="+DATA"/>
      </ControlfileAttributes>
      <DatafileAttributes id="&lt;OMF_SYSAUX_DATAFILE_0>">
         <tablespace>SYSAUX</tablespace>
         <temporary>false</temporary>
         <online>true</online>
         <status>0</status>
         <size unit="MB">120</size>
         <reuse>false</reuse>
         <autoExtend>true</autoExtend>
         <increment unit="KB">10240</increment>
         <maxSize unit="MB">-1</maxSize>
      </DatafileAttributes>
      <DatafileAttributes id="&lt;OMF_SYSTEM_DATAFILE_0>">
         <tablespace>SYSTEM</tablespace>
         <temporary>false</temporary>
         <online>true</online>
         <status>0</status>
         <size unit="MB">300</size>
         <reuse>false</reuse>
         <autoExtend>true</autoExtend>
         <increment unit="KB">10240</increment>
         <maxSize unit="MB">-1</maxSize>
      </DatafileAttributes>
      <DatafileAttributes id="&lt;OMF_TEMP_DATAFILE_0>">
         <tablespace>TEMP</tablespace>
         <temporary>false</temporary>
         <online>true</online>
         <status>0</status>
         <size unit="MB">20</size>
         <reuse>false</reuse>
         <autoExtend>true</autoExtend>
         <increment unit="KB">640</increment>
         <maxSize unit="MB">-1</maxSize>
      </DatafileAttributes>
      <DatafileAttributes id="&lt;OMF_UNDOTBS1_DATAFILE_0>">
         <tablespace>UNDOTBS1</tablespace>
         <temporary>false</temporary>
         <online>true</online>
         <status>0</status>
         <size unit="MB">200</size>
         <reuse>false</reuse>
         <autoExtend>true</autoExtend>
         <increment unit="KB">5120</increment>
         <maxSize unit="MB">-1</maxSize>
      </DatafileAttributes>
      <DatafileAttributes id="&lt;OMF_USERS_DATAFILE_0>">
         <tablespace>USERS</tablespace>
         <temporary>false</temporary>
         <online>true</online>
         <status>0</status>
         <size unit="MB">5</size>
         <reuse>false</reuse>
         <autoExtend>true</autoExtend>
         <increment unit="KB">1280</increment>
         <maxSize unit="MB">-1</maxSize>
      </DatafileAttributes>
      <TablespaceAttributes id="SYSAUX">
         <online>true</online>
         <offlineMode>1</offlineMode>
         <readOnly>false</readOnly>
         <temporary>false</temporary>
         <defaultTemp>false</defaultTemp>
         <undo>false</undo>
         <local>true</local>
         <blockSize>-1</blockSize>
         <allocation>1</allocation>
         <uniAllocSize unit="KB">-1</uniAllocSize>
         <initSize unit="KB">64</initSize>
         <increment unit="KB">64</increment>
         <incrementPercent>50</incrementPercent>
         <minExtends>1</minExtends>
         <maxExtends>4096</maxExtends>
         <minExtendsSize unit="KB">64</minExtendsSize>
         <logging>true</logging>
         <recoverable>false</recoverable>
         <maxFreeSpace>0</maxFreeSpace>
         <autoSegmentMgmt>true</autoSegmentMgmt>
         <bigfile>false</bigfile>
         <datafilesList>
            <TablespaceDatafileAttributes id="&lt;OMF_SYSAUX_DATAFILE_0>">
               <id>-1</id>
            </TablespaceDatafileAttributes>
         </datafilesList>
      </TablespaceAttributes>
      <TablespaceAttributes id="SYSTEM">
         <online>true</online>
         <offlineMode>1</offlineMode>
         <readOnly>false</readOnly>
         <temporary>false</temporary>
         <defaultTemp>false</defaultTemp>
         <undo>false</undo>
         <local>true</local>
         <blockSize>-1</blockSize>
         <allocation>3</allocation>
         <uniAllocSize unit="KB">-1</uniAllocSize>
         <initSize unit="KB">64</initSize>
         <increment unit="KB">64</increment>
         <incrementPercent>50</incrementPercent>
         <minExtends>1</minExtends>
         <maxExtends>-1</maxExtends>
         <minExtendsSize unit="KB">64</minExtendsSize>
         <logging>true</logging>
         <recoverable>false</recoverable>
         <maxFreeSpace>0</maxFreeSpace>
         <autoSegmentMgmt>true</autoSegmentMgmt>
         <bigfile>false</bigfile>
         <datafilesList>
            <TablespaceDatafileAttributes id="&lt;OMF_SYSTEM_DATAFILE_0>">
               <id>-1</id>
            </TablespaceDatafileAttributes>
         </datafilesList>
      </TablespaceAttributes>
      <TablespaceAttributes id="TEMP">
         <online>true</online>
         <offlineMode>1</offlineMode>
         <readOnly>false</readOnly>
         <temporary>true</temporary>
         <defaultTemp>true</defaultTemp>
         <undo>false</undo>
         <local>true</local>
         <blockSize>-1</blockSize>
         <allocation>1</allocation>
         <uniAllocSize unit="KB">-1</uniAllocSize>
         <initSize unit="KB">64</initSize>
         <increment unit="KB">64</increment>
         <incrementPercent>0</incrementPercent>
         <minExtends>1</minExtends>
         <maxExtends>0</maxExtends>
         <minExtendsSize unit="KB">64</minExtendsSize>
         <logging>true</logging>
         <recoverable>false</recoverable>
         <maxFreeSpace>0</maxFreeSpace>
         <autoSegmentMgmt>true</autoSegmentMgmt>
         <bigfile>false</bigfile>
         <datafilesList>
            <TablespaceDatafileAttributes id="&lt;OMF_TEMP_DATAFILE_0>">
               <id>-1</id>
            </TablespaceDatafileAttributes>
         </datafilesList>
      </TablespaceAttributes>
      <TablespaceAttributes id="UNDOTBS1">
         <online>true</online>
         <offlineMode>1</offlineMode>
         <readOnly>false</readOnly>
         <temporary>false</temporary>
         <defaultTemp>false</defaultTemp>
         <undo>true</undo>
         <local>true</local>
         <blockSize>-1</blockSize>
         <allocation>1</allocation>
         <uniAllocSize unit="KB">-1</uniAllocSize>
         <initSize unit="KB">512</initSize>
         <increment unit="KB">512</increment>
         <incrementPercent>50</incrementPercent>
         <minExtends>8</minExtends>
         <maxExtends>4096</maxExtends>
         <minExtendsSize unit="KB">512</minExtendsSize>
         <logging>true</logging>
         <recoverable>false</recoverable>
         <maxFreeSpace>0</maxFreeSpace>
         <autoSegmentMgmt>true</autoSegmentMgmt>
         <bigfile>false</bigfile>
         <datafilesList>
            <TablespaceDatafileAttributes id="&lt;OMF_UNDOTBS1_DATAFILE_0>">
               <id>-1</id>
            </TablespaceDatafileAttributes>
         </datafilesList>
      </TablespaceAttributes>
      <TablespaceAttributes id="USERS">
         <online>true</online>
         <offlineMode>1</offlineMode>
         <readOnly>false</readOnly>
         <temporary>false</temporary>
         <defaultTemp>false</defaultTemp>
         <undo>false</undo>
         <local>true</local>
         <blockSize>-1</blockSize>
         <allocation>1</allocation>
         <uniAllocSize unit="KB">-1</uniAllocSize>
         <initSize unit="KB">128</initSize>
         <increment unit="KB">128</increment>
         <incrementPercent>0</incrementPercent>
         <minExtends>1</minExtends>
         <maxExtends>4096</maxExtends>
         <minExtendsSize unit="KB">128</minExtendsSize>
         <logging>true</logging>
         <recoverable>false</recoverable>
         <maxFreeSpace>0</maxFreeSpace>
         <autoSegmentMgmt>true</autoSegmentMgmt>
         <bigfile>false</bigfile>
         <datafilesList>
            <TablespaceDatafileAttributes id="&lt;OMF_USERS_DATAFILE_0>">
               <id>-1</id>
            </TablespaceDatafileAttributes>
         </datafilesList>
      </TablespaceAttributes>
      <RedoLogGroupAttributes id="1">
         <reuse>false</reuse>
         <fileSize unit="MB">2048</fileSize>
         <Thread>1</Thread>
         <member ordinal="0" memberName="OMF_1_REDOLOG_MEMBER_0" filepath="+DATA"/>
         <member ordinal="11" memberName="OMF_1_REDOLOG_MEMBER_1" filepath="+DATA"/>
      </RedoLogGroupAttributes>
      <RedoLogGroupAttributes id="2">
         <reuse>false</reuse>
         <fileSize unit="MB">2048</fileSize>
         <Thread>1</Thread>
         <member ordinal="0" memberName="OMF_2_REDOLOG_MEMBER_0" filepath="+DATA"/>
         <member ordinal="6" memberName="OMF_2_REDOLOG_MEMBER_1" filepath="+DATA"/>
      </RedoLogGroupAttributes>
      <RedoLogGroupAttributes id="3">
         <reuse>false</reuse>
         <fileSize unit="MB">2048</fileSize>
         <Thread>1</Thread>
         <member ordinal="0" memberName="OMF_3_REDOLOG_MEMBER_0" filepath="+DATA"/>
         <member ordinal="6" memberName="OMF_3_REDOLOG_MEMBER_1" filepath="+DATA"/>
      </RedoLogGroupAttributes>
   </StorageAttributes>
</DatabaseTemplate>





Comments

Post a Comment

Popular posts from this blog

How to Power On/off Oracle Exadata Machine

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using  button on front of the server The power on sequence is as follows. 1. Start Rack, including switches  Note:- Ensure the switches have had power applied for a few minutes to complete power on  configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers  Note:- Ensure all Exadata Storage Servers complete the boot process before starting the   database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the serve...
Post a Comment
Read more

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco...
7 comments
Read more

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1     node1-vip node2     node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:
1 comment
Read more

ORA-46630: keystore cannot be created at the specified location

<<Back to DB Administration Main Page ORA-46630: keystore cannot be created at the specified location CDB011> ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "xxxxxxx"; ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "EncTest123" * ERROR at line 1: ORA-46630: keystore cannot be created at the specified location Cause  Creating a keystore at a location where there is already a keystore exists Solution To solve the problem, use a different location to create a keystore (use ENCRYPTION_WALLET_LOCATION in sqlnet.ora file to specify the keystore location), or move this ewallet.p12 file to some other location. Note: Oracle does not recommend deleting keystore file (ewallet.p12) that belongs to a database. If you have multiple keystores, you can choose to merge them rather than deleting either of them.
Post a Comment
Read more

ORA-65104: operation not allowed on an inactive pluggable database alter pluggable database open

<<Back to DB Administration Main Page ORA-65104: operation not allowed on an inactive pluggable database SQL> alter pluggable database TEST_CLON open; alter pluggable database TEST_CLON open * ERROR at line 1: ORA-65104: operation not allowed on an inactive pluggable database Cause The pluggable database status was UNUSABLE. It was still being created or there was an error during the create operation. A PDB can only be opened if it is successfully created and its status is marked as NEW in cdb_pdbs.status column SQL> select PDB_NAME,STATUS from cdb_pdbs; PDB_NAME             STATUS -------------------- --------------------------- PDB$SEED             NORMAL TEST_CLON            UNUSABLE Solution:  Drop the PDB and create it again. Related Posts How to Clone Oracle PDB (Pluggable Database) with in the Same Container
Post a Comment
Read more

ORA-16905: The member was not enabled yet

<<Back to Oracle DataGuard Main Page ORA-16905 Physical Standby Database is disabled DGMGRL> show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database (disabled)       ORA-16905: The member was not enabled yet. Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 58 seconds ago) DGMGRL> DGMGRL> enable database 'ORCL1PS'; Enabled. DGMGRL>  show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 38 seconds ago)
Post a Comment
Read more

How to Switch Log File from All Instances in RAC

<<Back to Oracle RAC Main Page Switch The Log File of All Instances in Oracle RAC. In many cases you need to switch the logfile of the database. You can switch logfile using alter system switch logfile command but if you want to switch the logfile from all the instances you need to execute the command on all the instances individually and therefore you must login on all the instances. You can avoid this and switch logfile of all instances by just running the below command from any of the instance in RAC database SQL> ALTER SYSTEM SWITCH ALL LOGFILE;   System altered.
Post a Comment
Read more

Starting RMAN and connecting to Database

  <<Back to Oracle Backup & Recovery Main Page Starting RMAN and connecting to Database Starting RMAN and connecting to Database To start RMAN you need to set the environment and type rman and press enter. You can connect to database either using connect command or using command line option. using command line option localhost:$ export ORACLE_HOME=/ora_app/product/18c/dbd2 localhost:$ export PATH=$ORACLE_HOME/bin:$PATH localhost:$ export ORACLE_SID=ORCL1P localhost:$ rman target / Recovery Manager: Release 18.0.0.0.0 - Production on Sun Apr 4 08:11:01 2021 Version 18.11.0.0.0 Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved. connected to target database: ORCL1P (DBID=4215484517) RMAN> using connect option localhost:$ rman RMAN> connect target sys@ORCL1P  target database Password:******** connected to target database: ORCL1P (DBID=4215484517) NOTE: To use connect command you need to ensure that  you have proper TNS sentry...
Post a Comment
Read more

How to Attach to a Datapump Job and Check Status of Export or Import

<<Back to Oracle DATAPUMP Main Page How to check the progress of  export or import Jobs You can attach to the export/import  job using ATTACH parameter of oracle datapump utility. Once you are attached to the job you check its status by typing STATUS command. Let us see how Step1>  Find the Export/Import Job Name You can find the datapump job information from  DBA_DATAPUMP_JOBS or  USER_DATAPUMP_JOBS view. SQL> SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME                       OPERATION            JOB_MODE   STATE ---------- ------------------------------ -------------------- ---------- ---------- SYSTEM     SYS_EXPORT_FULL_02          ...
7 comments
Read more

ORA-46655: no valid keys in the file from which keys are to be imported

<<Back to DB Administration Main Page SQL> administer key management import encryption keys with secret "xxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxx" with backup; administer key management import encryption keys with secret "xxxxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxxxx" with backup * ERROR at line 1: ORA-46655: no valid keys in the file from which keys are to be imported Cause: Either the keys to be imported already present in the target database or correct container (PDB) is not set. Solution: In my case I got the error because I attempted to import the keys for newly plugged database PDB02 from CDB$ROOT container. To Solve the issue just switched to the correct container and re run the import. SQL> show con_name CON_NAME ------------------------------ CDB$ROOT <===Wrong Container selected  SQL> alter session set container=PDB02; Session alt...
Post a Comment
Read more