RPCs Passed to Oracle

RPCs that are not interpreted by ECDA Option for Oracle are passed directly to Oracle for execution.

When ECDA Option for Oracle executes a stored program, it associates the actual and formal parameters by position. Therefore, when calling a subprogram using ECDA Option for Oracle, the parameters must be passed using positional notation or named notation.

Note: Mixed notations (both positional notation and named notation) are not supported in a single Oracle procedure call.

Stored Procedures with Named Parameters

When an Oracle stored procedure is called with named parameters, the name must match the parameter name of the Oracle procedure. If the names do not match, a procedure call is made without the named parameter being used and an Oracle error occurs.

Note: If the parameter name does not match the input parameter name, and the parameter name has a default coded value, the procedure executes using the default value and no error is issued.

Create Stored Procedures

The syntax for the Oracle create procedure SQL command can be found in Oracle SQL language reference documentation.

Stored Procedures within a Package
Examples that illustrate the use of stored procedures based on the Oracle table and data.
RPC Restrictions
When handling RPC parameters of datatype tinyint, only valid values (between 0 and 255) can be passed back. If the back-end database returns a negative value, that value is passed to the user as a NULL value.

Parent topic: Remote Procedure Calls