Keywords

U2000 V100R006, database password, complexity, upgrade failure

Version Mapping

NMS	OS	Database	NE
Source version: U2000 V100R006C02 or earlier Target version: U2000 V100R008 or later	Solaris, Linux, Windows	-	-

 

Symptom

After a user upgrades the U2000 from V100R006 (or earlier) to V100R008 (or later), the U2000 fails to be started. According to upgrade logs, the database user dbuser failed to be created during the upgrade.

Problem Identification

This is a UExpert bug.

Cause Analysis

                               Step 1     After the database processes are successfully started, confirm that the dbuser user does not exist.

[Confirmation method on Windows OS]

1.         Open the CLI on the U2000 server.

2.         Run the following command to connect to the database:

isql -SDBSVR -Usa

Enter the password when prompted.

3.         Run the following commands to query database users:

1> select name from master..syslogins

2> go

The dbuser user is not listed.

 

4.         Close the CLI.

[Confirmation method on Solaris or Linux OS]

1.         Log in to the OS as the root user.

2.         Run the following commands to connect to the database:

su - dbuser

isql -SDBSVR -Usa

Enter the password for the sa user when prompted.

3.         Run the following commands to query database users:

1> select name from master..syslogins

2> go

The dbuser user is not listed.

4.         Log out of the OS.

                               Step 2     Query the logs recorded during the upgrade.

A failure to create dbuser was recorded.

[Confirmation method on Windows OS]

Query information in C:\ OSSENGR\upgrade\scripts\windows\ modifydbuserattr.log.

The following errors are found:

1> 2> Msg 15118, Level 16, State 1, Server NMSSERVER, Line 1

Password validity check failed. The specified password is too short according to the password policy used on Windows OS.

Msg 15007, Level 16, State 1, Server NMSSERVER, Procedure sp_addsrvrolemember, Line 68

The user name 'dbuser' is invalid or you do not have the required rights.

set password

Msg 15007, Level 16, State 1, Server NMSSERVER, Procedure sp_password, Line 29

The user name 'dbuser' is invalid or you do not have the required rights.

1> 2> Msg 15151, Level 16, State 1, Server NMSSERVER, Line 1

Cannot modify the logged-in user name "dbuser", because it does not exist or you do not have the required rights.

[Confirmation method on Solaris or Linux OS]

Query information in /var/tmp/engrlogs/install/createdbuser_hello.log. The following errors are found:

Msg 10317, Level 14, State 1:

Server 'DBSVR', Procedure 'sp_password', Line 118:

The specified password is too short. Passwords must be at least 8 character(s) long.

Msg 17720, Level 16, State 1:

Server 'DBSVR', Procedure 'sp_password', Line 128:

Error:  Unable to set the Password.

(return status = 1)

Msg 11105, Level 16, State 3:

Server 'DBSVR', Procedure 'sp_role', Line 48:

No such user/role 'dbuser’ exists.

(return status = 1)

......

Server 'DBSVR':

Login failed.

                               Step 3     Check the password for the NMSuser user on the source version.

The password is simple.

In conclusion, the dbuser user fails to be created because the source version uses a simple password for the NMSuser user whereas the complex database password policy is enabled.

----End

Affected Scope

The source version is U2000 V100R006 or earlier; the target version is U2000 V100R008 or later.

Preventive Measure

l   Before the upgrade, ask frontline engineers to check whether the database user password meets complexity requirements. If it does not meet complexity requirements (for example, the initial password Changeme_123 is in use), use the U2000 MSuite to change it.

l   If the database user password is forgotten, run the following commands to disable the complex password policy:

#isql –Usa –SDBSVR

1>sp_passwordpolicy 'clear', 'disallow simple passwords'

2>go

1>sp_passwordpolicy 'clear', 'min digits in password'

2>go

1>sp_passwordpolicy 'clear', 'min special char in password'

2>go

1>sp_passwordpolicy 'clear', 'min upper char in password'

2>go

1>sp_passwordpolicy 'clear', 'min lower char in password'

2>go

1>sp_passwordpolicy 'set', 'minimum password length', 6

2>go

Solution

Roll back the U2000 to the source version, change the database user password according to complexity requirements, and upgrade the U2000 again.

Before upgrading a single U2000 version earlier than V200R001SPC500, check it on the UEasy HealthCheck tool.

From V200R001SPC500, the U2000 begins to support the upgrade with a simple database user password.

Suggestion and Summary

None