Db2

Is there a way to override this check in dmctop (version 1.0.4.1):

level=error msg=DbConfig error="DB version ******** not supported"

Dmctop documentation states that dmctop supports Db2 11.1 and above. Masked by me field in a/m is definitely above 11.1 :-)

Hello Jan,

dmctop does not check the db2level (instance level), it checks the database level.

Can you please run the following command, and see if your database level is the same as your instance level:

db2 "select versionnumber from sysibm.sysversions order by 1 desc"

If they are not the same, you will need to run the db2updv111 command as described in the Db2 manual at:

https://www.ibm.com/docs/en/db2/11.1?topic=sc-db2updv111-update-database-version-111-fix-pack-command

The reason that we check the database level is because dmctop uses internal Db2 APIs, and if they are not on the correct level, Db2 returns SQLCODE=-206 "<column_name> is not valid in the context where it is used." error, and dmctop can't get the information from Db2.

I hope that helps!

Is there a way to override this check in dmctop (version 1.0.4.1):

level=error msg=DbConfig error="DB version ******** not supported"

Dmctop documentation states that dmctop supports Db2 11.1 and above. Masked by me field in a/m is definitely above 11.1 :-)

Indeed my database version number is higher than 11.1 ...

I was suspecting that Db2 API's play a role - I was assuming that "supporting version 11.1 and above will allow dmctop to be executed on higher database versions.

Hello Jan,

dmctop does not check the db2level (instance level), it checks the database level.

Can you please run the following command, and see if your database level is the same as your instance level:

db2 "select versionnumber from sysibm.sysversions order by 1 desc"

If they are not the same, you will need to run the db2updv111 command as described in the Db2 manual at:

https://www.ibm.com/docs/en/db2/11.1?topic=sc-db2updv111-update-database-version-111-fix-pack-command

The reason that we check the database level is because dmctop uses internal Db2 APIs, and if they are not on the correct level, Db2 returns SQLCODE=-206 "<column_name> is not valid in the context where it is used." error, and dmctop can't get the information from Db2.

I hope that helps!

Is there a way to override this check in dmctop (version 1.0.4.1):

level=error msg=DbConfig error="DB version ******** not supported"

Dmctop documentation states that dmctop supports Db2 11.1 and above. Masked by me field in a/m is definitely above 11.1 :-)

Hello Jan,

Yes, dmctop supports Db2 11.1 or higher, as long as your APIs are on the same instance level:

https://www.ibm.com/docs/en/db2-data-mgr-console/3.1.x?topic=monitoring-utility-dmctop

If you still have problems with it, please create a case with Db2 Data Management Console support team for further investigation.

Thanks!

Indeed my database version number is higher than 11.1 ...

I was suspecting that Db2 API's play a role - I was assuming that "supporting version 11.1 and above will allow dmctop to be executed on higher database versions.

Hello Jan,

dmctop does not check the db2level (instance level), it checks the database level.

Can you please run the following command, and see if your database level is the same as your instance level:

db2 "select versionnumber from sysibm.sysversions order by 1 desc"

If they are not the same, you will need to run the db2updv111 command as described in the Db2 manual at:

https://www.ibm.com/docs/en/db2/11.1?topic=sc-db2updv111-update-database-version-111-fix-pack-command

The reason that we check the database level is because dmctop uses internal Db2 APIs, and if they are not on the correct level, Db2 returns SQLCODE=-206 "<column_name> is not valid in the context where it is used." error, and dmctop can't get the information from Db2.

I hope that helps!

Is there a way to override this check in dmctop (version 1.0.4.1):

level=error msg=DbConfig error="DB version ******** not supported"

Dmctop documentation states that dmctop supports Db2 11.1 and above. Masked by me field in a/m is definitely above 11.1 :-)

Indeed version of database = version of instance and both are higher than 11.1:

