Recovery of Frectured block

Oracle 10g 10.2.0.1.0 on win 2003 server both(32 bit)
Problem:
=======
1. select*from v$log;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
1 1 1892 52428800 1 NO INACTIVE 62251690 23-JAN-12
2 1 1893 52428800 1 NO CURRENT 62260537 23-JAN-12
3 1 1891 52428800 1 NO INACTIVE 62231557 23-JAN-12
2.
select*from v$logfile;
GROUP# STATUS TYPE MEMBER
3 STALE ONLINE D:\ORACLE\ORADATA\OLRLFG3\REDO03.LOG
2 ONLINE D:\ORACLE\ORADATA\OLRLFG2\REDO02.LOG
1 ONLINE D:\ORACLE\ORADATA\OLRLFG1\REDO01.LOG
4 STANDBY D:\ORACLE\ORADATA\STANDBY_OLRLFG1\SB_REDO01.LOG
3.
Mon Jan 23 10:53:55 2012
Beginning log switch checkpoint up to RBA [0x765.2.10], SCN: 62260537
Thread 1 advanced to log sequence 1893
Current log# 2 seq# 1893 mem# 0: D:\ORACLE\ORADATA\OLRLFG2\REDO02.LOG
Mon Jan 23 10:59:16 2012
Completed checkpoint up to RBA [0x765.2.10], SCN: 62260537
Mon Jan 23 11:01:00 2012
Hex dump of (file 3, block 29417) in trace file d:\oracle\product\10.2.0\admin\cwo\bdump\cwo_j000_6084.trc
Corrupt block relative dba: 0x00c072e9 (file 3, block 29417)
Fractured block found during buffer read
Data in bad block:
type: 6 format: 2 rdba: 0x00c072e9
last change scn: 0x0000.03b33d6b seq: 0x2 flg: 0x04
spare1: 0x0 spare2: 0x0 spare3: 0x0
consistency value in tail: 0x6b390603
check value in block header: 0x6188
computed block checksum: 0xb0c5
Reread of rdba: 0x00c072e9 (file 3, block 29417) found same corrupted data
Mon Jan 23 11:01:16 2012
Errors in file d:\oracle\product\10.2.0\admin\cwo\bdump\cwo_m000_5884.trc:
ORA-00600: internal error code, arguments: [6002], [6], [6], [5], [0], [], [], []
Mon Jan 23 11:01:20 2012
Hex dump of (file 3, block 37080) in trace file d:\oracle\product\10.2.0\admin\cwo\bdump\cwo_j000_6084.trc
Corrupt block relative dba: 0x00c090d8 (file 3, block 37080)
Fractured block found during buffer read
Data in bad block:
type: 6 format: 2 rdba: 0x00c090d8
last change scn: 0x0000.037f9b2e seq: 0x2 flg: 0x06
spare1: 0x0 spare2: 0x0 spare3: 0x0
consistency value in tail: 0xacb70602
check value in block header: 0xe1cb
computed block checksum: 0x9d1
Reread of rdba: 0x00c090d8 (file 3, block 37080) found same corrupted data
Mon Jan 23 11:01:39 2012
Corrupt Block Found
TSN = 2, TSNAME = SYSAUX
RFN = 3, BLK = 29417, RDBA = 12612329
OBJN = 49890, OBJD = 49890, OBJECT = MGMT_METRICS_1HOUR_PK, SUBOBJECT =
SEGMENT OWNER = SYSMAN, SEGMENT TYPE = Index Segment
Mon Jan 23 11:02:59 2012
Corrupt Block Found
TSN = 2, TSNAME = SYSAUX
RFN = 3, BLK = 37080, RDBA = 12619992
OBJN = 49890, OBJD = 49890, OBJECT = MGMT_METRICS_1HOUR_PK, SUBOBJECT =
SEGMENT OWNER = SYSMAN, SEGMENT TYPE = Index Segment
Mon Jan 23 11:12:58 2012
Incremental checkpoint up to RBA [0x765.aba9.0], current log tail at RBA [0x765.ad03.0]
=======================================
This frectured block is causing problem in RMAN backup.
Please help.

dba mis wrote:
Oracle 10g 10.2.0.1.0 on win 2003 server both(32 bit)
Problem:
=======
1. select*from v$log;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
1 1 1892 52428800 1 NO INACTIVE 62251690 23-JAN-12
2 1 1893 52428800 1 NO CURRENT 62260537 23-JAN-12
3 1 1891 52428800 1 NO INACTIVE 62231557 23-JAN-12
2.
select*from v$logfile;
GROUP# STATUS TYPE MEMBER
3 STALE ONLINE D:\ORACLE\ORADATA\OLRLFG3\REDO03.LOG
2 ONLINE D:\ORACLE\ORADATA\OLRLFG2\REDO02.LOG
1 ONLINE D:\ORACLE\ORADATA\OLRLFG1\REDO01.LOG
4 STANDBY D:\ORACLE\ORADATA\STANDBY_OLRLFG1\SB_REDO01.LOG
3.
Mon Jan 23 10:53:55 2012
Beginning log switch checkpoint up to RBA [0x765.2.10], SCN: 62260537
Thread 1 advanced to log sequence 1893
Current log# 2 seq# 1893 mem# 0: D:\ORACLE\ORADATA\OLRLFG2\REDO02.LOG
Mon Jan 23 10:59:16 2012
Completed checkpoint up to RBA [0x765.2.10], SCN: 62260537
Mon Jan 23 11:01:00 2012
Hex dump of (file 3, block 29417) in trace file d:\oracle\product\10.2.0\admin\cwo\bdump\cwo_j000_6084.trc
Corrupt block relative dba: 0x00c072e9 (file 3, block 29417)
Fractured block found during buffer read
Data in bad block:
type: 6 format: 2 rdba: 0x00c072e9
last change scn: 0x0000.03b33d6b seq: 0x2 flg: 0x04
spare1: 0x0 spare2: 0x0 spare3: 0x0
consistency value in tail: 0x6b390603
check value in block header: 0x6188
computed block checksum: 0xb0c5
Reread of rdba: 0x00c072e9 (file 3, block 29417) found same corrupted data
Mon Jan 23 11:01:16 2012
Errors in file d:\oracle\product\10.2.0\admin\cwo\bdump\cwo_m000_5884.trc:
ORA-00600: internal error code, arguments: [6002], [6], [6], [5], [0], [], [], []
Mon Jan 23 11:01:20 2012
Hex dump of (file 3, block 37080) in trace file d:\oracle\product\10.2.0\admin\cwo\bdump\cwo_j000_6084.trc
Corrupt block relative dba: 0x00c090d8 (file 3, block 37080)
Fractured block found during buffer read
Data in bad block:
type: 6 format: 2 rdba: 0x00c090d8
last change scn: 0x0000.037f9b2e seq: 0x2 flg: 0x06
spare1: 0x0 spare2: 0x0 spare3: 0x0
consistency value in tail: 0xacb70602
check value in block header: 0xe1cb
computed block checksum: 0x9d1
Reread of rdba: 0x00c090d8 (file 3, block 37080) found same corrupted data
Mon Jan 23 11:01:39 2012
Corrupt Block Found
TSN = 2, TSNAME = SYSAUX
RFN = 3, BLK = 29417, RDBA = 12612329
OBJN = 49890, OBJD = 49890, OBJECT = MGMT_METRICS_1HOUR_PK, SUBOBJECT =
SEGMENT OWNER = SYSMAN, SEGMENT TYPE = Index Segment
Mon Jan 23 11:02:59 2012
Corrupt Block Found
TSN = 2, TSNAME = SYSAUX
RFN = 3, BLK = 37080, RDBA = 12619992
OBJN = 49890, OBJD = 49890, OBJECT = MGMT_METRICS_1HOUR_PK, SUBOBJECT =
SEGMENT OWNER = SYSMAN, SEGMENT TYPE = Index Segment
Mon Jan 23 11:12:58 2012
Incremental checkpoint up to RBA [0x765.aba9.0], current log tail at RBA [0x765.ad03.0]
=======================================
This frectured block is causing problem in RMAN backup.
Please help.But more than this you have
ORA-00600: internal error code, arguments: [6002], [6], [6], [5], [0], [], [], []in your database.If this is production site Contact MOS immediately

