POST
|
We also ran into this error, but with the schema owner. It is very strange that a schema owner cannot preview of show the properties of a table. We noticed that some tables worked whereas other tables gave the error. There seemed no difference in registration, so we looked at the Oracle code behind the table and noticed that the one table had one extra role permission. We gave the schema owner the role permission and suddenly the table was accessible. So now you guess it will be straightforward to figure out which permission was missing...if it was always that simple we would get bored, so we had to dig deeper. After revoking ALL permissions from the schema owner and giving the schema owner just enough to make a connection, we could also 'see' all the tables, so a role GRANTED to the schema owner caused the issue. Our roles and permissions structure is fairly complex, so it took a hundred times of granting and revoking permissions and disconnecting/connecting to the geodatabase to find out that the issue was: granting a role with editing permissions which is granted to another role directly to a user caused the issue. So: CREATE ROLE LEVEL_ONE; CREATE ROLE LEVEL_TWO; GRANT LEVEL_TWO TO LEVEL_ONE; GRANT DELETE, INSERT, SELECT, UPDATE ON GEODATA.LOOKUP_VALUES TO LEVEL_TWO; GRANT LEVEL_TWO TO GEODATA; -- this last grant causes the GEODATA user to not be able to access the LOOKUP_VALUES table in his own schema. REVOKE LEVEL_TWO FROM GEODATA; -- just to make sure: revoking this role makes the dataset accessible again.
... View more
04-13-2017
07:01 AM
|
2
|
0
|
1809
|
POST
|
Same here. Also while working through the Getting started tutorial. removing Hillshade solved the issue
... View more
01-06-2017
05:01 AM
|
1
|
0
|
957
|
POST
|
I've succesfully migrated ST_GEOMETRY databases with datapump. This is how: 1. Use 11.2.0.4 or apply the patch as mentioned before 2. Grant permissions GRANT EXECUTE ON sys.dbms_pipe TO public; GRANT EXECUTE ON sys.dbms_lock TO public; GRANT EXECUTE ON sys.dbms_lob TO public; GRANT EXECUTE ON sys.dbms_utility TO public; GRANT EXECUTE ON sys.dbms_sql TO public; GRANT EXECUTE ON sys.utl_raw TO public; GRANT EXECUTE ON sys.DBMS_CRYPTO TO public; -- DBMS_CRYPTO appears to be needed to create the ST_GEOMETRY data type and as the user SDE doesn't exist yet we grant it to public to avoid permission errors 3. Import SDE schema without indexes/constraints etc (this is the content of the .par file): userid = "/@TARGETDATABASE as sysdba" directory = DMPDIR dumpfile = ORADUMP.DMP logfile = oraimpdp_stap1.log EXCLUDE = CONSTRAINT,REF_CONSTRAINT,INDEX,TABLE_STATISTICS,TRIGGER,REFRESH_GROUP SCHEMAS = SDE 4. Verify import by fixing invalid objects Exec dbms_utility.compile_schema( 'SDE', compile_all => FALSE ); SELECT * FROM DBA_OBJECTS WHERE STATUS <> 'VALID' ORDER BY OWNER, OBJECT_NAME; 5. Import USER schemas without indexes/constraints etc (this is the content of the .par file): userid = "/@TARGETDATABASE as sysdba" directory = dmpdir dumpfile = ORADUMP.DMP logfile = oraimpdp_stap2.log EXCLUDE = CONSTRAINT,REF_CONSTRAINT,INDEX,TABLE_STATISTICS,TRIGGER,REFRESH_GROUP SCHEMAS = GEO,REF,TOPO 6. Verify import by fixing invalid objects Exec dbms_utility.compile_schema( 'GEO', compile_all => FALSE ); SELECT * FROM DBA_OBJECTS WHERE STATUS <> 'VALID' ORDER BY OWNER, OBJECT_NAME; 7. Import SDE & USER schema indexes/constraints etc (this is the content of the .par file): userid = "/@TARGETDATABASE as sysdba" directory = dmpdir dumpfile = ORADUMP.DMP logfile = oraimpdp_stap3.log SKIP_UNUSABLE_INDEXES = Y INCLUDE = CONSTRAINT,REF_CONSTRAINT,INDEX,TABLE_STATISTICS,TRIGGER,REFRESH_GROUP SCHEMAS = SDE,GEO,REF,TOPO 8. Update statistics EXECUTE DBMS_STATS.GATHER_SCHEMA_STATS(ownname => 'SDE', estimate_percent => DBMS_STATS.AUTO_SAMPLE_SIZE); EXECUTE DBMS_STATS.GATHER_SCHEMA_STATS(ownname => 'GEO', estimate_percent => DBMS_STATS.AUTO_SAMPLE_SIZE); EXECUTE DBMS_STATS.GATHER_SCHEMA_STATS(ownname => 'REF', estimate_percent => DBMS_STATS.AUTO_SAMPLE_SIZE); EXECUTE DBMS_STATS.GATHER_SCHEMA_STATS(ownname => 'TOPO', estimate_percent => DBMS_STATS.AUTO_SAMPLE_SIZE); You might need to remove the REFRESH_GROUP option if these objects don't exists in the dmp file. (You can just try and if you get an error just remove it)
... View more
12-02-2015
02:11 AM
|
1
|
0
|
370
|
POST
|
Hi Chet, I've posted a comment regarding 'Create SDE spatial view from ArcGIS Desktop' on the Ideas website a year ago: https://c.na9.visual.force.com/apex/ideaView?id=08730000000884aAAA This idea has been marked as implemented, but as per my comment, the functionality of a query layer differs from an SDE (or as ArcSDE is gone, a geodatabase) view. I have never understood why a tool like 'sdetable -o create_view" does not have an ArcToolbox counterpart as nearly all my clients use geo views for performance reasons. For over 10 years I have explained my clients how to use the create_view command as a hacky workaround and now it seems I have to explain them the even hackier workaround David Gifford suggested. Last year I spoke to Sannon Shields at the Esri UC who told me that there are quite a lot of customers who worry about losing the create_view command.
... View more
02-05-2015
03:01 PM
|
0
|
4
|
697
|
POST
|
There are currently two ideas about creating spatial views on ideas.arcgis.com: Create SDE spatial view from ArcGIS Desktop http://ideas.arcgis.com/ideaView?id=08730000000884aAAA Create Views In ArcCatalog Like In SDE Command Line http://ideas.arcgis.com/ideaView?id=087E00000005A9tIAE The first one is marked as implemented by the Create Database View tool, which I object against, because (as other contributors above have mentioned) the result is not nearly the same as the sdetable -o create_view. The second one is the request for a replacement for sdetable -o create_view. Please promote the idea if this is something you also run into. A lot of improvements on the geodatabase side have been made in the lastest ArcGIS releases like renaming and modifying columns and making the sde command line tools available via tools. The possibility of creating proper spatial views however, still needs attention before deprecating the current tools.
... View more
03-04-2014
10:00 AM
|
2
|
1
|
782
|
Title | Kudos | Posted |
---|---|---|
1 | 01-06-2017 05:01 AM | |
2 | 04-13-2017 07:01 AM | |
1 | 12-02-2015 02:11 AM | |
2 | 03-04-2014 10:00 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|