Loading...

Follow ORACLE-HELP - Oracle DBA and Cloud Articles on Feedspot

Continue with Google
Continue with Facebook
or

Valid

RMAN : RMAN is an Oracle Database client and every DBA’s favorite tool for backup and recovery of the database. We have many RMAN related posts which can help you in all scenarios .

However, today we will see a basic RMAN commands that will show what RMAN offers you. This post is mainly for DBAs who want to explore RMAN from scratch

To connect RMAN for your particular database , you need to use target clause , let us see how

[oracle@dbatesting ~]$ export ORACLE_SID=orcl1
[oracle@dbatesting ~]$ rman target /

Recovery Manager: Release 12.2.0.1.0 - Production on Thu May 9 21:07:59 2019

Copyright (c) 1982, 2017, Oracle and/or its affiliates.  All rights reserved.

connected to target database: ORCL1 (DBID=1383488253)

RMAN>

Just set your ORACLE_SID and give / for your target , your database will connected to your desired database

Every DBA’s second command will be show all where you will see list of configuration with your database .

Note : If your database is new then you will see default configurations for each configuration

RMAN> show all;

using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name ORCL1 are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/12.2.0.1/db_1/dbs/snapcf_orcl1.f'; # default

Now, if your database has already have some backup taken previously we can check it using list backup command .

RMAN> list backup;


List of Backup Sets
===================


BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
1       Full    17.94M     DISK        00:00:07     31-JAN-19      
        BP Key: 1   Status: EXPIRED  Compressed: NO  Tag: TAG20190131T233122
        Piece Name: /u01/app/oracle/fast_recovery_area/orcl1/ORCL1/autobackup/2019_01_31/o1_mf_s_999041482_g56fzs1j_.bkp
  SPFILE Included: Modification time: 31-JAN-19
  SPFILE db_unique_name: ORCL1
  Control File Included: Ckp SCN: 1444586      Ckp time: 31-JAN-19

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
2       Full    17.94M     DISK        00:00:02     10-FEB-19      
        BP Key: 2   Status: AVAILABLE  Compressed: NO  Tag: TAG20190210T102914
        Piece Name: /u01/app/oracle/fast_recovery_area/orcl1/ORCL1/autobackup/2019_02_10/o1_mf_s_999858554_g5zcx47j_.bkp
  SPFILE Included: Modification time: 10-FEB-19
  SPFILE db_unique_name: ORCL1
  Control File Included: Ckp SCN: 1547969      Ckp time: 10-FEB-19

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
3       Full    17.94M     DISK        00:00:17     10-FEB-19      
        BP Key: 3   Status: AVAILABLE  Compressed: NO  Tag: TAG20190210T220953
        Piece Name: /u01/app/oracle/fast_recovery_area/orcl1/ORCL1/autobackup/2019_02_10/o1_mf_s_999900594_g60nzcsd_.bkp
  SPFILE Included: Modification time: 10-FEB-19
  SPFILE db_unique_name: ORCL1
  Control File Included: Ckp SCN: 1698850      Ckp time: 10-FEB-19

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
4       Full    17.94M     DISK        00:00:01     10-FEB-19      
        BP Key: 4   Status: AVAILABLE  Compressed: NO  Tag: TAG20190210T233519
        Piece Name: /u01/app/oracle/fast_recovery_area/orcl1/ORCL1/autobackup/2019_02_10/o1_mf_s_999905720_g60sz1lg_.bkp
  SPFILE Included: Modification time: 10-FEB-19
  SPFILE db_unique_name: ORCL1
  Control File Included: Ckp SCN: 1717829      Ckp time: 10-FEB-19

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
6       Full    557.34M    DISK        00:01:10     09-MAY-19      
        BP Key: 6   Status: AVAILABLE  Compressed: NO  Tag: TAG20190509T211650
        Piece Name: /u01/app/oracle/fast_recovery_area/orcl1/ORCL1/80C5B383246F06B2E0531201A8C09E95/backupset/2019_05_09/o1_mf_nnndf_TAG20190509T211650_gf8ly0x5_.bkp
  List of Datafiles in backup set 6
  Container ID: 3, PDB Name: JIGI
  File LV Type Ckp SCN    Ckp Time  Abs Fuz SCN Sparse Name
  ---- -- ---- ---------- --------- ----------- ------ ----
  9       Full 1966939    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_system_g56fjomp_.dbf
  10      Full 1966939    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_sysaux_g56fjoqy_.dbf
  11      Full 1966939    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_undotbs1_g56fjoqz_.dbf
  12      Full 1966939    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_users_g56fmk1x_.dbf
  19      Full 1966939    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_tsa_g60sbrnw_.dbf
  20      Full 1966939    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_tsb_g60scc47_.dbf
  21      Full 1966939    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_tsc_g60scts8_.dbf
  22      Full 1966939    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_tsd_g60sdjw8_.dbf

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
7       Full    543.82M    DISK        00:00:28     09-MAY-19      
        BP Key: 7   Status: AVAILABLE  Compressed: NO  Tag: TAG20190509T211650
        Piece Name: /u01/app/oracle/fast_recovery_area/orcl1/ORCL1/8183F1693BDD1468E0531201A8C02271/backupset/2019_05_09/o1_mf_nnndf_TAG20190509T211650_gf8m0dgf_.bkp
  List of Datafiles in backup set 7
  Container ID: 4, PDB Name: TEST
  File LV Type Ckp SCN    Ckp Time  Abs Fuz SCN Sparse Name
  ---- -- ---- ---------- --------- ----------- ------ ----
  13      Full 1966978    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/8183F1693BDD1468E0531201A8C02271/datafile/o1_mf_system_g5zcg9hv_.dbf
  14      Full 1966978    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/8183F1693BDD1468E0531201A8C02271/datafile/o1_mf_sysaux_g5zcg9k5_.dbf
  15      Full 1966978    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/8183F1693BDD1468E0531201A8C02271/datafile/o1_mf_undotbs1_g5zcg9k7_.dbf

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
8       Full    498.41M    DISK        00:00:22     09-MAY-19      
        BP Key: 8   Status: AVAILABLE  Compressed: NO  Tag: TAG20190509T211650
        Piece Name: /u01/app/oracle/fast_recovery_area/orcl1/ORCL1/80C541CF0FA65E3FE0531201A8C06FB0/backupset/2019_05_09/o1_mf_nnndf_TAG20190509T211650_gf8m1hrt_.bkp
  List of Datafiles in backup set 8
  Container ID: 2, PDB Name: PDB$SEED
  File LV Type Ckp SCN    Ckp Time  Abs Fuz SCN Sparse Name
  ---- -- ---- ---------- --------- ----------- ------ ----
  5       Full 1441388    31-JAN-19              NO    /u01/app/oracle/oradata/ORCL1/datafile/o1_mf_system_g56ch5lh_.dbf
  6       Full 1441388    31-JAN-19              NO    /u01/app/oracle/oradata/ORCL1/datafile/o1_mf_sysaux_g56ch5h5_.dbf
  8       Full 1441388    31-JAN-19              NO    /u01/app/oracle/oradata/ORCL1/datafile/o1_mf_undotbs1_g56ch5o2_.dbf

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
9       Full    498.41M    DISK        00:00:23     09-MAY-19      
        BP Key: 9   Status: AVAILABLE  Compressed: NO  Tag: TAG20190509T211650
        Piece Name: /u01/app/oracle/fast_recovery_area/orcl1/ORCL1/818DC149F5282394E0531201A8C0C446/backupset/2019_05_09/o1_mf_nnndf_TAG20190509T211650_gf8m29bc_.bkp
  List of Datafiles in backup set 9
  Container ID: 5, PDB Name: APP_PDB
  File LV Type Ckp SCN    Ckp Time  Abs Fuz SCN Sparse Name
  ---- -- ---- ---------- --------- ----------- ------ ----
  16      Full 1698582    10-FEB-19              NO    /u01/app/oracle/oradata/ORCL1/818DC149F5282394E0531201A8C0C446/datafile/o1_mf_system_g60nm8qh_.dbf
  17      Full 1698582    10-FEB-19              NO    /u01/app/oracle/oradata/ORCL1/818DC149F5282394E0531201A8C0C446/datafile/o1_mf_sysaux_g60nm8r7_.dbf
  18      Full 1698582    10-FEB-19              NO    /u01/app/oracle/oradata/ORCL1/818DC149F5282394E0531201A8C0C446/datafile/o1_mf_undotbs1_g60nm8r8_.dbf

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
10      Full    1.04G      DISK        00:00:51     09-MAY-19      
        BP Key: 10   Status: AVAILABLE  Compressed: NO  Tag: TAG20190509T212535
        Piece Name: /u01/app/oracle/fast_recovery_area/orcl1/ORCL1/backupset/2019_05_09/o1_mf_nnndf_TAG20190509T212535_gf8mcqgg_.bkp
  List of Datafiles in backup set 10
  File LV Type Ckp SCN    Ckp Time  Abs Fuz SCN Sparse Name
  ---- -- ---- ---------- --------- ----------- ------ ----
  1       Full 1967272    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/datafile/o1_mf_system_g56bzr71_.dbf
  3       Full 1967272    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/datafile/o1_mf_sysaux_g56c4gwz_.dbf
  4       Full 1967272    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/datafile/o1_mf_undotbs1_g56c8082_.dbf
  7       Full 1967272    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/datafile/o1_mf_users_g56c8cf3_.dbf

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
11      Full    557.34M    DISK        00:00:35     09-MAY-19      
        BP Key: 11   Status: AVAILABLE  Compressed: NO  Tag: TAG20190509T212535
        Piece Name: /u01/app/oracle/fast_recovery_area/orcl1/ORCL1/80C5B383246F06B2E0531201A8C09E95/backupset/2019_05_09/o1_mf_nnndf_TAG20190509T212535_gf8mfgw3_.bkp
  List of Datafiles in backup set 11
  Container ID: 3, PDB Name: JIGI
  File LV Type Ckp SCN    Ckp Time  Abs Fuz SCN Sparse Name
  ---- -- ---- ---------- --------- ----------- ------ ----
  9       Full 1967300    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_system_g56fjomp_.dbf
  10      Full 1967300    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_sysaux_g56fjoqy_.dbf
  11      Full 1967300    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_undotbs1_g56fjoqz_.dbf
  12      Full 1967300    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_users_g56fmk1x_.dbf
  19      Full 1967300    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_tsa_g60sbrnw_.dbf
  20      Full 1967300    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_tsb_g60scc47_.dbf
  21      Full 1967300    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_tsc_g60scts8_.dbf
  22      Full 1967300    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_tsd_g60sdjw8_.dbf

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
12      Full    543.82M    DISK        00:00:29     09-MAY-19      
        BP Key: 12   Status: AVAILABLE  Compressed: NO  Tag: TAG20190509T212535
        Piece Name: /u01/app/oracle/fast_recovery_area/orcl1/ORCL1/8183F1693BDD1468E0531201A8C02271/backupset/2019_05_09/o1_mf_nnndf_TAG20190509T212535_gf8mgwc7_.bkp
  List of Datafiles in backup set 12
  Container ID: 4, PDB Name: TEST
  File LV Type Ckp SCN    Ckp Time  Abs Fuz SCN Sparse Name
  ---- -- ---- ---------- --------- ----------- ------ ----
  13      Full 1967955    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/8183F1693BDD1468E0531201A8C02271/datafile/o1_mf_system_g5zcg9hv_.dbf
  14      Full 1967955    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/8183F1693BDD1468E0531201A8C02271/datafile/o1_mf_sysaux_g5zcg9k5_.dbf
  15      Full 1967955    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/8183F1693BDD1468E0531201A8C02271/datafile/o1_mf_undotbs1_g5zcg9k7_.dbf

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
13      Full    498.41M    DISK        00:00:24     09-MAY-19      
        BP Key: 13   Status: AVAILABLE  Compressed: NO  Tag: TAG20190509T212535
        Piece Name: /u01/app/oracle/fast_recovery_area/orcl1/ORCL1/80C541CF0FA65E3FE0531201A8C06FB0/backupset/2019_05_09/o1_mf_nnndf_TAG20190509T212535_gf8mhzwb_.bkp
  List of Datafiles in backup set 13
  Container ID: 2, PDB Name: PDB$SEED
  File LV Type Ckp SCN    Ckp Time  Abs Fuz SCN Sparse Name
  ---- -- ---- ---------- --------- ----------- ------ ----
  5       Full 1441388    31-JAN-19              NO    /u01/app/oracle/oradata/ORCL1/datafile/o1_mf_system_g56ch5lh_.dbf
  6       Full 1441388    31-JAN-19              NO    /u01/app/oracle/oradata/ORCL1/datafile/o1_mf_sysaux_g56ch5h5_.dbf
  8       Full 1441388    31-JAN-19              NO    /u01/app/oracle/oradata/ORCL1/datafile/o1_mf_undotbs1_g56ch5o2_.dbf

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
14      Full    498.41M    DISK        00:00:32     09-MAY-19      
        BP Key: 14   Status: AVAILABLE  Compressed: NO  Tag: TAG20190509T212535
        Piece Name: /u01/app/oracle/fast_recovery_area/orcl1/ORCL1/818DC149F5282394E0531201A8C0C446/backupset/2019_05_09/o1_mf_nnndf_TAG20190509T212535_gf8mjtw6_.bkp
  List of Datafiles in backup set 14
  Container ID: 5, PDB Name: APP_PDB
  File LV Type Ckp SCN    Ckp Time  Abs Fuz SCN Sparse Name
  ---- -- ---- ---------- --------- ----------- ------ ----
  16      Full 1698582    10-FEB-19              NO    /u01/app/oracle/oradata/ORCL1/818DC149F5282394E0531201A8C0C446/datafile/o1_mf_system_g60nm8qh_.dbf
  17      Full 1698582    10-FEB-19              NO    /u01/app/oracle/oradata/ORCL1/818DC149F5282394E0531201A8C0C446/datafile/o1_mf_sysaux_g60nm8r7_.dbf
  18      Full 1698582    10-FEB-19              NO    /u01/app/oracle/oradata/ORCL1/818DC149F5282394E0531201A8C0C446/datafile/o1_mf_undotbs1_g60nm8r8_.dbf

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
15      Full    17.94M     DISK        00:00:00     09-MAY-19      
        BP Key: 15   Status: AVAILABLE  Compressed: NO  Tag: TAG20190509T212854
        Piece Name: /u01/app/oracle/fast_recovery_area/orcl1/ORCL1/autobackup/2019_05_09/o1_mf_s_1007846934_gf8mkyho_.bkp
  SPFILE Included: Modification time: 09-MAY-19
  SPFILE db_unique_name: ORCL1
  Control File Included: Ckp SCN: 1968008      Ckp time: 09-MAY-19

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
16      Full    1.04G      DISK        00:00:41     09-MAY-19      
        BP Key: 16   Status: AVAILABLE  Compressed: NO  Tag: TAG20190509T213944
        Piece Name: /u01/app/oracle/fast_recovery_area/orcl1/ORCL1/backupset/2019_05_09/o1_mf_nnndf_TAG20190509T213944_gf8n68hq_.bkp
  List of Datafiles in backup set 16
  File LV Type Ckp SCN    Ckp Time  Abs Fuz SCN Sparse Name
  ---- -- ---- ---------- --------- ----------- ------ ----
  1       Full 1968434    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/datafile/o1_mf_system_g56bzr71_.dbf
  3       Full 1968434    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/datafile/o1_mf_sysaux_g56c4gwz_.dbf
  4       Full 1968434    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/datafile/o1_mf_undotbs1_g56c8082_.dbf
  7       Full 1968434    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/datafile/o1_mf_users_g56c8cf3_.dbf

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
17      Full    557.34M    DISK        00:00:32     09-MAY-19      
        BP Key: 17   Status: AVAILABLE  Compressed: NO  Tag: TAG20190509T213944
        Piece Name: /u01/app/oracle/fast_recovery_area/orcl1/ORCL1/80C5B383246F06B2E0531201A8C09E95/backupset/2019_05_09/o1_mf_nnndf_TAG20190509T213944_gf8n7p03_.bkp
  List of Datafiles in backup set 17
  Container ID: 3, PDB Name: JIGI
  File LV Type Ckp SCN    Ckp Time  Abs Fuz SCN Sparse Name
  ---- -- ---- ---------- --------- ----------- ------ ----
  9       Full 1968502    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_system_g56fjomp_.dbf
  10      Full 1968502    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_sysaux_g56fjoqy_.dbf
  11      Full 1968502    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_undotbs1_g56fjoqz_.dbf
  12      Full 1968502    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_users_g56fmk1x_.dbf
  19      Full 1968502    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_tsa_g60sbrnw_.dbf
  20      Full 1968502    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_tsb_g60scc47_.dbf
  21      Full 1968502    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_tsc_g60scts8_.dbf
  22      Full 1968502    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/80C5B383246F06B2E0531201A8C09E95/datafile/o1_mf_tsd_g60sdjw8_.dbf

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
18      Full    543.82M    DISK        00:00:26     09-MAY-19      
        BP Key: 18   Status: AVAILABLE  Compressed: NO  Tag: TAG20190509T213944
        Piece Name: /u01/app/oracle/fast_recovery_area/orcl1/ORCL1/8183F1693BDD1468E0531201A8C02271/backupset/2019_05_09/o1_mf_nnndf_TAG20190509T213944_gf8n8skb_.bkp
  List of Datafiles in backup set 18
  Container ID: 4, PDB Name: TEST
  File LV Type Ckp SCN    Ckp Time  Abs Fuz SCN Sparse Name
  ---- -- ---- ---------- --------- ----------- ------ ----
  13      Full 1968525    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/8183F1693BDD1468E0531201A8C02271/datafile/o1_mf_system_g5zcg9hv_.dbf
  14      Full 1968525    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/8183F1693BDD1468E0531201A8C02271/datafile/o1_mf_sysaux_g5zcg9k5_.dbf
  15      Full 1968525    09-MAY-19              NO    /u01/app/oracle/oradata/ORCL1/8183F1693BDD1468E0531201A8C02271/datafile/o1_mf_undotbs1_g5zcg9k7_.dbf

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
19      Full    498.41M    DISK        00:00:21     09-MAY-19      
        BP Key: 19   Status: AVAILABLE  Compressed: NO  Tag: TAG20190509T213944
        Piece Name: /u01/app/oracle/fast_recovery_area/orcl1/ORCL1/80C541CF0FA65E3FE0531201A8C06FB0/backupset/2019_05_09/o1_mf_nnndf_TAG20190509T213944_gf8n9wrg_.bkp
  List of Datafiles in backup set 19
  Container ID: 2, PDB Name: PDB$SEED
  File LV Type Ckp SCN    Ckp Time  Abs Fuz SCN Sparse Name
  ---- -- ---- ---------- --------- ----------- ------ ----
  5       Full 1441388    31-JAN-19              NO    /u01/app/oracle/oradata/ORCL1/datafile/o1_mf_system_g56ch5lh_.dbf
  6       Full 1441388    31-JAN-19              NO    /u01/app/oracle/oradata/ORCL1/datafile/o1_mf_sysaux_g56ch5h5_.dbf
  8       Full 1441388    31-JAN-19              NO    /u01/app/oracle/oradata/ORCL1/datafile/o1_mf_undotbs1_g56ch5o2_.dbf

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
20      Full    498.41M    DISK        00:00:24     09-MAY-19      
        BP Key: 20   Status: AVAILABLE  Compressed: NO  Tag: TAG20190509T213944
        Piece Name: /u01/app/oracle/fast_recovery_area/orcl1/ORCL1/818DC149F5282394E0531201A8C0C446/backupset/2019_05_09/o1_mf_nnndf_TAG20190509T213944_gf8nbp70_.bkp
  List of Datafiles in backup set 20
  Container ID: 5, PDB Name: APP_PDB
  File LV Type Ckp SCN    Ckp Time  Abs Fuz SCN Sparse Name
  ---- -- ---- ---------- --------- ----------- ------ ----
  16      Full 1698582    10-FEB-19              NO    /u01/app/oracle/oradata/ORCL1/818DC149F5282394E0531201A8C0C446/datafile/o1_mf_system_g60nm8qh_.dbf
  17      Full 1698582    10-FEB-19              NO    /u01/app/oracle/oradata/ORCL1/818DC149F5282394E0531201A8C0C446/datafile/o1_mf_sysaux_g60nm8r7_.dbf
  18      Full 1698582    10-FEB-19              NO    /u01/app/oracle/oradata/ORCL1/818DC149F5282394E0531201A8C0C446/datafile/o1_mf_undotbs1_g60nm8r8_.dbf

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
21      Full    17.94M     DISK        00:00:00     09-MAY-19      
        BP Key: 21   Status: AVAILABLE  Compressed: NO  Tag: TAG20190509T214231
        Piece Name: /u01/app/oracle/fast_recovery_area/orcl1/ORCL1/autobackup/2019_05_09/o1_mf_s_1007847751_gf8nchvk_.bkp
  SPFILE Included: Modification time: 09-MAY-19
  SPFILE db_unique_name: ORCL1
  Control File Included: Ckp SCN: 1968730      Ckp time: 09-MAY-19

