Migrate software from postgres to oracle: problems with objects

[Anonymous]

Hi,

I want to change the destination database from postgres to oracle. The connections to the database are in JDBC, when changing the driver to oracle I have problems with the objects: map, twarm, etc. In MAPs, the fields are not recognized in uppercase (oracle) and the others in lowercase.
How can I make the migration with minimal impact?
Currently I have to go object by object reviewing all the configuration.

greetings and many thanks

[Anonymous]

Hi,

    Could you please provide some screen shots of the flow and the error you are getting so that we will get a better idea of your use case?

Warm Regards,
Nikhil Thampi

Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂

[Anonymous]

Hi,

The problems are:
-It is necessary to choose the schema table again in the component: because if not, it gives an error that the table does not exist
-When together a select component to the tmap, the names of the columns are capitalized and even if the link changes (for example to existing row1) the tMAP does not perform the union since it is case-sensitive.

Thanks!!!

[Anonymous]

Hi,

    I would appreciate if you could provide some screenshots of the issue (before and after).

    I guess you are having db specific changes in the schema which is not matching when the DB type is getting modified. 

Warm Regards,
Nikhil Thampi

Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂

[Anonymous]

Hi,

 I attach two images of before and after

01-PostgresJDBC.JPG
02-componentOracleTMAP00.JPG
03-componentOracleTMAP01.JPG

[Anonymous · Accepted solution]

Hi,

    Thanks for the details. I guess you are doing Guess schema after connecting the Oracle DB and it is providing the columns in upper case. Since java differentiates the variables between upper case and lower case, you are facing this issue at later stages.

     Why don't you create schema metadata for your tables in the same format as before so that these type of errors can be avoided and you will have less migration effort while changing the DB type. This will be the most easy method for you to complete the migration.

Warm Regards,
Nikhil Thampi

Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