Oracle Cloud Infrastructure v2.28.0 published on Thursday, Mar 27, 2025 by Pulumi
oci.DatabaseManagement.getExternalExadataStorageServerIormPlan
Explore with Pulumi AI
This data source provides details about a specific External Exadata Storage Server Iorm Plan resource in Oracle Cloud Infrastructure Database Management service.
Get the IORM plan from the specific Exadata storage server.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";
const testExternalExadataStorageServerIormPlan = oci.DatabaseManagement.getExternalExadataStorageServerIormPlan({
externalExadataStorageServerId: testExternalExadataStorageServer.id,
});
import pulumi
import pulumi_oci as oci
test_external_exadata_storage_server_iorm_plan = oci.DatabaseManagement.get_external_exadata_storage_server_iorm_plan(external_exadata_storage_server_id=test_external_exadata_storage_server["id"])
package main
import (
"github.com/pulumi/pulumi-oci/sdk/v2/go/oci/databasemanagement"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := databasemanagement.GetExternalExadataStorageServerIormPlan(ctx, &databasemanagement.GetExternalExadataStorageServerIormPlanArgs{
ExternalExadataStorageServerId: testExternalExadataStorageServer.Id,
}, nil)
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Oci = Pulumi.Oci;
return await Deployment.RunAsync(() =>
{
var testExternalExadataStorageServerIormPlan = Oci.DatabaseManagement.GetExternalExadataStorageServerIormPlan.Invoke(new()
{
ExternalExadataStorageServerId = testExternalExadataStorageServer.Id,
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.oci.DatabaseManagement.DatabaseManagementFunctions;
import com.pulumi.oci.DatabaseManagement.inputs.GetExternalExadataStorageServerIormPlanArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
final var testExternalExadataStorageServerIormPlan = DatabaseManagementFunctions.getExternalExadataStorageServerIormPlan(GetExternalExadataStorageServerIormPlanArgs.builder()
.externalExadataStorageServerId(testExternalExadataStorageServer.id())
.build());
}
}
variables:
testExternalExadataStorageServerIormPlan:
fn::invoke:
function: oci:DatabaseManagement:getExternalExadataStorageServerIormPlan
arguments:
externalExadataStorageServerId: ${testExternalExadataStorageServer.id}
Using getExternalExadataStorageServerIormPlan
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getExternalExadataStorageServerIormPlan(args: GetExternalExadataStorageServerIormPlanArgs, opts?: InvokeOptions): Promise<GetExternalExadataStorageServerIormPlanResult>
function getExternalExadataStorageServerIormPlanOutput(args: GetExternalExadataStorageServerIormPlanOutputArgs, opts?: InvokeOptions): Output<GetExternalExadataStorageServerIormPlanResult>
def get_external_exadata_storage_server_iorm_plan(external_exadata_storage_server_id: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetExternalExadataStorageServerIormPlanResult
def get_external_exadata_storage_server_iorm_plan_output(external_exadata_storage_server_id: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetExternalExadataStorageServerIormPlanResult]
func GetExternalExadataStorageServerIormPlan(ctx *Context, args *GetExternalExadataStorageServerIormPlanArgs, opts ...InvokeOption) (*GetExternalExadataStorageServerIormPlanResult, error)
func GetExternalExadataStorageServerIormPlanOutput(ctx *Context, args *GetExternalExadataStorageServerIormPlanOutputArgs, opts ...InvokeOption) GetExternalExadataStorageServerIormPlanResultOutput
> Note: This function is named GetExternalExadataStorageServerIormPlan
in the Go SDK.
public static class GetExternalExadataStorageServerIormPlan
{
public static Task<GetExternalExadataStorageServerIormPlanResult> InvokeAsync(GetExternalExadataStorageServerIormPlanArgs args, InvokeOptions? opts = null)
public static Output<GetExternalExadataStorageServerIormPlanResult> Invoke(GetExternalExadataStorageServerIormPlanInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetExternalExadataStorageServerIormPlanResult> getExternalExadataStorageServerIormPlan(GetExternalExadataStorageServerIormPlanArgs args, InvokeOptions options)
public static Output<GetExternalExadataStorageServerIormPlanResult> getExternalExadataStorageServerIormPlan(GetExternalExadataStorageServerIormPlanArgs args, InvokeOptions options)
fn::invoke:
function: oci:DatabaseManagement/getExternalExadataStorageServerIormPlan:getExternalExadataStorageServerIormPlan
arguments:
# arguments dictionary
The following arguments are supported:
- External
Exadata Storage Server Id This property is required. string - The OCID of the Exadata storage server.
- External
Exadata Storage Server Id This property is required. string - The OCID of the Exadata storage server.
- external
Exadata Storage Server Id This property is required. String - The OCID of the Exadata storage server.
- external
Exadata Storage Server Id This property is required. string - The OCID of the Exadata storage server.
- external_
exadata_ storage_ server_ id This property is required. str - The OCID of the Exadata storage server.
- external
Exadata Storage Server Id This property is required. String - The OCID of the Exadata storage server.
getExternalExadataStorageServerIormPlan Result
The following output properties are available:
- Db
Plans List<GetExternal Exadata Storage Server Iorm Plan Db Plan> - The resource allocation directives must all use the share attribute, or they must all use the level and allocation attributes. If you use the share attribute to allocate I/O resources, then the database plan can have a maximum of 1024 directives. If you use the level and allocation attributes to allocate I/O resources, then the database plan can have a maximum of 32 directives. Only one directive is allowed for each database name and each profile name.
- External
Exadata stringStorage Server Id - Id string
- The provider-assigned unique ID for this managed resource.
- Plan
Objective string - The objective of the IORM plan.
- Plan
Status string - The status of the IORM plan.
- Db
Plans []GetExternal Exadata Storage Server Iorm Plan Db Plan - The resource allocation directives must all use the share attribute, or they must all use the level and allocation attributes. If you use the share attribute to allocate I/O resources, then the database plan can have a maximum of 1024 directives. If you use the level and allocation attributes to allocate I/O resources, then the database plan can have a maximum of 32 directives. Only one directive is allowed for each database name and each profile name.
- External
Exadata stringStorage Server Id - Id string
- The provider-assigned unique ID for this managed resource.
- Plan
Objective string - The objective of the IORM plan.
- Plan
Status string - The status of the IORM plan.
- db
Plans List<GetExternal Exadata Storage Server Iorm Plan Db Plan> - The resource allocation directives must all use the share attribute, or they must all use the level and allocation attributes. If you use the share attribute to allocate I/O resources, then the database plan can have a maximum of 1024 directives. If you use the level and allocation attributes to allocate I/O resources, then the database plan can have a maximum of 32 directives. Only one directive is allowed for each database name and each profile name.
- external
Exadata StringStorage Server Id - id String
- The provider-assigned unique ID for this managed resource.
- plan
Objective String - The objective of the IORM plan.
- plan
Status String - The status of the IORM plan.
- db
Plans GetExternal Exadata Storage Server Iorm Plan Db Plan[] - The resource allocation directives must all use the share attribute, or they must all use the level and allocation attributes. If you use the share attribute to allocate I/O resources, then the database plan can have a maximum of 1024 directives. If you use the level and allocation attributes to allocate I/O resources, then the database plan can have a maximum of 32 directives. Only one directive is allowed for each database name and each profile name.
- external
Exadata stringStorage Server Id - id string
- The provider-assigned unique ID for this managed resource.
- plan
Objective string - The objective of the IORM plan.
- plan
Status string - The status of the IORM plan.
- db_
plans Sequence[databasemanagement.Get External Exadata Storage Server Iorm Plan Db Plan] - The resource allocation directives must all use the share attribute, or they must all use the level and allocation attributes. If you use the share attribute to allocate I/O resources, then the database plan can have a maximum of 1024 directives. If you use the level and allocation attributes to allocate I/O resources, then the database plan can have a maximum of 32 directives. Only one directive is allowed for each database name and each profile name.
- external_
exadata_ strstorage_ server_ id - id str
- The provider-assigned unique ID for this managed resource.
- plan_
objective str - The objective of the IORM plan.
- plan_
status str - The status of the IORM plan.
- db
Plans List<Property Map> - The resource allocation directives must all use the share attribute, or they must all use the level and allocation attributes. If you use the share attribute to allocate I/O resources, then the database plan can have a maximum of 1024 directives. If you use the level and allocation attributes to allocate I/O resources, then the database plan can have a maximum of 32 directives. Only one directive is allowed for each database name and each profile name.
- external
Exadata StringStorage Server Id - id String
- The provider-assigned unique ID for this managed resource.
- plan
Objective String - The objective of the IORM plan.
- plan
Status String - The status of the IORM plan.
Supporting Types
GetExternalExadataStorageServerIormPlanDbPlan
- Items
This property is required. List<GetExternal Exadata Storage Server Iorm Plan Db Plan Item> - A list of DatabasePlanDirectives.
- Items
This property is required. []GetExternal Exadata Storage Server Iorm Plan Db Plan Item - A list of DatabasePlanDirectives.
- items
This property is required. List<GetExternal Exadata Storage Server Iorm Plan Db Plan Item> - A list of DatabasePlanDirectives.
- items
This property is required. GetExternal Exadata Storage Server Iorm Plan Db Plan Item[] - A list of DatabasePlanDirectives.
- items
This property is required. Sequence[databasemanagement.Get External Exadata Storage Server Iorm Plan Db Plan Item] - A list of DatabasePlanDirectives.
- items
This property is required. List<Property Map> - A list of DatabasePlanDirectives.
GetExternalExadataStorageServerIormPlanDbPlanItem
- Allocation
This property is required. int - The resource allocation as a percentage (0-100) within the level.
- Asm
Cluster This property is required. string - Starting with Oracle Exadata System Software release 19.1.0, you can use the asmcluster attribute to distinguish between databases with the same name running in different Oracle ASM clusters.
- Flash
Cache Limit This property is required. string - Defines a soft limit for space usage in Exadata Smart Flash Cache. If the cache is not full, the limit can be exceeded. You specify the value for flashcachelimit in bytes. You can also use the suffixes M (megabytes), G (gigabytes), or T (terabytes) to specify larger values. For example, 300M, 150G, or 1T. The value for flashcachelimit must be at least 4 MB. The flashcachelimit and flashcachesize attributes cannot be specified in the same directive. The value for flashcachelimit cannot be smaller than flashcachemin, if it is specified.
- Flash
Cache Min This property is required. string - Specifies a minimum guaranteed space allocation in Exadata Smart Flash Cache. You specify the value for flashcachemin in bytes. You can also use the suffixes M (megabytes), G (gigabytes), or T (terabytes) to specify larger values. For example, 300M, 150G, or 1T. The value for flashcachemin must be at least 4 MB. In any plan, the sum of all flashcachemin values cannot exceed the size of Exadata Smart Flash Cache. If flashcachelimit is specified, then the value for flashcachemin cannot exceed flashcachelimit. If flashcachesize is specified, then the value for flashcachemin cannot exceed flashcachesize.
- Flash
Cache Size This property is required. string - Defines a hard limit for space usage in Exadata Smart Flash Cache. The limit cannot be exceeded, even if the cache is not full. In an IORM plan, if the size of Exadata Smart Flash Cache can accommodate all of the flashcachemin and flashcachesize allocations, then each flashcachesize definition represents a guaranteed space allocation. However, starting with Oracle Exadata System Software release 19.2.0 you can use the flashcachesize attribute to over-provision space in Exadata Smart Flash Cache. Consequently, if the size of Exadata Smart Flash Cache cannot accommodate all of the flashcachemin and flashcachesize allocations, then only flashcachemin is guaranteed.
- Is
Flash Cache On This property is required. bool - Controls use of Exadata Smart Flash Cache by a database. This ensures that cache space is reserved for mission-critical databases. flashcache=off is invalid in a directive that contains the flashcachemin, flashcachelimit, or flashcachesize attributes.
- Is
Flash Log On This property is required. bool - Controls use of Exadata Smart Flash Log by a database. This ensures that Exadata Smart Flash Log is reserved for mission-critical databases.
- Is
Pmem Cache On This property is required. bool - Controls use of the persistent memory (PMEM) cache by a database. This ensures that cache space is reserved for mission-critical databases. pmemcache=off is invalid in a directive that contains the pmemcachemin, pmemcachelimit, or pmemcachesize attributes.
- Is
Pmem Log On This property is required. bool - Controls use of persistent memory logging (PMEM log) by a database. This ensures that PMEM log is reserved for mission-critical databases.
- Level
This property is required. int - The allocation level. Valid values are from 1 to 8. Resources are allocated to level 1 first, and then remaining resources are allocated to level 2, and so on.
- Limit
This property is required. int - Name
This property is required. string - The name of a database or a profile.
- Pmem
Cache Limit This property is required. string - Defines a soft limit for space usage in the persistent memory (PMEM) cache. If the cache is not full, the limit can be exceeded. You specify the value for pmemcachelimit in bytes. You can also use the suffixes M (megabytes), G (gigabytes), or T (terabytes) to specify larger values. For example, 300M, 150G, or 1T. The value for pmemcachelimit must be at least 4 MB. The pmemcachelimit and pmemcachesize attributes cannot be specified in the same directive. The value for pmemcachelimit cannot be smaller than pmemcachemin, if it is specified.
- Pmem
Cache Min This property is required. string - Specifies a minimum guaranteed space allocation in the persistent memory (PMEM) cache.
- Pmem
Cache Size This property is required. string - Defines a hard limit for space usage in the persistent memory (PMEM) cache. The limit cannot be exceeded, even if the cache is not full. In an IORM plan, if the size of the PMEM cache can accommodate all of the pmemcachemin and pmemcachesize allocations, then each pmemcachesize definition represents a guaranteed space allocation. However, you can use the pmemcachesize attribute to over-provision space in the PMEM cache. Consequently, if the PMEM cache size cannot accommodate all of the pmemcachemin and pmemcachesize allocations, then only pmemcachemin is guaranteed.
- Role
This property is required. string - Enables you to specify different plan directives based on the Oracle Data Guard database role.
This property is required. int- The relative priority of a database in the database plan. A higher share value implies higher priority and more access to the I/O resources. Use either share or (level, allocation). All plan directives in a database plan should use the same setting. Share-based resource allocation is the recommended method for a database plan.
- Type
This property is required. string - Enables you to create a profile or template, to ease management and configuration of resource plans in environments with many databases.
- type=database: Specifies a directive that applies to a specific database. If type in not specified, then the directive defaults to the database type.
- type=profile: Specifies a directive that applies to a profile rather than a specific database.
- Allocation
This property is required. int - The resource allocation as a percentage (0-100) within the level.
- Asm
Cluster This property is required. string - Starting with Oracle Exadata System Software release 19.1.0, you can use the asmcluster attribute to distinguish between databases with the same name running in different Oracle ASM clusters.
- Flash
Cache Limit This property is required. string - Defines a soft limit for space usage in Exadata Smart Flash Cache. If the cache is not full, the limit can be exceeded. You specify the value for flashcachelimit in bytes. You can also use the suffixes M (megabytes), G (gigabytes), or T (terabytes) to specify larger values. For example, 300M, 150G, or 1T. The value for flashcachelimit must be at least 4 MB. The flashcachelimit and flashcachesize attributes cannot be specified in the same directive. The value for flashcachelimit cannot be smaller than flashcachemin, if it is specified.
- Flash
Cache Min This property is required. string - Specifies a minimum guaranteed space allocation in Exadata Smart Flash Cache. You specify the value for flashcachemin in bytes. You can also use the suffixes M (megabytes), G (gigabytes), or T (terabytes) to specify larger values. For example, 300M, 150G, or 1T. The value for flashcachemin must be at least 4 MB. In any plan, the sum of all flashcachemin values cannot exceed the size of Exadata Smart Flash Cache. If flashcachelimit is specified, then the value for flashcachemin cannot exceed flashcachelimit. If flashcachesize is specified, then the value for flashcachemin cannot exceed flashcachesize.
- Flash
Cache Size This property is required. string - Defines a hard limit for space usage in Exadata Smart Flash Cache. The limit cannot be exceeded, even if the cache is not full. In an IORM plan, if the size of Exadata Smart Flash Cache can accommodate all of the flashcachemin and flashcachesize allocations, then each flashcachesize definition represents a guaranteed space allocation. However, starting with Oracle Exadata System Software release 19.2.0 you can use the flashcachesize attribute to over-provision space in Exadata Smart Flash Cache. Consequently, if the size of Exadata Smart Flash Cache cannot accommodate all of the flashcachemin and flashcachesize allocations, then only flashcachemin is guaranteed.
- Is
Flash Cache On This property is required. bool - Controls use of Exadata Smart Flash Cache by a database. This ensures that cache space is reserved for mission-critical databases. flashcache=off is invalid in a directive that contains the flashcachemin, flashcachelimit, or flashcachesize attributes.
- Is
Flash Log On This property is required. bool - Controls use of Exadata Smart Flash Log by a database. This ensures that Exadata Smart Flash Log is reserved for mission-critical databases.
- Is
Pmem Cache On This property is required. bool - Controls use of the persistent memory (PMEM) cache by a database. This ensures that cache space is reserved for mission-critical databases. pmemcache=off is invalid in a directive that contains the pmemcachemin, pmemcachelimit, or pmemcachesize attributes.
- Is
Pmem Log On This property is required. bool - Controls use of persistent memory logging (PMEM log) by a database. This ensures that PMEM log is reserved for mission-critical databases.
- Level
This property is required. int - The allocation level. Valid values are from 1 to 8. Resources are allocated to level 1 first, and then remaining resources are allocated to level 2, and so on.
- Limit
This property is required. int - Name
This property is required. string - The name of a database or a profile.
- Pmem
Cache Limit This property is required. string - Defines a soft limit for space usage in the persistent memory (PMEM) cache. If the cache is not full, the limit can be exceeded. You specify the value for pmemcachelimit in bytes. You can also use the suffixes M (megabytes), G (gigabytes), or T (terabytes) to specify larger values. For example, 300M, 150G, or 1T. The value for pmemcachelimit must be at least 4 MB. The pmemcachelimit and pmemcachesize attributes cannot be specified in the same directive. The value for pmemcachelimit cannot be smaller than pmemcachemin, if it is specified.
- Pmem
Cache Min This property is required. string - Specifies a minimum guaranteed space allocation in the persistent memory (PMEM) cache.
- Pmem
Cache Size This property is required. string - Defines a hard limit for space usage in the persistent memory (PMEM) cache. The limit cannot be exceeded, even if the cache is not full. In an IORM plan, if the size of the PMEM cache can accommodate all of the pmemcachemin and pmemcachesize allocations, then each pmemcachesize definition represents a guaranteed space allocation. However, you can use the pmemcachesize attribute to over-provision space in the PMEM cache. Consequently, if the PMEM cache size cannot accommodate all of the pmemcachemin and pmemcachesize allocations, then only pmemcachemin is guaranteed.
- Role
This property is required. string - Enables you to specify different plan directives based on the Oracle Data Guard database role.
This property is required. int- The relative priority of a database in the database plan. A higher share value implies higher priority and more access to the I/O resources. Use either share or (level, allocation). All plan directives in a database plan should use the same setting. Share-based resource allocation is the recommended method for a database plan.
- Type
This property is required. string - Enables you to create a profile or template, to ease management and configuration of resource plans in environments with many databases.
- type=database: Specifies a directive that applies to a specific database. If type in not specified, then the directive defaults to the database type.
- type=profile: Specifies a directive that applies to a profile rather than a specific database.
- allocation
This property is required. Integer - The resource allocation as a percentage (0-100) within the level.
- asm
Cluster This property is required. String - Starting with Oracle Exadata System Software release 19.1.0, you can use the asmcluster attribute to distinguish between databases with the same name running in different Oracle ASM clusters.
- flash
Cache Limit This property is required. String - Defines a soft limit for space usage in Exadata Smart Flash Cache. If the cache is not full, the limit can be exceeded. You specify the value for flashcachelimit in bytes. You can also use the suffixes M (megabytes), G (gigabytes), or T (terabytes) to specify larger values. For example, 300M, 150G, or 1T. The value for flashcachelimit must be at least 4 MB. The flashcachelimit and flashcachesize attributes cannot be specified in the same directive. The value for flashcachelimit cannot be smaller than flashcachemin, if it is specified.
- flash
Cache Min This property is required. String - Specifies a minimum guaranteed space allocation in Exadata Smart Flash Cache. You specify the value for flashcachemin in bytes. You can also use the suffixes M (megabytes), G (gigabytes), or T (terabytes) to specify larger values. For example, 300M, 150G, or 1T. The value for flashcachemin must be at least 4 MB. In any plan, the sum of all flashcachemin values cannot exceed the size of Exadata Smart Flash Cache. If flashcachelimit is specified, then the value for flashcachemin cannot exceed flashcachelimit. If flashcachesize is specified, then the value for flashcachemin cannot exceed flashcachesize.
- flash
Cache Size This property is required. String - Defines a hard limit for space usage in Exadata Smart Flash Cache. The limit cannot be exceeded, even if the cache is not full. In an IORM plan, if the size of Exadata Smart Flash Cache can accommodate all of the flashcachemin and flashcachesize allocations, then each flashcachesize definition represents a guaranteed space allocation. However, starting with Oracle Exadata System Software release 19.2.0 you can use the flashcachesize attribute to over-provision space in Exadata Smart Flash Cache. Consequently, if the size of Exadata Smart Flash Cache cannot accommodate all of the flashcachemin and flashcachesize allocations, then only flashcachemin is guaranteed.
- is
Flash Cache On This property is required. Boolean - Controls use of Exadata Smart Flash Cache by a database. This ensures that cache space is reserved for mission-critical databases. flashcache=off is invalid in a directive that contains the flashcachemin, flashcachelimit, or flashcachesize attributes.
- is
Flash Log On This property is required. Boolean - Controls use of Exadata Smart Flash Log by a database. This ensures that Exadata Smart Flash Log is reserved for mission-critical databases.
- is
Pmem Cache On This property is required. Boolean - Controls use of the persistent memory (PMEM) cache by a database. This ensures that cache space is reserved for mission-critical databases. pmemcache=off is invalid in a directive that contains the pmemcachemin, pmemcachelimit, or pmemcachesize attributes.
- is
Pmem Log On This property is required. Boolean - Controls use of persistent memory logging (PMEM log) by a database. This ensures that PMEM log is reserved for mission-critical databases.
- level
This property is required. Integer - The allocation level. Valid values are from 1 to 8. Resources are allocated to level 1 first, and then remaining resources are allocated to level 2, and so on.
- limit
This property is required. Integer - name
This property is required. String - The name of a database or a profile.
- pmem
Cache Limit This property is required. String - Defines a soft limit for space usage in the persistent memory (PMEM) cache. If the cache is not full, the limit can be exceeded. You specify the value for pmemcachelimit in bytes. You can also use the suffixes M (megabytes), G (gigabytes), or T (terabytes) to specify larger values. For example, 300M, 150G, or 1T. The value for pmemcachelimit must be at least 4 MB. The pmemcachelimit and pmemcachesize attributes cannot be specified in the same directive. The value for pmemcachelimit cannot be smaller than pmemcachemin, if it is specified.
- pmem
Cache Min This property is required. String - Specifies a minimum guaranteed space allocation in the persistent memory (PMEM) cache.
- pmem
Cache Size This property is required. String - Defines a hard limit for space usage in the persistent memory (PMEM) cache. The limit cannot be exceeded, even if the cache is not full. In an IORM plan, if the size of the PMEM cache can accommodate all of the pmemcachemin and pmemcachesize allocations, then each pmemcachesize definition represents a guaranteed space allocation. However, you can use the pmemcachesize attribute to over-provision space in the PMEM cache. Consequently, if the PMEM cache size cannot accommodate all of the pmemcachemin and pmemcachesize allocations, then only pmemcachemin is guaranteed.
- role
This property is required. String - Enables you to specify different plan directives based on the Oracle Data Guard database role.
This property is required. Integer- The relative priority of a database in the database plan. A higher share value implies higher priority and more access to the I/O resources. Use either share or (level, allocation). All plan directives in a database plan should use the same setting. Share-based resource allocation is the recommended method for a database plan.
- type
This property is required. String - Enables you to create a profile or template, to ease management and configuration of resource plans in environments with many databases.
- type=database: Specifies a directive that applies to a specific database. If type in not specified, then the directive defaults to the database type.
- type=profile: Specifies a directive that applies to a profile rather than a specific database.
- allocation
This property is required. number - The resource allocation as a percentage (0-100) within the level.
- asm
Cluster This property is required. string - Starting with Oracle Exadata System Software release 19.1.0, you can use the asmcluster attribute to distinguish between databases with the same name running in different Oracle ASM clusters.
- flash
Cache Limit This property is required. string - Defines a soft limit for space usage in Exadata Smart Flash Cache. If the cache is not full, the limit can be exceeded. You specify the value for flashcachelimit in bytes. You can also use the suffixes M (megabytes), G (gigabytes), or T (terabytes) to specify larger values. For example, 300M, 150G, or 1T. The value for flashcachelimit must be at least 4 MB. The flashcachelimit and flashcachesize attributes cannot be specified in the same directive. The value for flashcachelimit cannot be smaller than flashcachemin, if it is specified.
- flash
Cache Min This property is required. string - Specifies a minimum guaranteed space allocation in Exadata Smart Flash Cache. You specify the value for flashcachemin in bytes. You can also use the suffixes M (megabytes), G (gigabytes), or T (terabytes) to specify larger values. For example, 300M, 150G, or 1T. The value for flashcachemin must be at least 4 MB. In any plan, the sum of all flashcachemin values cannot exceed the size of Exadata Smart Flash Cache. If flashcachelimit is specified, then the value for flashcachemin cannot exceed flashcachelimit. If flashcachesize is specified, then the value for flashcachemin cannot exceed flashcachesize.
- flash
Cache Size This property is required. string - Defines a hard limit for space usage in Exadata Smart Flash Cache. The limit cannot be exceeded, even if the cache is not full. In an IORM plan, if the size of Exadata Smart Flash Cache can accommodate all of the flashcachemin and flashcachesize allocations, then each flashcachesize definition represents a guaranteed space allocation. However, starting with Oracle Exadata System Software release 19.2.0 you can use the flashcachesize attribute to over-provision space in Exadata Smart Flash Cache. Consequently, if the size of Exadata Smart Flash Cache cannot accommodate all of the flashcachemin and flashcachesize allocations, then only flashcachemin is guaranteed.
- is
Flash Cache On This property is required. boolean - Controls use of Exadata Smart Flash Cache by a database. This ensures that cache space is reserved for mission-critical databases. flashcache=off is invalid in a directive that contains the flashcachemin, flashcachelimit, or flashcachesize attributes.
- is
Flash Log On This property is required. boolean - Controls use of Exadata Smart Flash Log by a database. This ensures that Exadata Smart Flash Log is reserved for mission-critical databases.
- is
Pmem Cache On This property is required. boolean - Controls use of the persistent memory (PMEM) cache by a database. This ensures that cache space is reserved for mission-critical databases. pmemcache=off is invalid in a directive that contains the pmemcachemin, pmemcachelimit, or pmemcachesize attributes.
- is
Pmem Log On This property is required. boolean - Controls use of persistent memory logging (PMEM log) by a database. This ensures that PMEM log is reserved for mission-critical databases.
- level
This property is required. number - The allocation level. Valid values are from 1 to 8. Resources are allocated to level 1 first, and then remaining resources are allocated to level 2, and so on.
- limit
This property is required. number - name
This property is required. string - The name of a database or a profile.
- pmem
Cache Limit This property is required. string - Defines a soft limit for space usage in the persistent memory (PMEM) cache. If the cache is not full, the limit can be exceeded. You specify the value for pmemcachelimit in bytes. You can also use the suffixes M (megabytes), G (gigabytes), or T (terabytes) to specify larger values. For example, 300M, 150G, or 1T. The value for pmemcachelimit must be at least 4 MB. The pmemcachelimit and pmemcachesize attributes cannot be specified in the same directive. The value for pmemcachelimit cannot be smaller than pmemcachemin, if it is specified.
- pmem
Cache Min This property is required. string - Specifies a minimum guaranteed space allocation in the persistent memory (PMEM) cache.
- pmem
Cache Size This property is required. string - Defines a hard limit for space usage in the persistent memory (PMEM) cache. The limit cannot be exceeded, even if the cache is not full. In an IORM plan, if the size of the PMEM cache can accommodate all of the pmemcachemin and pmemcachesize allocations, then each pmemcachesize definition represents a guaranteed space allocation. However, you can use the pmemcachesize attribute to over-provision space in the PMEM cache. Consequently, if the PMEM cache size cannot accommodate all of the pmemcachemin and pmemcachesize allocations, then only pmemcachemin is guaranteed.
- role
This property is required. string - Enables you to specify different plan directives based on the Oracle Data Guard database role.
This property is required. number- The relative priority of a database in the database plan. A higher share value implies higher priority and more access to the I/O resources. Use either share or (level, allocation). All plan directives in a database plan should use the same setting. Share-based resource allocation is the recommended method for a database plan.
- type
This property is required. string - Enables you to create a profile or template, to ease management and configuration of resource plans in environments with many databases.
- type=database: Specifies a directive that applies to a specific database. If type in not specified, then the directive defaults to the database type.
- type=profile: Specifies a directive that applies to a profile rather than a specific database.
- allocation
This property is required. int - The resource allocation as a percentage (0-100) within the level.
- asm_
cluster This property is required. str - Starting with Oracle Exadata System Software release 19.1.0, you can use the asmcluster attribute to distinguish between databases with the same name running in different Oracle ASM clusters.
- flash_
cache_ limit This property is required. str - Defines a soft limit for space usage in Exadata Smart Flash Cache. If the cache is not full, the limit can be exceeded. You specify the value for flashcachelimit in bytes. You can also use the suffixes M (megabytes), G (gigabytes), or T (terabytes) to specify larger values. For example, 300M, 150G, or 1T. The value for flashcachelimit must be at least 4 MB. The flashcachelimit and flashcachesize attributes cannot be specified in the same directive. The value for flashcachelimit cannot be smaller than flashcachemin, if it is specified.
- flash_
cache_ min This property is required. str - Specifies a minimum guaranteed space allocation in Exadata Smart Flash Cache. You specify the value for flashcachemin in bytes. You can also use the suffixes M (megabytes), G (gigabytes), or T (terabytes) to specify larger values. For example, 300M, 150G, or 1T. The value for flashcachemin must be at least 4 MB. In any plan, the sum of all flashcachemin values cannot exceed the size of Exadata Smart Flash Cache. If flashcachelimit is specified, then the value for flashcachemin cannot exceed flashcachelimit. If flashcachesize is specified, then the value for flashcachemin cannot exceed flashcachesize.
- flash_
cache_ size This property is required. str - Defines a hard limit for space usage in Exadata Smart Flash Cache. The limit cannot be exceeded, even if the cache is not full. In an IORM plan, if the size of Exadata Smart Flash Cache can accommodate all of the flashcachemin and flashcachesize allocations, then each flashcachesize definition represents a guaranteed space allocation. However, starting with Oracle Exadata System Software release 19.2.0 you can use the flashcachesize attribute to over-provision space in Exadata Smart Flash Cache. Consequently, if the size of Exadata Smart Flash Cache cannot accommodate all of the flashcachemin and flashcachesize allocations, then only flashcachemin is guaranteed.
- is_
flash_ cache_ on This property is required. bool - Controls use of Exadata Smart Flash Cache by a database. This ensures that cache space is reserved for mission-critical databases. flashcache=off is invalid in a directive that contains the flashcachemin, flashcachelimit, or flashcachesize attributes.
- is_
flash_ log_ on This property is required. bool - Controls use of Exadata Smart Flash Log by a database. This ensures that Exadata Smart Flash Log is reserved for mission-critical databases.
- is_
pmem_ cache_ on This property is required. bool - Controls use of the persistent memory (PMEM) cache by a database. This ensures that cache space is reserved for mission-critical databases. pmemcache=off is invalid in a directive that contains the pmemcachemin, pmemcachelimit, or pmemcachesize attributes.
- is_
pmem_ log_ on This property is required. bool - Controls use of persistent memory logging (PMEM log) by a database. This ensures that PMEM log is reserved for mission-critical databases.
- level
This property is required. int - The allocation level. Valid values are from 1 to 8. Resources are allocated to level 1 first, and then remaining resources are allocated to level 2, and so on.
- limit
This property is required. int - name
This property is required. str - The name of a database or a profile.
- pmem_
cache_ limit This property is required. str - Defines a soft limit for space usage in the persistent memory (PMEM) cache. If the cache is not full, the limit can be exceeded. You specify the value for pmemcachelimit in bytes. You can also use the suffixes M (megabytes), G (gigabytes), or T (terabytes) to specify larger values. For example, 300M, 150G, or 1T. The value for pmemcachelimit must be at least 4 MB. The pmemcachelimit and pmemcachesize attributes cannot be specified in the same directive. The value for pmemcachelimit cannot be smaller than pmemcachemin, if it is specified.
- pmem_
cache_ min This property is required. str - Specifies a minimum guaranteed space allocation in the persistent memory (PMEM) cache.
- pmem_
cache_ size This property is required. str - Defines a hard limit for space usage in the persistent memory (PMEM) cache. The limit cannot be exceeded, even if the cache is not full. In an IORM plan, if the size of the PMEM cache can accommodate all of the pmemcachemin and pmemcachesize allocations, then each pmemcachesize definition represents a guaranteed space allocation. However, you can use the pmemcachesize attribute to over-provision space in the PMEM cache. Consequently, if the PMEM cache size cannot accommodate all of the pmemcachemin and pmemcachesize allocations, then only pmemcachemin is guaranteed.
- role
This property is required. str - Enables you to specify different plan directives based on the Oracle Data Guard database role.
This property is required. int- The relative priority of a database in the database plan. A higher share value implies higher priority and more access to the I/O resources. Use either share or (level, allocation). All plan directives in a database plan should use the same setting. Share-based resource allocation is the recommended method for a database plan.
- type
This property is required. str - Enables you to create a profile or template, to ease management and configuration of resource plans in environments with many databases.
- type=database: Specifies a directive that applies to a specific database. If type in not specified, then the directive defaults to the database type.
- type=profile: Specifies a directive that applies to a profile rather than a specific database.
- allocation
This property is required. Number - The resource allocation as a percentage (0-100) within the level.
- asm
Cluster This property is required. String - Starting with Oracle Exadata System Software release 19.1.0, you can use the asmcluster attribute to distinguish between databases with the same name running in different Oracle ASM clusters.
- flash
Cache Limit This property is required. String - Defines a soft limit for space usage in Exadata Smart Flash Cache. If the cache is not full, the limit can be exceeded. You specify the value for flashcachelimit in bytes. You can also use the suffixes M (megabytes), G (gigabytes), or T (terabytes) to specify larger values. For example, 300M, 150G, or 1T. The value for flashcachelimit must be at least 4 MB. The flashcachelimit and flashcachesize attributes cannot be specified in the same directive. The value for flashcachelimit cannot be smaller than flashcachemin, if it is specified.
- flash
Cache Min This property is required. String - Specifies a minimum guaranteed space allocation in Exadata Smart Flash Cache. You specify the value for flashcachemin in bytes. You can also use the suffixes M (megabytes), G (gigabytes), or T (terabytes) to specify larger values. For example, 300M, 150G, or 1T. The value for flashcachemin must be at least 4 MB. In any plan, the sum of all flashcachemin values cannot exceed the size of Exadata Smart Flash Cache. If flashcachelimit is specified, then the value for flashcachemin cannot exceed flashcachelimit. If flashcachesize is specified, then the value for flashcachemin cannot exceed flashcachesize.
- flash
Cache Size This property is required. String - Defines a hard limit for space usage in Exadata Smart Flash Cache. The limit cannot be exceeded, even if the cache is not full. In an IORM plan, if the size of Exadata Smart Flash Cache can accommodate all of the flashcachemin and flashcachesize allocations, then each flashcachesize definition represents a guaranteed space allocation. However, starting with Oracle Exadata System Software release 19.2.0 you can use the flashcachesize attribute to over-provision space in Exadata Smart Flash Cache. Consequently, if the size of Exadata Smart Flash Cache cannot accommodate all of the flashcachemin and flashcachesize allocations, then only flashcachemin is guaranteed.
- is
Flash Cache On This property is required. Boolean - Controls use of Exadata Smart Flash Cache by a database. This ensures that cache space is reserved for mission-critical databases. flashcache=off is invalid in a directive that contains the flashcachemin, flashcachelimit, or flashcachesize attributes.
- is
Flash Log On This property is required. Boolean - Controls use of Exadata Smart Flash Log by a database. This ensures that Exadata Smart Flash Log is reserved for mission-critical databases.
- is
Pmem Cache On This property is required. Boolean - Controls use of the persistent memory (PMEM) cache by a database. This ensures that cache space is reserved for mission-critical databases. pmemcache=off is invalid in a directive that contains the pmemcachemin, pmemcachelimit, or pmemcachesize attributes.
- is
Pmem Log On This property is required. Boolean - Controls use of persistent memory logging (PMEM log) by a database. This ensures that PMEM log is reserved for mission-critical databases.
- level
This property is required. Number - The allocation level. Valid values are from 1 to 8. Resources are allocated to level 1 first, and then remaining resources are allocated to level 2, and so on.
- limit
This property is required. Number - name
This property is required. String - The name of a database or a profile.
- pmem
Cache Limit This property is required. String - Defines a soft limit for space usage in the persistent memory (PMEM) cache. If the cache is not full, the limit can be exceeded. You specify the value for pmemcachelimit in bytes. You can also use the suffixes M (megabytes), G (gigabytes), or T (terabytes) to specify larger values. For example, 300M, 150G, or 1T. The value for pmemcachelimit must be at least 4 MB. The pmemcachelimit and pmemcachesize attributes cannot be specified in the same directive. The value for pmemcachelimit cannot be smaller than pmemcachemin, if it is specified.
- pmem
Cache Min This property is required. String - Specifies a minimum guaranteed space allocation in the persistent memory (PMEM) cache.
- pmem
Cache Size This property is required. String - Defines a hard limit for space usage in the persistent memory (PMEM) cache. The limit cannot be exceeded, even if the cache is not full. In an IORM plan, if the size of the PMEM cache can accommodate all of the pmemcachemin and pmemcachesize allocations, then each pmemcachesize definition represents a guaranteed space allocation. However, you can use the pmemcachesize attribute to over-provision space in the PMEM cache. Consequently, if the PMEM cache size cannot accommodate all of the pmemcachemin and pmemcachesize allocations, then only pmemcachemin is guaranteed.
- role
This property is required. String - Enables you to specify different plan directives based on the Oracle Data Guard database role.
This property is required. Number- The relative priority of a database in the database plan. A higher share value implies higher priority and more access to the I/O resources. Use either share or (level, allocation). All plan directives in a database plan should use the same setting. Share-based resource allocation is the recommended method for a database plan.
- type
This property is required. String - Enables you to create a profile or template, to ease management and configuration of resource plans in environments with many databases.
- type=database: Specifies a directive that applies to a specific database. If type in not specified, then the directive defaults to the database type.
- type=profile: Specifies a directive that applies to a profile rather than a specific database.
Package Details
- Repository
- oci pulumi/pulumi-oci
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
oci
Terraform Provider.