RMAN>

Crosscheck Backup : This command will check the list of backup available in metadata is physically available or not . If it is physically deleted than it will give an EXPIRED status to those backup

RMAN> CROSSCHECK BACKUP;

using channel ORA_DISK_1
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=/u01/app/oracle/fast_recovery_area/orcl1/ORCL1/autobackup/2019_01_31/o1_mf_s_999041482_g56fzs1j_.bkp RECID=1 STAMP=999041488
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u01/app/oracle/fast_recovery_area/orcl1/ORCL1/autobackup/2019_02_10/o1_mf_s_999858554_g5zcx47j_.bkp RECID=2 STAMP=999858556
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u01/app/oracle/fast_recovery_area/orcl1/ORCL1/autobackup/2019_02_10/o1_mf_s_999900594_g60nzcsd_.bkp RECID=3 STAMP=999900611
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u01/app/oracle/fast_recovery_area/orcl1/ORCL1/autobackup/2019_02_10/o1_mf_s_999905720_g60sz1lg_.bkp RECID=4 STAMP=999905721
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u01/app/oracle/fast_recovery_area/orcl1/ORCL1/backupset/2019_05_09/o1_mf_nnndf_TAG20190509T211650_gf8lvcdn_.bkp RECID=5 STAMP=1007846211
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u01/app/oracle/fast_recovery_area/orcl1/ORCL1/80C5B383246F06B2E0531201A8C09E95/backupset/2019_05_09/o1_mf_nnndf_TAG20190509T211650_gf8ly0x5_.bkp RECID=6 STAMP=1007846296
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u01/app/oracle/fast_recovery_area/orcl1/ORCL1/8183F1693BDD1468E0531201A8C02271/backupset/2019_05_09/o1_mf_nnndf_TAG20190509T211650_gf8m0dgf_.bkp RECID=7 STAMP=1007846372
crosschecked..
Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Hi Readers

