Unable to mask a Sybase table using Fast Data Masker

Products

• CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

While trying to mask a specific table in a Sybase database, we are getting an exception stating that " Css_InsertExportTable may be run only in unchained transaction mode. The 'SET CHAINED OFF' command will cause the current session to use unchained transaction mode." 

We checked with the DBA team and confirmed that "All procedures are set to unchained". 

Below is an example of the error we are seeing in the FDM log:

>2020-03-11 09:11:45.507  

>2020-03-11 09:11:45.601 Thread:1 -  Starting at 2020.03.11 09:11:45.601 EDT 

>2020-03-11 09:11:45.647 Thread:1 - Masking table Css_Entity using where clause: Entity_Syskey IN (2147470768,2137019554,2144373193) 

>2020-03-11 09:11:45.647 Cursor Fetchsize:1000 

>2020-03-11 09:11:45.647 Autocommit:false 

>2020-03-11 09:11:45.835 Stored procedure 'Css_InsertExportTable' may be run only in unchained transaction mode. The 'SET CHAINED OFF' command will cause the current session to use unchained transaction mode.

Environment

Release : 4.8

Component : CA Test Data Manager

Cause

Engineering looked into this and said the 'Css_InsertExportTable' stored procedure is not anything we are doing in the background. It's not part of the TDM product, therefore it's out of our control. 

Resolution

The error you are seeing is a Sybase error. According to the Sybase Software Developer's Kit 15.7, under the jConnect for JDBC 7.07 Programmers Reference > Troubleshooting > Resolving stored procedure errors:

Stored procedure executed in unchained transaction mode

Sybase Error 7713 - Stored Procedure can only be executed in unchained transaction mode.

This error occurs when JDBC attempts to put the connection in autocommit(true) mode. The application can change the connection to chained mode using Connection.setAutoCommit(false) or by using a “set chained on” language command. This error occurs if the stored procedure was not created in a compatible mode.

To fix the problem, use:

sp_procxmode procedure_name,"anymode"

See http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc39001.0707/html/prjdbc0707/CHDEGBEA.htm

Another option might be to disable the stored procedure and see if that provides better results.