I just ran into this error while importing an application export file into our production environment, but this did not happen in our staging environment...
Did anyone get back to you on this or did you find a workaround?
HI Joe, could you be more specific about the version of Apex you exported from , which database then and which database your running now with the Apex 4.2.5 ?
Thanks for reporting this issue. We have reproduced this internally. I filed Bug 18719750 - ORA-01858 DURING APPLICATION IMPORT. We're working on a patch set exception (bug fix) now. Stay tuned, and I apologize for the disruption.
I was able to get around the issue by first deleting the application in the target APEX environment and then importing it (rather than doing a replace). Give that a try (export the one you are going to delete first!) and let us know if that works for you too.
In the case above, both the source and the target were upgraded to 4.2.5.00.8 and then the export/import (replace) was attempted to yield the referenced error.
One downside to the suggested workaround is that you will lose any saved private interactive reports.
The patch set exception for bug 18719750 in APEX 4.2.5 is now available on My Oracle Support. Please let me know if you run into any issues.
Excellent. The support/dev guys for APEX are really spoiling us! Thanks for the super quick turn around.