World of Oracle DBA

Problem Description While installing oracle on my windows machine it fails with the message, OUI-10133: Invalid staging area. There are no top level components for Windows NT, Windows 2000 available for installation in this staging area. On linux system this message is like, OUI-10133: Invalid staging area. There are no top level components for Linux available for installation in this staging area. Cause of the problem There are many causes by which this problem can happen. 1)The product.xml directory is not found and hence the problem occurs. In the oraparam.ini the source location is specified to product.xml but no product.xml exist in the stage directory. 2)Someone has deleted the products.xml file from its location and installer could not find it. 3)You have downloaded oracle from e-delivery.oracle.com which contains three zip files and you extracted three zip files into different locations. 4)The staging area i.e stage folder is corrupted. 5)The media is corrupted. Solution of the...

What is ORACLE_HOME used for? * The ORACLE_HOME is an environment variable which is used to set and define the path of Oracle Home (server) Directory. * The ORACLE_HOME directory will have the sub directories, binaries, executables, programs, scripts, etc. for the Oracle Database. * This directory can be used by any user who wants to use the particular database. * If the ORACLE_HOME variable is defined as an environment variable, then during the installation process, the Oracle Home Path will be set to the directory defined as default. If the variable is not defined, then the Oracle will take its own default location. i.e. The ORACLE_HOME variable does not have to be preset as an environment variable, it can be set during the installation process. * Basically The ORACLE_HOME variable is in the following ORACLE_BASE directory: ORACLE_HOME=$ORACLE_BASE/product/10.2.0. What is ORACLE_BASE used for? * The ORACLE_BASE is also an environment variable to define the base/...

What is ORACLE_HOME used for? * The ORACLE_HOME is an environment variable which is used to set and define the path of Oracle Home (server) Directory. * The ORACLE_HOME directory will have the sub directories, binaries, executables, programs, scripts, etc. for the Oracle Database. * This directory can be used by any user who wants to use the particular database. * If the ORACLE_HOME variable is defined as an environment variable, then during the installation process, the Oracle Home Path will be set to the directory defined as default. If the variable is not defined, then the Oracle will take its own default location. i.e. The ORACLE_HOME variable does not have to be preset as an environment variable, it can be set during the installation process. * Basically The ORACLE_HOME variable is in the following ORACLE_BASE directory: ORACLE_HOME=$ORACLE_BASE/product/10.2.0. What is ORACLE_BASE used for? * The ORACLE_BASE is also an environment variable to define the base/...

We have recently configured shared server in some of our databases. Steps to follow to enable shared server are below. The following configuration is on Enterprise Edition 9.2.0.5. The numbers used in the settings shown are only examples. We are running an OLTP system with about 2000 concurrent users with these parameters without any problem. The parameters you need to set for the shared server and their default values are: NAME VALUE ------------------------------ ---------- circuits 0 dispatchers max_dispatchers 5 max_shared_servers 20 mts_circuits 0 mts_dispatchers mts_max_dispatchers 5 shared_server_sessions 0 shared_servers 0 The ones starting with mts are for backward compatibility, setting circuits, dispatchers and max_dispatchers or mts_circuits, mts_dispatchers and mts_max_dispatchers is the same and is up to you. If we go over these ...

We have recently configured shared server in some of our databases. Steps to follow to enable shared server are below. The following configuration is on Enterprise Edition 9.2.0.5. The numbers used in the settings shown are only examples. We are running an OLTP system with about 2000 concurrent users with these parameters without any problem. The parameters you need to set for the shared server and their default values are: NAME VALUE ------------------------------ ---------- circuits 0 dispatchers max_dispatchers 5 max_shared_servers 20 mts_circuits 0 mts_dispatchers mts_max_dispatchers 5 shared_server_sessions 0 shared_servers 0 The ones starting with mts are for backward compatibility, setting circuits, dispatchers and max_dispatchers or mts_circuits, mts_dispatchers and mts_max_dispatchers is the same and is up to you. If we go over these ...

