When 19.8 GI RU is applied, you can use "asmcmd credverify" and "asmcmd credfix" to verify and fix the asm credential issue.
The asmcmd "credverify" checks to see if credentials have been created properly across a multinode cluster, and are consistent across the OCR, OLR, and password file. the asmcmd "credfix" also does the same, but the command additionally deletes inconsistent credentials and adds new ones across the OCR, OLR, and password file. It also enables flex ASM if the GPnP profile has not been changed yet.
The following is one example of how "asmcmd credverify" and "asmcmd credfix" work.
The recommended usage is "asmcmd --nocp credverify" and "asmcmd --nocp credfix" as the following example shows.
The “nocp” option is used to disable the connection feature pooling for ASMCMD. The option is being used to ensure connection pooling doesn’t affect the execution of ‘credverify’ and ‘credfix’.
There is no negative impact of using --nocp option
Starting from 20.3, the default behavior is --nocp, so starting from 20.3, "asmcmd credverify" and "asmcmd credfix" behaves same as asmcmd --nocp credverify" and "asmcmd--nocp credfix"
Case 1: If there is no credentials in OCR:
GI_HOME/bin/asmcmd --nocp credverify
credverify: No credentials in OCR, please run 'credfix' to fix the credentials.
GI_HOME/bin/asmcmd --nocp credfix
op=addcrscreds wrap=/tmp/creds0.xml
credfix: Creating new credentials, no valid credentials in OCR.
credfix: New user <username2> created.
op=credimport wrap=/tmp/creds0.xml olr=true force=true
credfix: OLR for <node1> has been fixed if credentials were created incorrectly.
credfix: Starting SSH session on node den02rrx.
credfix: OLR for <node2> has been fixed if credentials were created incorrectly.
credverify: Credentials created correctly on <node1>.
credverify: starting SSH session on node <node2>.
credverify: Credentials created correctly on <node2>. Exiting SSH session.
credfix: Credentials have been fixed if they were created incorrectly.