time="2023-02-18T05:55:57.277671Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=babba900-8ab6-4cda-baf2-4fc162f1b076
time="2023-02-18T05:56:24.565631Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.271955Z" level=info msg=DbUtils event=Information info="Setting DB Connection Info" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.271955Z" level=info msg=DbUtils event=Information info="Connecting to DB" moreInfo=";25000;sample;db2admin" trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.940927Z" level=info msg=DbUtils event=Information info="Connected to DB" moreInfo=";25000;sample;db2admin" trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.940927Z" level=info msg=ConfigUtils event=Information info="Initializing DB config" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:36.267717Z" level=error msg=DbConfig error="DB version 12010000 not supported" event="Encountered exception" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586

Hello Jan,

Yes, dmctop supports Db2 11.1 or higher, as long as your APIs are on the same instance level:

https://www.ibm.com/docs/en/db2-data-mgr-console/3.1.x?topic=monitoring-utility-dmctop

If you still have problems with it, please create a case with Db2 Data Management Console support team for further investigation.

Thanks!

Indeed my database version number is higher than 11.1 ...

I was suspecting that Db2 API's play a role - I was assuming that "supporting version 11.1 and above will allow dmctop to be executed on higher database versions.

Hello Jan,

dmctop does not check the db2level (instance level), it checks the database level.

Can you please run the following command, and see if your database level is the same as your instance level:

db2 "select versionnumber from sysibm.sysversions order by 1 desc"

If they are not the same, you will need to run the db2updv111 command as described in the Db2 manual at:

https://www.ibm.com/docs/en/db2/11.1?topic=sc-db2updv111-update-database-version-111-fix-pack-command

The reason that we check the database level is because dmctop uses internal Db2 APIs, and if they are not on the correct level, Db2 returns SQLCODE=-206 "<column_name> is not valid in the context where it is used." error, and dmctop can't get the information from Db2.

I hope that helps!

Is there a way to override this check in dmctop (version 1.0.4.1):

level=error msg=DbConfig error="DB version ******** not supported"

Dmctop documentation states that dmctop supports Db2 11.1 and above. Masked by me field in a/m is definitely above 11.1 :-)

Thanks Jan for the information. 

May you pls open a case against Data Management Console to let team do further investigation on this issue?

Indeed version of database = version of instance and both are higher than 11.1:

time="2023-02-18T05:55:57.277671Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=babba900-8ab6-4cda-baf2-4fc162f1b076
time="2023-02-18T05:56:24.565631Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.271955Z" level=info msg=DbUtils event=Information info="Setting DB Connection Info" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.271955Z" level=info msg=DbUtils event=Information info="Connecting to DB" moreInfo=";25000;sample;db2admin" trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.940927Z" level=info msg=DbUtils event=Information info="Connected to DB" moreInfo=";25000;sample;db2admin" trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.940927Z" level=info msg=ConfigUtils event=Information info="Initializing DB config" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:36.267717Z" level=error msg=DbConfig error="DB version 12010000 not supported" event="Encountered exception" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586

Hello Jan,

Yes, dmctop supports Db2 11.1 or higher, as long as your APIs are on the same instance level:

https://www.ibm.com/docs/en/db2-data-mgr-console/3.1.x?topic=monitoring-utility-dmctop

If you still have problems with it, please create a case with Db2 Data Management Console support team for further investigation.

Thanks!

Indeed my database version number is higher than 11.1 ...

I was suspecting that Db2 API's play a role - I was assuming that "supporting version 11.1 and above will allow dmctop to be executed on higher database versions.

Hello Jan,

dmctop does not check the db2level (instance level), it checks the database level.

Can you please run the following command, and see if your database level is the same as your instance level:

db2 "select versionnumber from sysibm.sysversions order by 1 desc"

If they are not the same, you will need to run the db2updv111 command as described in the Db2 manual at:

https://www.ibm.com/docs/en/db2/11.1?topic=sc-db2updv111-update-database-version-111-fix-pack-command

The reason that we check the database level is because dmctop uses internal Db2 APIs, and if they are not on the correct level, Db2 returns SQLCODE=-206 "<column_name> is not valid in the context where it is used." error, and dmctop can't get the information from Db2.

I hope that helps!

Is there a way to override this check in dmctop (version 1.0.4.1):

level=error msg=DbConfig error="DB version ******** not supported"

