The following solutions apply to problems with scaling an Oracle Database Cloud Service environment.
My scaling operation does not start
The system is overloaded with requests.
Wait before you try to scale again. If that doesn't work, contact Oracle Support.
My deployment is too busy to allow scaling
Your database deployment has a pending maintenance operation such as backup or patching.
Wait until maintenance has completed before you try scaling again.
After scaling the shape of my Data Guard configuration, I get an ORA-16792 warning when I check the status of the configuration
After scaling the shape of a Data Guard configuration, both the DGMGRL
SHOW CONFIGURATION command and the dbaascli
dataguard status command report the warning: "ORA-16792: configurable property value is inconsistent with database setting."
Perform the following steps to resolve the inconsistent setting warning:
Connect as the
oracleuser to the compute node hosting the primary database. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH).
$ dgmgrl /
Use the DGMGRL
SHOW DATABASEcommand to determine which Data Guard broker property is inconsistent with the database setting.
DGMGRL> SHOW DATABASE 'database-name' 'InconsistentProperties';
database-nameis the name of the primary database (SID).
DGMGRL> SHOW DATABASE 'ORCL' 'InconsistentProperties'; INCONSISTENT PROPERTIES INSTANCE_NAME PROPERTY_NAME MEMORY_VALUE SPFILE_VALUE BROKER_VALUE ORCL ArchiveLagTarget 0 0
Use the DGMGRL
EDIT DATABASEcommand to reset the Data Guard broker property value, which in turn sets the value in the server parameter file (SPFILE).
DGMGRL> EDIT DATABASE 'database-name' SET PROPERTY 'property-name'=value;Where:
database-nameis the name of the database (SID)
property-nameis the name of the Data Guard broker property displayed in the output from the
valueis the value displayed in
MEMORY_VALUEin the output from the
DGMGRL> EDIT DATABASE 'ORCL' SET PROPERTY 'ArchiveLagTarget'=0; Property "ArchiveLagTarget" updated
Exit from DGMGRL and close your connection to the compute node.