This is the solution for the following problem:The Data Guard broker could not execute a health check at the moment, so the configuration status could not be determined.
In this article you will be presented a suitable solution for DGM-17016 in Oracle 11g Release 2 (11.2).
Read this article if you found a DGM-17009 error in you logs. This article is dedicated especially for Oracle 11g Release 2 (11.2) but it can be useful for other Oracle Database releases.
This is the solution for the following problem:The Observer was started on an operating system that does not support multi-threading.
This is the solution for the following problem:The named database to be removed is the primary database.
This is the solution for the following problem:The named instance exists on more than one database.
This is a quick solution for Oracle error DGM-16999. This solution is suitable for Oracle 11g Release 2 (11.2). If you are interested please come in.
In htis article you will fine a solution for error: The named resource exists on more than one site.. This solution is suitable for Oracle 11g Release 2 (11.2).
This is a quick solution for Oracle error DGM-16979. This solution is suitable for Oracle 11g Release 2 (11.2). If you are interested please come in.
If the following problem occurs in your application read this article: The status could not be retrieved.
In this article you will be presented a brief description for error DGM-16959.
This is the solution for the following problem:The Observer configuration file cannot be opened or cannot be locked for exclusive access.
This is a short information taken from Oracle documentation where you can find a proposed solution for Oracle error: DGM-16953. This solution is suitable for Oracle 11g Release 2 (11.2). If you are interested please come in.
In this article you will be presented a brief description for error DGM-16952.
This is a quick solution for Oracle error DGM-16951. This solution is suitable for Oracle 11g Release 2 (11.2). If you are interested please come in.