I was managing and configuration an Active-Standby database running in an Oracle RAC that has two nodes when I found the following output from the alert.log:
2021-08-24 Log Apply Services Managed Standby Recovery Canceled 2021-08-24 Log Apply Services Attempt to start background Managed Standby Recovery process 2021-08-24 Log Apply Services Background Managed Standby Recovery process started 2021-08-24 Log Apply Services Managed Standby Recovery starting Real Time Apply 2021-08-24 Log Apply Services Media Recovery Waiting for T-1.S-194 2021-08-24 Log Transport Services Error 12154 received logging on to the standby 2021-08-24 Fetch Archive Log FAL: Error 12154 connecting to DB_TECH1,DB_TECH2 for fetching gap sequence
After some research, I found that the parameter FAL_SERVER was not configured right in both Primary and Standby databases. The parameter was fixed on both sides. The main issue to cause this to happen is because the multiple service names in the FAL_SERVER parameter on the Standby database were not configured correctly.
The issue was that the parameter was configured as below:
fal_server = '<service name of database 1>,<service name of database 2>'
Instead of correct form as below:
Example :
fal_server = '<service name of database 1>,<service name of database 2>' ALTER SYSTEM SET fal_server='DB_TECH1','DB_TECH2' SCOPE=BOTH SID='*';
After the right configuration, the Data Guard 19c starts to works correctly.
Hi! I am Bruno, a Brazilian born and bred. Former Oracle ACE, Computer Scientist, MSc in Data Science, over ten years of experience in companies such as IBM, Epico Tech, and Playtech based in three different countries (Brazil, Hungary, and Sweden) and joined projects remotely in many others. I am super excited to show you my interest in Databases, Cloud, Data Science, Data Engineering, Bigdata, AI, Programming, Software Engineering, and data in general.
(Continue reading)