Category: ATP

  • Exploring Autonomous Database – Init Parameters

    Exploring Autonomous Database – Init Parameters

    A CDB in Oracle Cloud could host both ATP and ADW (pluggable) databases (see here). Let’s look at the initialization parameter differences at the PDB level for ATP and ADW.  

    ATP has a minimum number of parameters configured, whereas ADW has several initialization parameters. Though my ATP and ADW databases are both 1 oCPU / 1 TB size, the SGA and PGA values are different. ADW has a bigger PGA, ATP has bigger SGA. 

    Init ParameterATPADW
    pga_aggregate_target3000M5100M
    pga_aggregate_limit6000M10200M
    sga_target8000M3400M

    All the parameters set in the ATP database are set in the ADW database as well. ADW has a lot more, though. Here are the parameters from ADW. The first column shows if the parameter is set in ATP or not. 

    ATP?PARAMETER NAMEDISPLAY VALUEDEFAULT VALUE
    _cell_offload_vector_groupbyFALSETRUE
    _cloud_service_typeDWCSNULL
    _datapump_inherit_svcnameTRUEFALSE
    _default_pct_free10
    _enable_parallel_dmlTRUEFALSE
    YES_kd_rows_chkFALSETRUE
    _ldr_io_size33554432262144
    _ldr_io_size2335544321048576
    _max_io_size335544321048576
    _optimizer_answering_ query_using_statsTRUEFALSE
    _optimizer_gather_stats_on_ load_allTRUEFALSE
    _optimizer_gather_stats_on_ load_histTRUEFALSE
    _parallel_cluster_cache_ policyADAPTIVEADAPTIVE
    _pdb_inherit_cfdTRUEFALSE
    _pdb_lockdown_ddl_clauses1310660
    _pdb_max_audit_size200M0
    _pdb_max_diag_size100M0
    _px_xtgranule_size12800010000
    YEScpu_count10
    YES db_lost_write_protectTYPICALNONE
    max_idle_blocker_time50
    YES nls_languageAMERICANAMERICAN
    YESnls_territoryAMERICAAMERICA
    YESofs_threads404
    parallel_degree_policyAUTOMANUAL
    YESparallel_max_servers124294967295
    parallel_min_degreeCPU1
    YESparallel_servers_target120
    YESpga_aggregate_limit10200M0
    YESpga_aggregate_target5100M0
    YESplscope_settingsidentifiers:allIDENTIFIERS:NONE
    YESplsql_optimize_level22
    resource_manager_planFORCE:DWCS_PLANNULL
    result_cache_max_result15
    YESresult_cache_max_size10M1
    result_cache_modeFORCEMANUAL
    YESsessions1004294967295
    YESsga_target3400M0

    Out of the 39 parameters set in ADW, half are underscored parameters!

    The ATP and ADW have two different resource management plans. ADW plan name is DWCS_PLAN and ATP plan name is OLTP_PLAN. The (default) tablespaces are same for ATP and ADW.

  • Exploring Autonomous Database – The CDB

    Exploring Autonomous Database – The CDB

    I am the new kid in the block, wandering around the autonomous database cloud. Let me share something I found interesting. Though on Oracle Cloud Infrastructure, the ATP (Autonomous Transaction Processing) and the ADW (Autonomous Data Warehouse) have two different higher level menu and they appear to be different, they are not.

    Here are two ADW databases I created:

    Autonomous Data Warehouse Instances Created on 10 Sep and 2 Oct. 

    Here are two ATP databases created:

    Autonomous Transaction Processing Instances Created on 10 Sep and 2 Oct.

    Each instance of the ADW and ATP  is a pluggable database. The (pluggable) databases created on Sep 10th – one ATP and one ADW – belonged to the same CDB. Similarly, the (pluggable) databases created on Oct 2 – again one ATP and one ADW – belonged to the same CDB. So, it appears that at the CDB level, both ATP and ADW have the same configuration. The differences are only in the PDB. And my guess is that Oracle creates the new instances (ATP and ADW) in a CDB until that CDB reaches its capacity threshold, then moves to the next CDB.

    The database properties are same as well for ATP and ADW. The only (obviously) difference is the GLOBAL_DB_NAME value.