Dmctop documentation states that dmctop supports Db2 11.1 and above. Masked by me field in a/m is definitely above 11.1 :-)

Thanks Jan for the information. 

May you pls open a case against Data Management Console to let team do further investigation on this issue?

Indeed version of database = version of instance and both are higher than 11.1:

time="2023-02-18T05:55:57.277671Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=babba900-8ab6-4cda-baf2-4fc162f1b076
time="2023-02-18T05:56:24.565631Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.271955Z" level=info msg=DbUtils event=Information info="Setting DB Connection Info" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.271955Z" level=info msg=DbUtils event=Information info="Connecting to DB" moreInfo=";25000;sample;db2admin" trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.940927Z" level=info msg=DbUtils event=Information info="Connected to DB" moreInfo=";25000;sample;db2admin" trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.940927Z" level=info msg=ConfigUtils event=Information info="Initializing DB config" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:36.267717Z" level=error msg=DbConfig error="DB version 12010000 not supported" event="Encountered exception" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586

Hello Jan,

Yes, dmctop supports Db2 11.1 or higher, as long as your APIs are on the same instance level:

https://www.ibm.com/docs/en/db2-data-mgr-console/3.1.x?topic=monitoring-utility-dmctop

If you still have problems with it, please create a case with Db2 Data Management Console support team for further investigation.

Thanks!

Indeed my database version number is higher than 11.1 ...

I was suspecting that Db2 API's play a role - I was assuming that "supporting version 11.1 and above will allow dmctop to be executed on higher database versions.

Hello Jan,

dmctop does not check the db2level (instance level), it checks the database level.

Can you please run the following command, and see if your database level is the same as your instance level:

db2 "select versionnumber from sysibm.sysversions order by 1 desc"

If they are not the same, you will need to run the db2updv111 command as described in the Db2 manual at:

https://www.ibm.com/docs/en/db2/11.1?topic=sc-db2updv111-update-database-version-111-fix-pack-command

The reason that we check the database level is because dmctop uses internal Db2 APIs, and if they are not on the correct level, Db2 returns SQLCODE=-206 "<column_name> is not valid in the context where it is used." error, and dmctop can't get the information from Db2.

I hope that helps!

Is there a way to override this check in dmctop (version 1.0.4.1):

level=error msg=DbConfig error="DB version ******** not supported"

Dmctop documentation states that dmctop supports Db2 11.1 and above. Masked by me field in a/m is definitely above 11.1 :-)

Thanks Jan for the information. 

May you pls open a case against Data Management Console to let team do further investigation on this issue?

Indeed version of database = version of instance and both are higher than 11.1:

time="2023-02-18T05:55:57.277671Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=babba900-8ab6-4cda-baf2-4fc162f1b076
time="2023-02-18T05:56:24.565631Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.271955Z" level=info msg=DbUtils event=Information info="Setting DB Connection Info" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.271955Z" level=info msg=DbUtils event=Information info="Connecting to DB" moreInfo=";25000;sample;db2admin" trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.940927Z" level=info msg=DbUtils event=Information info="Connected to DB" moreInfo=";25000;sample;db2admin" trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.940927Z" level=info msg=ConfigUtils event=Information info="Initializing DB config" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:36.267717Z" level=error msg=DbConfig error="DB version 12010000 not supported" event="Encountered exception" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586

Hello Jan,

Yes, dmctop supports Db2 11.1 or higher, as long as your APIs are on the same instance level:

https://www.ibm.com/docs/en/db2-data-mgr-console/3.1.x?topic=monitoring-utility-dmctop

If you still have problems with it, please create a case with Db2 Data Management Console support team for further investigation.

Thanks!

Indeed my database version number is higher than 11.1 ...

I was suspecting that Db2 API's play a role - I was assuming that "supporting version 11.1 and above will allow dmctop to be executed on higher database versions.

Hello Jan,

dmctop does not check the db2level (instance level), it checks the database level.

Can you please run the following command, and see if your database level is the same as your instance level:

db2 "select versionnumber from sysibm.sysversions order by 1 desc"

If they are not the same, you will need to run the db2updv111 command as described in the Db2 manual at:

