Comments for Askoracledba's Weblog

Comment on Understanding of Oracle 11g Automatic Diagnostic Repository – Part 1 by Jagriti

Jagriti — Thu, 13 Aug 2009 08:41:49 +0000

Good explanation

Comment on HW enqueue contention with LOB by leosanil

leosanil — Thu, 22 May 2008 13:21:04 +0000

Yes, bug# 6376915 is fixed in 10.2.0.4.

For windows this bug is fixed in 10.2.0.3.0 Patch 15 available in 32-Bit Patch 6637235 and 64-Bit (x64) Patch 6637236.

Comment on ASM Disk Discovery by ORA-15063 - ASM Discovered Insufficient amount of Disks « Askoracledba’s Weblog

Sun, 18 May 2008 17:39:22 +0000

[...] To Check ASM_DISKSTRING parameter you can check previous post on ASM Disk Discovery [...]

Comment on 10.2.0.4 on AIX5L (64-Bit) is Out by Amit

Amit — Sat, 17 May 2008 16:41:27 +0000

Thanks Laurent for your comment. I was not aware of this fact. Thanks again

Regards
Amit

Comment on 10.2.0.4 on AIX5L (64-Bit) is Out by Laurent Schneider

Laurent Schneider — Sat, 17 May 2008 04:25:58 +0000

AIX has always been bigger, mainly due to the amount of static libraries (.a) in AIX vs shared libraries (.so) in Linux/Solaris.

I bet they will split 10.2.0.5 in two files

Comment on HW enqueue contention with LOB by eckes

eckes — Sat, 10 May 2008 02:01:00 +0000

I wonder why 6376915 is not available as a patch for windows. Also it looks like the fix is part of 10.2.0.4, but that is not available for win64… strange.

Comment on ERRORSTACK- Oracle Debugging Event by Aman Sharma

Aman Sharma — Sat, 19 Apr 2008 07:48:00 +0000

Hey Amit,
Thanks for making my request as a blog post.And yes it was a good one as like always .

Comment on Diagnostics For Database Hang by Amit

Amit — Sat, 05 Apr 2008 01:28:00 +0000

Aarya,You can use P1,P2,P3 values to diagnose the parameters for wait event. e.g You see event ‘latch free’ as considerable wait event, then
P1 = Latch address
P2 = Latch number

Now you can identify the latch name from V$LATCHNAME
SELECT * FROM v$latchname WHERE latch# =P2;
Moreover there can be situation where many sessions are waiting on same latch anf their P1 and P2 values are same say it points to Shared Pool Latch. From this we can be sure that some latching issue is causing the Database Hang.I will try to take up a case study sometime so that it can be more clear.And for your second question, you can refer to
Note 121779.1-Taking a SYSTEMSTATE dump when you cannot CONNECT to Oracle.

It is already mentioned in the post.In case of 10g, you can use prelim to connect to database.
e.g
sqlplus -prelim “/ as sysdba”

Cheers
Amit

Comment on Diagnostics For Database Hang by Aarya

Aarya — Fri, 21 Mar 2008 14:36:00 +0000

Hi Piyush,

Very good information on database hang.
But i have few questions on this:

-What does p1,p2,p3 represents in v$session_wait and what are their significanse here.
- I have faced this situation many a times but i was not able to login to database when the hang occured, so what to do in that case, i.e how to generate dumps.