Oracle Analytics Publisher

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Publisher

Categories

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

Oracle Analytics Publisher Upgrade to 7.6 (2024) facing Socket read timed out issue.

Accepted answer
104
Views
2
Comments
Tiang
Tiang Rank 4 - Community Specialist
in Oracle Analytics Publisher

We recently upgraded several servers running Oracle Analytics Server from version 5.5 to version 7.6 and applied the latest patch. However, after the upgrade, we began experiencing some unusual issues.

Prior to the upgrade, certain reports—even those that took up to 3 hours to complete—were executing successfully. After the upgrade, those same long-running reports are now failing after approximately 1 hour, returning the following error:

oracle.xdo.servlet.data.DataException: oracle.xdo.XDOException: java.sql.SQLRecoverableException: IO Error: Socket read timed out

In addition, we observed inconsistent behavior with some reports triggered during off-peak hours. For example, a report scheduled at 2:30 AM fails, but if run again at 2:31 AM, it completes successfully.

Is there any official documentation or best practices that outline necessary changes or tuning steps after upgrading to version 7.6? Should we consider modifying queries or adjusting configuration parameters to resolve these issues?

I had attached the report data model validate log with null value also with value to test. Also attached the diagnostic log that report keep failed after upgrade but in Production success.

frmp039d_Job_3003.log
DMValidation-UAT-WithValue.log
DMValidation-Prod-WithValue.log

Production (Version 5.5) - Success
UAT (Version 7.6) - Failed

Thanks.

Tagged:

Best Answer

  • Tiang
    Tiang Rank 4 - Community Specialist
    edited May 2, 2025 2:13AM Answer ✓

    Hi,

    The issue had been fixed.

    image.png

    The DataSource i created in XMLPSERVER that have no any properties for me to do tuning or add parameter.

    So i Create DataSource in WebLogic with oracle.jdbc.ReadTimeout parameter and set 4hour.

    Created JNDI connection from XMLPSERVEFR and link to WebLogic DataSource.

    Report DataModel choose this new JNDI DataSource, so the report able trigger more than an hour and within 4hour timeout it able to finish.

    Regards,

    Tiang

Answers

  • Mallikarjuna Kuppauru-Oracle
    Mallikarjuna Kuppauru-Oracle Rank 8 - Analytics Strategist

    Hi @Tiang

    Do you have an timeout setting at Data model level? I hope its an schedule job and its failing after 1 hour(default timeout).

    You can able to override the option from Data model level and then schedule the same to fix the issue.

    Regards,

    Arjun