Abstract: A method for establishing a connection between a data server and a middleware server is disclosed. The method includes defining a plurality of trust attributes corresponding to a trusted context between the middleware server and the data server and validating the plurality of trust attributes against a plurality of attributes corresponding to the middleware server. The plurality of attributes provided in a connection request. The method also includes establishing the trusted context based on the validating the plurality of trust attributes.

Abstract: Systems, methods, and computer products that support techniques associated with highly reliable transaction protocol semantics in databases. Such techniques extend database transaction semantics that support a single-phase or a two-phase commit protocol to include user-defined operations while supporting the XA X/Open® Distributed Transaction Processing Protocol (“XA Transaction Protocol”). The preferred embodiment of the present invention novelly enables user-defined operations that access external resources by means of the XA Transaction Protocol to be included in database transaction processing features. Thereby user-level access to well-defined APIs is provided. Further, the preferred embodiment of the present invention novelly ensures atomicity for the results of the database transaction that includes both the user-defined operations and database operations. According to the preferred embodiment of the present invention the database acts, in part, as an XA transaction manager.

Abstract: An improved automatically updated timestamp for database systems is disclosed. The automatically updated timestamp can be provided in a hidden timestamp column for a table, where the value of the timestamp column can be retrieved with a query that calls the column by name. Optionally, the timestamp column can be provided for each table in the database system to ensure its availability to applications. For cases where a timestamp for each row in a table is not desired, an automatically updated timestamp can be provided for a data page. This timestamp can be retrieved from an update timestamp recorded on disk and in the buffer pool or from a log relative byte address. Although this is a page-level timestamp, its use may be desirable for infrequently updated tables or where space on the disk and buffer pool is at a premium.

Abstract: In a system for avoiding section collision for application server requests over a single database connection, the database server assigns query identifiers to each instance of the same cursor opened for the same processing level within an application, allowing multiple instances of the same cursor to be processed in parallel without section collision. The application server assigns a command source identifier to each statement sent over a single database connection to uniquely identify the application source of the statement. This applies for multiples of the same statement sent by different application sources within the same application, for a single statement containing multiple application sources, and for multiple statements from different applications multiplexed over a single database connection. These statements can be processed separately from and in parallel with the each other without section collision.

Abstract: A system for establishing a connection between a data server and a middleware server is disclosed. The system includes defining a plurality of trust attributes corresponding to a trusted context between the middleware server and the data server and validating the plurality of trust attributes against a plurality of attributes corresponding to the middleware server. The plurality of attributes provided in a connection request. The system also includes establishing the trusted context based on the validating the plurality of trust attributes.

Abstract: An apparatus, system, and method are disclosed for efficiently supporting generic SQL data manipulation statements. The method includes determining whether an SQL statement includes extended indicator parameters such as DEFAULT and UNASSIGNED indicators. The method further includes delaying an authorization check for an operation for an SQL statement using extended indicators, and bypassing an SQL exception where an otherwise unauthorized operation involves an UNASSIGNED variable. The method further includes bypassing a database operation such as a referential integrity check where a data change would induce the database operation, but the data change involves an UNASSIGNED variable. The method further includes modifying the SQL statement when the SQL statement involves an UNASSIGNED variable in a predicate clause, allowing the SQL statement to properly execute.

Abstract: In a method for avoiding section collision for application server requests over a single database connection, the database server assigns query identifiers to each instance of the same cursor opened for the same processing level within an application, allowing multiple instances of the same cursor to be processed in parallel without section collision. The application server assigns a command source identifier to each statement sent over a single database connection to uniquely identify the application source of the statement. This applies for multiples of the same statement sent by different application sources within the same application, for a single statement containing multiple application sources, and for multiple statements from different applications multiplexed over a single database connection. These statements can be processed separately from and in parallel with the each other without section collision.

Abstract: A database server helps to streamline the retrieval of LOB values by deciding to send a locator in replacement of the LOB value, or the LOB value itself, depending upon the specific LOB value being retrieved. A threshold value is determined in a fetch query, and the LOB sizes below that threshold are sent as values in a corresponding fetch response, and the lengths above are sent as locators in the fetch response. Indicators are inserted in a fetch parameter of the response to inform the receiving client the form of retrieval that was used for each requested LOB value being returned.

Abstract: A cursor query identifier is defined to uniquely identify cursors in a relational database system that supports nested routine invocation. The identifier includes a cursor nesting level value that corresponds to the nested level at which the cursor is opened. The identifier also includes a invocation identifier that corresponds to the routine within which a cursor is opened. The third part of the identifier is a unique cursor counter. The definition of the cursor query identifier permits cursors to be opened within nested levels of the same relational database context and to be uniquely identified for reference by database system and by applications accessing the system.

Abstract: Computer program code which is a candidate for Web enablement or stored procedures is identified. Source code corresponding to computer program code is scanned and parsed to determine static information concerning the computer program code. The static information is stored in a database. Dynamic information concerning the computer program code during an execution of the computer program code is also collected and stored in the database. Responsive to the static information and dynamic information stored in the database, relationships and dependencies are then developed and stored in the database. The database may then be queried to produce a set of potential candidates of computer program code meeting a constraint of the query. If insufficient candidates are returned by the query, then the query constraint may be relaxed, and the query repeated.

