1. Packages
  2. Oracle Cloud Infrastructure
  3. API Docs
  4. DatabaseManagement
  5. getExternalExadataStorageServerIormPlan
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,
});
Copy
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"])
Copy
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
	})
}
Copy
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,
    });

});
Copy
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());

    }
}
Copy
variables:
  testExternalExadataStorageServerIormPlan:
    fn::invoke:
      function: oci:DatabaseManagement:getExternalExadataStorageServerIormPlan
      arguments:
        externalExadataStorageServerId: ${testExternalExadataStorageServer.id}
Copy

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>
Copy
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]
Copy
func GetExternalExadataStorageServerIormPlan(ctx *Context, args *GetExternalExadataStorageServerIormPlanArgs, opts ...InvokeOption) (*GetExternalExadataStorageServerIormPlanResult, error)
func GetExternalExadataStorageServerIormPlanOutput(ctx *Context, args *GetExternalExadataStorageServerIormPlanOutputArgs, opts ...InvokeOption) GetExternalExadataStorageServerIormPlanResultOutput
Copy

> 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)
}
Copy
public static CompletableFuture<GetExternalExadataStorageServerIormPlanResult> getExternalExadataStorageServerIormPlan(GetExternalExadataStorageServerIormPlanArgs args, InvokeOptions options)
public static Output<GetExternalExadataStorageServerIormPlanResult> getExternalExadataStorageServerIormPlan(GetExternalExadataStorageServerIormPlanArgs args, InvokeOptions options)
Copy
fn::invoke:
  function: oci:DatabaseManagement/getExternalExadataStorageServerIormPlan:getExternalExadataStorageServerIormPlan
  arguments:
    # arguments dictionary
Copy

The following arguments are supported:

ExternalExadataStorageServerId This property is required. string
The OCID of the Exadata storage server.
ExternalExadataStorageServerId This property is required. string
The OCID of the Exadata storage server.
externalExadataStorageServerId This property is required. String
The OCID of the Exadata storage server.
externalExadataStorageServerId 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.
externalExadataStorageServerId This property is required. String
The OCID of the Exadata storage server.

getExternalExadataStorageServerIormPlan Result

The following output properties are available:

DbPlans List<GetExternalExadataStorageServerIormPlanDbPlan>
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.
ExternalExadataStorageServerId string
Id string
The provider-assigned unique ID for this managed resource.
PlanObjective string
The objective of the IORM plan.
PlanStatus string
The status of the IORM plan.
DbPlans []GetExternalExadataStorageServerIormPlanDbPlan
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.
ExternalExadataStorageServerId string
Id string
The provider-assigned unique ID for this managed resource.
PlanObjective string
The objective of the IORM plan.
PlanStatus string
The status of the IORM plan.
dbPlans List<GetExternalExadataStorageServerIormPlanDbPlan>
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.
externalExadataStorageServerId String
id String
The provider-assigned unique ID for this managed resource.
planObjective String
The objective of the IORM plan.
planStatus String
The status of the IORM plan.
dbPlans GetExternalExadataStorageServerIormPlanDbPlan[]
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.
externalExadataStorageServerId string
id string
The provider-assigned unique ID for this managed resource.
planObjective string
The objective of the IORM plan.
planStatus string
The status of the IORM plan.
db_plans Sequence[databasemanagement.GetExternalExadataStorageServerIormPlanDbPlan]
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_storage_server_id str
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.
dbPlans 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.
externalExadataStorageServerId String
id String
The provider-assigned unique ID for this managed resource.
planObjective String
The objective of the IORM plan.
planStatus String
The status of the IORM plan.

Supporting Types

GetExternalExadataStorageServerIormPlanDbPlan

Items This property is required. List<GetExternalExadataStorageServerIormPlanDbPlanItem>
A list of DatabasePlanDirectives.
Items This property is required. []GetExternalExadataStorageServerIormPlanDbPlanItem
A list of DatabasePlanDirectives.
items This property is required. List<GetExternalExadataStorageServerIormPlanDbPlanItem>
A list of DatabasePlanDirectives.
items This property is required. GetExternalExadataStorageServerIormPlanDbPlanItem[]
A list of DatabasePlanDirectives.
items This property is required. Sequence[databasemanagement.GetExternalExadataStorageServerIormPlanDbPlanItem]
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.
AsmCluster 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.
FlashCacheLimit 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.
FlashCacheMin 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.
FlashCacheSize 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.
IsFlashCacheOn 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.
IsFlashLogOn 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.
IsPmemCacheOn 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.
IsPmemLogOn 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.
PmemCacheLimit 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.
PmemCacheMin This property is required. string
Specifies a minimum guaranteed space allocation in the persistent memory (PMEM) cache.
PmemCacheSize 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.
Share 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.
AsmCluster 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.
FlashCacheLimit 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.
FlashCacheMin 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.
FlashCacheSize 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.
IsFlashCacheOn 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.
IsFlashLogOn 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.
IsPmemCacheOn 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.
IsPmemLogOn 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.
PmemCacheLimit 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.
PmemCacheMin This property is required. string
Specifies a minimum guaranteed space allocation in the persistent memory (PMEM) cache.
PmemCacheSize 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.
Share 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.
asmCluster 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.
flashCacheLimit 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.
flashCacheMin 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.
flashCacheSize 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.
isFlashCacheOn 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.
isFlashLogOn 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.
isPmemCacheOn 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.
isPmemLogOn 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.
pmemCacheLimit 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.
pmemCacheMin This property is required. String
Specifies a minimum guaranteed space allocation in the persistent memory (PMEM) cache.
pmemCacheSize 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.
share 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.
asmCluster 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.
flashCacheLimit 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.
flashCacheMin 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.
flashCacheSize 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.
isFlashCacheOn 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.
isFlashLogOn 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.
isPmemCacheOn 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.
isPmemLogOn 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.
pmemCacheLimit 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.
pmemCacheMin This property is required. string
Specifies a minimum guaranteed space allocation in the persistent memory (PMEM) cache.
pmemCacheSize 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.
share 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.
share 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.
asmCluster 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.
flashCacheLimit 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.
flashCacheMin 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.
flashCacheSize 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.
isFlashCacheOn 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.
isFlashLogOn 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.
isPmemCacheOn 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.
isPmemLogOn 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.
pmemCacheLimit 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.
pmemCacheMin This property is required. String
Specifies a minimum guaranteed space allocation in the persistent memory (PMEM) cache.
pmemCacheSize 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.
share 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.