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

Cool - I remember I once used the maps to visualize where warehouse stock is located and then in a second step to optimize the way of transportation but this second part has not been realized, sorrily

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

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…

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

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…

I face the same problem - and it's an error by Oracle BI. I think it comes with the new Alta UI. If you run this Answer in a Dashboard or if you use "Show as it looks in a Dashboard", then you will see the Buttons. I've opened a SR and the guy from the support says he cannot replicate even if I have exactly the same…

One hint about a webcatalog upgrade is the timestamp and the contenct of webcatupgrade0.log and the inherent upgrade-objects-folder in <INSTANCE_HOME>\diagnostics\logs\OracleBIPresentationServicesComponent\coreapplication_obips1

Oracle says: "Before upgrading from OBIEE 11g to OBIEE 12c, ensure that your 11.1.1.7 | 11.1.1.9 catalog is the correct version. This is accomplished by running a full catalog upgrade (not Scan and Update in the Answers Administration link) on your current 11g catalog environment." and "When the full catalog upgraded is…

Sorry for this is not an answer actually - but we face the same problem in OBIEE 12c - 12.2.1.1. as well as in 12.2.1.2. And we did not had this error before ( 11.1.1.7.) ?

I thought it would be a problem of Oracle BI 12c, since we have it as from the migration from 11.1.1.7 to 12c!?

What about a graceful shutdown, when the windows Server will be rebooted? I thought this is important too, isn't it?