@Generated(value="OracleSDKGenerator", comments="API Version: 20160918") public class DatabaseAsyncClient extends BaseAsyncClient implements DatabaseAsync
Async client implementation for Database service.
There are two ways to use async client: 1. Use AsyncHandler: using AsyncHandler, if the response
to the call is an InputStream
, like getObject Api in object storage service,
developers need to process the stream in AsyncHandler, and not anywhere else, because the stream
will be closed right after the AsyncHandler is invoked.
2. Use Java Future: using Java Future, developers need to close the stream after they are done
with the Java Future.
Accessing the result should be done in a mutually exclusive manner, either through the Future or
the AsyncHandler, but not both. If the Future is used, the caller should pass in null as the
AsyncHandler. If the AsyncHandler is used, it is still safe to use the Future to determine
whether or not the request was completed via Future.isDone/isCancelled.
Please refer to
https://github.com/oracle/oci-java-sdk/blob/master/bmc-examples/src/main/java/ResteasyClientWithObjectStorageExample.java
Modifier and Type | Class and Description |
---|---|
static class |
DatabaseAsyncClient.Builder
Builder class for this client.
|
Modifier and Type | Field and Description |
---|---|
String |
clientCommonLibraryVersion
Compatible SDK version, provided by the codegen.
|
Optional<String> |
minimumClientCommonLibraryVersionFromClient
Minimum compatible SDK version, maybe provided by the codegen.
|
static Service |
SERVICE
Service instance for Database.
|
Constructor and Description |
---|
DatabaseAsyncClient(AbstractAuthenticationDetailsProvider authenticationDetailsProvider,
ClientConfiguration configuration,
ClientConfigurator clientConfigurator,
RequestSignerFactory defaultRequestSignerFactory)
Deprecated.
Use the
builder instead. |
DatabaseAsyncClient(AbstractAuthenticationDetailsProvider authenticationDetailsProvider,
ClientConfiguration configuration,
ClientConfigurator clientConfigurator,
RequestSignerFactory defaultRequestSignerFactory,
List<ClientConfigurator> additionalClientConfigurators)
Deprecated.
Use the
builder instead. |
DatabaseAsyncClient(AbstractAuthenticationDetailsProvider authenticationDetailsProvider,
ClientConfiguration configuration,
ClientConfigurator clientConfigurator,
RequestSignerFactory defaultRequestSignerFactory,
List<ClientConfigurator> additionalClientConfigurators,
String endpoint)
Deprecated.
Use the
builder instead. |
DatabaseAsyncClient(AbstractAuthenticationDetailsProvider authenticationDetailsProvider,
ClientConfiguration configuration,
ClientConfigurator clientConfigurator,
RequestSignerFactory defaultRequestSignerFactory,
Map<SigningStrategy,RequestSignerFactory> signingStrategyRequestSignerFactories,
List<ClientConfigurator> additionalClientConfigurators,
String endpoint)
Deprecated.
Use the
builder instead. |
DatabaseAsyncClient(BasicAuthenticationDetailsProvider authenticationDetailsProvider)
Deprecated.
Use the
builder instead. |
DatabaseAsyncClient(BasicAuthenticationDetailsProvider authenticationDetailsProvider,
ClientConfiguration configuration)
Deprecated.
Use the
builder instead. |
DatabaseAsyncClient(BasicAuthenticationDetailsProvider authenticationDetailsProvider,
ClientConfiguration configuration,
ClientConfigurator clientConfigurator)
Deprecated.
Use the
builder instead. |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
getEndpoint, refreshClient, setEndpoint, useRealmSpecificEndpointTemplate
close
public static final Service SERVICE
Service instance for Database.
public final String clientCommonLibraryVersion
@Deprecated public DatabaseAsyncClient(BasicAuthenticationDetailsProvider authenticationDetailsProvider)
builder
instead.Create a new client instance.
authenticationDetailsProvider
- The authentication details (see DatabaseAsyncClient.Builder.build(com.oracle.bmc.auth.AbstractAuthenticationDetailsProvider)
)@Deprecated public DatabaseAsyncClient(BasicAuthenticationDetailsProvider authenticationDetailsProvider, ClientConfiguration configuration)
builder
instead.Create a new client instance.
authenticationDetailsProvider
- The authentication details (see DatabaseAsyncClient.Builder.build(com.oracle.bmc.auth.AbstractAuthenticationDetailsProvider)
)configuration
- ClientBuilderBase.configuration
@Deprecated public DatabaseAsyncClient(BasicAuthenticationDetailsProvider authenticationDetailsProvider, ClientConfiguration configuration, ClientConfigurator clientConfigurator)
builder
instead.Create a new client instance.
authenticationDetailsProvider
- The authentication details (see DatabaseAsyncClient.Builder.build(com.oracle.bmc.auth.AbstractAuthenticationDetailsProvider)
)configuration
- ClientBuilderBase.configuration
clientConfigurator
- ClientBuilderBase.clientConfigurator(com.oracle.bmc.http.ClientConfigurator)
@Deprecated public DatabaseAsyncClient(AbstractAuthenticationDetailsProvider authenticationDetailsProvider, ClientConfiguration configuration, ClientConfigurator clientConfigurator, RequestSignerFactory defaultRequestSignerFactory)
builder
instead.Create a new client instance.
authenticationDetailsProvider
- The authentication details (see DatabaseAsyncClient.Builder.build(com.oracle.bmc.auth.AbstractAuthenticationDetailsProvider)
)configuration
- ClientBuilderBase.configuration
clientConfigurator
- ClientBuilderBase.clientConfigurator(com.oracle.bmc.http.ClientConfigurator)
defaultRequestSignerFactory
- ClientBuilderBase.requestSignerFactory
@Deprecated public DatabaseAsyncClient(AbstractAuthenticationDetailsProvider authenticationDetailsProvider, ClientConfiguration configuration, ClientConfigurator clientConfigurator, RequestSignerFactory defaultRequestSignerFactory, List<ClientConfigurator> additionalClientConfigurators)
builder
instead.Create a new client instance.
authenticationDetailsProvider
- The authentication details (see DatabaseAsyncClient.Builder.build(com.oracle.bmc.auth.AbstractAuthenticationDetailsProvider)
)configuration
- ClientBuilderBase.configuration
clientConfigurator
- ClientBuilderBase.clientConfigurator(com.oracle.bmc.http.ClientConfigurator)
defaultRequestSignerFactory
- ClientBuilderBase.requestSignerFactory
additionalClientConfigurators
- ClientBuilderBase.additionalClientConfigurators
@Deprecated public DatabaseAsyncClient(AbstractAuthenticationDetailsProvider authenticationDetailsProvider, ClientConfiguration configuration, ClientConfigurator clientConfigurator, RequestSignerFactory defaultRequestSignerFactory, List<ClientConfigurator> additionalClientConfigurators, String endpoint)
builder
instead.Create a new client instance.
authenticationDetailsProvider
- The authentication details (see DatabaseAsyncClient.Builder.build(com.oracle.bmc.auth.AbstractAuthenticationDetailsProvider)
)configuration
- ClientBuilderBase.configuration
clientConfigurator
- ClientBuilderBase.clientConfigurator(com.oracle.bmc.http.ClientConfigurator)
defaultRequestSignerFactory
- ClientBuilderBase.requestSignerFactory
additionalClientConfigurators
- ClientBuilderBase.additionalClientConfigurators
endpoint
- ClientBuilderBase.endpoint(java.lang.String)
@Deprecated public DatabaseAsyncClient(AbstractAuthenticationDetailsProvider authenticationDetailsProvider, ClientConfiguration configuration, ClientConfigurator clientConfigurator, RequestSignerFactory defaultRequestSignerFactory, Map<SigningStrategy,RequestSignerFactory> signingStrategyRequestSignerFactories, List<ClientConfigurator> additionalClientConfigurators, String endpoint)
builder
instead.Create a new client instance.
authenticationDetailsProvider
- The authentication details (see DatabaseAsyncClient.Builder.build(com.oracle.bmc.auth.AbstractAuthenticationDetailsProvider)
)configuration
- ClientBuilderBase.configuration
clientConfigurator
- ClientBuilderBase.clientConfigurator(com.oracle.bmc.http.ClientConfigurator)
defaultRequestSignerFactory
- ClientBuilderBase.requestSignerFactory
additionalClientConfigurators
- ClientBuilderBase.additionalClientConfigurators
endpoint
- ClientBuilderBase.endpoint(java.lang.String)
signingStrategyRequestSignerFactories
- ClientBuilderBase.signingStrategyRequestSignerFactories
public static DatabaseAsyncClient.Builder builder()
Create a builder for this client.
public void setRegion(Region region)
DatabaseAsync
Sets the region to call (ex, Region.US_PHOENIX_1).
Note, this will call setEndpoint
after resolving the
endpoint. If the service is not available in this region, however, an
IllegalArgumentException will be raised.
setRegion
in interface DatabaseAsync
region
- The region of the service.public void setRegion(String regionId)
DatabaseAsync
Sets the region to call (ex, ‘us-phoenix-1’).
Note, this will first try to map the region ID to a known Region and call setRegion
.
If no known Region could be determined, it will create an endpoint based on the default
endpoint format (Region.formatDefaultRegionEndpoint(Service, String)
and then call setEndpoint
.
setRegion
in interface DatabaseAsync
regionId
- The public region ID.public Future<ActivateExadataInfrastructureResponse> activateExadataInfrastructure(ActivateExadataInfrastructureRequest request, AsyncHandler<ActivateExadataInfrastructureRequest,ActivateExadataInfrastructureResponse> handler)
DatabaseAsync
Activates the specified Exadata infrastructure resource. Applies to Exadata Cloud@Customer instances only.
activateExadataInfrastructure
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<AddStorageCapacityCloudExadataInfrastructureResponse> addStorageCapacityCloudExadataInfrastructure(AddStorageCapacityCloudExadataInfrastructureRequest request, AsyncHandler<AddStorageCapacityCloudExadataInfrastructureRequest,AddStorageCapacityCloudExadataInfrastructureResponse> handler)
DatabaseAsync
Makes the storage capacity from additional storage servers available for Cloud VM Cluster consumption. Applies to Exadata Cloud Service instances and Autonomous Database on dedicated Exadata infrastructure only.
addStorageCapacityCloudExadataInfrastructure
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<AddStorageCapacityExadataInfrastructureResponse> addStorageCapacityExadataInfrastructure(AddStorageCapacityExadataInfrastructureRequest request, AsyncHandler<AddStorageCapacityExadataInfrastructureRequest,AddStorageCapacityExadataInfrastructureResponse> handler)
DatabaseAsync
Makes the storage capacity from additional storage servers available for VM Cluster consumption. Applies to Exadata Cloud@Customer instances only.
addStorageCapacityExadataInfrastructure
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<AddVirtualMachineToCloudVmClusterResponse> addVirtualMachineToCloudVmCluster(AddVirtualMachineToCloudVmClusterRequest request, AsyncHandler<AddVirtualMachineToCloudVmClusterRequest,AddVirtualMachineToCloudVmClusterResponse> handler)
DatabaseAsync
Add Virtual Machines to the Cloud VM cluster. Applies to Exadata Cloud instances only.
addVirtualMachineToCloudVmCluster
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<AddVirtualMachineToVmClusterResponse> addVirtualMachineToVmCluster(AddVirtualMachineToVmClusterRequest request, AsyncHandler<AddVirtualMachineToVmClusterRequest,AddVirtualMachineToVmClusterResponse> handler)
DatabaseAsync
Add Virtual Machines to the VM cluster. Applies to Exadata Cloud@Customer instances only.
addVirtualMachineToVmCluster
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<AutonomousDatabaseManualRefreshResponse> autonomousDatabaseManualRefresh(AutonomousDatabaseManualRefreshRequest request, AsyncHandler<AutonomousDatabaseManualRefreshRequest,AutonomousDatabaseManualRefreshResponse> handler)
DatabaseAsync
Initiates a data refresh for an Autonomous Database refreshable clone. Data is refreshed from the source database to the point of a specified timestamp.
autonomousDatabaseManualRefresh
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CancelBackupResponse> cancelBackup(CancelBackupRequest request, AsyncHandler<CancelBackupRequest,CancelBackupResponse> handler)
DatabaseAsync
Cancel automatic/standalone full/incremental create backup workrequests specified by the backup Id.
cancelBackup
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CancelExecutionWindowResponse> cancelExecutionWindow(CancelExecutionWindowRequest request, AsyncHandler<CancelExecutionWindowRequest,CancelExecutionWindowResponse> handler)
DatabaseAsync
Cancels the in progress maintenance activity under this execution window.
cancelExecutionWindow
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CascadingDeleteSchedulingPlanResponse> cascadingDeleteSchedulingPlan(CascadingDeleteSchedulingPlanRequest request, AsyncHandler<CascadingDeleteSchedulingPlanRequest,CascadingDeleteSchedulingPlanResponse> handler)
DatabaseAsync
Delete the scheduling plan resource along with all the scheduled actions associated with this resource.
cascadingDeleteSchedulingPlan
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeAutonomousContainerDatabaseCompartmentResponse> changeAutonomousContainerDatabaseCompartment(ChangeAutonomousContainerDatabaseCompartmentRequest request, AsyncHandler<ChangeAutonomousContainerDatabaseCompartmentRequest,ChangeAutonomousContainerDatabaseCompartmentResponse> handler)
DatabaseAsync
Move the Autonomous Container Database and its dependent resources to the specified compartment. For more information about moving Autonomous Container Databases, see Moving Database Resources to a Different Compartment.
changeAutonomousContainerDatabaseCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeAutonomousDatabaseCompartmentResponse> changeAutonomousDatabaseCompartment(ChangeAutonomousDatabaseCompartmentRequest request, AsyncHandler<ChangeAutonomousDatabaseCompartmentRequest,ChangeAutonomousDatabaseCompartmentResponse> handler)
DatabaseAsync
Move the Autonomous Database and its dependent resources to the specified compartment. For more information about moving Autonomous Databases, see Moving Database Resources to a Different Compartment.
changeAutonomousDatabaseCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeAutonomousDatabaseSoftwareImageCompartmentResponse> changeAutonomousDatabaseSoftwareImageCompartment(ChangeAutonomousDatabaseSoftwareImageCompartmentRequest request, AsyncHandler<ChangeAutonomousDatabaseSoftwareImageCompartmentRequest,ChangeAutonomousDatabaseSoftwareImageCompartmentResponse> handler)
DatabaseAsync
Move the Autonomous Database Software Image and its dependent resources to the specified compartment.
changeAutonomousDatabaseSoftwareImageCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeAutonomousDatabaseSubscriptionResponse> changeAutonomousDatabaseSubscription(ChangeAutonomousDatabaseSubscriptionRequest request, AsyncHandler<ChangeAutonomousDatabaseSubscriptionRequest,ChangeAutonomousDatabaseSubscriptionResponse> handler)
DatabaseAsync
Associate an Autonomous Database with a different subscription.
changeAutonomousDatabaseSubscription
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeAutonomousExadataInfrastructureCompartmentResponse> changeAutonomousExadataInfrastructureCompartment(ChangeAutonomousExadataInfrastructureCompartmentRequest request, AsyncHandler<ChangeAutonomousExadataInfrastructureCompartmentRequest,ChangeAutonomousExadataInfrastructureCompartmentResponse> handler)
DatabaseAsync
Deprecated. Use the changeCloudExadataInfrastructureCompartment
operation to move an Exadata
infrastructure resource to a different compartment and changeCloudAutonomousVmClusterCompartment
operation to move an
Autonomous Exadata VM cluster to a different compartment. For more information, see Moving
Database Resources to a Different
Compartment.
changeAutonomousExadataInfrastructureCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeAutonomousVmClusterCompartmentResponse> changeAutonomousVmClusterCompartment(ChangeAutonomousVmClusterCompartmentRequest request, AsyncHandler<ChangeAutonomousVmClusterCompartmentRequest,ChangeAutonomousVmClusterCompartmentResponse> handler)
DatabaseAsync
Moves an Autonomous VM cluster and its dependent resources to another compartment. Applies to
Exadata Cloud@Customer only. For systems in the Oracle cloud, see changeAutonomousVmClusterCompartment
.
changeAutonomousVmClusterCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeBackupDestinationCompartmentResponse> changeBackupDestinationCompartment(ChangeBackupDestinationCompartmentRequest request, AsyncHandler<ChangeBackupDestinationCompartmentRequest,ChangeBackupDestinationCompartmentResponse> handler)
DatabaseAsync
Move the backup destination and its dependent resources to the specified compartment. For more information, see Moving Database Resources to a Different Compartment.
changeBackupDestinationCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeCloudAutonomousVmClusterCompartmentResponse> changeCloudAutonomousVmClusterCompartment(ChangeCloudAutonomousVmClusterCompartmentRequest request, AsyncHandler<ChangeCloudAutonomousVmClusterCompartmentRequest,ChangeCloudAutonomousVmClusterCompartmentResponse> handler)
DatabaseAsync
Moves an Autonomous Exadata VM cluster in the Oracle cloud and its dependent resources to
another compartment. For Exadata Cloud@Customer systems, see changeAutonomousVmClusterCompartment
.
changeCloudAutonomousVmClusterCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeCloudExadataInfrastructureCompartmentResponse> changeCloudExadataInfrastructureCompartment(ChangeCloudExadataInfrastructureCompartmentRequest request, AsyncHandler<ChangeCloudExadataInfrastructureCompartmentRequest,ChangeCloudExadataInfrastructureCompartmentResponse> handler)
DatabaseAsync
Moves a cloud Exadata infrastructure resource and its dependent resources to another compartment. Applies to Exadata Cloud Service instances and Autonomous Database on dedicated Exadata infrastructure only.For more information about moving resources to a different compartment, see Moving Database Resources to a Different Compartment.
changeCloudExadataInfrastructureCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeCloudExadataInfrastructureSubscriptionResponse> changeCloudExadataInfrastructureSubscription(ChangeCloudExadataInfrastructureSubscriptionRequest request, AsyncHandler<ChangeCloudExadataInfrastructureSubscriptionRequest,ChangeCloudExadataInfrastructureSubscriptionResponse> handler)
DatabaseAsync
Associate a cloud Exadata infrastructure with a different subscription.
changeCloudExadataInfrastructureSubscription
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeCloudVmClusterCompartmentResponse> changeCloudVmClusterCompartment(ChangeCloudVmClusterCompartmentRequest request, AsyncHandler<ChangeCloudVmClusterCompartmentRequest,ChangeCloudVmClusterCompartmentResponse> handler)
DatabaseAsync
Moves a cloud VM cluster and its dependent resources to another compartment. Applies to Exadata Cloud Service instances and Autonomous Database on dedicated Exadata infrastructure only.
changeCloudVmClusterCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeCloudVmClusterSubscriptionResponse> changeCloudVmClusterSubscription(ChangeCloudVmClusterSubscriptionRequest request, AsyncHandler<ChangeCloudVmClusterSubscriptionRequest,ChangeCloudVmClusterSubscriptionResponse> handler)
DatabaseAsync
Associate a cloud VM cluster with a different subscription.
changeCloudVmClusterSubscription
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeDatabaseSoftwareImageCompartmentResponse> changeDatabaseSoftwareImageCompartment(ChangeDatabaseSoftwareImageCompartmentRequest request, AsyncHandler<ChangeDatabaseSoftwareImageCompartmentRequest,ChangeDatabaseSoftwareImageCompartmentResponse> handler)
DatabaseAsync
Move the Database Software Image and its dependent resources to the specified compartment. For more information about moving Databse Software Images, see Moving Database Resources to a Different Compartment.
changeDatabaseSoftwareImageCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeDataguardRoleResponse> changeDataguardRole(ChangeDataguardRoleRequest request, AsyncHandler<ChangeDataguardRoleRequest,ChangeDataguardRoleResponse> handler)
DatabaseAsync
Switch the Autonomous Container Database role between Standby and Snapshot Standby. For more information about changing Autonomous Container Databases Dataguard Role, see Convert Physical Standby to Snapshot Standby and Convert Snapshot Standby to Physical Standby.
changeDataguardRole
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeDbSystemCompartmentResponse> changeDbSystemCompartment(ChangeDbSystemCompartmentRequest request, AsyncHandler<ChangeDbSystemCompartmentRequest,ChangeDbSystemCompartmentResponse> handler)
DatabaseAsync
Moves the DB system and its dependent resources to the specified compartment. For more information about moving DB systems, see Moving Database Resources to a Different Compartment.
changeDbSystemCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeDisasterRecoveryConfigurationResponse> changeDisasterRecoveryConfiguration(ChangeDisasterRecoveryConfigurationRequest request, AsyncHandler<ChangeDisasterRecoveryConfigurationRequest,ChangeDisasterRecoveryConfigurationResponse> handler)
DatabaseAsync
This operation updates the cross-region disaster recovery (DR) details of the standby Autonomous Database Serverless database, and must be run on the standby side.
changeDisasterRecoveryConfiguration
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeExadataInfrastructureCompartmentResponse> changeExadataInfrastructureCompartment(ChangeExadataInfrastructureCompartmentRequest request, AsyncHandler<ChangeExadataInfrastructureCompartmentRequest,ChangeExadataInfrastructureCompartmentResponse> handler)
DatabaseAsync
Moves an Exadata infrastructure resource and its dependent resources to another compartment.
Applies to Exadata Cloud@Customer instances only. To move an Exadata Cloud Service
infrastructure resource to another compartment, use the changeCloudExadataInfrastructureCompartment
operation.
changeExadataInfrastructureCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeExadbVmClusterCompartmentResponse> changeExadbVmClusterCompartment(ChangeExadbVmClusterCompartmentRequest request, AsyncHandler<ChangeExadbVmClusterCompartmentRequest,ChangeExadbVmClusterCompartmentResponse> handler)
DatabaseAsync
Moves a Exadata VM cluster on Exascale Infrastructure and its dependent resources to another compartment. Applies to Exadata Database Service on Exascale Infrastructure only.
changeExadbVmClusterCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeExascaleDbStorageVaultCompartmentResponse> changeExascaleDbStorageVaultCompartment(ChangeExascaleDbStorageVaultCompartmentRequest request, AsyncHandler<ChangeExascaleDbStorageVaultCompartmentRequest,ChangeExascaleDbStorageVaultCompartmentResponse> handler)
DatabaseAsync
Moves a Exadata Database Storage Vault to another compartment.
changeExascaleDbStorageVaultCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeExternalContainerDatabaseCompartmentResponse> changeExternalContainerDatabaseCompartment(ChangeExternalContainerDatabaseCompartmentRequest request, AsyncHandler<ChangeExternalContainerDatabaseCompartmentRequest,ChangeExternalContainerDatabaseCompartmentResponse> handler)
DatabaseAsync
Move the createExternalContainerDatabaseDetails
and its dependent resources to
the specified compartment. For more information about moving external container databases,
see Moving Database Resources to a Different
Compartment.
changeExternalContainerDatabaseCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeExternalNonContainerDatabaseCompartmentResponse> changeExternalNonContainerDatabaseCompartment(ChangeExternalNonContainerDatabaseCompartmentRequest request, AsyncHandler<ChangeExternalNonContainerDatabaseCompartmentRequest,ChangeExternalNonContainerDatabaseCompartmentResponse> handler)
DatabaseAsync
Move the external non-container database and its dependent resources to the specified compartment. For more information about moving external non-container databases, see Moving Database Resources to a Different Compartment.
changeExternalNonContainerDatabaseCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeExternalPluggableDatabaseCompartmentResponse> changeExternalPluggableDatabaseCompartment(ChangeExternalPluggableDatabaseCompartmentRequest request, AsyncHandler<ChangeExternalPluggableDatabaseCompartmentRequest,ChangeExternalPluggableDatabaseCompartmentResponse> handler)
DatabaseAsync
Move the createExternalPluggableDatabaseDetails
and its dependent resources to
the specified compartment. For more information about moving external pluggable databases,
see Moving Database Resources to a Different
Compartment.
changeExternalPluggableDatabaseCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeKeyStoreCompartmentResponse> changeKeyStoreCompartment(ChangeKeyStoreCompartmentRequest request, AsyncHandler<ChangeKeyStoreCompartmentRequest,ChangeKeyStoreCompartmentResponse> handler)
DatabaseAsync
Move the key store resource to the specified compartment. For more information about moving key stores, see Moving Database Resources to a Different Compartment.
changeKeyStoreCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeKeyStoreTypeResponse> changeKeyStoreType(ChangeKeyStoreTypeRequest request, AsyncHandler<ChangeKeyStoreTypeRequest,ChangeKeyStoreTypeResponse> handler)
DatabaseAsync
Changes encryption key management type
changeKeyStoreType
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeOneoffPatchCompartmentResponse> changeOneoffPatchCompartment(ChangeOneoffPatchCompartmentRequest request, AsyncHandler<ChangeOneoffPatchCompartmentRequest,ChangeOneoffPatchCompartmentResponse> handler)
DatabaseAsync
Move the one-off patch to the specified compartment.
changeOneoffPatchCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeSchedulingPlanCompartmentResponse> changeSchedulingPlanCompartment(ChangeSchedulingPlanCompartmentRequest request, AsyncHandler<ChangeSchedulingPlanCompartmentRequest,ChangeSchedulingPlanCompartmentResponse> handler)
DatabaseAsync
Moves an scheduling plan resource to another compartment.
changeSchedulingPlanCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeSchedulingPolicyCompartmentResponse> changeSchedulingPolicyCompartment(ChangeSchedulingPolicyCompartmentRequest request, AsyncHandler<ChangeSchedulingPolicyCompartmentRequest,ChangeSchedulingPolicyCompartmentResponse> handler)
DatabaseAsync
Moves an scheduling policy resource to another compartment.
changeSchedulingPolicyCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ChangeVmClusterCompartmentResponse> changeVmClusterCompartment(ChangeVmClusterCompartmentRequest request, AsyncHandler<ChangeVmClusterCompartmentRequest,ChangeVmClusterCompartmentResponse> handler)
DatabaseAsync
Moves a VM cluster and its dependent resources to another compartment. Applies to Exadata
Cloud@Customer instances only. To move a cloud VM cluster in an Exadata Cloud Service
instance to another compartment, use the changeCloudVmClusterCompartment
operation.
changeVmClusterCompartment
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CheckExternalDatabaseConnectorConnectionStatusResponse> checkExternalDatabaseConnectorConnectionStatus(CheckExternalDatabaseConnectorConnectionStatusRequest request, AsyncHandler<CheckExternalDatabaseConnectorConnectionStatusRequest,CheckExternalDatabaseConnectorConnectionStatusResponse> handler)
DatabaseAsync
Check the status of the external database connection specified in this connector. This operation will refresh the connectionStatus and timeConnectionStatusLastUpdated fields.
checkExternalDatabaseConnectorConnectionStatus
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CompleteExternalBackupJobResponse> completeExternalBackupJob(CompleteExternalBackupJobRequest request, AsyncHandler<CompleteExternalBackupJobRequest,CompleteExternalBackupJobResponse> handler)
DatabaseAsync
Changes the status of the standalone backup resource to ACTIVE
after the backup is created
from the on-premises database and placed in Oracle Cloud Infrastructure Object Storage.
*Note:** This API is used by an Oracle Cloud Infrastructure Python script that is packaged with the Oracle Cloud Infrastructure CLI. Oracle recommends that you use the script instead using the API directly. See [Migrating an On-Premises Database to Oracle Cloud Infrastructure by Creating a Backup in the Cloud](https://docs.cloud.oracle.com/Content/Database/Tasks/mig-onprembackup.htm) for more information.
completeExternalBackupJob
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ConfigureAutonomousDatabaseVaultKeyResponse> configureAutonomousDatabaseVaultKey(ConfigureAutonomousDatabaseVaultKeyRequest request, AsyncHandler<ConfigureAutonomousDatabaseVaultKeyRequest,ConfigureAutonomousDatabaseVaultKeyResponse> handler)
DatabaseAsync
Configures the Autonomous Database Vault service key.
configureAutonomousDatabaseVaultKey
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ConfigureSaasAdminUserResponse> configureSaasAdminUser(ConfigureSaasAdminUserRequest request, AsyncHandler<ConfigureSaasAdminUserRequest,ConfigureSaasAdminUserResponse> handler)
DatabaseAsync
This operation updates SaaS administrative user configuration of the Autonomous Database.
configureSaasAdminUser
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ConfirmKeyStoreDetailsAreCorrectResponse> confirmKeyStoreDetailsAreCorrect(ConfirmKeyStoreDetailsAreCorrectRequest request, AsyncHandler<ConfirmKeyStoreDetailsAreCorrectRequest,ConfirmKeyStoreDetailsAreCorrectResponse> handler)
DatabaseAsync
This is for user to confirm to DBaaS that the Oracle Key Valut (OKV) connection IPs, username and password are all correct. This operation will put the Key Store back into Active state. If details are incorrect, your OKV account may get locked after some unsuccessful attempts to connect.
confirmKeyStoreDetailsAreCorrect
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ConvertToPdbResponse> convertToPdb(ConvertToPdbRequest request, AsyncHandler<ConvertToPdbRequest,ConvertToPdbResponse> handler)
DatabaseAsync
Converts a non-container database to a pluggable database.
convertToPdb
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<ConvertToRegularPluggableDatabaseResponse> convertToRegularPluggableDatabase(ConvertToRegularPluggableDatabaseRequest request, AsyncHandler<ConvertToRegularPluggableDatabaseRequest,ConvertToRegularPluggableDatabaseResponse> handler)
DatabaseAsync
Converts a Refreshable clone to Regular pluggable database (PDB). Pluggable Database will be
in READ_WRITE
openmode after conversion.
convertToRegularPluggableDatabase
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateApplicationVipResponse> createApplicationVip(CreateApplicationVipRequest request, AsyncHandler<CreateApplicationVipRequest,CreateApplicationVipResponse> handler)
DatabaseAsync
Creates a new application virtual IP (VIP) address in the specified cloud VM cluster based on the request parameters you provide.
createApplicationVip
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateAutonomousContainerDatabaseResponse> createAutonomousContainerDatabase(CreateAutonomousContainerDatabaseRequest request, AsyncHandler<CreateAutonomousContainerDatabaseRequest,CreateAutonomousContainerDatabaseResponse> handler)
DatabaseAsync
Creates an Autonomous Container Database in the specified Autonomous Exadata Infrastructure.
createAutonomousContainerDatabase
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateAutonomousContainerDatabaseDataguardAssociationResponse> createAutonomousContainerDatabaseDataguardAssociation(CreateAutonomousContainerDatabaseDataguardAssociationRequest request, AsyncHandler<CreateAutonomousContainerDatabaseDataguardAssociationRequest,CreateAutonomousContainerDatabaseDataguardAssociationResponse> handler)
DatabaseAsync
Create a new Autonomous Data Guard association. An Autonomous Data Guard association represents the replication relationship between the specified Autonomous Container database and a peer Autonomous Container database. For more information, see Using Oracle Data Guard.
All Oracle Cloud Infrastructure resources, including Data Guard associations, get an Oracle-assigned, unique ID called an Oracle Cloud Identifier (OCID). When you create a resource, you can find its OCID in the response. You can also retrieve a resource's OCID by using a List API operation on that resource type, or by viewing the resource in the Console. For more information, see [Resource Identifiers](https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm).
createAutonomousContainerDatabaseDataguardAssociation
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateAutonomousDatabaseResponse> createAutonomousDatabase(CreateAutonomousDatabaseRequest request, AsyncHandler<CreateAutonomousDatabaseRequest,CreateAutonomousDatabaseResponse> handler)
DatabaseAsync
Creates a new Autonomous Database.
createAutonomousDatabase
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateAutonomousDatabaseBackupResponse> createAutonomousDatabaseBackup(CreateAutonomousDatabaseBackupRequest request, AsyncHandler<CreateAutonomousDatabaseBackupRequest,CreateAutonomousDatabaseBackupResponse> handler)
DatabaseAsync
Creates a new Autonomous Database backup for the specified database based on the provided request parameters.
createAutonomousDatabaseBackup
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateAutonomousDatabaseSoftwareImageResponse> createAutonomousDatabaseSoftwareImage(CreateAutonomousDatabaseSoftwareImageRequest request, AsyncHandler<CreateAutonomousDatabaseSoftwareImageRequest,CreateAutonomousDatabaseSoftwareImageResponse> handler)
DatabaseAsync
create Autonomous Database Software Image in the specified compartment.
createAutonomousDatabaseSoftwareImage
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateAutonomousVmClusterResponse> createAutonomousVmCluster(CreateAutonomousVmClusterRequest request, AsyncHandler<CreateAutonomousVmClusterRequest,CreateAutonomousVmClusterResponse> handler)
DatabaseAsync
Creates an Autonomous VM cluster for Exadata Cloud@Customer. To create an Autonomous VM
Cluster in the Oracle cloud, see createCloudAutonomousVmCluster
.
createAutonomousVmCluster
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateBackupResponse> createBackup(CreateBackupRequest request, AsyncHandler<CreateBackupRequest,CreateBackupResponse> handler)
DatabaseAsync
Creates a new backup in the specified database based on the request parameters you provide. If you previously used RMAN or dbcli to configure backups and then you switch to using the Console or the API for backups, a new backup configuration is created and associated with your database. This means that you can no longer rely on your previously configured unmanaged backups to work.
createBackup
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateBackupDestinationResponse> createBackupDestination(CreateBackupDestinationRequest request, AsyncHandler<CreateBackupDestinationRequest,CreateBackupDestinationResponse> handler)
DatabaseAsync
Creates a backup destination in an Exadata Cloud@Customer system.
createBackupDestination
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateCloudAutonomousVmClusterResponse> createCloudAutonomousVmCluster(CreateCloudAutonomousVmClusterRequest request, AsyncHandler<CreateCloudAutonomousVmClusterRequest,CreateCloudAutonomousVmClusterResponse> handler)
DatabaseAsync
Creates an Autonomous Exadata VM cluster in the Oracle cloud. For Exadata Cloud@Customer
systems, see createAutonomousVmCluster
.
createCloudAutonomousVmCluster
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateCloudExadataInfrastructureResponse> createCloudExadataInfrastructure(CreateCloudExadataInfrastructureRequest request, AsyncHandler<CreateCloudExadataInfrastructureRequest,CreateCloudExadataInfrastructureResponse> handler)
DatabaseAsync
Creates a cloud Exadata infrastructure resource. This resource is used to create either an Exadata Cloud Service instance or an Autonomous Database on dedicated Exadata infrastructure.
createCloudExadataInfrastructure
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateCloudVmClusterResponse> createCloudVmCluster(CreateCloudVmClusterRequest request, AsyncHandler<CreateCloudVmClusterRequest,CreateCloudVmClusterResponse> handler)
DatabaseAsync
Creates a cloud VM cluster.
createCloudVmCluster
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateConsoleConnectionResponse> createConsoleConnection(CreateConsoleConnectionRequest request, AsyncHandler<CreateConsoleConnectionRequest,CreateConsoleConnectionResponse> handler)
DatabaseAsync
Creates a new console connection to the specified database node. After the console connection has been created and is available, you connect to the console using SSH.
createConsoleConnection
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateConsoleHistoryResponse> createConsoleHistory(CreateConsoleHistoryRequest request, AsyncHandler<CreateConsoleHistoryRequest,CreateConsoleHistoryResponse> handler)
DatabaseAsync
Captures the most recent serial console data (up to a megabyte) for the specified database node.
createConsoleHistory
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateDataGuardAssociationResponse> createDataGuardAssociation(CreateDataGuardAssociationRequest request, AsyncHandler<CreateDataGuardAssociationRequest,CreateDataGuardAssociationResponse> handler)
DatabaseAsync
Creates a new Data Guard association. A Data Guard association represents the replication relationship between the specified database and a peer database. For more information, see Using Oracle Data Guard.
All Oracle Cloud Infrastructure resources, including Data Guard associations, get an Oracle-assigned, unique ID called an Oracle Cloud Identifier (OCID). When you create a resource, you can find its OCID in the response. You can also retrieve a resource's OCID by using a List API operation on that resource type, or by viewing the resource in the Console. For more information, see [Resource Identifiers](https://docs.cloud.oracle.com/Content/General/Concepts/identifiers.htm).
createDataGuardAssociation
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateDatabaseResponse> createDatabase(CreateDatabaseRequest request, AsyncHandler<CreateDatabaseRequest,CreateDatabaseResponse> handler)
DatabaseAsync
Creates a new database in the specified Database Home. If the database version is provided, it must match the version of the Database Home. Applies to Exadata and Exadata Cloud@Customer systems.
createDatabase
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateDatabaseSoftwareImageResponse> createDatabaseSoftwareImage(CreateDatabaseSoftwareImageRequest request, AsyncHandler<CreateDatabaseSoftwareImageRequest,CreateDatabaseSoftwareImageResponse> handler)
DatabaseAsync
create database software image in the specified compartment.
createDatabaseSoftwareImage
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateDbHomeResponse> createDbHome(CreateDbHomeRequest request, AsyncHandler<CreateDbHomeRequest,CreateDbHomeResponse> handler)
DatabaseAsync
Creates a new Database Home in the specified database system based on the request parameters you provide. Applies to bare metal DB systems, Exadata systems, and Exadata Cloud@Customer systems.
createDbHome
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateExadataInfrastructureResponse> createExadataInfrastructure(CreateExadataInfrastructureRequest request, AsyncHandler<CreateExadataInfrastructureRequest,CreateExadataInfrastructureResponse> handler)
DatabaseAsync
Creates an Exadata infrastructure resource. Applies to Exadata Cloud@Customer instances only.
To create an Exadata Cloud Service infrastructure resource, use the createCloudExadataInfrastructure
operation.
createExadataInfrastructure
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateExadbVmClusterResponse> createExadbVmCluster(CreateExadbVmClusterRequest request, AsyncHandler<CreateExadbVmClusterRequest,CreateExadbVmClusterResponse> handler)
DatabaseAsync
Creates an Exadata VM cluster on Exascale Infrastructure
createExadbVmCluster
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateExascaleDbStorageVaultResponse> createExascaleDbStorageVault(CreateExascaleDbStorageVaultRequest request, AsyncHandler<CreateExascaleDbStorageVaultRequest,CreateExascaleDbStorageVaultResponse> handler)
DatabaseAsync
Creates an Exadata Database Storage Vault
createExascaleDbStorageVault
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateExecutionActionResponse> createExecutionAction(CreateExecutionActionRequest request, AsyncHandler<CreateExecutionActionRequest,CreateExecutionActionResponse> handler)
DatabaseAsync
Creates an execution action resource.
createExecutionAction
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateExecutionWindowResponse> createExecutionWindow(CreateExecutionWindowRequest request, AsyncHandler<CreateExecutionWindowRequest,CreateExecutionWindowResponse> handler)
DatabaseAsync
Creates an execution window resource.
createExecutionWindow
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateExternalBackupJobResponse> createExternalBackupJob(CreateExternalBackupJobRequest request, AsyncHandler<CreateExternalBackupJobRequest,CreateExternalBackupJobResponse> handler)
DatabaseAsync
Creates a new backup resource and returns the information the caller needs to back up an on-premises Oracle Database to Oracle Cloud Infrastructure.
*Note:** This API is used by an Oracle Cloud Infrastructure Python script that is packaged with the Oracle Cloud Infrastructure CLI. Oracle recommends that you use the script instead using the API directly. See [Migrating an On-Premises Database to Oracle Cloud Infrastructure by Creating a Backup in the Cloud](https://docs.cloud.oracle.com/Content/Database/Tasks/mig-onprembackup.htm) for more information.
createExternalBackupJob
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateExternalContainerDatabaseResponse> createExternalContainerDatabase(CreateExternalContainerDatabaseRequest request, AsyncHandler<CreateExternalContainerDatabaseRequest,CreateExternalContainerDatabaseResponse> handler)
DatabaseAsync
Creates a new external container database resource.
createExternalContainerDatabase
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateExternalDatabaseConnectorResponse> createExternalDatabaseConnector(CreateExternalDatabaseConnectorRequest request, AsyncHandler<CreateExternalDatabaseConnectorRequest,CreateExternalDatabaseConnectorResponse> handler)
DatabaseAsync
Creates a new external database connector.
createExternalDatabaseConnector
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateExternalNonContainerDatabaseResponse> createExternalNonContainerDatabase(CreateExternalNonContainerDatabaseRequest request, AsyncHandler<CreateExternalNonContainerDatabaseRequest,CreateExternalNonContainerDatabaseResponse> handler)
DatabaseAsync
Creates a new ExternalNonContainerDatabase resource
createExternalNonContainerDatabase
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateExternalPluggableDatabaseResponse> createExternalPluggableDatabase(CreateExternalPluggableDatabaseRequest request, AsyncHandler<CreateExternalPluggableDatabaseRequest,CreateExternalPluggableDatabaseResponse> handler)
DatabaseAsync
Registers a new createExternalPluggableDatabaseDetails
resource.
createExternalPluggableDatabase
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateKeyStoreResponse> createKeyStore(CreateKeyStoreRequest request, AsyncHandler<CreateKeyStoreRequest,CreateKeyStoreResponse> handler)
DatabaseAsync
Creates a Key Store.
createKeyStore
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateMaintenanceRunResponse> createMaintenanceRun(CreateMaintenanceRunRequest request, AsyncHandler<CreateMaintenanceRunRequest,CreateMaintenanceRunResponse> handler)
DatabaseAsync
Creates a maintenance run with one of the following: 1. The latest available release update patch (RUP) for the Autonomous Container Database. 2. The latest available RUP and DST time-zone (TZ) file updates for the Autonomous Container Database. 3. The DST TZ file updates for the Autonomous Container Database.
createMaintenanceRun
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateOneoffPatchResponse> createOneoffPatch(CreateOneoffPatchRequest request, AsyncHandler<CreateOneoffPatchRequest,CreateOneoffPatchResponse> handler)
DatabaseAsync
Creates one-off patch for specified database version to download.
createOneoffPatch
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreatePluggableDatabaseResponse> createPluggableDatabase(CreatePluggableDatabaseRequest request, AsyncHandler<CreatePluggableDatabaseRequest,CreatePluggableDatabaseResponse> handler)
DatabaseAsync
Creates and starts a pluggable database in the specified container database. Pluggable
Database can be created using different operations (e.g. LocalClone, RemoteClone, Relocate )
with this API. Use the startPluggableDatabase
and stopPluggableDatabase
APIs to start and stop the pluggable database.
createPluggableDatabase
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateScheduledActionResponse> createScheduledAction(CreateScheduledActionRequest request, AsyncHandler<CreateScheduledActionRequest,CreateScheduledActionResponse> handler)
DatabaseAsync
Creates a Scheduled Action resource.
createScheduledAction
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateSchedulingPlanResponse> createSchedulingPlan(CreateSchedulingPlanRequest request, AsyncHandler<CreateSchedulingPlanRequest,CreateSchedulingPlanResponse> handler)
DatabaseAsync
Creates a Scheduling Plan resource.
createSchedulingPlan
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateSchedulingPolicyResponse> createSchedulingPolicy(CreateSchedulingPolicyRequest request, AsyncHandler<CreateSchedulingPolicyRequest,CreateSchedulingPolicyResponse> handler)
DatabaseAsync
Creates a Scheduling Policy resource.
createSchedulingPolicy
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateSchedulingWindowResponse> createSchedulingWindow(CreateSchedulingWindowRequest request, AsyncHandler<CreateSchedulingWindowRequest,CreateSchedulingWindowResponse> handler)
DatabaseAsync
Creates a Scheduling Window resource.
createSchedulingWindow
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateVmClusterResponse> createVmCluster(CreateVmClusterRequest request, AsyncHandler<CreateVmClusterRequest,CreateVmClusterResponse> handler)
DatabaseAsync
Creates an Exadata Cloud@Customer VM cluster.
createVmCluster
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<CreateVmClusterNetworkResponse> createVmClusterNetwork(CreateVmClusterNetworkRequest request, AsyncHandler<CreateVmClusterNetworkRequest,CreateVmClusterNetworkResponse> handler)
DatabaseAsync
Creates the VM cluster network. Applies to Exadata Cloud@Customer instances only. To create a
cloud VM cluster in an Exadata Cloud Service instance, use the createCloudVmCluster
operation.
createVmClusterNetwork
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DbNodeActionResponse> dbNodeAction(DbNodeActionRequest request, AsyncHandler<DbNodeActionRequest,DbNodeActionResponse> handler)
DatabaseAsync
Performs one of the following power actions on the specified DB node: - start - power on - stop - power off - softreset - ACPI shutdown and power on - reset - power off and power on
*Note:** Stopping a node affects billing differently, depending on the type of DB system:
*Bare metal and Exadata systems* - The _stop_ state has no effect on the resources you
consume. Billing continues for DB nodes that you stop, and related resources continue to
apply against any relevant quotas. You must terminate the DB system (terminateDbSystem
) to
remove its resources from billing and quotas. *Virtual machine DB systems* - Stopping a node
stops billing for all OCPUs associated with that node, and billing resumes when you restart
the node.
dbNodeAction
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteApplicationVipResponse> deleteApplicationVip(DeleteApplicationVipRequest request, AsyncHandler<DeleteApplicationVipRequest,DeleteApplicationVipResponse> handler)
DatabaseAsync
Deletes and deregisters the specified application virtual IP (VIP) address.
deleteApplicationVip
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteAutonomousDatabaseResponse> deleteAutonomousDatabase(DeleteAutonomousDatabaseRequest request, AsyncHandler<DeleteAutonomousDatabaseRequest,DeleteAutonomousDatabaseResponse> handler)
DatabaseAsync
Deletes the specified Autonomous Database.
deleteAutonomousDatabase
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteAutonomousDatabaseBackupResponse> deleteAutonomousDatabaseBackup(DeleteAutonomousDatabaseBackupRequest request, AsyncHandler<DeleteAutonomousDatabaseBackupRequest,DeleteAutonomousDatabaseBackupResponse> handler)
DatabaseAsync
Deletes a long-term backup. You cannot delete other backups using this API.
deleteAutonomousDatabaseBackup
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteAutonomousDatabaseSoftwareImageResponse> deleteAutonomousDatabaseSoftwareImage(DeleteAutonomousDatabaseSoftwareImageRequest request, AsyncHandler<DeleteAutonomousDatabaseSoftwareImageRequest,DeleteAutonomousDatabaseSoftwareImageResponse> handler)
DatabaseAsync
Delete an Autonomous Database Software Image
deleteAutonomousDatabaseSoftwareImage
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteAutonomousVmClusterResponse> deleteAutonomousVmCluster(DeleteAutonomousVmClusterRequest request, AsyncHandler<DeleteAutonomousVmClusterRequest,DeleteAutonomousVmClusterResponse> handler)
DatabaseAsync
Deletes the specified Autonomous VM cluster in an Exadata Cloud@Customer system. To delete an
Autonomous VM Cluster in the Oracle cloud, see deleteCloudAutonomousVmCluster
.
deleteAutonomousVmCluster
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteBackupResponse> deleteBackup(DeleteBackupRequest request, AsyncHandler<DeleteBackupRequest,DeleteBackupResponse> handler)
DatabaseAsync
Deletes a full backup. You cannot delete automatic backups using this API.
deleteBackup
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteBackupDestinationResponse> deleteBackupDestination(DeleteBackupDestinationRequest request, AsyncHandler<DeleteBackupDestinationRequest,DeleteBackupDestinationResponse> handler)
DatabaseAsync
Deletes a backup destination in an Exadata Cloud@Customer system.
deleteBackupDestination
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteCloudAutonomousVmClusterResponse> deleteCloudAutonomousVmCluster(DeleteCloudAutonomousVmClusterRequest request, AsyncHandler<DeleteCloudAutonomousVmClusterRequest,DeleteCloudAutonomousVmClusterResponse> handler)
DatabaseAsync
Deletes the specified Autonomous Exadata VM cluster in the Oracle cloud. For Exadata
Cloud@Customer systems, see deleteAutonomousVmCluster
.
deleteCloudAutonomousVmCluster
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteCloudExadataInfrastructureResponse> deleteCloudExadataInfrastructure(DeleteCloudExadataInfrastructureRequest request, AsyncHandler<DeleteCloudExadataInfrastructureRequest,DeleteCloudExadataInfrastructureResponse> handler)
DatabaseAsync
Deletes the cloud Exadata infrastructure resource. Applies to Exadata Cloud Service instances and Autonomous Database on dedicated Exadata infrastructure only.
deleteCloudExadataInfrastructure
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteCloudVmClusterResponse> deleteCloudVmCluster(DeleteCloudVmClusterRequest request, AsyncHandler<DeleteCloudVmClusterRequest,DeleteCloudVmClusterResponse> handler)
DatabaseAsync
Deletes the specified cloud VM cluster. Applies to Exadata Cloud Service instances and Autonomous Database on dedicated Exadata infrastructure only.
deleteCloudVmCluster
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteConsoleConnectionResponse> deleteConsoleConnection(DeleteConsoleConnectionRequest request, AsyncHandler<DeleteConsoleConnectionRequest,DeleteConsoleConnectionResponse> handler)
DatabaseAsync
Deletes the specified database node console connection.
deleteConsoleConnection
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteConsoleHistoryResponse> deleteConsoleHistory(DeleteConsoleHistoryRequest request, AsyncHandler<DeleteConsoleHistoryRequest,DeleteConsoleHistoryResponse> handler)
DatabaseAsync
Deletes the specified database node console history.
deleteConsoleHistory
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteDatabaseResponse> deleteDatabase(DeleteDatabaseRequest request, AsyncHandler<DeleteDatabaseRequest,DeleteDatabaseResponse> handler)
DatabaseAsync
Deletes the specified database. Applies only to Exadata systems.
The data in this database is local to the Exadata system and will be lost when the database is deleted. Oracle recommends that you back up any data in the Exadata system prior to deleting it. You can use the `performFinalBackup` parameter to have the Exadata system database backed up before it is deleted.
deleteDatabase
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteDatabaseSoftwareImageResponse> deleteDatabaseSoftwareImage(DeleteDatabaseSoftwareImageRequest request, AsyncHandler<DeleteDatabaseSoftwareImageRequest,DeleteDatabaseSoftwareImageResponse> handler)
DatabaseAsync
Delete a database software image
deleteDatabaseSoftwareImage
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteDbHomeResponse> deleteDbHome(DeleteDbHomeRequest request, AsyncHandler<DeleteDbHomeRequest,DeleteDbHomeResponse> handler)
DatabaseAsync
Deletes a Database Home. Applies to bare metal DB systems, Exadata Cloud Service, and Exadata Cloud@Customer systems.
Oracle recommends that you use the `performFinalBackup` parameter to back up any data on a bare metal DB system before you delete a Database Home. On an Exadata Cloud@Customer system or an Exadata Cloud Service system, you can delete a Database Home only when there are no databases in it and therefore you cannot use the `performFinalBackup` parameter to back up data.
deleteDbHome
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteExadataInfrastructureResponse> deleteExadataInfrastructure(DeleteExadataInfrastructureRequest request, AsyncHandler<DeleteExadataInfrastructureRequest,DeleteExadataInfrastructureResponse> handler)
DatabaseAsync
Deletes the Exadata Cloud@Customer infrastructure.
deleteExadataInfrastructure
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteExadbVmClusterResponse> deleteExadbVmCluster(DeleteExadbVmClusterRequest request, AsyncHandler<DeleteExadbVmClusterRequest,DeleteExadbVmClusterResponse> handler)
DatabaseAsync
Deletes the specified Exadata VM cluster on Exascale Infrastructure. Applies to Exadata Database Service on Exascale Infrastructure only.
deleteExadbVmCluster
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteExascaleDbStorageVaultResponse> deleteExascaleDbStorageVault(DeleteExascaleDbStorageVaultRequest request, AsyncHandler<DeleteExascaleDbStorageVaultRequest,DeleteExascaleDbStorageVaultResponse> handler)
DatabaseAsync
Deletes the specified Exadata Database Storage Vault.
deleteExascaleDbStorageVault
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteExecutionActionResponse> deleteExecutionAction(DeleteExecutionActionRequest request, AsyncHandler<DeleteExecutionActionRequest,DeleteExecutionActionResponse> handler)
DatabaseAsync
Deletes the execution action.
deleteExecutionAction
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteExecutionWindowResponse> deleteExecutionWindow(DeleteExecutionWindowRequest request, AsyncHandler<DeleteExecutionWindowRequest,DeleteExecutionWindowResponse> handler)
DatabaseAsync
Deletes the execution window.
deleteExecutionWindow
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteExternalContainerDatabaseResponse> deleteExternalContainerDatabase(DeleteExternalContainerDatabaseRequest request, AsyncHandler<DeleteExternalContainerDatabaseRequest,DeleteExternalContainerDatabaseResponse> handler)
DatabaseAsync
Deletes the createExternalContainerDatabaseDetails
resource. Any external pluggable
databases registered under this container database must be deleted in your Oracle Cloud
Infrastructure tenancy prior to this operation.
deleteExternalContainerDatabase
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteExternalDatabaseConnectorResponse> deleteExternalDatabaseConnector(DeleteExternalDatabaseConnectorRequest request, AsyncHandler<DeleteExternalDatabaseConnectorRequest,DeleteExternalDatabaseConnectorResponse> handler)
DatabaseAsync
Deletes an external database connector. Any services enabled using the external database connector must be deleted prior to this operation.
deleteExternalDatabaseConnector
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteExternalNonContainerDatabaseResponse> deleteExternalNonContainerDatabase(DeleteExternalNonContainerDatabaseRequest request, AsyncHandler<DeleteExternalNonContainerDatabaseRequest,DeleteExternalNonContainerDatabaseResponse> handler)
DatabaseAsync
Deletes the Oracle Cloud Infrastructure resource representing an external non-container database.
deleteExternalNonContainerDatabase
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteExternalPluggableDatabaseResponse> deleteExternalPluggableDatabase(DeleteExternalPluggableDatabaseRequest request, AsyncHandler<DeleteExternalPluggableDatabaseRequest,DeleteExternalPluggableDatabaseResponse> handler)
DatabaseAsync
Deletes the createExternalPluggableDatabaseDetails
. resource.
deleteExternalPluggableDatabase
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteKeyStoreResponse> deleteKeyStore(DeleteKeyStoreRequest request, AsyncHandler<DeleteKeyStoreRequest,DeleteKeyStoreResponse> handler)
DatabaseAsync
Deletes a key store.
deleteKeyStore
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteOneoffPatchResponse> deleteOneoffPatch(DeleteOneoffPatchRequest request, AsyncHandler<DeleteOneoffPatchRequest,DeleteOneoffPatchResponse> handler)
DatabaseAsync
Deletes a one-off patch.
deleteOneoffPatch
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeletePluggableDatabaseResponse> deletePluggableDatabase(DeletePluggableDatabaseRequest request, AsyncHandler<DeletePluggableDatabaseRequest,DeletePluggableDatabaseResponse> handler)
DatabaseAsync
Deletes the specified pluggable database.
deletePluggableDatabase
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteScheduledActionResponse> deleteScheduledAction(DeleteScheduledActionRequest request, AsyncHandler<DeleteScheduledActionRequest,DeleteScheduledActionResponse> handler)
DatabaseAsync
Deletes the scheduled action.
deleteScheduledAction
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteSchedulingPlanResponse> deleteSchedulingPlan(DeleteSchedulingPlanRequest request, AsyncHandler<DeleteSchedulingPlanRequest,DeleteSchedulingPlanResponse> handler)
DatabaseAsync
Deletes the scheduling plan.
deleteSchedulingPlan
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteSchedulingPolicyResponse> deleteSchedulingPolicy(DeleteSchedulingPolicyRequest request, AsyncHandler<DeleteSchedulingPolicyRequest,DeleteSchedulingPolicyResponse> handler)
DatabaseAsync
Deletes the scheduling policy.
deleteSchedulingPolicy
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteSchedulingWindowResponse> deleteSchedulingWindow(DeleteSchedulingWindowRequest request, AsyncHandler<DeleteSchedulingWindowRequest,DeleteSchedulingWindowResponse> handler)
DatabaseAsync
Deletes the scheduling window.
deleteSchedulingWindow
in interface DatabaseAsync
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.public Future<DeleteVmClusterResponse> deleteVmCluster(DeleteVmClusterRequest request, AsyncHandler<DeleteVmClusterRequest,DeleteVmClusterResponse> handler)
DatabaseAsync
Deletes the specified VM cluster. Applies to Exadata Cloud@Customer instances only.
deleteVmCluster
in interface DatabaseAsync