Finally, I’ve successfully passed 1Z0-074, Upgrade Oracle DBA 11g or 12c to 12c R2. It was almost more than 3 months that I’ve been preparing for this.

The Exam contains 75 questions related to Oracle Database 12cR2 New Features. To earn this certification you need to get 63% marks.

This was the result of the journey: Oracle Certified Professional, Database 12cR2 Administration.

In this post you will find:

  • A path to achieve it
  • Study Materials
  • Exam Detail & Score

How to Achieve this Certification?

Before appearing to this exam you must have the vast knowledge of Oracle Database 12cR2 and Oracle Database Cloud.

List of exam topics

  • Using CDBs and Application Containers
  • Creating Different Types of PDBs
  • Managing Performance in PDBs and CDBs
  • Creating and Managing Profiles and Privileges
  • Using Data Redaction
  • Using TSPD policies with Auditing and Column Encryption
  • Recovering a database
  • Using Oracle Data Pump, SQL*Loader and External Tables
  • Tuning SQL Statements
  • Applying Different Types of Partitioning
  • Using Diagnostic Enhancements
  • Using SQL Enhancements
  • Administrating Storage
  • Managing Users and Users Access to Data in a Multitenant Environment
  • Recovering and Flashing back CDBs and PDBs
  • Upgrading Database from 11g or 12.1 to 12.2
  • Performing Unified Auditing
  • Using Data Encryption
  • Creating and Managing backup and recovery catalog
  • Transporting a tablespace
  • Performing In-Memory Column Store
  • Memory and Other Performance Enhancements
  • Manageability
  • Managing Oracle Database Cloud Services
  • Using Information Lifecycle Management and Storage Enhancements)

