'java.io.FileNotFoundException: aveksa-version.properties' error running createSchema.sh in RSA Identity Governance & Lifecycle
Originally Published: 2019-11-18
Article Number
Applies To
RSA Version/Condition: 7.1.0 P08, 7.1.0 P09, 7.1.1 P02, 7.1.1 P03
Issue
- java.io.FileNotFoundException: /home/oracle/database/reportdefs/UserEntitlements.jrxml (No such file or directory)
- java.io.FileNotFoundException: aveksa-version.properties
After starting RSA Identity Governance & Lifecycle, users are unable to login to the user interface:
Unable to check Database.java.lang.NullPointerException
The errors are also seen in the /home/oracle/database/log/create.log file:
SQL/line#: /home/oracle/database/migration/populateReports.sql(1):
Start time [Fri Nov 15 13:30:08 EST 2019]
java com.aveksa.migration.jdbctool.JavaStepPopulateReports
java.io.FileNotFoundException: /home/oracle/database/reportdefs/UserEntitlements.jrxml
(No such file or directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.<init>(FileInputStream.java:138)
at com.aveksa.common.utils.IOUtils.getFileAsString(IOUtils.java:101)
at com.aveksa.migration.jdbctool.PopulateAvReports.readJRXML(PopulateAvReports.java:2757)
at com.aveksa.migration.jdbctool.PopulateAvReports.createReportFromXMLFile(PopulateAvReports.java:2672)
at com.aveksa.migration.jdbctool.PopulateAvReports.createReportFromXMLFile(PopulateAvReports.java:2654)
at com.aveksa.migration.jdbctool.PopulateAvReports.createReportFromXMLFile(PopulateAvReports.java:2639)
at com.aveksa.migration.jdbctool.PopulateAvReports.initializeReportTemplates(PopulateAvReports.java:88)
at com.aveksa.migration.jdbctool.PopulateAvReports.execute(PopulateAvReports.java:69)
at com.aveksa.migration.jdbctool.JavaStepPopulateReports.run(JavaStepPopulateReports.java:17)
at com.aveksa.migration.jdbctool.SQLFileExecutor.execute(SQLFileExecutor.java:211)
at com.aveksa.migration.jdbctool.SQLFileExecutor.execute(SQLFileExecutor.java:107)
at com.aveksa.migration.jdbctool.SQLFileExecutor.execute(SQLFileExecutor.java:98)
at com.aveksa.migration.jdbctool.IncrementalUpdate.update(IncrementalUpdate.java:481)
at com.aveksa.migration.jdbctool.CreateSchema.execute(CreateSchema.java:103)
at com.aveksa.cli.CreateMigrateSchemaModule.runCommandImpl(CreateMigrateSchemaModule.java:277)
at com.aveksa.cli.BaseDatabaseCLIModule.runCommand(BaseDatabaseCLIModule.java:97)
at com.aveksa.cli.Main.run(Main.java:351)
at com.aveksa.cli.Main.main(Main.java:405)
End time [Fri Nov 15 13:30:08 EST 2019]
Execution time (s): 0
SQL/line#: /home/oracle/database/migration/setVersion.sql(1):
Start time [Fri Nov 15 13:30:51 EST 2019]
java com.aveksa.migration.jdbctool.JavaStepSetVersion
java.io.FileNotFoundException: aveksa-version.properties
at com.aveksa.migration.jdbctool.JavaStepSetVersion.run(JavaStepSetVersion.java:35)
at com.aveksa.migration.jdbctool.SQLFileExecutor.execute(SQLFileExecutor.java:211)
at com.aveksa.migration.jdbctool.SQLFileExecutor.execute(SQLFileExecutor.java:107)
at com.aveksa.migration.jdbctool.SQLFileExecutor.execute(SQLFileExecutor.java:98)
at com.aveksa.migration.jdbctool.IncrementalUpdate.update(IncrementalUpdate.java:481)
at com.aveksa.migration.jdbctool.CreateSchema.execute(CreateSchema.java:103)
at com.aveksa.cli.CreateMigrateSchemaModule.runCommandImpl(CreateMigrateSchemaModule.java:277)
at com.aveksa.cli.BaseDatabaseCLIModule.runCommand(BaseDatabaseCLIModule.java:97)
at com.aveksa.cli.Main.run(Main.java:351)
at com.aveksa.cli.Main.main(Main.java:405)
End time [Fri Nov 15 13:30:51 EST 2019]
Execution time (s): 0
[0:00:00] File Completion Time: /home/oracle/database/migration/setVersion.sql
[0:09:32] Total Migration Time
Please note this is also a problem with the migrate.sh script file. Please see RSA Knowledge Base Article 000038148 -- 'java.io.FileNotFoundException: aveksa-version.properties' error running migrate.sh in RSA Identity Governance & Lifecycle for more information.
Cause
Resolution
- RSA Identity Governance & Lifecycle 7.1.1 P05
- RSA Identity Governance & Lifecycle 7.2
Workaround
STEPS
- Download the attached aveksa-version.zip file.
- Note the files are named in the format aveksa-version_<versionpatch>.properties.
- Extract the appropriate file for your RSA Identity Governance & Lifecycle version and patch level.
- Copy the file to the /home/oracle/database directory using WinSCP or a similar tool.
- Login to the server as the oracle user.
- Rename aveksa-version_<versionpatch>.properties to aveksa-version.properties.
cd /home/oracle/database mv aveksa-version_<versionpatch>.properties aveksa-version.properties
- Run createSchema.sh again.
./createSchema.sh
- Restart RSA Identity Governance & Lifecycle
acm restart
Notes
java.io.FileNotFoundException: /home/oracle/database/reportdefs/UserEntitlements.jrxml (No such file or directory)
Attachments
If the attachment does not open when clicked, please refresh the page and try again. You must be logged into view the file(s).
Related Articles
'java.io.FileNotFoundException: aveksa-version.properties' error running migrate.sh in RSA Identity Governance & Lifecycle 165Number of Views Running upgradeJDK.sh issues "ACM is not supported on this version of linux" in RSA VIA Lifecycle & Governance 59Number of Views Schema migration fails with ORA-01017 or ORA-28000 in RSA Governance & Lifecycle 74Number of Views Upgrade from 7.2.1 or earlier version to SecurID Governance & Lifecycle 7.5.0 or later version stalls at step ACM-102799.sql 860Number of Views Upgrade to RSA Identity Governance & Lifecycle 7.0.2 fails with message "Error occurred when determining the version of th… 200Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?