Similar Messages

HT201413 My iPhone 4's password protection is locked and is in recovery mode. The recovery download is blocked because of the password and I am unable to enter it. How can find no way to bypass the password stored on my phone?

How can I bypass or disable my pass word on my iPhone 4 when it is in recovery and I cannot access the password locked phone to unlock it?

See Here > http://support.apple.com/kb/HT1808
You may need to try this More than Once...
But... if the Device has been Modified... this will Not necessarily work.

ORA-01172: recovery of thread 1 stuck at block 1340 of file 2

Database Version: Oracle 10G rel 10.02
OS:- Windows XP SP2.
Scenario:- Trying to open the database .
Error:-
SQL> startup open;
ORACLE instance started.
Total System Global Area 272629760 bytes
Fixed Size 1248476 bytes
Variable Size 100664100 bytes
Database Buffers 163577856 bytes
Redo Buffers 7139328 bytes
Database mounted.
ORA-01172: recovery of thread 1 stuck at block 1340 of file 2
ORA-01151: use media recovery to recover block, restore backup if needed
Please advise.

SQL> select name,status,enabled from v$datafile where file#=2;
NAME
STATUS ENABLED
D:\ORADATA\ORCL\UNDOTBS01.DBF
ONLINE READ WRITE

Doing Block Recovery of a Table

Hello,
We have to do a single block recovery of a table on Oracle 10gR2 Solaris machine.
One of the archive was missing or corrupted.
I was trying to do block recovery from the backup of 3 days. But it is applying all the archives and after that errors out saying media recovery failure due to missing/corrupt archive log.
I have tried until scn , until sysdate-2 , using tag tagname etc....
But in all the situations it is applying archive logs and giving media recovery failure.
Is there any way I can only apply certain archive logs or do until a point in time of recovery of that single block.
or just get the block from the backup and not apply the archive logs.
Thanks

Street Hawk wrote:
Then you have to forget that block.
OR
you will have to do an incomplete recoveryI have to say that its "really wrong". How would you do an incomplete recovry of a corrupted block?
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc2.htm#i1008221
>
Note these restrictions of block media recovery:
You can only perform block media recovery with RMAN. No SQL*Plus recovery interface is available.
You can only perform complete recovery of individual blocks. In other words, you cannot stop recovery before all redo has been applied to the block.
You can only recover blocks marked media corrupt. The V$DATABASE_BLOCK_CORRUPTION view indicates which blocks in a file were marked corrupt since the most recent BACKUP or BACKUP ... VALIDATE command was run against the file.
You must have a full RMAN backup. Incremental backups are not used by block media recovery. Proxy backups are also not used by block media recovery. Only full backups and archived log files are used.
Block media recovery is able to restore blocks from parent incarnation backups and recover the corrupted blocks through a RESETLOGS.
Blocks that are marked media corrupt are not accessible to users until recovery is complete. Any attempt to use a block undergoing media recovery results in an error message indicating that the block is media corrupt.>
Flashback also is WRONG suggestion. It recovers your logical changes,not the physcial corruptions like block failure and you don't need to enable it. Its there by default. The flashback database option has to be enabled. But putting the whole database back in past , just because a block is corrupted , is that a wise thing to do?
@OP,
If you don't have all the archive logs, I would suggest to repair the block using [dbms_repair|http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_repair.htm] package. Note that the name of the package is "misleading".
HTH
Aman....

Data Block Corruption

I'm on 9i R2 Patch 7 on a Microsoft Windows Server 2003.
How do you fix data block corruption in a Table?
Is the some way to retrieve the data from the Table drop it then recreate and reimport the data?
or do you have to succumb with restoring the Database from the last known good backup?

