Stefan,
I used DBA_HIST_SQLBIND because I was looking for bind values between a very
specific period which occurred about two days ago. The problem is that this
statement does not run longer all the times, it only runs longer intermittently
for certain values which are highly skewed and I was able to validate it after
capturing those values from the view.
Did you have any concern that I was capturing bind values incorrectly?
Thanks
-----Original Message-----
From: Stefan Koehler [mailto:contact@xxxxxxxx] ;
Sent: Friday, September 16, 2016 10:13 AM
To: Hameed, Amir <Amir.Hameed@xxxxxxxxx>; oracle-l@xxxxxxxxxxxxx
Subject: RE: "Row Source Operation" section in TKP
Hey Amir,
are you sure? ;-)
DBA_HIST_SQLBIND is based on V$SQL_BIND_CAPTURE and V$SQL_BIND_CAPTURE content
is controlled with "_cursor_bind_capture_interval".
Best Regards
Stefan Koehler
Freelance Oracle performance consultant and researcher
Homepage: http://www.soocs.de
Twitter: @OracleSK
"Hameed, Amir" <Amir.Hameed@xxxxxxxxx> hat am 16. September 2016 um 16:06��i��0���zX���+�� n��{�+i�^
geschrieben:
I was able to pull bind values from DBA_HIST_SQLBIND view for the bad
run. But, my question was more from the standpoint of clarifying my
understanding of the section.
