Differences

This shows you the differences between two versions of the page.

--- public:module:oracle:requirements [2021/04/20 15:44]
ronnie.chan
+++ public:module:oracle:requirements [2021/04/20 16:31] (current)
ronnie.chan
@@ Line 1: / Line 1: @@
 ====== Requirements ======
-----
-.1    Hardware Requirement
+===== 2.1. Hardware Requirement =====
-Refer to the following article for the list of hardware requirements for CloudBacko Pro:
+Refer to [[public:edition:cloudbacko_pro:hardware_requirement|here]] for the list of hardware requirements for CloudBacko Pro.
-FAQ: Ahsay Hardware Requirement List (HRL) for version 8.1 or above
+===== 2.2. Software Requirement =====
-.2    Software Requirement
-Refer to the following article for the list of supported operating systems and application versions:
+  * [[public:edition:cloudbacko_pro:supported_platforms|Supported operating systems]]
+  * [[public:edition:cloudbacko_pro:supported_applications|Supported application versions]]
-FAQ: Ahsay Software Compatibility List (SCL) for version 8.1 or above
+===== 2.3. CloudBacko Pro Installation =====
-.3    CloudBacko Pro Installation
 Make sure the latest version of CloudBacko Pro is installed directly on the machine where the Oracle database server is hosted.
-NOTE
+<WRAP info>
 Backup and restore of Oracle database(s) running on a remote machine is not supported.
-.4    CloudBacko Pro Add-On Module Configuration
+</WRAP>
-Make sure the Oracle Database Server add-on module is enabled on your CloudBacko Pro user account.
-Please contact your backup service provider for more details.
+===== 2.4. CloudBacko Pro Add-On Module Configuration =====
-.5    Backup Quota Requirement
+Make sure the Oracle Database Server add-on module is purchased for your CloudBacko Pro license.
-Make sure that your CloudBacko Pro user account has enough storage quota assigned to accommodate the storage of Oracle database server backup set and retention policy.
+===== 2.5. Java Heap Size =====
-.6    Java Heap Size
 The default Java heap size setting on CloudBacko Pro is 2048MB. For Oracle database backup, it is highly recommended to increase the Java heap size setting to be at least 4096MB to improve backup and restore performance. The actual heap size is dependent on the amount of free memory available on your Oracle server.
-For details on how to modify the Java heap size setting of CloudBacko Pro/AhsayACB, refer to the following article:
+For details on how to modify the Java heap size setting of CloudBacko Pro/AhsayACB, refer to [[public:edition:cloudbacko_pro:faq:how_to_increase_java_heap_size|here]].
-https://wiki.ahsay.com/doku.php?id=public:8011_faq:how_to_modify_the_java_heap_size_of_ahsayobc
+===== 2.6. Temporary Directory Folder =====
-.7    Temporary Directory Folder
 The Temporary directory folder is used by CloudBacko Pro during a backup job as the storage of:
-·         The spooled Oracle database(s) and archived log files
+  * The spooled Oracle database(s) and archived log files
+  * Any incremental or differential delta files generated
-·         Any incremental or differential delta files generated
 It is strongly recommended that the temporary directory folder is located on a local drive with enough free disk space to be used by the spooled databases and archived log files. The temporary folder should not be located on the Windows System C:\ drive or Oracle Home drive.
-NOTE
+<WRAP info>
+  * The calculation of disk space required on the drive where the temporary folder is located is as follows: \\ (Total Database Size * Delta Ratio) * number of backup destinations = Minimum Free Space Required
+</WRAP>
-The calculation of disk space required on the drive where the temporary folder is located is as follows:
+**Example:**
-(Total Database Size * Delta Ratio) * number of backup destinations = Minimum Free Space Required
-Example:
 If the default Delta ratio is 50% for in-file delta, and if the total Oracle database size is 1TB and there is only one backup destination, the minimum free space needed on the drive where the temporary directory folder is located = 1.5TB:
-TB = Total Oracle database size
+  * 1TB = Total Oracle database size
+  * 500GB = Total maximum size of incremental or differential delta files generated
-GB = Total maximum size of incremental or differential delta files generated
 To obtain the size of the data files on the Oracle database instance, use the Oracle RMAN REPORT SCHEMA feature and sum up the total “List of Permanent Datafiles” by running the following command.