https://www.ibm.com/docs/en/db2/11.1?topic=sc-db2updv111-update-database-version-111-fix-pack-command

The reason that we check the database level is because dmctop uses internal Db2 APIs, and if they are not on the correct level, Db2 returns SQLCODE=-206 "<column_name> is not valid in the context where it is used." error, and dmctop can't get the information from Db2.

I hope that helps!

Is there a way to override this check in dmctop (version 1.0.4.1):

level=error msg=DbConfig error="DB version ******** not supported"

Dmctop documentation states that dmctop supports Db2 11.1 and above. Masked by me field in a/m is definitely above 11.1 :-)

Thanks Jan for the information. 

May you pls open a case against Data Management Console to let team do further investigation on this issue?

Indeed version of database = version of instance and both are higher than 11.1:

time="2023-02-18T05:55:57.277671Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=babba900-8ab6-4cda-baf2-4fc162f1b076
time="2023-02-18T05:56:24.565631Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.271955Z" level=info msg=DbUtils event=Information info="Setting DB Connection Info" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.271955Z" level=info msg=DbUtils event=Information info="Connecting to DB" moreInfo=";25000;sample;db2admin" trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.940927Z" level=info msg=DbUtils event=Information info="Connected to DB" moreInfo=";25000;sample;db2admin" trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.940927Z" level=info msg=ConfigUtils event=Information info="Initializing DB config" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:36.267717Z" level=error msg=DbConfig error="DB version 12010000 not supported" event="Encountered exception" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586

Hello Jan,

Yes, dmctop supports Db2 11.1 or higher, as long as your APIs are on the same instance level:

https://www.ibm.com/docs/en/db2-data-mgr-console/3.1.x?topic=monitoring-utility-dmctop

If you still have problems with it, please create a case with Db2 Data Management Console support team for further investigation.

Thanks!

Indeed my database version number is higher than 11.1 ...

I was suspecting that Db2 API's play a role - I was assuming that "supporting version 11.1 and above will allow dmctop to be executed on higher database versions.

Hello Jan,

dmctop does not check the db2level (instance level), it checks the database level.

Can you please run the following command, and see if your database level is the same as your instance level:

db2 "select versionnumber from sysibm.sysversions order by 1 desc"

If they are not the same, you will need to run the db2updv111 command as described in the Db2 manual at:

https://www.ibm.com/docs/en/db2/11.1?topic=sc-db2updv111-update-database-version-111-fix-pack-command

The reason that we check the database level is because dmctop uses internal Db2 APIs, and if they are not on the correct level, Db2 returns SQLCODE=-206 "<column_name> is not valid in the context where it is used." error, and dmctop can't get the information from Db2.

I hope that helps!

Is there a way to override this check in dmctop (version 1.0.4.1):

level=error msg=DbConfig error="DB version ******** not supported"

Dmctop documentation states that dmctop supports Db2 11.1 and above. Masked by me field in a/m is definitely above 11.1 :-)

I will repeat my question: when DMCTop will recognize Db2 LUW V12.1.0.o or later?

Are we waiting for Db2 LUV V13.1.0.0?

Thanks Jan for the information. 

May you pls open a case against Data Management Console to let team do further investigation on this issue?

Indeed version of database = version of instance and both are higher than 11.1:

time="2023-02-18T05:55:57.277671Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=babba900-8ab6-4cda-baf2-4fc162f1b076
time="2023-02-18T05:56:24.565631Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.271955Z" level=info msg=DbUtils event=Information info="Setting DB Connection Info" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.271955Z" level=info msg=DbUtils event=Information info="Connecting to DB" moreInfo=";25000;sample;db2admin" trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.940927Z" level=info msg=DbUtils event=Information info="Connected to DB" moreInfo=";25000;sample;db2admin" trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.940927Z" level=info msg=ConfigUtils event=Information info="Initializing DB config" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:36.267717Z" level=error msg=DbConfig error="DB version 12010000 not supported" event="Encountered exception" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586

Hello Jan,

Yes, dmctop supports Db2 11.1 or higher, as long as your APIs are on the same instance level:

