Predefined Autonomous Databases Role

Autonomous Databases come with a predefined database role named DWROLE.
This role provides the common privileges for a database developer or data scientist to perform real-time analytics.
Depending on the usage requirements you may also need to grant individual privileges to users.

For more details please refer to the below link:

Ref:

https://docs.oracle.com/en/cloud/paas/autonomous-database/adbsa/manage-users-privileges.html#GUID-50450FAD-9769-4CF7-B0D1-EC14B465B873

Default AWR retention period for Autonomous Database

AWR retention period for Autonomous Database

The default eight-day retention period for Autonomous Database performance data can be modified using
MODIFY_SNAPSHOT_SETTINGS subprogram procedure of DBMS_WORKLOAD_REPOSITORY

Be aware that increasing the retention time results in more storage usage for performance data.

For more details, you can refer to the below link:

https://docs.oracle.com/en/cloud/paas/autonomous-data-warehouse-cloud/user/monitor-performance-intro.html#GUID-4A1E8FCA-FAF1-43F5-93E0-559C0145D6C3

ASM disks Informations

SET LINESIZE 130
SET PAGESIZE 200
COL NAME FORMAT A13 HEADING ‘ASM Diskgroup’
COL DISK_NUMBER FORMAT 99 HEADING ‘DISK#’
COL MODE_STATUS FORMAT A11
COL PATH FORMAT A45
BREAK ON NAME

SELECT g.name
       , disk_number
       , path
       , d.mode_status
       , d.total_mb
       , d.free_mb
FROM   v$asm_disk d
       , v$asm_diskgroup g
WHERE  d.group_number(+) = g.group_number
ORDER  BY name;

ASM Diskgroup DISK# PATH                                          MODE_STATUS   TOTAL_MB    FREE_MB
————- —– ——————————————— ———– ———- ———-
CRS               1 ORCL:ASMDISK7                                 ONLINE           10239       9801
DATA              1 ORCL:ASMDISK6                                 ONLINE          985000     325353
                  0 ORCL:ASMDISK11                                ONLINE          985000     325363
DATA2             0 ORCL:ASMDISK10                                ONLINE          102398      56184
                  1 ORCL:ASMDISK9                                 ONLINE          102398      56184
FRA               1 ORCL:ASMDISK5                                 ONLINE          204797     201362
REDOLOG           1 ORCL:ASMDISK8                                 ONLINE           20479      20342

SYSRAC

select distinct username,status from gv$session where type <> ‘BACKGROUND’ ;

SQL> select distinct username,status from gv$session where type <> ‘BACKGROUND’ ;

USERNAME             STATUS
——————– ——————–
HAFEDA               INACTIVE
SYS                  ACTIVE
SYSRAC               INACTIVE

Separation of Duty for Administering Oracle Real Application Clusters :

Starting with Oracle Database 12c Release 2 (12.2), Oracle Database provides support for separation of duty best practices when administering
Oracle Real Application Clusters (Oracle RAC) by introducing the SYSRAC administrative privilege for the clusterware agent.

This feature removes the need to use the powerful SYSDBA administrative privilege for Oracle RAC.

SYSRAC, like SYSDG, SYSBACKUP and SYSKM, helps enforce separation of duties and reduce reliance on the use of SYSDBA on production systems.
This administrative privilege is the default mode for connecting to the database by the clusterware agent on behalf of the Oracle RAC utilities such as SRVCTL.

Ref:

https://docs.oracle.com/en/database/oracle/oracle-database/12.2/rilin/changes-in-this-release-for-oracle-rac.html#GUID-360D6CC4-46B1-4A74-A413-C2F3BB80472D

Disabling the Flash Recovery Area

Below the actions how to disabling and roll backing the FRA.

Before disabling the FRA we will take an overview of the below parameters for roll backing operation when is needed.

SQL> show parameter recovery

db_recovery_file_dest_size  big integer 4122M
db_recovery_file_dest  string   /u01/app/oracle/fast_recovery_area

Disabling the Flash Recovery Area

To disable the flash recovery area, set the DB_RECOVERY_FILE_DEST initialzation parameter to a null string.

ALTER SYSTEM SET DB_RECOVERY_FILE_DEST=” SCOPE=BOTH SID=”*”;

The database will no longer provide the space management features of the flash recovery area for the files stored in the old DB_RECOVERY_FILE_DEST location.
The files will still be known to the RMAN repository, however, and available for backup and restore activities.

Examples :

ALTER SYSTEM SET DB_RECOVERY_FILE_DEST = ” scope=both;

To set a new destination for the archivelogs:

ALTER SYSTEM SET LOG_ARCHIVE_DEST=’/u04/archlog’ scope=both;

rollback:

ALTER SYSTEM SET db_recovery_file_dest_size=4122M scope=both;
ALTER SYSTEM SET DB_RECOVERY_FILE_DEST=’/u01/app/oracle/fast_recovery_area’ scope=both;

Note:

We need always specify the size parameter before specifying the location parameter.
In a RAC database, all instances must have the same values for these parameters.

Ref:

How to disable use of Flash Recovery Area for Archivelogs and Backups (Doc ID 297397.1)
https://docs.oracle.com/cd/B19306_01/backup.102/b14192/setup005.htm