Oracle Database Administrators

How to overcome the error ( CRS-0223 resource has placement error) when starting rac database using srvctl

2012-01-24T03:51:00.000-08:00

When starting the RAC database using srvctl you may get the following error
CRS-0223 resource has placement error
the reason behind this the ASM instances are not started before
Lets consider we run a two node rac setup
where nodes are rac1,rac2
do the following to overcome the error
Step 1.
login to rac1 using putty as root
login as oracle user
$crsctl check crs
make sure all the status is UP
Step 2.
do the following in rac1 as oracle user
$export ORACLE_SID=+ASM1
$sqlplus ‘/ as sysdba’
SQL>select * from v$instance;
ensure that the ASM1 is up..
if not start it
you can start also using $srvctl start asm -n rac1
Step 3.
do the following in rac2 as oracle user
$export ORACLE_SID=+ASM2
$sqlplus ‘/ as sysdba’
SQL>select * from v$instance;
ensure that the ASM2 is up..
if not start it
you can start also using $srvctl start asm -n rac2
Step 4.
verify the listener is up in both nodes
lsnrctl status , if not start in rac1
using $lsnrctl start LISTENER_RAC1
in rac2
$lsnrctl status , if not started then start it
using $lsnrctl start LISTENER_RAC2
Step 5.
login to tmprac1 and start the database using
$srvctl start database -d
if it is giving any error then start it using sqlplus
$sqlplus ‘ / as sysdba’
SQL>startup
do this in rac2 also
after everything login to sqlplus ‘/ as sysdba’
SQL>select * from v$active_instances;
it will display two RAC database instances;;
so now the startup is complete..

How to enable Wampserver when Oracle Agent is Running

2011-11-26T03:36:00.001-08:00