Detailed Steps to Configure Statspack! Definition made simple: - The Statspack package is a set of SQL, PL/SQL, and SQL*Plus scripts that allow the collection, automation, storage, and viewing of performance data. Statspack stores the performance statistics permanently in Oracle tables, which can later be used for reporting and analysis. The data collected can be analyzed using Statspack reports, which includes an instance health and load summary page, high resource SQL statements, and the traditional wait events and initialization parameters. Space Requirements for Statspack! Approximately 64MB is required to install Statspack. If you install the package in a dictionary-managed tablespace, then you should monitor the space used by the objects created and, if required, adjust the storage clauses of the segments. *** If you install the package in a locally managed tablespace, then storage clauses are not required, because the storage characteristics are automatically managed. Start SQL*...

Detailed Steps to Configure Statspack! Definition made simple: - The Statspack package is a set of SQL, PL/SQL, and SQL*Plus scripts that allow the collection, automation, storage, and viewing of performance data. Statspack stores the performance statistics permanently in Oracle tables, which can later be used for reporting and analysis. The data collected can be analyzed using Statspack reports, which includes an instance health and load summary page, high resource SQL statements, and the traditional wait events and initialization parameters. Space Requirements for Statspack! Approximately 64MB is required to install Statspack. If you install the package in a dictionary-managed tablespace, then you should monitor the space used by the objects created and, if required, adjust the storage clauses of the segments. *** If you install the package in a locally managed tablespace, then storage clauses are not required, because the storage characteristics are automatically managed. Start SQL*...

Step to Create Database Manually 1. Create the directory adump,bdump,cdump,dpump,pfile,udump,archive, flash_recovery_area under C:\oracle\product\10.2.0\admin folder... Create testdb directory under C:\oracle\product\10.2.0\oradata\ folder 2. Go Cmd Prompt. C:\>set oracle_sid=testdb 3 --Create Password File C:\>orapwd file=C:\oracle\product\10.2.0\db_1\database\pwdtestdb.ora password=khaleel entries=5 4 --- Start Oracle Services C:\>oradim.exe -new -sid testdb C:\>oradim.exe -edit -sid testdb -startmode auto -srvcstart system C:\>sqlplus /nolog sql>conn / as sysdba connected Before running below script check database is shutdown sql>startup nomount pfile=C:\oracle\product\10.2.0\admin\testdb\pfile\inittestdb.ora 5. --- database creation scripts. CREATE DATABASE testdb LOGFILE GROUP 1 ('C:\oracle\product\10.2.0\oradata\testdb\testredo01.log') SIZE 100M REUSE, GROUP 2 ('C:\oracle\product\10.2.0\oradata\testdb\testredo02.log') SIZE 100M REUSE, GROUP 3 ...

Step to Create Database Manually 1. Create the directory adump,bdump,cdump,dpump,pfile,udump,archive, flash_recovery_area under C:\oracle\product\10.2.0\admin folder... Create testdb directory under C:\oracle\product\10.2.0\oradata\ folder 2. Go Cmd Prompt. C:\>set oracle_sid=testdb 3 --Create Password File C:\>orapwd file=C:\oracle\product\10.2.0\db_1\database\pwdtestdb.ora password=khaleel entries=5 4 --- Start Oracle Services C:\>oradim.exe -new -sid testdb C:\>oradim.exe -edit -sid testdb -startmode auto -srvcstart system C:\>sqlplus /nolog sql>conn / as sysdba connected Before running below script check database is shutdown sql>startup nomount pfile=C:\oracle\product\10.2.0\admin\testdb\pfile\inittestdb.ora 5. --- database creation scripts. CREATE DATABASE testdb LOGFILE GROUP 1 ('C:\oracle\product\10.2.0\oradata\testdb\testredo01.log') SIZE 100M REUSE, GROUP 2 ('C:\oracle\product\10.2.0\oradata\testdb\testredo02.log') SIZE 100M REUSE, GROUP 3 ...