-NOTE: The values shown are just examples and might be different on your Oracle instance.
+**NOTE:** The values shown are just examples and might be different on your Oracle instance.
+<code>
 C:\Users\Administrator>set ORACLE_SID=orcl
 C:\Users\Administrator>rman target /
 Recovery Manager: Release 19.0.0.0.0 - Production on Thu Oct 29 18:29:44 2020
 Version 19.3.0.0.0
 Copyright (c) 1982, 2019, Oracle and/or its affiliates.  All rights reserved.
 connected to target database: ORCL (DBID=1562659286)
 RMAN> report schema;
 using target database control file instead of recovery catalog
 Report of database schema for database with db_unique_name ORCL
 List of Permanent Datafiles
 ===========================
 File Size(MB) Tablespace        RB segs  Datafile Name
 ---- -------  -----------       -------- ----------------
     910      SYSTEM             YES     D:\ORACLE\ORADATA\ORCL\SYSTEM01.DBF
     920      SYSAUX             NO      D:\ORACLE\ORADATA\ORCL\SYSAUX01.DBF
     60       UNDOTBS1           YES     D:\ORACLE\ORADATA\ORCL\UNDOTBS01.DBF
     260      PDB$SEED:SYSTEM    NO      D:\ORACLE\ORADATA\ORCL\PDBSEED\SYSTEM01.DBF
     280      PDB$SEED:SYSAUX    NO      D:\ORACLE\ORADATA\ORCL\PDBSEED\SYSAUX01.DBF
     5        USERS              NO      D:\ORACLE\ORADATA\ORCL\USERS01.DBF
     100      PDB$SEED:UNDOTBS1  NO      D:\ORACLE\ORADATA\ORCL\PDBSEED\UNDOTBS01.DBF
     260      ORCLPDB:SYSTEM     NO      D:\ORACLE\ORADATA\ORCL\ORCLPDB\SYSTEM01.DBF
    300      ORCLPDB:SYSAUX     NO      D:\ORACLE\ORADATA\ORCL\ORCLPDB\SYSAUX01.DBF
    100      ORCLPDB:UNDOTBS1   NO      D:\ORACLE\ORADATA\ORCL\ORCLPDB\UNDOTBS01.DBF
    5        ORCLPDB:USERS      NO      D:\ORACLE\ORADATA\ORCL\ORCLPDB\USERS01.DBF
 List of Temporary Files
 =======================
 File Size(MB) Tablespace   Maxsize(MB) Tempfile Name
 ---- -------- -----------  ----------- --------------------
     32       TEMP          32767      D:\ORACLE\ORADATA\ORCL\TEMP01.DBF
     36       PDB$SEED:TEMP 32767      D:\ORACLE\ORADATA\ORCL\PDBSEED\TEMP012020-03-12_18-17-27-260-PM.DBF
     128      ORCLPDB:TEMP  32767      D:\ORACLE\ORADATA\ORCL\ORCLPDB\TEMP01.DBF
+RMAN>
-RMAN>
+</code>
-.8    Windows Requirements
+===== 2.7. Windows Requirements =====
 Ensure that the following Windows requirements and conditions are met.
-.8.1        Supported Windows Server Version
-Oracle 19c (from v8.5.0.63 or above)
+<WRAP indent>
+==== 2.7.1. Supported Windows Server Version ====
-The backup of Oracle 19c is supported on the following Windows Server version:
+<WRAP indent>
-Windows Server 2019
+=== Oracle 19c (from v8.5.0.63 or above) ===
-Windows Server 2012 R2
+The backup of Oracle 19c is supported on the following Windows Server version:
-Windows Server 2016
+| Windows Server 2019 | Windows Server 2012 R2 |
+| Windows Server 2016 |  |
-Oracle 18c (from v8.5.0.77 or above)
+=== Oracle 18c (from v8.5.0.77 or above) ===
 The backup of Oracle 18c is supported on the following Windows Server version:
-Windows Server 2016
+| Windows Server 2016 | Windows Server 2012 |
+| Windows Server 2012 R2 |   |
-Windows Server 2012
-Windows Server 2012 R2
+=== Oracle 12c ===
-Oracle 12c
 The backup of Oracle 12c is supported on the following Windows Server version:
-Windows Server 2012 R2
+| Windows Server 2012 R2 | Windows Server 2008 R2 |
+| Windows Server 2012 | Windows Server 2008 |
-Windows Server 2008 R2
+</WRAP>
-Windows Server 2012
+==== 2.7.2. Windows User Account Permission ====
-Windows Server 2008
-.8.2        Windows User Account Permission
 The Windows user account must be a member of the following security groups:
-·         Administrator
+  * Administrator
+  * ORA_DBA
-·         ORA_DBA
+  * ORA_OraDB19Home1_SYSBACKUP
+  * ORA_OraDB19Home1_SYSDG
-·         ORA_OraDB19Home1_SYSBACKUP
+  * ORA_OraDB19Home1_SYSKM
-·         ORA_OraDB19Home1_SYSDG
-·         ORA_OraDB19Home1_SYSKM
+To verify, click the start menu and search for "Computer Management". Open the application. Locate the Oracle security groups through Computer Management (Local)>System Tools>Locals Users and Groups>Users. Right-click the Administrator and select Properties.
-To verify, click the start menu and search for “Computer Management”. Open the application. Locate the Oracle security groups through Computer Management (Local)>System Tools>Locals Users and Groups>Users. Right-click the Administrator and select Properties.
+{{public:module:oracle:image018.gif}}
 Click the Member Of tab to see the list of Oracle security groups.
+{{public:module:oracle:image019.png}}
+==== 2.7.3. Oracle Database-related Windows Services ====
-.8.3        Oracle Database-related Windows Services
 Ensure that all Oracle database-related services are started:
+  * OracleJobScheduler$SID$
+  * OracleOraDB19Home1MTSRecoveryService
+  * OracleOraDB19Home1TNSListener
+  * OracleRemExecServiceV2
+  * OracleService$SID$
-·         OracleJobScheduler$SID$
+To verify, click the start menu and search for “Services”. Look for the Oracle database-related services. Their statuses should be “Running”.
-·         OracleOraDB19Home1MTSRecoveryService
+{{public:module:oracle:image021.png?700}}
-·         OracleOraDB19Home1TNSListener
+</WRAP>
-·         OracleRemExecServiceV2
+===== 2.8. Oracle Backup Requirements =====
-·         OracleService$SID$
+Ensure that the following requirements and conditions on the Oracle database server are met.
-To verify, click the start menu and search for “Services”. Look for the Oracle database-related services. Their statuses should be “Running”.
+<WRAP important>
+Please consult the Oracle database administrator before making any changes.
+</WRAP>
-.9    Oracle Backup Requirements
+<WRAP indent>
-Ensure that the following requirements and conditions on the Oracle database server are met.
-NOTE: Please consult the Oracle database administrator before making any changes.
+==== 2.8.1. Oracle Tools ====
-.9.1        Oracle Tools
 Although the following tools are usually installed by default on all Oracle database installations, ensure that the following tools are installed on the Oracle database server and they are functioning correctly.
-·         RMAN (Recovery manager) - is required by CloudBacko Pro for both full database and archive log backups.
+  * **RMAN (Recovery manager)** - is required by CloudBacko Pro for both full database and archive log backups.
+<WRAP indent>
 To verify if RMAN is installed on the Oracle database server and is working properly, run the following command.
 Example of RMAN running in Oracle 19c
+<code>
 C:\Users\Administrator>set ORACLE_SID=orcl
+C:\Users\Administrator>rman target /
-C:\Users\Administrator>rman target /
 Recovery Manager: Release 19.0.0.0.0 - Production on Thu Nov 12 09:36:48 2020
 Version 19.3.0.0.0
 Copyright (c) 1982, 2019, Oracle and/or its affiliates.  All rights reserved.
 connected to target database: ORCL (DBID=1562659286)
+RMAN>
-RMAN>
+</code>
+</WRAP>
-·         SQL*Plus – is required by CloudBacko Pro during Oracle Backup Set creation, backup and restore.
+  * **SQL*Plus** – is required by CloudBacko Pro during Oracle Backup Set creation, backup and restore.
+<WRAP indent>
 To verify if SQL*Plus is installed on the Oracle database server and is working properly, run the following command sqlplus / as sysdba.
 Example of SQL*Plus running in Oracle 19c
+<code>
 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>
-.9.2        Oracle Internal Process Checking
+</code>
+</WRAP>
+==== 2.8.2. Oracle Internal Process Checking ====
 For the Oracle instance to run smoothly, ensure that the following internal processes are working well:
-·         PMON (Process Monitor)
+  * **PMON** (Process Monitor)
+  * **PSP0** (Process Spawner Process)
-·         PSP0 (Process Spawner Process)
+  * **MMAN** (Memory Manager Process)
-·         MMAN (Memory Manager Process)
+  * **DBW0** (Database Writer)
-·         DBW0 (Database Writer)
+  * **ARC0** (Archive Process (or thread on Windows))
-·         ARC0 (Archive Process (or thread on Windows))
+  * **LGWR** (Log Writer)
-·         LGWR (Log Writer)
+  * **CKPT** (Checkpoint process (thread on Windows) that runs by default on Windows)
-·         CKPT (Checkpoint process (thread on Windows) that runs by default on Windows)
+  * **SMON** (System Monitor)
-·         SMON (System Monitor)
+  * **RECO** (Distributed Recovery Background Process)
-·         RECO (Distributed Recovery Background Process)
 To check this, click the start menu and search for “cmd”. Open the command prompt as administrator.
@@ Line 343: / Line 256: @@
 Run the SQLPlus to connect to the Oracle database server. Once connected, use the following SQL query to verify if the internal processes are running.
+<code>
 C:\Users\Administrator>sqlplus / as sysdba
@@ Line 510: / Line 424: @@
 SQL>
-.9.3        Supported Oracle Database Server Version
+</code>
+==== 2.8.3. Supported Oracle Database Server Version ====
 CloudBacko Pro supports the following versions of Oracle database server:
-·         Oracle 19c
+  * Oracle 19c
+  * Oracle 18c
-·         Oracle 18c
+  * Oracle 12c
-·         Oracle 12c
 To verify if the Oracle database server version is supported by CloudBacko Pro, use the following SQL query.
-Oracle 19c
+**Oracle 19c**
+<code>
 C:\Users\Administrator>sqlplus / as sysdba
@@ Line 539: / Line 455: @@
 SQL>
+</code>
-Oracle 18c
+**Oracle 18c**
+<code>
 C:\Users\Administrator>sqlplus / as sysdba
@@ Line 558: / Line 477: @@
 SQL>
-Oracle 12c
+</code>
+**Oracle 12c**
+<code>
 C:\Users\Administrator>sqlplus / as sysdba
@@ Line 573: / Line 496: @@
 SQL>
-.9.4        System Identifier (SID)
+</code>
+==== 2.8.4 System Identifier (SID) ====
 Make sure the System Identifier (SID) is correct by using the following SQL query.
+<code>
 SQL> select instance from v$thread;
 INSTANCE
 ---------------------------------------------------------------
 orcl
 SQL>
+</code>
-NOTE: The instance shown is just an example. The SID may be different on your Oracle instance.
+<WRAP info>
+The instance shown is just an example. The SID may be different on your Oracle instance.
+</WRAP>
 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++).
+<code>
 ###########################################
 # Database Identification
 ###########################################
 db_name="orcl"
+</code>
+==== 2.8.5. Oracle_Home Path ====
+**Oracle 19c**
-.9.5        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”.
+<code>
 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
 SQL>
+</code>
-NOTE: The directory path shown is just an example. The Oracle_Home path may be different on your Oracle instance.
+<WRAP info>
+The directory path shown is just an example. The Oracle_Home path may be different on your Oracle instance.
+</WRAP>
 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++).
+<code>
 ###########################################
 # File Configuration
 ###########################################
 control_files=("D:\app\oracle\oradata\ORCL\control01.ctl", "D:\app\oracle\oradata\ORCL\control02.ctl")
+###########################################
+</code>
- ###########################################
+**Oracle 18c**
-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”.
+<code>
 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
 SQL>
+</code>
-NOTE: The directory path shown is just an example. The Oracle_Home path may be different on your Oracle instance.
+<WRAP info>
+The directory path shown is just an example. The Oracle_Home path may be different on your Oracle instance.
+</WRAP>
 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++).
+<code>
 ###########################################
 # File Configuration
 ###########################################
 control_files=("D:\app\oracle\oradata\orcl18c\control01.ctl", "D:\app\oracle\oradata\orcl18c\control02.ctl")
+###########################################
+</code>
- ###########################################
+**Oracle 12c**
-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”.
+<code>
 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
 SQL>
+</code>
-NOTE: The directory shown is just an example. The Oracle_Home path may be different on your Oracle instance.
+<WRAP info>
+The directory shown is just an example. The Oracle_Home path may be different on your Oracle instance.
+</WRAP>
 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++).
