ArcSDE install on PostgreSQL

VitantonioRifino — Thu, 23 Sep 2010 08:42:37 GMT

Hello,

i have installed arcsde 9.3 on windows xp sp3. Post-install program seems to work fine with postgresql 8.3 (same computer); but i notice some errors in sde_setup.log.

wise_err.log:
WARNING: Parameter "TEMP" not found in giomgr.defs file!
WARNING: Setting TEMP to "C:\DOCUME~1\ADMINI~1\IMPOST~1\Temp"
WARNING: Parameter "TEMP" not found in giomgr.defs file!
WARNING: Setting TEMP to "C:\DOCUME~1\ADMINI~1\IMPOST~1\Temp"

ESRI ArcSDE Server Setup Utility Thu Sep 23 11:15:28 2010
----------------------------------------------------------------
Creating ST_GEOMETRY and ArcSde schema.....
Successfully created ST_GEOMETRY and ArcSde schema.

Installing locators.....
Successfully installed locators.

Creating geodatabase schema.....
Successfully created GDB schema.

Successfully installed ArcSDE components.
Refer SDEHOME\etc\sde_setup.log for more details.

sde_setup.log:
[Thu Sep 23 11:15:28 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "sde.sde_server_config" does not exist

[Thu Sep 23 11:15:28 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "sde.sde_dbtune" does not exist

[Thu Sep 23 11:15:28 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "sde.sde_server_config" does not exist

[Thu Sep 23 11:15:28 2010] ST_GEOMETRY support being installed...
[Thu Sep 23 11:15:31 2010] ST_GEOMETRY support installed...
[Thu Sep 23 11:15:31 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "sde.sde_server_config" does not exist

[Thu Sep 23 11:15:31 2010] VERSION table created...
[Thu Sep 23 11:15:31 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "sde.sde_coordinate_systems" does not exist

[Thu Sep 23 11:15:31 2010] COORDINATE_SYSTEMS table being created...
[Thu Sep 23 11:15:31 2010] COORDINATE_SYSTEMS table created...
[Thu Sep 23 11:15:31 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "public.sde_spatial_references" does not exist

[Thu Sep 23 11:15:31 2010] SPATIAL_REFERENCES table being created...
[Thu Sep 23 11:15:31 2010] SPATIAL_REFERENCES table created...
[Thu Sep 23 11:15:31 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "sde.sde_geometry_columns" does not exist

[Thu Sep 23 11:15:31 2010] GEOMETRY_COLUMNS table being created...
[Thu Sep 23 11:15:32 2010] GEOMETRY_COLUMNS table created...
[Thu Sep 23 11:15:32 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "sde.sde_layers" does not exist

[Thu Sep 23 11:15:32 2010] LAYERS table being created...
[Thu Sep 23 11:15:32 2010] LAYERS table created...
[Thu Sep 23 11:15:32 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "sde.sde_metadata" does not exist

[Thu Sep 23 11:15:32 2010] METADATA table being created...
[Thu Sep 23 11:15:32 2010] METADATA table created...
[Thu Sep 23 11:15:32 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "sde.sde_raster_columns" does not exist

[Thu Sep 23 11:15:32 2010] RASTER_COLUMNS table being created...
[Thu Sep 23 11:15:32 2010] RASTER_COLUMNS table created...
[Thu Sep 23 11:15:32 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "sde.sde_table_registry" does not exist

[Thu Sep 23 11:15:32 2010] TABLE_REGISTRY table being created...
[Thu Sep 23 11:15:32 2010] TABLE_REGISTRY table created...
[Thu Sep 23 11:15:32 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "sde.sde_states" does not exist

[Thu Sep 23 11:15:32 2010] STATES table being created...
[Thu Sep 23 11:15:32 2010] STATES table created...
[Thu Sep 23 11:15:32 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "sde.sde_versions" does not exist

[Thu Sep 23 11:15:32 2010] VERSIONS table being created...
[Thu Sep 23 11:15:32 2010] VERSIONS table created...
[Thu Sep 23 11:15:32 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "sde.sde_mvtables_modified" does not exist

[Thu Sep 23 11:15:32 2010] MVTABLES_MODIFIED table being created...
[Thu Sep 23 11:15:32 2010] MVTABLES_MODIFIED table created...
[Thu Sep 23 11:15:32 2010] STATE_LINEAGES table being created...
[Thu Sep 23 11:15:32 2010] STATE_LINEAGES table created...
[Thu Sep 23 11:15:32 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "sde.sde_locators" does not exist

[Thu Sep 23 11:15:32 2010] LOCATORS table being created...
[Thu Sep 23 11:15:32 2010] LOCATORS table created...
[Thu Sep 23 11:15:32 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "sde.sde_xml_index_tags" does not exist

[Thu Sep 23 11:15:32 2010] XML tables being created...
[Thu Sep 23 11:15:33 2010] Warning: Error querying tsearch2 system table schema. You will
need to grant select access to public to pg_ts_cfg,pg_ts_cfgmap
pg_ts_dict,pg_ts_parser for xml functionality
[Thu Sep 23 11:15:33 2010] XML tables created...
[Thu Sep 23 11:15:33 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "sde.sde_column_registry" does not exist

[Thu Sep 23 11:15:33 2010] COLUMN_REGISTRY table being created...
[Thu Sep 23 11:15:33 2010] COLUMN_REGISTRY table created...
[Thu Sep 23 11:15:33 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "sde.sde_archives" does not exist

[Thu Sep 23 11:15:33 2010] ARCHIVES table being created...
[Thu Sep 23 11:15:33 2010] ARCHIVES table created...
[Thu Sep 23 11:15:33 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "sde.sde_logfile_pool" does not exist

[Thu Sep 23 11:15:33 2010] LOGFILE_POOL tables being created...
[Thu Sep 23 11:15:33 2010] LOGFILE_POOL tables created...
[Thu Sep 23 11:15:34 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "sde.sde_dbtune" does not exist

[Thu Sep 23 11:15:34 2010] DBTUNE table being created...
[Thu Sep 23 11:15:34 2010] DBTUNE table created...
[Thu Sep 23 11:15:34 2010] ev.SQLstate = 42P01
SDE DBMS Error: -37 ERROR: relation "sde.sde_server_config" does not exist

[Thu Sep 23 11:15:34 2010] SERVER_CONFIG tables being created...
[Thu Sep 23 11:15:34 2010] SERVER_CONFIG tables created...
[Thu Sep 23 11:15:34 2010] DBMS stored procedures being created or updated...
[Thu Sep 23 11:15:36 2010] DBMS stored procedures created or updated...
[Thu Sep 23 11:15:36 2010] WARNING: Config parameter "XML_TS_CONFIG" not found in keyword "DEFAULTS".
Inserting the default values.
[Thu Sep 23 11:15:36 2010] WARNING: Config parameter "UI_TOPOLOGY_TEXT" not found in keyword "TOPOLOGY_DEFAULTS".
Inserting the default values.
[Thu Sep 23 11:16:00 2010]
Successfully installed ArcSde.

Successfully created locator "Single Field"
Successfully created locator "StreetMap USA"
........
Successfully created locator "ZIP (5-Digit)"
[Thu Sep 23 11:18:09 2010] Upgrading geocoding rules.....
[Thu Sep 23 11:18:09 2010] Creating table GCDRULES...
[Thu Sep 23 11:18:09 2010] Installing geocoding rules...
[Thu Sep 23 11:18:10 2010] Geocoding rules installed.
[Thu Sep 23 11:18:10 2010] Successfully upgraded geocoding rules.

Creating GeoDatabase Schema
---------------------------
Creating table GDB_tables_last_modified...
Granting permissions...
Permissions Granted...
.....
Creating table GDB_ExtensionDatasets...
Granting permissions...
Permissions Granted...
Registering OID column ID on table GDB_ExtensionDatasets

I can't understand if the installation is fine or not.
any idea ?

thanks,
Vito

Re: ArcSDE install on PostgreSQL

VinceAngelo — Thu, 23 Sep 2010 11:09:25 GMT

It's common to see "table does not exist" errors during initial creation, since it's
best practice to check if something already exists before creating it. SQL doesn't
generally have an "exists" function, so you query permissions and let the "table
not found" error stand as an answer. It's perhaps misleading to use a single
error-handling function when you *expect* an error, but we're just talking about
a setup log, after all.

- V

Re: ArcSDE install on PostgreSQL

VitantonioRifino — Thu, 23 Sep 2010 11:37:19 GMT

It's common to see "table does not exist" errors during initial creation, since it's
best practice to check if something already exists before creating it. SQL doesn't
generally have an "exists" function, so you query permissions and let the "table
not found" error stand as an answer. It's perhaps misleading to use a single
error-handling function when you *expect* an error, but we're just talking about
a setup log, after all.

- V

Thanks,
Vito

topic ArcSDE install on PostgreSQL in Data Management Questions

ArcSDE install on PostgreSQL

Re: ArcSDE install on PostgreSQL

Re: ArcSDE install on PostgreSQL