For more detail, you can follow the below link.

https://education.oracle.com/upgrade-oracle-dba-11g-or-12c-to-12c-r2/pexam_1Z0-074

How to prepare for the exam?

There is only one way to study for this exam

  1. Oracle Database 12c R2: New Features for 12c R1 Administrators

How to register for the exam?

If you want to enroll exam, please click on below link.

Exam Number: 1Z0-074

Exam Title: Upgrade Oracle DBA 11g or 12c to 12c R2


https://education.oracle.com/upgrade-oracle-dba-11g-or-12c-to-12c-r2/pexam_1Z0-074

Below are the Exam Details related to scoring.

There is a nice post from my fellow DBA – Alex Zaballa

You Should Avoid Brain Dumps When Preparing for Certifications

Special Thanks

Joel Perez is an Oracle OCM and ACED who gave an opportunity to write him and motivating me to learn new things.  I’m very thankful to him as this was the kick off for my studies.

Thank you for giving your valuable time to read the above information.

If you want to be updated with all our articles send us the Invitation or Follow us:

Skant Gupta’s LinkedIn: www.linkedin.com/in/skantali/

Joel Perez’s LinkedIn: Joel Perez’s Profile

LinkedIn Group: Oracle Cloud DBAAS

Facebook Page: OracleHelp

The post Upgrade Oracle DBA 11g or 12c to 12c R2 (1Z0-074) appeared first on ORACLE-HELP.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

In this article we will see password based encryption.

Step 1 : Connect to RMAN

[oracle@localhost ~]$ rman target /

Recovery Manager: Release 12.2.0.1.0 - Production on Mon Jan 7 13:44:38 2019

Copyright (c) 1982, 2017, Oracle and/or its affiliates.  All rights reserved.

connected to target database: DEMO (DBID=3740643610)

RMAN> show all;

using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name DEMO are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/oracle/product/12.2.0/db_1/dbs/snapcf_demo.f'; # default

Step 2 : Set encryption algorithm

RMAN> SET ENCRYPTION ON ALGORITHM 'AES128' IDENTIFIED BY 'orarmanbkp';

executing command: SET encryption

Step 3 : Here I am taking backup of one tablespace in ORCLPDB pluggable database

RMAN> BACKUP DEVICE TYPE DISK TABLESPACE ORCLPDB:DEM_TBS;

Starting backup at 24-APR-19
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=136 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00016 name=/home/appndb/oracle/oradata/ORCL/7D624BBBEC2B4677E0538001A8C06AFB/datafile/o1_mf_dem_tbs_gd0ml9d4_.dbf
channel ORA_DISK_1: starting piece 1 at 24-APR-19
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 04/24/2019 17:25:04
ORA-19914: unable to encrypt backup
ORA-28365: wallet is not open

We can see an error is thrown here , unable to encrypt backup , wallet is not open

Explanation : To set password only encryption we need to apply “ONLY” keyword at the end of this command .

RMAN> SET ENCRYPTION ON ALGORITHM 'AES128' IDENTIFIED BY 'orarmanbkp' ONLY;

executing command: SET encryption

Now let us take backup

RMAN> BACKUP DEVICE TYPE DISK TABLESPACE PDB:DEM_TBS;

Starting backup at 07-JAN-19
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00014 name=/u02/oradata/DEMO/7E8758AC5ED126B4E055000000000001/datafile/o1_mf_dem_tbs_g362hp3q_.dbf
channel ORA_DISK_1: starting piece 1 at 07-JAN-19
channel ORA_DISK_1: finished piece 1 at 07-JAN-19
piece handle=/u02/fast_recovery_area/demo/DEMO/7E8758AC5ED126B4E055000000000001/backupset/2019_01_07/o1_mf_nnndf_TAG20190107T135002_g362xl9n_.bkp tag=TAG20190107T135002 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 07-JAN-19

Starting Control File and SPFILE Autobackup at 07-JAN-19
piece handle=/u02/fast_recovery_area/demo/DEMO/autobackup/2019_01_07/o1_mf_s_996933003_g362xn6s_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 07-JAN-19

RMAN>

Thank you for giving your valuable time to read the above information.

If you want to be updated with all our articles send us the Invitation or Follow us:

Telegram Channel: https://t.me/helporacle

Skant Gupta’s LinkedIn: www.linkedin.com/in/skantali/

Joel Perez’s LinkedIn: Joel Perez’s Profile

LinkedIn Group: Oracle Cloud DBAAS

Facebook Page: OracleHelp

The post Password Based Encryption in RMAN Backup appeared first on ORACLE-HELP.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

This article describes about the Oracle 19C new feature – Active Data Guard DML Redirection.

ACTIVE DATA GUARD DML REDIRECT feature enables DML operation on the standby database to be redirected to and run on the primary database instead of failing, where the data changes will be applied. The updated data will then be streamed back to the standby database to maintain redundancy.

As the operations actually perform on primary, so better to avoid running too many DMLs on Active Data Guard standby databases.It might impact the performance of the primary due to too many DML operations.But it is good for applications that mostly read-applications with rare DML executions.

Below steps to achieve Applying DML on standby database:

— User executes DML against open standby database.
— DML redirects to primary database.
— Then DML is applied to the primary database.
— Then the data change is streamed back to standby database.
— Data is visible to client.

