Friday 24 October 2014

ORA_01017: Invalid username/password error while creating a standby database

Issue: ORA_01017: Invalid username/password error while creating a standby database

$ rman TARGET sys/change_on_install@TEST

Recovery Manager: Release 11.2.0.4.0 - Production on Fri Oct 24 15:24:44 2014

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-01017: invalid username/password; logon denied

Though I changed the passwords and recreated the password file in primary and copied back to standby server, still i received the invalid username and password on the standy

Solution:


SQL> show parameter REMOTE_LOGIN_PASSWORD

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
remote_login_passwordfile            string      NONE

SQL> show parameter REMOTE_OS_AUTHENT

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
remote_os_authent                    boolean     FALSE
SQL>


The parameter remote_login_password file should be set to exclusive. Changed the value to EXCLUSIVE in primary and restarted the database

SQL> alter system set remote_login_passwordfile='EXCLUSIVE' scope=spfile;

System altered.


SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.

Total System Global Area 2405122048 bytes
Fixed Size                  2255592 bytes
Variable Size             503317784 bytes
Database Buffers         1895825408 bytes
Redo Buffers                3723264 bytes
Database mounted.
Database opened.
SQL>

Now the rman command duplicate target database for standby works fine.

Tuesday 21 October 2014

Errors: ORA-00301, ORA-17502, ORA-15005 name is already used by an existing alias

Errors: ORA-00301, ORA-17502, ORA-15005

SQL> ALTER DATABASE ADD LOGFILE THREAD 2
 GROUP 5 ('+TEST_REDO/TEST_redo_t2g1m1',
  2    3           '+TEST_REDO/TEST_redo_t2g1m2') size 20M,
  4   GROUP 6 ('+TEST_REDO/TEST_redo_t2g2m1',
  5           '+TEST_REDO/TEST_redo_t2g2m2') size 20M,
  6   GROUP 7 ('+TEST_REDO/TEST_redo_t2g3m1',
  7           '+TEST_REDO/TEST_redo_t2g3m2') size 20M,
  8   GROUP 8 ('+TEST_REDO/TEST_redo_t2g4m1',
  9           '+TEST_REDO/TEST_redo_t2g4m2') size 20M;
ALTER DATABASE ADD LOGFILE THREAD 2
*
ERROR at line 1:
ORA-00301: error in adding log file '+TEST_REDO/TEST_redo_t2g1m1' - file cannot be created
ORA-17502: ksfdcre:4 Failed to create file +TEST_REDO/TEST_redo_t2g1m1
ORA-15005: name "TEST_redo_t2g1m1" is already used by an existing alias

The problem is because the logfile exists in the ASM disks as below

servTEST501:grid $ asmcmd
ASMCMD> cd TEST_REDO
ls
ASMCMD> TEST/
TEST_def_temp_01
TEST_redo_t1g1m1
TEST_redo_t1g1m2
TEST_redo_t1g2m1
TEST_redo_t1g2m2
TEST_redo_t1g3m1
TEST_redo_t1g3m2
TEST_redo_t1g3m3
TEST_redo_t1g3m4
TEST_redo_t1g4m1
TEST_redo_t1g4m2
TEST_redo_t2g1m1
TEST_redo_t2g1m2
TEST_redo_t2g2m1
TEST_redo_t2g2m2
TEST_redo_t2g3m1
TEST_redo_t2g3m2
TEST_redo_t2g4m1
TEST_redo_t2g4m2
TEST_temp_01
ASMCMD> rm TEST_redo_t2g1m1
ASMCMD> rm TEST_redo_t2g1m2
;
:
ASMCMD>rm TEST_redo_t2g4m2

remove the logfiles created for thread 2 in the asm and recreate the logfiles

SQL> ALTER DATABASE ADD LOGFILE THREAD 2
 GROUP 5 ('+TEST_REDO/TEST_redo_t2g1m1',
         '+TEST_REDO/TEST_redo_t2g1m2') size 20M,
  2    3    4   GROUP 6 ('+TEST_REDO/TEST_redo_t2g2m1',
  5           '+TEST_REDO/TEST_redo_t2g2m2') size 20M,
  6   GROUP 7 ('+TEST_REDO/TEST_redo_t2g3m1',
  7           '+TEST_REDO/TEST_redo_t2g3m2') size 20M,
  8   GROUP 8 ('+TEST_REDO/TEST_redo_t2g4m1',
  9           '+TEST_REDO/TEST_redo_t2g4m2') size 20M;

Database altered.

Explanation: Though we drop the logs using the sql command it is registered as dropped in the controlfile but the physical file exists which has to be removed manually.