This bug should really be fixed ASAP - not only from the user standpoint but also from the standpoint of supporting other GIS users in an organization. Thanks for those who share the tips and the workaround works - by selecting records first, it will export. Yet, this is NOT the proper way to export data. It is very hard to expect in support role we tell user to deal with this kinds of problem by asking user to do this kind of work around. The experience was as what the other stated here - when exporting the data (hosted in Oracle Enterprise), it always cites the error and the message is also somewhat misleading. When copying the data out to a local new geodatabase, it will export. Alternatively (as the others said) selecting all records first, it will export (data hosted in Oracle Enterprise), Yet, this is really not a proper workflows to export data. This is very basic function and is broken! ESRI, please fix this bug ASAP.
... View more
