An Issue of Oracle DataGuard Broker

An Issue of Oracle distributed uard Broker has been studying how to build Data Guard with a Broker. It has been a good job in the past. A strange problem was suddenly found in the past two days, the configuration process is correct, but the following error message is displayed: DGMGRL> show configuration; Configuration Name: dgmgrl_1 Enabled: YES Protection Mode: maxPerformance Fast-Start Failover: DISABLED Databases: prod-Primary database sbdb-Physical standby databaseCurrent status for "dgmgrl_1": Warning: ORA-16608: one or more da Tabases have warnings DGMGRL> show database 'prod' statusreport; status report INSTANCE_NAME SEVERITY ERROR_TEXTDGMGRL> show database 'sbdb' statusreport; status report INSTANCE_NAME SEVERITY ERROR_TEXT * WARNING ORA-16707: the value of the property DbFileNameConvert is invalid, valid values are pairs of file specifications sbdb warning ORA-16714: the value of property DbFileNameConvert is inconsist Ent with the database setting from this error message, we can see that db_file_name_convert of the standby database SBDB has a problem, so I did the following operations and finally found the problem, the red font section is truncated. DGMGRL> show database verbose SBDBDatabase Name: sbdb Role: physical standby Enabled: YES Intended State: ONLINE Instance (s): SBDB Properties: initialConnectIdentifier = 'sbdb' LogXptMode = 'async' Dependency = ''delaymins = '0' Binding = 'optional' MaxFailure = '0' MaxConnections = '1' ReopenSecs = '8080' NetTimeout = '000000' LogShipping = 'on' PreferredApplyInstance = ''applyinstancetimeout = '0' ApplyParallel = 'auto' StandbyFileManagement = 'auto' ArchiveLagTarget = '0' LogArchiveMaxProcesses = '2' memory = '1' DbFileNameConvert = '/u01/app/oracle/oradata/PROD/Disk1, /u01/app/oracle/oradata/SBDB,/u01/app/oracle/oradata/PROD/Disk2,/u01/app/oracle/oradata/SBDB, /u01/app/oracle/oradata/PROD/Disk3,/u01/app/oracle/oradata/SBDB,/u01/app/oracle/oradata/PROD/Disk4, /u01/app /Oracle/oradata/SBDB,/u01/app/oracle/oradata/PROD/Disk5,/u01/app/oracle/oradata/SBDB, /u01/app/oracle/oradata/PROD/Disk6,/u01/app/oracle/oradata/SBDB,/u01/app/oracle/oradata/PROD/Disk7, /u01/app/oracle/oradata/SBDB,/u01/app/oracle/oradata/PROD/Disk8 'logfilenameconvert = '/u01/app/oracle/oradata/PROD/Disk1, /u01/app/oracle/oradata/SBDB,/u01/app/oracle/oradata/PROD/Disk2,/u01/app/oracle/orad Ata/SBDB,/u01/app/oracle/oradata/PROD/Disk3,/u01/app/oracle/oradata/SBDB 'faststartfailovertarget = 'statusreport = '(monitor) 'inconsistentproperties = '(monitor) 'inconsistentlogxptprops =' (monitor) 'sendqentries = '(monitor) 'logxptstatus =' (monitor) 'RecvQEntries =' (monitor) 'hostname = 'even .oracle.com 'SidName = 'sbdb' LocalListenerAddress =' (ADDRESS = (PROTOCOL = tcp) (HOST = even. oracle. c Om) (PORT = 1521 )) 'standbyarchivelocation = '/u01/app/oracle/bak/arch1' AlternateLocation = ''logarchivetrace = '0' LogArchiveFormat =' % t _ % s _ % r. dbf 'latestlog = '(monitor) 'topwaitevents =' (monitor) 'current status for "sbdb": Warning: ORA-16809: multiple warnings detected for the database I initSBDB. ora is like the following. Obviously, the broker is inconsistent with my SPFILE, so an error is always reported. Db_file_name_convert = '/u01/app/oracle/oradata/PROD/Disk1', '/u01/app/oracle/oradata/sbdb ', '/u01/app/oracle/oradata/PROD/disk2','/u01/app/oracle/oradata/sbdb ', '/u01/app/oracle/oradata/PROD/Disk3', '/u01/app/oracle/oradata/sbdb ', '/u01/app/oracle/oradata/PROD/Disk4', '/u01/app/oracle/oradata/sbdb ', '/u01/app/oracle/oradata/PROD/Disk5', '/u01/app/oracle/oradata/sbdb ', '/u01/app/oracle/oradata/PROD/disk6','/u 01/app/oracle/oradata/sbdb', '/u01/app/oracle/oradata/PROD/disk7','/u01/app/oracle/oradata/sbdb ', '/u01/app/oracle/oradata/PROD/disk8','/u01/app/oracle/oradata/sbdb ', '/u01/app/oracle/oradata/prod','/u01/app/oracle/oradata/sbdb' the following bug was found in metlink: Bug 9469176: broker doesnot set DB_FILE_NAME_CONVERT (DBFILENAMECONVERT) CORRECTLYDescriptionData Guard broker limit the pairs of strings in DbFileNameConve Rt and LogFileNameConvert to only 10. exceeding that number, broker will not set them into the actual DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameter carefully analyzed and found that the VALUE of v $ parameter is VARCHAR2 (512 ), the value I set in pfile is longer than this. As a result, show and broker see all truncated values. SQL> desc v $ parameter Name Null? Type verification -------- interval num number name VARCHAR2 (80) type number value VARCHAR2 (512) DISPLAY_VALUE VARCHAR2 (512) ISDEFAULT VARCHAR2 (9) ISSES_MODIFIABLE VARCHAR2 (5) ISSYS_MODIFIABLE VARCHAR2 (9) ISINSTANCE_MODIFIABLE VARCHAR2 (5) ISMODIFIED VARCHAR2 (10) ISADJUSTED VARCHAR2 (5) ISDEPRECATED VARCHAR2 (5) DESCRIPTION VARCHAR2 (255) UPDATE_COMMENT VARCHAR2 (255) hash number Broker important diagnostic commands: show database 'sbdb' statusreport; show database verbose sbdb; conclusion: the length of the parameter file value should not exceed 512, otherwise, problems may occur. Record it and give yourself a Lessons learned handle.