KB221993: Metadata Database User Account becomes locked during daily License Compliance Check

• Strategy

This document describes a scenario where the Database User Account associated with the Metadata may become locked during the daily License Compliance Check due to incorrect credentials being present in a Database Instance referencing the Metadata. This document explains the interaction with Database Instances during the daily License Compliance Check and documents an Enhancement Request to change this functionality in future versions of the MicroStrategy Analytics Enterprise product suite.

SUMMARY:

This document describes a scenario where the Database User Account associated with the Metadata may become locked during the daily License Compliance Check due to incorrect credentials being present in a Database Instance referencing the Metadata. This document explains the interaction with Database Instances during the daily License Compliance Check and documents an Enhancement Request to change this functionality in future versions of the Strategy Analytics Enterprise product suite.

SYMPTOM:

When the daily License Compliance check is performed, the Database User Account associated with the Metadata becomes locked. When the Database User Account associated with the Metadata becomes locked, the Strategy environment will not be able to function properly until the Database User Account is unlocked.

The following errors are seen in the DSSErrors.log on the Intelligence Server during the License Compliance Check period:


2014-10-21 12:54:00.793-05:00 [HOST:WAS-TEST][PID:10385][THR:3062827328][Kernel][Info] Server checking License compliance has the following license key: 
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
2014-10-21 12:54:00.796-05:00 [HOST:WAS-TEST][PID:10385][THR:3062827328][Kernel][Info] Server is checking Named User Licenses.
2014-10-21 12:54:07.684-05:00 [HOST:WAS-TEST][PID:10385][THR:3062827328][Kernel][Info] Server is in Named User compliance based on contract 285952.
2014-10-21 12:54:07.812-05:00 [HOST:WAS-TEST][PID:10385][THR:3062827328][Kernel][Info] Server finishes checking Named User Licenses.
2014-10-21 12:54:07.814-05:00 [HOST:WAS-TEST][PID:10385][THR:3062827328][Kernel][Info] Server checking License compliance for activation has the following license key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
2014-10-21 12:54:07.815-05:00 [HOST:WAS-TEST][PID:10385][THR:3062827328][Kernel][Info] Server is checking License Activation.
2014-10-21 12:54:19.429-05:00 [HOST:WAS-TEST][PID:10385][THR:3062827328][Database Classes][Error] Connect failed. Login failed. Error type: Odbc error. Odbc operation attempted: SQLDriverConnect. [28000:1017: on SQLHANDLE] [Strategy][ODBC Oracle Wire Protocol driver][Oracle]ORA-01017: invalid username/password; logon denied Connection String: DSN=Metadata;UID=mstr;.
.
.
.
2014-10-21 12:57:19.312-05:00 [HOST:WAS-TEST][PID:10385][THR:3298658624][Database Classes][Error] Connect failed. 
Error type: Odbc error. Odbc operation attempted: SQLDriverConnect. [HY000:28000: on SQLHANDLE] [Strategy][ODBC Oracle Wire Protocol driver][Oracle]ORA-28000: the account is locked Connection String: DSN=Metadata;UID=mstr;ENABLENCHARSUPPORT=1;ENABLEDESCRIBEPARAM=1;.

CAUSE:

As part of the daily License Compliance Check, Strategy will connect to all Database Instances contained with the Metadata. If a Database Instance is referencing the Metadata database and has incorrect credentials, it is possible for the Database User Account to become locked due to database security protocols established on the Database Server.

ACTION:

The Database User credentials should always be updated for any Data Instances referencing the Metadata database.

An Enhancement Request has been logged to change the interaction with Database Instances during daily License Compliance Checks.

Comment

0 comments

Details

Knowledge Article

Published:

April 3, 2017

Last Updated:

April 3, 2017

2014-10-21 12:54:00.793-05:00 [HOST:WAS-TEST][PID:10385][THR:3062827328][Kernel][Info] Server checking License compliance has the following license key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 2014-10-21 12:54:00.796-05:00 [HOST:WAS-TEST][PID:10385][THR:3062827328][Kernel][Info] Server is checking Named User Licenses. 2014-10-21 12:54:07.684-05:00 [HOST:WAS-TEST][PID:10385][THR:3062827328][Kernel][Info] Server is in Named User compliance based on contract 285952. 2014-10-21 12:54:07.812-05:00 [HOST:WAS-TEST][PID:10385][THR:3062827328][Kernel][Info] Server finishes checking Named User Licenses. 2014-10-21 12:54:07.814-05:00 [HOST:WAS-TEST][PID:10385][THR:3062827328][Kernel][Info] Server checking License compliance for activation has the following license key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 2014-10-21 12:54:07.815-05:00 [HOST:WAS-TEST][PID:10385][THR:3062827328][Kernel][Info] Server is checking License Activation. 2014-10-21 12:54:19.429-05:00 [HOST:WAS-TEST][PID:10385][THR:3062827328][Database Classes][Error] Connect failed. Login failed. Error type: Odbc error. Odbc operation attempted: SQLDriverConnect. [28000:1017: on SQLHANDLE] [Strategy][ODBC Oracle Wire Protocol driver][Oracle]ORA-01017: invalid username/password; logon denied Connection String: DSN=Metadata;UID=mstr;. . . . 2014-10-21 12:57:19.312-05:00 [HOST:WAS-TEST][PID:10385][THR:3298658624][Database Classes][Error] Connect failed. Error type: Odbc error. Odbc operation attempted: SQLDriverConnect. [HY000:28000: on SQLHANDLE] [Strategy][ODBC Oracle Wire Protocol driver][Oracle]ORA-28000: the account is locked Connection String: DSN=Metadata;UID=mstr;ENABLENCHARSUPPORT=1;ENABLEDESCRIBEPARAM=1;.