First of all both Wampserver and Oracle Sql PLus utilises the same web server Apache .Since you have installed both the oracle and the wampserver suite .. it means that you have installed Apache Web Server two times .
Databases Normalization E Book(R. Comprehensive EBook(R) On Normalization Techniques For General Relational Databases Such As Oracle, Sql Server And Others.!
The one which is installed recently will be working fine and the firstly installed suite will not work since it will be disabled by the recently installed suite.
Or else the Oracle will work fine since the oracle agent and the oracle HTTP server will be activated while booting . Since wampserver is activated only when th developer starts it , it will show that the wampserver is offline in the quick launch toolbar .
For rectifying this problem,Do the following steps:-
Step 1:
Start the Wampserver and wait for the wampserver icon to launch in the quick launch toolbar.Then click on the icon anselect -> localhost.

Step 2:
Step 1 results in the following page.

Step 3:
Oracle 10g Database, Oracle 9i, Oracle 11g, Oracle 11i & Oracle R12 Student Guides.
Now select the following Wampserver icon -> Apache ->httpd.conf

Step 4:
Now the httpd.conf file opens ,then search for the text listen and then change the port no Listen 80 to
ip address:8080
Listen 8080
as shown below in the image

Step 5:
Now restart the wampserver and click put online if the below screen is displayed.

Step 6:
If that doesnt work out, do this and stop the Oracle services which are automatic as shown below..

Step 7:
Then repeat the step 5 .Then click on the icon anselect -> localhost.
I hope ur wampserver works fine ... if u still have doubt comment here ...

Manual Database Creation Oracle 11g

2011-09-16T20:44:00.000-07:00

Manually Database Creation is one of the most important works of aDBA.

The procedure is same as previous which we are used for 9i, 10g.

In this database creation I used below features

1. OMF (Oracle Managed File) for datafiles, redolog files & controlfiles
2. FRA (Flash Recovery Area) for Archivelog or backup files

1. Create Required Directories

Microsoft Windows XP [Version 5.1.2600]

C:\Documents and Settings\UserXP>mkdir D:\app\UserXP\admin\mandb11g

2. Set Enviourment Variable (ORACLE_HOME,ORACLE_SID,PATH)

C:\Documents and Settings\UserXP>set ORACLE_HOME=D:\app\UserXP\product\11.1.0\db
_1

C:\Documents and Settings\UserXP>set PATH=D:\app\UserXP\product\11.1.0\db_1\BIN

C:\Documents and Settings\UserXP>set ORACLE_SID=mandb11g

3. Creating INIT.ORA parameter file

Set minimum required parameter in INIT.ora file.

Open NOTEPAD file and set below parameters

db_name = 'MANDB11G'
#Database name.

db_create_file_dest='D:\app\UserXP\oradata\mandb11g\data'
#OMF configuration for Datafile,controlfile
db_create_online_log_dest_1='D:\app\UserXP\oradata\mandb11g\redo'
#OMF configuration for redolog file

db_recovery_file_dest='D:\app\UserXP\oradata\mandb11g\flash_recovery'
db_recovery_file_dest_size=4G
#FRA (FLASH RECOVERY AREA configuration)

diagnostic_dest='D:\app\UserXP\admin\mandb11g'
#It is new feature with 11g for trace files (bdump,udump,cdump or many others
#folder created in "DIAG" folder inside "D:\app\UserXP\admin\mandb11g" folder.

Save it in Temporary folder.

4. Create an Instance

C:\Documents and Settings\UserXP>oradim -new -sid mandb11g -startmode auto

Instance created.

5. Connect to an Instance

C:\Documents and Settings\UserXP>sqlplus /nolog

SQL*Plus: Release 11.1.0.7.0 - Production on Tue Aug 9 05:49:42 2011

SQL> conn / as sysdba

Connected to an idle instance.

6. Create Server Parameter file (SPFILE)

SQL> create spfile from pfile='D:\init.ora';

File created.

7. Start the Instance

SQL> startup nomount

ORACLE instance started.

Total System Global Area 150667264 bytes

Fixed Size 1345868 bytes

Variable Size 92276404 bytes

Database Buffers 50331648 bytes

Redo Buffers 6713344 bytes

7. Start the Instance

SQL> create database mandb11g;

Database created.

9. Create Temporary and Additional Tablespace

SQL> create temporary tablespace temp tempfile size 5m;

Tablespace created.

SQL> create tablespace userdata datafile size 10m autoextend on;

Tablespace created.

SQL> alter database default temporary tablespace temp;

Database altered.

SQL> alter database default tablespace userdata;

Database altered.

SQL> shutdown immediate

Database closed.

Database dismounted.

ORACLE instance shut down.

SQL> startup mount

ORACLE instance started.

Total System Global Area 150667264 bytes

Fixed Size 1345868 bytes

Variable Size 92276404 bytes

Database Buffers 50331648 bytes

Redo Buffers 6713344 bytes

Database mounted.

SQL> alter database archivelog;

Database altered.

SQL> alter database open;

Database altered.

10. Run Scripts to build data dictionary views

@%ORACLE_HOME%/rdbms/admin/catalog.sql
@%ORACLE_HOME%/rdbms/admin/catproc.sql
@%ORACLE_HOME%/sqlplus/admin/pupbld.sql

11. Change Database Mode from NO-ARCHIVELOG to ARCHIVELOG.

SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.

SQL> startup mount
ORACLE instance started.
Total System Global Area 150667264 bytes
Fixed Size 1331740 bytes
Variable Size 92278244 bytes
Database Buffers 50331648 bytes
Redo Buffers 6725632 bytes
Database mounted.
SQL> alter database ARCHIVELOG;
Database altered.
SQL> alter database OPEN;
Database altered.

NOTE: It is recommended to run database in ARCHIVELOG MODE

12. Check all database files

SQL> select NAME from v$datafile

2 union all

3 select NAME from v$controlfile

4 union all

5 select MEMBER from v$logfile;

NAME

--------------------------------------------------------------------------------

D:\APP\USERXP\ORADATA\MANDB11G\DATA\MANDB11G\DATAFILE\O1_MF_SYSTEM_741CP7KL_.DBF

D:\APP\USERXP\ORADATA\MANDB11G\DATA\MANDB11G\DATAFILE\O1_MF_SYSAUX_741CPC5V_.DBF

D:\APP\USERXP\ORADATA\MANDB11G\DATA\MANDB11G\DATAFILE\O1_MF_SYS_UNDO_741CPFMK_.D

D:\APP\USERXP\ORADATA\MANDB11G\DATA\MANDB11G\DATAFILE\O1_MF_USERDATA_741CY41G_.D

D:\APP\USERXP\ORADATA\MANDB11G\REDO\MANDB11G\CONTROLFILE\O1_MF_741CP37T_.CTL

D:\APP\USERXP\ORADATA\MANDB11G\REDO\MANDB11G\ONLINELOG\O1_MF_1_741CP3PG_.LOG

D:\APP\USERXP\ORADATA\MANDB11G\REDO\MANDB11G\ONLINELOG\O1_MF_2_741CP5D6_.LOG

7 rows selected.

SQL>

RMAN Backup and Recovery Scenarios in Oracle

2011-08-31T13:31:00.000-07:00

Complete Closed Database Recovery. System tablespace is missing

If the system tablespace is missing or corrupted the database cannot be started up so a complete closed database recovery must be performed.

Pre requisites: A closed or open database backup and archived logs.

1. Use OS commands to restore the missing or corrupted system datafile to its original location, ie:

cp -p /user/backup/uman/system01.dbf /user/oradata/u01/dbtst/system01.dbf

2. startup mount;
3. recover datafile 1;
4. alter database open;

Complete Open Database Recovery. Non system tablespace is missing

If a non system tablespace is missing or corrupted while the database is open, recovery can be performed while the database remain open.

Pre requisites: A closed or open database backup and archived logs.

1. Use OS commands to restore the missing or corrupted datafile to its original location, ie:

cp -p /user/backup/uman/user01.dbf /user/oradata/u01/dbtst/user01.dbf

2. alter tablespace offline immediate;

3. recover tablespace ;

4. alter tablespace online;

Complete Open Database Recovery (when the database is initially closed).Non system tablespace is missing

If a non system tablespace is missing or corrupted and the database crashed,recovery can be performed after the database is open.

Pre requisites: A closed or open database backup and archived logs.

1. startup; (you will get ora-1157 ora-1110 and the name of the missing datafile, the database will remain mounted)

2. Use OS commands to restore the missing or corrupted datafile to its original location, ie:

cp -p /user/backup/uman/user01.dbf /user/oradata/u01/dbtst/user01.dbf

3. alter database datafile3 offline; (tablespace cannot be used because the database is not open)

4. alter database open;

5. recover datafile 3;

6. alter tablespace online;

Recovery of a Missing Datafile that has no backups (database is open).

If a non system datafile that was not backed up since the last backup is missing,recovery can be performed if all archived logs since the creation of the missing datafile exist.
Pre requisites: All relevant archived logs.

1. alter tablespace offline immediate;

2. alter database create datafile ‘/user/oradata/u01/dbtst/newdata01.dbf’;

3. recover tablespace ;

4. alter tablespace online;

If the create datafile command needs to be executed to place the datafile on a location different than the original use:

alter database create datafile ‘/user/oradata/u01/dbtst/newdata01.dbf’ as ‘/user/oradata/u02/dbtst/newdata01.dbf’

Restore and Recovery of a Datafile to a different location.

If a non system datafile is missing and its original location not available, restore can be made to a different location and recovery performed.
Pre requisites: All relevant archived logs.

1. Use OS commands to restore the missing or corrupted datafile to the new location, ie:

cp -p /user/backup/uman/user01.dbf /user/oradata/u02/dbtst/user01.dbf

2. alter tablespace offline immediate;

3. alter tablespace rename datafile ‘/user/oradata/u01/dbtst/user01.dbf’ to ‘/user/oradata/u02/dbtst/user01.dbf’;

4. recover tablespace ;

5. alter tablespace online;

Control File Recovery

Always multiplex your controlfiles. Controlfiles are missing, database crash.
Pre requisites: A backup of your controlfile and all relevant archived logs.

1. startup; (you get ora-205, missing controlfile, instance start but database is not mounted)

2. Use OS commands to restore the missing controlfile to its original location:

cp -p /user/backup/uman/control01.dbf /user/oradata/u01/dbtst/control01.dbf
cp -p /user/backup/uman/control02.dbf /user/oradata/u01/dbtst/control02.dbf

3. alter database mount;

4. recover automatic database using backup controlfile;

5. alter database open resetlogs;

6. make a new complete backup, as the database is open in a new incarnation and previous archived log are not relevant.

Incomplete Recovery, Until Time/Sequence/Cancel

Incomplete recovery may be necessaire when an archived log is missing, so recovery can only be made until the previous sequence, or when an important object was dropped, and recovery needs to be made until before the object was dropped.

Pre requisites: A closed or open database backup and archived logs, the time or sequence that the ‘until’ recovery needs to be performed.

1. If the database is open, shutdown abort

2. Use OS commands to restore all datafiles to its original locations:

cp -p /user/backup/uman/u01/*.dbf /user/oradata/u01/dbtst/

cp -p /user/backup/uman/u02/*.dbf /user/oradata/u01/dbtst/

cp -p /user/backup/uman/u03/*.dbf /user/oradata/u01/dbtst/

cp -p /user/backup/uman/u04/*.dbf /user/oradata/u01/dbtst/

etc…

3. startup mount;

4. recover automatic database until time ’2004-03-31:14:40:45′;

5. alter database open resetlogs;

6. make a new complete backup, as the database is open in a new incarnation and previous archived log are not relevant.Alternatively you may use instead of until time, until sequence or until cancel:
recover automatic database until sequence 120 thread 1; OR
recover database until cancel;

Rman Recovery Scenarios

Rman recovery scenarios require that the database is in archive log mode, and that backups of datafiles, control files and archived redolog files are made using Rman. Incremental Rman backups may be used also.

Rman can be used with the repository installed on the archivelog, or with a recovery catalog that may be installed in the same or other database.

Configuration and operation recommendations:

Set the parameter controlfile autobackup to ON to have with each backup a
controlfile backup also:

configure controlfile autobackup on;

set the parameter retention policy to the recovery window you want to have,

ie redundancy 2 will keep the last two backups available, after executing delete obsolete commands:

configure retention policy to redundancy 2;

Execute your full backups with the option ‘plus archivelogs’ to include your archivelogs with every backup:

backup database plus archivelog;

Perform daily maintenance routines to maintain on your backup directory the number of backups you need only:

crosscheck backup;

crosscheck archivelog all;

delete noprompt obsolete backup;

To work with Rman and a database based catalog follow these steps:

1. sqlplus /

2. create tablespace repcat;

3. create user rcuser identified by rcuser default tablespace repcat temporary tablespace temp;

4. grant connect, resource, recovery_catalog_owner to rcuser

5. exit

6. rman catalog rcuser/rcuser # connect to rman catalog as the rcuser

7. create catalog # create the catalog

8. connect target / #

Complete Closed Database Recovery. System tablespace is missing

In this case complete recovery is performed, only the system tablespace is missing,so the database can be opened without reseting the redologs.

1. rman target /

2. startup mount;

3. restore database;

4. recover database;

5. alter database open;

Complete Open Database Recovery. Non system tablespace is missing,database is up

1. rman target /

2. sql ‘alter tablespace offline immediate’;

3. restore datafile 3;

4. recover datafile 3;

5. sql ‘alter tablespace online’;

Complete Open Database Recovery (when the database is initially closed).Non system tablespace is missing

A user datafile is reported missing when tryin to startup the database. The datafile can be turned offline and the database started up. Restore and recovery are performed using Rman. After recovery is performed the datafile can be turned online again.

1. sqlplus /nolog

2. connect / as sysdba

3. startup mount

4. alter database datafile ‘’ offline;

5. alter database open;

6. exit;

7. rman target /

8. restore datafile ‘’;

9. recover datafile ‘’;

10. sql ‘alter tablespace online’;

Recovery of a Datafile that has no backups (database is up).

If a non system datafile that was not backed up since the last backup is missing,recovery can be performed if all archived logs since the creation of the missing datafile exist. Since the database is up you can check the tablespace name and put it offline. The option offline immediate is used to avoid that the update of the datafile header.

Pre requisites: All relevant archived logs.

1. sqlplus ‘/ as sysdba’

2. alter tablespace offline immediate;

3. alter database create datafile ‘/user/oradata/u01/dbtst/newdata01.dbf;

4. exit

5. rman target /

6. recover tablespace ;

7. sql ‘alter tablespace online’;

If the create datafile command needs to be executed to place the datafile on a location different than the original use:

alter database create datafile ‘/user/oradata/u01/dbtst/newdata01.dbf’ as ‘/user/oradata/u02/dbtst/newdata01.dbf’

Restore and Recovery of a Datafile to a different location. Database is up.

If a non system datafile is missing and its original location not available, restore can be made to a different location and recovery performed.

Pre requisites: All relevant archived logs, complete cold or hot backup.

1. Use OS commands to restore the missing or corrupted datafile to the new location, ie:

cp -p /user/backup/uman/user01.dbf /user/oradata/u02/dbtst/user01.dbf

2. alter tablespace offline immediate;

3. alter tablespace rename datafile ‘/user/oradata/u01/dbtst/user01.dbf’ to ‘/user/oradata/u02/dbtst/user01.dbf’;

4. rman target /

5. recover tablespace ;

6. sql ‘alter tablespace online’;

Control File Recovery

Always multiplex your controlfiles. If you loose only one controlfile you can replace it with the one you have in place, and startup the Database. If both controlfiles are missing, the database will crash.

Pre requisites: A backup of your controlfile and all relevant archived logs. When using Rman alway set configuration parameter autobackup of controlfile to ON. You will need the dbid to restore the controlfile, get it from the name of the backed up controlfile.It is the number following the ‘c-’ at the start of the name.

1. rman target /

2. set dbid

3. startup nomount;

4. restore controlfile from autobackup;

5. alter database mount;

6. recover database;

7. alter database open resetlogs;

8. make a new complete backup, as the database is open in a new incarnation and previous archived log are not relevant.

Incomplete Recovery, Until Time/Sequence/Cancel

Incomplete recovery may be necessaire when the database crash and needs to be recovered, and in the recovery process you find that an archived log is missing. In this case recovery can only be made until the sequence before the one that is missing.

Another scenario for incomplete recovery occurs when an important object was dropped or incorrect data was committed on it.

In this case recovery needs to be performed until before the object was dropped.

Pre requisites: A full closed or open database backup and archived logs, the time or sequence that the ‘until’ recovery needs to be performed.

1. If the database is open, shutdown it to perform full restore.

2. rman target \

3. startup mount;

4. restore database;

5. recover database until sequence 8 thread 1; # you must pass the thread, if a single instance will always be 1.

6. alter database open resetlogs;

7. make a new complete backup, as the database is open in a new incarnation and previous archived log are not relevant.Alternatively you may use instead of until sequence, until time, ie: ’2004-12-28:01:01:10′.

How to Install Windows XP from a USB Flash Drive

2011-06-26T07:39:00.000-07:00

How to Install Windows XP from a USB Flash Drive

What do you do when there is no optical drive in your PC or Laptop and you want to install a Windows XP on it? You can use a USB drive to do the same. Here is a detailed step by step procedure to install Windows XP from a USB Flash Drive in your computer. Before we Install, we should create a bootable USB flash drive with Windows XP loaded into it. This will be required if we want to reinstall the OS.

Previously we discussed How to Boot into Windows XP using a Flash Drive

Install Windows XP from a USB Flash Drive

In order to install Windows XP from a flash drive, first you should dump your OS into this thumb drive. In order to do that, you will need

a desktop or laptop with Windows XP/Vista/7
An optical drive in the PC.
The original Windows XP or Vista or Windows 7 installation disk.
A USB flash drive for Windows OS.
A software called ‘Komku-SP-usb.exe’

Here is the procedure to make the USB Flash Drive ready i.e., to make it bootable.

Step 1: Download and install ‘Komku’

Download the software ‘Komku-SP-usb.exe’ from this link and execute it. The executable file will extract the necessary utilities to a folder called ‘C:komku’.

STEP 2: Prepare the USB drive

Once the package has been extracted, go to the folder ‘C:komkuPeToUSB’ using Windows Explorer. Execute the file ‘PeToUSB.exe’. Plug in the USB flash drive and make sure you choose the following (see image below) before clicking the start button.

Select ‘USB removable’, ‘Enable Disk Format’, ‘Quick format’, ‘Enable LBA (Fat 16x)’ and finally give the drive a name under ‘Drive Label’. Once it’s done, click start to let the utility format the drive.

STEP 3: Copy the boot sector to the USB flash drive

Next you will need to start the command prompt. Click ‘Start > Run’, type ‘cmd’ and press [Enter]. Then go to the ‘bootsect’ directory by typing the command ‘cd C:komkubootsect’ and pressing [Enter].

Now type the command ‘bootsect /nt52 F:’ and press [Enter]. (The ‘F:’ is the USB flash drive letter represented in ‘My Computer’. Check to verify the drive letter used by your USB flash drive). Let the utility do the needful. Do not exit the Command Prompt yet.

STEP 4: Launch the ‘USB_prep8′ utility.

Now you will need to change to the directory ‘Usb_Prep8’ by using the command ‘cd C:komkuusb _ prep8’ and pressing [Enter].

Here execute the command ‘usb _ prep8’ and press [Enter]. Press any key to continue and you will see a welcome screen with a menu appear in the Command Prompt.

STEP 5: Enter the source path for the Windows XP CD.

Now at this stage, you will have to insert the Windows XP installation disk into your optical drive. At the Command Prompt menu, type ‘1’ and press [Enter]. A new popup will appear asking you to choose the location (path) of the Windows installation disk.

Select the optical drive and click ‘OK’. Next choose ‘2’ from the menu and change the drive letter to any drive letter which has not been taken. It is drive ‘T:’ by default and you can ignore this step unless you do have a ‘T:’ drive on your computer. After this, choose ‘3’ from the menu and enter the drive letter of your USB flash drive (in this case it would be ‘F’).

Finally choose ‘4’ from the menu and press [Enter]. Wait for a few seconds for the process to complete and you will see a prompt to allow the utility to format the USB fash drive. Type ‘Y’ and then press [Enter] at this stage to let the utility proceed and install the necessary files from the Windows XP installation disk to the USB flash drive. This process will take a few minutes and depends on the speed of the flash drive.

STEP 6: Allow the utility to copy the data to the drive

After the files are copied, you will see a popup window asking you for permission to copy files from the temp drive to the USB flash drive. Select ‘Yes’.

STEP 7: Allow the changes to allocate a drive letter.

Next there will be another popup window asking you to allow the utility to change the boot drive letter of the USB flash drive from ‘F:’ to ‘U:’. Select ‘Yes’.

STEP 8: Unmount the virtual drive.

Finally, after all the processes are complete, you will see yet another popup window asking if you want to unmount the virtual drive. Select ‘Yes’. Exit the Command Prompt now and you will see that your flash drive is ready to install Windows XP to another computer.

To install Windows XP to the computer, you will have to do the following steps..

Go to the BIOS and enable the option of booting from a USB removable device. This option is usually found under the boot sequence menu of the BIOS.
Plug in the USB drive to the computer before you turn it on.
Now your computer will boot from the USB flash drive and will be ready to install Windows XP.

Follow the necessary steps to install Windows XP and your computer will be up, raring and ready to go and running Windows in no time. This is an easy and better way to install your Operating System as a USB port is available on every system.

How to install Windows XP from USB flash drive

2011-06-26T07:03:00.000-07:00

How to install Windows XP from USB flash drive Part-I

At first download the software Win to Flash . It does not need the installation. After running the setup file the following screen will appear.

From Task tab you can chose your task.

After choosing task press next .

Select the source path of the windows installation disk or copy and then the path of your USB flash drive.

Now the exact bootable copy will be made in the USB Flash drive.
You can now install Windows XP from Flash drive.It is pretty easy method to install Windows XP from your Usb flash drive.If any problem arises then contact us.You can also manually build your USB flash drive enabled for installing XP in it.
But that process is quite complex and so I recommend the process Install Windows XP from USB Flash Drive part-II. Any question or suggestion is always welcome.

Install Windows XP From USB Flash Drive Part-II

I previously wrote an article Install Windows XP from USB Flash/Pen Drive part-I. This process allows you make a USB flash disk/drive bootable and exactly the same as the XP installation CD.

To make the whole process you should have a PC/Computer/Laptop with CD/DVD Rom. Once you make your USB drive ready to boot windows XP setup from it then you can start Installing Windows XP from that USB Disk/drive in any computer.
Also read how to Install Any Software You need In Your USB Flash Drive With Mojopac.
I shall describe the process how to make the USB drive ready to install XP in your computer step by step.
Requirements:
1. At first you have to get a USB flash drive/disk(at least 1 GB).
2. XP_FROM_USB.rar from the given link below:
Download link
Update: You should have XP installed computer for this process.

The procedure

1. Extract the XP_FROM_USB.rar archive in a folder named Softslas(Say) in C: drive.
Now navigate to C:\Softslas\PeToUSB\ and double click on the peToUSB.exe

The appearing window will be like this
Set these:

select “USB Removable as Destination Drive”
select “Enable Disk Format”
select “Quick Format”
select “Enable LBA (FAT 16x)”
Put XP-Softslas (or whatever you want) in Drive Label :

Now click Start
Then you will get the message and click yes
Another message box will again appear and click Yes

After clicking on “Yes” the USB disk will be formatted.Wait for few seconds and then click on “Ok” and then chose “Close”.
3. Now open the windows Command prompt typing cmd in Start->Run
Now in Command Prompt window type
cd c:\softslas\bootsect and press “Enter”.
Now type the command
bootsect /nt52 I: and press “Enter”

Then again type “cd..” and press “Enter” and cd usb_prep8 and press “Enter”.

Now type usb_prep8 and press “Enter”.

4. Press any key to continue.
Now the command prompt window will look like this.

Prepares Windows XP LocalSource for Copy to USB-Drive:
0) Change Type of USB-Drive, currently [USB-stick]
1) Change XP Setup Source Path, currently []
2) Change Virtual TempDrive, currently [T:]
3) Change Target USB-Drive Letter, currently []
4) Make New Tempimage with XP LocalSource and Copy to USB-Drive
5) Use Existing Tempimage with XP LocalSource and Copy to USB-Drive
F) Change Log File – Simple OR Extended, currently [Simple]
Q) Quit
Enter your choice:_

Insert the XP installation CD in you CD/DVD ROM and in command prompt window type 1 and press “Enter”..
A “Browse For Folder” window will appear and here select the CD/DVD drive and then click OK.
Similarly for the choice field enter 2 and if there assigned the letter “T” for your computer then change it otherwise do not alter it. After typing 2 in the choice option it will prompt “Enter Available Virtual Drive Letter”.
Here type a letter that is not any drive letter of your computer.
Let us say S is not a drive letter in your computer. So put S then press “Enter”.
Now it will get back to the Command prompt and then type 3 where it prompts for the choice. Then it will prompt “Please give Target USB-Drive Letter e.g type U”.

Now put your USB drive letter and press “Enter”. Here my USB drive label is “I” so I put “I”.
Now input 4 and press Enter. It creates the new temporary image and makes a copy of it to the USB Flash Drive .
Please wait for a few seconds..
A warning message will appear like this:
“WARNING, ALL DATA ON NON-REMOVABLE DISK DRIVE T: WILL BE LOST! Proceed with Format (Y/N)?”
Type Y and press “Enter”.
Please wait………..
After completing Format it will prompt “Press any key to continue” and to continue hit any key .
Please wait………..
It will again prompt “Press any key to continue” and obviously press any key to continue.
5. Now a message box will appear showing
“Copy TempDrive Files to USB-Drive in about 15 minutes = Yes OR STOP = End Program = No”

Click “Yes”.
Now after this a message box will appear showing “Would you like USB-stick to be preferred Boot Drive U……………….”
Click “Yes”.
The next one asking “Would you like to unmount the Virtual Drive ?”

Click “Yes”.
Now wait some time and press any key…………….
Press any key again to close usb_prep8.
Now your USB you can Install Windows XP from the USB drive.
6. Insert your USB drive in the USB port and Reboot your computer. When starts the computer enter in the BIOS Setup and set the first boot preference as USB Hard Disk.Now Save and Exit from the BIOS Setup. Your computer will again restart and the following screen will appear.

Now Chose The TXT Mode Setup.After completing the partition, formatting and copying file the computer will restart again.
Now chose the GUI Mode Setup Option.
Wait for completing your installation.
I think this will help you to install XP from USB flash disk/drive especially in those computer without CD/DVD ROM.

Oracle Background Processes - Oracle 10g

2011-06-05T02:54:00.000-07:00

Process Monitor	PMON	Responsible for cleaning up after abnormally terminated connections. Responsible for monitoring other server processes and restarting them if necessary Registers the instance with the listener dynamically (dynamic service registration). Restarts failed server processes and dispatcher processes
System Monitor	SMON	Temporary space cleanup Crash recovery apon restart Coalescing free space Recovering transactions active against unavailable files Instance recovery of failed node in OPS (Oracle parallel server) Cleans up OJB$ (Low Level data dictionary) Shrinks rollback segments Offline's rollback segments Other processes call the SMON process when required.
Distributed database recovery	RECO	Recovers transactions that are left in a prepared state because of a crash or loss of connection during a two-phase commit.
Checkpoint process	CKPT	The checkpoint process is charged with instructing the database block buffer writers to write the database buffer cache to disk, it then updates the data file headers and control file to indicate when the checkpoint was performed. There is a relationship with checkpoints and recovery time, the more checkpointing the less recovery time is need when a crash occurs. The ckpt process does not do the checkpoint but assists with the checkpointing process by updating the file headers of the data files. A checkpointing process involves the following: Flushing the redo log buffers to the redo log files Writing a checkpoint record to the redo log file Flushing the database log buffers to the data files Updating the data file headers and control files after the checkpoint completes
Database block writer	DBWn	Responsible for writing dirty blocks to disk when free space within the database buffer cache is low, it writes the dirty blocks from the buffer cache out to the disk. It uses the LRU (Least Recently Used) algorithm which retains data in the memory based on how long it has been since someone asked for that data. The database buffer cache is flushed to disk when the database issues a checkpoint when a server process can't find a clean reusable buffer after checking a threshold number of buffers every 3 seconds users process has searched to long for a free buffer when reading a buffer into the buffer cache Instance is shutdown tablespace is put in backup mode or offline segment is dropped If you have multiple CPU's then it is advised to run multiple database writers. Use the DB_WRITER_PROCESSES parameter to increase the number of database writers, the instance has to be rebooted.
Log writer	LGWR	Responsible for flushing to disk the contents of the redo log buffer located in the SGA. Both committed and uncommitted changes are written to the redo log buffer. The redo log buffer is flushed to disk before the data blocks are written to disk. The redo log buffer is flushed to disk every 3 seconds whenever a user commits a transaction when the redo log buffer is a third full or contains 1 Mb of buffered data before the DBWn process writes when a checkpoint occurs
Archive process	ARCn	Used when the database is in archive-mode, it copies the online redo log file to another location when LGWR fills up, these log files would be used to perform media recovery. There can be a maximum of ten archive processes running ARC0-ARC9. The LOG_ARCHIVE_MAX_PROCESSES parameter determines how many archive processes will be started (default is 1).
Manageability Monitor	MMON	Collects statistics to help the database manage itself. The MMON process collects the AWR (automatic workload repository) snapshot information which is used by the ADDM (automatic database diagnostic monitor), also MMON issues alerts when database thresholds are exceeded.
Manageability Monitor Light	MMNL	The process flushes ASH information to disk when the buffer is full, it also captures session history and database metrics.
Memory Manager	MMAN	Uses the the metrics collected to determine the ideal distribution of memory within oracle. It constantly monitors the database and adjusts the memory allocations according to workloads.
Job Queue Coordination	CJQ0	Used to schedule and run user jobs. It spawns job queue slave processes (J000-J999) which actually run the job.
Job Queue Process	J000-J999	These processes are what actually run the schedule jobs requested by CJQ0.
File Mapping Monitor	FMON	Maps files to immediate storage layers and physical devices. Results are normally kept in the DBMS_STORAGE_MAP view. Generally the 3rd party LVM (logical volume manager) supplier will supply a driver to map to.
Recovery Writer	RVWR	This process is started when you implement flashback logging, it logs the before image (taken from the flashback buffers) of an oracle block before it is changed, this is written to the flashback log files.
Change Tracking Writer	CTWR	This process tracks any data blocks that have changed which then RMAN can use to speed up backups as it will no longer need to read the entire data file to see what has changed.
Queue Monitor Coordinator	QMNC	Spawns and coordinates queue slave processes.
Block server process	BSP	Used in OPS and keeps each servers SGA in the clusters consistent with each other.
Lock monitor process	LMON	Used in OPS and monitors all instances in a cluster to detect a failure of an instance.
Lock manager daemon	LMD	Used in OPS and controls the global locks and global resources for the block buffer cache in a clustered environment.
Lock process	LCKn	Used in OPS and is the same as the LMD daemon but handles requests for all global resources other than database block buffers
Dispatcher process	Dnnn	Dispatcher processes that are used when using a shared server environment
Shared Server process	Snnn	Shared Server processes that are used when using a shared server environment
Oracle process spawner	PSP0	Process spawner has the job of creating and managing other Oracle processes.
Oracle shadow process	SHAD	Oracle's shadow process, could not find much on this process
Streams Advanced Queuing process	q000 - q???	I believe this is something to do with Oracle Streams Advanced Queuing I believe this is something to do with Oracle Streams Advanced Queuing

Gathering Table statistics in Oracle - DBMS_STATS.GATHER_TABLE_STATS

2011-01-25T09:02:00.000-08:00

DECLARE

CURSOR CUR_PARTITION IS

SELECT TABLE_NAME FROM DBA_TABLES WHERE OWNER = 'SUVIN' AND PARTITIONED ='YES';

CURSOR CUR_NONPARTITION IS

SELECT OWNER, TABLE_NAME FROM DBA_TABLES WHERE OWNER IN ('SUVIN','RETAIL') AND PARTITIONED != 'YES' AND TABLE_NAME NOT IN ('RETAIL_TRANS', 'WHOLETRANS');

BEGIN

FOR REC_PARTITION IN CUR_PARTITION LOOP

DBMS_STATS.GATHER_TABLE_STATS(

ownname => 'SUVIN',

tabname => REC_PARTITION.table_name,

partname => NULL,

estimate_percent => 100,

block_sample => FALSE,

method_opt => 'FOR ALL COLUMNS SIZE 1', -- including column stats, without histograms

degree => 4, -- running parallel for partitioned tables with degree of 4

granularity => 'ALL', -- global, partition, subpartition stats

cascade => TRUE, -- including index stats

stattab => NULL,

statid => NULL,

force => TRUE,

statown => NULL);

END LOOP;

FOR REC_NONPARTITION IN CUR_NONPARTITION LOOP

DBMS_STATS.GATHER_TABLE_STATS(

ownname => rec_nopart_tab.owner,

tabname => rec_nopart_tab.table_name,

partname => NULL,

estimate_percent => 100,

block_sample => FALSE,

method_opt => 'FOR ALL COLUMNS SIZE 1', -- including column stats, without histograms

degree => NULL,

granularity => 'DEFAULT',

cascade => TRUE, -- including index stats

stattab => NULL,

statid => NULL,

force => TRUE,

statown => NULL);

END LOOP;

END;

SSH Configuration between servers

2010-11-26T11:03:00.000-08:00

SSH Configuration between linux servers without giving password

SSH can give you authenticated and encrypted connections to remote computers. If you set up keys you can make these connections without passwords.

I test this for RHEL5 64 bit OS

Step1: Generate a public and private key pair on the machine from where you want to login to other machines.

For SSH1:

# ssh-keygen -b 1024 -t rsa

For SSH2 (Recommended):

# ssh-keygen -b 1024 -t dsa

You will be prompted for a file in which the key and a passphrase will be saved.
You may press Enter through each of these prompts.
If you do so, the key generation program will assume that you wish to use the default file name of id_dsa and your private key will not be protected by a password.
Once this is done, you will see id_rsa and id_rsa.pub file in the .ssh directory in your home directory if you have not supplied a file name as I mentioned above.

Step 2: Copy the content of id_rsa.pub file to authorized_keys2 file available in .ssh directory of the remote host(s)

Copy the public keys (id_rsa.pub) to the remote host. That is the content of id_rsa.pub file to the file called authorized_keys2 available in .ssh directory of the host(s) where you wanted to connect without password.
Be aware that .ssh directory will be available in the home directory as hidden file so make sure it availability by ls -ltr command in the home directory.

# scp ~/.ssh/id_rsa.pub remote_host:/

Step 3: Login to the remote host and check if you already have authorized_keys2 file in .ssh dir. If this doesn’t exist, create it with the following commands.

# touch ~/.ssh/authorized_keys2

Step 4: On the remote host where you are in step 3, copy your public key to the authorized_keys2 file, with the following command.

# cat ~/ id_rsa.pub >> ~/.ssh/authorized_keys2

Step 5: You are set to use SSH authentication without password now. If you want you can delete or move id_rsa.pub file.

You can follow steps 2 – 5 for all other hosts where you want to have public key authentication.

Recompiling Invalid Objects

2010-11-06T20:52:00.000-07:00

STEP 1: Use the below query to find INVALID Objects

SELECT OWNER, OBJECT_NAME, OBJECT_TYPE, STATUS FROM DBA_OBJECTS WHERE STATUS='INVALID';
Export the result of the above query to xls.

STEP 2: Identify the Object Type of each invalid object.

STEP 3: If the object type is synonym

Use the below query for generating a query to create or replace invalid synonyms

SELECT 'CREATE OR REPLACE PUBLIC SYNONYM ' ||OBJECT_NAME ||' FOR '
||OBJECT_NAME||';' FROM DBA_OBJECTS where status='INVALID' AND OBJECT_TYPE='SYNONYM';

Use the below query for generating a query to grant privileges to synonyms

SELECT 'GRANT ALL ON ' ||OBJECT_NAME ||' TO PUBLIC||;' FROM DBA_OBJECTS where status='INVALID' AND OBJECT_TYPE='SYNONYM';

STEP 4: Copy and paste the result set of both the above queries in separate file

Now execute the first result set

CREATE OR REPLACE PUBLIC SYNONYM SYNONYM_NAME1 FOR OBJECT_NAME1;

CREATE OR REPLACE PUBLIC SYNONYM SYNONYM_NAME2 FOR OBJECT_NAME2;

CREATE OR REPLACE PUBLIC SYNONYM SYNONYM_NAME3 FOR OBJECT_NAME3;

CREATE OR REPLACE PUBLIC SYNONYM SYNONYM_NAME4 FOR OBJECT_NAME4;

CREATE OR REPLACE PUBLIC SYNONYM SYNONYM_NAME5 FOR OBJECT_NAME5;
CREATE OR REPLACE PUBLIC SYNONYM SYNONYM_NAME6 FOR OBJECT_NAME6;

CREATE OR REPLACE PUBLIC succeeded.
CREATE OR REPLACE PUBLIC succeeded.
CREATE OR REPLACE PUBLIC succeeded.
CREATE OR REPLACE PUBLIC succeeded.
CREATE OR REPLACE PUBLIC succeeded.
CREATE OR REPLACE PUBLIC succeeded.

Now execute the second result set

GRANT ALL ON SYNONYM_NAME1 TO PUBLIC;
GRANT ALL ON SYNONYM_NAME2 TO PUBLIC;
GRANT ALL ON SYNONYM_NAME3 TO PUBLIC;
GRANT ALL ON SYNONYM_NAME4 TO PUBLIC;
GRANT ALL ON SYNONYM_NAME5 TO PUBLIC;
GRANT ALL ON SYNONYM_NAME6 TO PUBLIC;

GRANT ALL succeeded.
GRANT ALL succeeded.
GRANT ALL succeeded.
GRANT ALL succeeded.
GRANT ALL succeeded.
GRANT ALL succeeded.

Use the below query to check whether the objects has been recompiled and the status is VALID

SELECT OWNER, OBJECT_NAME, OBJECT_TYPE, STATUS FROM DBA_OBJECTS
WHERE STATUS='VALID' AND OBJECT_TYPE='SYNONYM' AND OBJECT_NAME IN ('OBJECT_NAME1','OBJECT_NAME2','OBJECT_NAME3','OBJECT_NAME4',
'OBJECT_NAME5';

STEP 5: If the object type is not synonym

Recompile other objects as the show below

Uploading CSV in SQLLDR

2010-11-06T20:31:00.000-07:00

Normal CSV Upload

Step 1: Before loading data you need two files control file and csv file.
Step 2: Change the following in the control file

Path of the csv file.
Table name.
Column names for which the data has to be inserted.

Step 3: Execute the command sqlldr control=c:\ctrl3, log=c:\tablename.log userid=username/password@connectionname

Blob and Date Column CSV Upload via SQLLDR

Step 1: Before loading data you need two files control file and csv file .

This is different from normal upload since it has date field to be loaded and XML_BLOB field that need to loaded.

Prerequisite: Char_Set_ID will be given

Step 2: Export the Char_Set table (for the Char_Set_ID given) excluding the char_set_xml column as csv.

Step 3: Now export the char_set_xml column for each of the given Char_Set_ID as single dat file.

Step 4: Change the following in the csv file

In the XML_BLOB (char_Set_xml) column mention the path of the dat file XML_BLOB (char_Set_xml).
Also check for the date format of the date fields as mentioned in the control file.

Step 5: Change the following in the control file

Path of the csv file.
Table name.
Column names for which the data has to be inserted.
Give the correct format of the date fields. For Example insert_date Date "MM/DD/YYYY HH24:MI:SS",
XML_BLOB column has to be mentioned as below in the control file. For Example lob file filler char,CHAR_SET_XML LOBFILE(lob_file) TERMINATED BY EOF

Step 4: Execute the command sqlldr control=c:\ctrl, log=c:\tablename.log userid=suvin/welcome@connectionname

Control File Content

LOAD DATA

INFILE "c:\char_set.csv"
Append INTO TABLE CHAR_SET
FIELDS TERMINATED BY ','
(
CHAR_SET_ID,
CHAR_SET_ID,
CHAR_SET_NAME,
QUERY_TABLE_ID,
lob_file filler char,
CHAR_SET_XML LOBFILE(lob_file) TERMINATED BY EOF,
domain_name,
insert_user,
insert_date Date "MM/DD/YYYY HH24:MI:SS",
update_user,
update_date Date "MM/DD/YYYY HH24:MI:SS"
)

Sample

Microsoft Windows XP [Version 5.1.2600]

(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\;sqlldr userid=suvin/welcome@tmstest control=c:/CTRL4, log=tablename_04_NOV.log

SQL*Loader: Release 10.1.0.2.0 - Production on Wed Nov 3 17:13:44 2010
Copyright (c) 1982, 2004, Oracle. All rights reserved.

Commit point reached - logical record count 53

C:\Documents and Settings\sqlldr userid=suvin/welcome@tmsprod1 control=c:/CTRL4, log=tablename_04_NOV.log

SQL*Loader: Release 10.1.0.2.0 - Production on Wed Nov 3 17:16:01 2010
Copyright (c) 1982, 2004, Oracle. All rights reserved.

Commit point reached - logical record count 53

C:\Documents and Settings\;

How To Repair the Master Boot Record In Windows XP

2010-10-18T09:55:00.000-07:00

Repairing the master boot record on your Windows XP system is accomplished using the fixmbr command, available in Recovery Console. This is necessary when the master boot record has become corrupt due to a virus or some kind of damage.

Follow these easy steps to repair a damaged master boot record in Windows XP.

Difficulty: Easy

Time Required: Repairing the master boot record on a Windows XP system takes less than 15 minutes

Here's How:

Enter Windows XP Recovery Console.

When you reach the command prompt (detailed in Step 6 in the link above), type the following and then press Enter.

fixmbr

The fixmbr utility will write a master boot record to the hard drive that you're currently using to boot into Windows XP. This will repair any corruption or damage that the master boot record may have.

Take out the Windows XP CD, type exit and then press Enter to restart your PC.

Assuming that a corrupt master boot record was your only issue, Windows XP should now start normally

How To Recover Windows 7 Multi-boot Option with Windows XP

2010-06-28T10:25:00.001-07:00

Hello guys i think this is the common problem to all, as if you use Windows 7 as a second operating system with Windows Vista or Windows XP boot menu option automatically creates a new operating system option in the boot menu there. However, if you have Windows 7, and then try installing Windows XP, you will overwrite the MBR with one that does not recognize the code, the boot loader of Windows 7.
If any body of us are in the same situation and looking for the way to fix and get back Windows 7 option in boot menu then follow below simple steps.

1. Open a command prompt in the Xp/Vista operating( i mean in the older operating systems ) systems and run from the Windows 7 DVD the following command, Hear H is my drive letter replace yours:

H:\boot\ bootsect.exe /nt60 all

Just restart, now you should see the Windows 7 menu.

2. To restore the menu entry for your earlier version of Windows, open an elevated Command Prompt window and type this command:

bcdedit /create {ntldr} –H “Menu description goes here”

(or)

Download and Install EasyBCD on your Windows 7 to add boot entry for XP.

Launch the app and go to Add/Remove Entries. Under “Add an Entry” open the Windows tab and select the Type as “Windows NT/2k/XP/2k3”.

Give it a name like ‘Windows XP’ and click on ‘Add Entry’. Then select Save.

That’s it. Now restart you PC and you’ll be presented with two options, Windows 7 and Windows XP. Select the one which you want to work on.

Cheers:
Substitute your own description for the placeholder text, being sure to include the quotation marks. The next time you start your computer, the menus should appear as you intended.

killing rac sessions

2010-05-20T21:37:00.001-07:00

SET LINESIZE 100

COLUMN spid FORMAT A10

COLUMN username FORMAT A10

COLUMN program FORMAT A45

SELECT s.inst_id,

s.sid,

s.serial#,

p.spid,

s.username,

s.program

FROM gv$session s

JOIN gv$process p ON p.addr = s.paddr AND p.inst_id = s.inst_id

WHERE s.type != 'BACKGROUND';

The basic syntax for killing a session is shown below.

SQL> ALTER SYSTEM KILL SESSION 'sid,serial#';

In a RAC environment, you optionally specify the INST_ID, shown when querying the

GV$SESSION view. This allows you to kill a session on different RAC node.

SQL> ALTER SYSTEM KILL SESSION 'sid,serial#@inst_id';

In addition to the syntax described above, you can add the IMMEDIATE clause.

SQL> ALTER SYSTEM KILL SESSION 'sid,serial#' IMMEDIATE;

DISCONNECT SESSION

SQL> ALTER SYSTEM DISCONNECT SESSION 'sid,serial#' POST_TRANSACTION;

SQL> ALTER SYSTEM DISCONNECT SESSION 'sid,serial#' IMMEDIATE;

The POST_TRANSACTION and IMMEDIATE clauses can be used together, but the documentation

states that in this case the IMMEDIATE clause is ignored. In addition, the syntax diagram

suggests both clauses are optional, but in reality, one or both must be specified or you

receive an error.

SQL> alter system disconnect session '30,7';

alter system disconnect session '30,7'

*

ERROR at line 1:

ORA-02000: missing POST_TRANSACTION or IMMEDIATE keyword

The Windows Approach

To kill the session on the Windows operating system, first identify the session, then

substitute the relevant SID and SPID values into the following command issued from the

command line.

C:> orakill ORACLE_SID spid

The UNIX Approach

To kill the session on UNIX or Linux operating systems, first identify the session, then substitute the relevant SPID into the following command.

% kill spid

If after a few minutes the process hasn't stopped, terminate the session using the following.

% kill -9 spid

If in doubt check that the SPID matches the UNIX PROCESSID shown using.

% ps -ef
grep ora

----------------Session Waits--------------------

SQL> select event, seconds_in_wait, sid from v$session_wait where sid in (10,14);

Export and Import Dump

2010-05-20T21:36:00.001-07:00

------------Importing Full Dump File-------------

If you want to Import all the objects in a dump file then you can type the

following command.

$impdp hr/hr DUMPFILE=dpump_dir1:expfull.dmp FULL=y

LOGFILE=dpump_dir2:full_imp.log

This example imports everything from the expfull.dmp dump file. In this example,

a DIRECTORY parameter is not provided. Therefore, a directory object must be provided

on both the DUMPFILE parameter and the LOGFILE parameter

-------------Importing Objects of One Schema to another Schema---------------

The following example loads all tables belonging to hr schema to scott schema

$impdp SYSTEM/password DIRECTORY=dpump_dir1 DUMPFILE=hr.dmp

REMAP_SCHEMA=hr:scott

If SCOTT account exist in the database then hr objects will be loaded into scott schema.

If scott account does not exist, then Import Utility will create the SCOTT account with

an unusable password because, the dump file was exported by the user SYSTEM and imported

by the user SYSTEM who has DBA privileges.

-------------Loading Objects of one Tablespace to another Tablespace--------------------

You can use remap_tablespace option to import objects of one tablespace to another

tablespace by giving the command

$impdp SYSTEM/password DIRECTORY=dpump_dir1 DUMPFILE=hr.dmp

REMAP_TABLESPACE=users:sales

The above example loads tables, stored in users tablespace, in the sales tablespace.

---------Generating SQL File containing DDL commands using Data Pump Import---------

You can generate SQL file which contains all the DDL commands which Import would have

executed if you actually run Import utility

The following is an example of using the SQLFILE parameter.

$ impdp hr/hr DIRECTORY=dpump_dir1 DUMPFILE=expfull.dmp

SQLFILE=dpump_dir2:expfull.sql

A SQL file named expfull.sql is written to dpump_dir2.

-----------------------Importing objects of only a Particular Schema---------------------

$impdp hr/hr SCHEMAS=hr,oe DIRECTORY=dpump_dir1 LOGFILE=schemas.log

DUMPFILE=expdat.dmp

-----------------Importing Only Particular Tables---------------

The following example shows a simple use of the TABLES parameter to import only the employees and jobs tables from the expfull.dmp file. You can create the expfull.dmp dump file used in this example by running the example provided for the Full Database Export in Previous Topic.

$impdp hr/hr DIRECTORY=dpump_dir1 DUMPFILE=expfull.dmp TABLES=employees,jobs

This will import only employees and jobs tables from the DUMPFILE

RMAN IMPLEMENTATION in Oracle 9i,10g,11g -- Create Catalog Repository

2010-03-13T04:31:00.000-08:00

Target Database Name: Test
Catalog Database Name: Catdb

SQL> SELECT FILE_NAME FROM DBA_DATA_FILES;

FILE_NAME                                                                       
--------------------------------------------------------------------------------
E:\ORACLE\PRODUCT\10.2.0\ORADATA\CATDB\DATAFILE\O1_MF_USERS_5QKOR4NW_.DBF       
E:\ORACLE\PRODUCT\10.2.0\ORADATA\CATDB\DATAFILE\O1_MF_SYSAUX_5QKOR41T_.DBF      
E:\ORACLE\PRODUCT\10.2.0\ORADATA\CATDB\DATAFILE\O1_MF_UNDOTBS1_5QKOR4H0_.DBF    
E:\ORACLE\PRODUCT\10.2.0\ORADATA\CATDB\DATAFILE\O1_MF_SYSTEM_5QKOR3S8_.DBF      

Steps 1: Create Repository Tablespace 

SQL> CREATE TABLESPACE RMAN
  2  DATAFILE 'E:\ORACLE\PRODUCT\10.2.0\ORADATA\CATDB\DATAFILE\RMAN.DBF'
  3  SIZE 200M REUSE AUTOEXTEND ON
  4  EXTENT MANAGEMENT LOCAL
  5  SEGMENT SPACE MANAGEMENT AUTO;

Tablespace created.

SQL> SELECT TABLESPACE_NAME FROM DBA_TABLESPACES;

TABLESPACE_NAME                                                                 
------------------------------                                                  
SYSTEM                                                                          
UNDOTBS1                                                                        
SYSAUX                                                                          
TEMP                                                                            
USERS                                                                           
RMAN                                                                            

6 rows selected.

Steps 2: Create Repository Schema

SQL> CREATE USER RMAN IDENTIFIED BY RMAN
  2  TEMPORARY TABLESPACE TEMP
  3  DEFAULT TABLESPACE RMAN
  4  QUOTA UNLIMITED ON RMAN;

User created.

Steps 3: Grant Privileges to user RMAN.

SQL> GRANT RECOVERY_CATALOG_OWNER TO RMAN;

Grant succeeded.

SQL> GRANT CONNECT,RESOURCE TO RMAN;

Grant succeeded.


Steps 4: Creating the Recovery Catalog

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\administrator>RMAN CATALOG RMAN@CATDB

Recovery Manager: Release 10.2.0.1.0 - Production on Mon Feb 15 11:34:31 2010

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

recovery catalog database Password:
connected to recovery catalog database

RMAN> CREATE CATALOG;

recovery catalog created

RMAN> Exit
Recovery Manager complete

Steps 5: Let the Catalog Database keep information in its control file for 30 days. (Optional)


SQL> SHOW PARAMETER CONTROL_FILE_RECORD_KEEP_TIME

NAME                                 TYPE        VALUE                          
------------------------------------ ----------- ------------------------------ 
control_file_record_keep_time        integer     7

SQL> ALTER SYSTEM SET CONTROL_FILE_RECORD_KEEP_TIME=30;

System altered.

SQL> SHOW PARAMETER CONTROL_FILE_RECORD_KEEP_TIME

NAME                                 TYPE        VALUE                          
------------------------------------ ----------- ------------------------------ 
control_file_record_keep_time        integer     30                             
SQL> DISC
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> EXIT

Steps 6: Setup Target Database (Register Database)

EACH DATABASE TO BE BACKED UP BY RMAN MUST BE REGISTERED.

C:\Documents and Settings\administrator>RMAN CATALOG=RMAN/RMAN@CATDB TARGET=SYS/
TEST@TEST

Recovery Manager: Release 10.2.0.1.0 - Production on Mon Feb 15 11:54:28 2010

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

connected to target database: TEST (DBID=1969872048)
connected to recovery catalog database

RMAN> REGISTER DATABASE;

database registered in recovery catalog
starting full resync of recovery catalog
full resync complete

RMAN> LIST INCARNATION;


List of Database Incarnations
DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
------- ------- -------- ---------------- --- ---------- ----------
321     328     TEST     1969872048       PARENT  1          30-AUG-05
321     322     TEST     1969872048       CURRENT 534907     25-NOV-08

RMAN>


------------------------Backup in RMAN-----------------------


Recovery Manager: Release 10.2.0.1.0 - Production on Mon Feb 15 13:38:42 2010

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

RMAN> connect target sys@synapse

target database Password:
connected to target database: SYNAPSE (DBID=3340585066)

RMAN> backup database;

Starting backup at 15-FEB-10
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=129 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00002 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAPSE\UNDOTBS01
.DBF
input datafile fno=00009 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAPSE\PORTING01
.DBF
input datafile fno=00001 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAPSE\SYSTEM01.
DBF
input datafile fno=00007 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAPSE\VI1.DBF
input datafile fno=00003 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAPSE\SYSAUX01.
DBF
input datafile fno=00004 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAPSE\USERS01.D
BF
input datafile fno=00006 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAPSE\ORASER01.
DBF
input datafile fno=00005 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAPSE\EXAMPLE01
.DBF
input datafile fno=00008 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAPSE\ORASYNAPS
E.DBF
channel ORA_DISK_1: starting piece 1 at 15-FEB-10
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/15/2010 13:43:
35
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 2147483648 limit
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 15-FEB-10
channel ORA_DISK_1: finished piece 1 at 15-FEB-10
piece handle=E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SYNAPSE\BACKUPSET\2010
_02_15\O1_MF_NCSNF_TAG20100215T133909_5QL0KL06_.BKP tag=TAG20100215T133909 comme
nt=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:06
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================

RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/15/2010 13:43:
35
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 2147483648 limit

RMAN> delete backup of database;

using channel ORA_DISK_1

RMAN> backup database;

Starting backup at 15-FEB-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00002 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAPSE\UNDOTBS01
.DBF
input datafile fno=00009 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAPSE\PORTING01
.DBF
input datafile fno=00001 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAPSE\SYSTEM01.
DBF
input datafile fno=00007 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAPSE\VI1.DBF
input datafile fno=00003 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAPSE\SYSAUX01.
DBF
input datafile fno=00004 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAPSE\USERS01.D
BF
input datafile fno=00006 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAPSE\ORASER01.
DBF
input datafile fno=00005 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAPSE\EXAMPLE01
.DBF
input datafile fno=00008 name=E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAPSE\ORASYNAPS
E.DBF
channel ORA_DISK_1: starting piece 1 at 15-FEB-10
channel ORA_DISK_1: finished piece 1 at 15-FEB-10
piece handle=E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SYNAPSE\BACKUPSET\2010
_02_15\O1_MF_NNNDF_TAG20100215T141344_5QL2B2OW_.BKP tag=TAG20100215T141344 comme
nt=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:05:36
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 15-FEB-10
channel ORA_DISK_1: finished piece 1 at 15-FEB-10
piece handle=E:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SYNAPSE\BACKUPSET\2010
_02_15\O1_MF_NCSNF_TAG20100215T141344_5QL2NLDB_.BKP tag=TAG20100215T141344 comme
nt=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 15-FEB-10

RMAN>

Manual Database Creation in Oracle 10g

2010-02-21T06:04:00.000-08:00

Manual Creation of database in windows with oracle 10g

STEP: 1

Now open a command prompt and set oracle SID as set oracle_sid=mandb

--------------------------------------------------------------------------------
C:\Documents and Settings\administrator.SUVIN>set oracle_sid=mandb
--------------------------------------------------------------------------------

STEP: 2

Start a windows service with internal password oradim –new –sid
intpwd is the syntax.

--------------------------------------------------------------------------------
C:\Documents and Settings\administrator.SUVIN>oradim -new -sid mandb -intpwd mandb
Instance created.
--------------------------------------------------------------------------------

STEP: 3

Create a directory called mandb. In my case I created it in d:\ drive
D:\mandb\data
D:\mandb\redo
D:\mandb\control
D:\mandb\bdump
D:\mandb\cdump
D:\mandb\udump
D:\mandb\pfile
D:\mandb\spfile
D:\mandb\temp

(Note: all my parameter files and .sql file that are going to discuss following are based on my
location, you can change the location according to yours)

STEP: 4

Now create a pfile for the database namely initmandb.ora in D:\mandb\pfile
Give the necessary parameter in the pfile.I gave thelease amount of parameters.

----Contents of initmandb.ora-----

db_name=mandb
instance_name=mandb

db_block_size=8192
db_cache_size=25165824

background_dump_dest=D:\mandb\bdump
core_dump_dest=D:\mandb\cdump
user_dump_dest=D:\mandb\udump

control_files=("D:\mandb\control\control01.ctl", "D:\mandb\control\CONTROL02.ctl",
"D:\mandb\control\CONTROL03.ctl")

shared_pool_size=50331648

undo_management=AUTO

STEP: 5

Now type following in your current command prompt sqlplus/nolog and in sql
prompt type conn sys/mandb as sysdba then you should see that you
are connected to an idle instance

--------------------------------------------------------------------------------
C:\Documents and Settings\administrator.SUVIN>sqlplus/nolog

SQL*Plus: Release 10.2.0.1.0 - Production on Mon Feb 1 15:18:36 2010

Copyright (c) 1982, 2005, Oracle. All rights reserved.

SQL> conn sys/mandb as sysdba
Connected to an idle instance.
SQL>
--------------------------------------------------------------------------------

STEP: 6

Now start the instance in nomount mode as,

startup nomount pfile=D:\mandb\pfile\initmandb.ora

why are you starting the database in nomount mode ?
The reason is still we are not created control files. “An instance would be started in
the NOMOUNT stage only during database creation or the re-creation of control files.

------------------------------------------------------------------------------------
SQL> startup nomount pfile=D:\mandb\pfile\initmandb.ora
ORACLE instance started.

Total System Global Area 109051904 bytes
Fixed Size 1247540 bytes
Variable Size 75499212 bytes
Database Buffers 25165824 bytes
Redo Buffers 7139328 bytes
SQL>

------------------------------------------------------------------------------------

STEP: 7

Now create the database by the following command...

CREATE DATABASE mandb
LOGFILE
GROUP 1('D:\mandb\redo\redo01.log') SIZE 50M,
GROUP 2('D:\mandb\redo\redo02.log') SIZE 50M,
GROUP 3('D:\mandb\redo\redo03.log') SIZE 50M
DATAFILE 'D:\mandb\data\system01.dbf' SIZE 200M autoextend on
SYSAUX DATAFILE 'D:\mandb\data\sysaux01.dbf' SIZE 200M
UNDO TABLESPACE UNDOTBS
DATAFILE 'D:\mandb\data\UNDOTBS.dbf' SIZE 100M
default temporary tablespace TEMP
tempfile 'D:\mandb\temp\temp_01_db01.dbf' SIZE 50M
extent management local uniform size 128k
;

Run the script in the SQL prompt
--------------------------------------------------------------------------------------
SQL> CREATE DATABASE mandb
2 LOGFILE
3 GROUP 1('D:\mandb\redo\redo01.log') SIZE 50M,
4 GROUP 2('D:\mandb\redo\redo02.log') SIZE 50M,
5 GROUP 3('D:\mandb\redo\redo03.log') SIZE 50M
6 DATAFILE 'D:\mandb\data\system01.dbf' SIZE 200M autoextend on
7 SYSAUX DATAFILE 'D:\mandb\data\sysaux01.dbf' SIZE 200M
8 UNDO TABLESPACE UNDOTBS
9 DATAFILE 'D:\mandb\data\UNDOTBS.dbf' SIZE 100M
10 default temporary tablespace TEMP
11 tempfile 'D:\mandb\temp\temp_01_db01.dbf' SIZE 50M
12 extent management local uniform size 128k
13 ;

Database created.

SQL>

once you run this you can see the control files, redo log file, Alert log file, .dbf files and .trc
(Background Trace files & User Trace files) files are created in D:\mandb\ folder.

--------------------------------------------------------------------------------------

STEP: 8

Now you can shutdown the database using shutdown command.

---------------------------------
Database dismounted.
ORACLE instance shut down.
SQL>
---------------------------------

Once the database shutdown reboot your PC

STEP: 9

Connect again as sysdba to default database

---------------------------------
sqlplus/nolog,
SQL>conn sys/mandb as sysdba
---------------------------------

check which database you are in by using the following command

show parameter service_name

STEP: 10

Now place the pfile initmandb.ora in this lacation
D:\Oracle\product\10.2.0\db_1\database\

Then try to connect like this

SQL>conn sys/mandb as sysdba

and startup your database.

You dont have to mention your pfile in th startup command since you have placed it in the
default pfile location

D:\Oracle\product\10.2.0\db_1\database\

------------------------------------------------------------------

C:\Documents and Settings\administrator.SUVIN>sqlplus

SQL*Plus: Release 10.2.0.1.0 - Production on Mon Feb 1 15:48:15 2010

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Enter user-name: sys/mandb as sysdba
Connected to an idle instance.

SQL> startup
ORACLE instance started.

Total System Global Area 109051904 bytes
Fixed Size 1247540 bytes
Variable Size 75499212 bytes
Database Buffers 25165824 bytes
Redo Buffers 7139328 bytes
Database mounted.
Database opened.
SQL>

------------------------------------------------------------------

STEP: 11

Execute catalog.sql SQL>@d:\ORANT\rdbms\admin\catalog.sql
Execute catproc.sql SQL>@d:\ORANT\rdbms\admin\catproc.sql

STEP: 12

Now you need to edit the following files

D:\Oracle\product\10.2.0\db_1\NETWORK\ADMIN\tnsnames.ora
D:\Oracle\product\10.2.0\db_1\NETWORK\ADMIN\listener.ora

Here are the files that I used…you can change those accordingly
# TNSNAMES.ORA Network Configuration File: D:\ORANT\network\admin\tnsnames.ora
# Generated by Oracle configuration tools.
SURANGA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = NEWP4)(PORT = 1521))
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = suranga)
)
)
mandb =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = inal075)(PORT = 1521))
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = mandb)
)
)
INST1_HTTP =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = NEWP4)(PORT = 1521))
)
(CONNECT_DATA =
(SERVER = SHARED)
(SERVICE_NAME = MODOSE)
(PRESENTATION = http://HRService)
)
)
6
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
)
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
)
)

# LISTENER.ORA Network Configuration File: D:\ORANT\network\admin\listener.ora
# Generated by Oracle configuration tools.
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = NEWP4)(PORT = 1521))
)
)
)
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = D:\ORANT)
(PROGRAM = extproc)
)
(SID_DESC =
(GLOBAL_DBNAME = suranga)
(ORACLE_HOME = D:\ORANT)
(SID_NAME = suranga)
)
(SID_DESC =
(GLOBAL_DBNAME = mandb)
(ORACLE_HOME = D:\mandb)
(SID_NAME = mandb)
)
)
Now start configuring tns Service Name in Client System from where you need to
access the Oracle 10g Enterprise Server
Open Net Manager
Start->Programs->Oracle10gHome->Configuration and Migration Tools->Net Manager

Create a User in mandb Database and test the connection in Net Manager
by changing the login.

How to recover dropped table in Oracle 10g using flashback feature

2010-02-16T21:38:00.000-08:00

SQL*Plus: Release 10.1.0.2.0 - Production on Wed Feb 17 11:07:27 2010

Copyright (c) 1982, 2004, Oracle. All rights reserved.

Enter user-name: suvin@test
Enter password:

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
STEP 1 : WE ARE GOING TO DROP TABLE TABLE2.
SQL> desc table2;
Name Null? Type
----------------------------------------- -------- ----------------------------
ID NUMBER(3)

SQL> select * from table2;

ID
----------
2
2
3
4
4
5

6 rows selected.

STEP 2 : NOW DROP THE TABLE.

SQL> drop table table2;

Table dropped.

SQL> show user
USER is "SUVIN"

SQL> select * from table2;
select * from table2
*
ERROR at line 1:
ORA-00942: table or view does not exist

Now We are confirmed that table has been dropped.

SQL> show user
USER is "SUVIN"

STEP 2 : CHECK WHEATHER THE TABLE IS AVAILABLE IN RECYCLEBIN.

SQL> select object_name,original_name from user_recyclebin;

OBJECT_NAME ORIGINAL_NAME
------------------------------ --------------------------------
BIN$T0xRBK9YSomiRRmhwn/xPA==$0 TABLE2

STEP 2 : USE THIS FLASHBACK COMMAND TO RECOVER THE DROPPED TABLE.

SQL> flashback table table2 to before drop;

Flashback complete.

SQL> select * from table2;

ID
----------
2
2
3
4
4
5

6 rows selected.

SQL> disc
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> exit

IF THE DROPPED TABLE IS NOT IN RECYCLEBIN THEN YOU CANT USE FLASHBACK FEATURE TO RECOVER THE TABLE.

Else, you'll need a Backup or a dump to restore your Table.

For instance, by duplicating your database elsewhere and get back the Table by DataPump (expdp/impdp).

Exporting and Importing Tables in Oracle 10g

2010-02-10T03:02:00.000-08:00

SQL> $exp porting@test file=c:/activity1.dmp log=c:/activity1.log tables=activity_master

Export: Release 9.2.0.1.0 - Production on Wed Feb 10 16:20:12 2010

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Password:

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set

About to export specified tables via Conventional Path ...
. . exporting table ACTIVITY_MASTER 13658 rows exported
Export terminated successfully without warnings.

SQL> conn
Enter user-name: raja@test
Enter password:
Connected.

SQL> drop table activity_master;
drop table activity_master
*
ERROR at line 1:
ORA-02449: unique/primary keys in table referenced by foreign keys

SQL> drop table activity_master cascade constraints;

Table dropped.

SQL> $imp raja@test file=c:/activity1.dmp log=c:/activity1.log tables=activity_master fromuser=porting touser=raja;

Import: Release 9.2.0.1.0 - Production on Wed Feb 10 16:33:14 2010

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Password:

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options

Export file created by EXPORT:V09.02.00 via conventional path

Warning: the objects were exported by PORTING, not by you

import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
. . importing table "ACTIVITY_MASTER" 13658 rows imported
About to enable constraints...
Import terminated successfully without warnings.

SQL>

Oracle 10g Express Edition Installation on Windows and connecting to sys schema

2010-01-28T22:55:00.000-08:00

Download Oracle Database 10g Express Edition here
http://www.oracle.com/technology/software/products/database/xe/index.html

Download these files for Windows
OracleXEUniv.exe
OracleXEClient.exe

Oracle 10g export - Export dump in 10g Real time procedure

2009-12-28T02:44:00.000-08:00

User Suvin Already have schema full of data which has to be exported.

Enter user-name: sys@test as sysdba
Enter password: <--(Password for User sys is given here)

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options

SQL> create or replace directory export_dest as 'D:\export\';

Directory created.

SQL> grant read,write on directory export_dest to suvin;

Grant succeeded.

SQL> grant read,write on directory export_dest to jretail;

Grant succeeded.

SQL> $expdp suvin@test directory=export_dest schemas=suvin dumpfile=jr.dmp logfile=jr.log;

Export: Release 10.2.0.1.0 - Production on Monday, 28 December, 2009 16:04:53

Copyright (c) 2003, 2005, Oracle. All rights reserved.
Password: <--(Password for User Suvin is given here)

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options
Starting "JRETAIL"."SYS_EXPORT_SCHEMA_01": jretail/********@test directory=expo
rt_dest dumpfile=jr.dmp
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 56.62 MB
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/COMMENT
Processing object type SCHEMA_EXPORT/FUNCTION/FUNCTION
Processing object type SCHEMA_EXPORT/PROCEDURE/PROCEDURE
Processing object type SCHEMA_EXPORT/FUNCTION/ALTER_FUNCTION
Processing object type SCHEMA_EXPORT/PROCEDURE/ALTER_PROCEDURE
Processing object type SCHEMA_EXPORT/VIEW/VIEW
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/FUNCTIONAL_AND_BITMAP/INDEX
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/FUNCTIONAL_AND_BITMA
P/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
. . exported "SUVIN"."POSTING" 7.871 MB 114815 rows
. . exported "SUVIN"."STOCKLEDGER" 6.185 MB 80000 rows
. . exported "SUVIN"."TAGHEADER" 4.956 MB 43622 rows
. . exported "SUVIN"."SALEITEMDETAIL" 3.865 MB 33755 rows
. . exported "SUVIN"."MAKINGWASTAGECHARGEDETAIL" 2.748 MB 62761 rows
. . exported "SUVIN"."SALEHEADER" 2.450 MB 22871 rows
. . exported "SUVIN"."SALEPAYMENTGENERAL" 1.102 MB 24014 rows
. . exported "SUVIN"."SALETAXSURCHARGEDETAIL" 1.365 MB 36806 rows
. . exported "SUVIN"."ITEMMASTERHEADER" 523.8 KB 3977 rows
. . exported "SUVIN"."VOUCHERDETAIL" 788.4 KB 10151 rows
. . exported "SUVIN"."CHITRECEIPTHEADER" 430.0 KB 6663 rows
. . exported "SUVIN"."STOCKAUDITINGTEMP" 574.3 KB 11368 rows
. . exported "SUVIN"."TEMP_JSTOCK" 551.4 KB 9785 rows
. . exported "SUVIN"."CHITMEMBERINSTALLMENTDETAIL" 354.9 KB 7445 rows
. . exported "SUVIN"."CHITRECEIPTDETAIL" 306.8 KB 6664 rows
. . exported "SUVIN"."PARTYLOCATIONDETAIL" 308.0 KB 2962 rows
. . exported "SUVIN"."ACCOUNTMASTER" 255.6 KB 3401 rows
. . exported "SUVIN"."PARTYMASTERHEADER" 250.3 KB 2946 rows
. . exported "SUVIN"."SALEORDERHEADER" 154 KB 1016 rows
. . exported "SUVIN"."TAGSTONEDETAIL" 198.3 KB 3326 rows
. . exported "SUVIN"."VOUCHERHEADER" 231.8 KB 4149 rows
. . exported "SUVIN"."PURCHASEHEADER" 139.9 KB 969 rows
. . exported "SUVIN"."SALEORDERDETAIL" 112.0 KB 1065 rows
. . exported "SUVIN"."BILLWISEADJUSTMENT" 125.3 KB 1188 rows
. . exported "SUVIN"."CHITMEMBER" 85.26 KB 870 rows
. . exported "SUVIN"."PURCHASEITEMDETAIL" 97.75 KB 1020 rows
. . exported "SUVIN"."STOCKAUDITDETAIL" 144.1 KB 3227 rows
. . exported "SUVIN"."TEMP_VITABLE" 132.3 KB 1226 rows
. . exported "SUVIN"."ACCOUNTOPENING" 89.46 KB 4543 rows
. . exported "SUVIN"."BILLWISEADJUSTMENTSCHEDULE" 50.39 KB 1188 rows
. . exported "SUVIN"."FORMATDETAIL" 76.24 KB 1267 rows
. . exported "SUVIN"."ITEMMASTERATTRIBUTESDETAIL" 63.53 KB 1571 rows
. . exported "SUVIN"."MAKINGWASTAGECHARGEHEADER" 88.5 KB 3306 rows
. . exported "SUVIN"."PRICEREVISIONDETAIL" 62.84 KB 1800 rows
. . exported "SUVIN"."PURCHASEPAYMENTGENERAL" 33.67 KB 577 rows
. . exported "SUVIN"."PURTAXSURCHARGEDETAIL" 46.18 KB 1003 rows
. . exported "SUVIN"."RATEITEMDETAIL" 60.92 KB 898 rows
. . exported "SUVIN"."SALEITEMSTONEDETAIL" 69.67 KB 1057 rows
. . exported "SUVIN"."SALEORDERPAYMENTGENERAL" 63.22 KB 1017 rows
. . exported "SUVIN"."SMITHRECEIPTHEADER" 34.41 KB 285 rows
. . exported "SUVIN"."SMITHRECEIPTITEMDETAIL" 33.70 KB 315 rows
. . exported "SUVIN"."AGEINGMASTER" 7.468 KB 6 rows
. . exported "SUVIN"."APPLICATIONCONFIGURATION" 11.53 KB 2 rows
. . exported "SUVIN"."BUDGETMASTERDETAIL" 8.187 KB 4 rows
. . exported "SUVIN"."BUDGETMASTERHEADER" 8.398 KB 1 rows
. . exported "SUVIN"."CALENDARMASTER" 8.039 KB 4 rows
. . exported "SUVIN"."CHITMASTER" 11.31 KB 10 rows
. . exported "SUVIN"."COMPANYMASTER" 13.10 KB 2 rows
. . exported "SUVIN"."DAYCLOSURE" 19.60 KB 454 rows
. . exported "SUVIN"."DIAMONDRATEDETAIL" 9.281 KB 2 rows
. . exported "SUVIN"."DIAMONDRATEMASTER" 7.796 KB 1 rows
. . exported "SUVIN"."EMPLOYEEMASTERHEADER" 24.80 KB 80 rows
. . exported "SUVIN"."EMPLOYEEROLEDETAILS" 13.56 KB 103 rows
. . exported "SUVIN"."FORMATHEADER" 10.26 KB 36 rows
. . exported "SUVIN"."INDENTDETAIL" 8.5 KB 2 rows
. . exported "SUVIN"."INDENTHEADER" 8.296 KB 1 rows
. . exported "SUVIN"."ITEMCATEGORYMASTER" 10.04 KB 5 rows
. . exported "SUVIN"."ITEMTYPEATTRIBUTESDETAIL" 9.828 KB 2 rows
. . exported "SUVIN"."ITEMTYPEMASTERHEADER" 10.07 KB 27 rows
. . exported "SUVIN"."LEDGERGROUP" 8.343 KB 48 rows
. . exported "SUVIN"."LOCATIONMASTER" 12.53 KB 2 rows
. . exported "SUVIN"."LOOKUPCODEMASTER" 27.70 KB 358 rows
. . exported "SUVIN"."LOOKUPTYPEMASTER" 10.32 KB 42 rows
. . exported "SUVIN"."LOTCHARGESDETAIL" 7.414 KB 1 rows
. . exported "SUVIN"."LOTHEADER" 11.17 KB 1 rows
. . exported "SUVIN"."MENUMASTER" 21.07 KB 184 rows
. . exported "SUVIN"."OBJECTMASTER" 21.25 KB 296 rows
. . exported "SUVIN"."OTHERCHARGEDETAIL" 9.015 KB 9 rows
. . exported "SUVIN"."OTHERCHARGEHEADER" 7.367 KB 3 rows
. . exported "SUVIN"."PARTYCOMMUNICATIONDETAIL" 15.13 KB 144 rows
. . exported "SUVIN"."PARTYLOCATIONCONTACTLINES" 15.26 KB 120 rows
. . exported "SUVIN"."PRICEREVISIONHEADER" 15.35 KB 138 rows
. . exported "SUVIN"."PURCHASEITEMSTONEDETAIL" 10.80 KB 4 rows
. . exported "SUVIN"."PURCHASEORDER" 12.25 KB 2 rows
. . exported "SUVIN"."PURCHASEORDERDETAIL" 12.95 KB 2 rows
. . exported "SUVIN"."PURCHASEPAYMENTDUESCHEDULE" 25.38 KB 377 rows
. . exported "SUVIN"."PURCHASEQUOTATION" 15.57 KB 1 rows
. . exported "SUVIN"."PURCHASEQUOTATIONDETAIL" 13.23 KB 1 rows
. . exported "SUVIN"."PURCHASERETURNDETAIL" 17.13 KB 36 rows
. . exported "SUVIN"."PURCHASERETURNHEADER" 19.62 KB 31 rows
. . exported "SUVIN"."PURORDTAXSURCHARGEDETAIL" 9.781 KB 2 rows
. . exported "SUVIN"."PURQUOTTAXSURCHARGEDETAIL" 9.75 KB 1 rows
. . exported "SUVIN"."PURRETTAXSURCHARGEDETAIL" 10.41 KB 19 rows
. . exported "SUVIN"."RATEFORMULAMASTER" 10.24 KB 3 rows
. . exported "SUVIN"."RATEMASTER" 19.47 KB 338 rows
. . exported "SUVIN"."ROLEMENUMASTER" 20.15 KB 526 rows
. . exported "SUVIN"."ROLEPRIVILAGEMASTER" 8.992 KB 31 rows
. . exported "SUVIN"."SALEORDERITEMSTONEDETAIL" 11.16 KB 4 rows
. . exported "SUVIN"."SALEORDERSAMPLEDETAIL" 12.60 KB 57 rows
. . exported "SUVIN"."SALEOTHERCHARGEDETAIL" 8.546 KB 4 rows
. . exported "SUVIN"."SALEPAYMENTDUESCHEDULE" 26.72 KB 406 rows
. . exported "SUVIN"."SALEQUOTATIONDETAIL" 22.77 KB 66 rows
. . exported "SUVIN"."SALEQUOTOTHERCHARGEDETAIL" 8.789 KB 11 rows
. . exported "SUVIN"."SECTIONISSUEHEADER" 8.398 KB 1 rows
. . exported "SUVIN"."SECTIONISSUEITEMDETAIL" 9.218 KB 1 rows
. . exported "SUVIN"."SIDETAIL" 20.53 KB 243 rows
. . exported "SUVIN"."SIHEADER" 25.71 KB 240 rows
. . exported "SUVIN"."SMITHCHARGEDETAIL" 9.062 KB 6 rows
. . exported "SUVIN"."SMITHCHARGEHEADER" 7.117 KB 3 rows
. . exported "SUVIN"."SMITHRECEIPTPAYMENTDUESCHEDULE" 14.67 KB 143 rows
. . exported "SUVIN"."SMITHRECEIPTPAYMENTGENERAL" 15.46 KB 137 rows
. . exported "SUVIN"."STOCKAUDITHEADER" 8.195 KB 4 rows
. . exported "SUVIN"."TAB1" 5.25 KB 4 rows
. . exported "SUVIN"."TAB2" 5.25 KB 4 rows
. . exported "SUVIN"."TAGCHARGEDETAIL" 7.773 KB 1 rows
. . exported "SUVIN"."TAXMASTER" 10.22 KB 8 rows
. . exported "SUVIN"."TDSCERTIFICATEDETAIL" 12.67 KB 30 rows
. . exported "SUVIN"."TDSCERTIFICATEHEADER" 9.171 KB 2 rows
. . exported "SUVIN"."TRANSACTIONORDER" 7.117 KB 10 rows
. . exported "SUVIN"."UOMMASTER" 8.015 KB 4 rows
. . exported "SUVIN"."VOUCHERTEMPLATEDETAIL" 9.601 KB 16 rows
. . exported "SUVIN"."VOUCHERTEMPLATEHEADER" 8.5 KB 4 rows
. . exported "SUVIN"."VOUCHERTYPE" 8.125 KB 8 rows
. . exported "SUVIN"."CALENDARMONTHDETAIL" 0 KB 0 rows
. . exported "SUVIN"."GAIDETAIL" 0 KB 0 rows
. . exported "SUVIN"."GAIHEADER" 0 KB 0 rows
. . exported "SUVIN"."GAIITEMSTONEDETAIL" 0 KB 0 rows
. . exported "SUVIN"."GRADETAIL" 0 KB 0 rows
. . exported "SUVIN"."GRAHEADER" 0 KB 0 rows
. . exported "SUVIN"."GRAITEMSTONEDETAIL" 0 KB 0 rows
. . exported "SUVIN"."GRTDETAIL" 0 KB 0 rows
. . exported "SUVIN"."GRTHEADER" 0 KB 0 rows
. . exported "SUVIN"."GRTITEMSTONEDETAIL" 0 KB 0 rows
. . exported "SUVIN"."GTODETAIL" 0 KB 0 rows
. . exported "SUVIN"."GTOHEADER" 0 KB 0 rows
. . exported "SUVIN"."GTOITEMSTONEDETAIL" 0 KB 0 rows
. . exported "SUVIN"."NARRATIONMASTER" 0 KB 0 rows
. . exported "SUVIN"."PARTYRELATIONSDETAIL" 0 KB 0 rows
. . exported "SUVIN"."POSTINGTEMP" 0 KB 0 rows
. . exported "SUVIN"."POSTINGTEMP1" 0 KB 0 rows
. . exported "SUVIN"."PURCHASEORDERITEMSTONEDETAIL" 0 KB 0 rows
. . exported "SUVIN"."PURCHASEPAYMENTMETAL" 0 KB 0 rows
. . exported "SUVIN"."PURCHASEQUOTATIONITEMSTONEDTL" 0 KB 0 rows
. . exported "SUVIN"."PURCHASERETURNITEMSTONEDTL" 0 KB 0 rows
. . exported "SUVIN"."PURCHASERETURNPAYMENTGENERAL" 0 KB 0 rows
. . exported "SUVIN"."PURCHASERETURNPAYMENTMETAL" 0 KB 0 rows
. . exported "SUVIN"."PURSTOCKLEDGER" 0 KB 0 rows
. . exported "SUVIN"."RATEHISTORYDETAILS" 0 KB 0 rows
. . exported "SUVIN"."RATEHISTORYMASTER" 0 KB 0 rows
. . exported "SUVIN"."REPAIRDELIVERYHEADER" 0 KB 0 rows
. . exported "SUVIN"."REPAIRDELIVERYPAYMENTGENRAL" 0 KB 0 rows
. . exported "SUVIN"."REPAIRORDERHEADER" 0 KB 0 rows
. . exported "SUVIN"."RETAGGING" 0 KB 0 rows
. . exported "SUVIN"."SALEHEADERPLUS" 0 KB 0 rows
. . exported "SUVIN"."SALEITEMDETAILPLUS" 0 KB 0 rows
. . exported "SUVIN"."SALEITEMSTONEDETAILPLUS" 0 KB 0 rows
. . exported "SUVIN"."SALEORDERPAYMENTDUESCHEDULE" 0 KB 0 rows
. . exported "SUVIN"."SALEOTHERCHARGEDETAILPLUS" 0 KB 0 rows
. . exported "SUVIN"."SALEPAYMENTDUESCHEDULEPLUS" 0 KB 0 rows
. . exported "SUVIN"."SALEPAYMENTGENERALPLUS" 0 KB 0 rows
. . exported "SUVIN"."SALEQUOTATION" 0 KB 0 rows
. . exported "SUVIN"."SALEQUOTATIONSTONEDETAIL" 0 KB 0 rows
. . exported "SUVIN"."SALEQUOTTAXSURCHARGEDETAIL" 0 KB 0 rows
. . exported "SUVIN"."SALERETURNHEADER" 0 KB 0 rows
. . exported "SUVIN"."SALERETURNITEMSTONEDETAIL" 0 KB 0 rows
. . exported "SUVIN"."SALERETURNOTHERCHARGEDETAIL" 0 KB 0 rows
. . exported "SUVIN"."SALERETURNPAYMENTGENERAL" 0 KB 0 rows
. . exported "SUVIN"."SALERETURNPAYMENTMETAL" 0 KB 0 rows
. . exported "SUVIN"."SALERETURNTAXSURCHARGEDETAIL" 0 KB 0 rows
. . exported "SUVIN"."SALETAXSURCHARGEDETAILPLUS" 0 KB 0 rows
. . exported "SUVIN"."SALRETURNDETAIL" 0 KB 0 rows
. . exported "SUVIN"."SECTIONRELEASEDETAIL" 0 KB 0 rows
. . exported "SUVIN"."SECTIONRELEASEHEADER" 0 KB 0 rows
. . exported "SUVIN"."SECTIONTRANSFERDETAIL" 0 KB 0 rows
. . exported "SUVIN"."SECTIONTRANSFERHEADER" 0 KB 0 rows
. . exported "SUVIN"."SISAMPLEDETAIL" 0 KB 0 rows
. . exported "SUVIN"."SISTONEDETAIL" 0 KB 0 rows
. . exported "SUVIN"."SMITHRECEIPTITEMSTONEDETAIL" 0 KB 0 rows
. . exported "SUVIN"."SMITHRECEIPTPAYMENTMETAL" 0 KB 0 rows
. . exported "SUVIN"."SMITHVOUCHER" 0 KB 0 rows
. . exported "SUVIN"."STOCKADJUSTMENTDETAIL" 0 KB 0 rows
. . exported "SUVIN"."STOCKADJUSTMENTHEADER" 0 KB 0 rows
. . exported "SUVIN"."STOCKLEDGERPERIODWISE" 0 KB 0 rows
. . exported "SUVIN"."TAGMERGINGDETAIL" 0 KB 0 rows
. . exported "SUVIN"."TAGMERGINGHEADER" 0 KB 0 rows
. . exported "SUVIN"."TAXSURCHARGEDETAIL" 0 KB 0 rows
. . exported "SUVIN"."TDSACKNOWLEDGEMENT" 0 KB 0 rows
. . exported "SUVIN"."TEMP_SSTOCK" 0 KB 0 rows
. . exported "SUVIN"."TJRETAIL" 0 KB 0 rows
. . exported "SUVIN"."UOMCONVERSIONDETAIL" 0 KB 0 rows
Master table "SUVIN"."SYS_EXPORT_SCHEMA_01" successfully loaded/unloaded
******************************************************************************
Dump file set for SUVIN.SYS_EXPORT_SCHEMA_01 is:
D:\EXPORT\JR.DMP
Job "SUVIN"."SYS_EXPORT_SCHEMA_01" successfully completed at 16:06:39

SQL>

Oracle 10g - Manually Create a Physical Standby Database Using Data Guard

2009-12-07T03:27:00.000-08:00

Step-by-step instructions on how to create a Physical Standby Database on Windows and UNIX servers, and maintenance tips on the databases in a Data Guard Environment.

Oracle 10g Data Guard is a great tool to ensure high availability, data protection and disaster recovery for enterprise data. I have been working on Data Guard/Standby databases using both Grid control and SQL command line for a couple of years, and my latest experience with Data Guard was manually creating a Physical Standby Database for a Laboratory Information Management System (LIMS) half a year ago. I maintain it daily and it works well. I would like to share my experience with the other DBAs.

In this example the database version is 10.2.0.3.. The Primary database and Standby database are located on different machines at different sites. The Primary database is called PRIM and the Standby database is called STAN. I use Flash Recovery Area, and OMF.

I. Before you get started:

1. Make sure the operating system and platform architecture on the primary and standby systems are the same;

2. Install Oracle database software without the starter database on the standby server and patch it if necessary. Make sure the same Oracle software release is used on the Primary and Standby databases, and Oracle home paths are identical.

3. Test the Standby Database creation on a test environment first before working on the Production database.

II. On the Primary Database Side:

1. Enable forced logging on your primary database:
SQL> ALTER DATABASE FORCE LOGGING;

2. Create a password file if it doesn’t exist.
1) To check if a password file already exists, run the following command:
SQL> select * from v$pwfile_users;

2) If it doesn’t exist, use the following command to create one:
- On Windows:
$cd %ORACLE_HOME%\database
$orapwd file=pwdPRIM.ora password=xxxxxxxx force=y
(Note: Replace xxxxxxxxx with the password for the SYS user.)

- On UNIX:
$Cd $ORACLE_HOME/dbs
$Orapwd file=pwdPRIM.ora password=xxxxxxxx force=y
(Note: Replace xxxxxxxxx with your actual password for the SYS user.)

3. Configure a Standby Redo log.
1) The size of the standby redo log files should match the size of the current Primary database online redo log files. To find out the size of your online redo log files:
SQL> select bytes from v$log;

BYTES
----------
52428800
52428800
52428800

2) Use the following command to determine your current log file groups:
SQL> select group#, member from v$logfile;

3) Create standby Redo log groups.
My primary database had 3 log file groups originally and I created 3 standby redo log groups using the following commands:
SQL>ALTER DATABASE ADD STANDBY LOGFILE GROUP 4 SIZE 50M;
SQL>ALTER DATABASE ADD STANDBY LOGFILE GROUP 5 SIZE 50M;
SQL>ALTER DATABASE ADD STANDBY LOGFILE GROUP 6 SIZE 50M;

4) To verify the results of the standby redo log groups creation, run the following query:
SQL>select * from v$standby_log;

4. Enable Archiving on Primary.
If your primary database is not already in Archive Log mode, enable the archive log mode:
SQL>shutdown immediate;
SQL>startup mount;
SQL>alter database archivelog;
SQL>alter database open;
SQL>archive log list;

5. Set Primary Database Initialization Parameters
Create a text initialization parameter file (PFILE) from the server parameter file (SPFILE), to add the new primary role parameters.

1) Create pfile from spfile for the primary database:
- On Windows:
SQL>create pfile=’\database\pfilePRIM.ora’ from spfile;
(Note- specify your Oracle home path to replace ‘’).

- On UNIX:
SQL>create pfile=’/dbs/pfilePRIM.ora’ from spfile;
(Note- specify your Oracle home path to replace ‘’).

2) Edit pfilePRIM.ora to add the new primary and standby role parameters: (Here the file paths are from a windows system. For UNIX system, specify the path accordingly)

db_name=PRIM
db_unique_name=PRIM
LOG_ARCHIVE_CONFIG='DG_CONFIG=(PRIM,STAN)'
LOG_ARCHIVE_DEST_1=
'LOCATION=F:\Oracle\flash_recovery_area\PRIM\ARCHIVELOG
VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=PRIM'
LOG_ARCHIVE_DEST_2=
'SERVICE=STAN LGWR ASYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
DB_UNIQUE_NAME=STAN'
LOG_ARCHIVE_DEST_STATE_1=ENABLE
LOG_ARCHIVE_DEST_STATE_2=ENABLE
LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
LOG_ARCHIVE_MAX_PROCESSES=30
remote_login_passwordfile='EXCLUSIVE'
FAL_SERVER=STAN
FAL_CLIENT=PRIM
STANDBY_FILE_MANAGEMENT=AUTO
# Specify the location of the standby DB datafiles followed by the primary location;
DB_FILE_NAME_CONVERT='E:\oracle\product\10.2.0\oradata\STAN\DATAFILE','E:\oracle\product\10.2.0\oradata\PRIM\DATAFILE'
# Specify the location of the standby DB online redo log files followed by the primary location LOG_FILE_NAME_CONVERT=’E:\oracle\product\10.2.0\oradata\STAN\ONLINELOG’,’E:\oracle\product\10.2.0\oradata\PRIM\ONLINELOG’,’F:\Oracle\flash_recovery_area\STAN\ONLINELOG’,’F:\Oracle\flash_recovery_area\PRIM\ONLINELOG’

6. Create spfile from pfile, and restart primary database using the new spfile.
Data Guard must use SPFILE. Create the SPFILE and restart database.
- On windows:
SQL> shutdown immediate;
SQL> startup nomount pfile=’\database\pfilePRIM.ora’;
SQL>create spfile from pfile=’\database\pfilePRIM.ora’;
-- Restart the Primary database using the newly created SPFILE.
SQL>shutdown immediate;
SQL>Startup;
(Note- specify your Oracle home path to replace ‘’).

- On UNIX:
SQL> shutdown immediate;
SQL> startup nomount pfile=’/dbs/pfilePRIM.ora’;
SQL>create spfile from pfile=’/dbs/pfilePRIM.ora’;
-- Restart the Primary database using the newly created SPFILE.
SQL>shutdown immediate;
SQL>Startup;
(Note- specify your Oracle home path to replace ‘’).

III. On the Standby Database Site:

1. Create a copy of Primary database data files on the Standby Server:
On Primary DB:
SQL>shutdown immediate;

On Standby Server (While the Primary database is shut down):
1) Create directory for data files, for example, on windows, E:\oracle\product\10.2.0\oradata\STAN\DATAFILE.
On UNIX, create the directory accordingly.

2) Copy the data files and temp files over.

3) Create directory (multiplexing) for online logs, for example, on Windows, E:\oracle\product\10.2.0\oradata\STAN\ONLINELOG and F:\Oracle\flash_recovery_area\STAN\ONLINELOG.
On UNIX, create the directories accordingly.

4) Copy the online logs over.

2. Create a Control File for the standby database:
On Primary DB, create a control file for the standby to use:
SQL>startup mount;
SQL>alter database create standby controlfile as ‘STAN.ctl;
SQL>ALTER DATABASE OPEN;

3. Copy the Primary DB pfile to Standby server and rename/edit the file.

1) Copy pfilePRIM.ora from Primary server to Standby server, to database folder on Windows or dbs folder on UNIX under the Oracle home path.

2) Rename it to pfileSTAN.ora, and modify the file as follows. : (Here the file paths are from a windows system. For UNIX system, specify the path accordingly)

*.audit_file_dest='E:\oracle\product\10.2.0\admin\STAN\adump'
*.background_dump_dest='E:\oracle\product\10.2.0\admin\STAN\bdump'
*.core_dump_dest='E:\oracle\product\10.2.0\admin\STAN\cdump'
*.user_dump_dest='E:\oracle\product\10.2.0\admin\STAN\udump'
*.compatible='10.2.0.3.0'
control_files='E:\ORACLE\PRODUCT\10.2.0\ORADATA\STAN\CONTROLFILE\STAN.CTL','F:\ORACLE\FLASH_RECOVERY_AREA\STAN\CONTROLFILE\STAN.CTL'
db_name='PRIM'
db_unique_name=STAN
LOG_ARCHIVE_CONFIG=’DG_CONFIG=(PRIM,STAN)’
LOG_ARCHIVE_DEST_1=
‘LOCATION=F:\Oracle\flash_recovery_area\STAN\ARCHIVELOG
VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=STAN’
LOG_ARCHIVE_DEST_2=
‘SERVICE=PRIM LGWR ASYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
DB_UNIQUE_NAME=PRIM’
LOG_ARCHIVE_DEST_STATE_1=ENABLE
LOG_ARCHIVE_DEST_STATE_2=ENABLE
LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
LOG_ARCHIVE_MAX_PROCESSES=30
FAL_SERVER=PRIM
FAL_CLIENT=STAN
remote_login_passwordfile='EXCLUSIVE'
# Specify the location of the primary DB datafiles followed by the standby location
DB_FILE_NAME_CONVERT=’E:\oracle\product\10.2.0\oradata\PRIM\DATAFILE’,’E:\oracle\product\10.2.0\oradata\STAN\DATAFILE’
# Specify the location of the primary DB online redo log files followed by the standby location
LOG_FILE_NAME_CONVERT=’E:\oracle\product\10.2.0\oradata\PRIM\ONLINELOG’,’E:\oracle\product\10.2.0\oradata\STAN\ONLINELOG’,’F:\Oracle\flash_recovery_area\PRIM\ONLINELOG’,’F:\Oracle\flash_recovery_area\STAN\ONLINELOG’
STANDBY_FILE_MANAGEMENT=AUTO

(Note: Not all the parameter entries are listed here.)

4. On Standby server, create all required directories for dump and archived log destination:
Create directories adump, bdump, cdump, udump, and archived log destinations for the standby database.

5. Copy the standby control file ‘STAN.ctl’ from primary to standby destinations ;

6. Copy the Primary password file to standby and rename it to pwdSTAN.ora.
On Windows copy it to \database folder, and on UNIX copy it to /dbs directory. And then rename the password file.

7. For Windows, create a Windows-based services (optional):
$oradim –NEW –SID STAN –STARTMODE manual

8. Configure listeners for the primary and standby databases.

1) On Primary system: use Oracle Net Manager to configure a listener for PRIM and STAN. Then restart the listener.
$lsnrctl stop
$lsnrctl start

2) On Standby server: use Net Manager to configure a listener for PRIM and STAN. Then restart the listener.
$lsnrctl stop
$lsnrctl start

9. Create Oracle Net service names.
1) On Primary system: use Oracle Net Manager to create network service names for PRIM and STAN. Check tnsping to both services:
$tnsping PRIM
$tnsping STAN

2) On Standby system: use Oracle Net Manager to create network service names for PRIM and STAN. Check tnsping to both services:
$tnsping PRIM
$tnsping STAN

10. On Standby server, setup the environment variables to point to the Standby database.

Set up ORACLE_HOME and ORACLE_SID.

11. Start up nomount the standby database and generate a spfile.
- On Windows:
SQL>startup nomount pfile=’\database\pfileSTAN.ora’;
SQL>create spfile from pfile=’\database\pfileSTAN.ora’;
-- Restart the Standby database using the newly created SPFILE.
SQL>shutdown immediate;
SQL>startup mount;

- On UNIX:
SQL>startup nomount pfile=’/dbs/pfileSTAN.ora’;
SQL>create spfile from pfile=’/dbs/pfileSTAN.ora’;
-- Restart the Standby database using the newly created SPFILE.
SQL>shutdown immediate;
SQL>startup mount;
(Note- specify your Oracle home path to replace ‘’).

12. Start Redo apply
1) On the standby database, to start redo apply:
SQL>alter database recover managed standby database disconnect from session;

If you ever need to stop log apply services:
SQL> alter database recover managed standby database cancel;

13. Verify the standby database is performing properly:
1) On Standby perform a query:
SQL>select sequence#, first_time, next_time from v$archived_log;

2) On Primary, force a logfile switch:
SQL>alter system switch logfile;

3) On Standby, verify the archived redo log files were applied:
SQL>select sequence#, applied from v$archived_log order by sequence#;

14. If you want the redo data to be applied as it is received without waiting for the current standby redo log file to be archived, enable the real-time apply.

To start real-time apply:
SQL> alter database recover managed standby database using current logfile disconnect;

15. To create multiple standby databases, repeat this procedure.

IV. Maintenance:

1. Check the alert log files of Primary and Standby databases frequently to monitor the database operations in a Data Guard environment.

2. Cleanup the archive logs on Primary and Standby servers.

I scheduled weekly Hot Whole database backup against my primary database that also backs up and delete the archived logs on Primary.

For the standby database, I run RMAN to backup and delete the archive logs once per week.
$rman target /@STAN;
RMAN>backup archivelog all delete input;

To delete the archivelog backup files on the standby server, I run the following once a month:
RMAN>delete backupset;

3. Password management
The password for the SYS user must be identical on every system for the redo data transmission to succeed. If you change the password for SYS on Primary database, you will have to update the password file for Standby database accordingly, otherwise the logs won’t be shipped to the standby server.

Checking Growth of Oracle Database in Oracle 10g

2008-09-22T04:57:00.000-07:00

Step : 1 Calculate total Size of tablespace
SELECT sum(bytes)/1024/1024 "TOTAL SIZE (MB)"
FROM dba_Data_files

Step : 2 Calculate Free Space in Tablespace
SELECT sum(bytes)/1024/1024 "FREE SPACE (MB)"
FROM dba_free_space

Step : 3 Calculate total size , free space and used space in tablespace

SELECT t2.total "TOTAL SIZE",
t1.free "FREE SPACE",
(t1.free/t2.total)*100 "FREE (%)" ,
(1-t1.free/t2.total)*100 "USED (%)"
FROM (SELECT sum(bytes)/1024/1024 free FROM dba_free_space) t1 ,
(SELECT sum(bytes)/1024/1024 total FROM dba_Data_files) t2

Step : 4 Create table which is store all free/use space related information of tablespace

CREATE TABLE db_growth
AS
SELECT *
FROM(
SELECT sysdate,
t2.total "TOTAL_SIZE",
t1.free "FREE_SPACE",
(t1.free/t2.total)*100 "FREE% "
FROM
(SELECT sum(bytes)/1024/1024 free
FROM dba_free_space) t1 ,
(SELECT sum(bytes)/1024/1024 total
FROM dba_Data_files) t2
)

Step : 5 Insert free space information in DB_GROWTH table (if you want to populate data Manually)

INSERT INTO db_growth
SELECT *
FROM (
SELECT sysdate,
t2.total "TOTAL_SIZE",
t1.free "FREE_SPACE",
(t1.free/t2.total)*100 "FREE%"
FROM
(SELECT sum(bytes)/1024/1024 free
FROM dba_free_space) t1 ,
(SELECT sum(bytes)/1024/1024 total
FROM dba_Data_files) t2
)

Step : 6 Create View on DB_GROWTH based table ( This Steps is Required if you want to populate data automatically)

CREATE VIEW v_db_growth
AS SELECT *
FROM
(
SELECT sysdate,
t2.total "TOTAL_SIZE",
t1.free "FREE_SPACE",
(t1.free/t2.total)*100 "FREE%"
FROM
(SELECT sum(bytes)/1024/1024 free
FROM dba_free_space) t1 ,
(SELECT sum(bytes)/1024/1024 total
FROM dba_Data_files) t2
)

Step : 7 Insert data into DB_GROWTH table from V_DD_GROWTH view

INSERT INTO db_growth select *
FROM v_db_growth

Step : 8 Check everything goes fine.

SELECT * FROM db_growth;

Check Result
Step : 9 Execute following SQL for more time stamp information

ALTER SESSION SET nls_date_format ='dd-mon-yyyy hh24:mi:ss' ;
Session altered.

Step : 10 Create a DBMS jobs which execute after 24 hours
DECLARE
jobno NUMBER;
BEGIN
DBMS_JOB.submit(
jobno, 'BEGIN INSERT INTO db_growth SELECT * FROM v_db_growth;COMMIT:END;', sysdate, 'SYSDATE+ 24', TRUE);
COMMIT;
END;

PL/SQL procedure successfully completed.

Step: 11 View your dbms jobs and it's other information
SELECT * FROM user_jobs;
TIPS: If you want to execute dbms jobs manually execute following command other wise jobs is executing automatically
EXEC DBMS_JOB.run(ENTER_JOB_NUMBER)
PL/SQL procedure successfully completed.
Step: 12 Finally all data populated in db_growth table
SELECT * FROM db_growth

How to Drop All Objects in a Schema in Oracle 10g

2008-08-26T01:02:00.000-07:00

Normally, it is simplest to drop and add the user. This is the preferred method if you have system or sysdba access to the database.

If you don't have system level access, and want to scrub your schema, the following sql will produce a series of drop statments, which can then be executed.

select 'drop '||object_type||' '|| object_name|| DECODE(OBJECT_TYPE,'TABLE',' CASCADE CONSTRAINTS;',';')
from user_objects

Then, I normally purge the recycle bin to really clean things up. To be honest, I don't see a lot of use for oracle's recycle bin, and wish i could disable it... but anyway:

purge recyclebin;

This will produce a list of drop statements. Not all of them will execute - if you drop with cascade, dropping the PK_* indices will fail. But in the end, you will have a pretty clean schema. Confirm with:

select * from user_objects

Importing the whole User Schema (All Objects Included) in SQL Plus from one user to another user with different name

2008-07-22T02:24:00.000-07:00

Before Importing Create a user

SQL> create user jretail1 identified by jretail*****;

User created.

Grant privileges to the user

SQL> grant resource,connect,create view to jretail1;

Grant succeeded.

Then start the import process

SQL> $imp jretail1@test file=c:\jretail1120am.dmp log=c:\jretail1120am.log fromuser=jretail touser=jretail1;

Import: Release 10.1.0.2.0 - Production on Thu Oct 22 14:58:32 2009

Copyright (c) 1982, 2004, Oracle. All rights reserved.

Password:

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options

Export file created by EXPORT:V09.02.00 via conventional path

Warning: the objects were exported by JRETAIL, not by you

import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
. . importing table "ACCOUNTMASTER" 3203 rows imported
. . importing table "ACCOUNTOPENING" 4345 rows imported
. . importing table "AGEINGMASTER" 6 rows imported
. . importing table "APPLICATIONCONFIGURATION" 2 rows imported
. . importing table "BILLWISEADJUSTMENT" 462 rows imported
. . importing table "BILLWISEADJUSTMENTSCHEDULE" 462 rows imported
. . importing table "BUDGETMASTERDETAIL" 4 rows imported
. . importing table "BUDGETMASTERHEADER" 1 rows imported
. . importing table "CALENDARMASTER" 4 rows imported
. . importing table "CALENDARMONTHDETAIL" 0 rows imported
. . importing table "CHITMASTER" 10 rows imported
. . importing table "CHITMEMBER" 850 rows imported
. . importing table "CHITMEMBERINSTALLMENTDETAIL" 7107 rows imported
. . importing table "CHITRECEIPTDETAIL" 6351 rows imported
. . importing table "ITEMTYPEATTRIBUTESDETAIL" 2 rows imported
About to enable constraints...
Import terminated successfully without warnings.

SQL>

Importing the whole User Schema (All Objects Included) in SQL Plus from one user to another user with the same name

2008-06-23T06:55:00.000-07:00

Before Importing Create a user

SQL> create user visynapse identified by visynapse*******;

User created.

Grant privileges to the user

SQL> grant resource,connect,create view to visynapse;

Grant succeeded.

Then start the import process

SQL> $imp visynapse@test file=E:/uploaddb_19_10_09.dmp log=E:/implogvisyn.log;

Import: Release 10.1.0.2.0 - Production on Mon Oct 19 12:50:41 2009

Copyright (c) 1982, 2004, Oracle. All rights reserved.

Password:*****

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options

Export file created by EXPORT:V10.01.00 via conventional path
import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
. importing VISYNAPSE's objects into VISYNAPSE
. . importing table "CALCULATION_SECURITY" 199 rows imported
. . importing table "CALCULATION_TABLE" 207 rows imported
. . importing table "COLOUR" 1 rows imported
. . importing table "CUBE" 8 rows imported
. . importing table "DASHBOARD" 2 rows imported
. . importing table "DASHBOARD_METRIC" 8 rows imported
. . importing table "DASH_TABLE" 3 rows imported
. . importing table "DATA_DICTIONARY" 48 rows imported
. . importing table "DIMENSION_26" 295 rows imported
. . importing table "DIMENSION_27" 432 rows imported
. . importing table "DIMENSION_28" 295 rows imported
. . importing table "DIMENSION_SECURITY" 19 rows imported
. . importing table "DOMAIN" 1 rows imported
. . importing table "FILTERS" 0 rows imported
. . importing table "GRAINS" 6148 rows imported
. . importing table "HEADER_FOOTER" 0 rows imported
. . importing table "KEY_PERFORMANCE_INDICATOR" 0 rows imported
. . importing table "KEY_PERFORMANCE_INDICATOR_CS" 0 rows imported
. . importing table "KPI_DIMENSION" 0 rows imported
. . importing table "KPI_DIMENSION_CS" 0 rows imported
. . importing table "LINKMETRIC" 0 rows imported
. . importing table "METRIC" 8 rows imported
. . importing table "METRIC_CALCULATION_SET" 207 rows imported
. . importing table "METRIC_CUBE_SET" 8 rows imported
. . importing table "REPORT_CHANNEL" 0 rows imported
. . importing table "REPORT_CONFIG" 23 rows imported
. . importing table "REPORT_HEADER" 0 rows imported
. . importing table "SCORECARD" 0 rows imported
. . importing table "SELECTION_DIMENSION" 0 rows imported
. . importing table "SELECTION_FILTERCRITERIA" 0 rows imported
. . importing table "SELECTION_FORMULA" 0 rows imported
. . importing table "SELECTION_SHAREDREPORT" 0 rows imported
. . importing table "SELECTION_TABLE" 0 rows imported
. . importing table "STATIC_REPORT_TABLE" 8 rows imported
. . importing table "SUMMARY_CONFIG" 0 rows imported
. . importing table "TIME_FREQUENCY" 6 rows imported
. . importing table "USER_DASHBOARD_SECURITY" 2 rows imported
. . importing table "USER_GROUP" 1 rows imported
. . importing table "USER_PROFILES" 1 rows imported
. . importing table "USER_TARGETS" 8 rows imported
. . importing table "VALUE_SECURITY" 0 rows imported
About to enable constraints...
Import terminated successfully without warnings.

SQL>

Exporting the whole User Schema (All Objects Included) in Oracle SQL Plus

2008-05-10T00:46:00.000-07:00

SQL> $exp visynapse@uploaddb file=E:/uploaddb_19_10_09.dmp log=E:/uploadlog.log;

Export: Release 10.1.0.2.0 - Production on Mon Oct 19 11:18:48 2009

Copyright (c) 1982, 2004, Oracle. All rights reserved.

Password:******

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user VISYNAPSE
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions for user VISYNAPSE
About to export VISYNAPSE's objects ...
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
. about to export VISYNAPSE's tables via Conventional Path ...
. . exporting table CALCULATION_SECURITY 199 rows exported
. . exporting table CALCULATION_TABLE 207 rows exported
. . exporting table COLOUR 1 rows exported
. . exporting table CUBE 8 rows exported
. . exporting table DASHBOARD 2 rows exported
. . exporting table DASHBOARD_METRIC 8 rows exported
. . exporting table DASH_TABLE 3 rows exported
. . exporting table DATA_DICTIONARY 48 rows exported
. . exporting table DEFINITIONS_21 21 rows exported
. . exporting table DEFINITIONS_22 12 rows exported
. . exporting table DEFINITIONS_23 17 rows exported
. . exporting table DEFINITIONS_24 30 rows exported
. . exporting table DEFINITIONS_25 22 rows exported
. . exporting table DEFINITIONS_26 25 rows exported
. . exporting table DEFINITIONS_27 23 rows exported
. . exporting table DEFINITIONS_28 28 rows exported
. . exporting table DIMENSION_SECURITY 19 rows exported
. . exporting table DOMAIN 1 rows exported
. . exporting table FILTERS 0 rows exported
. . exporting table GRAINS 6148 rows exported
. . exporting table HEADER_FOOTER 0 rows exported
. . exporting table KEY_PERFORMANCE_INDICATOR 0 rows exported
. . exporting table KEY_PERFORMANCE_INDICATOR_CS 0 rows exported
. . exporting table KPI_DIMENSION 0 rows exported
. . exporting table KPI_DIMENSION_CS 0 rows exported
. . exporting table LINKMETRIC 0 rows exported
. . exporting table METRIC 8 rows exported
. . exporting table METRIC_CALCULATION_SET 207 rows exported
. . exporting table METRIC_CUBE_SET 8 rows exported
. . exporting table REPORT_CHANNEL 0 rows exported
. . exporting table REPORT_CONFIG 23 rows exported
. . exporting table REPORT_HEADER 0 rows exported
. . exporting table SCORECARD 0 rows exported
. . exporting table SELECTION_DIMENSION 0 rows exported
. . exporting table SELECTION_FILTERCRITERIA 0 rows exported
. . exporting table SELECTION_FORMULA 0 rows exported
. . exporting table SELECTION_SHAREDREPORT 0 rows exported
. . exporting table SELECTION_TABLE 0 rows exported
. . exporting table STATIC_REPORT_TABLE 8 rows exported
. . exporting table SUMMARY_CONFIG 0 rows exported
. . exporting table TIME_FREQUENCY 6 rows exported
. . exporting table USER_DASHBOARD_SECURITY 2 rows exported
. . exporting table USER_GROUP 1 rows exported
. . exporting table USER_PROFILES 1 rows exported
. . exporting table USER_TARGETS 8 rows exported
. . exporting table VALUES_28_CONTROL 196 rows exported
. . exporting table VALUE_SECURITY 0 rows exported
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting referential integrity constraints
. exporting triggers
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting materialized views
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting statistics
Export terminated successfully without warnings.

SQL>

Procedure for Installing Redhat and installing oracle 9i on RHEL4

2008-04-19T07:39:00.000-07:00

Part I: Installing Linux

Minimum hardware requirement:
* Pentium IV processor
* 512MB of RAM
* minimum 40GB HARD DISK

1. Boot the server using the first CD.
* You may need to change your BIOS settings to allow booting from the CD.

2. The boot screen appears with the boot: prompt at the bottom of the screen.
* Select Enter to continue with a graphical install on the console. (For other installation methods and options, refer to the Red Hat Installation Guide.)
* The installer scans your hardware, briefly displays the Red Hat splash screen, and then begins a series of screen prompts.

3. Language Selection
* Accept the default.

4. Keyboard Configuration
* Accept the default.

5. Welcome Screen
* Click on Next.

6. Disk Partitioning Setup
* Do the disk partitioning as per the following
PARTITIONS MINIMUMSIZE
/ 12GB
/boot 100MB
/opt 4GB
/oracle 10GB
/tmp 3GB
swap double the size of RAM not more than 2GB

7. Boot Loader Configuration
* Accept the default.

8. Network Configuration
* It is usually best to configure database servers with a static IP address. To do so, click on Edit .
* A pop-up window appears. Uncheck the Configure using DHCP box, and enter the IP Address and Netmask for the server. Be sure that Activate on boot is checked, and click on OK .
* In the Hostname box, select manually and enter the hostname.
* In the Miscellaneous Settings box, enter the remaining network settings.

9. Firewall Configuration
* For the purposes of this walk-through, no firewall is configured. Select No firewall
* Select Disabled on the "Enable SELinux" drop down list.
* Click on Proceed when the "Warning - No Firewall" window appears.

10. Additional Language Support
* Accept the default.

11. Time Zone Selection
* Choose the time settings that are appropriate for your area. Setting the system clock to UTC is usually a good practice for servers. To do so, click on System clock uses UTC.

12. Set Root Password
* Enter a password for root, and enter it again to confirm.

13. Package Installation Defaults
* Select Customize software packages to be installed.

14. Package Group Selection
* Select only the package sets shown here and leave all others unselected.
* Desktop
o X Window System
o Gnome
* Applications
o Graphical Internet (optional)
* Servers
o Do not select anything in this group.
* Development
o Development Tools
* System
o Administration Tools
o System Tools
+ Add the package 'sysstat' by clicking on the Details link and selecting "sysstat - The sar an iostat system monitoring commands." from the Optional Packages list.
* Miscellaneous
o Do not select anything in this group.
* Click on Next to proceed.

15. Installing Packages
* Software will be copied to the hard disk and installed. Change disks as prompted.

16. Congratulations
* Remove the installation media from the system, and click on Reboot .

17. The system automatically reboots and presents a new welcome screen.
* Click on Next.

18. License Agreement
* Read the license agreement. If you agree to the terms, select Yes, I agree to the License Agreement and click on Next.

19. Date and Time
* Set the Date and Time.
* If you want to use an NTP server (recommended), select Enable Network Time Protocol and enter the name of the NTP server.

20. Display
* Accept the defaults or change as required.

21. Red Hat Login
* Enter your Red Hat Network login and password or create a new one.

22. System User
* Create an account for yourself.
* Do not create an account for oracle at this time. Creating the oracle account is covered later in this section.

23. Additional CDs
* Click on Next.

24. Finish Setup
* Click on Next.

25. A graphical login screen appears.

26. Congratulations! Your RHEL4 software is now installed.

27. Restart the system and logged in a root user, hence keeping the system ready to install Oracle 9i Release 2 on it.

II.Installation steps of oracle 9i:

Before Installing oracle, acquire the following softwares

1.Oracle 9i release 2(9.2.0.4.0) CD 1 OF 3.
2.Oracle 9i release 2(9.2.0.4.0) CD 2 of 3.
3.Oracle 9i release 2(9.2.0.4.0) CD 3 of 3.
4.Oracle 9i release 2(9.2.0.4.0) patch CD.
5.jdk1.5 update 6.

Download Oracle9i for Linux from the following web site:
http://otn.oracle.com/software/products/oracle9i/htdocs/linuxsoft.html

Download java for linux from the following website:
http://java.sun.com

The following steps are for installing oracle 9i on RHEL4.
1.Install JDK1.5 in /usr/java folder by using the following command.
* Create folder named javasoft on the Desktop.
* Open a new terminal using the following command:
right click on the Desktop and click Open terminal from the popup menu.
* Copy jdk-1_5_0_06-linux-i586.bin from the CD to /root/Desktop/javasoft folder, using the following commands.
Insert the CD containing jdk1.5 software

#mount /media/cdrom
*cp /media/cdrom/jdk-1_5_0_06-linux-i586.bin /root/Desktop/javasoft
*create a folder named java in the /usr folder.

#mkdir -p /usr/java
*Use the following commands to install jdk1.5
*cd /usr/java
*/root/Desktop/javasoft/jdk-1_5_0_06-linux-i586.bin
follow the steps as prompted to install the software.
*Create a symbolic link "jdk1.5" for easy accessibility using the following command:
#ln -s jdk-1_5_0_06 jdk1.5
*Do the permanent path setting for writing and executing the java programs without going to this folder every time.
#vi /etc/profile
Insert the following lines at the end of the file.
JAVA_HOME=/usr/java/jdk1.5
export JAVA_HOME
PATH=$JAVA_HOME/bin:$PATH
export PATH
*save and relogin as root user.

2.Open the terminal window on the linux desktop

3.Use the following commands to go to the home directory.
#cd /home

4.Insert the oracle 9i release CD no.1/3 to the CD Drive.

5.Mount the CD by the following command:
#mount /media/cdrom

6.Confirm the availability of the .cpio file the CD using the following command:
#ls /media/cdrom

7.Use the following command to extract the software from CD 1 of oracle
#cpio -idmv < /media/cdrom/ship_9204_linux_disk1.cpionote: once you do this a folder named Disk1 will be created in /home directory8.Unmount the CD using the following command:
#umount /media/cdrom

9.Insert the oracle 9i release CD no.2/3 to the CD Drive.

10.Mount the CD by the following command:
#mount /media/cdrom

11.Confirm the availability of the .cpio file the CD using the following command:
#ls /media/cdrom

12.Use the following command to extract the software from CD 2 of oracle
#cpio -idmv < /media/cdrom/ship_9204_linux_disk2.cpioNote: once you do this a folder named Disk2 will be created in /home directory

13.Unmount the CD using the following command:
#umount /media/cdrom

14.Insert the oracle 9i release CD no.3/3 to the CD Drive.

15.Mount the CD by the following command:
#mount /media/cdrom

16.Confirm the availability of the .cpio file the CD using the following command:
#ls /media/cdrom

17.Use the following command to extract the software from CD 3 of oracle
#cpio -idmv < /media/cdrom/ship_9204_linux_disk3.cpionote: once you do this a folder named Disk3 will be created in /home directory18.Unmount the CD using the following command:
#umount /media/cdrom

19.For patch use the following commands:
#mkdir 92040

20.Insert the patch CD to the CD Drive.

21.Mount the CD using following command:
#mount /media/cdrom

22.Use the following command to unzip the files
#unzip -d /home/92040 /media/cdrom/p3006854_9204_LINUX.zip

23.After issuing the above command, it will create a folder named as 3006854 in the /home/92040 directory. please confirm the same.

24.Issue the following commands to extract the p4198954 patch.
#unzip -d /home/92040 /media/cdrom/p4198954_40_LINUX.zip

you will able to see the following rpms within the specified folder.
1) compact-orcle-rhel4-1-0-5.i386.rpm
2) compact-libcwait-2.1-1.i386.rpm