Hey, you can do the BMR (Block Media Recovery).
Since block corruption is to few subsets of blocks, i.e. a single table, you dont need to restore from the previous valid backup, you can simply do the following to achieve BMR.
Connect to rman and run the following:
run{ backup validate database};
Once the above commend is finishes, exit from RMAN and connect to the database as / as sysdba and use the following view to know the details required for BMR.
select * from V$backup_corruption;
The above queries gives you file# and block# information. Once you have the information do the BMR using following command at the RMAN prompt:
run {blockrecover datafile # block #};
# : indicated the datafile number and block number from the above view.
Let me know if you have any further issues.
You can also use view V$DATABASE_BLOCK_CORRUPTION to view the file# and corrupted blocks information.
Jaffar

Block corruption - cant restore from backup

Hi,
we have development database 11.2.0.1. There was problem with storage, and as a result there are two corrupted blocks in data files.
SQL> select * from V$DATABASE_BLOCK_CORRUPTION;
FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTIO
6 2359942 1 0 FRACTURED
25 1855622 1 0 FRACTURED
I have scheduled weekly full backup and daily incremental backup using EM so now I want to use rman to perform media recovery on corrupted blocks. However rman says there is no backup for affected data files (see below)
RMAN> RECOVER CORRUPTION LIST;
Starting recover at 03-NOV-12
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_DISK_4
using channel ORA_DISK_5
channel ORA_DISK_1: restoring block(s)
channel ORA_DISK_1: specifying block(s) to restore from backup set
restoring blocks of datafile 00006
channel ORA_DISK_1: reading from backup piece /opt/oraBackup/rman/i2npb3o9_1_1
channel ORA_DISK_1: piece handle=/opt/oraBackup/rman/i2npb3o9_1_1 tag=BACKUP_FULL_110212103009
channel ORA_DISK_1: restored block(s) from backup piece 1
channel ORA_DISK_1: block restore complete, elapsed time: 00:42:35
channel ORA_DISK_1: restoring block(s)
channel ORA_DISK_1: specifying block(s) to restore from backup set
restoring blocks of datafile 00025
channel ORA_DISK_1: reading from backup piece /opt/oraBackup/rman/i9npbd5e_1_1
channel ORA_DISK_1: piece handle=/opt/oraBackup/rman/i9npbd5e_1_1 tag=BACKUP_FULL_110212103009
channel ORA_DISK_1: restored block(s) from backup piece 1
channel ORA_DISK_1: block restore complete, elapsed time: 00:16:35
failover to previous backup
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 11/03/2012 11:59:29
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 25 found to restore
RMAN-06023: no backup or copy of datafile 6 found to restore
I dont understand this, because the backups are performed weekly and daily and all files are at their proper location. When I check the EM backup reports, I see COMPLETED for every weekly and daily backup.
Anyone please could suggest how to repair the blocks from backups ?

Hi people, I am back to this issue. I have found this in the database
SQL> select * from v$backup_corruption;
     RECID      STAMP SET_STAMP SET_COUNT     PIECE#      FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# MAR CORRUPTIO
         1 796949262 796948233       9293          1          6    2359942          1                  0 NO CORRUPT
         2 796953328 796949174       9300          1         25    1855622          1                  0 NO CORRUPT
         3 797035604 797034635       9318          1          6    2359942          1                  0 NO CORRUPT
         4 797039692 797035556       9325          1         25    1855622          1                  0 NO CORRUPT
         5 797134390 797121030       9343          1          6    2359942          1                  0 NO CORRUPT
         6 797137228 797134397       9368          1         25    1855622          1                  0 NO CORRUPT
         7 797739951 797725854       9590          1          6    2359942          1                  0 NO CORRUPT
         8 797744507 797739957       9597          1         25    1855622          1                  0 NO CORRUPT
         9 798340269 798330633       9794          1          6    2359942          1                  0 NO CORRUPT
        10 798343497 798340270       9801          1         25    1855622          1                  0 NO CORRUPTSo the backup contains corrupted blocks. Right ? Older backups are already gone because of retention policy.
I have set up the backup using Enterprise Manager - Schedule Backup.
What I need to know is how to avoid taking backup with corrupted blocks in future. I need such backup to fail.
Thank you for advices and regards.

ORA-01172: Recovery of thread 1 stuck at...

My db got corrupted, and I'm having the following issue when opening it:
ORA-01172: recovery of thread 1 stuck at block 31823 of file 2
ORA-01151: use media recovery to recover block, restore backup if neededI did the following... but am now stuck. I accidentally entered a newline when I was supposed to specify the log file (I guess?). Any help would be great. Thanks!
SQL> recover database until cancel;
ORA-00279: change 12390169168251 generated at 06/26/2012 09:41:48 needed for
thread 1
ORA-00289: suggestion :
C:\APP\GRExxxxxxx\FLASH_RECOVERY_AREA\MYDB\ARCHIVELOG\2012_06_27\O1_MF_1_1
27_%U_.ARC
ORA-00280: change 12390169168251 for thread 1 is in sequence #127
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'C:\APP\GRExxxxxxx\FLASH_RECOVERY_AREA\MYDB\ARCHIVELOG\2012_06_27\O1_MF_1_
127_%U_.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-10879: error signaled in parallel recovery slave
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'C:\APP\GRExxxxxxx\ORADATA\MYDB\SYSTEM01.DBF'

Hi,
speicfy the logs as it requested to complete the recovery (it might ask you for online redo based on you crash/scn), if you are not left over with any archives with recovery then you cancel the recover and open the database with
reset logs
- Pavan Kumar N

Blocked WIndows Serial Key

Dear Respected,
I have purchased this HP envy laptop (15-j050tx) and somehow I lost my recovery partition. Now I did a clean installation of Windows 8.1 (64-but) using Windows Media recovery tool but it is not accepting the serial Key embedded in BIOS / Motherboard. Windows is telling me that my recovery key is blocked. Yesterday talking to a Microsoft agent he told me that my windows serial key is blocked by manufacturer (HP). I donot know why HP blocked my serial key. I want to use embedded windows serial or when I install other software (Windows 8.1 Pro) downloaded from my university MSDN link it does not work and my system always fall in problems (may be getting a conflict with motherboard serial key or something else). Kindly help me in this regard and please tell me the way how can HP unblock my serial key so I can use it.
Saluti,

Hi
There is no benefit in opening a new thread again.
Your issue has been already escalated by me and someone from HP would be soon looking into it. Be patient and wait.
Please don't create a new that regarding this issue and make a confusion out of it.
See this thread:
http://h30434.www3.hp.com/t5/Notebook-Recovery/HP-envy-15-j050tx-recovery-usb/td-p/4898173/page/2
Regards
Visruth
++Please click KUDOS / White thumb to say thanks
++Please click ACCEPT AS SOLUTION to help others, find this solution faster
**I'm a Volunteer, I do not work for HP**

Creating Vista Recovery disk on Portege M400

I have upgraded an M400 which came with XP to Vista Business. Launching the Toshiba Recovery Disk utility delivers a message "not HDD partition found". The management console shows a recovery partition - though it probably still has the XP recovery info.
Anybody got ideas on how to transfer in a Vista recovery image into this partition? Is this available from Toshiba somewhere in the world? I can get my tech support people to chase it if we know it exists....
Cheers
From Australia

Hi,
maybe you should properly format the drive and remove ALL partitions with an external program (like UBCD -> "Ultimate Boot CD") and then try it again.
It can be that the XP recovery partition is blocking the new recovery/installation process.
If I were you I would try this format-thingy.
Otherwise grab another HDD and try it with this. ;)
Cheers

Recovery Manager Windows 10

Having Upgraded to windows 10 from Windows 7 Home Edition, I am also planning to upgrade my hardware (memory 4G>8G and an SSD). The SSD being a bit smaller in capacity(240gigs) than my installed drive (441 C drive +19.69 D recovery partition or about 461 gigs), I am trying to eliminate anything unneeded on the drive. I wanted to create a recovery disk &/or image on one of my NAS drives so that I can safely delete the D partition, but cannot find the HP Recovery Manager. I have learned that many people are finding that the Recovery Manager is blocked in Windows 10 because of an expired security certificate, but I can't even find the Recovery Manager. I'm probably going to stick with Windows 10, but I want to err on the side of caution and keep a way to recover my system, just in case. I could create an image of my whole system myself and save it to an .iso file on one of my 2T hard drives, but I'd like to be able to use the HP Recovery Manager if at all possible. Is it?

