PSTL Vendor Combiner - cursor with the name 'ta_VCCursor' already exists

(0) Share

Report

Posted on by Community Member

When using the PSTL Vendor Combiner, the user is getting the following error for one of the vendors but has no issues combining others:

[Microsoft][SQL Server Native Client 10.0] A cursor with the name ta_VCCursor already exists. [Microsoft][SQL Server Native Client 10.0][SQL Server]The cursor is already open.

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Almas Mahfooz 11,009 User Group Leader on at

Like (0)

Report

Logout all the users from GP.

Find the SPID for the open cursor by running below SQL script.

SELECT f.session_id

FROM sys.dm_exec_cursors(0) f

WHERE f.name = 'ta_VCCursor'

kill the session of the user. remove the session_id with the value you got from above query.

kill 'session_id'

Was this reply helpful? Yes No
Tim W 2,925 on at

Like (0)

Report

I've gotten this error when PSTL could not complete a combiner process (we have a couple third party tables that cause an issue unless dealt with first) and the PSTL errors out. If I correct the issue with the table and re-run the combine without logging out I get this exact error 100% of the time.

I found I need to close out of GP and then restart the client to then be able to re-run the combine.

My guess is when the PSTL errors out it does not clean up the temp table created and so can't create a new one until I lose that session and establish a new one.

I'd be wondering if your user got a different error message first and then was re-running the combine.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks. They did get an error on another combine just prior (duplicate key from 3rd party). I will resolve the key error first and we should be good.

Was this reply helpful? Yes No