FME geodatabase_sde reader gives cursor error

3631
2
11-22-2011 11:35 PM
RaivoAlla
New Contributor II
Hello!

I think this is a right place to discuss my problem 🙂
I have ArcGIS 10/PostgreSQL 8.3, and the base I'm trying to read from, is a one-way replica with archiving.Using FME Desktop 2011 SP4, I try to access some SDE featureclasses (that has always been successful before), but I encounter a strange problem reading one particular featureclass. Excerpt from FME log:

[INDENT]Reading table/feature class 'vahetuum_admin.kolvikud_a' ...
Unable to retrieve feature from table/feature class
'vahetuum_admin.kolvikud_a'. Aborting reading from table
'vahetuum_admin.kolvikud_a'. The error number from ArcObjects is:
'-2147216072'. The error message from
ArcObjects is: {Underlying DBMS error [ERROR: cursor
"sdecur_1405_511" does not exist
] [vahetuum.vahetuum_admin.kolvikud_a]}[/INDENT]

Sometimes I'm successful to read first 71, sometimes a bit more
features, till I get that error and the reader stops reading further.

PostgreSQL log is showing this:
[INDENT]2011-11-23 10:59:25 EET ERROR: out of memory
2011-11-23 10:59:25 EET DETAIL: Failed on request of size 1248.
2011-11-23 10:59:25 EET STATEMENT: COMMIT
2011-11-23 10:59:27 EET ERROR: SAVEPOINT can only be used in
transaction blocks
2011-11-23 10:59:27 EET STATEMENT: SAVEPOINT sp_sde_1322038767_0_1413
2011-11-23 10:59:27 EET ERROR: cursor "sdecur_1405_515" does not
exist
2011-11-23 10:59:27 EET STATEMENT: FETCH FORWARD 1000 from
sdecur_1405_515
2011-11-23 10:59:27 EET ERROR: cursor "sdecur_1405_515" does not
exist
2011-11-23 10:59:27 EET STATEMENT: CLOSE sdecur_1405_515
2011-11-23 10:59:27 EET ERROR: current transaction is aborted,
commands ignored until end of transaction block [/INDENT]


What could cause that problem?

With hope,
Raivo Alla,
Estonian Land Board
0 Kudos
2 Replies
RaivoAlla
New Contributor II
Sorry,  PostgreSQL version is 8.4.7 with PostGIS 1.4.0


Raivo
0 Kudos
RaivoAlla
New Contributor II
Today we had a lucky day to solve the problem:
In PostgreSQL configuration file, the parameter WORK_MEM was set to 32MB (We increased it cause
we thought error message displayed hints to give more memory). The solution was to set WORK_MEM back to 1MB (default value).

Now the reading process runs fine, still for us tiny mystery remains in PG log file. Running that reader in FME creates log entry, where that strange error appears which doesn't ring any bell in my mind:
2011-11-29 11:15:06 EET ERROR:  relation "sde.sch_dataset" does not exist at character 15
2011-11-29 11:15:06 EET STATEMENT:  SELECT 1 FROM vahetuum.sde.SCH_DATASET WHERE 1 = 0
...

But generally that issue is solved,
Raivo
0 Kudos