Just a couple things to add - you might want to take a look at dba_hist_sqlbind (if you have a Diagnostics Pack license) if you're interested in older bind variables. I think the way v$sql_bind_capture and dba_hist_sqlbind works is that they only capture the bind variables at hard parse time since these are the only variables that are peeked by the CBO in order to determine the optimal execution plan. If your developer isn't comfortable with unix, ftp, scp, etc. maybe you could create a samba share to facilitate easier access to the udump directory? Regards, Brandon -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Teijo Lallukka Hopefully some day v$sql_bind_capture will do the trick... -Teijo Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it. -- //www.freelists.org/webpage/oracle-l