This seems similar to my issue recently where our "database" source connector using ODBC would take forever to connect, and eventually fail to connect, even though "Test connection" button in source connector (ie. configure connector) and the ODBC DSN "Test connection" button were successful.

We ended up converting the source connector to use oracle-native instead of ODBC, now all is well.

Hello Mark

Thank you for your advice but the first way that we use to get a connection DB is with oracle-native in the connector configuration and connect-it shows the error

We did some test with only the ODBC an it works but when we try use in the connector configuration again we have error to get connection

Could you please tell me if you have another advice? Thank you in advance

Best regards 

Other than ensuring "run as administrator", I do not.

Hello Mark

I doesn't work with the administrator account. I see another wrong behavior when I try to use ODBC but the combo box in the connector is empty I have the ODBC 32bits configured but I can use it

Do you have some advice about the connector behavior or to fix the connections? Thank you so much for your attention and participation.

Best regards

Sorry, even though I have been hearing ODBC is deprecated, I cannot be of more help.  You mention ODBC 32-bit, so I assume the CIT application is also 32-bit as I am sure you would have converted to ODBC 64-bit.  Contact MicroFocus for help.

Yes you´re rigth

But I have another error when I try to use ODBC

"ORA-01406 fetched column value was truncated. SQLStare 1000"

I have a connection to DB but when I try to do the mapping between the DB connector and SM web service appears this message and I can't continue the mapping configuration.

Do you have some advice about that?

Thank you

Best regards

Not really, but a simple online search returns the following possibilities...

Number of columns from a table

Declared variable size not large enough

ODBC DSN settings for oracle / workaround tabs