DB version: 19c
OS : RHEL 8.4
I have a 2-node RAC DB as primary and a standalone DB as standby. Standalone standby DB uses ASM (Oracle Restart) too.
Following the advice in MOS Doc 2452286.1, I used the following ALTER USER command in primary to change SYS user's password. ie., I didn't use orapwd utility for this
ALTER USER SYS IDENTIFIED BY Kmsp#crv592 CONTAINER = ALL;
After the password change, I did the following connection tests to both primary and standby and the below tests went fine
Connecting to sys in primary
sqlplus sys/Kmsp#crv592@cl28-scan.domain.net:1528/cdb_28p.domain.net as sysdba
Connecting to sys in standby
sqlplus sys/Kmsp#crv592@msnahprd83.domain.net:1521/cdb_28ps.domain.net as sysdba
After the password change, I did few log switches and log shipping and the redo applying at standby seem to be working fine. There are no gaps.
Question1.
Would the password change using ALTER USER from SQL*Plus get propagated to the password files in primary and standby ?
Question2.
Password files for both primary and standby are stored in ASM in my case (not in $ORACLE_HOME/dbs). Even after changing the password using ALTER USER command, the timestamp of the password file hasn't changed. Any idea why ? Or am I looking at the wrong place in ASM diskgroup hierarchy or something ?
ASMCMD> pwd
+DATA_DG/CDB_28P/PASSWORD
ASMCMD>
ASMCMD> ls -l
Type Redund Striped Time Sys Name
PASSWORD UNPROT COARSE OCT 09 2022 Y pwdCDB_28P.256.1085383953
Question3.
Is there a way I can verify if the password change got reflected in the password files too ? I know the password file will be used initially for authentication when the standby DB is being built. But, on a functioning dataguard environment, I don't know how to verify this.