ANR0424W Session for node $$_TSMDBMGR_$$ refused - invalid password submitted.

[Lordriki]

Hello IBM SP specialists

I have 2 IBM SP servers (8.1.6.100) on Windows Server 2012r2, both server exhibit the same behavior:
If I restart the Spectrum Protect server (by using Halt command or any other means), the first time I'll do a DB BACKUP command I will get the following error:

"ANR0424W Session 12 for node $$_TSMDBMGR_$$ (127.0.0.1(49262)) refused - invalid password submitted.(SESSION: 12)"
The DB backup will still proceed successfully.... and after that any other DB BACKUP command will proceed successfully without any warning or error message.. Until I need to restart the Spectrum Protect server again...


I included here a copy of Q ACTLOG,

Hopefully you guys can help me and tell me if I need to worry.


Date/Time Message
-------------------- ----------------------------------------------------------
09/24/2020 14:06:37 ANR8592I Session 9 connection is using protocol TLSV12,
cipher specification TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3-
84, certificate TSM Self-Signed Certificate. (SESSION: 9)
09/24/2020 14:06:37 ANR0407I Session 9 started for administrator *********
(Windows) (SSL ). (SESSION: 9)
09/24/2020 14:06:44 ANR0405I Session 9 ended for administrator *********
(Windows). (SESSION: 9)
09/24/2020 14:06:49 ANR8592I Session 10 connection is using protocol TLSV12,
cipher specification TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3-
84, certificate TSM Self-Signed Certificate. (SESSION:
10)
09/24/2020 14:06:49 ANR0407I Session 10 started for administrator *********
(Windows) (SSL ). (SESSION: 10)
09/24/2020 14:06:49 ANR2017I Administrator ********* issued command: BACKUP DB
TYPE=FULL DEVCLASS=DBBACKUP (SESSION: 10)
09/24/2020 14:06:49 ANR0984I Process 1 for Database Backup started in the
BACKGROUND at 14:06:49. (SESSION: 10, PROCESS: 1)
09/24/2020 14:06:49 ANR4559I Backup DB is in progress. (SESSION: 10, PROCESS:
1)
09/24/2020 14:06:49 ANR2280I Full database backup started as process 1.
(SESSION: 10, PROCESS: 1)
09/24/2020 14:06:49 ANR0405I Session 10 ended for administrator *********
(Windows). (SESSION: 10)
09/24/2020 14:06:50 ANR8340I FILE volume D:\TSMDATA\MOUNT\TSM_DBBACKUP\009708-
10.DBV mounted. (SESSION: 10, PROCESS: 1)
09/24/2020 14:06:50 ANR0513I Process 1 opened output volume
D:\TSMDATA\MOUNT\TSM_DBBACKUP\00970810.DBV. (SESSION:
10, PROCESS: 1)
09/24/2020 14:06:50 ANR1360I Output volume D:\TSMDATA\MOUNT\TSM_DBBACKUP\0097-
0810.DBV opened (sequence number 1). (SESSION: 10,
PROCESS: 1)
09/24/2020 14:06:50 ANR4626I Database backup will use 1 streams for
processing with the number originally requested 1.
(SESSION: 10, PROCESS: 1)
09/24/2020 14:06:54 ANR8592I Session 11 connection is using protocol TLSV12,
cipher specification TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3-
84, certificate TSM Self-Signed Certificate. (SESSION:
11)
09/24/2020 14:06:54 ANR0407I Session 11 started for administrator *********
(Windows) (SSL ). (SESSION: 11)
09/24/2020 14:06:55 ANR0405I Session 11 ended for administrator *********
(Windows). (SESSION: 11)
09/24/2020 14:06:56 ANR0424W Session 12 for node $$_TSMDBMGR_$$
(127.0.0.1(49262)) refused - invalid password submitted.
(SESSION: 12)
09/24/2020 14:06:57 ANR8592I Session 13 connection is using protocol TLSV12,
cipher specification TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3-
84, certificate TSM Self-Signed Certificate. (SESSION:
13)
09/24/2020 14:06:57 ANR0406I Session 13 started for node $$_TSMDBMGR_$$
(DB2/NT64) (SSL 127.0.0.1:49263). (SESSION: 13)
09/24/2020 14:07:19 ANR8592I Session 14 connection is using protocol TLSV12,
cipher specification TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3-
84, certificate TSM Self-Signed Certificate. (SESSION:
14)
09/24/2020 14:07:19 ANR0407I Session 14 started for administrator *********
(Windows) (SSL ). (SESSION: 14)
09/24/2020 14:07:19 ANR8592I Session 15 connection is using protocol TLSV12,
cipher specification TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3-
84, certificate TSM Self-Signed Certificate. (SESSION:
15)
09/24/2020 14:07:19 ANR0407I Session 15 started for administrator *********
(Windows) (SSL ). (SESSION: 15)
09/24/2020 14:07:19 ANR0405I Session 14 ended for administrator *********
(Windows). (SESSION: 14)
09/24/2020 14:07:20 ANR0405I Session 15 ended for administrator *********
(Windows). (SESSION: 15)
09/24/2020 14:07:20 ANR8592I Session 16 connection is using protocol TLSV12,
cipher specification TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3-
84, certificate TSM Self-Signed Certificate. (SESSION:
16)
09/24/2020 14:07:20 ANR0407I Session 16 started for administrator *********
(Windows) (SSL 10.8.38.198:49951). (SESSION: 16)
09/24/2020 14:07:21 ANR0405I Session 16 ended for administrator *********
(Windows). (SESSION: 16)
09/24/2020 14:07:38 ANR8592I Session 17 connection is using protocol TLSV12,
cipher specification TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3-
84, certificate TSM Self-Signed Certificate. (SESSION:
17)
09/24/2020 14:07:38 ANR0407I Session 17 started for administrator *********
(Windows) (SSL ). (SESSION: 17)
09/24/2020 14:07:38 ANR2017I Administrator ********* issued command: QUERY
SESSION (SESSION: 17)
09/24/2020 14:07:38 ANR0405I Session 17 ended for administrator *********
(Windows). (SESSION: 17)
09/24/2020 14:07:51 ANR8592I Session 18 connection is using protocol TLSV12,
cipher specification TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3-
84, certificate TSM Self-Signed Certificate. (SESSION:
18)
09/24/2020 14:07:51 ANR0407I Session 18 started for administrator *********
(Windows) (SSL 10.8.38.198:49955). (SESSION: 18)
09/24/2020 14:07:54 ANR0405I Session 18 ended for administrator *********
(Windows). (SESSION: 18)
09/24/2020 14:07:59 ANR8592I Session 19 connection is using protocol TLSV12,
cipher specification TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3-
84, certificate TSM Self-Signed Certificate. (SESSION:
19)
09/24/2020 14:07:59 ANR0407I Session 19 started for administrator *********
(Windows) (SSL ). (SESSION: 19)
09/24/2020 14:08:00 ANR0405I Session 19 ended for administrator *********
(Windows). (SESSION: 19)
09/24/2020 14:08:00 ANR8592I Session 20 connection is using protocol TLSV12,
cipher specification TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3-
84, certificate TSM Self-Signed Certificate. (SESSION:
20)
09/24/2020 14:08:00 ANR0407I Session 20 started for administrator *********
(Windows) (SSL ). (SESSION: 20)
09/24/2020 14:08:01 ANR0405I Session 20 ended for administrator *********
(Windows). (SESSION: 20)
09/24/2020 14:08:24 ANR8592I Session 21 connection is using protocol TLSV12,
cipher specification TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3-
84, certificate TSM Self-Signed Certificate. (SESSION:
21)
09/24/2020 14:08:24 ANR0407I Session 21 started for administrator *********
(Windows) (SSL ). (SESSION: 21)
09/24/2020 14:08:25 ANR0405I Session 21 ended for administrator *********
(Windows). (SESSION: 21)
09/24/2020 14:08:34 ANR0403I Session 13 ended for node $$_TSMDBMGR_$$
(DB2/NT64). (SESSION: 13)
09/24/2020 14:08:39 ANR8592I Session 22 connection is using protocol TLSV12,
cipher specification TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3-
84, certificate TSM Self-Signed Certificate. (SESSION:
22)
09/24/2020 14:08:39 ANR0406I Session 22 started for node $$_TSMDBMGR_$$
(DB2/NT64) (SSL 127.0.0.1:49273). (SESSION: 22)
09/24/2020 14:08:40 ANR1361I Output volume D:\TSMDATA\MOUNT\TSM_DBBACKUP\0097-
0810.DBV closed. (SESSION: 22)
09/24/2020 14:08:40 ANR0514I Session 22 closed volume
D:\TSMDATA\MOUNT\TSM_DBBACKUP\00970810.DBV. (SESSION: 22)
09/24/2020 14:08:40 ANR0403I Session 22 ended for node $$_TSMDBMGR_$$
(DB2/NT64). (SESSION: 22)
09/24/2020 14:08:46 ANR8592I Session 23 connection is using protocol TLSV12,
cipher specification TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3-
84, certificate TSM Self-Signed Certificate. (SESSION:
23)
09/24/2020 14:08:46 ANR0406I Session 23 started for node $$_TSMDBMGR_$$
(DB2/NT64) (SSL 127.0.0.1:49274). (SESSION: 23)
09/24/2020 14:08:46 ANR0403I Session 23 ended for node $$_TSMDBMGR_$$
(DB2/NT64). (SESSION: 23)
09/24/2020 14:08:46 ANR4550I Full database backup (process 1) completed.
Total bytes backed up: 46,769,897,472. (SESSION: 10,
PROCESS: 1)
09/24/2020 14:08:56 ANR8592I Session 24 connection is using protocol TLSV12,
cipher specification TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA3-
84, certificate TSM Self-Signed Certificate. (SESSION:
24)
09/24/2020 14:08:56 ANR0407I Session 24 started for administrator *********
(Windows) (SSL ). (SESSION: 24)
09/24/2020 14:08:59 ANR0405I Session 24 ended for administrator *********
(Windows). (SESSION: 24)

 