Abstract: A method for providing database connections in a network includes: (a) mapping a first plurality of logical connections for a transaction at the application server to a physical connection between the application server and the database server; (b) sending a request of the transaction to the database server utilizing one of the first plurality of logical connections, where the request is sent utilizing the physical connection; and (c) processing the request by a logical agent on the database server, where the logical agent is associated with the transaction, where the request is maintained in one of a second plurality of logical connections within the logical agent. In this manner, connections are logically separated from one another with minimal storage implications. Conflicts and unpredictable behavior can also be avoided.

Abstract: System, method, and program product for managing transactions on a plurality of Database Management Systems residing on separate participant servers and a coordinator server. A single transaction proceeds by multiple steps across more then one of the plurality of Database Management Systems as participants. Savepoints are assigned to the participants across the Database Management System, with at least one savepoint within a multiple step transaction. The DBMS responds to application requests to rollback to savepoint by rolling back the transaction, across the Database Management System participants, to the savepoint Further disclosed is a program product that contains code, which, either as written on the medium, or as instantiated in RAM, or both, controls the operation of a distributed database management system.

Abstract: A database server helps to streamline the retrieval of LOB values by deciding to send a locator in replacement of the LOB value, or the LOB value itself, depending upon the specific LOB value being retrieved. A threshold value is determined in a fetch query, and the LOB sizes below that threshold are sent as values in a corresponding fetch response, and the lengths above are sent as locators in the fetch response. Indicators are inserted in a fetch parameter of the response to inform the receiving client the form of retrieval that was used for each requested LOB value being returned.

Abstract: A method for providing database connections in a network includes: (a) mapping a first plurality of logical connections for a transaction at the application server to a physical connection between the application server and the database server; (b) sending a request of the transaction to the database server utilizing one of the first plurality of logical connections, where the request is sent utilizing the physical connection; and (c) processing the request by a logical agent on the database server, where the logical agent is associated with the transaction, where the request is maintained in one of a second plurality of logical connections within the logical agent. In this manner, connections are logically separated from one another with minimal storage implications. Conflicts and unpredictable behavior can also be avoided.

Abstract: A cursor query identifier is defined to uniquely identify cursors in a relational database system that supports nested routine invocation. The identifier includes a cursor nesting level value that corresponds to the nested level at which the cursor is opened. The identifier also includes a invocation identifier that corresponds to the routine within which a cursor is opened. The third part of the identifier is a unique cursor counter. The definition of the cursor query identifier permits cursors to be opened within nested levels of the same relational database context and to be uniquely identified for reference by database system and by applications accessing the system.

Abstract: System, method, and program product for managing transactions on a plurality of Database Management Systems residing on separate participant servers and a coordinator server, A single transaction proceeds by multiple steps across more then one of the plurality of Database Management Systems as participants. Savepoints are assigned to the participants across the Database Management System, with at least one savepoint within a multiple step transaction. The DBMS responds to application requests to rollback to savepoint by rolling back the transaction, across the Database Management System participants, to the savepoint Further disclosed is a program product that contains code, which, either as written on the medium, or as instantiated in RAM, or both, controls the operation of a distributed database management system.

Abstract: A method, apparatus, and article of manufacture for providing a programming development environment that supports the development of portable server routines. More specifically, the present invention discloses a method for storing and retrieving server routines within the database independent of any file I/O system. Also, the present invention discloses a debugging environment that allows debugging of server routines in a multi-tier environment, wherein the source code being debugged runs on the development machine.

Abstract: A computer program product and program storage device for incorporating an external predefined procedure into an existing unit of work. The existing unit of work is part of a client application process, wherein the client application process is not able to execute external programs. A logical representation of the client application process is created in a database environment. The logical representation is disconnected from the client application process, and is connected to a procedure operating environment capable of executing external programs. The external predefined procedure is caused to executed in the procedure operating environment. Then, the logical representation is reconnected to the client application process.

Abstract: A system for processing diverse and non-diverse result sets is described. The system includes a client process in a client computer system that constructs a client process execution request identifying a stored procedure and specifying constraints on the quantity of response data that the client process is capable of handling. The client process execution request is transferred from the client process in the client computer system to a server process in a server computer system. The server process invokes the stored procedure identified by the client process execution request. Execution of the stored procedure results in the generation of answer set data for a plurality of diverse query result sets. Result set generators obtain answer set data for X of the query result sets, where X is defined by the constraints. The server process then generates an initial response containing, for each of the X query result sets, an amount of the obtained answer set data consistent with the constraints.

Abstract: A system for processing diverse and non-diverse result sets is described. The system includes a client process in a client computer system that constructs a client process execution request identifying a stored procedure and specifying constraints on the quantity of response data that the client process is capable of handling. The client process execution request is transferred from the client process in the client computer system to a server process in a server computer system. The server process invokes the stored procedure identified by the client process execution request. Execution of the stored procedure results in the generation of answer set data for a plurality of diverse query result sets. Result set generators obtain answer set data for X of the query result sets, where X is defined by the constraints. The server process then generates an initial response containing, for each of the X query result sets, an amount of the obtained answer set data consistent with the constraints.