Recovery partiton contains windows 8.1 - It will create only recovery of windows 8.1 even if you install Windows 10 or 8 or 7.The windows 10 copy that you will get is from microsoft and not HP and its free.so if you ever need to re-install, you will have to install windows 8.1 and then perform the upgrade again. You can also download the win10 ISO and burn it to a disc or create a bootable USB Flash Drive to install from and use your microsoft account to activate win10.

En-Countering Error While trying to Open the Database

Hi Everybody,
Database Version:Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit Production
Os: Solaris9
This is one of our Test Database which is running in No-Archivelog Mode and having no backup of Physical Datafiles.
Due to some Server issues the Database was Shutdown Abnormally after which when we are trying to open our DB it showing the following Error......
ORA-01172: recovery of thread 1 stuck at block 13447 of file 216
ORA-01151: use media recovery to recover block, restore backup if needed....
we are also not able to perform a media recovery since the database is running in No-Archivelog Mode....
The only way we know to bring up the Database is making the Datafile=216 offline and opening the Database...
In there any workaround in order to resolve the Block corruption of Data-File 216........Since we will be needing the data located in datafile 216.
Any help Appreciated,
Thanks & Regards,
Prosenjit Mukherjee

DBVERIFY: Release 9.2.0.4.0 - Production on Thu Feb 26 15:37:47 2009
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
DBVERIFY - Verification starting : FILE = /sts/oradata/npm/sts/STPUSER10.dbf
DBVERIFY - Verification complete
Total Pages Examined : 98304
Total Pages Processed (Data) : 97673
Total Pages Failing (Data) : 0
Total Pages Processed (Index): 1
Total Pages Failing (Index): 0
Total Pages Processed (Other): 570
Total Pages Processed (Seg) : 0
Total Pages Failing (Seg) : 0
Total Pages Empty : 60
Total Pages Marked Corrupt : 0
Total Pages Influx : 0
This is the Output of the Dbverify Utility,but as i can see "Total Pages Marked Corrupt : 0"
its telling me that neither of the blocks are corrupted......
Earlier when i was trying to do a Recovery it was giving me the Following Error....
ORA-01172: recovery of thread 1 stuck at block 13447 of file 216
ORA-01151: use media recovery to recover block, restore backup if needed.........

Error while Loggin into Database

Hello,
As i am entering my username & password m getting an Error..
" ORA-01033: ORACLE initialization or shutdown in progress "
Then i found few suggestions related to this error .. & some steps to rectify this.. & the Result i got is ..
C:\>sqlplus /nolog
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Dec 15 14:34:25 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> connect sys/manager as sysdba
Connected.
SQL>
SQL> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL>
SQL>
SQL> startup
ORACLE instance started.
Total System Global Area 251658240 bytes
Fixed Size 1248380 bytes
Variable Size 83886980 bytes
Database Buffers 163577856 bytes
Redo Buffers 2945024 bytes
Database mounted.
ORA-01172: recovery of thread 1 stuck at block 59 of file 2
ORA-01151: use media recovery to recover block, restore backup if needed.
i am very new to this ... please suggest me some solution

