Blog

ORA-01017: invalid username/password; logon denied

Try to connect to 12c standby database , then get “ORA-01017” error.

$ sqlplus sys/password@TESTDBSTY as sysdba

SQL*Plus: Release 12.1.0.2.0 Production on Tue Jan 15 18:07:54 2019

Copyright (c) 1982, 2014, Oracle. All rights reserved.

ERROR:
ORA-01017: invalid username/password; logon denied

After investigation, found the listener is running by 11R2 binary, instead of 12cR1 binary.

Restart the listener in 12cR1 ORACLE_HOME, then everything is fine.

Always run listener by using the highest version of all ORACLE_HOME.

ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

Before start to create standby database by using DUPLICATE command, try to connect to  auxiliary instance:

RMAN>  connect auxiliary  sys/password@testdbsty

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-04006: error from auxiliary database: 
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
$ sqlplus sys/password@testdbsty as sysdba

SQL*Plus: Release 11.2.0.4.0 Production on Tue Jan 15 15:18:35 2019

Copyright (c) 1982, 2013, Oracle. All rights reserved.

ERROR:
ORA-12154: TNS:could not resolve the connect identifier specified

Workaround:

Add an entry in listener.ora, and then reload listener to make it effective:

SID_LIST_LISTENER =
(SID_LIST =
   (SID_DESC =
      (GLOBAL_DBNAME = TESTDBSTY)
      (SID_NAME = TESTDBSTY)
      (ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
  )
..
.
}

$lsnrctl status
Services Summary...
Service "TESTDBSTY" has 2 instance(s).
  Instance "TESTDBSTY", status UNKNOWN, has 1 handler(s) for this service...
  Instance "TESTDBSTY", status BLOCKED, has 1 handler(s) for this service...
...
.
.

ORA-17628 RMAN-03009 duplicate target database for standby from active database

While run RMAN “duplicate target database for standby from active database nofilenamecheck” in 11g database, then got below errors:

...
..
.
set newname for datafile 3 to "/u02/oradata/TESTDBSTY/undotbs01.dbf";
...
..
.
channel ORA_DISK_1: starting datafile copy
input datafile file number=00003 name=/u02/oradata/TESTDB/undotbs01.dbf
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 01/15/2019 15:53:17
ORA-17628: Oracle error 19505 returned by remote Oracle server
continuing other job steps, job failed will not be re-run
...
..
.

Subscribe to get access

Read more of this content when you subscribe today.

SQL*Net message from client

A client asked about why it takes 14.96 seconds for below sql(1):

SQL>select * from dba_tables;
Elapsed: 00:00:14.96

While it takes only 0.59 second for this sql(2):

SQL>select count(*) from dba_tables;
Elapsed: 00:00:00.59

Let’s compare the tkprof summary from sql tracing for those two sqls:

Subscribe to get access

Read more of this content when you subscribe today.

Log file switch (checkpoint incomplete)

“Log file switch (checkpoint incomplete)” waiting events are seen in v$session_wait, and AWR report. This event is caused normally by :
1) Redo log files are too small.
2) More redo groups are needed.
3) Disk I/O is not fast enough.

Normally this issue can be addressed through adding more redo groups and/or increasing redo log file size.

Oracle recommends no more than five log switches per hour.