DGMCategorySubscribe

The following is the DGM-17017 error message, you … Continue Reading DGM-17017: unable to determine configuration status cause and solution

The following is the DGM-17016 error message, you … Continue Reading DGM-17016: failed to retrieve status for database “string” cause and solution

The following is the DGM-17009 error message, you … Continue Reading DGM-17009: New primary database “string” is opening… cause and solution

The following is the DGM-17007 error message, you … Continue Reading DGM-17007: Unsupported platform, observer cannot start cause and solution

The following is the DGM-17002 error message, you … Continue Reading DGM-17002: Primary database cannot be removed cause and solution

The following is the DGM-17000 error message, you … Continue Reading DGM-17000: Two or more instances have the name “string” cause and solution

The following is the DGM-16999 error message, you … Continue Reading DGM-16999: Instance “string” was not found cause and solution

The following is the DGM-16991 error message, you … Continue Reading DGM-16991: Two or more resources have the name “string” cause and solution

The following is the DGM-16979 error message, you … Continue Reading DGM-16979: Unable to log on to the primary or standby database as SYSDBA cause and solution

The following is the DGM-16960 error message, you … Continue Reading DGM-16960: Status not available cause and solution

The following is the DGM-16959 error message, you … Continue Reading DGM-16959: No response from broker server process cause and solution

The following is the DGM-16954 error message, you … Continue Reading DGM-16954: Unable to open and lock the Observer configuration file cause and solution

The following is the DGM-16953 error message, you … Continue Reading DGM-16953: XML document is too long cause and solution

The following is the DGM-16952 error message, you … Continue Reading DGM-16952: Configuration details cannot be determined by DGMGRL cause and solution

The following is the DGM-16951 error message, you … Continue Reading DGM-16951: Unable to failover cause and solution

The following is the DGM-16949 error message, you … Continue Reading DGM-16949: Object “string” was not found cause and solution

The following is the DGM-16948 error message, you … Continue Reading DGM-16948: Unable to switchover, primary database is still “string” cause and solution

The following is the DGM-16946 error message, you … Continue Reading DGM-16946: Site “string” was not found cause and solution

The following is the DGM-16945 error message, you … Continue Reading DGM-16945: Syntax error before or at “string” cause and solution

The following is the DGM-16944 error message, you … Continue Reading DGM-16944: Failover succeeded, new primary is “string” cause and solution