ORA-01017: invalid username/password; logon denied

Hello everyone,

 

We're suddenly getting this error now on a few oracle database jobs in DP(but others are ok) that have been working for years.  I checked and verified the username/password and they are still ok so that is not the issue yet DP thinks it is.  Any ideas on how to fix this? 

 

Thanks in advance for your time!

Dave

 

The database reported error while performing requested operation.
SBT_LIBRARY=/opt/omni/lib/libob2oracle8_64bit.so
CHILDERROR:1
Process exit code: 1, Signal: 0
RMAN PID=22529
APPERROR:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-01017: invalid username/password; logon denied
Recovery Manager complete.

Tags:

Parents
  • i also had same problem data invalid username and password so i follow this solution and its work for me :)

  • Dears,

     

    Just to update you .

     

    I have got similar problem and solution to that was oracle account using for DP integration didnt have sysdba prvillege . The was the reason using oracle user name and password in SQL promt worked but util_oracle8.pl failed with same credntial, because util_oracle8.pl uses user names as sysdba when connecting.

     

    summary 

    1) Make sure  DP integration oracle account has sydba prvilege  ( from 12C I beleive Oracle introduced sysbackup privillege to avoid granting sysdba for backup)

     

    2)Double check Oracle_Home , Oracle_SID

     

    Sincere Regards,

    Aneesh

  • Just to add to what Dineesh said, when we get this error, we have you run, on the Oracle server

     

       sqlplus /nolog

       connect username/password@service as sysdba

     

    'service' may, or may not be the name of the instance.  It can be seen in the 'tnsnames.ora' file

     

    This is how Data Protector trie to log into Oracle, so if the command fails the integration is not going to work

  • Just to add to what Dineesh said, when we get this error, we have you run, on the Oracle server

     

       sqlplus /nolog

       connect username/password@service as sysdba

     

    'service' may, or may not be the name of the instance.  It can be seen in the 'tnsnames.ora' file

     

    This is how Data Protector trie to log into Oracle, so if the command fails the integration is not going to work

  • Just to add to what Dineesh said, when we get this error, we have you run, on the Oracle server

     

       sqlplus /nolog

       connect username/password@service as sysdba

     

    'service' may, or may not be the name of the instance.  It can be seen in the 'tnsnames.ora' file

     

    This is how Data Protector trie to log into Oracle, so if the command fails the integration is not going to work

  • Folks

    This issue can be ascribed to not replicating/syncing the database password file across all nodes of a RAC cluster.

    When you grant sysdba priv to an account, it updates the local password file but that does not then replicate across to the other nodes in a RAC cluster..
    So you need to ensure all nodes receive the updated password file.

    So as an example
    DB Name = TEST
    2 Node Cluster = Host1, Host2
    2 Instances = TEST1, Test2

    Password file was orginally created with orapwd tool and the file was originally delivered to $ORACLE_HOME/dbs/orapwTEST1. This was then copied to the second node to $ORACLE_HOME/dbs/orapwTEST2.

    When the grant sysdba was given to the account, the local password file gets an entry update [for this example lets use node 1 = TEST1]
    So now you need to copy the password file across to Node 2.

    scp $ORACLE_HOME/dbs/orapwTEST1 host2:$ORACLE_HOME/dbs/orapwTEST2

    Now no matter which node the DP connects on it should be able to connect on the account that has sysdba privs.

     

    HTHs

Reply
  • Folks

    This issue can be ascribed to not replicating/syncing the database password file across all nodes of a RAC cluster.

    When you grant sysdba priv to an account, it updates the local password file but that does not then replicate across to the other nodes in a RAC cluster..
    So you need to ensure all nodes receive the updated password file.

    So as an example
    DB Name = TEST
    2 Node Cluster = Host1, Host2
    2 Instances = TEST1, Test2

    Password file was orginally created with orapwd tool and the file was originally delivered to $ORACLE_HOME/dbs/orapwTEST1. This was then copied to the second node to $ORACLE_HOME/dbs/orapwTEST2.

    When the grant sysdba was given to the account, the local password file gets an entry update [for this example lets use node 1 = TEST1]
    So now you need to copy the password file across to Node 2.

    scp $ORACLE_HOME/dbs/orapwTEST1 host2:$ORACLE_HOME/dbs/orapwTEST2

    Now no matter which node the DP connects on it should be able to connect on the account that has sysdba privs.

     

    HTHs

Children
  • All,

    Seem to have the same problem.

    current setup is as follows:

    Oracle 12c running in Oracle Failsafe 4.1 - 2 node Windows cluster with Win2008 R2.

    1. password file is created for all 9 databases.

    2. TNSPING works just fine and able to connect SUCCESSFULLY using: username/password@service_name as sysdba

    This issue, started all of a sudden, when Wintel team patched (monthly security updates) the systems and they were restarted.

    A month ago, when this issue started (again, it was also after patching activity, which typically involves restart of the servers), it was fixed, on its own (not sure how though... yep, strangely [ as we do not know the root cause])

    one point is that, the databases are currently on the same node, where they were before patching and no configuration changes have been done.

    ERROR:
    ORA-01017: invalid username/password; logon denied
    CONNECT: rman/*****@<service_name>