Cadet 1st Class Cadet 1st Class
Cadet 1st Class
11547 views

Issues generating portfolio reports (audit summary).

Jump to solution

Hi,

Having issues generating portfolie reports (audit summary). It result in error with the following cause;

Caused by: java.sql.SQLException: ORA-00904: "OGINALFILENAME": invalid identifier

Complete errorcode below;

2016-03-14 15:20:51,109 [INFO] com.fortify.birtrunner.Main - savedReportId=63093580 Report generation started enhancedSecurity=true java_version=1.8.0_65

2016-03-14 15:20:55,750 [ERROR] com.fortify.birtrunner.Main - savedReportId=63093580 Report generation failed

com.fortify.birtrunner.exception.BirtReportGenerationException: Unable to generate the report

  at com.fortify.birtrunner.BirtRunner.renderReport(BirtRunner.java:84) ~[birtrunner-4.42.jar:?]

  at com.fortify.birtrunner.Main.main(Main.java:87) [birtrunner-4.42.jar:?]

Caused by: com.fortify.birtrunner.exception.ResourceLocatorException: An error while locating BIRT database resources has occurred

  at com.fortify.birtrunner.DatabaseResourceLocator.findResource(DatabaseResourceLocator.java:53) ~[birtrunner-4.42.jar:?]

  at org.eclipse.birt.report.model.core.ModuleImpl.findResource(ModuleImpl.java:1304) ~[org.eclipse.birt.runtime_4.4.2.v20150217-1805.jar:?]

  at org.eclipse.birt.report.model.parser.IncludedLibrariesStructureListState$IncludedLibraryStructureState.end(IncludedLibrariesStructureListState.java:112) ~[org.eclipse.birt.runtime_4.4.2.v20150217-1805.jar:?]

  at org.eclipse.birt.report.model.util.XMLParserHandler.endElement(XMLParserHandler.java:186) ~[org.eclipse.birt.runtime_4.4.2.v20150217-1805.jar:?]

  at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) ~[org.apache.xerces_2.9.0.v201101211617.jar:?]

  at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source) ~[org.apache.xerces_2.9.0.v201101211617.jar:?]

  at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) ~[org.apache.xerces_2.9.0.v201101211617.jar:?]

  at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) ~[org.apache.xerces_2.9.0.v201101211617.jar:?]

  at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) ~[org.apache.xerces_2.9.0.v201101211617.jar:?]

  at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) ~[org.apache.xerces_2.9.0.v201101211617.jar:?]

  at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) ~[org.apache.xerces_2.9.0.v201101211617.jar:?]

  at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) ~[org.apache.xerces_2.9.0.v201101211617.jar:?]

  at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) ~[org.apache.xerces_2.9.0.v201101211617.jar:?]

  at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source) ~[org.apache.xerces_2.9.0.v201101211617.jar:?]

  at org.eclipse.birt.report.model.parser.ModuleReader.readModule(ModuleReader.java:98) ~[org.eclipse.birt.runtime_4.4.2.v20150217-1805.jar:?]

  at org.eclipse.birt.report.model.parser.DesignReader.read(DesignReader.java:88) ~[org.eclipse.birt.runtime_4.4.2.v20150217-1805.jar:?]

  at org.eclipse.birt.report.model.core.DesignSessionImpl.openDesign(DesignSessionImpl.java:309) ~[org.eclipse.birt.runtime_4.4.2.v20150217-1805.jar:?]

  at org.eclipse.birt.report.model.api.SessionHandleImpl.openDesign(SessionHandleImpl.java:294) ~[org.eclipse.birt.runtime_4.4.2.v20150217-1805.jar:?]

  at org.eclipse.birt.report.model.api.SessionHandle.openDesign(SessionHandle.java:1) ~[org.eclipse.birt.runtime_4.4.2.v20150217-1805.jar:?]

  at org.eclipse.birt.report.engine.parser.ReportParser.getDesignHandle(ReportParser.java:158) ~[org.eclipse.birt.runtime_4.4.2.v20150217-1805.jar:?]

  at org.eclipse.birt.report.engine.api.impl.ReportEngineHelper.getReportDesignHandle(ReportEngineHelper.java:255) ~[org.eclipse.birt.runtime_4.4.2.v20150217-1805.jar:?]

  at org.eclipse.birt.report.engine.api.impl.ReportEngineHelper.openReportDesign(ReportEngineHelper.java:274) ~[org.eclipse.birt.runtime_4.4.2.v20150217-1805.jar:?]

  at org.eclipse.birt.report.engine.api.impl.ReportEngineHelper.openReportDesign(ReportEngineHelper.java:196) ~[org.eclipse.birt.runtime_4.4.2.v20150217-1805.jar:?]

  at org.eclipse.birt.report.engine.api.impl.ReportEngineHelper.openReportDesign(ReportEngineHelper.java:130) ~[org.eclipse.birt.runtime_4.4.2.v20150217-1805.jar:?]

  at org.eclipse.birt.report.engine.api.impl.ReportEngine.openReportDesign(ReportEngine.java:313) ~[org.eclipse.birt.runtime_4.4.2.v20150217-1805.jar:?]

  at com.fortify.birtrunner.BirtRunner.loadReport(BirtRunner.java:165) ~[birtrunner-4.42.jar:?]

  at com.fortify.birtrunner.BirtRunner.renderReport(BirtRunner.java:68) ~[birtrunner-4.42.jar:?]

  ... 1 more

