ORA-22285 error running Data Archiving of RSA Identity Governance & Lifecycle
2 years ago
Originally Published: 2019-12-20
Article Number
000043050
Applies To
RSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.1.x
Issue
 The "ORA-22285: non-existent directory or file for FILEEXISTS operation" error is thrown running Data Archiving of RSA Identity Governance & Lifecycle.
11/14/2019 12:31:56.230 WARN (default task-47) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] SQL Error: 22285, SQLState: 99999
11/14/2019 12:31:56.232 ERROR (default task-47) [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] ORA-22285: non-existent directory or file for FILEEXISTS operation
ORA-06512: at "SYS.DBMS_LOB", line 786
ORA-06512: at "AVUSER.ARCHIVEPURGE_PKG", line 1451
ORA-06512: at line 1
...
Caused by: Error : 22285, Position : 0, Sql = BEGIN :1 := ArchivePurge_Pkg.DBServer_FileExists(:2 ); END;, OriginalSql = {? = call ArchivePurge_Pkg.DBServer_FileExists(?)}, Error Msg = ORA-22285: non-existent directory or file for FILEEXISTS operation
ORA-06512: at "SYS.DBMS_LOB", line 786
ORA-06512: at "AVUSER.ARCHIVEPURGE_PKG", line 1451
ORA-06512: at line 1

at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:498)
... 92 more
Cause
The required Export/Import directory is not configured properly as documented in the RSA Identity Governance & Lifecycle Database Setup and Management Guide V7.1 as it is missing the READ-WRITE permissions.
Resolution
You run your first query to confirm you have the issue, not to fix the issue. Then follow the guide to fix the issue. Then run the next query to confirm the issue is fixed. Something like:
--To confirm you have this issue...run this query
-- Follow the instructions in the guide or.... I believe it is ok here to replicate the steps needed to fix this issue even though they are documented in the guide but it is important to emphasize that they are documented You did mention the guide which is great but I'd like to see more emphasis on the fact that if you run into this issue, for once it is not the product's fault. (It has enough problems.)
-- To confirm this issue is fixed.... run this query.