topic Underlying DBMS error [ERROR: out of memory DETAIL: Faild on request of size 40.] in Data Management Questions

Underlying DBMS error [ERROR: out of memory DETAIL: Faild on request of size 40.]

Anonymous User — Thu, 30 May 2013 05:04:49 GMT

Original User: allwin2002au

Hi all,

Underlying DBMS error [ERROR: out of memory DETAIL: Faild on request of size 40. ::SQL state: 53200][.sde.GDB_Items]

I am trying to load feature dataset

from:
OS:Linux 2.6.18-308.11.1.el5 #1 SMP Fri Jun 15 15:41:53 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux
PG: PostgreSQL 8.3.9 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.4.6 20060404 (Red Hat 3.4.6-10)
POSTGIS="1.3.5" GEOS="3.0.3-CAPI-1.4.2" PROJ="Rel. 4.6.1, 21 August 2008" USE_STATS
ArcSDE 9.3

To:

OS: Linux 2.6.32-279.2.1.el6.x86_64 #1 SMP Thu Jul 5 21:08:58 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux
PG: PostgreSQL 9.1.3 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.4.6 20120305 (Red Hat 4.4.6-4), 64-bit
POSTGIS="2.0.3 r11128" GEOS="3.3.2-CAPI-1.7.2" PROJ="Rel. 4.7.1, 23 September 2009" GDAL="GDAL 1.7.3, released 2010/11/10 GDAL_DATA not found" LIBXML="2.7.6" TOPOLOGY RASTER
ArcSDE: 10.1
ArcGIS 10.1 Server

using ArcCatalog 10.1 (Build 3143), ArcGIS 10.1 SP1 for Desktop (Build 3143). I am using database connection copy the dataset and paste it in the new database connection with the same user name.

The process failed with out of memory error.

the log file shows

pg_database_datname_index: 3072 total in 2 blocks; 1720 free (3 chunks); 1352 used
    pg_auth_members_role_member_index: 3072 total in 2 blocks; 1704 free (4 chunks); 1368 used
    pg_database_oid_index: 3072 total in 2 blocks; 1720 free (3 chunks); 1352 used
    pg_authid_rolname_index: 3072 total in 2 blocks; 1720 free (3 chunks); 1352 used
MdSmgr: 24576 total in 2 blocks; 15232 free (20 chunks); 9344 used
LOCALLOCK hash: 24576 total in 2 blocks; 9808 free (4 chunks); 14768 used
Timezones: 83472 total in 2 blocks; 3744 free (0 chunks); 79728 used
ErrorContext: 8192 total in 1 blocks; 8160 free (0 chunks); 32 used

ERROR: out of memory

DETAIL: Failed on request of size 40.
STATEMENT:   SELECT a.attname, a.atttypid,    pg_catalog.format_type(a.atttypid, a.atttypmod),    cast(a.attnotnull AS INTEGER) FROM pg_catalog.pg_attribute a WHERE a.attrelid = (select c.oid from pg_class c ,pg_user,pg_namespace n where relowner = usesysid AND relnamespace = n.oid AND relname = lower($1) AND usename = lower($2) AND n.nspname = lower($3) AND has_table_privilege(current_user, c.oid,'SELECT'))    AND a.attnum > 0 AND NOT a.attisdropped ORDER BY a.attnum
TopMemoryContext: 246368 total in 31 blocks; 31056 free (143 chunks); 215312 used
TopTransactionContext: 8192 total in 1 blocks; 6112 free (0 chunks); 2080 used
    CurTransactionContext: 0 total in 0 blocks; 0 free (0 chunks); 0 used
      CurTransactionContext: 0 total in 0 blocks; 0 free (0 chunks); 0 used
PL/pgSQL function context: 24576 total in 2 blocks; 2776 free (2 chunks); 21800 used
PL/pgSQL function context: 24576 total in 2 blocks; 11856 free (2 chunks); 12720 used
PL/pgSQL function context: 24576 total in 2 blocks; 15824 free (2 chunks); 8752 used
PL/pgSQL function context: 24576 total in 2 blocks; 8680 free (2 chunks); 15896 used
PL/pgSQL function context: 57344 total in 3 blocks; 16536 free (1 chunks); 40808 used
PL/pgSQL function context: 57344 total in 3 blocks; 32528 free (2 chunks); 24816 used
PL/pgSQL function context: 57344 total in 3 blocks; 30552 free (1 chunks); 26792 used

thanks for your help.

Re: Underlying DBMS error [ERROR: out of memory DETAIL: Faild on request of size 40.]

Anonymous User — Thu, 30 May 2013 11:05:40 GMT

Original User: vangelo

You've provided a lot of information (albeit incomplete with respect to ArcGIS
service packs and storage types involved), but what's the question?

This looks like a low-level database query failure. There isn't anything that
indicates any ArcGIS code is involved. You need to break the problem down
into smaller pieces, perhaps by exporting to file geodatabase, just to give
an indication of which instance generated the failure. If that works, then
you can try importing.

