nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

SDE and ArcMap Desktop interoperability by version? (SDE 10.1, ArcMap 10.0 and 10.1)

howardfoster

Hello all,

I have successfully installed ArcSDE 10.1 for postgres (PostgreSQL) on both Linux and Windows machines. From ArcMap 10.1, these work fine, but I�??m having problems writing layers from ArcMap 10.0 to these databases, which leads me to wonder if you can�??t write from Desktop clients version 10.0 to SDE 10.1�??is this true? Or did I do something wrong. I remember seeing a table of Desktop and SDE interoperability by versions with entries something like ... read+write, read-only, <blank=none>. Can someone give me a pointer to this table?

If I did something wrong, then I can report error messages, etc, plus results of interoperabiliy experiments.

Any pointers appreciated, thanks for your help,
-H

Finde mehr Beiträge mit dem Tag

Accepted answers

All comments

VinceAngelo

What sort of problems are you having?

- V

AsrujitSengupta

Desktop 10.0 can write/read data from SDE 10.1, without any problem.

The error message would help us to understand better, the problem that you are facing.

howardfoster

A short answer is... from ArcCatalog 10.0 to sde 10.1, via a direct connection, when I "import" a vanilla vector file, I get a string of error messages, the most significant one is "function or procedure does not exist...DBMS table not found". I will have more details later on. (Things work fine with desktop 10.1 to sde 10.1.) Thank you for your prompt replies. -H

howardfoster

More on error messages. Here's a typical screen shot from a 10.0 client trying to import a feature layer into SDE 10.1 (Windows machine). Should I be installing some additional software to make 10.0 clients connect to sde 10.1+postgresql (similar to that which is needed for ArcMap 10.1)?
-H

sde_failure.jpg

tKasiaTuszynska

HFoster,
You have seemed to find a bug fixed with sp5:
NIM080370 - PostgreSQL: ArcGIS 10.0 clients must be able to create, import, or paste feature classes into a 10.1 geodatabase.

This was an issue one would find when connecting from 10.0 client(Desktop, Engine, ArcGIS Server) to 10.1 server (postgres/sde), and working with data with the default spatial reference settings of 4326.
Is this consistent with your data environment?

The fix is in 10sp5
http://gisupdates.esri.com/10sp5/ArcSDE/ArcSDE10sp5-issues.htm

Sincerely,
Kasia

howardfoster

Well, some progress with 10.0 clients. I upgraded to SP 5 and they now can write layers to SDE 10.1 via direct connections (reading has never been a problem). Service connections for both reading and writing through, e.g., port 5151 remain undoable (again, this is only 10.0 clients to SDE 10.1--10.1 to 10.1 has always worked just fine via both methods), and I get the bizarre error message, reported below, when I try to make the connection (.sde) file. I guess I will declare partial victory and begin to deploy 10.1 servers. 9.3.1 (SP 2) client connections to SDE 10.1 remain completely undoable.

If anyone has had success connecting 9.3.1 clients to 10.1 and/or service connections from 10.0 to 10.1, I would sure love to hear from you. Remember, this is for PostgreSQL 9.0.5.

Bizarre error message when attempting to define a service connection: basically I get cross-database error message and reference to the wrong database. Somehow database references are being confused in the connection attempt. Here�??s an example:

Failed to connect to the specified server.
FDO error: -2147216072
Underlying DBMS error [ERROR: cross-database references are not implemented: <wrong_database>.sde.gdb_release
LINE 1: select <wrong_database>.sde.gdb_release.* from <wrong_database>.sde...
^
::SQL state: 0A000] [<wrong_database>.GDB_Release]

Thank you all, -Howard

VinceAngelo

You will not ever get a 9.3.1 client to work with a 10.1 server -- It's hard enough to make
the last one or two service packs of release N connect to N+1 without trying for a 2-3 year
leap forward from N-1 to N+1.

The client and geodatabase compatibilty matrix is published in advance of the N+1 release,
so users can start geodatabase upgrade planning.

- V

DanielMrvos

Heya,

we have the same issues. Client 10.0 can't connect to a sde GDB if there is more than one database to connect to in PostgresSQL, through sde service. And in the compatibility matrix it says it can, 10.0 clients can conect to sde 10.1.

We also tried this reference http://support.esri.com/en/knowledgebase/techarticles/detail/36445

But given that sde 10.1 doesn't have sdesetup -o install the last step was a little bit difficult.

When connecting through sde 10.1 service with a client of 10.0 the connection somehow gets confused. For instance if I want to connect to Database1 it tries to connect to Database2
If you connect with a 10.1 client everything works as expected.

We tried it with every client version that we got. The error is the same as HFOSTER stated it. And what he meant with <wrong database> is that the connection tries to connect to another database than stated in the database connection.

The setup is as follows:

SDE 10.1 SP1 on Linux64.
PostgresSQL 9.1.3 on Linux64.
ArcGis for Desktop Advanced (SP1, postgresql patch) x 1
ArcEditor x2 (10.0) (SP5)
ArcGis for Desktop Basic x1 (SP1, postgresql patch)
ArcView (10.0) x2 (SP5)

Thanks....

VinceAngelo