DML REDIRECT can be configured at the the system level or the session level by set the parameter ADG_REDIRECT_DML using below commands.The session level setting overrides the system level setting.

Enable ADG_REDIRECT_DML at System Level:
alter system set ADG_REDIRECT_DML=TRUE scope=both;

Enable ADG_REDIRECT_DML at Session Level:
alter session enable adg_redirect_dml;

Thank you for giving your valuable time to read the above information.

The post Oracle 19C Active Data Guard DML Redirection Feature appeared first on ORACLE-HELP.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

CREATE GUARANTEED RESTORE POINT:

  1. Stop redo transport and redo apply
    a)If broker is not configured:
    On primary database:
    SQL> alter system set log_archive_dest_state_2=’defer’;
    On standby database:
    SQL> alter database recover managed standby database cancel;
    b)If broker is in place:
    DGMGRL> edit database db set state = ‘TRANSPORT-OFF’;
    DGMGRL> edit database db01 set state = ‘APPLY-OFF’;
  2. Set Restore Point in standby database
    On standby database:
    SQL> CREATE RESTORE POINT restore_dg GUARANTEE FLASHBACK DATABASE;
  3. Set Restore Point in primary database
    On primary database:
    SQL> CREATE RESTORE POINT restore_dg GUARANTEE FLASHBACK DATABASE;
  4. Enable redo transport and redo apply
    a)If broker is not configured:
    On primary database:
    SQL> alter system set log_archive_dest_state_2=’enable’;
    On standby database:
    SQL> alter database recover managed standby database disconnect from session;
    b)If broker is in place:
    DGMGRL> edit database db set state = ‘TRANSPORT-ON’;
    DGMGRL> edit database db01 set state = ‘APPLY-ON’;

FLASHBACK DATABASE TO GUARANTEED RESTORE POINT

  1. Stop redo transport and redo apply
    a)If broker is not configured:
    On primary database:
    SQL> alter system set log_archive_dest_state_2=’defer’;
    On standby database:
    SQL> alter database recover managed standby database cancel;
    b)If broker is in place:
    DGMGRL> edit database db set state = ‘TRANSPORT-OFF’;
    DGMGRL> edit database db01 set state = ‘APPLY-OFF’;
  2. Shutdown Primary Database and start in mount state
  3. Flashback primary database to restore point
    On primary database:
    SQL> flashback database to RESTORE POINT restore_dg;
    SQL> alter database open resetlogs;
  4. Shutdown Standby database and start in mount state
  5. Flashback standby database
    On standby database:
    SQL> flashback database to RESTORE POINT restore_dg;
  6. Enable redo transport and redo apply
    a)If broker is not configured:
    On primary database:
    SQL> alter system set log_archive_dest_state_2=’enable’;
    On standby database:
    SQL> alter database recover managed standby database disconnect from session;
    b)If broker is in place:
    DGMGRL> edit database db set state = ‘TRANSPORT-ON’;
    DGMGRL> edit database db01 set state = ‘APPLY-ON’;

DROP GUARANTEED RESTORE POINT

  1. Stop redo transport and redo apply
    a)If broker is not configured:
    On primary database:
    SQL> alter system set log_archive_dest_state_2=’defer’;
    On standby database:
    SQL> alter database recover managed standby database cancel;
    b)If broker is in place:
    DGMGRL> edit database db set state = ‘TRANSPORT-OFF’;
    DGMGRL> edit database db01 set state = ‘APPLY-OFF’;
  2. Drop Restore Point in primary database
    On primary database:
    SQL> drop RESTORE POINT restore_dg;
  3. Drop Restore Point in standby database
    Ensure the standby database is in mount state and drop
    GUARANTEED RESTORE POINT :
    SQL> drop restore point restore_dg;
    If Active Data Guard is used, open read only the standby database after dropping the Guaranteed restore point.
  4. Enable redo transport and redo apply
    a)If broker is not configured:
    On primary database:
    SQL> alter system set log_archive_dest_state_2=’enable’;
    On standby database:
    SQL> alter database recover managed standby database disconnect from session;
    b)If broker is in place:
    DGMGRL> edit database db set state = ‘TRANSPORT-ON’;
    DGMGRL> edit database db01 set state = ‘APPLY-ON’;

The post Steps to Create,Drop and Flashback Guaranteed restore point in Dataguard appeared first on ORACLE-HELP.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

In this post we will discuss the steps to decrypt WebLogic credential from Boot Properties. During OEM upgrade process when WebLogic password is required, if you have forget the password you can decrypt the WebLogic credential using below steps.

1.Go to your domain/bin directory where setDomainEnv.sh file present.

oracle=>cd /u01/app/app00/cloudc/gc_inst/user_projects/domains/GCDomain/bin

oracle=>ls -ltr

total 60

drwxr-x—. 2 oracle dba  4096 Aug  6  2018 nodemanager

drwxr-x—. 2 oracle dba  4096 Aug  6  2018 service_migration

drwxr-x—. 2 oracle dba  4096 Aug  6  2018 server_migration

-rwxr-x—. 1 oracle dba  6304 Aug  6  2018 startEMServer.sh

-rwxr-x—. 1 oracle dba  5698 Aug  6  2018 startWebLogic.sh

-rwxr-x—. 1 oracle dba  2001 Aug  6  2018 stopWebLogic.sh

-rwxr-x—. 1 oracle dba  3243 Aug  6  2018 startManagedWebLogic.sh

-rwxr-x—. 1 oracle dba  2479 Aug  6  2018 stopManagedWebLogic.sh

-rwxr-x—. 1 oracle dba 16530 Aug  6  2018 setDomainEnv.sh

2. Collect encrypted information from boot.properties file.

oracle=>locate boot.properties
/u01/app/app00/cloudc/gc_inst/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/security/boot.properties

oracle=>more /u01/app/app00/cloudc/gc_inst/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/security/boot.properties

# Generated by Configuration Wizard on Wed Aug 06 15:42:00 IST 2018

username={AES}xxxx

password={AES}yyyy

=>/u01/app/app00/cloudc/gc_inst/user_projects/domains/GCDomain

