Im grasping a bit at straws here but I have been having a slightly "heated" finger pointing debate with a DBA colleague
We have a nightly ETL process run through OWB.
This process has not changed in some months now, as development work has been on another project.
The process was running perfectly fine up until yesterday evening, when it got "stuck" or "froze" on a mapping.
Looking in control center, I dont see the mapping doing anything at all. No SELECT, UPDATE, DELETE or anything, its just sitting there.
It sat there from about 6 AM till about 9 AM
We killed the job and restarted it and waited till about 1 PM and still no dice.
The local DBA restarted the database and we started again and still no progress.
There is no error message, it just seems to "hang" there and is frozen.
This ETL is a mirror (serving as a back up) to another ETL process.
The main ETL process ran just fine as usual, and obviously since no changes both are exactly the same. They are both run against the same database as well it just pulls the data into different schemas, so I am really befuddled and have no idea where to start to debug.
I dont even have an error message, its just "hanging" there
What can one do in a situation like this?
Any insight appreciated
Worked with the DBA and apparently it had to do with a "parallel" hint that was being used in our mapping.
It only seemed to affect this one enviroment, very odd
We implemented the change across the enviroments to make the code consistent and now it works just fine, but initial issue was just with the one enviroment.