https://www.ibm.com/docs/en/db2-data-mgr-console/3.1.x?topic=monitoring-utility-dmctop

If you still have problems with it, please create a case with Db2 Data Management Console support team for further investigation.

Thanks!

Indeed my database version number is higher than 11.1 ...

I was suspecting that Db2 API's play a role - I was assuming that "supporting version 11.1 and above will allow dmctop to be executed on higher database versions.

Hello Jan,

dmctop does not check the db2level (instance level), it checks the database level.

Can you please run the following command, and see if your database level is the same as your instance level:

db2 "select versionnumber from sysibm.sysversions order by 1 desc"

If they are not the same, you will need to run the db2updv111 command as described in the Db2 manual at:

https://www.ibm.com/docs/en/db2/11.1?topic=sc-db2updv111-update-database-version-111-fix-pack-command

The reason that we check the database level is because dmctop uses internal Db2 APIs, and if they are not on the correct level, Db2 returns SQLCODE=-206 "<column_name> is not valid in the context where it is used." error, and dmctop can't get the information from Db2.

I hope that helps!

Is there a way to override this check in dmctop (version 1.0.4.1):

level=error msg=DbConfig error="DB version ******** not supported"

Dmctop documentation states that dmctop supports Db2 11.1 and above. Masked by me field in a/m is definitely above 11.1 :-)

Hello Jan,
Are you using dmctop to monitor z/OS databases?
dmctop only supports LUW databases, just like DMC, we don't monitor z/OS databases.
I hope that answers your question.

I will repeat my question: when DMCTop will recognize Db2 LUW V12.1.0.o or later?

Are we waiting for Db2 LUV V13.1.0.0?

Thanks Jan for the information. 

May you pls open a case against Data Management Console to let team do further investigation on this issue?

Indeed version of database = version of instance and both are higher than 11.1:

time="2023-02-18T05:55:57.277671Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=babba900-8ab6-4cda-baf2-4fc162f1b076
time="2023-02-18T05:56:24.565631Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.271955Z" level=info msg=DbUtils event=Information info="Setting DB Connection Info" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.271955Z" level=info msg=DbUtils event=Information info="Connecting to DB" moreInfo=";25000;sample;db2admin" trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.940927Z" level=info msg=DbUtils event=Information info="Connected to DB" moreInfo=";25000;sample;db2admin" trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.940927Z" level=info msg=ConfigUtils event=Information info="Initializing DB config" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:36.267717Z" level=error msg=DbConfig error="DB version 12010000 not supported" event="Encountered exception" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586

Hello Jan,

Yes, dmctop supports Db2 11.1 or higher, as long as your APIs are on the same instance level:

https://www.ibm.com/docs/en/db2-data-mgr-console/3.1.x?topic=monitoring-utility-dmctop

If you still have problems with it, please create a case with Db2 Data Management Console support team for further investigation.

Thanks!

Indeed my database version number is higher than 11.1 ...

I was suspecting that Db2 API's play a role - I was assuming that "supporting version 11.1 and above will allow dmctop to be executed on higher database versions.

Hello Jan,

dmctop does not check the db2level (instance level), it checks the database level.

Can you please run the following command, and see if your database level is the same as your instance level:

db2 "select versionnumber from sysibm.sysversions order by 1 desc"

If they are not the same, you will need to run the db2updv111 command as described in the Db2 manual at:

https://www.ibm.com/docs/en/db2/11.1?topic=sc-db2updv111-update-database-version-111-fix-pack-command

The reason that we check the database level is because dmctop uses internal Db2 APIs, and if they are not on the correct level, Db2 returns SQLCODE=-206 "<column_name> is not valid in the context where it is used." error, and dmctop can't get the information from Db2.

I hope that helps!

Is there a way to override this check in dmctop (version 1.0.4.1):

level=error msg=DbConfig error="DB version ******** not supported"

Dmctop documentation states that dmctop supports Db2 11.1 and above. Masked by me field in a/m is definitely above 11.1 :-)

As I stated several times in this thread - I am using Db2 for LUW (Linux, Unix and Windows).

