Melek Durdu

Hata:

PING[ARC1]: Heartbeat failed to connect to standby ‘teststby’. Error is 16057.

Çözüm :

Primary veritabanında aşağıdaki şekilde sorgulandığında Data Guard konfigürasyonu ile ilgili hata göstermektedir.

SQL> select dest_id,error,status,log_sequence,applied_scn from v$archive_dest where dest_id=2;DEST_ID|ERROR |STATUS |LOG_SEQUENCE|APPLIED_SCN
— — | — — — — — — — —
2 |ORA-16057: server not in Data Guard configuration |ERROR | 0| 0

log_archive_config parametresi setlenmediğinden kaynaklı hata vermektedir. Primary veritabanında aşağıdaki gibi log_archive_config parametresi setlenir.

SQL> alter system set log_archive_config='dg_config=(TESTDB,TESTSTBY)';

Primary veritabanının Standby’a redo transferini gerçekleştirebilmesi için log_archive_dest_state_x parametresi enable edilir.

SQL> alter system set log_archive_dest_state_2=defer;SQL> alter system set log_archive_dest_state_2=enable;

--

--

Hata :

PMON (ospid: 23645): terminating the instance due to ORA error 471

Çözüm:

Memory yetersizliğinden dolayı işletim sistemi üzerinden OOM Killer (Out of Memory Killer) Oracle’ ı killediğinden dolayı yukarıdaki hata alınmaktadır. İşletim sistemi log’ u incelendiğinde aşağıdaki gibi görünecektir.

$ vi /var/log/messages

Hatayı gidermek için memory arttırımı yapılmalıdır.

--

--

I will share the solution of the following error received during the startup ASM instance.

Error :

SQL> startup
ORA-01078: failure in processing system parameters
ORA-29701: unable to connect to Cluster Synchronization Service

Solution :

  1. To fix this problem, it is necessary to start has ( high availability services ).
$ crsctl enable has
CRS-4622: Oracle High Availability Services autostart is enabled.
$ crsctl start res ora.cssd -init
CRS-2672: Attempting to start 'ora.cssd' on 'orcl'
CRS-2672: Attempting to start 'ora.diskmon' on 'orcl'
CRS-2676: Start of 'ora.diskmon' on 'orcl' succeeded
CRS-2676: Start of 'ora.cssd' on 'orcl' succeeded

2. Startup ASM Instance

SQL> startup
ASM instance started
Total System Global Area 1137173320 bytes
Fixed Size 8905544 bytes
Variable Size 1103101952 bytes
ASM Cache 25165824 bytes
ASM diskgroups mounted

--

--

I will share the solution of the following error received during the installation of Oracle 11gR2 Software.

Error :

Error in invoking target ‘agent nmhs’ of makefile ‘/u01/app/oracle/product/11.0.0/db1/sysman/lib/ins_emagent.mk’. See ‘/u01/app/oraInventory/logs/installActions2021–08–12_04–21–06PM.log’ for details.

Solution :

Enter $ORACLE_HOME/sysman/lib/ins_emagent.mk.

$ vi $ORACLE_HOME/sysman/lib/ins_emagent.mk

Search the $(MK_EMAGENT_NMECTL) line and change it as follows.

#$(MK_EMAGENT_NMECTL)$(MK_EMAGENT_NMECTL) -lnnz11

--

--

I will share the following error with its solution, after switchover between primary and standby in PostgreSQL. (Database version : PostgreSQL 13)

Error :

LOG: started streaming WAL from primary at 0/6000000 on timeline 2
FATAL: could not receive data from WAL stream: ERROR: requested WAL segment 000000020000000000000006 has already been removed

Solution :

Archives missing from the primary database are copied to the pg_wal directory in the standby database.

$ scp -r 000000020000000000000006 postgres@<standby_server_ip>:/var/lib/pgsql/13/data/pg_wal

After the missing archives are copied, the standby database is restarted.

$ pg_ctl -D /var/lib/pgsql/13/data stop$ pg_ctl -D /var/lib/pgsql/13/data start

--

--