I tried to validate everything and it looked okay ("tnsping" worked), but I could not connect through SQL*Net at all, whether from RMAN or SQL*Plus. Local direct connections worked fine though. Eventually I managed to work out what was wrong. So in case anyone else runs into the same problem ...RMAN> connect auxiliary sys/syspassword@dgtest_stdby RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-04006: error from auxiliary database: ORA-01017: invalid username/password; logon denied
What I had originally was:
- A newly created database (using
CREATE DATABASE
the old fashioned way) - An Oracle password file created using
orapwd
with the SYS password - A listner.ora on each server defining a static service name for the database on that server
- A tnsnames.ora on each server defining the mappings of connection names to servers and services
ALTER USER SYS IDENTIFIED BY NEW_PASSWORD
- This automatically updates the
$ORACLE_HOME/dbs/ora$ORACLE_SID
password file on the server - Copy (ftp) this file over to the second, standby server
I would say that the error message is not particularly helpful, as it seems that all manner of different error conditions can give rise to the same error message. And there is almost no way of investigating this, other than trial and error - which I was getting sick of after 2 hours of getting nowhere. I knew that the underlying SQL*Net worked, as
tnsping
worked, and I knew that the Listener configurations were correct.
Eventually I simply decided to change the SYS password to be something
completely different and lo and behold I could now connect to the
primary database remotely. It then took another few minutes before I realised
that I needed to copy the Oracle password file to the standby server
again, because it had changed.
No comments:
Post a Comment