3. Create below sample java script and save it as recoverpassword.java.

cat recoverpassword.java
public class recoverpassword {
public static void main(String[] args)
{
System.out.println(
new weblogic.security.internal.encryption.ClearOrEncryptedService(
weblogic.security.internal.SerializedSystemIni.getEncryptionService(args[0]
)).decrypt(args[1]));
}
}

4. Execute the setDomainEnv.sh .

oracle=>. ./setDomainEnv.sh

5. Use the below to get the password in readable format.

oracle=>java -cp $CLASSPATH:. recoverpassword $DOMAIN_HOME {AES}yyyy
good

Thank you for giving your valuable time to read the above information.

The post Steps to recover WebLogic Credential [OEM 12cR5] appeared first on ORACLE-HELP.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 
  • This post explains about the steps are used by DBAs to install OEM agent using Silent Method.
  1. On the OMS host, you need to login using the EMCLI command [Note that SYSMAN password is required]

oracle=>emcli login -username=sysman

2.oracle=>emcli sync

Synchronized successfully

Note Message should be “synchronized successfully”

3) List support platforms [Run it on OMS Host]

oracle=>emcli get_supported_platforms

———————————————–

Version = 12.1.0.4.0

 Platform = IBM AIX on POWER Systems (64-bit)

———————————————–

Version = 12.1.0.4.0

 Platform = Linux x86-64

———————————————–

Version = 12.1.0.4.0

 Platform = Oracle Solaris on SPARC (64-bit)

———————————————–

Platforms list displayed successfully.

4) Download the agent image to a temporary location of the OMS host.

emcli get_agentimage -destination=/tmp -platform=”Oracle Solaris on SPARC (64-bit)” -version=12.1.0.4.0

5. Transfer the file like AgentCore.zip to the target host (The server where you want to install the agent) of ‘/u01/agent/agent12c’ agent base directory. please create the agent base directory as per your environment.

6. Unzip the AgentCore.zip file to get the “agentDeploy.sh” and “agent.rsp”.

7. Edit the agent.rsp file for the specifics to be needed during the install.

You need to edit the below parameters in the agent.rsp file as per your environment.

OMS_HOST= oemgrid

EM_UPLOAD_PORT=4903

AGENT_REGISTRATION_PASSWORD=Welcome

AGENT_INSTANCE_HOME=/u01/agent/agent12c/core

AGENT_PORT=3872

b_startAgent=true

ORACLE_HOSTNAME= orcl (the host name where you want to install the agent)

s_agentHomeName=”agent12c”

8. Execute the “agentDeploy.sh” which you got from step no 6 after unzip and use the response file which you have saved on step no 7. [During execution, At the end you will get message as “Agent deployment completed successfully.”, if it completes without any error]

oracle=>./agentDeploy.sh AGENT_BASE_DIR=/u01/agent/agent12c RESPONSE_FILE=/u01/agent/agent12c/agent.rsp

9. You will also get message on step no 8 as “The following configuration scripts need to be executed as the “root” user. Then please login as “root” and run the “root.sh” script (script location details you will get from step no 8.)

10. After installation, Check the agent status using the below command.

emctl status agent

Thank you for giving your valuable time to read the above information.

The post OEM Management Agent Installation Using Silent Method appeared first on ORACLE-HELP.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Started seeing this OEM error alert mails for OEM agents.

EM Incident: Critical:New: – Agent Blocked (Bounce Counter Mismatch)

Cause

For every agent in the repository OEM maintains a Bounce Counter.At the time of agent restart, if the agent side Bounce Counter value is not in sync with repository, then uploads from this agent is getting blocked by OMS until the information about the Agent and all its targets are in sync between the Repository and the Agent.

Solution:

–Login to your OEM console.

–Go to Setup—Manage Cloud Control—Agent

–Check the agent status is showing as blocked or not. If blocked, select the respective agent and click on unblock button.So that agent will be unblocked.

–After that check targets(database,listener) related to that respective agent is showing as up or not on console. if not, then connect to target database using putty, try to do emctl upload agent.If at the time of upload you have not get any error, then issue has been fixed and you will be able to see target status as up from OEM console. If at the time of upload you got error,

Then try the below steps:

emctl stop agent

emctl clearstate agent

emctl start agent

emctl upload agent.

—Again check the targets status from OEM console that should be shown as available/up.

Thank you for giving your valuable time to read the above information.

The post Agent Blocked (Bounce Counter Mismatch) OEM 12C/13C appeared first on ORACLE-HELP.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Use the below command to Stop only the Oracle Management Service:
emctl stop oms

Use the below command to stop Oracle Management Service including Administartion Server, HTTP Server and Node Manager:
emctl stop oms -all

Use the below command to check the status of OMS:
emctl status oms

Use the below command to get detailed status of your OMS [Note that SYSMAN Password is required] :
emctl status oms -details

Use the below command to stop your management agent:
emctl stop agent

Use the below command to start your management agent:
emctl start agent

Use the below command to check the status of your management agent:
emctl status agent

Thank you for giving your valuable time to read the above information.

If you want to be updated with all our articles send us the Invitation or Follow us:

Telegram Channel: https://t.me/helporacle

Skant Gupta’s LinkedIn: www.linkedin.com/in/skantali/

Joel Perez’s LinkedIn: Joel Perez’s Profile

LinkedIn Group: Oracle Cloud DBAAS

Facebook Page: OracleHelp

The post Basic Commands For Controlling OEM 12C/13C Cloud Control appeared first on ORACLE-HELP.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

In the last post, we installed Oracle 19c Database Software by running RPM Package. Now, we are going to create and configure a Database with default Setting.
Log in as root and run the below command to configure an Oracle Database instance.

[root@oracle19c dbhome_1]# /etc/init.d/oracledb_ORCLCDB-19c configure
Configuring Oracle Database ORCLCDB.
[FATAL] [DBT-06103] The port (1,521) is already in use.
   ACTION: Specify a free port.

Database configuration failed.

To resolve the above error, make sure /etc/hosts has configured properly and ping to the server is also working.

[root@oracle19c dbhome_1]# ping oracle19c
ping: oracle19c: Name or service not known

