You can't make this shit up.
I've been troubleshooting an ETL problem on our development server since last Thursday. The server is an x64 (64-bit Windows) machine. The ETL has been running fine on my laptop, and my bosses laptops. It crashes and burns miserably on the server with common Oracle errors, but ones which are inexplicable under the circumstances.
It turns out that all 32-bit components on 64-bit Windows are installed in folders named "Program Files (x86)". It also turns out that Oracle's database client has a bug in it which causes crashes if the path to the program has either '(' or ')' in it. You can't modify the Windows pathname without causing chaos on the system, so you are basically stuff in this Microsoft/Oracle inter-compatibility nightmare.
There is supposedly a patch for the Oracle bug now, but as is so common with Oracle support of 64-bit Windows, I keep downloading the wrong version. Hopefully, I have finally found the right one.
But seriously, I've lost a week's worth of work over a design decision by Microsoft combined with a totally bizarre Oracle bug. There's also been unbelievable collateral damage at work... The IT gatekeepers found out we were using the production database for our source data, and took our access away. They moved the QA box without telling us, and then bitched that we should have requested firewall ports weeks ago. It's just unbelievable.