Keeping up with EPM Cloud

The ODTUG Kscope conference attracts Oracle experts from all over the globe to learn and share knowledge with other Oracle technology users. This year Kscope24 was held in Nashville (aka music city), at the Gaylord Opryland Resort & Convention Center. Representing Brovanture this year was myself (Lydia Maksoud) and my colleagues Sarah Dow and Roger Cressey. Friday As Sarah and I were travelling over from London, we flew in on Friday and after a relatively smooth journey (compared to the connecting flights last year) we arrived in Nashville on Friday evening. The first thing that hit us was the heat, it’s around 38 degrees in Nashville and very humid! The second thing was the size of the hotel – the Gaylord Opryland has multiple regions, almost like a small town, and is quite literally the biggest hotel either of us had ever been to. Saturday Luckily on Saturday we had some spare time to explore a bit of Nashville before the conference kicked off. This of course meant we had

Recently I came across an issue with Pipelines where if a job was taking longer than around 30 mins in a pipeline, the pipeline would move onto the next job before letting the job finish. The job would also show as "RUNNING" in the pipeline email notification, and the email would say the pipeline has failed, even though when we check the job console, none of the jobs in the pipeline had failed. For example below, the pipeline moves on even though the aggregation is still running which then means the remaining jobs are not running in the correct order and the pipeline status shows as FAILED: After asking on Customer Connect, a helpful user (thank you Ija Vidaurri!) gave us the solution, which is to set the Batch Timeout In Minutes setting to a higher value (by default this is empty so I’m not sure of the exact default timeout). This can be done by going to Data Exchange -> System Settings and entering a minute value into the Batch Timeout In Minutes setting.