As soon as you try to install these RPM's then you will receive dependency failure.
Use the following steps to avoid dependency failure:
1)Insert the RHEL4 CD no.3 to the CD Drive.

2)Mount the CD using the following command:
#mount /media/cdrom
#cd /media/cdrom/RedHat/RPMS

3)Execute the following RPMs
#rpm -ivh --aid libaio-devel-0.3.102-1.i386.rpm
#rpm -ivh --aid openmotif21-2.1.30-11.RHEL4.2.i386.rpm

4)After successful execution of the above RPMs, execute the RPMs already unzipped from the 4198954 patch.
#cd /home/92040
#rpm -ivh compat-oracle-rhel4-1.0.5.i386.rpm
#rpm -ivh compat-libcwait-2.1-1.i386.rpm

5)unmount the 3rd CD of RHEL4 using the following command
#unmount /media/cdrom

25.Configuring the Linux Kernel Parameters, update the /etc/sysctl.conf file,by adding the following lines towards the end of the file.
#vi /etc/sysctl.conf
kernel.shmall = 2097152
kernel.shmmax = 536870912
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default=262144
net.core.wmem_default=262144
net.core.rmem_max=262144
net.core.wmem_max=26214

save the file and relogin.

26.Create the Oracle Groups and User Account:
# groupadd oinstall
# groupadd dba
# groupadd oper
# useradd -g oinstall -G dba oracle
# id oracle