[AngeloDeAngelis]

open a case for this - this is something we need to look at...
pull the db2diag file and see what db2 is complaining about and possible sense code error.
open a case with support.

 

[arakenmaccioly]

Hi, I know my by-pass is ugly...
If you remove the folder "C:\ProgramData\Tivoli\TSM\baclient\Nodes\$$_TSMDBMGR_$$" before, the backup of DB is proceed successfully.
First of all I have a node SERVER_ITSM (server prompt schedule style).
I made I server script:
- DEF CLIENTACT SERVER_ITSM ACT=C OBJ="a script wich removes the folder" WAIT=YES
- BACKUP DB

 

[Lordriki]

Hi, I know my by-pass is ugly...
If you remove the folder "C:\ProgramData\Tivoli\TSM\baclient\Nodes\$$_TSMDBMGR_$$" before, the backup of DB is proceed successfully.
First of all I have a node SERVER_ITSM (server prompt schedule style).
I made I server script:
- DEF CLIENTACT SERVER_ITSM ACT=C OBJ="a script wich removes the folder" WAIT=YES
- BACKUP DB

Just a quick question, you also got the same warning messages I got and you fixed the problem with this script?

 

[arakenmaccioly]

Yes. Try first:
- remove the folder "C:\ProgramData\Tivoli\TSM\baclient\Nodes\$$_TSMDBMGR_$$"
- Make a backup (expect to be ok)
- remove again the folder
- Make a new backup

 

[RecoveryOne]

I'd recommend opening a case with support. There is something going on with your instances. The database is not something you want to be playing around with in my opinion.

 

[arakenmaccioly]

I'd recommend opening a case with support. There is something going on with your instances. The database is not something you want to be playing around with in my opinion.

I agree with you. It is only a bypass to make a backup without halt. Not to live with that.

 

[Lordriki]

You guys have convinced me, I will open a case with IBM , see what fix they have for that problem. I will keep you guys posted.

Thanks for your help!

 

[marcinek]

Hi! It seems I've just hit the same issue but upon the restore of the database... @Lordriki did you managed to solve it with IBM support ?