POST
|
fawna, NIM059456 refers to the internal tracking number for the requested functionality. If you were to log a call with Esri Technical Support with this request your account would be attached to this reference. I would advise raising the profile of this request on the Ideas Portal where you have the ability to outline the exact enhancement requested and have others in the community vote for the suggestion. This site is actively reviewed by developers and receives greater exposure than an enhancement request. - Jon
... View more
03-29-2012
03:40 AM
|
0
|
0
|
388
|
POST
|
There is currently an enhancement request for the functionality to enable export of raster fields to a report: NIM059456: Support the display of raster images from raster field and Hyperlinked sources in reports
... View more
03-28-2012
05:39 AM
|
0
|
0
|
388
|
POST
|
Bharathi, Using the default of shared logfiles in Oracle you should see the SDE_LOGFILES and SDE_LOGFILE_DATA tables within each schema that will perform selections et al following the creation of a selection set >100. The choice of which log file type to use is dependent upon various factors yet for most configurations within Oracle shared will suffice. ArcSDE log file tables in a geodatabase in Oracle From a review of your sdeconfig.txt file it appears as though your config file is set to use both shared, session, and standalone log files to some extent. It could be that due to the settings within this table your instance is trying to use standalone log files which require more elevated permissions than the other types. In what order do ArcSDE log file types get used? The following settings are needed in the SERVER_CONFIG table to create shared log file tables: MAXSTANDALONELOGS = 0 ALLOWSESSIONLOGFILE = FALSE LOGFILEPOOLSIZE = 0 Granting the following permissions to the user schema in question should enable the logfile tables to be created: CREATE SESSION CREATE TABLE CREATE SEQUENCE After the log file tables are created within the user's schema the CREATE TABLE permissions can be revoked. - Jon
... View more
03-27-2012
03:36 AM
|
0
|
0
|
1370
|
POST
|
Quinn, Edits made within a Multiversioned view behave similarly as if you were to make edits within a version in ArcMap. They create states within the delta tables and can be synchronized with a relative replica elsewhere in the same manner. There are some limitations in the type of data you may edit however: What type of data can be edited using SQL? - Jon
... View more
03-26-2012
08:27 AM
|
0
|
0
|
939
|
POST
|
A full compress *can* pull data from the business tables into your default version yet there are many areas where error can be introduced if your workflow is not completed precisely. In theory you could edit the business tables if the data was not registered as versioned, when using move-to-base editing, or through a careful workflow to pull these base edits into the sde.DEFAULT. If you are sold on using SQL to edit the attributes the best move would be to use a mutliversioned view to edit these attributes within SQL Server. This would enable you to edit using the sql comands as you desire but do it within a version. Multiversioned views incorporate database views, stored procedures, triggers, and functions to access a specified version of data in a geodatabase table using Structured Query Language (SQL). What are multiversioned views? Creating Multiversioned Views Editing versioned data in SQL Server using multiversioned views and SQL
... View more
03-23-2012
11:49 AM
|
0
|
0
|
939
|
POST
|
Quinn, I would be weary of editing the backend SQL base tables for the sake of convenience. While there are editing scenarios that would accommodate this, a replica is not one of them. The replica synchronization depends on edits being made to the delta tables which are then flagged and sent over the the relative replica upon the sync operation. Editing the base table directly would not update these deltas...as a result the edits would never be sent over to the parent replica. - Jon
... View more
03-23-2012
09:33 AM
|
0
|
0
|
939
|
POST
|
Hi Chad, Could you provide a screenshot of your sde.versions, sde.mv_tables_modified, sde.state_lineages, and sde.compress_log for review. The usual reason for behavior such as this is locks, edit connections, orphaned states, or replicas in need of synchronization. If none of these appear to be leading to this behavior we would need to investigate this further. You can also call Esri Technical Support with this information as well and they should be able to assist you rather quickly through a series of tests. - Jon
... View more
03-23-2012
08:49 AM
|
0
|
0
|
1619
|
POST
|
Chad - Following removal of the versions and running of compress these states should have been truncated and SDE.DEFAULT should point to 0. Do you have any orphaned state_locks within your ArcSDE repository? I would recommend contacting Technical Support with your full system configuration as well as a screenshot of your sde.versions table to investigate this further. - Jon
... View more
03-22-2012
09:05 AM
|
0
|
0
|
1619
|
POST
|
SQL Server 2012 will be supported in 10.1 Final release.
... View more
03-22-2012
08:59 AM
|
0
|
0
|
896
|
POST
|
cfoster15, Have you run a compress following the deletion of your boss' version? Do you have any replicas synchronize versions within this configuration? - Jon
... View more
03-22-2012
08:51 AM
|
0
|
0
|
1619
|
POST
|
Monjur, Exit Status 255 is not an ArcSDE exit code but from Oracle. Could you upload the logs from ArcSDE from when this issue was encountered? We may be able to glean more information from these errors. Check out the Oracle alert.log and Windows Event Viewer for additional information outside of that seen within the %SDEHOME%\etc error logs. Does this behavior affect direct-connections? - Jon
... View more
03-22-2012
07:08 AM
|
0
|
0
|
344
|
POST
|
The best answer is...it depends. The questions I would ask myself are: 1) Is my IT staff dependable and responsive to the GIS staff's needs? 2) How much control do I need over my configuration outside of ArcSDE? There are many objects to consider here but if licensing costs are a big hurdle to cross and your IT group plans on managing the server the bets bet would be to move forward using a 'SDE' schema geodatabase which would enable granular access to the GIS staff to access and manage the ArcSDE geodatabases while not stepping on the toes of the IT department. It would be a good idea to separate this data into two databases as you have outlined. The raster database will not be updated frequently and will also not be edited, therefore it may use a different recovery model (SIMPLE). Separation will make backup and restore operations on your vector database much easier to manage. The decision to configure your own separate SQL Server instance will be entirely dependent upon who you wish to manage the actual server as you will require sysadmin to perform certain database administration functions not related to ArcSDE and to manage user logins and other operations that do require admin permissions on the database instance every now and then. I understand this is not a comprehensive response but the real answer unfortunately is that it depends on many things (of which company culture is a large one) and no two sites are alike. - Jon
... View more
03-22-2012
06:29 AM
|
0
|
0
|
161
|
POST
|
There is currently no way to complete this process using COTS tools within ArcGIS to re-link a previous archive class. Although unsupported, there are blogs outlining where others have found methods to accomplish this. If I can find the link I will try and post. You may want to promote this suggestion on the Ideas site as well: Enable the ability to Re-Associate Archive Tables -Jon
... View more
03-22-2012
05:31 AM
|
0
|
0
|
444
|
POST
|
Jarrko, Are you able to make a direct-connection to the newly enabled geodatabase? After connecting through your Database Connection, right-click the connection and go to Geodatabase Connection Properties and verify you can see a DEFAULT version and then click OK. From the "create_enterprise_gdb.err.log" the instalaltion looks to have completed successfully. If so, the creation of the ArcSDE service on this Postgresql geoedatabase should be no different from that seen within previous releases. Verify that the service is assigned to a port as needed within the following locations: $SDEHOME/etc/services.sde /etc/services I would expect to see something akin to esri_sde 5151/tcp in each of these locations. Registering an ArcSDE service on UNIX or Linux http://resourcesbeta.arcgis.com/en/help/main/10.1/index.html#/Registering_an_ArcSDE_service_on_UNIX_or_Linux/002p0000004v000000/ Following this you should be able to start with nothing more than sdemon -o start -i esri_sde (or -i 5151). For some reason the error (-162 SE_INVALID_DATABASE) thinks that you are trying to start the service to hit a database named "sde". Should this continue to fail please upload the contents of your $SDEHOME/etc for review.
... View more
03-21-2012
12:01 PM
|
0
|
0
|
2539
|
POST
|
If you are able to capture any error logs (mentioned in my previous post) while this issue occurs please post this information for review or contact Esri Technical Support for further assistance.
... View more
03-20-2012
11:48 AM
|
0
|
0
|
1844
|
Title | Kudos | Posted |
---|---|---|
1 | a month ago | |
1 | 06-18-2024 12:48 PM | |
1 | 05-16-2024 06:15 AM | |
1 | 11-16-2023 12:21 PM | |
1 | 07-26-2023 11:46 AM |
Online Status |
Offline
|
Date Last Visited |
3 weeks ago
|