Set the password on the oracle account:
# passwd oracle
Changing password for user oracle.
New password:
Retype new password:
passwd: all authentication tokens updated successfully.

27.Create Directories for oracle software.
# mkdir -p /oracle/app/oracle/product/9.2.0.4.0
# chown -R oracle:oinstall /oracle
# chmod -R 775 /oracle

28.Login as the oracle user and add the following lines at the end of the .bash_profile file:
#vi .bash_profile

ORACLE_BASE=/oracle/app/oracle; export ORACLE_BASE
ORACLE_HOME=$ORACLE_BASE/product/9.2.0.4.0; export ORACLE_HOME
ORACLE_TERM=xterm; export ORACLE_TERM
PATH=$ORACLE_HOME/bin:$PATH:/usr/java/jdk1.5/bin; export PATH
ORACLE_OWNER=oracle; export ORACLE_OWNER
ORACLE_SID=jay; export ORACLE_SID

LD_LIBRARY_PATH=$ORACLE_HOME/lib; export LD_LIBRARY_PATH
CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib;
export CLASSPATH
ORACLE_OEM_JAVARUNTIME=/usr/java/jdk1.5; export ORACLE_OEM_JAVARUNTIME

LD_ASSUME_KERNEL=2.4.19; export LD_ASSUME_KERNEL
THREADS_FLAG=native; export THREADS_FLAG
TMP=/tmp; export TMP
TMPDIR=$TMP; export TMPDIR

