ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

JasperReports Server 6.4.3 installation failed - Oracle Advanced Security enabled

book

Article ID: 133091

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal

Issue/Introduction

I am trying to install Jasper Report Server 6.4.3 on Windows Server 2012, the Database is Oracle 12c, in tab where I need to provide database information, I use System user and I got error that user "does not have correct privileges".  

However, reviewing the actual install log the following error appears:

Exception found while verifyting the supported DB Versoionscom.ca.bicoe.cajasperserver.install.preinstall.utils.CABIException: java.sql.SQLException: [TibcoSoftwareInc][Oracle JDBC Driver]The connect attempt failed because the server requires Oracle Advanced Security. To enable the driver to use OAS, please use the "dataIntegrityLevel" and/or "encryptionLevel" connect options.


Environment

JasperReport Server 6.4.3

Resolution

They had two problems:

-Connect to Oracle Service on install

-Enable OAS for install


We had to change the following files with several properties:


buildomatic\conf_source\db\oracle\db.template.properties - appended OAS properties for connection URLs:


admin.jdbcUrl=jdbc:tibcosoftware:oracle://${dbHost}:${dbPort};${dbSidOrServiceNameProp}${AdditionalAdminProperties};DataIntegrityLevel=accepted;EncryptionLevel=accepted;EncryptionType=AES256

js.jdbcUrl=jdbc:tibcosoftware:oracle://${dbHost}:${dbPort};${dbSidOrServiceNameProp};DataIntegrityLevel=accepted;EncryptionLevel=accepted;EncryptionType=AES256

sugarcrm.jdbcUrl=jdbc:tibcosoftware:oracle://${dbHost}:${dbPort};CatalogOptions=0;${dbSidOrServiceNameProp};DataIntegrityLevel=accepted;EncryptionLevel=accepted;EncryptionType=AES256

foodmart.jdbcUrl=jdbc:tibcosoftware:oracle://${dbHost}:${dbPort};CatalogOptions=0;${dbSidOrServiceNameProp};DataIntegrityLevel=accepted;EncryptionLevel=accepted;EncryptionType=AES256


buildomatic\default_master.properties - added serviceName="Name" instead of SID:


serviceName=idm.service.name


These changes resolved the issue with OAS.