Focal Point
Object is in a zombie state

This topic can be found at:
https://forums.informationbuilders.com/eve/forums/a/tpc/f/1381057331/m/1117089036

May 22, 2013, 08:05 AM
Koby1Kanoby
Object is in a zombie state
I have a DBMS SQL Flow that I have been running without issue every month, and not sure why it's now failing.

When I click on the "Test SQL Statement" button from the SQL Statement window, I see my 50 rows.

When I click on the "Test Transforms" button from the Transformations window, I see my 50 rows.

Any help would be most appreciated.

Here is the error log...

------ Start of Log Record for dev_financial/load_stg_budgetdetailscompensation
Request - dev_financial/load_stg_budgetdetailscompensation (Owner: [removed to post on forum]
stg_budgetdetailscompensation type MS SQL Server Existing target
Issuing PREPARE
Bulk Insert active. INSERTSIZE = 1000
Starting Load
0 WARNING.. ON MATCH INCLUDE INPUTS DUPLICATE SEGMENTS
REFERENCE...AT TRANS 1000
Commit forced at: 1000 for 1000 row(s)
SQLCODE IS -1 (HEX: FFFFFFFF)
: Microsoft SQL Server Native Client 10.0: [] The object is in a zombie st
: ate. An object may enter a zombie state when either ITransaction::Commit
: or ITransaction::Abort is called, or when a storage object was created
: and not yet released.
SQL FETCH CURSOR ERROR. : SQLIN
Ending Load
Return Code = 1407
Request: dev_financial/load_stg_budgetdetailscompensation - finished processing
CPU Time : 125
Finished
Elapsed run time 0:00:12
------ End of Log Record for dev_financial/load_stg_budgetdetailscompensation --


WebFOCUS 7.6
Windows, All Outputs
May 23, 2013, 03:39 PM
Clif
As you've determined the source tables are fine; the problem is with the state of the target table.

In my experience this error most often occurs because some process didn't issue a COMMIT when it was done.


N/A
June 11, 2013, 03:00 PM
Koby1Kanoby
It COMMITs the first 1000 rows, then goes in to "a zombie state".


WebFOCUS 7.6
Windows, All Outputs