29.Save the .bash_profile file and relogin as oracle user.

30.Make sure the .bash_profile file ran correctly by issuing the following command:
$set | more

31.Login to Root using this command:
$su -
password:rootpassword

32.Execute the 3006854 patch using the following command:
#sh /home/92040/3006854/rhel3_pre_install.sh

33.Exit from the Root.
#exit
$(After typing exit you will receive the oracle login $ prompt)

34.Start the universal installer using the following command:
$/home/Disk1/runInstaller

note: This will start the universal installer. Follow the steps in the wizard to install oracle software.

NOTE: During the installation enter the appropriate ORACLE_HOME and name then continue as normal

1. Welcome Screen:
Click Next

2.Inventory Location:
"/oracle/app/oracle/oraInventory"and Click Next

3.Unix Group Name:
Use "oinstall" and click Next
When asked to run /tmp/orainstRoot.sh, run it before you click Continue
open a new terminal,by click the desktop
$su -
password:root password
#cd /tmp
#./orainstRoot.sh
once this execution is over and you get back the prompt, switch to the dialog box in the Universal Installer and continue next.

5.File Locations:
name:use default value
path:/oracle/app/oracle/product/9.2.0.4.0

6.Available Products:
Select "Oracle9i Database 9.2.0.1.0"

7.Installation Types:
Select "Enterprise Edition(2.84GB)

