Ingres 9.2 Migration Guide - Actian

Connectivity EnhancementsServer Type Reported for Terminated ProgramsWhen a program attached to the Ingres shared memory segment terminatesunexpectedly, a message is written to the log to identify the running programand, if it is a command line program, the program arguments. For example:Process (000033B4) died with info 'auditdb -a tstdb'.When database servers and database utilities such as auditdb are executing,they attach themselves to the Ingres shared memory segment. In previousreleases, when an error occurred, it was difficult to determine which memoryattachedprogram terminated and, thus, whether the failure was critical ormerely a benign error that could, for example, be resolved by re-running theutility program that failed or was canceled.The new information logged makes it easier to debug problems associated withthe shared memory segment.Note: Because the messages appear in the log when Ingres notices theabnormal termination, their writing may be asynchronous with the programtermination itself.Connectivity EnhancementsLOB Locator Support in JDBC and OpenAPIJDBC supports an abstraction of LOB locators through the BLOB and CLOBclasses. LOB locators allow the client to request data from a specific offset inthe LOB without having to retrieve the data in between. For details, see thesection LOB Locators in the chapter "Understanding JDBC Connectivity" in theConnectivity Guide.With OpenAPI, an application can request a reference to the long data, called alocator, by setting the IIAPI_QF_LOCATOR flag when calling IIapi_query().Locators are 4-byte integer values that reference the long data where itresides in the database. For details, see the section LOB Locators in thechapter "Introduction" in the OpenAPI User Guide.152 Migration Guide