Aijaz Mallick wrote:
Hello Robert,
Can you plz give me the steps for recovering datafile 2.. i am very new to thisRobert has already given you the command :)
It's RMAN command. If you have taken RMAN backup of the database, you will be able to recover that file using that command :
RMAN>RECOVER DATAFILE 2;- - - - - - - - - - - - - - - - - - - - -
[Kamran Agayev A. |http://kamranagayev.wordpress.com] (OCP 9i/10g)
Author of *"Oracle Backup & Recovery: Expert secrets for using RMAN and Data Pump"*
http://www.rampant-books.com/book_1002_rman_backup_recovery.htm

XE Database Dead?

Hello. I'm not very knowledgeable when it comes to DBA work, but I've hit a snag and would appreciate a little advice. I have an Oracle XE install on my home computer for keeping track of business receipts and such. Recently I couldn't connect to APEX and started looking into it. When I tried to connect with SQL+, I would get the message:
ERROR:
OR-01033: ORACLE initialization or shutdown in progress
So I stopped and started the DB, checked to see the listener service was going, and still have the issue. I checked my alert_xe.log file, and it's... huge. Attached at the bottom, I included a fragment of my log file that consists of the last recent timestamp.
I do have a script that runs on my computer that does an EXP every night on my schema, but if I try an IMP, I get the same message (which makes sense since my DB apparently isn't running).
What would be your suggestions? I wanted some advice before I uninstalled and re-installed then imported my dmp backups.
Thanks to any necromancers who can help me bring this back from the dead!
Kerry.
Dump file e:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Thu Oct 29 20:40:40 2009
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows XP Version V5.1 Service Pack 2
CPU : 1 - type 586
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:211M/511M, Ph+PgF:1012M/1247M, VA:1945M/2047M
Thu Oct 29 20:40:40 2009
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Thu Oct 29 20:40:52 2009
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
sessions = 49
__shared_pool_size = 104857600
__large_pool_size = 8388608
__java_pool_size = 4194304
__streams_pool_size = 0
spfile = E:\ORACLEXE\APP\ORACLE\PRODUCT\10.2.0\SERVER\DBS\SPFILEXE.ORA
sga_target = 146800640
control_files = E:\ORACLEXE\ORADATA\XE\CONTROL.DBF
__db_cache_size = 25165824
compatible = 10.2.0.1.0
db_recovery_file_dest = E:\oraclexe\app\oracle\flash_recovery_area
db_recovery_file_dest_size= 10737418240
undo_management = AUTO
undo_tablespace = UNDO
remote_login_passwordfile= EXCLUSIVE
dispatchers = (PROTOCOL=TCP) (SERVICE=XEXDB)
shared_servers = 4
job_queue_processes = 4
audit_file_dest = E:\ORACLEXE\APP\ORACLE\ADMIN\XE\ADUMP
background_dump_dest = E:\ORACLEXE\APP\ORACLE\ADMIN\XE\BDUMP
user_dump_dest = E:\ORACLEXE\APP\ORACLE\ADMIN\XE\UDUMP
core_dump_dest = E:\ORACLEXE\APP\ORACLE\ADMIN\XE\CDUMP
db_name = XE
open_cursors = 300
os_authent_prefix =
pga_aggregate_target = 41943040
PSP0 started with pid=3, OS id=2988
MMAN started with pid=4, OS id=2992
PMON started with pid=2, OS id=2984
DBW0 started with pid=5, OS id=3004
LGWR started with pid=6, OS id=3008
CKPT started with pid=7, OS id=3012
SMON started with pid=8, OS id=3016
RECO started with pid=9, OS id=3020
CJQ0 started with pid=10, OS id=3024
MMON started with pid=11, OS id=3028
MMNL started with pid=12, OS id=3032
Thu Oct 29 20:40:55 2009
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 4 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Thu Oct 29 20:41:00 2009
alter database mount exclusive
Thu Oct 29 20:41:05 2009
Setting recovery target incarnation to 2
Thu Oct 29 20:41:05 2009
Successful mount of redo thread 1, with mount id 2582644764
Thu Oct 29 20:41:05 2009
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Thu Oct 29 20:41:05 2009
alter database open
Thu Oct 29 20:41:06 2009
Beginning crash recovery of 1 threads
Thu Oct 29 20:41:06 2009
Started redo scan
Thu Oct 29 20:41:07 2009
Completed redo scan
9180 redo blocks read, 514 data blocks need recovery
Thu Oct 29 20:41:07 2009
Started redo application at
Thread 1: logseq 797, block 5520
Thu Oct 29 20:41:09 2009
Recovery of Online Redo Log: Thread 1 Group 2 Seq 797 Reading mem 0
Mem# 0 errs 0: E:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_2MXYQN2G_.LOG
RECOVERY OF THREAD 1 STUCK AT BLOCK 28 OF FILE 2
Thu Oct 29 20:41:11 2009
Aborting crash recovery due to error 1172
Thu Oct 29 20:41:11 2009
Errors in file e:\oraclexe\app\oracle\admin\xe\udump\xe_ora_3080.trc:
ORA-01172: recovery of thread 1 stuck at block 28 of file 2
ORA-01151: use media recovery to recover block, restore backup if needed
ORA-1172 signalled during: alter database open...
Thu Oct 29 20:55:05 2009
db_recovery_file_dest_size of 10240 MB is 0.98% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Thu Oct 29 22:50:17 2009
WARNING: inbound connection timed out (ORA-3136)

Billy Verreynne wrote:
Kamran Agayev A. wrote:
Let it be a lesson for you to take RMAN backup of your database and to be able to recover your database from almost any situation you areOn XE.. by an end-user with very little to no Oracle experience, never mind DBA experience!? Come on! That is a totally unrealistic expectation on your part.
Rather think how you can assist an end-user with an XE database to make regular backups of his database in case of a problem. Be constructive instead of pointing a finger and go "+lesson must be learned+".
What do you think he should be doing for backups? Run schema exports? If so, how does he backup APEX applications? DB exports? Rman? Run the database in archive log mode?
Remember, that XE is fully an end-user environment. That is the market that Oracle choose to aim XE at.. and that is the market that our "solutions" offered here should be aimed at.Hi Billy
As it's written in doc which Forstmann has suggested, it's possible to use RMAN in XE database. You're right, may be it's not so simple to make backups directly from RMAN utility, but it's possible:
In Oracle Database XE, the database backup and recovery facility is based upon the Recovery Manager (RMAN) utility that is integrated into the database. Although there is an RMAN command line client similar to SQL Command Line, you do not need to interact with it directly to back up or restore your database. Oracle Database XE includes backup and restore scripts that you access using menu choices on your desktop. These scripts perform a full backup and restore of the entire database, and store backup files in the flash recovery area
Just my 2 cents
P.S.By google-ing I've found a blog post for backing up XE and APEX. Hope this article might be helpful for OP
http://beyondoracle.wordpress.com/2008/06/19/basic-oraclexe-apex-backup/
Edited by: Kamran Agayev A. on Oct 30, 2009 12:16 PM

How unhealthy is this RAC?

Here's is the contents of v$system_event..
Is this
EVENT     TOTAL_WAITS     TIME_WAITED     AVERAGE_WAIT
enq: TX - index contention     40564851     214701526      5.29
enq: TX - row lock contention     188846     12454614     65.95
enq: SQ - contention     141971     70568     0.5
cause for concern?
EVENT     TOTAL_WAITS     TIME_WAITED     AVERAGE_WAIT
SQL*Net message to client     6015051449     607254     0
SQL*Net message from client     6015048542     178177969892     29.62
gcs remote message     2948555287     2633481757     0.89
CGS wait for IPC msg     1517805027     634397     0
db file sequential read     1500615188     816364485     0.54
ges remote message     1247679701     1407300224     1.13
gc cr multi block request     778432813     9913464     0.01
gc current block 2-way     747852637     38030616     0.05
db file scattered read     709428365     460939295     0.65
rdbms ipc message     708473316     37650068633     53.14
gc buffer busy acquire     671285134     1033621285     1.54
PX Deq: reap credit     667784615     484449     0
gcs log flush sync     592376026     171712257     0.29
gc cr block 2-way     530861847     19607062     0.04
library cache pin     437937120     15126237     0.03
log file sync     379523272     797193932     2.1
DIAG idle wait     359607166     2822108755     7.85
log file parallel write     351225436     259263769     0.74
LNS ASYNC end of log     350170653     1398410516     3.99
LNS wait on SENDREQ     321652621     3209301     0.01
PX qref latch     297396661     94308     0
read by other session     289140108     148440270     0.51
buffer deadlock     163505781     983055     0.01
gc current block busy     119223825     467716658     3.92
PX Deq: Table Q Normal     117332841     23574867     0.2
ksxr poll remote instances     110480324     90333     0
buffer busy waits     106938153     19933900     0.19
direct path read     93429599     108427028     1.16
SQL*Net more data from client     86471785     23026529     0.27
gc current grant busy     84978157     28215346     0.33
control file sequential read     82646297     23694583     0.29
PX Deq Credit: send blkd     78641669     9569299     0.12
latch: cache buffers chains     74218671     690277     0.01
gc current grant 2-way     72557796     1920419     0.03
library cache: mutex X     71106697     75993     0
DFS lock handle     70722498     2716407     0.04
gc cr grant 2-way     64558237     1633004     0.03
PX Deq: Execution Msg     61706261     314222076     5.09
gc cr block busy     61469863     119850802     1.95
library cache lock     52428649     3773354     0.07
PX Deq: Slave Session Stats     48040224     1886805     0.04
db file parallel read     46415188     118467902     2.55
IPC send completion sync     46250594     965101     0.02
enq: TX - index contention     40564851     214701526     5.29
PX Deq: Execute Reply     39689685     17243721     0.43
gc buffer busy release     36976909     242714774     6.56
SQL*Net more data to client     36627952     44167     0
PX Deq: Msg Fragment     30501244     343397     0.01
rdbms ipc reply     29725302     1352370     0.05
RMAN backup & recovery I/O     28824547     37722662     1.31
reliable message     27892263     3082134     0.11
PX Idle Wait     27356097     4651277341     170.03
ASM file metadata operation     25098749     8850323     0.35
gc object scan     22705857     7485     0
db file parallel write     19896252     52152606     2.62
latch: ges resource hash list     19336183     427451     0.02
enq: PS - contention     19143961     707455     0.04
PX Deq: Parse Reply     19093356     895799     0.05
gc cr disk read     17816846     448909     0.03
ASM background timer     16101806     1383957874     85.95
PX Deq: Slave Join Frag     16044789     233149     0.01
wait for unread message on broadcast channel     15056320     1413552546     93.88
cursor: mutex X     13435193     24140     0
KJC: Wait for msg sends to complete     13268497     11397     0
PX Deq: Signal ACK RSG     13214824     101941     0.01
KSV master wait     13206286     4235645     0.32
direct path read temp     12617694     5487608     0.43
PX Deq Credit: need buffer     11675868     879967     0.08
row cache lock     11536185     398216     0.03
PX Deq Credit: Session Stats     9480862     78910     0.01
SQL*Net message to dblink     9312894     1538     0
SQL*Net message from dblink     9312894     6279631     0.67
control file parallel write     7760982     11854435     1.53
pmon timer     7558889     1412576090     186.88
PX Deq: Join ACK     7548816     498931     0.07
gc current multi block request     6035173     155898     0.03
PING     5706961     1413230267     247.63
enq: XR - database force logging     4662671     198813     0.04
class slave wait     4561877     7097429006     1555.81
Streams AQ: waiting for messages in the queue     4495828     1543411682     343.3
SQL*Net more data from dblink     3696582     444575     0.12
LGWR wait for redo copy     3655353     17840     0
log file sequential read     3387305     6610414     1.95
Log archive I/O     2990486     276772     0.09
SQL*Net break/reset to client     2971976     2385935     0.8
direct path write temp     2839390     2522114     0.89
Space Manager: slave idle wait     2827526     1412987186     499.73
latch: shared pool     2808517     298150     0.11
latch: gc element     2421717     24688     0.01
SGA: MMAN sleep for component shrink     2336447     2458094     1.05
latch: enqueue hash chains     2279645     15435     0.01
latch free     2089418     78732     0.04
gc current split     2044784     1864009     0.91
PX Deq: Signal ACK EXT     1976164     19263     0.01
enq: FB - contention     1473469     61036     0.04
cursor: pin S wait on X     1313129     1464789     1.12
SQL*Net more data to dblink     1232891     986     0
Streams AQ: RAC qmn coordinator idle wait     1211300     788     0
enq: HW - contention     1175390     2077008     1.77
latch: session allocation     1167768     21883     0.02
Streams AQ: qmn coordinator idle wait     1144699     1412546634     1233.99
Streams AQ: qmn slave idle wait     1031585     2227183681     2158.99
lock deadlock retry     962937     4698     0
enq: CF - contention     956154     609647     0.64
latch: cache buffers lru chain     902764     37552     0.04
latch: object queue header operation     817911     27717     0.03
global enqueue expand wait     768633     654105     0.85
Data file init write     756191     329758     0.44
latch: gcs resource hash     647021     4147     0.01
local write wait     603007     286191     0.47
latch: row cache objects     599358     6453     0.01
ges lmd/lmses to freeze in rcfg - mrcvr     481759     156345     0.32
shared server idle wait     471190     1413238589     2999.3
enq: RF - DG Broker Current File ID     469833     23209     0.05
smon timer     432383     1411851085     3265.28
SGA: allocation forcing component growth     363333     379008     1.04
gc current retry     341104     1121252     3.29
enq: RF - synch: DG Broker metadata     319143     588290     1.84
enq: PG - contention     313659     14830     0.05
enq: TT - contention     260134     11207172     43.08
enq: KO - fast object checkpoint     236745     820808     3.47
dispatcher timer     236637     1413242481     5972.2
direct path write     231382     191008     0.83
cursor: pin S     229011     394     0
Streams AQ: waiting for time management or cleanup tasks     199981     1413148548     7066.41
enq: TX - row lock contention     188846     12454614     65.95
enq: TX - allocate ITL entry     153703     54252     0.35
enq: SQ - contention     141971     70568     0.5
ksdxexeother     141885     56     0
latch: redo allocation     138912     1858     0.01
recovery area: computing applied logs     126415     45925     0.36
gc current block congested     126318     21768     0.17
resmgr:cpu quantum     123074     151384     1.23
jobq slave wait     120678     35574221     294.79
Datapump dump file I/O     90431     9127     0.1
ges inquiry response     89402     4041     0.05
os thread startup     83809     222586     2.66
cr request retry     80062     71896     0.9
PX Deq: Table Q Sample     79665     133402     1.67
gc cr block congested     79026     14792     0.19
gc cr failure     77521     25019     0.32
enq: WF - contention     73983     825388     11.16
enq: TQ - TM contention     72871     3319     0.05
lock escalate retry     65714     1574     0.02
buffer exterminate     59775     64919     1.09
fbar timer     47136     1413183353     29980.98
log file switch completion     46911     452097     9.64
recovery area: computing obsolete files     45699     8547     0.19
enq: US - contention     40401     8805     0.22
enq: TM - contention     39149     5435032     138.83
library cache load lock     36311     382575     10.54
kjbdrmcvtq lmon drm quiesce: ping completion     31668     47443     1.5
enq: TD - KTF dump entries     31468     1424     0.05
enq: RO - fast object reuse     28422     31772     1.12
parallel recovery slave wait for change     27558     3163     0.11
name-service call wait     23694     181533     7.66
control file single write     22375     1624     0.07
kksfbc child completion     21239     106926     5.03
PX Deq: Table Q qref     19325     245     0.01
enq: TX - contention     18805     113253     6.02
latch: messages     17203     181     0.01
enq: RS - prevent file delete     16913     1013     0.06
enq: RS - prevent aging list update     15682     642     0.04
PX Deq: Table Q Get Keys     14322     42935     3
gc current grant congested     14292     2192     0.15
cursor: mutex S     13285     8     0
log file single write     13164     5371     0.41
latch: undo global data     12649     178     0.01
kksfbc research     11894     12680     1.07
parallel recovery slave idle wait     11193     5872     0.52
wait list latch free     11026     11794     1.07
enq: CT - state     11001     417     0.04
latch: checkpoint queue latch     10526     132     0.01
enq: PE - contention     10506     1139     0.11
ARCH wait on SENDREQ     9957     216480     21.74
gc cr grant congested     9465     1584     0.17
wait for scn ack     9377     3155     0.34
enq: TA - contention     8856     324     0.04
log buffer space     8777     89323     10.18
enq: TK - Auto Task Serialization     8542     343     0.04
enq: DR - contention     7842     323     0.04
process diagnostic dump     7707     2072     0.27
JOX Jit Process Sleep     7612     11286431     1482.72
enq: TC - contention     7357     340817     46.33
ges global resource directory to be frozen     7140     12299     1.72
enq: CO - master slave det     6850     312     0.05
enq: JS - job run lock - synchronize     6704     397     0.06
gcs drm freeze in enter server mode     6542     40742     6.23
enq: TS - contention     5959     89332     14.99
ARCH wait for archivelog lock     5600     36     0.01
PX Nsq: PQ load info query     5377     104798     19.49
db file single write     5373     3452     0.64
gc remaster     5315     50625     9.52
latch: parallel query alloc buffer     4939     1906     0.39
enq: TO - contention     4799     143     0.03
enq: AF - task serialization     4395     161     0.04
enq: PI - contention     4251     163     0.04
ges2 LMON to wake up LMD - mrcvr     4210     28     0.01
enq: DL - contention     3889     239     0.06
kjctssqmg: quick message send wait     3408     22     0.01
LNS wait on DETACH     3275     741     0.23
ksfd: async disk IO     3274     1     0
LNS wait on ATTACH     3273     51940     15.87
ARCH wait on DETACH     3231     714     0.22
ARCH wait on ATTACH     3226     43238     13.4
enq: BR - file shrink     2787     116     0.04
write complete waits     2631     1070     0.41
enq: MD - contention     2596     67     0.03
enq: WL - contention     2198     266518     121.25
single-task message     2098     25896     12.34
enq: OD - Serializing DDLs     2054     66     0.03
resmgr:internal state change     2001     14735     7.36
ARCH wait on c/f tx acquire 2     1751     175230     100.07
enq: WR - contention     1636     69     0.04
latch: cache buffer handles     1610     29     0.02
statement suspended, wait error to be cleared     1497     22626     15.11
Streams AQ: qmn coordinator waiting for slave to start     1214     678966     559.28
enq: PD - contention     1182     33     0.03
JS kgl get object wait     1096     4922     4.49
undo segment extension     1070     10065     9.41
PL/SQL lock timer     949     8739819     9209.5
enq: AE - lock     937     28     0.03
LGWR-LNS wait on channel     832     913     1.1
ges DFS hang analysis phase 2 acks     816     495     0.61
latch: redo writing     729     9     0.01
gc quiesce     665     564     0.85
enq: JS - queue lock     482     2111     4.38
PX Deq: Test for credit     442     13     0.03
enq: SS - contention     386     274     0.71
recovery area: computing dropped files     328     1400     4.27
recovery area: computing backed up files     328     496     1.51
ksdxexeotherwait     279     10592     37.97
log switch/archive     250     137570     550.28
gc domain validation     223     39964     179.21
auto-sqltune: wait graph update     195     96514     494.95
wait for a undo record     170     1214     7.14
parallel recovery coord send blocked     168     4     0.02
enq: JS - wdw op     168     3741     22.27
enq: KT - contention     165     5     0.03
switch logfile command     156     6290     40.32
gcs resource directory to be unfrozen     149     12839     86.17
Data Guard Broker Wait     139     10906     78.46
enq: SK - contention     129     4     0.03
enq: JS - job recov lock     128     4     0.03
gc cr block lost     125     6772     54.17
virtual circuit wait     122     3     0.03
ges LMON to get to FTDONE      100     187     1.87
enq: CU - contention     80     242     3.02
enq: JQ - contention     78     7     0.09
cursor: pin X     73     83     1.14
parallel recovery coord wait for reply     70     510     7.29
PX Deq: Txn Recovery Start     67     3436     51.29
SQL*Net break/reset to dblink     60     0     0
gc current block lost     57     2869     50.33
ges LMD suspend for testing event     51     709     13.89
inactive session     46     4550     98.91
recovery read     45     5     0.11
JS kill job wait     41     3548     86.53
enq: AS - service activation     40     1     0.03
enq: TL - contention     35     2     0.05
enq: UL - contention     34     524     15.42
gcs enter server mode     33     1559     47.24
wait for stopper event to be increased     30     218     7.27
enq: TQ - DDL contention     24     300     12.52
enq: MR - contention     21     1     0.03
ges reconfiguration to start     20     54     2.72
ges enter server mode     20     502     25.08
buffer latch     18     1337     74.26
enq: SR - contention     18     1     0.05
Streams: RAC waiting for inter instance ack     18     3748     208.21
enq: PR - contention     17     46     2.72
kupp process wait     16     166     10.39
checkpoint completed     15     3678     245.19
PX Deque wait     14     68     4.87
enq: BF - allocation contention     14     1     0.08
enq: XL - fault extent map     14     51     3.66
enq: FU - contention     14     17     1.18
enq: TH - metric threshold evaluation     13     114     8.78
enq: MW - contention     12     0     0.04
enq: DD - contention     10     0     0.04
process terminate     8     41     5.08
ges cgs registration     8     151     18.9
buffer resize     7     0     0
ktm: instance recovery     7     698     99.66
LNS wait on LGWR     6     0     0
ASM background starting     6     381     63.43
gc cr block 3-way     5     0     0.08
enq: PV - syncstart     5     9     1.74
Global transaction acquire instance locks     4     4     1.09
enq: RS - read alert level     4     0     0.04
LGWR wait on LNS     3     0     0
gc recovery     3     540     179.85
Streams AQ: enqueue blocked on low memory     3     544     181.2
DBWR range invalidation sync     3     17     5.83
enq: DM - contention     3     0     0.03
enq: RF - FSFO Observer Heartbeat     3     0     0.03
enq: JS - q mem clnup lck     3     0     0
DG Broker configuration file I/O     2     0     0
enq: RC - Result Cache: Contention     2     493     246.6
enq: KM - contention     2     0     0.03
enq: RT - contention     2     0     0.04
instance state change     2     0     0.12
kkdlgon     2     10     5.11
enq: TQ - INI contention     2     292     146.07
enq: JS - contention     2     0     0
ARCH wait for netserver start     1     400     400.02
log file switch (checkpoint incomplete)     1     3     3.44
JS coord start wait     1     50     50.09
ges lmd and pmon to attach     1     1     1.26
wait for tmc2 to complete     1     3     3.03
control file heartbeat     1     400     400.02
enq: SW - contention     1     0     0.04
enq: PW - perwarm status in dbw0     1     0     0.09
enq: FS - contention     1     0     0.04
enq: XR - quiesce database     1     0     0.04
enq: RS - write alert level     1     0     0.02
enq: CN - race with init     1     0     0.03
enq: FE - contention     1     4     3.77
Wait for shrink lock2     1     10     10.03
enq: IA - contention     1     0     0.02
enq: RF - atomicity     1     0     0.05
enq: RF - synchronization: aifo master     1     0     0.02
enq: RF - RF - Database Automatic Disable     1     0     0.06
enq: WP - contention     1     0     0.02
enq: TB - SQL Tuning Base Cache Load     1     0     0.05
enq: JS - evt notify     1     0     0.02Edited by: steffi on Mar 20, 2011 12:21 AM
Edited by: steffi on Mar 20, 2011 8:18 AM
Edited by: steffi on Mar 20, 2011 8:19 AM

Text can be formatted by tagging the beginning and end of the block of text with the code ta
\Formatted text goes here.
\Example:
This is formatted.When cutting and pasting text such as execution plans, excerpts from AWR reports, etc, it will maintain spacing and formatting, and make for much easier reading.
As to the content, well, dumping the contents of v$system_event is pretty close to useless.
As to the first three events you listed, 'enq: TX - index contention', 'enq: TX - row lock contention', 'enq: SQ - contention', well, all of those are easily tunable.
First, for 'enq: SQ - contention', check your sequences. Do you have any NOCACHE sequences? Or sequences with small caches?
As for 'enq: TX - row lock contention', well that's fairly self-explanatory. You have multiple sessions trying to lock the same row in the same table at the same time.
Last, 'enq: TX - index contention', that's non-row level contention on an index. For example, if you have a unique index, insert a row w/ column value 1, but don't commit, then try to insert that same value from another session.
But, before you do any of that, I think you need to clearly understand where the bottlenecks are. Try taking some AWR snapshots, about 5 minutes apart, when you're having performance problems. Look at the AWR report for that 5 minute period. In particular, look at your Top 5 timed events.
Hope that helps,
-Mark

Portal Upgrade Failure

Hi!
I ran the portal upgrade script against a copy of my production database to bring it up from 3.0.8.9.8 to 3.0.9. About an hour after the script was running, the database abruptly came down. When I looked in the altert log, there were numerous ORA-07445, ORA-12805 and ORA-00600 errors that only materialized after this upgrade script started running. It filled my system up with thousands of trace files and core subdirectories which I had to delete but the filesystem never filled up. Now I can open the database but it won't stay open for very long before it abruptly shuts down. Here's a startup from my alert log:
Fri Jul 20 14:13:51 2001
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
LICENSE_MAX_USERS = 0
Starting up ORACLE RDBMS Version: 8.1.7.0.0.
System parameters with non-default values:
processes = 165
shared_pool_size = 267665203
large_pool_size = 614400
java_pool_size = 20971520
control_files = /u01/oracle/oradata/play/control01.ctl, /u01/oracle
/oradata/play/control02.ctl, /u01/oracle/oradata/play/control03.ctl
db_block_buffers = 58021
db_block_size = 8192
compatible = 8.1.0
log_buffer = 163840
log_checkpoint_interval = 10000
log_checkpoint_timeout = 1800
max_enabled_roles = 30
remote_login_passwordfile= EXCLUSIVE
db_domain = msd.ray.com
instance_name = play
service_names = play.msd.ray.com
mts_dispatchers = (PROTOCOL=TCP)(PRE=oracle.aurora.server.SGiopServer
sort_area_size = 165536
sort_area_retained_size = 165536
db_name = play
open_cursors = 300
os_authent_prefix =
job_queue_processes = 1
job_queue_interval = 60
background_dump_dest = /u01/oracle/admin/play/bdump
user_dump_dest = /u01/oracle/play/udump
max_dump_file_size = 10000
core_dump_dest = /u01/oracle/admin/play/cdump
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
SNP0 started with pid=8
Fri Jul 20 14:13:57 2001
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL
=TCP))'...
Fri Jul 20 14:13:57 2001
alter database mount
Fri Jul 20 14:14:02 2001
Successful mount of redo thread 1, with mount id 741551593.
Fri Jul 20 14:14:02 2001
Database mounted in Exclusive Mode.
Completed: alter database mount
Fri Jul 20 14:14:02 2001
alter database open
Beginning crash recovery of 1 threads
Fri Jul 20 14:14:02 2001
Thread recovery: start rolling forward thread 1
Recovery of Online Redo Log: Thread 1 Group 1 Seq 3146 Reading mem 0
Mem# 0 errs 0: /u01/oracle/oradata/play/redo01.log
Recovery of Online Redo Log: Thread 1 Group 2 Seq 3147 Reading mem 0
Mem# 0 errs 0: /u01/oracle/oradata/play/redo02.log
Fri Jul 20 14:14:04 2001
Thread recovery: finish rolling forward thread 1
Thread recovery: 140 data blocks read, 139 data blocks written, 893 redo blocks
read
Crash recovery completed successfully
Fri Jul 20 14:14:04 2001
Thread 1 advanced to log sequence 3148
Thread 1 opened at log sequence 3148
Current log# 3 seq# 3148 mem# 0: /u01/oracle/oradata/play/redo03.log
Successful open of redo thread 1.
Fri Jul 20 14:14:04 2001
SMON: enabling cache recovery
SMON: enabling tx recovery
Fri Jul 20 14:14:07 2001
Errors in file /u01/oracle/admin/play/bdump/play_p003_1051.trc:
ORA-07445: exception encountered: core dump [ktugru()+72] [SIGBUS] [Invalid addr
ess alignment] [21] [] []
Fri Jul 20 14:14:07 2001
Errors in file /u01/oracle/admin/play/bdump/play_p004_1053.trc:
ORA-07445: exception encountered: core dump [ktugru()+72] [SIGBUS] [Invalid addr
ess alignment] [21] [] []
Fri Jul 20 14:14:14 2001
Completed: alter database open
Fri Jul 20 14:14:56 2001
SMON: Restarting fast_start parallel rollback
Fri Jul 20 14:14:56 2001
Errors in file /u01/oracle/admin/play/bdump/play_smon_1035.trc:
ORA-07445: exception encountered: core dump [kqrprl()+92] [SIGSEGV] [Address not
mapped to object] [2] [] []
ORA-12805: parallel query server died unexpectedly
Fri Jul 20 14:16:01 2001
PMON: terminating instance due to error 474
Instance terminated by PMON, pid = 1027
I am running Oracle 8.1.7, 9iAS 1.0.2.0.1 (have a separate 1.0.2.2 which I'll point to the upgraded portal), and Solaris 2.7. There were no errors in the alert log before I started the upgrade script.
Has anyone else upgrading just their portal from 3.0.8.9.8 to 3.0.9 experienced this difficulty. Thank GAWD this wasn't my prod portal...
Much thanks for any reply....Kate

Thank you Bob! My problem turned out to be that the database backup I used to restore a database copy was actually taken outside of my backup window before the database was shutdown. I should have known that using the init profile allowcorrupted_logs was a harbinger of worse things. Anyway, since the database was completely destroyed by the upgrade script, I used the next week's backup to restore a copy of the databse -- this time with much better results. The upgrade script worked fine after this.
Thanks for the heads up on the bug though. It will probably be useful. Thanks again.

Recovery of Frectured block

Similar Messages

Maybe you are looking for