Hello,
We recently upgraded ILMT from 9.2.3 to 9.2.31. Upgrade completed successfully with no issues.
Logged into the ILMT UI the next morning and there was an error that the db2 password had expired.
Checked the tema.log and verified the error on the db2 (v11.5) password expiration
Stopped the LMT services
Updated the password successfully.
Verified the db2 db is running
Started the LMT services
Verified the user for the db, db2inst1, and connected without issue using the new password
Checked the database.yml and system.xml files to make sure the encrypted password was the same. It is.
Opened the ILMT UI but it just keeps spinning
Checked the tema.log again and seeing the following error repeating every 60 seconds:
"Servlet Message - [tema]:.[ERROR] Cannot connect to the database: Java::ComIbmDb2JccAm::SqlInvalidAuthorizationSpecException: [jcc][t4][2013][11249][4.28.11] Connection authorization failure occurred. Reason: User ID or Password invalid. ERRORCODE=-4214, SQLSTATE=28000.
The next try for 60 seconds."
What other checks should I be performing?
Thank You,
George
------------------------------
George Wardner
------------------------------
Hello
George,
There are some unknowns here:
1) What Upgrade path was used ?
A direct Upgrade from 9.2.3 to 9.2.31 can't be done without intermediate installers (https://www.ibm.com/docs/en/license-metric-tool?topic=tool-upgrading-latest-version)
2) Which database user's password update procedure on ILMT side have you conducted ?
3) There is no such thing as '
system.xml
'...did you mean '
server.xml
' ?
At last,
Please make sure to run the
SetupDatabase
script (
https://www.ibm.com/docs/en/license-metric-tool?topic=database-changing-connection-parameters
) to update database user's password.
The biggest advantage of this script is that it allows to verify the new user's password against database engine before updating
server.xml/database.yml
files.
Oktawian Powązka, L3 Support
IBM License Metric Tool
------------------------------
Original Message
Original Message:
Sent: Thu May 18, 2023 04:02 PM
From: George Wardner
Subject: Upgrade from ILMT 9.2.3 to 9.2.31 - Invalid Username
Hello,
We recently upgraded ILMT from 9.2.3 to 9.2.31. Upgrade completed successfully with no issues.
Logged into the ILMT UI the next morning and there was an error that the db2 password had expired.
Checked the tema.log and verified the error on the db2 (v11.5) password expiration
Stopped the LMT services
Updated the password successfully.
Verified the db2 db is running
Started the LMT services
Verified the user for the db, db2inst1, and connected without issue using the new password
Checked the database.yml and system.xml files to make sure the encrypted password was the same. It is.
Opened the ILMT UI but it just keeps spinning
Checked the tema.log again and seeing the following error repeating every 60 seconds:
"Servlet Message - [tema]:.[ERROR] Cannot connect to the database: Java::ComIbmDb2JccAm::SqlInvalidAuthorizationSpecException: [jcc][t4][2013][11249][4.28.11] Connection authorization failure occurred. Reason: User ID or Password invalid. ERRORCODE=-4214, SQLSTATE=28000.
The next try for 60 seconds."
What other checks should I be performing?
Thank You,
George
------------------------------
George Wardner
------------------------------
Hi Oktawian,
Per my original post the upgrade from 9.2.30 to 9.2.31 worked fine. Was able to login to the UI after the upgrade and run the Data Import with no issue.
1) According to the documentation there were no intermediary steps needed for this upgrade:
"For application updates between
9.2.23
and
9.2.30
, upgrade directly to application update
9.2.31"
2) su to db2inst1, prompted to change password, changed password
Also, using the service account (non-root), ran the SetupDatabase.sh, applied the defaults but entered in the new password. Updated the connection per prompt and restarted the LMT services per prompt
3) Yes, server.xml. Not system.xml
I'm wondering if maybe we should have used the 'root' account to apply the password changes?
Thank You,
George
------------------------------
George Wardner
------------------------------
Original Message
Original Message:
Sent: Fri May 19, 2023 02:18 AM
From: Oktawian Powązka
Subject: Upgrade from ILMT 9.2.3 to 9.2.31 - Invalid Username
Hello
George,
There are some unknowns here:
1) What Upgrade path was used ?
A direct Upgrade from 9.2.3 to 9.2.31 can't be done without intermediate installers (https://www.ibm.com/docs/en/license-metric-tool?topic=tool-upgrading-latest-version)
2) Which database user's password update procedure on ILMT side have you conducted ?
3) There is no such thing as '
system.xml
'...did you mean '
server.xml
' ?
At last,
Please make sure to run the
SetupDatabase
script (
https://www.ibm.com/docs/en/license-metric-tool?topic=database-changing-connection-parameters
) to update database user's password.
The biggest advantage of this script is that it allows to verify the new user's password against database engine before updating
server.xml/database.yml
files.
Oktawian Powązka, L3 Support
IBM License Metric Tool
Original Message:
Sent: Thu May 18, 2023 04:02 PM
From: George Wardner
Subject: Upgrade from ILMT 9.2.3 to 9.2.31 - Invalid Username
Hello,
We recently upgraded ILMT from 9.2.3 to 9.2.31. Upgrade completed successfully with no issues.
Logged into the ILMT UI the next morning and there was an error that the db2 password had expired.
Checked the tema.log and verified the error on the db2 (v11.5) password expiration
Stopped the LMT services
Updated the password successfully.
Verified the db2 db is running
Started the LMT services
Verified the user for the db, db2inst1, and connected without issue using the new password
Checked the database.yml and system.xml files to make sure the encrypted password was the same. It is.
Opened the ILMT UI but it just keeps spinning
Checked the tema.log again and seeing the following error repeating every 60 seconds:
"Servlet Message - [tema]:.[ERROR] Cannot connect to the database: Java::ComIbmDb2JccAm::SqlInvalidAuthorizationSpecException: [jcc][t4][2013][11249][4.28.11] Connection authorization failure occurred. Reason: User ID or Password invalid. ERRORCODE=-4214, SQLSTATE=28000.
The next try for 60 seconds."
What other checks should I be performing?
Thank You,
George
------------------------------
George Wardner
------------------------------
Hello George,
Well, in your original post it says '
We recently upgraded ILMT from
9.2.3 to 9.2.31
...
'
Anyhow, at least that part is clear and we got a supported upgrade scenario.
If
SetupDatabase.sh
script hasn't spit out any errors it would suggest that the whole procedure was conducted properly.
I'd suggest to open up the support ticket and upload
server.xml/database.yml
files + output/screenshot from the
SetupDatabase.sh
script session....
Oktawian Powązka, L3 Support
IBM License Metric Tool
------------------------------
Original Message
Original Message:
Sent: Fri May 19, 2023 10:47 AM
From: George Wardner
Subject: Upgrade from ILMT 9.2.3 to 9.2.31 - Invalid Username
Hi Oktawian,
Per my original post the upgrade from 9.2.30 to 9.2.31 worked fine. Was able to login to the UI after the upgrade and run the Data Import with no issue.
1) According to the documentation there were no intermediary steps needed for this upgrade:
"For application updates between
9.2.23
and
9.2.30
, upgrade directly to application update
9.2.31"
2) su to db2inst1, prompted to change password, changed password
Also, using the service account (non-root), ran the SetupDatabase.sh, applied the defaults but entered in the new password. Updated the connection per prompt and restarted the LMT services per prompt
3) Yes, server.xml. Not system.xml
I'm wondering if maybe we should have used the 'root' account to apply the password changes?
Thank You,
George
------------------------------
George Wardner
Original Message:
Sent: Fri May 19, 2023 02:18 AM
From: Oktawian Powązka
Subject: Upgrade from ILMT 9.2.3 to 9.2.31 - Invalid Username
Hello
George,
There are some unknowns here:
1) What Upgrade path was used ?
A direct Upgrade from 9.2.3 to 9.2.31 can't be done without intermediate installers (https://www.ibm.com/docs/en/license-metric-tool?topic=tool-upgrading-latest-version)
2) Which database user's password update procedure on ILMT side have you conducted ?
3) There is no such thing as '
system.xml
'...did you mean '
server.xml
' ?
At last,
Please make sure to run the
SetupDatabase
script (
https://www.ibm.com/docs/en/license-metric-tool?topic=database-changing-connection-parameters
) to update database user's password.
The biggest advantage of this script is that it allows to verify the new user's password against database engine before updating
server.xml/database.yml
files.
Oktawian Powązka, L3 Support
IBM License Metric Tool
Original Message:
Sent: Thu May 18, 2023 04:02 PM
From: George Wardner
Subject: Upgrade from ILMT 9.2.3 to 9.2.31 - Invalid Username
Hello,
We recently upgraded ILMT from 9.2.3 to 9.2.31. Upgrade completed successfully with no issues.
Logged into the ILMT UI the next morning and there was an error that the db2 password had expired.
Checked the tema.log and verified the error on the db2 (v11.5) password expiration
Stopped the LMT services
Updated the password successfully.
Verified the db2 db is running
Started the LMT services
Verified the user for the db, db2inst1, and connected without issue using the new password
Checked the database.yml and system.xml files to make sure the encrypted password was the same. It is.
Opened the ILMT UI but it just keeps spinning
Checked the tema.log again and seeing the following error repeating every 60 seconds:
"Servlet Message - [tema]:.[ERROR] Cannot connect to the database: Java::ComIbmDb2JccAm::SqlInvalidAuthorizationSpecException: [jcc][t4][2013][11249][4.28.11] Connection authorization failure occurred. Reason: User ID or Password invalid. ERRORCODE=-4214, SQLSTATE=28000.
The next try for 60 seconds."
What other checks should I be performing?
Thank You,
George
------------------------------
George Wardner
------------------------------
Hi
Oktawian,
I opened a support case for this issue. However, by chance I shut down the services again and left it down over the weekend. When I brought up the services this morning everything magically worked. I was able to login to the UI and run the Data Import successfully.
Maybe it takes time for the db2 password change to take affect?
Anyway, all is good and ILMT is running again.
Thank You,
George
------------------------------
George Wardner
------------------------------
Original Message
Original Message:
Sent: Fri May 19, 2023 11:56 AM
From: Oktawian Powązka
Subject: Upgrade from ILMT 9.2.3 to 9.2.31 - Invalid Username
Hello George,
Well, in your original post it says '
We recently upgraded ILMT from
9.2.3 to 9.2.31
...
'
Anyhow, at least that part is clear and we got a supported upgrade scenario.
If
SetupDatabase.sh
script hasn't spit out any errors it would suggest that the whole procedure was conducted properly.
I'd suggest to open up the support ticket and upload
server.xml/database.yml
files + output/screenshot from the
SetupDatabase.sh
script session....
Oktawian Powązka, L3 Support
IBM License Metric Tool
Original Message:
Sent: Fri May 19, 2023 10:47 AM
From: George Wardner
Subject: Upgrade from ILMT 9.2.3 to 9.2.31 - Invalid Username
Hi Oktawian,
Per my original post the upgrade from 9.2.30 to 9.2.31 worked fine. Was able to login to the UI after the upgrade and run the Data Import with no issue.
1) According to the documentation there were no intermediary steps needed for this upgrade:
"For application updates between
9.2.23
and
9.2.30
, upgrade directly to application update
9.2.31"
2) su to db2inst1, prompted to change password, changed password
Also, using the service account (non-root), ran the SetupDatabase.sh, applied the defaults but entered in the new password. Updated the connection per prompt and restarted the LMT services per prompt
3) Yes, server.xml. Not system.xml
I'm wondering if maybe we should have used the 'root' account to apply the password changes?
Thank You,
George
------------------------------
George Wardner
Original Message:
Sent: Fri May 19, 2023 02:18 AM
From: Oktawian Powązka
Subject: Upgrade from ILMT 9.2.3 to 9.2.31 - Invalid Username
Hello
George,
There are some unknowns here:
1) What Upgrade path was used ?
A direct Upgrade from 9.2.3 to 9.2.31 can't be done without intermediate installers (https://www.ibm.com/docs/en/license-metric-tool?topic=tool-upgrading-latest-version)
2) Which database user's password update procedure on ILMT side have you conducted ?
3) There is no such thing as '
system.xml
'...did you mean '
server.xml
' ?
At last,
Please make sure to run the
SetupDatabase
script (
https://www.ibm.com/docs/en/license-metric-tool?topic=database-changing-connection-parameters
) to update database user's password.
The biggest advantage of this script is that it allows to verify the new user's password against database engine before updating
server.xml/database.yml
files.
Oktawian Powązka, L3 Support
IBM License Metric Tool
Original Message:
Sent: Thu May 18, 2023 04:02 PM
From: George Wardner
Subject: Upgrade from ILMT 9.2.3 to 9.2.31 - Invalid Username
Hello,
We recently upgraded ILMT from 9.2.3 to 9.2.31. Upgrade completed successfully with no issues.
Logged into the ILMT UI the next morning and there was an error that the db2 password had expired.
Checked the tema.log and verified the error on the db2 (v11.5) password expiration
Stopped the LMT services
Updated the password successfully.
Verified the db2 db is running
Started the LMT services
Verified the user for the db, db2inst1, and connected without issue using the new password
Checked the database.yml and system.xml files to make sure the encrypted password was the same. It is.
Opened the ILMT UI but it just keeps spinning
Checked the tema.log again and seeing the following error repeating every 60 seconds:
"Servlet Message - [tema]:.[ERROR] Cannot connect to the database: Java::ComIbmDb2JccAm::SqlInvalidAuthorizationSpecException: [jcc][t4][2013][11249][4.28.11] Connection authorization failure occurred. Reason: User ID or Password invalid. ERRORCODE=-4214, SQLSTATE=28000.
The next try for 60 seconds."
What other checks should I be performing?
Thank You,
George
------------------------------
George Wardner
------------------------------