Caused by: java.sql.SQLException: ORA-00904: "OGINALFILENAME": invalid identifier

Query: select data from reportexecblob where savedReport_id = ? and originalFilename = ? Parameters: [63093580, FortifyBasicElements.rptlibrary]

Labels (2)
0 Likes
1 Solution

Accepted Solutions
Vice Admiral
Vice Admiral

This is caused by a known issue in some versions of the Oracle JDBC driver.


You should update to this version: Oracle Database 12c Release 1 JDBC Driver Downloads

To replace the existing driver in use, shut down your application server and replace the existing ojdbc6/7.jar in <SSC exploded war folder>/WEB-INF/lib with the one you downloaded from above, then restart the app server.

Note, that just replacing this copy in the exploded war directory will mean that if the webapp is ever re-deployed from the .war, the old copy will be deployed. If that is likely to happen, you should use a zip tool to replace the copy of ojdbc6/7.jar within the .war file also.

-Josh

Fortify L3 Support Engineer

View solution in original post

0 Likes
5 Replies
Vice Admiral
Vice Admiral

This is caused by a known issue in some versions of the Oracle JDBC driver.


You should update to this version: Oracle Database 12c Release 1 JDBC Driver Downloads

To replace the existing driver in use, shut down your application server and replace the existing ojdbc6/7.jar in <SSC exploded war folder>/WEB-INF/lib with the one you downloaded from above, then restart the app server.

Note, that just replacing this copy in the exploded war directory will mean that if the webapp is ever re-deployed from the .war, the old copy will be deployed. If that is likely to happen, you should use a zip tool to replace the copy of ojdbc6/7.jar within the .war file also.

-Josh

Fortify L3 Support Engineer

View solution in original post

0 Likes
Cadet 3rd Class
Cadet 3rd Class

Hi,

  I am facing the same issue in Fortify 17.20 version, I tried to get the latest ojdbc jar file into the WEB-INF/lib folder, but there is no ojdbc6/7 jar file to replace. Please let me know how to resolve this issue.

0 Likes
Vice Admiral
Vice Admiral

With 17.20 and future versions, the JDBC driver is no longer stored inside the ssc.war or the extracted version to ssc/WEB-INF/lib, instead it should be placed in the 'lib' folder for your app server. 
For Tomcat (the most commonly used of our supported app servers), this is in <tomcat install folder>/lib (same place as the 'webapps' folder)

-Josh
Fortify L3 support engineer

0 Likes
Cadet 1st Class Cadet 1st Class
Cadet 1st Class

Hi Josh,

Thank you. That solved this issue.

Having some functional issues aswell;

Clicking on for example the ‘AUDIT’ button or on CPV CPV – Schade results in the same screen.

Thanks,

Detlef Kroeze

ASR Netherlands

Van: josh.anderson

Verzonden: dinsdag 15 maart 2016 12:03

Aan: Kroeze D.W. (Detlef)

Onderwerp: Re: - Issues generating portfolio reports (audit summary).

Protect724 <https://www.protect724.hpe.com/?et=watches.email.thread>

Issues generating portfolio reports (audit summary).

reply from Josh Anderson<https://www.protect724.hpe.com/people/josh.anderson?et=watches.email.thread> in Fortify - View the full discussion<https://www.protect724.hpe.com/message/78182?et=watches.email.thread#comment-78182>

0 Likes
Vice Admiral
Vice Admiral

Glad to hear it worked.


Regarding that issue, I've not seen it before, nor can I reproduce it on my version; I recommend opening a ticket with support (https://support.fortify.com or fortifytechsupport@hpe.com) so someone can work more closely on that with you. Please include the screenshot and relevant version numbers -- at least, which browser and version of SSC

-Josh

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.