For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!
Try to match the query of the Dynamic Value Query's cursor to the query of the cursor in the stored procedure... i.e. there is no "example" column in the "dual" table... why not to use "example_table where rownum=1" instead of "dual", for example?
Hope this helps...
BTW: Comparing the expected and received record sets as up to 32K strings works just fine, unless one of the expressions in the dynamic value query is larger than 30 characters, in which case the "Expected:[...]" header line would have the truncated 30 character expression header and the "Received:[...]" header line would have it at a full length... which would cause a false "failure" of the test... a workaround is to use a shorter than 30 character alias for the "offending" long expression...
Personally I see it as a bug and a showstopper in SQL Developer, because if your stored procedure is already deployed in Production environment and it doesn't have a short alias in its query you cannot use this workaround... I will try to file a bug for this on Metalink after creating a test case for them using HR schema or something...
Val