+<code>
 ###########################################
 # 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
+</code>
-WARNING
+<WRAP important>
 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 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.
+. The SQL query returns an empty or null value.
+</WRAP>
 Example of an SQL query return with a null value of the Oracle_Home path
+<code>
 SQL> SELECT file_spec FROM DBA_LIBRARIES WHERE library_name = 'DBMS_SUMADV_LIB';
 no rows selected
 SQL>
-.9.6        Database Status
+</code>
+==== 2.8.6. Database Status ====
 Ensure that the status of Oracle instance is “Open”. To check, use the following query.
+<code>
 SQL> select instance_name, status from v$instance;
 INSTANCE_NAME    STATUS
 --------------   ----------------------------------------------
 orcl             OPEN
 SQL>
-.9.7        Archived Log Mode
+</code>
+==== 2.8.7. Archived Log Mode ====
 Ensure that the database instance is in Archived Log mode. To check, use the following command.
+<code>
 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>
+</code>
-SQL>
+<WRAP info>
+The values shown are just examples and might be different on your Oracle instance.
+</WRAP>
-NOTE: The values shown are just examples and might be different on your Oracle instance.
+==== 2.8.8. Java Installation ====
-.9.8        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”.
+<code>
 SQL> select comp_name, status from dba_registry;
 COMP_NAME                                    STATUS
 --------------                               ------------
 Oracle Database Catalog Views                VALID
 Oracle Database Packages and Types           VALID
 Oracle Real Application Clusters             OPTION OFF
 COMP_NAME                                    STATUS
 --------------                               ------------
 JServer JAVA Virtual Machine                 VALID
 Oracle XDK                                   VALID
 Oracle Database Java Packages                VALID
 COMP_NAME                                    STATUS
 --------------                               ------------
 OLAP Analytic Workspace                      VALID
 Oracle XML Database                          VALID
 Oracle Workspace Manager                     VALID
 COMP_NAME                                    STATUS
 --------------                               ------------
 Oracle Text                                  VALID
 Oracle Multimedia                            VALID
 Spatial                                      VALID
 COMP_NAME                                    STATUS
 --------------                               ------------
 Oracle OLAP API                              VALID
 Oracle Label Security                        VALID
 Oracle Database Vault                        VALID
 rows selected.
 SQL>
+</code>
+<WRAP important>
+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 assistance.
-WARNING
+</WRAP>
-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 assistance.
+==== 2.8.9. JAVASYSPRIV Permission for Oracle System Account ====
-.9.9        JAVASYSPRIV Permission for Oracle System Account
 The Oracle system account is used by CloudBacko Pro 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 SQL query to assign.
+<code>
 SQL> select * from DBA_ROLE_PRIVS where upper(grantee)='SYSTEM';
 GRANTEE      GRANTED_ROLE            ADM DEL DEF COM INH
 -------      ----------              --- --- --- --- ---
 SYSTEM       DBA                     NO  NO  YES NO  NO
 SYSTEM       JAVASYSPRIV             NO  NO  YES NO  NO
 GRANTEE      GRANTED_ROLE            ADM DEL DEF COM INH
 -------      ----------              --- --- --- --- ---
 SYSTEM       DBA                     NO  NO  YES YES  NO
 SYSTEM       AQ_ADMINISTRATOR_ROLE   YES  NO  YES YES  NO
 SQL>
+</code>
 If not, grant javasyspriv to the system account by using the following SQL query.
+<code>
 SQL> grant javasyspriv to system;
 Grant succeeded.
 SQL>
-.9.10     SYSDBA Privileges for Oracle System Account
+</code>
+==== 2.8.10. SYSDBA Privileges for Oracle System Account ====
 To check if the system account has sysdba privileges, use the following SQL query.
+<code>
 SQL> select * from v$pwfile_users where sysdba='TRUE';
 USERNAME SYSDB SYSOP SYSAS SYSBA SYSDG SYSKM ACCOUNT_STATUS
 -------- ----- ----- ----- ----- ----- ----- --------------
 SYST     TRUE  TRUE  FALSE FALSE FALSE FALSE OPEN
 SQL>
+</code>
 If not, grant sysdba to the system account using the following SQL query.
-Oracle 19c and Oracle 18c
+**Oracle 19c** and **Oracle 18c**
+<code>
 SQL> grant sysdba to system container=ALL;
 Grant succeeded.
 SQL>
