Create Oracle 11g Database using DBCA
This step by step guide will show you how to create an Oracle database using dbca. This document should be used after you have installed the Oracle database software using “Install Oracle 11gR2 database software” tutorial..This guide is part of the series titled “Installing Oracle Enterprise Manager Gird Control 11gR1. The series is a step by step tutorial of installing Oracle Enterprise Manager Grid Control 11gR1. The series is divided into the following tutorials
Install Oracle Enterprise Linux
Prepare Linux for Oracle 11gR2 installation.
Install Java SDK 6 update 18
Install Oracle 11gR2 database software
Create Oracle 11gR2 database
Configure Oracle Net for Oracle 11gR2 database
Install Oracle WebLogic Server 11gR1 (10.3.2)
Install Oracle Enterprise Manger 11g Grid Control
Hardware/Software:
DELL – Intel Core 2 Duo CPU
RAM: 2GB
Hard Disk: 147GB
OS: Oracle enterprise Linux 5.3.
Oracle validated rpms
Directory Structure:
ORACLE_BASE=/u01/app/oracle
ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1
ORACLE_SID=gdb
Pre-Requisites:
Before running through this tutorial make sure you have complete the following tasks:
1. Oracle Enterprise Linux 5.3 installed
2. Linux box prepared for Database installation. See here for details instructions
3. Java SDK 6 update 8 installed
4. Oracle Database 11g R2 software is installed.
Installation instructions and options:
| Step/Screen Name | Action |
| 1 | Open X-Windows session to the server as oracle user |
| 2 | #cd /u01/app/oracle |
| 3 | #dbca |
| The Database configuration assistant will now start. You will use the dbca to create a database. For this excercise we will create a database named “GDB” which will be used as a repository for Oracle Enterprise Manager Grid Control |
|
| Welcome | Click Next |
| Operations | Select “Create a Database”and click Next
|
Oracle Enterprise Manager 11g Grid Control
The Oracle Enterprise Manager 11g Grid Control is Oracle solution to manage Grid environment that allows businesses to heighten application performance and deliver unparalleled IT infrastructure reliability.
All kings of business, small, medium or large can attain measurable IT cost savings by extending the availability of computing resources, cultivating more productive and effective administrators, and achieving higher quality of service. This can all be achieved by installing Oracle Enterprise Manager 11g Grid control to manage your Oracle technology stack.
In previous versions of Oracle Enterprise Manager (before 10g), it was mostly used for Oracle database management But the latest versions introduced Oracle Enterprise Manager 11g Grid Control capabilities of managing your infrastructure by monitoring/managing
- oracle databases
- oracle database servers or hosts
- application management
- application performance monitoring
- process monitoring
- streams
- active dataguard
- database replication
- cost-effective and easy automated configuration management
- oracle provisioning
Oracle Enterprise Manager 11g Grid Control has three major components which are
- Oracle WebLogic Server
- Oracle Management Service (OMS)
- Repository Database
- Oracle Management Agent
Oracle Weblogic Server is Oracle’s replacement for Oracle Application Server which was used till Oracle Enterprise Manager 10g. but 11g introduced
Oracle Weblogic Server, a more robust and stable application server. The Main engine or software for OEM is the OMS. That is a Java application
that sits on Oracle Webologic Server. The OMS interacts with Oracle repository database, Agents on targets, and Oracle Weblogic Server and provides an efficient web browser based Grid Control environment.
Oracle Repository database is an Oracle database that stores all the configuration data and stats sent from the agents. This data is displayed on users
logic and Oracle Enterprise Manager through Grid Control.
Other functionalities that Oracle Enterprise Manager 11g Grid Control includes
- Run ADDM Report
- Run ASH Report
- Capability to chaneg system parameters
- Run SQL Advisor
- Run Segment Advisor
- Run MTTR advisor
- SQL Performance Analyzer
- Streams Performance Advisor
- SQL Advisors
- Memory Advisors
- Automatic Undo Management
- Maximum Availability Architecture (MAA) Advisor
- Segment Advisors
- Viewing, purging and archiving Alert logs
- Viewing, purging and archiving Trace files
- Blackouts
- Apply Patch
- Scheduler Central
- SQL Worksheet
- Export to Export Files
- Import from Export Files
- Import from Database
- Load Data from User Files
- Monitor Export and Import Jobs
Granting Access To Non-DBA Users to the Oracle Enterprise Manager 11g Grid Control Performance Tab
Normally users who do not have DBA roles can not access Oracle 11g Performance related information using OEM 11g Grid Control.
Normally only Oracle 11g DBAs are allowed to view these tabs and they use them to do performance tuning or to identify problematic SQL or session etc.
However there is a way to grant access to OEM 11g Grid Control performance tab to users who do not have DBA roles. In this case the user means the users in the target database. This is helpful when you as a Oracle 11g DBA wants to grant access to the performance tab to management users who would like to have access to these data.
This is done by assigning OEM_MONITOR role to those users.
Caution: Please not that OEM_MONITOR role comes with a number of powerful privileges. So really give a thought if you need to assign OEM_MONITOR to not so technical users.
A way to avoid that is to create another role and assign OEM_MONITOR role like privileges to that role.
Here is a list of the privileges that OEM_MONITOR role has in Oracle 11g database:
SQL> select ROLE, TABLE_NAME, PRIVILEGE from ROLE_TAB_PRIVS where ROLE=’OEM_MONITOR’ order by 3,2;
ROLE TABLE_NAME PRIVILEGE
—————————— —————————— —————————————-
OEM_MONITOR ALERT_QUE DEQUEUE
OEM_MONITOR BSLN EXECUTE
OEM_MONITOR BSLN_INTERNAL EXECUTE
OEM_MONITOR BSLN_METRIC_SET EXECUTE
OEM_MONITOR BSLN_METRIC_T EXECUTE
OEM_MONITOR BSLN_OBSERVATION_SET EXECUTE
OEM_MONITOR BSLN_OBSERVATION_T EXECUTE
OEM_MONITOR BSLN_STATISTICS_SET EXECUTE
OEM_MONITOR BSLN_STATISTICS_T EXECUTE
OEM_MONITOR BSLN_VARIANCE_SET EXECUTE
OEM_MONITOR BSLN_VARIANCE_T EXECUTE
OEM_MONITOR DBMS_AQ EXECUTE
OEM_MONITOR DBMS_AQADM EXECUTE
OEM_MONITOR DBMS_DRS EXECUTE
OEM_MONITOR DBMS_MONITOR EXECUTE
OEM_MONITOR DBMS_SERVER_ALERT EXECUTE
OEM_MONITOR DBMS_SYSTEM EXECUTE
OEM_MONITOR DBMS_WORKLOAD_REPOSITORY EXECUTE
OEM_MONITOR MGMT_RESPONSE EXECUTE
OEM_MONITOR MGMT_UPDATE_DB_FEATURE_LOG EXECUTE
OEM_MONITOR BSLN_BASELINES SELECT
OEM_MONITOR BSLN_METRIC_DEFAULTS SELECT
OEM_MONITOR BSLN_STATISTICS SELECT
OEM_MONITOR BSLN_THRESHOLD_PARAMS SELECT
OEM_MONITOR BSLN_TIMEGROUPS SELECT
OEM_MONITOR MGMT_BASELINE SELECT
OEM_MONITOR MGMT_BASELINE_SQL SELECT
OEM_MONITOR MGMT_BSLN_BASELINES SELECT
OEM_MONITOR MGMT_BSLN_DATASOURCES SELECT
OEM_MONITOR MGMT_BSLN_INTERVALS SELECT
OEM_MONITOR MGMT_BSLN_METRICS SELECT
OEM_MONITOR MGMT_BSLN_STATISTICS SELECT
OEM_MONITOR MGMT_BSLN_THRESHOLD_PARMS SELECT
OEM_MONITOR MGMT_HISTORY SELECT
OEM_MONITOR MGMT_HISTORY_SQL SELECT
OEM_MONITOR MGMT_LATEST SELECT
OEM_MONITOR MGMT_LATEST_SQL SELECT
Oracle errro codes ORA-00052 to ORA-00057
ORA-00052: maximum number of enqueue resources (string) exceeded
Cause: Ran out of enqueue resources.
Action: Increase the value of the ENQUEUE_RESOURCES initialization parameter.
ORA-00053: maximum number of enqueues exceeded
Cause: Ran out of enqueue state objects.
Action: Increase the value of the ENQUEUES initialization parameter.
ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
Cause: Interested resource is busy.
Action: Retry if necessary or increase timeout.
ORA-00055: maximum number of DML locks exceeded
Cause: Ran out of DML lock state objects.
Action: Increase the value of the DML_LOCKS initialization parameter and warm start.
ORA-00056: DDL lock on object ‘string.string’ is already held in an incompatible mode
Cause: An attempt was made to acquire a DDL lock that is already locked.
Action: This happens if you attempt to drop a table that has parse locks on it.
ORA-00057: maximum number of temporary table locks exceeded
Cause: The number of temporary tables equals or exceeds the number of temporary table locks. Temporary tables are often created by large sorts.
Action: Increase the value of the TEMPORARY_TABLE_LOCKS initialization parameter and warm start.
Oracle error codes ORA-00043 to ORA-00051
ORA-00043: remote operation failed
Cause: Execution of the inter-instance operation failed.
Action: Check the status of the target instance. The operation may have partially executed. Verify the result of the intended operation.
ORA-00044: timed_statistics must be TRUE when statistics_level is not BASIC
Cause: The user attempted to set timed_statistics to FALSE when statistics_level was not BASIC. timed_statistics is required to be TRUE to collect meaningful statistics when statistics_level is set to TYPICAL or ALL.
Action: Either set timed_statistics to TRUE or set statistics_level to BASIC.
ORA-00050: operating system error occurred while obtaining an enqueue
Cause: Could not obtain the operating system resources necessary to cover an oracle enqueue. This is normally the result of an operating system user quota that is too low.
Action: Look up the operating system error in your system documentation and perform the needed action.
ORA-00051: timeout occurred while waiting for a resource
Cause: Usually due to a dead instance.
Action: Check for any dead, unrecovered instances and recover them.
Click Next
Select “Create a Database”
Recent Comments