What I am asking is when restriction of using Db2 for LUW (Linux, Unix and Windows) version > "11010000" be lifted?

time="2023-05-11T15:45:34.837905Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad
time="2023-05-11T15:45:34.838907Z" level=info msg=DbUtils event=Information info="Setting DB Connection Info" moreInfo= trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad
time="2023-05-11T15:45:34.838907Z" level=info msg=DbUtils event=Information info="Connecting to DB" moreInfo=";25000;sample;db2admin" trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad
time="2023-05-11T15:45:35.634904Z" level=info msg=DbUtils event=Information info="Connected to DB" moreInfo=";25000;sample;db2admin" trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad
time="2023-05-11T15:45:35.634904Z" level=info msg=ConfigUtils event=Information info="Initializing DB config" moreInfo= trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad
time="2023-05-11T15:45:35.634904Z" level=info msg=ConfigUtils event=Information info="Retriving DB config" moreInfo= trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad
time="2023-05-11T15:45:35.965010Z" level=error msg=DbConfig error="DB version 12010000 not supported" event="Encountered exception" moreInfo= trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad

Hello Jan,
Are you using dmctop to monitor z/OS databases?
dmctop only supports LUW databases, just like DMC, we don't monitor z/OS databases.
I hope that answers your question.

I will repeat my question: when DMCTop will recognize Db2 LUW V12.1.0.o or later?

Are we waiting for Db2 LUV V13.1.0.0?

Thanks Jan for the information. 

May you pls open a case against Data Management Console to let team do further investigation on this issue?

Indeed version of database = version of instance and both are higher than 11.1:

time="2023-02-18T05:55:57.277671Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=babba900-8ab6-4cda-baf2-4fc162f1b076
time="2023-02-18T05:56:24.565631Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.271955Z" level=info msg=DbUtils event=Information info="Setting DB Connection Info" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.271955Z" level=info msg=DbUtils event=Information info="Connecting to DB" moreInfo=";25000;sample;db2admin" trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.940927Z" level=info msg=DbUtils event=Information info="Connected to DB" moreInfo=";25000;sample;db2admin" trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.940927Z" level=info msg=ConfigUtils event=Information info="Initializing DB config" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:36.267717Z" level=error msg=DbConfig error="DB version 12010000 not supported" event="Encountered exception" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586

Hello Jan,

Yes, dmctop supports Db2 11.1 or higher, as long as your APIs are on the same instance level:

https://www.ibm.com/docs/en/db2-data-mgr-console/3.1.x?topic=monitoring-utility-dmctop

If you still have problems with it, please create a case with Db2 Data Management Console support team for further investigation.

Thanks!

Indeed my database version number is higher than 11.1 ...

I was suspecting that Db2 API's play a role - I was assuming that "supporting version 11.1 and above will allow dmctop to be executed on higher database versions.

Hello Jan,

dmctop does not check the db2level (instance level), it checks the database level.

Can you please run the following command, and see if your database level is the same as your instance level:

db2 "select versionnumber from sysibm.sysversions order by 1 desc"

If they are not the same, you will need to run the db2updv111 command as described in the Db2 manual at:

https://www.ibm.com/docs/en/db2/11.1?topic=sc-db2updv111-update-database-version-111-fix-pack-command

The reason that we check the database level is because dmctop uses internal Db2 APIs, and if they are not on the correct level, Db2 returns SQLCODE=-206 "<column_name> is not valid in the context where it is used." error, and dmctop can't get the information from Db2.

I hope that helps!

Is there a way to override this check in dmctop (version 1.0.4.1):

level=error msg=DbConfig error="DB version ******** not supported"

Dmctop documentation states that dmctop supports Db2 11.1 and above. Masked by me field in a/m is definitely above 11.1 :-)

Hello Jan,
Can you please open a case with support as suggested by Su Li, so we can investigate the issue?
I will need to get a developer involved for that.
Here is the link to create a case: 
https://www.ibm.com/mysupport/s/?language=en_US

As I stated several times in this thread - I am using Db2 for LUW (Linux, Unix and Windows).

