HP-UX AAA Server A.08.02 Administrator's Guide

Stored procedures are particularly useful, but not restricted to, the following:
• Executing multi-statement transactions: Stored procedures simplify the SQL access configuration
when multiple SQL statements forming a transaction need to be executed. For example, the
sample configuration includes a stored procedure that deletes a session row from the session
table, while returning the database column containing the IP address.
• Utilizing database schemas that contain child tables: Since SQL Access does not support
output of multiple database rows, stored procedures can be used to provide a "normalized"
view of the database parent and child tables to the AAA Server.
• Enhancing database security: Stored procedures can be written so that each execution is
logged in the database server. Furthermore, common operations on the database table can
be performed using stored procedures. This prevents applications and users from directly
accessing the database tables.
Stored procedures are executed in an SQL action as specified in the SQL statement using standard
SQL syntax.
NOTE: Use the IN and OUT parameters for stored procedures. INOUT for stored procedures is
not supported.
Use DBP for mapping to stored procedure input (target) and output (source) parameters.
The following example shows the definition of a stored procedure for OCI to remove session entries,
and its usage in the SQL action definition:
272 SQL Access