I found this out the fun way, of course, by going through, grabbing the SQL from the logs, and then modifying said SQL to run against Oracle. I should have paid attention to that "Check Consistency" warning.
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg4AJPnaWtRApGnCvC-thGV-SU34bDhZ-QAfdTK1BixpY5-_9X3IUbtkSuV4oCvV6eQi1sWG_Or4chZ7TdLVsBPP7XyVlzmt0BHNLSL7ESszKdVlFqDyVtjFSLpKiGEvDJJj4-ADDbTagM/s400/01_consistency_check_manager.jpg)
I spent an hour or so "fixing" the SQL, removing stuff like the following:
fn ifnullmostly small stuff, but annoying none-the-less. Strangely (to me anyway), this was the SQL submitted to an Oracle database...without errors. I'm guessing that somewhere, either in OBI or in the driver itself, the SQL is rewritten.
{ curly brackets }
d '2004-04-10'
ts '2004-04-10 13:44:39'
After I realized what had happened, I went back into the RPD and updated the database properties.
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiYW8tg_8InvrAzkasZDSgtE3zjaCeVFTc9RRYcYyGoySyK-TLGmx7ttkX8TkEHcTZQNey6D9Q2Kl6dypwEwAjZ0HfZM968Dig4Ez5RvBzIBAp71LttNrf5bMjocxo3bpc39ca95p90Kzw/s800/02_obiee1111.jpg)
It was ODBC basic
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjK854ziL9qBYZatIBaQ-ik5lK5Oc2PPHVTItGtT-4TVLleq7m75Ro40GiPmWAbmj7V9indSI4Aq83koxH1CVGbvzHfJ90E3wFVyDER5IZdi3EEk_O5-Mwys6akSkRRtC3kvnhKwSR4KE_c/s400/03_obiee_database_properties.jpg)
I changed it to Oracle 10R2/11g
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjlqbo3kGwEb34VZg4S6rbAPRut7gVMJpLxrUvZgnG5gudbMZR955PGOcTCTKsCMuGZiDyhOwXN69I0sEHTeqZ1m8v7YY7DIbJomMjIEu2YLs3czCkt8zy56hknkOUbOUoBQw-LeWitOO-N/s400/04_obiee_database_properties_changed.jpg)
I tried the Consistency Check again and still received the warning. Opened up the database properties again and selected the Features tab
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgJA9bujVPtbzm15gwLlKUjPVjs6w0_hnbJS_iqUWcPOG0HJ4IV-WUDBZvTN0sxQTxOCjet_g-NaJulTck0uiM8HEdtYI5uTIqEpu0OSXcIRwageA3BSU-Pvw0TcqF7J2m4Dy4TGga6u5wU/s400/05_database_properties_features.jpg)
Then selected "Revert to Defaults"
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj3dcfERTO-k3-lhhhUl9mq3tlENEhusIl1f5OTpckeM9rartiTVE94Z1IV2R5kOqiYYIYqoQ2plrvuT3rmNmiMvcRZMP0tE4afUuYX5IoUZKGdhr0rpBs3WHMz_LdSlHSnUgp6NpRO-xGU/s400/06_revert_to_defaults.jpg)
Run the Consistency Checker again and voila!
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg_hge8fbjUXwC-dMWvlozTFkYC4RZ6eNf8aux6HGWUfnH6hoxmNKuYLfnHVj_bRsvUPfXH9dbAkddxVHlTMgVZBe1K3xEz1ZqfgheHTsPmwkjBikEzAMMZ3s8nsdZn1lqvvJrPhhtsMyLI/s400/07_consistency.jpg)
So don't waste your time like I did. Make sure you use the Consistency Check Manager and make sure your database defaults match.
No comments:
Post a Comment