What happens to your ODI interopability when changes are made in your target datastore, in other words how are changes picked up and handled in ODI?
I staged such a scenario to test the robustness of ODI and following troubleshooting hints & tips could be of help to anyone facing this situation in a real-time environment:
- ‘The primary key is not unique, PK Errors’: I couldn’t figure out what this error was about because my sequences were defined correctly on the target datastore and the invocation in my ODI interface was defined correct as well. => Solution: delete the working tables in your sunopsis working repository, the snpw-schema. When you run the interface again it’ll work smoothly.
- ”Join error between the table ‘x’ and the table ‘y” => This error was resolved by deleting all constraints defined on my target-model and by reverse engineering the model-object again. => New attributes, constraint are reversed as expected, but existing constraints and attributes aren’t automatically deleted, this is a manual job you’ll have to perform.
- You’re getting ‘privileges’-exceptions when trying to execute your interfaces => make sure to grant the target-datasource dba-privileges this is needed to be able to access the snpw- and snpm-datastores.
- Working with Excel Data : ‘-1305 : S0002 : java.sql.SQLException: [Microsoft][ODBC Excel Driver] The Microsoft Jet database engine could not find the object ‘MO’. Make sure the object exists and that you spell its name and the path name correctly.’ => This error is thrown when the Excel you’re pointing to is opened up whilst running ODI interfaces. When you close the Excel file no, this exception will be resolved.
Other usefull hints & tips are always welcome.