Thanks for respnding Asrujit SenGupta.
I'm not sure that answers my question. Is the expected behavior for query layers not to work on ST_Geometry? That sounds counter intuitive to the quote in your repsonse. It seems to be telling me that I have the proper geometry (ST_Geometry) so it should work. Also, I have all the permission needed to do this type of query.
Maybe to add a bit of information to add to the mystery. We have 2 Oracle databases.
Database 1 is used to manage parcels of land for mining activities, so it is comprised of a number of stand alone tables, features classes and spatial views.
Database 2 is a larger corporate database and contains, amoung other things, copies of the feature classes and spatial views (but not the stand alone tables) that come from from the mining activities database.
Database specs:
DB1: SDE 10.2.2. Oracle v11 using ST Geometry Type
DB2: SDE 10.2.2. Oracle v12 using SDO Geometry Type.
So, in saying that, I tested the copy of one of the feature classes from both Database 1 and Database 2. Database 1 is the database where I have the issue. If I build a query layer using the feature class from Database 2 (the corporate database), it is successful. See images below.
Database 1. Notice the 'UNKNOWN' spatial reference:
Database 2. Notice that it populates spatial information in picture 2.