Oracle Legal Whitehill One - Stored Procedure Metalink Omits Comma Causing SQL Syntax Exceptions (Doc ID 989527.1)

Last updated on JANUARY 27, 2010

Applies to:

Oracle Legal Whitehill One - Version: 5.5 - Release: 5.5
Information in this document applies to any platform.


When a database metalink is created in the Whitehill One IDE and a stored procedure is chosen instead of an SQL Statement, the imported stored procedure input values should all be separated by commas, except the first two values are not. This throws exceptions further on in the wizard or when the metalink is run in the activity tester.

When trying to return a resultset, the Database Metalink Wizard exception reads:

"Encountered SQL error while trying to retrieve column definitions from the database:
You have an error in your SQL syntax; check the manual that corresponds your <database name> version for the right syntax to use near ..."


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms