Analysis :
There may be a mismatch in the "case" of characters between these items on the host where the auxiliary database resides:
1) The entry in the listener.ora file for service_name for the auxiliary instance.
2) The entry for db_name in the init<sid>.ora file for the auxiliary instance.
3) The naming of the password file.
4) The $ORACLE_SID for the auxiliary instance.
If all four items have matching case characters, you may find the errors connecting remotely via the password file are resolved.
Solution :
Listener example:
(DESCRIPTION=
(ADDRESS=...)
(ADDRESS=...)
(CONNECT_DATA=
(SERVICE_NAME=PROD.LOCALDOMIAN.COM)))
The init<sid>.ora file:
db_name=PROD
The password file:
orapwPROD.ora
The $ORACLE_SID:
$ ORACLE_SID=PROD; export ORACLE_SID
$ORACLE_SID and password file is must be same.
There may be a mismatch in the "case" of characters between these items on the host where the auxiliary database resides:
1) The entry in the listener.ora file for service_name for the auxiliary instance.
2) The entry for db_name in the init<sid>.ora file for the auxiliary instance.
3) The naming of the password file.
4) The $ORACLE_SID for the auxiliary instance.
If all four items have matching case characters, you may find the errors connecting remotely via the password file are resolved.
Solution :
Set the reference to service_name in the listener.ora,db_name in the init<sid>.ora,password file name itself,$ORACLE_SID to all uppercase.
Listener example:
(DESCRIPTION=
(ADDRESS=...)
(ADDRESS=...)
(CONNECT_DATA=
(SERVICE_NAME=PROD.LOCALDOMIAN.COM)))
The init<sid>.ora file:
db_name=PROD
The password file:
orapwPROD.ora
The $ORACLE_SID:
$ ORACLE_SID=PROD; export ORACLE_SID
$ORACLE_SID and password file is must be same.