If it's the export that's failing, it might be related to the unsupported PG
build (8.3.9 v 8.3.0), but if it's been working up until now, it's odd that it
would stop working. I think it more likely you've got a database corruption
issue here, and not even Tech Support can help with that.

- V

Re: Underlying DBMS error [ERROR: out of memory DETAIL: Faild on request of size 40.]

TamerThamer — Tue, 04 Jun 2013 00:06:52 GMT

Hi Vince

Thanks for you help.

I've changed my way to import the data and I've used Import XML Workspace Document after I've exported.
The import process failed with this error message "Field is not editable" in the ArcCatalog and ERROR out of memory in the PostgreSQL log file.

Patch finder output

**********************ArcSDE install summary:**********************
ArcSDE 10.1 PostgreSQL (64-bit) Install Location:
/arcsde/base/arcgis/sdeexe101

*********ArcGIS Server install summary:********
ArcGIS 10.1 for Server Install Location:
/arcsde/base/arcgis/server

Service Pack / Patch / Hot Fix Found:

SP-ID: ArcGIS 10.1 SP1 for Server
Date Installed: 05/15/13 04:53:04

ArcGIS 10.1 for Desktop
ArcGIS 10.1 SP1 for Desktop
ArcGIS VBA Compatibility 10.1
ArcGIS 10.1 Data Interoperability for Desktop

*******************************************************************

Log file
.....
pg_foreign_server_name_index: 3072 total in 2 blocks; 1768 free (4 chunks); 1304 used
    pg_conversion_oid_index: 3072 total in 2 blocks; 1768 free (4 chunks); 1304 used
    pg_user_mapping_user_server_index: 3072 total in 2 blocks; 1704 free (4 chunks); 1368 used
    pg_conversion_name_nsp_index: 3072 total in 2 blocks; 1704 free (4 chunks); 1368 used
    pg_authid_oid_index: 3072 total in 2 blocks; 1720 free (3 chunks); 1352 used
    pg_auth_members_member_role_index: 3072 total in 2 blocks; 1704 free (4 chunks); 1368 used
    pg_tablespace_oid_index: 3072 total in 2 blocks; 1720 free (3 chunks); 1352 used
    pg_database_datname_index: 3072 total in 2 blocks; 1720 free (3 chunks); 1352 used
    pg_auth_members_role_member_index: 3072 total in 2 blocks; 1704 free (4 chunks); 1368 used
    pg_database_oid_index: 3072 total in 2 blocks; 1720 free (3 chunks); 1352 used
    pg_authid_rolname_index: 3072 total in 2 blocks; 1720 free (3 chunks); 1352 used
MdSmgr: 8192 total in 1 blocks; 2944 free (4 chunks); 5248 used
LOCALLOCK hash: 24576 total in 2 blocks; 9808 free (4 chunks); 14768 used
Timezones: 83472 total in 2 blocks; 3744 free (0 chunks); 79728 used
ErrorContext: 8192 total in 1 blocks; 8160 free (0 chunks); 32 used
ERROR: out of memory
DETAIL: Failed on request of size 232.
CONTEXT: SQL statement "UPDATE corp.sde.sde_layers
             SET minx = new_minx, miny = new_miny,
                 maxx = new_maxx, maxy = new_maxy,
                 minz = new_minz, maxz = new_maxz,
                 minm = new_minm, maxm = new_maxm
             WHERE layer_id = i_layer_id"
        PL/pgSQL function "sde_layer_def_envelope_update" line 7 at SQL statement
STATEMENT: SELECT corp.sde.SDE_layer_def_envelope_update ( $1, $2, $3, $4, $5, $6, $7, $8, $9)
TopMemoryContext: 221792 total in 28 blocks; 25808 free (142 chunks); 195984 used
TopTransactionContext: 8192 total in 1 blocks; 6448 free (0 chunks); 1744 used
    CurTransactionContext: 0 total in 0 blocks; 0 free (0 chunks); 0 used
PL/pgSQL function context: 24576 total in 2 blocks; 2776 free (2 chunks); 21800 used
PL/pgSQL function context: 24576 total in 2 blocks; 11856 free (2 chunks); 12720 used
PL/pgSQL function context: 24576 total in 2 blocks; 15824 free (2 chunks); 8752 used
PL/pgSQL function context: 24576 total in 2 blocks; 8680 free (2 chunks); 15896 used
PL/pgSQL function context: 57344 total in 3 blocks; 16536 free (1 chunks); 40808 used
PL/pgSQL function context: 24576 total in 2 blocks; 17176 free (2 chunks); 7400 used
PL/pgSQL function context: 24576 total in 2 blocks; 17336 free (3 chunks); 7240 used
PL/pgSQL function context: 57344 total in 3 blocks; 32528 free (2 chunks); 24816 used
PL/pgSQL function context: 57344 total in 3 blocks; 30552 free (1 chunks); 26792 used
RI compare cache: 24576 total in 2 blocks; 15984 free (5 chunks); 8592 used
RI query cache: 24576 total in 2 blocks; 11888 free (5 chunks); 12688 used
PL/pgSQL function context: 24576 total in 2 blocks; 9480 free (2 chunks); 15096 used
.....