C:\Users\Administrator>sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 - Production on Thu Nov 12 09:41:15 2020
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>
Oracle Internal Process Checking: For the Oracle instance to run smoothly, please ensure that the internal processes for Oracle instance are working well:
DBW0 (Database Writer)
LGWR (Log Writer)
MMAN (Memory Manager Process)
PMON (Process Monitor)
PSP0 (Process Spawner Process)
SMON (System Monitor)
CKPT (Checkpoint process (thread on Windows) that runs by default on Windows)
ARC0 (Archive Process (or thread on Windows))
RECO (Distributed Recovery Background Process)
SQL> select name, description from v$bgprocess where PADDR <>'00';
NAME     DESCRIPTION
-----   ---------------------------------------
PMON     process cleanup
VKTM     Virtual Keeper of TiMe process
GEN0     generic0
DIAG     diagnosibility process
DBRM     DataBase Resource Manager
VKRM     Virtual sKeduler for Resource Manager
PSP0     process spawner 0
DIA0     diagnosibility process 0
MMAN     Memory Manager
DBW0     db writer process 0
TMON     Transport Monitor
ARC0     Archival Process 0
ARC1     Archival Process 1
ARC2     Archival Process 2
ARC3     Archival Process 3
LGWR     Redo etc.
CKPT     checkpoint
SMON     System Monitor Process
SMCO     Space Manager Process
RECO     distributed recovery
LREG     Listener Registration
CJQ0     Job Queue Coordinator
AQPC     AQ Process Coord
MMON     Manageability Monitor Process
MMNL     Manageability Monitor Process 2
Supported Oracle Database Server Version: %edition_name% supports the following versions of Oracle database server:
To verify if the Oracle database server version is supported by %edition_name%, use the following SQL query.
Oracle 19c
C:\Users\Administrator>sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 - Production on Thu Nov 12 12:04:25 2020
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>
Oracle 18c
C:\Users\Administrator>sqlplus / as sysdba
SQL*Plus: Release 18.0.0.0.0 - Production on Mon Jan 4 11:06:36 2021
Version 18.3.0.0.0
Copyright (c) 1982, 2018, Oracle. All rights reserved.
Connected to:
Oracle Database 18c Enterprise Edition Release 18.0.0.0.0 - Production
Version 18.3.0.0.0
SQL>
Oracle 12c
C:\Users\Administrator>sqlplus / as sysdba
SQL*Plus: Release 12.1.0.1.0 - Production on Mon May 26 15:33:44 2019
Version 12.1.0.1.0
Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - Production
Version 12.1.0.1.0
SQL>
System Identifier (SID): Make sure the System Identifier (SID) is correct by using the following SQL query.
- SQL command
SQL > select instance from v$thread;
INSTANCE
--------------------------------------
orcl
NOTE: The instance shown is just an example. The SID may be different on your Oracle instance.
OR
- init.ora file
Another way to verify the SID is by checking the init.ora file. Go to the D:\oracle\admin\orcl\pfile directory and open the init.ora file using a text editor (e.g. Notepad++).
###########################################
# Database Identification
###########################################
db_domain=""
db_name="orcl"
Oracle_Home path:
Oracle 19c
The Oracle_Home path can be obtained by using the following SQL query. The Oracle_Home path for Oracle 19c is “D:\app\oracle\19.0.0\dbhome_1”.
- SQL command
SQL > SELECT file_spec FROM DBA_LIBRARIES WHERE library_name = 'DBMS_SUMADV_LIB';
FILE_SPEC
-----------------------------------------------
D:\app\oracle\19.0.0\dbhome_1\bin\oraqsmashr.dll
NOTE: The directory path shown is just an example. The Oracle_Home may be different on your Oracle instance.
OR
- init.ora file
Another way to verify the Oracle_Home path is by checking the init.ora file. Go to the D:\oracle\admin\orcl\pfile directory and open the init.ora file using a text editor (e.g. Notepad++)
###########################################
# File Configuration
###########################################
control_files=("D:\app\oracle\oradata\ORCL\control01.ctl", "D:\app\oracle\oradata\ORCL\control02.ctl")
###########################################
Oracle 18c
The Oracle_Home path can be obtained by using the following SQL query. The Oracle_Home path for Oracle 18c is “D:\app\oracle\18.0.0\dbhome_1”.
- SQL command
SQL > SELECT file_spec FROM DBA_LIBRARIES WHERE library_name = 'DBMS_SUMADV_LIB';
FILE_SPEC
-----------------------------------------------
D:\app\oracle\18.0.0\dbhome_1\bin\oraqsmashr.dll
NOTE: The directory path shown is just an example. The Oracle_Home may be different on your Oracle instance.
OR
- init.ora file
Another way to verify the Oracle_Home path is by checking the init.ora file. Go to the D:\oracle\admin\orcl\pfile directory and open the init.ora file using a text editor (e.g. Notepad++)
###########################################
# File Configuration
###########################################
control_files=("D:\app\oracle\oradata\orcl18c\control01.ctl", "D:\app\oracle\oradata\orcl18c\control02.ctl")
###########################################
Oracle 12c
The Oracle_Home path can be obtained by using the following SQL query. The Oracle_Home path for Oracle 12c is “D:\app\oracle\product\12.1.0\dbhome_1”.
- SQL command
SQL > SELECT file_spec FROM DBA_LIBRARIES WHERE library_name = 'DBMS_SUMADV_LIB';
FILE_SPEC
-----------------------------------------------
D:\app\oracle\product\12.1.0\dbhome_1\bin\oraqsmashr.dll
NOTE: The instance shown is just an example. The Oracle_Home may be different on your Oracle instance.
OR
- init.ora file
Another way to verify the Oracle_Home path is by checking the init.ora file. Go to the D:\oracle\admin\orcl\pfile directory and open the init.ora file using a text editor (e.g. Notepad++)
###########################################
# File Configuration
###########################################
control_files=("D:\app\oracle\oradata\orcl12c\control01.ctl", "D:\app\oracle\recovery_area\orcl12c\control02.ctl")
db_recovery_file_dest="D:\app\oracle\recovery_area"
db_recovery_file_dest_size=6930m
!
If any of the following scenario is encountered, please contact the Oracle database administrator for further assistance:
The value of the Oracle_Home path in init.ora file does not match the value obtained from the SQL query.
The SQL query returns an empty or null value.
Example of an SQL query return with a null value of the Oracle_Home path
SQL > SELECT file_spec FROM DBA_LIBRARIES WHERE library_name = 'DBMS_SUMADV_LIB';
no rows selected
Database Status
Ensure that the status of Oracle instance is “Open”. To check, use the following query.
SQL > select instance_name, status form v$instance;
INSTANCE_NAME     STATUS
-------------     ----------
orcl             OPEN
Archived Log Mode
Ensure that the database instance is in Archived Log mode. To check, use the following command.
SQL > archive log list;
Database log mode           Archive Mode
Automatic archival           Enabled
Archive destination         USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     101
Next log sequence to archive   103
Current log sequence           103
SQL >
NOTE: The values shown are just examples and might be different on your Oracle instance.
Java Installation:
Java must be installed on the Oracle Database. To check if Java is installed, use the following SQL query. The status of the JServer JAVA Virtual Machine and Oracle Database Java Packages should be “VALID”.
SQL > select comp_name, status from dba_registry;
COMP_NAME                               STATUS
---------                               ------------
OWB                                      VALID
Oracle Application Express               VALID
Oracle Enterprise Manager               VALID
OLAP Catalog                             VALID
Spatial                                   VALID
Oracle Multimedia                      VALID
Oracle XML Database                     VALID
Oracle Text                           VALID
Oracle Expression Filter                 VALID
Oracle Rules Manager                     VALID
Oracle Workspace Manager              VALID
Oracle Database Catalog Views          VALID
Oracle Database Packages and Types       VALID
JServer JAVA Virtual Machine            VALID
Oracle XDK                                  VALID
Oracle Database Java Package             VALID
!
If the status of the JServer JAVA Virtual Machine and/or the Oracle Database Java Packages is INVALID, please contact the Oracle database administrator for further assistanc
JAVASYSPRIV Permission for Oracle System Account:
The Oracle system account is used by %edition_name% to connect to the Oracle database server to authenticate the backup and restore process. The following permission must be assigned to the system account.
Use the following command to check if the account has JAVASYSPRIV permission:
SQL> select * from DBA_ROLE_PRIVS where upper(grantee)='SYSTEM';
GRANTEE   GRANTED_ROLE           ADM   DEF   COM
-------   ------------           ---   ---   ---
SYSTEM   JAVASYSPRIV             NO     YES   NO
SYSTEM   AQ_ADMINISTRATOR_ROLE   YES   YES   YES
If not, grant JAVASYSPRIV to the system account by using the following SQL query.
SQL> grant javasyspriv to system;
Grant succeeded.
SYSDBA Privileges for Oracle System Account:
To check if the system account has sysdba privileges, use the following SQL query.
SQL> select * from v$pwfile_users where sysdba='TRUE';
USERNAME SYSDB SYSOP SYSAS SYSBA SYSDG SYSKM CON_ID
-------- ----- ----- ----- ----- ----- ----- ------
SYS       TRUE TRUE FALSE FALSE FALSE FALSE     0
SYSTEM   TRUE FALSE FALSE FALSE FALSE FALSE     1
If not, grant sysdba to the system account:
Oracle 19c and Oracle 18c
SQL> grant sysdba to system container=ALL;
Grant succeeded
Oracle 12c
SQL> grant sysdba to system;
Grant succeeded
TNS Listener Service
TNS listener service must be started to allow connections to the Oracle database server. To check if the TNS listener service is running, use the lsnrctl status command.
If the TNS listener service is not started, use the lsnrctl start command to start the service.
Example: A running TNS Listener service on Oracle 19c.
C:\Users\Administrator>lsnrctl status
LSNRCTL for 64-bit Windows: Version 19.0.0.0.0 - Production on 14-OCT-2020 16:45:29
Copyright (c) 1991, 2019, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
STATUS of the LISTENER
------------------------
Alias        LISTENER
Version      TNSLSNR for 64-bit Windows: Version 19.0.0.0.0 - Production
Start Date   14-OCT-2020 11:11:04
Uptime       0 days 5 hr. 34 min. 27 sec
Trace Level   off
Security     ON: Local OS Authentication
SNMP         OFF
Listener Parameter File     D:\oracle\19.3.0\dbhome\network\admin\listener.ora
Listener Log File     D:\oracle\diag\tnslsnr\w12x-5-43\listener\alert\log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ora19c-w2k16)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521ipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=ora19c-w2k16)(PORT=5500))(Security=(my_wallet_directory=D:\ORACLE\admin\orcl\xdb_wallet))(Presentation=HTTP)(Session=RAW))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "orcl" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
Service "orclcXDB" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
Service "pdborcl" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
The command completed successfully
If not,use the following command to start the TNS listener:
C:\Users\Administrator>lsnrctl start
LSNRCTL for 64-bit Windows: Version 19.0.0.0.0 - Production on 21-OCT-2020 15:44:41
Copyright (c) 1991, 2019, Oracle. All rights reserved.
TNS-01106: Listener using listener name LISTENER has already been started
NOTE: The values shown are just examples and might be different on your Oracle instance.
Localhost is Resolvable
Verify if the localhost IP 127.0.0.1 on the Oracle database server is resolvable using the command ping 127.0.0.1 as this will be the IP address that %edition_name% will use to connect to the Oracle instance.
C:\Users\Administrator>ping 127.0.0.1
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Users\Administrator>
Oracle Port Number: The default Oracle port number is 1521. To check, use the netstat and tnsping commands to verify the actual port number.
- NETSTAT
C:\Users\Administrator>netstat -a|more
Active Connections
Proto     Local Address     Foreign Address             State
TCP     0.0.0.0:135     w12x-5-43:0                 LISTENING
TCP     0.0.0.0:445     w12x-5-43:0            LISTENING
TCP     0.0.0.0:1521    w12x-5-43:0                 LISTENING
TCP     0.0.0.0:3389     w12x-5-43:0                 LISTENING
TCP     10.16.10.81:139     w12x-5-43:0                 LISTENING
TCP     10.16.10.81:1521     w12x-5-43:56851     ESTABLISHED
TCP     10.16.10.81:2030     w12x-5-43:0                 LISTENING
TCP     [::]:135         w12x-5-43:0                 LISTENING
TCP     [::]:445             w12x-5-43:0                 LISTENING
TCP     [::]:1521             w12x-5-43:0                 LISTENING
TCP     [::]:3389             w12x-5-43:0                 LISTENING
TCP     [fe80::4d71:5f81:58b0:552c%16]:2030     w12x-5-43:0     LISTENING
TCP     [fe80::713e:e2d4:8e82:5f77%17]:1521     w12x-5-43:56760     ESTABLISHED
TCP     [fe80::713e:e2d4:8e82:5f77%17]:2030     w12x-5-43:0     LISTENING
TCP     [fe80::713e:e2d4:8e82:5f77%17]:56760     w12x-5-43:1521     ESTABLISHED
NOTE: The values shown are just examples and might be different on your Oracle instance.
- TNSPING
C:\Users\Administrator>tnsping 127.0.0.1
TNS Ping Utility for 64-bit Windows: Version 19.0.0.0.0 - Production on 14-OCT-2020 16:54:27
Copyright (c) 1997, 2019, Oracle. All rights reserved.
Used parameter files:
D:\oracle\19.3.0\dbhome\network\admin\sqlnet.ora
Used EZCONNECT adapter to resolve the alias
Attempting to contact (DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=))(ADDRESS=(PROTOCOL=TCP)(HOST=127.0.0.1)(PORT=1521)))
OK (0 msec)
Best Practices and Recommendations
- To enable a full Oracle database instance recovery, all databases including SYSAUX, SYSTEM, UNDOTBS1, USERS and related application databases except for “TEMP” must be selected in the backup source when creating the backup set. Otherwise, without a backup of these databases, a full Oracle database instance recovery will NOT be possible.
- Full database backup or incremental / differential database backups should be scheduled when system activity is low to achieve the best possible performance and to minimize the impact on the database server performance (for example: scheduled to run on weekends).
- For Archived Log backups, the backup frequency should be dependent on the number of transactions or activity on the database. Databases with more transaction should run archived log backup more frequently (for example: instead of a daily backup, it should be run multiple times a day).
- To provide maximum data protection and flexible restore options, it is recommended to configure:
- At least one offsite or cloud destination
- At least one local destination for fast recovery
- Perform test restores periodically to ensure your backup is set up and data are bacekd up properly.
Performing recovery tests can also help identify potential issues or gaps in your recovery plan. It is important that you do not try to make the test easier, as the objective of a successful test is not to demonstrate that everything is flawless. There might be flaws identified in the plan throughout the test, and it is important to identify those flaws.
- The Restore Raw File is for advanced Oracle database administrators and should only be used if you have in-depth knowledge and understanding of Oracle database engine, Oracle database schema, knowledge of the database server and network infrastructure. Therefore, it is not recommended to use this restore option as there is need to utilize additional Oracle techniques and scripts to facilitate a manual database restore.
Please refer to the following articles of Oracle Database Backup and Recovery User's Guide for details:
Oracle 19c
https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/index.html.
Oracle 18c
https://docs.oracle.com/en/database/oracle/oracle-database/18/bradv/index.html.
Oracle 12c
https://docs.oracle.com/database/121/BRADV/title.html.
- To ensure an optimal backup/restoration performance, it is highly recommended to set the temporary directory folder to a local disk location with sufficient free disk space.
- For %edition_name% on Windows, it must be on another location other than Drive C: (e.g., Drive E:).
- For %edition_name% on Linux, it must NOT be on the location of the Oracle Home drive.
Limitations
- %edition_name% does not support Oracle Express Edition or Oracle XE.
- For Oracle database server on Linux CLI environment, %edition_name% does not fully support all restore options (i.e. Restore to Alternate location is not available).
Whenever possible, it is recommended to use %edition_name% on Linux GUI which supports restore to:
- Original Location
- Alternate Location; and
- Restore Raw File
- Backup and restore of Oracle database(s) running on a remote machine is not supported.
- %edition_name% Oracle database module only supports backup and/or restore of standalone Oracle installations. The following advanced Oracle database setups are not supported:
- Clusterware or RAC (Real Application Clusters)
- ASM (Automatic Storage Management)
- Data Guard etc.
- An %edition_name% Oracle database backup set supports the backup and restore of one Oracle instance. For Oracle database server’s setup with multiple instances, a separate backup set is required for each instance.
- To recover a full Oracle database instance, the following items must be selected in the backup source:
- Oracle Database Server must be selected.

-
All databases including SYSAUX, SYSTEM, UNDOTBS1, USERS and related application databases except for “TEMP” must be selected in the backup source when creating the backup set. Otherwise, without a backup of these databases, a full Oracle database instance recovery will NOT be possible.
NOTE: Even if the “TEMP” is selected in the backup source, this database will be skipped during a backup job.
Set the details of the backup set
Name |
The name of the backup set.
|
Backup set type |
the type of the backup set (i.e. Oracle Database Server Backup).
|
Login ID |
The login ID of the Oracle server. The default login ID is system.
|
Password |
The password for the login account.
|
Host |
This value is not user configurable.
|
Port |
The port where the connections to the Oracle server is made. The default port is “1521”.
|
SID |
The Oracle System Identifier.
|
To create a backup set:
- Type in a meaningful backup set name.
- Select the backup set type.
- Enter the Login ID.
- Enter the password.
- Enter the port.
- Enter the SID.
- Click [Next] button to continue.