What I am asking is when restriction of using Db2 for LUW (Linux, Unix and Windows) version > "11010000" be lifted?

time="2023-05-11T15:45:34.837905Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad
time="2023-05-11T15:45:34.838907Z" level=info msg=DbUtils event=Information info="Setting DB Connection Info" moreInfo= trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad
time="2023-05-11T15:45:34.838907Z" level=info msg=DbUtils event=Information info="Connecting to DB" moreInfo=";25000;sample;db2admin" trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad
time="2023-05-11T15:45:35.634904Z" level=info msg=DbUtils event=Information info="Connected to DB" moreInfo=";25000;sample;db2admin" trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad
time="2023-05-11T15:45:35.634904Z" level=info msg=ConfigUtils event=Information info="Initializing DB config" moreInfo= trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad
time="2023-05-11T15:45:35.634904Z" level=info msg=ConfigUtils event=Information info="Retriving DB config" moreInfo= trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad
time="2023-05-11T15:45:35.965010Z" level=error msg=DbConfig error="DB version 12010000 not supported" event="Encountered exception" moreInfo= trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad

Hello Jan,
Are you using dmctop to monitor z/OS databases?
dmctop only supports LUW databases, just like DMC, we don't monitor z/OS databases.
I hope that answers your question.

I will repeat my question: when DMCTop will recognize Db2 LUW V12.1.0.o or later?

Are we waiting for Db2 LUV V13.1.0.0?

Thanks Jan for the information. 

May you pls open a case against Data Management Console to let team do further investigation on this issue?

Indeed version of database = version of instance and both are higher than 11.1:

time="2023-02-18T05:55:57.277671Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=babba900-8ab6-4cda-baf2-4fc162f1b076
time="2023-02-18T05:56:24.565631Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.271955Z" level=info msg=DbUtils event=Information info="Setting DB Connection Info" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.271955Z" level=info msg=DbUtils event=Information info="Connecting to DB" moreInfo=";25000;sample;db2admin" trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.940927Z" level=info msg=DbUtils event=Information info="Connected to DB" moreInfo=";25000;sample;db2admin" trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.940927Z" level=info msg=ConfigUtils event=Information info="Initializing DB config" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:36.267717Z" level=error msg=DbConfig error="DB version 12010000 not supported" event="Encountered exception" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586

Hello Jan,

Yes, dmctop supports Db2 11.1 or higher, as long as your APIs are on the same instance level:

https://www.ibm.com/docs/en/db2-data-mgr-console/3.1.x?topic=monitoring-utility-dmctop

If you still have problems with it, please create a case with Db2 Data Management Console support team for further investigation.

Thanks!

Indeed my database version number is higher than 11.1 ...

I was suspecting that Db2 API's play a role - I was assuming that "supporting version 11.1 and above will allow dmctop to be executed on higher database versions.

Hello Jan,

dmctop does not check the db2level (instance level), it checks the database level.

Can you please run the following command, and see if your database level is the same as your instance level:

db2 "select versionnumber from sysibm.sysversions order by 1 desc"

If they are not the same, you will need to run the db2updv111 command as described in the Db2 manual at:

https://www.ibm.com/docs/en/db2/11.1?topic=sc-db2updv111-update-database-version-111-fix-pack-command

The reason that we check the database level is because dmctop uses internal Db2 APIs, and if they are not on the correct level, Db2 returns SQLCODE=-206 "<column_name> is not valid in the context where it is used." error, and dmctop can't get the information from Db2.

I hope that helps!

Is there a way to override this check in dmctop (version 1.0.4.1):

level=error msg=DbConfig error="DB version ******** not supported"

Dmctop documentation states that dmctop supports Db2 11.1 and above. Masked by me field in a/m is definitely above 11.1 :-)

I do not have customer number - what would you like me to put instead?

Hello Jan,
Can you please open a case with support as suggested by Su Li, so we can investigate the issue?
I will need to get a developer involved for that.
Here is the link to create a case: 
https://www.ibm.com/mysupport/s/?language=en_US

As I stated several times in this thread - I am using Db2 for LUW (Linux, Unix and Windows).

