If you're upgrading to JasperReports Server version 6.4 or later using the js-upgrade-samedb.sh/bat script, you may encounter an error if Oracle's Procedural Language (PL/SQL) is not enabled.
The upgrade script for upgrading to a 4.7 database from a 4.5 database requires enabling the PL/SQL language. The script is located here:
The error you encounter might look something like this:
[advanced-sql] PLS-00103: Encountered the symbol “end-of-file”
To enable your PL/SQL language, consult the documentation for your Oracle database to enable PL/SQL.
If you're upgrading from 4.7 to 6.4, and you use the js-upgrade-samedb.bat/sh script, you may get an error related to an inadequate PAGESIZE setting. The recommended minimal PAGESIZE setting for both 4.7 and 5.0 is 16384.
If the PAGESIZE setting is less than this you may get an error like this:
DB2 SQL Error: SQLCODE=-670,SQLSTATE=54010, SQLERRMC=4005;
DB2 SQL Error: SQLCODE=-286, SQLSTATE=42727, SQLERRMC=8192;DB2ADMIN,
If you get this error, recreate your 4.5 database using a command like the following:
CREATE DATABASE JSPRSRVR USING CODESET UTF-8 TERRITORY US PAGESIZE 16384
This may require reloading your database from your database backup and rerunning the upgrade procedure after PAGESIZE has been changed.
If you have auditing enabled and you run upgrade using js-upgrade-newdb.bat/sh, audit events are not imported by default. To import audit events, you need to run an additional command after the js-upgrade-newdb script completes. To do this, change to the buildomatic directory:
Then run one of the following commands:
js-import.bat --input-zip=js-my-export-all.zip --include-audit-events (Windows)
js-import.sh --input-zip=js-my-export-all.zip --include-audit-events (Linux)
ant import -DimportFile=js-my-export-all.zip -DimportArgs="--include-audit-events"
These commands reimport all resources from the specified export file, add the audit event, and do not overwrite existing resources.
When using either import utility, the server must be stopped to avoid issues with caches, configuration, and security.
If you're using the overlay upgrade procedure with a PostgreSQL database, and you installed an earlier version of JasperReports Server, you might see an HTTP Status 404 error.
The overlay installer is not supported with the bundled installation and may only be used with a war file installation of JRS.
When working with Domains using the MySQL database — and using the 1.1.2 version of the MariaDB JDBC driver (mariadb-java-client-1.1.2.jar) — there can be an issue handling Boolean values correctly. The fix is to upgrade to a higher version of the MariaDB JDBC driver such as 1.1.6.
Because JasperReports Server 5.5, 5.6, 6.0, 6.1 and the Overlay packages are distributed with the MariaDB 1.1.2 JDBC driver, this error can also occur even without an upgrade operation.
The issue may occur when a boolean filter is created on a domain. Because of a bug in older versions of the MariaDB driver, the boolean filter is evaluated as a numeric filter.