Bug 30372335 - GDSCTL: VALIDATION RESULTS: WRONG POOL NAME DETECTED
(Doc ID 2614078.1)
Last updated on MAY 04, 2020
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
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:
Region Name: reed
Pool Name: bdms
Although other GDSCTL commands succeed, the 'validate' command returns an error.
In this example, the region and pool names are configured as lower case.
GDSCTL> sync database
The operation completed successfully
[Warning] VLD2: Region "reed" does not have buddy region
[Error] VLD31: Database bdmssh2_bdmsprd1 : wrong pool name detected "BDMS" <========== pool name became uppercase
[Error] VLD32: Database bdmssh2_bdmsprd1 : wrong GDS region name detected "REED" <========== region name became uppercase
[Error] VLD31: Database bdmssh4_bdmsprd2 : wrong pool name detected "BDMS"
[Error] VLD32: Database bdmssh4_bdmsprd2 : wrong GDS region name detected "REED"
Total errors: 4. Total warnings:1
Catalog connection is established
Name Shard space Status State Region Availability
---- ----------- ------ ----- ------ ------------
bdmssh1_bdmsprd1 bdmsshard1 Ok Deployed reed ONLINE
bdmssh2_bdmsprd1 bdmsshard1 Ok Deployed reed READ ONLY
bdmssh3_bdmsprd2 bdmsshard2 Ok Deployed reed ONLINE
bdmssh4_bdmsprd2 bdmsshard2 Ok Deployed reed READ ONLY
The pool name and region name are actually lowercase in the GDS configuration.
You could get the GDS confiugration by
GSM parameters becomes uppercase after failover of a standby shard.
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