After restarting RSA Identity Governance & Lifecycle, the user interface indicates Schema Migration is required even though you have just run the migration script.
Image description
The errors are also seen in the /home/oracle/database/log/migrate.log (or /home/oracle/wildfly/standalone/log/migrate.log) file:
SQL/line#: /home/oracle/database/migration/populateReports.sql(1):
Start time [Mon Nov 18 10:39:24 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.MigrateSchema.execute(MigrateSchema.java:163)
at com.aveksa.migration.jdbctool.MigrateSchema.execute(MigrateSchema.java:83)
at com.aveksa.cli.CreateMigrateSchemaModule.runCommandImpl(CreateMigrateSchemaModule.java:211)
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 [Mon Nov 18 10:39:24 EST 2019]
Execution time (s): 0
SQL/line#: /home/oracle/database/migration/setVersion.sql(1):
Start time [Mon Nov 18 10:40:17 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.MigrateSchema.execute(MigrateSchema.java:163)
at com.aveksa.migration.jdbctool.MigrateSchema.execute(MigrateSchema.java:83)
at com.aveksa.cli.CreateMigrateSchemaModule.runCommandImpl(CreateMigrateSchemaModule.java:211)
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 [Mon Nov 18 10:40:17 EST 2019]
Execution time (s): 0
[0:00:00] File Completion Time: /home/oracle/database/migration/setVersion.sql
[0:04:08] Total Migration Time
Please note this is also a problem with the createSchema.sh script file. Please see RSA Knowledge Base Article 000038146 -- 'java.io.FileNotFoundException: aveksa-version.properties' error running createSchema.sh in RSA Identity Governance & Lifecycle for more information.
acm restart
cd /home/oracle/database mv aveksa-version_<versionpatch>.properties aveksa-version.properties
./migrate.sh
acm restart