Analysis connector Settings / Error executing DS job
Posted: Tue Sep 14, 2010 10:23 am
Hi Gurus,
I am a newbie to this world of IA. When i try to validate the engine settings, i get the above error executing ds job and check the log for more details.
The scenario is this: We are using an already existing environment of AIX for IA. The handover didnot happen in the best of the ways and i am left to explore everything of own. Previously, DB2 was used for metadata, analysis and storing data. However for storing data we have moved to Oracle and this works fine.
Having given a very brief background, i have 2 questions:
1. To resolve the above error for connecting it to analysis database on db2, what should i be doing? I am able to validate client connection & validate engine. I have added an entry for db2 wire protocol on .odbc.ini file as well. What am i missing?
2. Can i change now the analysis database to Oracle? Reason is i dont know the exact storage that will be required nor the constraints of db2 in terms of increasing the storage.
Thank you.
Regards,
Ramprasad Ramani
I am a newbie to this world of IA. When i try to validate the engine settings, i get the above error executing ds job and check the log for more details.
The scenario is this: We are using an already existing environment of AIX for IA. The handover didnot happen in the best of the ways and i am left to explore everything of own. Previously, DB2 was used for metadata, analysis and storing data. However for storing data we have moved to Oracle and this works fine.
Having given a very brief background, i have 2 questions:
1. To resolve the above error for connecting it to analysis database on db2, what should i be doing? I am able to validate client connection & validate engine. I have added an entry for db2 wire protocol on .odbc.ini file as well. What am i missing?
2. Can i change now the analysis database to Oracle? Reason is i dont know the exact storage that will be required nor the constraints of db2 in terms of increasing the storage.
Thank you.
Regards,
Ramprasad Ramani