|
POST
|
The successful connection using SQL Developer that you mentioned. Is the SQL Developer on the GIS Server? Were you able to connect using SQLPlus in Command Prompt on the GIS Server? Considering you are using the default 1521 port, you don't need to mention that in the connection string. Just try IP/GIS.
... View more
06-23-2017
09:51 AM
|
0
|
0
|
6000
|
|
POST
|
No, that "so on" was meant for any 9.3.x versions. Whenever 9.4.x will be supported, it will be mentioned separately.
... View more
06-20-2017
07:17 AM
|
0
|
0
|
1709
|
|
POST
|
I believe that you shared the results from the Diagnose tools. You can take a full DB backup and then execute the Repair tool. Repair Version Tables—Help | ArcGIS Desktop However, I'll recommend that if you are not completely sure, contact Esri Tech Support and they can guide you on a call and a quick screen sharing session.
... View more
06-19-2017
11:00 PM
|
1
|
3
|
4624
|
|
POST
|
Considering Oracle 12c was supported at ArcGIS 10.2.x (I think it was starting from 10.2.1), the 10.2.2 SDE Command line tools should work for the Oracle 12c databases at version 10.3. Its been sometime that I needed to use the SDE Command line tools, so I don't remember it exactly. This link ArcSDE application server for Oracle installation guide mentions that There is not a separate installation for Oracle 12c. Use the ArcSDE Application Server for Oracle 11g installation. Maybe a quick call to Esri Tech Support and they can show you.
... View more
06-19-2017
10:56 PM
|
1
|
1
|
2265
|
|
POST
|
1. No, its the same for both Server and Desktop. If you check the bottom of this link ArcGIS Server 10.5 system requirements—Installation Guides (10.5) | ArcGIS Enterprise , it lists the supported databases. Those links state the same thing and directs you to the same page I provided earlier. 2. No, the links mention the Base version which is supported with that ArcGIS release. Example: PostgreSQL 9.3.5 (64 bit) This indicates that 9.3.1, 9.3.2, 9.3.3 & 9.3.4 are not supported at ArcGIS 10.3.x However, versions higher than the base Supported version (in this case 9.3.5), that is, 9.3.6, 9.3.7 and so on are supported.
... View more
06-19-2017
10:36 PM
|
1
|
2
|
1709
|
|
POST
|
Use the tool Register with Geodatabase—Help | ArcGIS Desktop which is available from Desktop 10.5 or check this link FAQ: Can ArcSDE command line tools be used against 10.3 and newer geodatabases?
... View more
06-19-2017
10:29 PM
|
0
|
3
|
2265
|
|
POST
|
Your guess was spot on. PostgreSQL database requirements for ArcGIS 10.3.x—Help | ArcGIS Desktop Minimum supported database versions PostgreSQL 9.3.5 (64 bit) PostGIS 2.1 PostgreSQL 9.2.9 (64 bit) PostGIS 2.0 PostgreSQL 9.1.14 (64 bit) PostGIS 2.0
... View more
06-19-2017
01:17 AM
|
1
|
4
|
1709
|
|
POST
|
Creating versions and setting permissions—ArcGIS Help | ArcGIS Desktop You set the access level of a version to protect it from being edited or viewed by users other than the version owner. You can set one of three permissions on a version: Private: Only the owner or the geodatabase administrator may view the version and modify versioned data or the version itself. Protected: Any user may view the version, but only the owner or the geodatabase administrator may edit datasets in the version or the version itself. Public: Any user may view the version. Any user who has been granted read/write (update, insert, and delete) permissions on datasets can modify datasets in the version. When setting access on versions, consider your version workflow strategy along with the needs of the various users working within that framework. You should use version access along with dataset permissions to control access to the data. From your description, it seems all your Versions have the PUBLIC access level. A quick tour of reconciling a version—ArcGIS Help | ArcGIS Desktop Prerequisites To be able to reconcile, the following must be true: You must be the only user currently editing the version you are reconciling. No other user can be editing the target version. The exception is if the target version is DEFAULT—you can reconcile against DEFAULT even when other users are editing it. You must be able to view the target version, meaning it can be public or protected. If it is private, you must be the owner or the ArcSDE administrator. If your workflow is such that one user edits and another user reconciles, make sure the user who reconciles has full permissions to all the feature classes and tables that have been modified in the version; otherwise, he or she will not be able to reconcile. The user reconciling must have full permissions to both sides of any relationship that has been modified, including simple or composite relationships. In this type of workflow, the user reconciling must also have sufficient version permissions. The reconciling user must be able to modify the version to reconcile, meaning it must be public, and must be able to view the target version, meaning he or she either must own the version or it must be public or protected. These are the Prerequisites. So as long as you are meeting them, any user can be used to perform the Reconcile\Post. 3. In case of a Conflict, what options have you mentioned in the Script (your script is supposed to resolve conflicts in favor of the Parent version, which is Default). "FAVOR_TARGET_VERSION", By this I was intending to say that, whenever there is a Conflict, it will resolve in favor of the Target version (which is Default in your case). So the conflicting edits in the Edit\Child Version will be lost. For your experimentation, do not delete the same feature that you just created. Instead delete another feature which was already present and then check the behavior.
... View more
06-14-2017
11:06 AM
|
1
|
0
|
1609
|
|
POST
|
Partial Compress is not an issue. You can do the Full Compress later sometime by deciding upon a convenient downtime for that geodatabase. take a look at this link: Acheiving Full Compress on Geodatabases with Existing Replicas | Support Services Blog
... View more
06-14-2017
03:03 AM
|
1
|
5
|
4625
|
|
POST
|
This is called a Partial Compress and can be expected in multiple scenarios: 1. There are editors editing when you ran the compress 2. Because of Orphaned connections 3. ArcGIS Server services are running Geodatabase compression—Help | ArcGIS Desktop In a fully compressed geodatabase, there are no rows in the delta tables and the state tree is trimmed back to zero. Performance improvement is greatest if the geodatabase is fully compressed. To achieve this, do the following: Reconcile and post all outstanding changes in child versions to the DEFAULT version. As the geodatabase administrator, you can see in what order versions should be reconciled by default by opening the Reconcile Order subtab of the Versions tab on the Geodatabase Administration dialog box. See Version properties for information on the Reconcile Order subtab. Delete the versions themselves after you have reconciled and posted edits. Make sure no user is connected. Perform the compression operation. So try these steps and then let us know if there are still records left in the Delta Tables after the Compress operation.
... View more
06-14-2017
02:59 AM
|
1
|
0
|
556
|
|
POST
|
No. You should not play with the Tables in a Geodatabase from the database end. Inconsistencies may occur later. Maybe you can share the issue, which is leading you to delete the records from the Delta tables and can find a solution for that here.
... View more
06-14-2017
02:43 AM
|
1
|
9
|
4624
|
|
POST
|
When you are using Versioned Data, query the Versioned Views for the latest records. The Base\Business Tables will not have all the recent edits unless you have perform a Compress. The compress moves the recent edits from the Delta Tables (a- & d- Tables) into the Base table. What is a versioned view?—Help | ArcGIS Desktop When you query a versioned view, you can see the data in the base (business) table and the edits that are stored in the delta tables.
... View more
06-13-2017
01:13 PM
|
0
|
1
|
1205
|
|
POST
|
Some things to keep in mind while trying these: 1. What are the access levels of the Versions? 2. Which login are you using to connect and perform the reconcile\post 3. In case of a Conflict, what options have you mentioned in the Script (your script is supposed to resolve conflicts in Favour of the Parent version, which is Default). If you are connecting using any Admin login(example: any sysadmin login in SQL Server) to connect and perform the Reconcile\Post, then it should work for all scenarios.
... View more
06-13-2017
01:07 PM
|
0
|
0
|
1609
|
|
POST
|
An official confirmation for these information(specially related to upcoming releases) can only be provided by Esri Tech Support.
... View more
06-13-2017
04:23 AM
|
0
|
0
|
1774
|
|
POST
|
Make sure the new database has the same properties as the database you are going to restore, including name, encoding, and owner. Restore a geodatabase to PostgreSQL—Help | ArcGIS Desktop (Same link as George provided in his answer....check it for more details)
... View more
06-09-2017
06:29 AM
|
3
|
1
|
2274
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 10-12-2017 12:37 PM | |
| 4 | 06-18-2025 05:53 AM | |
| 1 | 02-19-2025 02:49 AM | |
| 1 | 02-05-2025 09:56 AM | |
| 2 | 12-16-2024 11:02 PM |
| Online Status |
Offline
|
| Date Last Visited |
3 weeks ago
|