What I am asking is when restriction of using Db2 for LUW (Linux, Unix and Windows) version > "11010000" be lifted?

time="2023-05-11T15:45:34.837905Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad
time="2023-05-11T15:45:34.838907Z" level=info msg=DbUtils event=Information info="Setting DB Connection Info" moreInfo= trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad
time="2023-05-11T15:45:34.838907Z" level=info msg=DbUtils event=Information info="Connecting to DB" moreInfo=";25000;sample;db2admin" trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad
time="2023-05-11T15:45:35.634904Z" level=info msg=DbUtils event=Information info="Connected to DB" moreInfo=";25000;sample;db2admin" trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad
time="2023-05-11T15:45:35.634904Z" level=info msg=ConfigUtils event=Information info="Initializing DB config" moreInfo= trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad
time="2023-05-11T15:45:35.634904Z" level=info msg=ConfigUtils event=Information info="Retriving DB config" moreInfo= trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad
time="2023-05-11T15:45:35.965010Z" level=error msg=DbConfig error="DB version 12010000 not supported" event="Encountered exception" moreInfo= trace=a1848be8-366d-4aa3-bb75-c16175d7f3ad

Hello Jan,
Are you using dmctop to monitor z/OS databases?
dmctop only supports LUW databases, just like DMC, we don't monitor z/OS databases.
I hope that answers your question.

I will repeat my question: when DMCTop will recognize Db2 LUW V12.1.0.o or later?

Are we waiting for Db2 LUV V13.1.0.0?

Thanks Jan for the information. 

May you pls open a case against Data Management Console to let team do further investigation on this issue?

Indeed version of database = version of instance and both are higher than 11.1:

time="2023-02-18T05:55:57.277671Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=babba900-8ab6-4cda-baf2-4fc162f1b076
time="2023-02-18T05:56:24.565631Z" level=info msg=ConfigUtils event=Information info="*************Initializing dmctop*************" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.271955Z" level=info msg=DbUtils event=Information info="Setting DB Connection Info" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.271955Z" level=info msg=DbUtils event=Information info="Connecting to DB" moreInfo=";25000;sample;db2admin" trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.940927Z" level=info msg=DbUtils event=Information info="Connected to DB" moreInfo=";25000;sample;db2admin" trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:35.940927Z" level=info msg=ConfigUtils event=Information info="Initializing DB config" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586
time="2023-02-18T05:56:36.267717Z" level=error msg=DbConfig error="DB version 12010000 not supported" event="Encountered exception" moreInfo= trace=0354e83b-3f5a-4900-9f3f-c8430b89f586

Hello Jan,

Yes, dmctop supports Db2 11.1 or higher, as long as your APIs are on the same instance level:

https://www.ibm.com/docs/en/db2-data-mgr-console/3.1.x?topic=monitoring-utility-dmctop

If you still have problems with it, please create a case with Db2 Data Management Console support team for further investigation.

Thanks!

Indeed my database version number is higher than 11.1 ...

I was suspecting that Db2 API's play a role - I was assuming that "supporting version 11.1 and above will allow dmctop to be executed on higher database versions.

Hello Jan,

dmctop does not check the db2level (instance level), it checks the database level.

Can you please run the following command, and see if your database level is the same as your instance level:

db2 "select versionnumber from sysibm.sysversions order by 1 desc"

If they are not the same, you will need to run the db2updv111 command as described in the Db2 manual at:

https://www.ibm.com/docs/en/db2/11.1?topic=sc-db2updv111-update-database-version-111-fix-pack-command

The reason that we check the database level is because dmctop uses internal Db2 APIs, and if they are not on the correct level, Db2 returns SQLCODE=-206 "<column_name> is not valid in the context where it is used." error, and dmctop can't get the information from Db2.

I hope that helps!

Is there a way to override this check in dmctop (version 1.0.4.1):

level=error msg=DbConfig error="DB version ******** not supported"

Dmctop documentation states that dmctop supports Db2 11.1 and above. Masked by me field in a/m is definitely above 11.1 :-)