Errors on reloading any [database] dataset in OAS 2024 ( 7.6)

Dirk - JEM

Hello,
I've installed OAS 2024 on 3 Windows Servers (2022) with OraDB19c as Repository-DB and on all 3 systems the reload of the simplest dataset is raising an error - the funny part is - it looks like the data are really "refreshed" and reloaded, but the status is failed and the log show internal errors.

Since the error occurs on 3 from scratch installed systems - maybe someone else has been facing the same problems?

Thanks,
Dirk

Dirk - JEM

Just for the sake of completeness - we solved this problem, it was just kind of a bug - we found out the Virtual-C version needed to be an older one than 2015-2022, that was installed on the systems … wow, this took a lot of trial and error. 😉
But … we could solve it.

Thanks for your participation,
Dirk

BalagurunathanBagavathy-Oracle

@fledicu Can you please post the error message / screenshot showing the error? Does the issue occur for a dataset based on CSV / Excel as well?

Dirk - JEM

Thanks for the fast response - I should add I've already created a SR but without any result yet, so I hoped to maybe found help in the community 😊
It does not occur on Excel

This is the log of the "Job History" - ( I chose the W_ETL_LOG table as dataset table so I could see the "new errors" after reloading 😉 )

thanks in advance …

• 2024-10-25 09:23:36 'bi_admin'.'DS Test 19c'

71 INFO 2024-10-25 09:23:36.643 CET Starting to process request, run id: DA1281551A62B64D15BD6D44EFF9AE0 after being in queue for 15 second(s), 636 millisecond(s).
221 INFO 2024-10-25 09:23:38.429 CET Will run up to 2 task(s) in parallel
225 INFO 2024-10-25 09:23:38.454 CET Creating necessary connections.
230 INFO 2024-10-25 09:23:38.46 CET Initializing connection to source: 'bi_admin'.'repos_system'.
239 INFO 2024-10-25 09:23:38.513 CET Sources created.
240 INFO 2024-10-25 09:23:38.516 CET 23,574 (MB) of 2,50 (TB) used (8.992782022687607E-4 %).
250 INFO 2024-10-25 09:23:38.548 CET Loading tasks for a new run.
253 FINER 2024-10-25 09:23:38.637 CET Loading of tasks completed
258 INFO 2024-10-25 09:23:38.696 CET A total of 1 task(s) need to be executed for this run.
261 INFO 2024-10-25 09:23:38.709 CET Executing tasks.
300 SEVERE 2024-10-25 09:23:40.038 CET An error occurred, which could not be interpreted.
306 SEVERE 2024-10-25 09:23:40.138 CET An error occurred, which could not be interpreted.
310 SEVERE 2024-10-25 09:23:40.142 CET An error occurred, which could not be interpreted.
311 SEVERE 2024-10-25 09:23:40.144 CET Task "DSET : DS Test 19c - W_ETL_LOG" failed. Check the tasks log for more information
336 INFO 2024-10-25 09:23:40.709 CET Finished.
339 INFO 2024-10-25 09:23:40.758 CET Transaction callback accepted for all tasks
342 INFO 2024-10-25 09:23:40.782 CET

• Summary

344 INFO 2024-10-25 09:23:40.784 CET Job Run Summary
Total Number Of Tasks: 1
Total Number Of Successful Rows across all tasks: 0
Total Data Size across all tasks: ,00 (BYTE)

346 INFO 2024-10-25 09:23:40.786 CET Job finishing up....
351 INFO 2024-10-25 09:23:40.79 CET Closing connections...
361 ALL 2024-10-25 09:23:40.845 CET The process failed.

BalagurunathanBagavathy-Oracle

@fledicu The error message is generic. This needs log file analysis, specifically, bi_server1 logs and obis1 logs. So, the SR is the right approach of investigating this issue further.

Dirk - JEM

I know, thank you - but we're investigating now for a while and maybe someone found a solution by itself somehow … 🤷‍♂️

SteveF-Oracle

Hi Dirk ( @fledicu ),

Can you provide:

1. The SR#
2. The output of: opatch lspatches
3. The error from [DOMAIN_HOME]\servers\bi_server1\logs\dataload.log and bi_server1-diagnostic.log when you refresh the database dataset.
   Also, is the dataset, configured for Live or Cached?
   If all the information is in the SR, or not shareable in public forum, then just provide the SR# and the information in the SR.

Dirk - JEM

Hi Steve,
thanks for your response - I think you will find anything inside the SR - SR 3-37526116821 : Reload of any data set in OAS 2024 fails.

When it occured first time - the system has been patched afterwards, but Support told me the patch was special for OAS2023.
In meantime I setup 2 more systems without changing anything and found the same behavior … so there is no relation to the patch at all

The datasets are "cache" - I guess live needs no explicit reload.

Thanks you for your effort.

Dirk

Dirk - JEM

Just to let you know - the SR is assigned to Dev and classified as a bug ..