<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments for Oracloid Blog</title>
	<atom:link href="http://www.oracloid.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.oracloid.com</link>
	<description>The Alex Gorbachev Oracle Blog</description>
	<pubDate>Sun, 05 Feb 2012 17:13:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>Comment on v$object_usage empty? by Mariana</title>
		<link>http://www.oracloid.com/2006/05/vobject_usage-empty/#comment-97352</link>
		<dc:creator>Mariana</dc:creator>
		<pubDate>Wed, 01 Feb 2012 20:12:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oracloid.com/?p=12#comment-97352</guid>
		<description>Just one question. Does the index monitor depend on how the audit trail parameter is set?
Thanks!</description>
		<content:encoded><![CDATA[<p>Just one question. Does the index monitor depend on how the audit trail parameter is set?<br />
Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bind Variable Peeking with no Histograms by zinassswerzz</title>
		<link>http://www.oracloid.com/2006/07/bind-variable-peeking-with-no-histograms/#comment-95626</link>
		<dc:creator>zinassswerzz</dc:creator>
		<pubDate>Thu, 05 Jan 2012 07:29:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oracloid.com/2006/07/bind-variable-peeking-with-no-histograms/#comment-95626</guid>
		<description>????!!! ? ????? ?????????? ?????, ? ??????? ???????? ? ????????? ???????? ?????? ???? ?? ??????????? (!) ??????? ??? ???????, ?? ????? ??? ?? ????????? ?????????, ? ???? ????????? - ????? ?????????? ?? ??? ????????, ??? ? ??? ???????? ???????????:   http://t1234.ru/index-nat.htm   !</description>
		<content:encoded><![CDATA[<p>????!!! ? ????? ?????????? ?????, ? ??????? ???????? ? ????????? ???????? ?????? ???? ?? ??????????? (!) ??????? ??? ???????, ?? ????? ??? ?? ????????? ?????????, ? ???? ????????? - ????? ?????????? ?? ??? ????????, ??? ? ??? ???????? ???????????:   <a href="http://t1234.ru/index-nat.htm" rel="nofollow">http://t1234.ru/index-nat.htm</a>   !</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on HASH GROUP BY can give wrong result in Oracle 10.2 by Change behavior of GROUP BY clause in Oracle 10g. &#171; Application DBA blog</title>
		<link>http://www.oracloid.com/2006/05/hash-group-by-can-give-wrong-result-in-oracle-102/#comment-95034</link>
		<dc:creator>Change behavior of GROUP BY clause in Oracle 10g. &#171; Application DBA blog</dc:creator>
		<pubDate>Thu, 29 Dec 2011 03:40:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oracloid.com/?p=6#comment-95034</guid>
		<description>[...] Alex had discussed about this behavior at his blog: http://www.oracloid.com/2006/05/hash-group-by-can-give-wrong-result-in-oracle-102/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Alex had discussed about this behavior at his blog: <a href="http://www.oracloid.com/2006/05/hash-group-by-can-give-wrong-result-in-oracle-102/" rel="nofollow">http://www.oracloid.com/2006/05/hash-group-by-can-give-wrong-result-in-oracle-102/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bind Variable Peeking with no Histograms by Odd Harry Ophaug</title>
		<link>http://www.oracloid.com/2006/07/bind-variable-peeking-with-no-histograms/#comment-93835</link>
		<dc:creator>Odd Harry Ophaug</dc:creator>
		<pubDate>Wed, 14 Dec 2011 13:02:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oracloid.com/2006/07/bind-variable-peeking-with-no-histograms/#comment-93835</guid>
		<description>&lt;a href="#comment-93805" rel="nofollow"&gt;@Khurram  &lt;/a&gt; 
Is this really true? According to Oracle Support article "Adaptive Cursor Sharing Overview [ID 740052.1]" the parameter must NOT be set to false for ACS to work:
"
Apart from checking for a valid operator there are also a number of subsequent bind sensitivity checks that need to be performed before it can be marked as bind sensitive, if it fails any of these the cursor will not be marked as bind sensitive and adaptive cursor sharing would not occur.  

If any of the following checks fail ECS will be disabled :-
- Extended cursor sharing is disabled
- The query has no binds
- Parallel query is used
- Certain parameters like ("bind peeking"=false) are set 
- You are using a /*+ NO_BIND_AWARE */ hint
- Outlines are being used
- It is a recursive query
- The number of binds in a given sql statement are greater than 14
...
Odd Harry</description>
		<content:encoded><![CDATA[<p><a href="#comment-93805" rel="nofollow">@Khurram  </a><br />
Is this really true? According to Oracle Support article &#8220;Adaptive Cursor Sharing Overview [ID 740052.1]&#8221; the parameter must NOT be set to false for ACS to work:<br />
&#8221;<br />
Apart from checking for a valid operator there are also a number of subsequent bind sensitivity checks that need to be performed before it can be marked as bind sensitive, if it fails any of these the cursor will not be marked as bind sensitive and adaptive cursor sharing would not occur.  </p>
<p>If any of the following checks fail ECS will be disabled :-<br />
- Extended cursor sharing is disabled<br />
- The query has no binds<br />
- Parallel query is used<br />
- Certain parameters like (&#8221;bind peeking&#8221;=false) are set<br />
- You are using a /*+ NO_BIND_AWARE */ hint<br />
- Outlines are being used<br />
- It is a recursive query<br />
- The number of binds in a given sql statement are greater than 14<br />
&#8230;<br />
Odd Harry</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bind Variable Peeking with no Histograms by Khurram</title>
		<link>http://www.oracloid.com/2006/07/bind-variable-peeking-with-no-histograms/#comment-93805</link>
		<dc:creator>Khurram</dc:creator>
		<pubDate>Wed, 14 Dec 2011 04:24:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oracloid.com/2006/07/bind-variable-peeking-with-no-histograms/#comment-93805</guid>
		<description>@Rakesh

I second to you that bind peeking occurs whether you have histogram or not till 10g , ACS for 11g will work only when you disable bind peeking by _optim_peek_user_binds.

Khurram</description>
		<content:encoded><![CDATA[<p>@Rakesh</p>
<p>I second to you that bind peeking occurs whether you have histogram or not till 10g , ACS for 11g will work only when you disable bind peeking by _optim_peek_user_binds.</p>
<p>Khurram</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on v$object_usage empty? by Behroz Bahrami</title>
		<link>http://www.oracloid.com/2006/05/vobject_usage-empty/#comment-93729</link>
		<dc:creator>Behroz Bahrami</dc:creator>
		<pubDate>Tue, 13 Dec 2011 13:59:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oracloid.com/?p=12#comment-93729</guid>
		<description>Thank you very much for sharing your knowledge as I have been trying to monitor Indexes for a User that we did not have its password and could also reset its password.  But by creating V$ALL_OBJECT_USAGE it solved all my problems.</description>
		<content:encoded><![CDATA[<p>Thank you very much for sharing your knowledge as I have been trying to monitor Indexes for a User that we did not have its password and could also reset its password.  But by creating V$ALL_OBJECT_USAGE it solved all my problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Oracle 10.2 RMAN Backup on NFS by Malinda Ramadhani</title>
		<link>http://www.oracloid.com/2007/06/oracle-102-rman-backup-on-nfs/#comment-92286</link>
		<dc:creator>Malinda Ramadhani</dc:creator>
		<pubDate>Wed, 30 Nov 2011 06:33:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oracloid.com/2007/06/oracle-102-rman-backup-on-nfs/#comment-92286</guid>
		<description>Hi Alex,

try this this way to mount

vim /etc/fstab

malinda:/home/oracle/archivelog       /home/oracle/archivelog      nfs  rw,bg,hard,nointr,tcp,vers=3,timeo=300,rsize=32768,wsize=32768,actimeo=0  0 0

Thanks</description>
		<content:encoded><![CDATA[<p>Hi Alex,</p>
<p>try this this way to mount</p>
<p>vim /etc/fstab</p>
<p>malinda:/home/oracle/archivelog       /home/oracle/archivelog      nfs  rw,bg,hard,nointr,tcp,vers=3,timeo=300,rsize=32768,wsize=32768,actimeo=0  0 0</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VLDB with ASM? by Alex Gorbachev</title>
		<link>http://www.oracloid.com/2006/05/vldb-with-asm/#comment-69606</link>
		<dc:creator>Alex Gorbachev</dc:creator>
		<pubDate>Fri, 28 Jan 2011 15:31:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oracloid.com/2006/05/vldb-with-asm/#comment-69606</guid>
		<description>@Prakash,

I would like to emphasize that I do not do free consulting on the blog. The blog is created to help readers understand the technology and make right decisions. If your need expert help with a specific production problem we can do a proper analysis and solution as part of Pythian services.

I'm also quite busy these days and usually ignore the requests with "Kindly reply Sonnest by today".

What you need to do is to understand the impact of the disks you are dropping and whether you still have enough capacity on your normal redundancy disk groups - not only to rebalance the data off the dropped disks but also to survive the failure of one of the disks that are left there. Based on your output, there are normal redundancy diskgroups with only two disks - you won't be able to recover automatically from a disk failure in these diskgroups.</description>
		<content:encoded><![CDATA[<p>@Prakash,</p>
<p>I would like to emphasize that I do not do free consulting on the blog. The blog is created to help readers understand the technology and make right decisions. If your need expert help with a specific production problem we can do a proper analysis and solution as part of Pythian services.</p>
<p>I&#8217;m also quite busy these days and usually ignore the requests with &#8220;Kindly reply Sonnest by today&#8221;.</p>
<p>What you need to do is to understand the impact of the disks you are dropping and whether you still have enough capacity on your normal redundancy disk groups - not only to rebalance the data off the dropped disks but also to survive the failure of one of the disks that are left there. Based on your output, there are normal redundancy diskgroups with only two disks - you won&#8217;t be able to recover automatically from a disk failure in these diskgroups.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Oracle 10.2 RMAN Backup on NFS by Alex Gorbachev</title>
		<link>http://www.oracloid.com/2007/06/oracle-102-rman-backup-on-nfs/#comment-69605</link>
		<dc:creator>Alex Gorbachev</dc:creator>
		<pubDate>Fri, 28 Jan 2011 15:00:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oracloid.com/2007/06/oracle-102-rman-backup-on-nfs/#comment-69605</guid>
		<description>@Mahesh: Before seeking for a solution, you need to find out what's the bottleneck of your backup speed. It can be network infrastructure, CPU, low # of spindles, poor RAID choice and bunch of other reasons.</description>
		<content:encoded><![CDATA[<p>@Mahesh: Before seeking for a solution, you need to find out what&#8217;s the bottleneck of your backup speed. It can be network infrastructure, CPU, low # of spindles, poor RAID choice and bunch of other reasons.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VLDB with ASM? by Prakash</title>
		<link>http://www.oracloid.com/2006/05/vldb-with-asm/#comment-69603</link>
		<dc:creator>Prakash</dc:creator>
		<pubDate>Fri, 28 Jan 2011 14:36:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.oracloid.com/2006/05/vldb-with-asm/#comment-69603</guid>
		<description>Alex;
Very impressive discussions here, thanks do much. I have a doubt as I'm required to drop 2 of the disks to from 2 diffrent existing normal redundancy diskgroup, in order to create another diskgroups with External rdunndancy. As I have my SAN storage(DS4700) configured with RAID 5, with proper failover capbilities. I've posted below my configuration for your perusal, kindly reply by today please.

SQL&#62; ;
  1  SELECT
  2      NVL(a.name, '[CANDIDATE]')      disk_group_name
  3    , b.path                          disk_file_path
  4    , b.name                          disk_file_name
  5    , b.failgroup                     disk_file_fail_group
  6  FROM
  7      v$asm_diskgroup a RIGHT OUTER JOIN v$asm_disk b USING (group_number)
  8  ORDER BY
  9*     a.name
SQL&#62; /

DISK_GROUP_NAME                DISK_FILE_PATH                           DISK_FILE_NAME                 DISK_FILE_FAIL_GROUP
------------------------------ ---------------------------------------- ------------------------------ ------------------------------
ARCHDG                         /dev/rhdisk26                            ARCHDG_0001                    GROUP2
ARCHDG                         /dev/rhdisk25                            ARCHDG_0000                    GROUP1
DATADG1                        /dev/rhdisk17                            DATADG1_0001                   GROUP2 -- want to take out 
DATADG1                        /dev/rhdisk16                            DATADG1_0000                   GROUP1 
DATADG1                        /dev/rhdisk15                            DATADG1_0003                   DATADG1_0003 --want to take out 
DATADG1                        /dev/rhdisk14                            DATADG1_0002                   DATADG1_0002
DATADG2                        /dev/rhdisk27                            DATADG2_0002                   DATADG2_0002
DATADG2                        /dev/rhdisk28                            DATADG2_0003                   DATADG2_0003 -------------- want to take out 
DATADG2                        /dev/rhdisk19                            DATADG2_0001                   GROUP2 -----------want to take out 
DATADG2                        /dev/rhdisk18                            DATADG2_0000                   GROUP1
INDEXDG                        /dev/rhdisk22                            INDEXDG_0001                   GROUP2
INDEXDG                        /dev/rhdisk21                            INDEXDG_0000                   GROUP1
TEMPDG                         /dev/rhdisk24                            TEMPDG_0002                    TEMPDG_0002--- want to take out 
TEMPDG                         /dev/rhdisk11                            TEMPDG_0000                    TEMPDG_0000
TEMPDG                         /dev/rhdisk13                            TEMPDG_0001                    TEMPDG_0001
[CANDIDATE]                    /dev/rhdisk23
[CANDIDATE]                    /dev/rhdisk7
[CANDIDATE]                    /dev/rhdisk8
[CANDIDATE]                    /dev/rhdisk9
[CANDIDATE]                    /dev/rhdisk20
[CANDIDATE]                    /dev/rhdisk12

21 rows selected.

SQL&#62; 

I've maked the disks , I'm willing to take out. Kindly reply Sonnest by today please.

Regards
Prakash</description>
		<content:encoded><![CDATA[<p>Alex;<br />
Very impressive discussions here, thanks do much. I have a doubt as I&#8217;m required to drop 2 of the disks to from 2 diffrent existing normal redundancy diskgroup, in order to create another diskgroups with External rdunndancy. As I have my SAN storage(DS4700) configured with RAID 5, with proper failover capbilities. I&#8217;ve posted below my configuration for your perusal, kindly reply by today please.</p>
<p>SQL&gt; ;<br />
  1  SELECT<br />
  2      NVL(a.name, &#8216;[CANDIDATE]&#8216;)      disk_group_name<br />
  3    , b.path                          disk_file_path<br />
  4    , b.name                          disk_file_name<br />
  5    , b.failgroup                     disk_file_fail_group<br />
  6  FROM<br />
  7      v$asm_diskgroup a RIGHT OUTER JOIN v$asm_disk b USING (group_number)<br />
  8  ORDER BY<br />
  9*     a.name<br />
SQL&gt; /</p>
<p>DISK_GROUP_NAME                DISK_FILE_PATH                           DISK_FILE_NAME                 DISK_FILE_FAIL_GROUP<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212; &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;- &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212; &#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
ARCHDG                         /dev/rhdisk26                            ARCHDG_0001                    GROUP2<br />
ARCHDG                         /dev/rhdisk25                            ARCHDG_0000                    GROUP1<br />
DATADG1                        /dev/rhdisk17                            DATADG1_0001                   GROUP2 &#8212; want to take out<br />
DATADG1                        /dev/rhdisk16                            DATADG1_0000                   GROUP1<br />
DATADG1                        /dev/rhdisk15                            DATADG1_0003                   DATADG1_0003 &#8211;want to take out<br />
DATADG1                        /dev/rhdisk14                            DATADG1_0002                   DATADG1_0002<br />
DATADG2                        /dev/rhdisk27                            DATADG2_0002                   DATADG2_0002<br />
DATADG2                        /dev/rhdisk28                            DATADG2_0003                   DATADG2_0003 &#8212;&#8212;&#8212;&#8212;&#8211; want to take out<br />
DATADG2                        /dev/rhdisk19                            DATADG2_0001                   GROUP2 &#8212;&#8212;&#8212;&#8211;want to take out<br />
DATADG2                        /dev/rhdisk18                            DATADG2_0000                   GROUP1<br />
INDEXDG                        /dev/rhdisk22                            INDEXDG_0001                   GROUP2<br />
INDEXDG                        /dev/rhdisk21                            INDEXDG_0000                   GROUP1<br />
TEMPDG                         /dev/rhdisk24                            TEMPDG_0002                    TEMPDG_0002&#8212; want to take out<br />
TEMPDG                         /dev/rhdisk11                            TEMPDG_0000                    TEMPDG_0000<br />
TEMPDG                         /dev/rhdisk13                            TEMPDG_0001                    TEMPDG_0001<br />
[CANDIDATE]                    /dev/rhdisk23<br />
[CANDIDATE]                    /dev/rhdisk7<br />
[CANDIDATE]                    /dev/rhdisk8<br />
[CANDIDATE]                    /dev/rhdisk9<br />
[CANDIDATE]                    /dev/rhdisk20<br />
[CANDIDATE]                    /dev/rhdisk12</p>
<p>21 rows selected.</p>
<p>SQL&gt; </p>
<p>I&#8217;ve maked the disks , I&#8217;m willing to take out. Kindly reply Sonnest by today please.</p>
<p>Regards<br />
Prakash</p>
]]></content:encoded>
	</item>
</channel>
</rss>

