Keeping the Java series, here is more one Java Code for ODI.
The below codes is used to create an Interface that can create Multiple Dataset depending on the source
datastore and Operator provided.
For example – Here
we are using three different source tables ,you can change them and provide any number of Source datastore in the array and accordingly n number of the Dataset are created.
For n number of the source database , n-1 number of the Operator needs to be provided.
For example if there are 4 different source datastore , then 3 operator need to provided which can be same or different depending on your requirement.
To move on I changed the win32 to win64 and saved ua.bat I again got the error , I thought let me go for win32 ODI installation .
Moved to 32 bit ODI Installation
Launched the Upgrade Assistant from <ODI_HOME>/bin/ua.bat
I am presently upgrading only the ODI repositories and not other component.
The third options – Check that Upgrade Occurs only to Cloned Repositories , caught my attention. Still I just clicked Next and moved ahead.
In this screen I checked Database Backup completed , so I thought to myself , looks like I need to do something or I am missing something , so I searched for the Upgrade from ODI 10g to ODI 11g documentation and I found this
Here they have mentioned to do the cloning or backup of the Repository of Master and Work under the Master . Rather than creating the scripts I used a simple process through SQL Developer –> Database Copy
Before doing so Create the required ODI 11g Master and Work Repository schema and assign the required tablespaces to them .Once done using the Database copy , copy the Tables and the data.
In Next step , SQL Developer lists all the steps and finally click Finish to start the copy Process. Once completed , you will able to find all the Master Repository tables created in the next Master Repository schema with the required data in it.
Keep repeating the Process for all the Work Repository under that above Master Repository. Once completed Click Next in the Upgrade Assistant to move to Step 4.
Here in Step 4 list all the details required and provide the Master Repository just created above and provide the SUPERVISOR username and Password used in ODI 10g Repository.
Once the above screen is successful , Upgrade Assistant will lists all the Work Repository under the Master . Now provide the username and password of the schema of Cloned ODI 11g schema .
[ Note in case , any of the above mentioned steps is wrong or incorrect you will get an error screen as shows below
Use the First or the Third option but never the second option as there might be chances of corruption causing issues or improper Repository setup ]
Once Work Repository schema authentication is done , Click Upgrade to start the Upgradation Process.
Finally the required tables , and LKM are upgraded and the logs can be visited by click on the link mentioned in the Upgrade Assistant .
Now login into the ODI Studio and provide the Master Repository detail and select the appropriate Work Repository and log in , you don’t need to provide the internal ID since it will use the Internal Id specified during ODI 10g setup .
As you can see all the Interface, Model , Topology, agents are all created but you would need to create the appropriate Standalone Agent script for the migrated Agent.
I wanted to test the migration so I executed an Interface and it worked.
I also had another EWR setup under my Master Repository , I logged inside it too.
I can see all the required Scenarios, topology and other ODI objects.
This are some of the simple Upgrade process from ODI 10g DWR and EWR to ODI 11g .
Hope to hear from you all how was your experience with the Upgrade Assistant and what kind of errors you encountered .
Keep looking into odiexperts for more ODI 11g series Posts.
In ODI 11g when I was doing the installation , I got a setup screen to setup the agent and I created the agent called MAIN_AGENT and I initially thought it’s a cool feature and thought that the Agent was created and automatically the ODIPARAMS and other files will get update .
Once the installation is done and the ODI 11g instance is started , I just triggered the agent and I got an Error . Oops I have not started the agent_MAIN_AGENT.bat and when I started it suddenly vanished , I had a feeling that some thing was wrong and something is not setup properly, so I went inside the agent_MAIN_AGENT.bat script and saw this
In short its just the file calling the agent.bat with the required parameters populated , so started digging around and looked at the odiparams .
The odiparams file was located where the standalone agent is located namely
I looked at it and saw that its pretty much the same but rather than the HSQL driver I was able to see the parameters for oracle. I started updating and provided the required parameters, at the ODI_MASTER_ENCODED_PASS I need to supply the encoded password , so I started typing in the command prompt
agent encode <password>
and ODI was trying to start the agent <password> ,so I knew some thing is changed again and I looked at the folder and I was able to see the encode.bat . Ah ! new funda . so I tried
encode <password >
Voila ! it worked
After updating the required parameters , I was scrolling and looking at the other option , I saw new options ODI_CONNECTION_RETRY_COUNT , ODI_CONNECTION_RETRY_DELAY
and also the ODI_JAVA_HOME is set with the required jdk path which mean it no more reads from the JAVA_HOME or setting the environment variable ODI_JAVA_HOME. hmm !
Coming back to the above two option I was trying to find out what do they mean and the definition was defined as follows
I thought ok , let me play with these option some time later and let me restart the agent.
So I went to topology and created and updated the physical and logical agents as required .
Now I thought let me start the agent_MAIN_AGENT.bat and start again .
It started . Cool ,but then I thought how about if I want to set up again another standalone agent on 20911, so I went to Topology created the Physical and Logical and called it second agent.
After doing so I made the duplicate of the agent_MAIN_AGENT.bat and called it agent_second_agent.bat and update the required parameters
Now I thought let me start that too and slowly the second_agent started too .
Now I wanted to make them as service so I was looking for agentservice.bat and I looked into the documentation and search for agent service but in vain .I even tried to bring in the Wrapper codes from ODI 10 g into 11g and make it as a service , i was successful in making the service but the conf files calls few java classes which could not be migrated since that would be complicated process.
Looks like we can only use the agentscheduler mode in windows but I can’t believe it… I will try to find out how to start it as service and publish as soon as I discovery!