This is a very bizarre issue and I am at a loss as to why this is happening. A user running queries in SQL Developer brought this to our attention, and when we tried it we ran into the same problem:
There is a "LastModified" field in most of our feature classes, which is stored as a Date field in the database. When looking at the table in ArcCatalog or ArcMap, you can sort the values, query them, etc. and see that the values for this field go all the way up to 05/29/2015. However, when querying this field in SQL Developer, SQL Plus, or TOAD, the max date is 12/11/2014.
Example:
SELECT MAX(LASTMODIFIED) FROM SDE.WaterValve;Returns 11-DEC-2014
We've even tried changing the query to deliberately select a 2015 date value that we know is there, and it will say that the value is not found.
Any ideas how in the world this could be happening? Again, when you look at or query the data in ArcMap/ArcCatalog, you get the expected results with all the 2015 dates.
أكثر...
There is a "LastModified" field in most of our feature classes, which is stored as a Date field in the database. When looking at the table in ArcCatalog or ArcMap, you can sort the values, query them, etc. and see that the values for this field go all the way up to 05/29/2015. However, when querying this field in SQL Developer, SQL Plus, or TOAD, the max date is 12/11/2014.
Example:
SELECT MAX(LASTMODIFIED) FROM SDE.WaterValve;Returns 11-DEC-2014
We've even tried changing the query to deliberately select a 2015 date value that we know is there, and it will say that the value is not found.
Any ideas how in the world this could be happening? Again, when you look at or query the data in ArcMap/ArcCatalog, you get the expected results with all the 2015 dates.
أكثر...