[root@oracle19c dbhome_1]# vi /etc/hosts

[root@oracle19c ~]$ cat /etc/hosts
192.168.2.7 oracle19c oracle19c.localdomain
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

[root@oracle19c ~]$ ping oracle19c
PING oracle19c (192.168.2.7) 56(84) bytes of data.
64 bytes from oracle19c (192.168.2.7): icmp_seq=1 ttl=64 time=0.044 ms
64 bytes from oracle19c (192.168.2.7): icmp_seq=2 ttl=64 time=0.044 ms

Now, re-run the configure for creating database instance.

[root@oracle19c dbhome_1]# /etc/init.d/oracledb_ORCLCDB-19c configure
Configuring Oracle Database ORCLCDB.
Prepare for db operation
8% complete
Copying database files
31% complete
Creating and starting Oracle instance
32% complete
36% complete
40% complete
43% complete
46% complete
Completing Database Creation
51% complete
54% complete
Creating Pluggable Databases
58% complete
77% complete
Executing Post Configuration Actions
100% complete
Database creation complete. For details check the logfiles at:
 /opt/oracle/cfgtoollogs/dbca/ORCLCDB.
Database Information:
Global Database Name:ORCLCDB
System Identifier(SID):ORCLCDB
Look at the log file "/opt/oracle/cfgtoollogs/dbca/ORCLCDB/ORCLCDB.log" for further details.

Database configuration completed successfully. The passwords were auto generated, you must change them by connecting to the database using 'sqlplus / as sysdba' as the oracle user.
[root@oracle19c dbhome_1]#

Note: You can modify the configuration parameters by changing in a configuration file.

[root@oracle19c sysconfig]# pwd
/etc/sysconfig
[root@oracle19c sysconfig]# cat oracledb_ORCLCDB-19c.conf
#This is a configuration file to setup the Oracle Database.
#It is used when running '/etc/init.d/oracledb_ORCLCDB configure'.
#Please use this file to modify the default listener port and the
#Oracle data location.

# LISTENER_PORT: Database listener
LISTENER_PORT=1521

# ORACLE_DATA_LOCATION: Database oradata location
ORACLE_DATA_LOCATION=/opt/oracle/oradata

# EM_EXPRESS_PORT: Oracle EM Express listener
EM_EXPRESS_PORT=5500
[root@oracle19c sysconfig]#

This script creates a container database (ORCLCDB) with one pluggable database (ORCLPDB1) and configures the listener at the default port (1521). Now, connect to a database with an Oracle user.

[oracle@oracle19c sw]# ps -ef|grep pmon
oracle   29358     1  0 03:47 ?        00:00:00 ora_pmon_ORCLCDB
root     30579 17822  0 03:59 pts/0    00:00:00 grep --color=auto pmon

[oracle@oracle19c sw]$ . oraenv
ORACLE_SID = [oracle] ? ORCLCDB
The Oracle base has been set to /opt/oracle
[oracle@oracle19c sw]$ sqlplus / as sysdba

SQL*Plus: Release 19.0.0.0.0 - Production on Fri Apr 26 03:59:49 2019
Version 19.3.0.0.0

Copyright (c) 1982, 2019, Oracle.  All rights reserved.


Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0

SQL> show pdbs

    CON_ID CON_NAME                       OPEN MODE  RESTRICTED
---------- ------------------------------ ---------- ----------
         2 PDB$SEED                       READ ONLY  NO
         3 ORCLPDB1                       READ WRITE NO

[oracle@oracle19c ~]#

Stop the database instance

[root@oracle19c ~]# /etc/init.d/oracledb_ORCLCDB-19c stop
Shutting down Oracle Database instance ORCLCDB.
Oracle Database instance ORCLCDB shut down.
Stopping Oracle Net Listener.
Oracle Net Listener stopped.

[root@oracle19c ~]#

Start the database instance

[root@oracle19c ~]# /etc/init.d/oracledb_ORCLCDB-19c start
Starting Oracle Net Listener.
Oracle Net Listener started.
Starting Oracle Database instance ORCLCDB.
Oracle Database instance ORCLCDB started.

[root@oracle19c ~]#

Restart the database instance

[root@oracle19c ~]# /etc/init.d/oracledb_ORCLCDB-19c restart
Shutting down Oracle Database instance ORCLCDB.
Oracle Database instance ORCLCDB shut down.
Stopping Oracle Net Listener.
Oracle Net Listener stopped.

Starting Oracle Net Listener.
Oracle Net Listener started.
Starting Oracle Database instance ORCLCDB.
Oracle Database instance ORCLCDB started.

[root@oracle19c ~]#

Delete the database instance

[root@oracle19c ~]# /etc/init.d/oracledb_ORCLCDB-19c delete
Detecting existing Listeners...
Deleting Oracle Listener....
Detecting existing Oracle Databases...
Deleting Oracle Database ORCLCDB.
[WARNING] [DBT-19202] The Database Configuration Assistant will delete the Oracle instances and datafiles for your database. All information in the database will be destroyed.
Prepare for db operation
32% complete
Connecting to database
35% complete
39% complete
42% complete
45% complete
48% complete
52% complete
65% complete
Updating network configuration files
68% complete
Deleting instance and datafiles
84% complete
100% complete
Database deletion completed.
Look at the log file "/opt/oracle/cfgtoollogs/dbca/ORCLCDB/ORCLCDB0.log" for further details.
[root@oracle19c ~]#

Thank you for giving your valuable time to read the above information.

If you want to be updated with all our articles send us the Invitation or Follow us:

Telegram Channel: https://t.me/helporacle

Skant Gupta’s LinkedIn: www.linkedin.com/in/skantali/

Joel Perez’s LinkedIn: Joel Perez’s Profile

LinkedIn Group: Oracle Cloud DBAAS

Facebook Page: OracleHelp

The post Creating and Configuring an Oracle Database for RPM Based appeared first on ORACLE-HELP.

Read Full Article

Read for later

Articles marked as Favorite are saved for later viewing.
close
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Separate tags by commas
To access this feature, please upgrade your account.
Start your free month
Free Preview