MX Release 3.2 (H06.25+, J06.14+)

ManualsBrandsHP ManualsServerHP Integrity NonStop J-Series

RemarksActual ResultExpected ResultOperation

Compiled plan is retrieved

from MFC.

SuccessSuccessStmt1 = Prepare("

select * from

testing")

MFC statement works as

expected.

SuccessSuccessStmt1.execute()

The table testing is dropped.SuccessSuccessStmt1.executeUpdate("

drop table testing")

The table testing is created

with varchar column.

SuccessSuccessStmt1.executeUpdate("

create table testing

(mycol varchar(

10))")

Compiled plan is retrieved

from MFC, which is not

SuccessSuccessStmt1 = Prepare("

select * from

testing")

correct because the table

datatype is changed when

the MFC plan is created.

MXOSRVR turned the

SQL/MX CQD

FailureSuccessStmt1.execute()

recompilation_warnings ON.

SQL/MX throws SQL

exception upon similarity

check failure and MXOSRVR

drops the invalid module file

from the

<compiled_module_l

ocation> location.

A new plan is created in the

MFC location.

SuccessSuccessStmt1 = Prepare("

select * from

testing")

MFC statement works as

expected.

SuccessSuccessStmt1.execute()

When performing the above operations, the execute() call fails when an invalid module file is

found in the MFC. However, subsequent prepare() calls create a new module file. This open issue

is similar to the Driver Side Cache (DSC) present in the JDBC/T4 driver.

Module File Caching (MFC) 55