Dt:19 March 2014
The honeymoon is over literally.Just when you were close to giving ODI the best ETL tool for OBIA award.They have goofed up.And Big time.
ODI-23040 -->this is the error which I get when I am trying to import my code from one environment to another.
No Rhyme no Reason. Guess it feels good to be a developer at Oracle when they are told never let the end user know what the error is.Let them come to us and beg for support.
But seriously for something as simple as migrating code from one environment to another which Informatica does so efficiently .I had to go through 100s of documents advising me how to use Internal Ids .What these internal Ids mean.How ODI stores this .......& so on....so forth..... .
I mean common which developer would share this information to his customer that this is how we store our objects and you have to change your backend Ids for our migration to work.
I understand that ODI was designed with another view of code migration .But Oracle being the business leader should have known for sure that the three tier architecture of DEV, QA & PROD is how projects are executed in the real world & this is how they should have built the migration module.
For now hope for those guys at Oracle Support to come out with a meaningful answer.It sucks.But yes its business !!!
The honeymoon is over literally.Just when you were close to giving ODI the best ETL tool for OBIA award.They have goofed up.And Big time.
ODI-23040 -->this is the error which I get when I am trying to import my code from one environment to another.
No Rhyme no Reason. Guess it feels good to be a developer at Oracle when they are told never let the end user know what the error is.Let them come to us and beg for support.
But seriously for something as simple as migrating code from one environment to another which Informatica does so efficiently .I had to go through 100s of documents advising me how to use Internal Ids .What these internal Ids mean.How ODI stores this .......& so on....so forth..... .
I mean common which developer would share this information to his customer that this is how we store our objects and you have to change your backend Ids for our migration to work.
I understand that ODI was designed with another view of code migration .But Oracle being the business leader should have known for sure that the three tier architecture of DEV, QA & PROD is how projects are executed in the real world & this is how they should have built the migration module.
For now hope for those guys at Oracle Support to come out with a meaningful answer.It sucks.But yes its business !!!