A strong password for the {@code SYS}, {@code SYSTEM}, and {@code PDB Admin} users to apply during standby creation.
The password must contain no fewer than nine characters and include:
At least two uppercase characters.
At least two lowercase characters.
At least two numeric characters.
At least two special characters. Valid special characters include \"_\", \"#\", and \"-\" only.
*The password MUST be the same as the primary admin password.**
The database software image OCID
True if active Data Guard is enabled.
The OCID of the DB home in which to create the standby database. You must supply this value to create standby database with an existing DB home
Specifies the {@code DB_UNIQUE_NAME} of the peer database to be created.
Specifies a prefix for the {@code Oracle SID} of the database to be created.
The OCID of the VM Cluster in which to create the standby database. You must supply this value if creationType is {@code ExistingVmCluster}.
The protection mode to set up between the primary and standby databases. For more information, see Oracle Data Guard Protection Modes in the Oracle Data Guard documentation.
*IMPORTANT** - The only protection mode currently supported by the Database service is MAXIMUM_PERFORMANCE.
The redo transport type to use for this Data Guard association. Valid values depend on the specified {@code protectionMode}:
MAXIMUM_AVAILABILITY - SYNC or FASTSYNC * MAXIMUM_PERFORMANCE - ASYNC * MAXIMUM_PROTECTION - SYNC
For more information, see [Redo Transport Services](http://docs.oracle.com/database/122/SBYDB/oracle-data-guard-redo-transport-services.htm#SBYDB00400) in the Oracle Data Guard documentation.
*IMPORTANT** - The only transport type currently supported by the Database service is ASYNC.
The configuration details for creating a Data Guard association for a ExaCC Vmcluster database. For these types of vm cluster databases, the {@code creationType} should be {@code ExistingVmCluster}. A standby database will be created in the VM cluster you specify.