Latest Contributions by tKasiaTuszynska

Matt, not sure what you mean by comment out the entries for ipv4 and ipv6 completely?Do the settings below work? - first row for ipv4 - second for ipv6 this is opening ipv4 and ipv6 wide open.... host all         all         0.0.0.0/0          md5 host all all ::/0 md5 Kasia ... View more

Hello Everybody, The most common reason for not seeing data created in a nongdb, regardless of type is that it is not owned by the user that owns the schema. For example: - you are logged into pgAdminIII as postgres - you are creating a table in the map schema - since you are logged in as postgres user the table resides in the map schema but it owned by the postgres user - in this case you will NOT see that data in Desktop - solution is to alter the table to grant ownership to the schema owner ALTER TABLE map.table OWNER to MAP; The second most common reason why nongdb data would not be visible in Desktop is that the objectid column is not defined with the "NOT NULL" constraint. The references to the pg trace showing that sde_layers table does not exist, is a just a check for the presence of that table, which in the case of a nongdb is correct in it's absence. Sincerely, Kasia ... View more

Vivek, Unfortunately our naming convention for the st_geometry libraries specific to the version of Postgres could have been improved in 10.2. The st_geometry library is build specific to the version of Postgres and specific to the version of the geodatabase. So, if you are running Postgres 9.2, you need a library built for 9.2, which resided in the 9.2 folder under DatabaseSupport, if you took just the "st_geometry" library residing directly in the DatabaseSupport folder that library was build for Postgres 9.0.5. In which case you got a correct error message. You can always check what version a library is built for, they are signed. Right- click on the library in question, look under properties, details, the Postgres version will be indicated in the first line. The linux libraries are also signed, use the "strings" command, at the very end of the output you will see the Postgres version. For future versions of the Database Support folder we have changed the structure to place all st_geometries in folders that indicate the Postgres version. Sincerely, Kasia ... View more

Andrew, Creating a gdb from Catalog against a Postgres instance in the cloud can be painful, ArcCatalog communicating to the instance and back will be very slow and can eventually time out. Sorry you are incurring frustration. The only thing I would recommend would be to execute the python tool to create a gdb locally on the amazon instance where postgres is installed. You can copy and paste the python syntax right out of documentation. Sincerely, Kasia ... View more

Carlos, a bad log in user error from postgres means that you were not passing in a correct password or that postgres was not setup to allow connections from your ip address, by changing the authentication method in pg_hba. conf from md5 to trust, you told postgres not to check your password. Which suggests that the bad login error was comming from passing in a wrong password. ... View more

dkav, Upon establishing a connection, the sde code determines what if any version of PostGIS is installed on the Postgres instance, the message you posted, is an indication that no PostGIS version is installed. It does not mean that you need to install it nor that anything is broken it is just a bit of discovery by our code when connecting. Sincerely, Kasia ... View more

Ufeliciano, I am weary of aliasing in PostgreSQL, the following query gave correct results: select sde.block_groups.tract90, sde.census_tracts.tract90 from sde.block_groups , sde.census_tracts where sde.st_intersects (sde.census_tracts.shape, sde.st_centroid(sde.block_groups.shape)); Sincerely, Kasia ... View more

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 ... View more

Holm, I am sorry that you have incurred frustration. For 10.1 we support the following: Postgres server on a 64bit os platform ArcGIS Server on 64bit os platform Please try the following steps: 1. place the 64bit postgers client libraries in the ArcGIS Server/bin location - you can use the 9.0.2 or 9.0.5 or the 9.1.3 libs, we have found no difference between them yet, but to be save I would recommend using the ones that correspond to your postgres server version. - they are located in the Customer Care portal, under DBMS Support Files - to my knowledge Postgres does not distribute their client libraries as a separate download, we separate them out and place them on the Customer Care portal for your convenience but aside from installing the postgres software on a 64bit os and separating out the libpq libraries and their dependencies, I do not know of any other way of finding them. - I am guessing that you have gotten past this step since you are getting the st_geometry lib errors. 2. place the st_geometry library in the postres lib location - on windows, the postgres lib loction is the following: C:\Program Files\PostgreSQL\9.0\lib - the ArcGIS Server installation will provide you with st_geometry lib version per postgres version, per os - the build of the library is specific to the version of Postgres, for example you can not use the 9.0.2 build of st_geometry with Postgres 9.1 etc. If your postgres version is 9.0.5 than you have to use the library build with 9.0.5. - if the Postgres installation is on a linux os, it may be tricky to place the st_geometry library in the correct place, since the place varies depending on how you installed Postgres. The safest way is to refer to the PKGLIBDIR value listed with pg_config and place the library there, please make sure that it is executable. - if ArcGIS Server is on a linux os, than you will need to fill out the init_user_param.sh under .../arcgis/server/usr for a direct connect to work Please respond if this was not helpful, Most Sincerely, Kasia ... View more

James, From the error message it seems that the tool is outputing to a surface, which is 3d polygon data. I think that there might be some mix up with versions of PostGis, What version of PostGIS do you have on your Postgres instance. Sincerely, Kasia ... View more

David, Couple of questions: Can you give an example of the sdeexport command? I am not aware of Postgres having issues on a restore if it runs out of RAM, but 2 gigs is the limit of memory that a window process can use, if Postgres was affected by lack of memory it would tell you that in the error logs. When you are restoring, you are restoring public schema first and than any other schema you might have right? Some amount of errors are expected because we have to brake up the restore. Postgres 8.3.8 does not have any replication features as part of the core product, that only came out recently with Postgres 9.1, so if you wanted to use db replication you would have to use one of the Postgres modules like Slony, for example. Most Sincerely, Kasia ... View more

Jarkko, The bug I am referring to should have made it impossible for you to create a gdb, or upgrade an existing one to prerelease if the settings on the client machine are non English, meaning that they use a "," instead of "." for decimal separation. The "errors" you have posted are the queries we send to postgres to make sure that the objects to do not exist before they are created, so they are not really errors. If you are indeed running into the bug I am referring to you should see a postgres level error when trying to create the spatial index on the gdb_items table, you may have to switch to loggin "ALL" in postgresql.conf to see it. Most Sincerely, Kasia ... View more

Shawn, I am glad that we are not hindering you too much. If this is fixed for sp5, you will see it listed as a known issue on the sp download page. Thanks for testing, Sincerely, Kasia ... View more

Shawn, Per your original post; I am able to reproduce your experience, on 10.0 sde for postgres, I am not able to create a mv view, with the table definitions given in your post. The issue is not reproducable in 10.1. It is up to you if you want to pursue this to be fixed for 10 sp5 or will you be migrating to 10.1? Most Sincerely, Kasia Tuszynska ArcSDE Product Engineer ... View more