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...

Whenever you connect to a database (rman version if different from source database version in fact rman version is higher than the source database) through RMAN using/without recovery catalog it fails with RMAN-06429: TARGET database is not compatible with this version of RMAN as below. C:\>rman target rman/rman@local2 catalog rman/rman@testdb Recovery Manager: Release 10.2.0.1.0 - Production on Tue Mar 24 05:07:14 2009 Copyright (c) 1982, 2005, Oracle. All rights reserved. Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 10.1.0.0 req uired RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-00554: initialization of internal recovery manager package failed RMAN-06429: TARGET database is not compatible with this version of RMAN Cause of the Problem You have higher RMAN version than the target data...

Kernel The linux kernel is the most important part or in order word called the heart of the linux operating system. It is the piece of code that manages both hardware and software components and communicates between them. It manages memory, processors, I/O devices with any applications and decides which applications will use hardware resources. Shell On your windows machine you have seen command prompt (command.com or cmd.exe) where you type command like ping, ipconfig etc. Similarly, on linux there is such prompt where you can type command and that prompt is called shell. In order to define shell we can say shell is an interpreter that interprets commands as typed from a keyboard or from a text script. The shell is provided in order to interact with the computer systems. Shell itself is not part of the kernel, but it uses kernel to executes commands. There are various types of shell and can be broadly defined into four categories. 1)Bourne like shell(sh): Almquist shell (ash), Bourne...

In many case inside your shell script you need to check whether the user who runs the script is root or not because based on the user you might need to take necessary action inside your shell script. Following shell script might help you in this case. Way 01: With system variable $LOGNAME As echo $LOGNAME show the currently logged in user show we can use this variable to determine whether it is root user. 1)create script # vi test_root.sh if [[ $LOGNAME = "root" ]] then echo "You are root user" else echo "You are $LOGNAME user" fi 2)Grant execute permission. # chmod +x test_root.sh 3)Test it by running as root. # whoami root # ./test_root.sh You are root user 4)Test it by running as oracle user. # su - oracle $ whoami oracle $ ./test_root.sh You are oracle user Way 02: As system variable $UID: As system variable $UID for root user is zero so we can use that in order to determine whether user is root. 1)create script # vi test_root2.sh if [[ $UID = "0...

In oracle data guard configuration, you need to setup one or more additional databases beside the primary database. These additional databases are called standby database. Up to nice standby database can be created for one primary database. Using a backup of primary database you can set up standby database and then you can made standby database as part of data guard configuration. Once you configured standby database, data guard automatically maintains standby database by transmitting redo log from the primary database and then applying redo to the standby database. A standby database can be of three types. 1)Physical Standby Database: A physical standby database is an identical copy of the primary database. The disk structures are also identical with primary database. It is kept synchronized with the primary database by Redo Apply- which means the redo data is received from the primary database and then redo is applied to the physical standby database. Note that as of Oracle Database...

Oracle data guard is the term(you can call it a feature too) used by oracle and this feature is integrated with oracle RDBMS. Data guard create, maintain, manage and monitor one/more extra databases -called standby database, beside production database. The goal is to survive production databases from any disasters, failure or data corruptions. At first, an exact replica of production database is created, which referred to as standby database later. Data guard then maintains and keep up to date of these standby databases with of production database. If production database becomes unavailable then data guard can switch standby database to production role and thus minimize the downtime without any data loss. In addition to availability of production database data guard gives other advantages. Like we can do real time query in standby database, do backup operation in it and thus minimize the load of production database. There is no restriction about the location of the stand by databases. ...