Good afternoon, I am deploying an ODM version 8.11 in an OKE environment which must have a connection to an external Oracle database, but when configuring the parameters for the Helm installation it does not take the value of the Oracle type database. I appreciate your help in telling me how to configure these parameters so that the installation takes the external Oracle database. The following lines are added to the Helm execution script:

--set externalDatabase.type=Oracle
--set externalDatabase.secretCredentials=secretodmdb
--set externalDatabase.url= 'jdbc:oracle:thin:@//hostname:port:SID'

Hello,

Have a try with : 

--set externalDatabase.type=oracle

instead of

--set externalDatabase.type=Oracle

BR,

Mathias

Good afternoon, I am deploying an ODM version 8.11 in an OKE environment which must have a connection to an external Oracle database, but when configuring the parameters for the Helm installation it does not take the value of the Oracle type database. I appreciate your help in telling me how to configure these parameters so that the installation takes the external Oracle database. The following lines are added to the Helm execution script:

--set externalDatabase.type=Oracle
--set externalDatabase.secretCredentials=secretodmdb
--set externalDatabase.url= 'jdbc:oracle:thin:@//hostname:port:SID'

Hello, thank you very much for your collaboration. I have already tried both ways and it still does not work. I appreciate your ideas to solve this problem.

Hello,

Have a try with : 

--set externalDatabase.type=oracle

instead of

--set externalDatabase.type=Oracle

BR,

Mathias

Good afternoon, I am deploying an ODM version 8.11 in an OKE environment which must have a connection to an external Oracle database, but when configuring the parameters for the Helm installation it does not take the value of the Oracle type database. I appreciate your help in telling me how to configure these parameters so that the installation takes the external Oracle database. The following lines are added to the Helm execution script:

--set externalDatabase.type=Oracle
--set externalDatabase.secretCredentials=secretodmdb
--set externalDatabase.url= 'jdbc:oracle:thin:@//hostname:port:SID'

Hello,

I just checked and unfortunately the externalDatabase.url parameter is not available with ODM8.11. It's delivered since ODM8.12 meaning ODM on K8S 23.1.0.

But perhaps you can manage it with the delivered parameters serverName/databaseName/port ?

The last solution is to use the externalCustomDatabase following https://www.ibm.com/docs/en/odm/8.11.0?topic=database-configuring-custom-external by providing the entire liberty datasource configuration.

BR,

Mathias

Hello, thank you very much for your collaboration. I have already tried both ways and it still does not work. I appreciate your ideas to solve this problem.

Hello,

Have a try with : 

--set externalDatabase.type=oracle

instead of

--set externalDatabase.type=Oracle

BR,

Mathias

Good afternoon, I am deploying an ODM version 8.11 in an OKE environment which must have a connection to an external Oracle database, but when configuring the parameters for the Helm installation it does not take the value of the Oracle type database. I appreciate your help in telling me how to configure these parameters so that the installation takes the external Oracle database. The following lines are added to the Helm execution script:

--set externalDatabase.type=Oracle
--set externalDatabase.secretCredentials=secretodmdb
--set externalDatabase.url= 'jdbc:oracle:thin:@//hostname:port:SID'

Good afternoon, I am deploying an ODM version 8.11 in an OKE environment which must have a connection to an external Oracle database, but when configuring the parameters for the Helm installation it does not take the value of the Oracle type database. I appreciate your help in telling me how to configure these parameters so that the installation takes the external Oracle database. The following lines are added to the Helm execution script:

--set externalDatabase.type=Oracle
--set externalDatabase.secretCredentials=secretodmdb
--set externalDatabase.url= 'jdbc:oracle:thin:@//hostname:port:SID'

Hello,

is there a specific reason for using an older version of ODM (8.11) instead of the current one (9.0.0.1) ? Clients adopting ODM on Kubernetes tend to stick to the latest versions.

Good afternoon, I am deploying an ODM version 8.11 in an OKE environment which must have a connection to an external Oracle database, but when configuring the parameters for the Helm installation it does not take the value of the Oracle type database. I appreciate your help in telling me how to configure these parameters so that the installation takes the external Oracle database. The following lines are added to the Helm execution script:

--set externalDatabase.type=Oracle
--set externalDatabase.secretCredentials=secretodmdb
--set externalDatabase.url= 'jdbc:oracle:thin:@//hostname:port:SID'

Hello,

is there a specific reason for using an older version of ODM (8.11) instead of the current one (9.0.0.1) ? Clients adopting ODM on Kubernetes tend to stick to the latest versions.

Good afternoon, I am deploying an ODM version 8.11 in an OKE environment which must have a connection to an external Oracle database, but when configuring the parameters for the Helm installation it does not take the value of the Oracle type database. I appreciate your help in telling me how to configure these parameters so that the installation takes the external Oracle database. The following lines are added to the Helm execution script:

--set externalDatabase.type=Oracle
--set externalDatabase.secretCredentials=secretodmdb
--set externalDatabase.url= 'jdbc:oracle:thin:@//hostname:port:SID'