As a DBA, you may be responsible for creating database storage structures, such as tablespaces.

In addition, you may create the schema or set of objects to hold application data. You must ensure that the database is available for users. You accomplish this by starting up the database, backing up the database on a regular basis, and monitoring the performance of the database. These tasks should be performed within the framework of a security strategy. Oracle supplies many tools helps DBA to install, manage, update Database smoothly. Oracle Enterprise Manager Database Control is the primary tool for managing your Oracle database. It is installed with the database. Using Database Control, you can perform administrative tasks such as creating schema objects (tables, views, indexes, and so on), managing user security, managing database memory and storage, backing up and recovering your database, and importing and exporting data. You can also view performance and status information about your database.

To manage your Oracle database: Start the database instance: after the installation, your instance is started and your database is open. In the future, there will be times, perhaps for doing database maintenance or because of a power or media failure, that you shut down your database instance and later restart it. Optionally, configure the network environment to enable clients to connect to your database. Review your database storage structures: tablespaces and data files, online redo log files, and control files. Create or modify storage structures as needed. Review memory allocation and adjust as needed. Review, unlock, and reset passwords for predefined database users as needed. Create new users, and assign privileges and roles to them.

Create the necessary schema objects, including tables, views, and indexes. Populate the tables with data. Create or review the backup strategy for the database and back up the database. Enable archiving of online redo log files, if not already done. Monitor database performance, diagnose performance problems, and tune the database as necessary. Investigate, gather diagnostic data for, and report to Oracle Support Services any critical database errors. Keep Oracle Database software up-to-date with the latest releases.

Oracle Universal Installer (OUI): Installs your Oracle software and options; can automatically launch the Database Configuration Assistant to create a database

Oracle Universal Installer 11g Release 1 (11.1) is a Java-based installer that enables you to install Oracle components from CDs or from a staged HTTP location. It performs component-based installations as well as complex installations, such as integrated bundle and suite installations, and installations over the Web. Database Configuration Assistant (DBCA): Creates a database from Oracle-supplied templates, enabling you to copy a preconfigured seed database (Alternatively, you can create your own database and templates.)

The Database Configuration Assistant (DBCA) offers several choices to assist you with various operations. You can use the DBCA to create, change the configuration of, or delete a database. You can also create a database from a list of predefined templates or use an existing database as a sample to create a new database or template. The DBCA provides several options to allow you to create a database to meet your needs. The DBCA provides a series of pages where you enter configuration information. On most pages, the DBCA provides default settings that you can accept if they apply.

Database Upgrade Assistant (DBUA): Guides you through the upgrade of your existing database to a new Oracle release.

The DBUA automates the upgrade process and makes appropriate recommendations for configuration options such as tablespaces and redo logs.

Oracle Net Manager (netmgr): Configures network connectivity for your Oracle databases and applications

Oracle Net Manager enables you to configure Oracle Net Services for an Oracle home on a local client or server host. You can use Oracle Net Manager to configure the following network components:

Listeners: Create and configure listeners to receive client connections. Naming: Define connect identifiers and map them to connect descriptors to identify the network location and identification of a service. Oracle Net Manager supports configuration of connect descriptors in local tnsnames.ora files or a centralized directory service. Naming Methods: Configure the ways connect identifiers are resolved to connect descriptors. Profiles: Configure preferences for enabling and configuring Oracle Net features on the client or server.

Oracle Net Configuration Assistant (NetCA): A graphical, wizard-based toolused to configure and manage Oracle Network configurations.

During a typical database installation, Net Configuration Assistant (NETCA) automatically configures a listener called LISTENER that has a TCP/IP listening protocol address for the database. If you do a custom installation, then NETCA prompts you to configure a listener name and protocol address of your choice. Use NETCA for initial network configuration after database installation. Thereafter, you can use Oracle Enterprise Manager and Oracle Net Manager to configure and administer your networks. Server Control Utility (srvctl): Standard command-line interface that can be used to start and stop the database and instances, manage ASM instances, manage configuration information, and move or remove instances and services. You can also use SRVCTL to add services and manage configuration information.

The Server Control (SRVCTL) utility is installed on each node by default. You can use SRVCTL to start and stop the database and instances, manage configuration information, and to move or remove instances and services. You can also use SRVCTL to add services. SRVCTL also manages configuration information. Some SRVCTL operations store configuration information in the Oracle Cluster Registry

(OCR). SRVCTL performs other operations, such as starting and stopping instances, by sending requests to the Oracle Clusterware process (CRSD), which then starts or stops the Oracle Clusterware resources.

Recovery Manager (RMAN): Oracle tool that provides a complete solution for the backup, restoration, and recovery needs of the entire database or of specific database files.

Recovery Manager (RMAN) is an Oracle Database client that performs backup and recovery tasks on your databases and automates administration of your backup strategies. It greatly simplifies backing up, restoring, and recovering database files. The RMAN environment consists of the utilities and databases that play a role in backing up your data. At a minimum, the environment for RMAN must include the following components: A target database: an Oracle database to which RMAN is connected with the TARGET keyword. A target database is a database on which RMAN is performing backup and recovery operations. RMAN always maintains metadata about its operations on a database in the control file of the database. The RMAN metadata is known as the RMAN repository. The RMAN client: an Oracle Database executable that interprets commands, directs server sessions to execute those commands, and records its activity in the target database control file. The RMAN executable is automatically installed with the database and is typically located in the same directory as the other database executables. For example, the RMAN client on Linux is located in $ORACLE_HOME/bin.

Data Pump: Enables the high-speed transfer of data from one database to another (For example, you may want to export a table and import it into another database.)

Oracle Data Pump is a feature of Oracle Database 11g Release 2 that enables very fast bulk data and metadata movement between Oracle databases. Oracle Data Pump provides new high-speed, parallel Export and Import utilities (expdp and impdp) as well as a Web-based Oracle Enterprise Manager interface. Data Pump Export and Import utilities are typically much faster than the original Export and Import Utilities. A single thread of Data Pump Export is about twice as fast as original Export, while Data Pump Import is 15-45 times fast than original Import. Data Pump jobs can be restarted without loss of data, whether or not the stoppage was voluntary or involuntary. Data Pump jobs support fine-grained object selection. Virtually any type of object can be included or excluded in a Data Pump job. Data Pump supports the ability to load one instance directly from another (network import) and unload a remote instance (network export).