My Oracle Support Banner

GSM Manager Dose Not Register Standby Database And Read_service Not Enabled On This Standby Database (Doc ID 2486670.1)

Last updated on DECEMBER 05, 2019

Applies to:

Oracle Database - Standard Edition - Version 12.2.0.1 and later
Information in this document applies to any platform.

Symptoms

NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the
Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual
environments, actual persons, living or dead, is purely coincidental and not intended in any manner.

For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:

Primary Database: rodspd01w1
Standby Databases: rodspd01r1, rodspd01r3
Configuration name:  dg_rodspd01

***************

On : 12.2.0.1 version, RDBMS

GSM manager dose not register standby database and read_service not enabled on this standby database

Data Guard 1 primary 2 standby and GSM manager register one and refusing to register the second standby database

DGMGRL> show configuration


Configuration - dg_rodspd01

Protection Mode: MaxAvailability
Members:
rodspd01w1 - Primary database
rodspd01r1 - (*) Physical standby database
rodspd01r3 - Physical standby database


Fast-Start Failover: ENABLED

Configuration Status:
SUCCESS (status updated 10 seconds ago)


GDSCTL>sync brokerconfig -gdspool rods_pd01
The operation completed successfully

GDSCTL>modify service -gdspool rods_pd01 -service reader_rods_pd01 -preferred rodspd01r3
The operation completed successfully

GDSCTL>modify service -gdspool rods_pd01 -service writer_rods_pd01 -available rodspd01r3
The operation completed successfully

GDSCTL>start service -gdspool rods_pd01 -service reader_rods_pd01
GSM Warnings:
GSM-40134: Service is already running on all possible databases

GDSCTL>status database -gdspool rods_pd01 -verbose
Alert: GSM listener rejected database registration.
Database: "rodspd01r1" Registered: Y State: Ok ONS: N. Role: PH_STNDBY Instances: 1 Region: <region name>  
  Service: "reader_rods_pd01" Globally started: Y Started: Y
  Scan: N Enabled: Y Preferred: Y
  Service: "writer_rods_pd01" Globally started: Y Started: N
  Scan: N Enabled: Y Preferred: N
  Registered instances:
  rods_pd01‘
Database: "rodspd01r3" Registered: N State: Uninitialized ONS: N. Role: N/A Instances: 0 Region:<region name>
  Service: "reader_rods_pd01" Globally started: Y Started: N
  Scan: N Enabled: Y Preferred: Y
  Service: "writer_rods_pd01" Globally started: Y Started: N
  Scan: N Enabled: Y Preferred: N
Database: "rodspd01w1" Registered: Y State: Ok ONS: N. Role: PRIMARY Instances: 1 Region:<region name>
  Service: "reader_rods_pd01" Globally started: Y Started: N
  Scan: N Enabled: Y Preferred: N
  Service: "writer_rods_pd01" Globally started: Y Started: Y
 

ERROR
-----------------------
GSM-40134: Service is already running on all possible databases

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.