FAL: Can’t identify FAL client, null string supplied

January 24, 2018

Question : FAL: Can’t identify FAL client, null string supplied

Our standby database is failing to apply the supplied log files and reports the following error in the standby error log

Failed to request gap sequence. Thread #: 1, gap sequence: 1861-1861

I find the following error in the primary server error log:

FAL: Can’t identify FAL client, null string supplied
Thread 1, gap sequence 1861-1861

Any ideas?

 

Solution: FAL: Can’t identify FAL client, null string supplied

Check your FAL_Client and FAL_Server settings in the init.ora files on the primary and standby database instances. They should be the same.