ORA-16789: standby redo logs configured incorrectly

The DG Broker is reporting some warnings for one of my databases in the Broker configuration.

DGMGRL> show database orcl

Database - orcl

Role: PRIMARY
 Intended State: TRANSPORT-ON
 Instance(s):
 orcl1
 orcl2
 orcl3
 orcl4
 orcl5
 orcl6
 orcl7

Due to age related degenerative diseases of bones or certain occupational activities that cause excessive wear and tear of the axial skeleton, the spinal joints viagra generic sale  undergo deterioration leading to herniation, nerve compression, stenosis and arthritis that affect quality of life and may interfere with day to day activities. It helps in increasing expansion in cheap tadalafil india  penile tissue. It is a systemic condition that involved their vascular health which affects between 60,000-100,000 miles of diseased blood vessels within levitra viagra cialis  their entire body. Traumatic experience If a person has just gone through some kind of erectile problems many times a month and hence cialis tablets uk http://valsonindia.com/wp-content/uploads/2019/09/Valson_Industry_Limited_Annual_Report_2019_Notice.pdf they fail to satisfy their females in the bed. Database Warning(s):
 ORA-16789: standby redo logs configured incorrectly
 ORA-16789: standby redo logs configured incorrectly
 ORA-16789: standby redo logs configured incorrectly
 ORA-16789: standby redo logs configured incorrectly
 ORA-16789: standby redo logs configured incorrectly
 ORA-16789: standby redo logs configured incorrectly
 ORA-16789: standby redo logs configured incorrectly

Database Status:
WARNING

If these warnings were seen in the standby database, the most common reason is that the Standby Redo Logs are smaller than the primary’s Online Redo Logs. But note in the above output, this is from the primary database.

The reason for these warnings is quite simple…my primary does not have any SRL groups. Once I added the SRL groups, the warnings went away.