-Oracle 12c
+</code>
+**Oracle 12c**
+<code>
 SQL> grant sysdba to system;
+Grant succeeded.
-Grant succeeded.
+SQL>
+</code>
+==== 2.8.11. TNS Listener Service ====
-SQL>
-.9.11     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.
@@ Line 988: / Line 817: @@
 Example: A running TNS Listener service on Oracle 19c.
+<code>
 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=TCP)(HOST=ora19c-w2k16)(PORT=1521)))
 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\ora19c-w2k16\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 "52448234712340b69f274bcc790ecfe0" has 1 instance(s).
   Instance "orcl", status READY, has 1 handler(s) for this service...
 Service "9400891b61bb4c4c8b3997957ffa8c8e" has 1 instance(s).
   Instance "orcl", status READY, has 1 handler(s) for this service...
 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 "orclXDB" has 1 instance(s).
   Instance "orcl", status READY, has 1 handler(s) for this service...
 Service "orclpdb" has 1 instance(s).
   Instance "orcl", status READY, has 1 handler(s) for this service...
 The command completed successfully
+C:\Users\Administrator>
+</code>
-C:\Users\Administrator>
+<WRAP indent>
+The values shown are just examples and might be different on your Oracle instance.
+</WRAP>
-NOTE: The values shown are just examples and might be different on your Oracle instance.
+==== 2.8.12. Localhost is Resolvable ====
-.9.12     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 CloudBacko Pro will use to connect to the Oracle instance.
+<code>
 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>
-.9.13     Oracle Port Number
+</code>
+==== 2.8.13. 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
+**NETSTAT**
+<code>
 C:\Users\Administrator>netstat -a|more
 Active Connections
 Proto   Local Address       Foreign Address        State
 TCP     0.0.0.0:135         ora19c-w2k16:0         LISTENING
 TCP     0.0.0.0:445         ora19c-w2k16:0         LISTENING
 TCP     0.0.0.0:1521        ora19c-w2k16:0         LISTENING
 TCP     0.0.0.0:2179        ora19c-w2k16:0         LISTENING
 TCP     0.0.0.0:3389        ora19c-w2k16:0         LISTENING
 TCP     0.0.0.0:5500        ora19c-w2k16:0         LISTENING
 TCP     0.0.0.0:5985        ora19c-w2k16:0         LISTENING
 TCP     0.0.0.0:47001       ora19c-w2k16:0         LISTENING
 TCP     0.0.0.0:49664       ora19c-w2k16:0         LISTENING
 TCP     0.0.0.0:49665       ora19c-w2k16:0         LISTENING
 TCP     0.0.0.0:49666       ora19c-w2k16:0         LISTENING
 TCP     0.0.0.0:49667       ora19c-w2k16:0         LISTENING
 TCP     0.0.0.0:49668       ora19c-w2k16:0         LISTENING
 TCP     0.0.0.0:49669       ora19c-w2k16:0         LISTENING
 TCP     0.0.0.0:49670       ora19c-w2k16:0         LISTENING
 TCP     0.0.0.0:49697       ora19c-w2k16:0         LISTENING
 TCP     10.16.10.123:139    ora19c-w2k16:0         LISTENING
 TCP     10.16.10.123:2030   ora19c-w2k16:0         LISTENING
 TCP     10.16.10.123:3389   192.168.12.1:56719     ESTABLISHED
 TCP     10.16.10.123:49671  40.90.189.152:https    ESTABLISHED
 TCP     10.16.10.123:49690  40.90.189.152:https    ESTABLISHED
 TCP     10.16.10.123:51761  ti-in-f95:https        ESTABLISHED
 TCP     127.0.0.1:1521      ora19c-w2k16:51740     ESTABLISHED
 TCP     127.0.0.1:51740     ora19c-w2k16:1521      ESTABLISHED
 TCP     172.16.10.123:139   ora19c-w2k16:0         LISTENING
+-- More  --
--- More  --
+</code>
-NOTE: The values shown are just examples and might be different on your Oracle instance.
+<WRAP info>
+The values shown are just examples and might be different on your Oracle instance.
+</WRAP>
-TNSPING
+**TNSPING**
+<code>
 C:\Users\Administrator>tnsping 127.0.0.1
@@ Line 1185: / Line 950: @@
 C:\Users\Administrator>
+</code>

User Tools

Site Tools

Differences

Page Tools