8.Database configuration:
Select "General Purpose"

9.Database Identification
Global Database Name:Antony
SID:Antony
and then Click Next

10.Database File Locations:
Directory for Database Files:/oracle/app/oracle/oradata
and then click Next

11.Database Character Set:
Use the default character set
and then click Next

12.Summary:
Start the Install

13.Setup privileges:
before completing the installation the universal installer will prompt another file to be executed from the root login.
follow the sequence commands to overcome this:
open the terminal
$su -
password:root password
#cd /oracle/app/oracle/product/9.2.0.4.0
#./root.sh
it will prompt for a path, press enter to keep it default.
after that press ok in the dialog box.

14.Configuration tools:
if any error comes, Simply ignore it.

15.Database Configuration Assistant:
enter password for sys and system and click OK

16. At the end of the installation, exit runInstaller.

Creating and Maintaining a Password File in Oracle 10g

2008-02-11T07:37:00.000-08:00

You can create a password file using the password file creation utility, ORAPWD. For some operating systems, you can create this file as part of your standard installation.

This section contains the following topics:

*

Using ORAPWD
*

Setting REMOTE_LOGIN_ PASSWORDFILE
*

Adding Users to a Password File
*

Maintaining a Password File

See Also:

*

"Using Password File Authentication"
*

"Selecting an Authentication Method for Database Administrators"

