POST
|
Hey Josh, Just wondering if you found any additional resources you found useful. Thanks, Matt
... View more
03-18-2017
09:08 AM
|
0
|
1
|
576
|
POST
|
Thanks, Vince. It was surprising to me, though, that we don't experience the same problem when using either a View or Query Layer.
... View more
05-05-2014
04:57 AM
|
0
|
0
|
476
|
POST
|
Hello, We are using Postgresql (9.2) database replication to distribute the load between a master and a slave. For a variety of reasons, we thought replicating at the Postgresql level instead of using ArcGIS's Geodatabase replication (we have a hot stand-by that we're replicating using both streaming and log-shipping) would work better for us. One of the limitations of using a postgresql replication in this way is that the slave is read-only, which we thought would be fine. We would make all the changes on the master and they would be pushed to the slave. And that is working great. The problem is that users who connect to the slave often receive this error (ERROR: cannot execute nextval() in a read-only transaction::SQL state: 25006) while do a spatial selection, either by doing "Select by Location" or using the Select Tool. [ATTACH=CONFIG]33564[/ATTACH] The error is sensitive to how large of a geographic area the user is selecting--smaller areas work fine, larger areas receive the error. I have found that if I access the same data via either a View or Query Layer (Select * from featureclass) , I do not receive the error at all so that is a possible work-around. However, both of these are 3-4 times slower than just accessing the feature class directly. I've got a support request working it's way through "channels" but wondered if the collective wisdom here might have any suggestions. Thanks for any ideas! Database servers: Windows 2008 r2, Postgresql 9.2 Clients: ArcGIS 10.2.1, Windows 7
... View more
05-02-2014
09:51 AM
|
0
|
3
|
2518
|
POST
|
I just want to confirm that as of 10.2, this still occurs, at least using a postgresql geodatabase (10.2 ArcGIS, postgres 9.2). I was NOT able to re-create the problem using either a file or personal geodatabase.
... View more
04-02-2014
06:14 AM
|
1
|
0
|
992
|
POST
|
I haven't found a way to actually use relative paths but I did find a tip in this Forum thread that points out you can repair the paths for a Mosaic Dataset by right-clicking on it in ArcCatalog and selecting, "Repair ...". While not really relative paths, it has allowed me to successfully move the source data and not have to painfully recreate my mosaic dataset. http://forums.arcgis.com/threads/32259-mosaic-dataset-change-path-after-the-fact
... View more
04-27-2012
06:11 AM
|
0
|
0
|
734
|
POST
|
It may be best to delete the entries from the 'sde.sde_process_information' table. What database are using (Oracle, SQL Server, PostgreSQL,...)? Thanks for the tip, Jake. I've been familiar with this table but didn't know if it was safe/acceptable to just delete rows for old connections or if I needed to go the sdemon -o kill route.
... View more
04-03-2012
04:15 AM
|
0
|
0
|
1483
|
Title | Kudos | Posted |
---|---|---|
1 | 04-02-2014 06:14 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|