Oracle Business Intelligence Applications

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

oracle.xdo.servlet.data.DataException: oracle.xdo.servlet.data.DataException: oracle.xdo.servlet.dat

Received Response
1235
Views
3
Comments

Hello everybody,

somebody asked me to develop BI Publisher report using a database template.  I was able to reproduce the XLS template I used for this report.  When I'm seeing the report on-line it seems we have no problems, until I change the type of output.  It gives me the exception in my title.  I'm using BI Publisher 12c.

oracle.xdo.servlet.data.DataException: oracle.xdo.servlet.data.DataException: oracle.xdo.servlet.data.DataException: oracle.xdo.template.online.dms.common.XDODmsException: IO Exception was thrown! null

There is no problem in the Data source because it works perfectly with the XLS template.  The only thing I see is that the report is using 32 empty ligne that should appear in a static table.  There is no need for a report table.  Do you have any diea on how fix this. ?  For an obscure reason, the HTML version working and show what I need.

Thank you !

Answers

  • Christian Berg-0racle
    Christian Berg-0racle Rank 10 - Analytics Guru

    The BIP forum is that way --->

  • persona4-77
    persona4-77 Rank 3 - Community Apprentice

    Ok, thank you !

  • persona4-77
    persona4-77 Rank 3 - Community Apprentice

    Ok, it seems I found a solution, but I do not understand why it's doing this.

    I my Data Set I had a field that was a VARCHAR2 pour is in fact a numeric value.  When I wrote the query, it was, BI Publisher selected a double type for it.  But, in my examples, this field might be null and each of the example I used were null.  When it was time to render the report, it throwed an exception, but I didn't know that the numeric data type had this impact on the rendering of the report.

    To correct the problem, I simply put a to_char around my numeric column.  I thinks it's weird because it didn't remember doing things like that in the previous versions of BI Publisher to make it work.