Using ORAPWD

The syntax of the ORAPWD command is as follows:

ORAPWD FILE=filename [ENTRIES=numusers]
[FORCE={Y|N}] [IGNORECASE={Y|N}] [NOSYSDBA={Y|N}]

Command arguments are summarized in the following table.
Argument Description
FILE Name to assign to the password file. See your operating system documentation for name requirements. You must supply a complete path. If you supply only a file name, the file is written to the current directory.
ENTRIES (Optional) Maximum number of entries (user accounts) to permit in the file.
FORCE (Optional) If y, permits overwriting an existing password file.
IGNORECASE (Optional) If y, passwords are treated as case-insensitive.
NOSYSDBA (Optional) For Data Vault installations. See the Data Vault installation guide for your platform for more information.

There are no spaces permitted around the equal-to (=) character.

The command prompts for the SYS password and stores the password in the created password file.

Example

The following command creates a password file named orapworcl that allows up to 30 privileged users with different passwords.

orapwd FILE=orapworcl ENTRIES=30

ORAPWD Command Line Argument Descriptions

The following sections describe the ORAPWD command line arguments.

FILE

This argument sets the name of the password file being created. You must specify the full path name for the file. If you supply only a file name, the file is written to the current directory. The contents of this file are encrypted, and the file cannot be read directly. This argument is mandatory.

