One database recovery

I. Solve disk errors
Dmesg errors: EXT3-fs error (device hda3) in start_transaction: Journal has aborted
Mount the partition after an error occurs in umount.
Disk repair: # e2fsck-y-C 0/dev/sdc1

II. Modify the/Oracle/dbs/initdbnms. ora File
*. Undo_management = 'auto'
_ Allow_resetlogs_upload uption = true
_ Uploupted_rollback_segments = (_ syssmu1 $, _ syssmu2 $, _ syssmu3 $)
3. Check for damaged blocks of DBF
DBV file = block. DBF blocksize = 8192
Select open_mode from V $ database;
Select File #, name from V $ datafile where file # = 1;
Select name from V $ rollname;

4. Compile bbed
CD/Oracle/rdbms/lib/ins_rdbms.mk
Make-F ins_rdbms.mk $ ORACLE_HOME/rdbms/lib/bbed
The default password of bbed is blockedit. Please use it with caution. Internal tools

5. Skip the bad block check during startup

1) Add "event =" 10231 trace name context forever, level 10 "to the initialization parameters, and then restart the database.

2) then extract the data with no bad blocks from the table with bad blocks and execute the following statement:
Create Table salvage_emp as select * From corrupt_table;

5. References.
Tune2fs-o ^ has_journal/dev/sdc1

Racker hacker
Words of wisdom from a server administrator EXT3-fs error (device hda3) in start_transaction: Journal has aborted
If your system abruptly loses power, or if a RAID card is beginning to fail, you might see an ominous message like this within your logs:

EXT3-fs error (device hda3) in start_transaction: Journal has aborted

basically, the system is telling you that it's detected a filesystem/Journal mismatch, and it can't utilize the journal any longer. when this situation pops up, the filesystem gets mounted read-only almost immediately. to fix the situation, you can Remount the partition as ext2 (if it isn' t your active root partition), or you can commence the repair operations.
if you're working with an active root partition, you will need to boot into some rescue media and perform these operations there. if this error occurs with an additional partition besides the root partition, simply unmount the broken filesystem and proceed with these operations.
remove the journal from the filesystem (partition tively turning it into ext2):

# tune2fs-o ^ has_journal/dev/hda3
now, you will need to fsck it to correct any possible problems (throw in a-y flag to say yes to all repairs,-C for a progress bar ):
# e2fsck [-y-C 0]/dev/sdc1
once that's finished, make a new journal which between tively makes the partition an ext3 filesystem again
# tune2fs-J/dev/hda3
You shocould be able to mount the partition as an ext3 part Ition at this time:
# Mount-T ext3/dev/hda3/mnt/fixed
be sure to check your dmesg output for any additional errors after you're finished!