Tip of the week:
Environment: EBS 12.1.3, Oracle 11.2.0.3, Microsoft Windows 2008 R2, SQL-Server 2008 R2, Oracle Fusion BI 11g.
As we continue to scuffle through Fusion OBIEE / EBS R12 / SQLServer we came across yet another enthralling issue. Yes its enthralling especially when you have heterogeneous databases in such tightly integrated complex environments.
While trying to perform a full load first time with 12.1.3 adapter (OBI Analytics provides 12.1.3 adapter to ease migration from EBS 11i to R12.1.3) , we ran into an interesting error that we found in informatica powercenter workflow monitor‘s log events.
ERROR : (8840 | WRITER_1_*_1) : (IS | BIA_IS) : node01_server_name : WRT_8229 : Database errors occurred:
FnName: Execute -- [Microsoft][ODBC SQL Server Driver]Datetime field overflow
FnName: Execute -- [Microsoft][ODBC Driver Manager] Function sequence error"
Looking further into the logs, we were able to figure out the exact record that was causing the failure. Interesting we found the error was due to a record with date 31-MAY-0201. Even though this error can be rectified in EBS(our source system) or try to locate where this error is occurring and fix the mapping to perform the operation with YYYY instead of just YY. Vital material to remember is SQLServer doesn't accept records outside of the date range January 1, 1753 - December 31, 9999. When we are so used to work on Oracle databases, such SQL Server limitation could be missed.
As you may know that you can skip errors in informatica using the property "Stop on Errors" to 0, which is set to 0. This is not the case with 12.1.3 adapter. Its set to 1 by default, which will force the job to fail on error. Of course, this is not applicable for fatal errors though.
Further tips on Fusion Oracle Business Intelligence / SQLServer environment @
http://oracletechnologistblog.wordpress.com/category/obiee-obia/
As always, thanks to contributors Ramke Ramakrishnan and Steve Meder.
No comments:
Post a Comment