The types of filenames allowed for the password file are operating system specific. Some operating systems require the password file to adhere to a specific format and be located in a specific directory. Other operating systems allow the use of environment variables to specify the name and location of the password file. For name and location information for the Unix and Linux operating systems, see Administrator's Reference for UNIX-Based Operating Systems. For Windows, see Platform Guide for Microsoft Windows. For other operating systems, see your operating system documentation.

If you are running multiple instances of Oracle Database using Oracle Real Application Clusters, the environment variable for each instance should point to the same password file.

Caution:
It is critically important to the security of your system that you protect your password file and the environment variables that identify the location of the password file. Any user with access to these could potentially compromise the security of the connection.
ENTRIES

This argument specifies the number of entries that you require the password file to accept. This number corresponds to the number of distinct users allowed to connect to the database as SYSDBA or SYSOPER. The actual number of allowable entries can be higher than the number of users, because the ORAPWD utility continues to assign password entries until an operating system block is filled. For example, if your operating system block size is 512 bytes, it holds four password entries. The number of password entries allocated is always a multiple of four.

Entries can be reused as users are added to and removed from the password file. If you intend to specify REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE, and to allow the granting of SYSDBA and SYSOPER privileges to users, this argument is required.

Caution:
When you exceed the allocated number of password entries, you must create a new password file. To avoid this necessity, allocate a number of entries that is larger than you think you will ever need.
FORCE

This argument, if set to Y, enables you to overwrite an existing password file. An error is returned if a password file of the same name already exists and this argument is omitted or set to N.
IGNORECASE

If this argument is set to y, passwords are case-insensitive. That is, case is ignored when comparing the password that the user supplies during login with the password in the password file.

See Also:
Oracle Database Security Guide for more information about case-sensitivity in passwords.
Setting REMOTE_LOGIN_ PASSWORDFILE

In addition to creating the password file, you must also set the initialization parameter REMOTE_LOGIN_PASSWORDFILE to the appropriate value. The values recognized are:

*

NONE: Setting this parameter to NONE causes Oracle Database to behave as if the password file does not exist. That is, no privileged connections are allowed over nonsecure connections.
*

EXCLUSIVE: (The default) An EXCLUSIVE password file can be used with only one instance of one database. Only an EXCLUSIVE file can be modified. Using an EXCLUSIVE password file enables you to add, modify, and delete users. It also enables you to change the SYS password with the ALTER USER command.
*

SHARED: A SHARED password file can be used by multiple databases running on the same server, or multiple instances of an Oracle Real Application Clusters (RAC) database. A SHARED password file cannot be modified. This means that you cannot add users to a SHARED password file. Any attempt to do so or to change the password of SYS or other users with the SYSDBA or SYSOPER privileges generates an error. All users needing SYSDBA or SYSOPER system privileges must be added to the password file when REMOTE_LOGIN_PASSWORDFILE is set to EXCLUSIVE. After all users are added, you can change REMOTE_LOGIN_PASSWORDFILE to SHARED, and then share the file.

This option is useful if you are administering multiple databases or a RAC database.

If REMOTE_LOGIN_PASSWORDFILE is set to EXCLUSIVE or SHARED and the password file is missing, this is equivalent to setting REMOTE_LOGIN_PASSWORDFILE to NONE.

Note:
You cannot change the password for SYS if REMOTE_LOGIN_PASSWORDFILE is set to SHARED. An error message is issued if you attempt to do so.
Adding Users to a Password File

When you grant SYSDBA or SYSOPER privileges to a user, that user's name and privilege information are added to the password file. If the server does not have an EXCLUSIVE password file (that is, if the initialization parameter REMOTE_LOGIN_PASSWORDFILE is NONE or SHARED, or the password file is missing), Oracle Database issues an error if you attempt to grant these privileges.

A user's name remains in the password file only as long as that user has at least one of these two privileges. If you revoke both of these privileges, Oracle Database removes the user from the password file.

Creating a Password File and Adding New Users to It

Use the following procedure to create a password and add new users to it:

1.

Follow the instructions for creating a password file as explained in "Using ORAPWD".
2.

Set the REMOTE_LOGIN_PASSWORDFILE initialization parameter to EXCLUSIVE. (This is the default.)

Note:
REMOTE_LOGIN_PASSWORDFILE is a static initialization parameter and therefore cannot be changed without restarting the database.
3.

Connect with SYSDBA privileges as shown in the following example, and enter the SYS password when prompted:

CONNECT SYS AS SYSDBA

4.

Start up the instance and create the database if necessary, or mount and open an existing database.
5.

Create users as necessary. Grant SYSDBA or SYSOPER privileges to yourself and other users as appropriate. See "Granting and Revoking SYSDBA and SYSOPER Privileges", later in this section.

Granting and Revoking SYSDBA and SYSOPER Privileges

If your server is using an EXCLUSIVE password file, use the GRANT statement to grant the SYSDBA or SYSOPER system privilege to a user, as shown in the following example:

GRANT SYSDBA TO oe;

Use the REVOKE statement to revoke the SYSDBA or SYSOPER system privilege from a user, as shown in the following example:

REVOKE SYSDBA FROM oe;

Because SYSDBA and SYSOPER are the most powerful database privileges, the WITH ADMIN OPTION is not used in the GRANT statement. That is, the grantee cannot in turn grant the SYSDBA or SYSOPER privilege to another user. Only a user currently connected as SYSDBA can grant or revoke another user's SYSDBA or SYSOPER system privileges. These privileges cannot be granted to roles, because roles are available only after database startup. Do not confuse the SYSDBA and SYSOPER database privileges with operating system roles.

See Also:
Oracle Database Security Guide for more information on system privileges
Viewing Password File Members

Use the V$PWFILE_USERS view to see the users who have been granted SYSDBA or SYSOPER system privileges for a database. The columns displayed by this view are as follows:
Column Description
USERNAME This column contains the name of the user that is recognized by the password file.
SYSDBA If the value of this column is TRUE, then the user can log on with SYSDBA system privileges.
SYSOPER If the value of this column is TRUE, then the user can log on with SYSOPER system privileges.

Maintaining a Password File

This section describes how to:

*

Expand the number of password file users if the password file becomes full
*

Remove the password file

Expanding the Number of Password File Users

If you receive the file full error (ORA-1996) when you try to grant SYSDBA or SYSOPER system privileges to a user, you must create a larger password file and regrant the privileges to the users.

Replacing a Password File

Use the following procedure to replace a password file:

1.

Identify the users who have SYSDBA or SYSOPER privileges by querying the V$PWFILE_USERS view.
2.

Delete the existing password file.
3.

Follow the instructions for creating a new password file using the ORAPWD utility in "Using ORAPWD". Ensure that the ENTRIES parameter is set to a number larger than you think you will ever need.
4.

Follow the instructions in "Adding Users to a Password File".

Removing a Password File

If you determine that you no longer require a password file to authenticate users, you can delete the password file and then optionally reset the REMOTE_LOGIN_PASSWORDFILE initialization parameter to NONE. After you remove this file, only those users who can be authenticated by the operating system can perform SYSDBA or SYSOPER database administration operations.

List Users Connected to Oracle Database

2007-10-28T07:36:00.000-07:00

col ip_address format a16

select username,osuser,terminal,
UTL_INADDR.get_host_address(substr(machine,instr(machine,'\')+1)) ip
from v$session
where username is not null order by username,osuser;

Viewing Privilege and Role Information in Oracle 10g Database

2007-10-22T10:32:00.000-07:00

DBA view describes all column object grants in the database. ALL view describes all column object grants for which the current user or PUBLIC is the object owner, grantor, or grantee. USER view describes column object grants for which the current user is the object owner, grantor, or grantee.

DBA_COL_PRIVS

ALL_COL_PRIVS

USER_COL_PRIVS

ALL view lists column object grants for which the current user is object owner or grantor. USER view describes column object grants for which the current user is the grantor.

ALL_COL_PRIVS_MADE

USER_COL_PRIVS_MADE

ALL view describes column object grants for which the current user or PUBLIC is the grantee. USER view describes column object grants for which the current user is the grantee.

ALL_COL_PRIVS_RECD

USER_COL_PRIVS_RECD

DBA view lists all grants on all objects in the database. ALL view lists the grants on objects where the user or PUBLIC is the grantee. USER view lists grants on all objects where the current user is the grantee.

DBA_TAB_PRIVS

ALL_TAB_PRIVS

USER_TAB_PRIVS

ALL view lists the all object grants made by the current user or made on the objects owned by the current user. USER view lists grants on all objects owned by the current user.

ALL_TAB_PRIVS_MADE

USER_TAB_PRIVS_MADE

ALL view lists object grants for which the user or PUBLIC is the grantee. USER view lists object grants for which the current user is the grantee.

ALL_TAB_PRIVS_RECD

USER_TAB_PRIVS_RECD

This view lists all roles that exist in the database.

DBA_ROLES

DBA view lists roles granted to users and roles. USER view lists roles granted to the current user.

DBA_ROLE_PRIVS

USER_ROLE_PRIVS

DBA view lists system privileges granted to users and roles. USER view lists system privileges granted to the current user.

DBA_SYS_PRIVS

USER_SYS_PRIVS

This view describes roles granted to other roles. Information is provided only about roles to which the user has access.

ROLE_ROLE_PRIVS

This view contains information about system privileges granted to roles. Information is provided only about roles to which the user has access.

ROLE_SYS_PRIVS

This view contains information about object privileges granted to roles. Information is provided only about roles to which the user has access.

ROLE_TAB_PRIVS

This view lists the privileges that are currently enabled for the user.

SESSION_PRIVS

This view lists the roles that are currently enabled to the user.

SESSION_ROLES

Predefined Roles in Oracle 9i Enterprise Database

2007-10-17T07:29:00.000-07:00

Roles
Predefined Roles
Along with the installation, more exactly with the creation of an oracle database, Oracle creates predefined roles. These are:

* connect, resource, dba
These might not be created anymore in future versions of Oracle.
Oracle 9.2 grants create session, alter session, create synonym, create view, create database link, create table, create cluster and create sequence to connect.

It also grants create table , create cluster, create sequence, create trigger create procedure, create type, create indextype and create operator to resource.
The role dba gets basically everything and that with admin option.

* delete_catalog_role, execute_catalog_role, select_catalog_role
Accessing data dictionary views (v$ views and static dictionary views)

* exp_full_database, imp_full_database
This role is needed to export objects found in another user's schema.
* aq_user_role, aq_administrator_role, global_aq_user_role(?)
* logstdby_administrator
* snmpagent
* recovery_catalog_owner
* hs_admin_role
* oem_monitor, oem_advisor
* scheduler_admin
* gather_system_statistics
* plustrace
* xdbadmin
* xdbwebservices
* ctxapp

Using DB_VERIFY Utility in Oracle 10g Enterprise Database for identifying block corruption in backup files and live datafiles

2007-10-11T07:24:00.000-07:00

This was in my Alert Log file

Wed Oct 07 22:00:57 2009
GATHER_STATS_JOB encountered errors. Check the trace file.
Wed Oct 07 22:00:57 2009
Errors in file d:\oracle\product\10.2.0\admin\synapse\bdump\synapse_j001_1036.trc:
ORA-01578: ORACLE data block corrupted (file # 1, block # 51522)
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAPSE\SYSTEM01.DBF'

Using Using DB_VERIFY Utility in Command prompt

C:\>dbv file=D:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAPSE\SYSTEM01.DBF

DBVERIFY: Release 10.2.0.4.0 - Production on Thu Oct 8 11:36:18 2009

Copyright (c) 1982, 2007, Oracle. All rights reserved.

DBVERIFY - Verification starting : FILE = D:\ORACLE\PRODUCT\10.2.0\ORADATA\SYNAP
SE\SYSTEM01.DBF
Page 51342 is influx - most likely media corrupt
Corrupt block relative dba: 0x0040c88e (file 1, block 51342)
Fractured block found during dbv:
Data in bad block:
type: 6 format: 2 rdba: 0x0040c88e
last change scn: 0x0000.01f696a1 seq: 0x1 flg: 0x06
spare1: 0x0 spare2: 0x0 spare3: 0x0
consistency value in tail: 0x00345352
check value in block header: 0xb5cc
computed block checksum: 0x82d

Page 51343 is marked corrupt
Corrupt block relative dba: 0x0040c88f (file 1, block 51343)
Bad header found during dbv:
Data in bad block:
type: 3 format: 0 rdba: 0x00000005
last change scn: 0x0003.00020002 seq: 0x0 flg: 0x06
spare1: 0x0 spare2: 0x0 spare3: 0x7010
consistency value in tail: 0x000005d8
check value in block header: 0x3
computed block checksum: 0xe09f

Page 51344 is marked corrupt
Corrupt block relative dba: 0x0040c890 (file 1, block 51344)
Bad header found during dbv:
Data in bad block:
type: 16 format: 2 rdba: 0x000009a8
last change scn: 0x0d78.00000294 seq: 0x0 flg: 0x00
spare1: 0x0 spare2: 0x0 spare3: 0xbd
consistency value in tail: 0x7f00001d
check value in block header: 0x201
block checksum disabled

Page 51345 is marked corrupt
Corrupt block relative dba: 0x0040c891 (file 1, block 51345)
Bad header found during dbv:
Data in bad block:
type: 255 format: 3 rdba: 0x23000000
last change scn: 0xba00.0000fdfb seq: 0x26 flg: 0x01
spare1: 0x2a spare2: 0x1b spare3: 0x100
consistency value in tail: 0x00000000
check value in block header: 0x100
block checksum disabled

Page 51346 is influx - most likely media corrupt
Corrupt block relative dba: 0x0040c892 (file 1, block 51346)
Fractured block found during dbv:
Data in bad block:
type: 0 format: 0 rdba: 0x00000000
last change scn: 0x0000.00000000 seq: 0x0 flg: 0x00
spare1: 0x0 spare2: 0x0 spare3: 0x0
consistency value in tail: 0x00000000
check value in block header: 0x0
block checksum disabled

Page 51347 is marked corrupt
Corrupt block relative dba: 0x0040c893 (file 1, block 51347)
Completely zero block found during dbv:

Page 51381 is marked corrupt
Corrupt block relative dba: 0x0040c8b5 (file 1, block 51381)
Bad check value found during dbv:
Data in bad block:
type: 6 format: 2 rdba: 0x0040c8b5
last change scn: 0x0000.01f73e6b seq: 0x2 flg: 0x04
spare1: 0x0 spare2: 0x0 spare3: 0x0
consistency value in tail: 0x3e6b0602
check value in block header: 0x94a3
computed block checksum: 0x89d9

Page 51522 is marked corrupt
Corrupt block relative dba: 0x0040c942 (file 1, block 51522)
Bad check value found during dbv:
Data in bad block:
type: 6 format: 2 rdba: 0x0040c942
last change scn: 0x0000.01fb92b7 seq: 0x1 flg: 0x06
spare1: 0x0 spare2: 0x0 spare3: 0x0
consistency value in tail: 0x92b70601
check value in block header: 0x1201
computed block checksum: 0x1

DBVERIFY - Verification complete

Total Pages Examined : 66560
Total Pages Processed (Data) : 40487
Total Pages Failing (Data) : 0
Total Pages Processed (Index): 8111
Total Pages Failing (Index): 0
Total Pages Processed (Other): 1929
Total Pages Processed (Seg) : 0
Total Pages Failing (Seg) : 0
Total Pages Empty : 16025
Total Pages Marked Corrupt : 8
Total Pages Influx : 2
Highest block SCN : 33440950 (0.33440950)