Deployment Manager site throws error: "Cursor signature mismatched for Procedure ExplainResources"
Article ID: KB0080176
Updated On:
| Products | Versions |
|---|---|
| TIBCO Data Virtualization | v7.0.x |
Description
After execution of a plan in Deployment Manager, the execution log repeatedly mentions that <various resources> could not be created on the target.
If you click on the target site, you may see a popup message that says:
A system exception has occurred. Cursor signature mismatched for Procedure "ExplainResources". It is defined to have "11" columns, but the physical stored procedure cursor has "13" columns. Use "Design by Example" to introspect columns with cursor data types. [data-2911065] [script-1900011]
Note: the actual number of columns mentioned in the error message may vary, it will not necessarily always be 11 and 13 as seen above.
If you click on the target site, you may see a popup message that says:
A system exception has occurred. Cursor signature mismatched for Procedure "ExplainResources". It is defined to have "11" columns, but the physical stored procedure cursor has "13" columns. Use "Design by Example" to introspect columns with cursor data types. [data-2911065] [script-1900011]
Note: the actual number of columns mentioned in the error message may vary, it will not necessarily always be 11 and 13 as seen above.
Issue/Introduction
This concerns an error from Deployment Manager when mismatching versions with TDV.
Resolution
ExplainResources is our native procedure found under /lib/resources and has been slowly updated over the life cycle of various v7.0.x releases. It used to have only 10 columns defined before v7.0.3 and has increased to 13 columns in v7.0.6.
Hence the mismatch is interpreted as an interface change and now DM won't accept it as a new site's execution plan.
We only support DM to be used between like server versions (ie; the source & target TDV servers), though the server versions delta could potentially be allowed to vary a bit as long as no significant interface updates were made by Tibco between the 2 versions involved.
However, this information is not documented and we do not support differing source & target versions when this type of error occurs.
Hence the mismatch is interpreted as an interface change and now DM won't accept it as a new site's execution plan.
We only support DM to be used between like server versions (ie; the source & target TDV servers), though the server versions delta could potentially be allowed to vary a bit as long as no significant interface updates were made by Tibco between the 2 versions involved.
However, this information is not documented and we do not support differing source & target versions when this type of error occurs.
Feedback
Yes
No
Powered by