ArcSDE application services can only run in one database (can't connect to multiple databases
through one service).

What values are you placing in the various connection parameters at 10.0 SP5? Are you using
Direct Connect or an application server port?

What PostgreSQL client libraries are you using on the various hosts?

- V

DanielMrvos

ArcSDE application services can only run in one database (can't connect to multiple databases
through one service).

What values are you placing in the various connection parameters at 10.0 SP5? Are you using
Direct Connect or an application server port?

What PostgreSQL client libraries are you using on the various hosts?

- V

Heya,

to clarify things a little bit here is the complete setup:

SDE server (Linux64):

-- /etc/services:
db1        6629/tcp
db1        6629/udp
db2        6630/tcp
db2        6630/udp

-- $SDEHOME/etc/services.sde

db1        6629/tcp
db2        6630/tcp

-- $SDEHOME/etc/dbinit_db1.sde

set PGHOST=/var/run/pgsql
set SDE_DATABASE=db1

-- $SDEHOME/etc/dbinit_db2.sde

set PGHOST=/var/run/pgsql
set SDE_DATABASE=db2

PGHOST=/var/run/pgsql SDE_DATABASE=db1 sdemon -o start -i 6629
PGHOST=/var/run/pgsql SDE_DATABASE=db2 sdemon -o start -i 6630

Connection Properties db1 (ArcCatalog 10.0):

Server: <address of db server>
Service: 6629
Database: db1
Database Authentication:
         Username: sde
         Password: <sde password>

Connection Properties db2 (ArcCatalog 10.0):

Server: <address of db server>
Service: 6630
Database: db2
Database Authentication:
         Username: sde
         Password: <sde password>

Connection Properties db1 (ArcCatalog 10.1):

Database Platfrom: Application Server
Server: <address of db server>
Service: 6629
Database Authentication:
         Username: sde
         Password: <sde password>
Database: db1

Connection Properties db2 (ArcCatalog 10.1):

Database Platfrom: Application Server
Server: <address of db server>
Service: 6630
Database Authentication:
         Username: sde
         Password: <sde password>
Database: db2

With 10.1 clients everything works normal. With 10.0 I can't establish a connection. For instance if I try to connect to db1 I get the same error message as hfoster for db2.

I don't use any client libraries because until 10.0 they weren't needed for SDE connections. And for 10.1 it works without client libraries.

Regards...

VinceAngelo

I always use multiple SDEHOMEs for multiple instances, partially because
I don't have the patience to work out how the files need to be named in
oreder to run multiple instances out of one. But I don't think your setup
is correct:
1) ArcSDE doesn't use UDP, so there's no reason to have duplicate
service name entries
2) If you do use one SDEHOME, your "-i" parameter should be the
service name (dbN), not the port number (so it finds the dbinit file)

I don't see how the 10.1 clients can be connecting to the right database,
but if they do, there's no apparent reason why the 10.0 clients should
not have the same behavior.

First off, use the service name in your 'sdemon' directives. If it still fails,
try using two different SDEHOME directories. If that fails, contact Tech
Support.

- V

DanielMrvos

I always use multiple SDEHOMEs for multiple instances, partially because
I don't have the patience to work out how the files need to be named in
oreder to run multiple instances out of one. But I don't think your setup
is correct:
1) ArcSDE doesn't use UDP, so there's no reason to have duplicate
service name entries
2) If you do use one SDEHOME, your "-i" parameter should be the
service name (dbN), not the port number (so it finds the dbinit file)

I don't see how the 10.1 clients can be connecting to the right database,
but if they do, there's no apparent reason why the 10.0 clients should
not have the same behavior.

First off, use the service name in your 'sdemon' directives. If it still fails,
try using two different SDEHOME directories. If that fails, contact Tech
Support.

- V

Heya,

thx for the reply. Tried it with instance name, same problem. Will try the multiple SDEHOME approach during the weekend.

Tried our regional Tech Support but they only gave me the afformentioned bug report or to use direct connections, but I'm not as ambitious as to change the connection properties and installations on 30+ computers 🙂

Regards...

MarcoBoeringa

1) ArcSDE doesn't use UDP, so there's no reason to have duplicate
service name entries

Vince, this was my understanding always too, but looking at the 10.1 Help regarding Starting a remote ArcSDE service on Linux or UNIX, I now read this:

"2. As the root user, duplicate the service name in the /etc/services file as a User Datagram Protocol (UDP) entry that uses the same port number on both the local and remote servers.

# \etc\services
esri_sde 5151/tcp
esri_sde 5151/udp

3. As the root user, update the /etc/inetd.conf file. Add this line to the bottom of the file.

<ArcSDE instance> dgram udp wait <owner of ArcSDE home>
<$SDEHOME>/bin/sderemote iomgr_inetd
<$SDEHOME><ArcSDE instance>"

The UDP connection seems necessary for running the ArcSDE service from a remote server, so in case it is installed on a physically separate server from the database server it uses the data from, as written on this Help page.

P.S. Just to clarify for other Forum users reading this thread...

VinceAngelo

UDP is used for remote server start, but I've never seen a need to use that feature.
Cluttering the services file with unused references isn't best practice.

- V

Nimm an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.