archive log gap in physical standby database

one of the cause
ORA-12154:TNS:could not resolve the connect identifier specified

>>>alert_.log

search for GAP keyword in alertlog.

sequence=8171 thread=1;

I had to restore that on the primary side

rman target / catalog rman/rman@abc

RMAN>restore archivelog sequence=8171 thread=1;

:):):)

PMON to register with the local listener

we don’t want that PMON to register automatically with the local listener.

For doing the same we can set Parameter LOCAL_LISTENER=dummy

Purpose of dummy is that the databases do not register anymore to port 1521.

Added Datafile on wrong mountpoint in Dataguard

There were two tasks to be done. One was to move the file from incorrect location to correct one for Logical Database. And then register the datafile in the Physical Standby.
>

1)To move the datafile to the correct location in Logical Standby

ALTER DATABASE STOP LOGICAL STANDBY APPLY;

ALTER TABLESPACE ***** OFFLINE NORMAL;

cp /wrong mount point /right mount point

ALTER TABLESPACE ****** RENAME DATAFILE '/old.dbf' TO '/new.dbf';

ALTER TABLESPACE ***** ONLINE;

ALTER DATABASE START LOGICAL STANDBY APPLY;


2)

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=MANUAL;

alert log:

ORA-01111: name for data file 65 is unknown - rename to correct file
ORA-01110: data file 65: '/UNNAMED00065'
ORA-01157: cannot identify/lock data file 65 - see DBWR trace file

ALTER DATABASE CREATE DATAFILE '/UNNAMED00065' as '/new.dbf';

ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=AUTO;

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE;