NetBackup IT Analytics Installation and Upgrade Guide for Linux
- Installation overview
- Install NetBackup IT Analytics on a Linux server
- Step-4: Install Oracle database application binaries (Linux)
- Verify the current license configuration
- Next steps
- Upgrade NetBackup IT Analytics Portal on Linux
- Upgrade NetBackup IT Analytics Portal
- Data Collector upgrades
- Upgrade and Migrate to a new server
- Upgrade and migrate to a new server
- Upgrade and migrate to a new server
- Appendix A. X Virtual Frame Buffer
- Appendix B. Oracle patches for the database server
Create database and users in existing Oracle farm in a Split Architecture deployment
This procedure provides the steps to create database and users in an existing Oracle farm during a Split-Architecture deployment of NetBackup IT Analytics.
Table: Prerequisites for creating database and users in existing Oracle farm
Requirement | Description |
---|---|
Oracle | Version 19c with latest security patches applied. |
Pluggable Database (PDB) |
|
Create database and users:
- Create tablespaces specific to NetBackup IT Analytics.
Tablespace name
Reference commands
aptare_tbs_data_1m
CREATE TABLESPACE aptare_tbs_data_1m DATAFILE <datafile path> SIZE 8G AUTOEXTEND ON NEXT 1G MAXSIZE UNLIMITED LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE DEFAULT NOCOMPRESS SEGMENT SPACE MANAGEMENT AUTO /
aptare_tbs_idx_1m
CREATE TABLESPACE aptare_tbs_idx_1m DATAFILE <datafile path> SIZE 8G AUTOEXTEND ON NEXT 1G MAXSIZE UNLIMITED LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE DEFAULT NOCOMPRESS SEGMENT SPACE MANAGEMENT AUTO /
aptare_tbs_data_20m
CREATE TABLESPACE aptare_tbs_data_20m DATAFILE <datafile path> SIZE 8G AUTOEXTEND ON NEXT 1G MAXSIZE UNLIMITED LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE DEFAULT NOCOMPRESS SEGMENT SPACE MANAGEMENT AUTO /
aptare_tbs_idx_10m
CREATE TABLESPACE aptare_tbs_idx_10m DATAFILE <datafile path> SIZE 8G AUTOEXTEND ON NEXT 1G MAXSIZE UNLIMITED LOGGING ONLINE PERMANENT BLOCKSIZE 8192 EXTENT MANAGEMENT LOCAL AUTOALLOCATE DEFAULT NOCOMPRESS SEGMENT SPACE MANAGEMENT AUTO /
aptare_tbs_data_200m
CREATE TABLESPACE aptare_tbs_data_200m DATAFILE <datafile path> SIZE 8G AUTOEXTEND ON NEXT 1G MAXSIZE UNLIMITED LOGGING ONLINE PERMANENT BLOCKSIZE 16K EXTENT MANAGEMENT LOCAL AUTOALLOCATE DEFAULT NOCOMPRESS SEGMENT SPACE MANAGEMENT AUTO /
aptare_tbs_idx_100m
CREATE TABLESPACE aptare_tbs_idx_100m DATAFILE <datafile path> SIZE 8G AUTOEXTEND ON NEXT 1G MAXSIZE UNLIMITED LOGGING ONLINE PERMANENT BLOCKSIZE 16K EXTENT MANAGEMENT LOCAL AUTOALLOCATE DEFAULT NOCOMPRESS SEGMENT SPACE MANAGEMENT AUTO /
aptare_tbs_data_200m_lob
CREATE TABLESPACE aptare_tbs_data_200m_lob DATAFILE <datafile path> SIZE 8G AUTOEXTEND ON NEXT 1G MAXSIZE UNLIMITED LOGGING ONLINE PERMANENT BLOCKSIZE 16K EXTENT MANAGEMENT LOCAL AUTOALLOCATE DEFAULT NOCOMPRESS SEGMENT SPACE MANAGEMENT AUTO /
aptare_tbs_data_200m_col
CREATE TABLESPACE aptare_tbs_data_200m_col DATAFILE <datafile path> SIZE 8G AUTOEXTEND ON NEXT 1G MAXSIZE UNLIMITED LOGGING ONLINE PERMANENT BLOCKSIZE 16K EXTENT MANAGEMENT LOCAL AUTOALLOCATE DEFAULT NOCOMPRESS SEGMENT SPACE MANAGEMENT AUTO /
aptare_tbs_iot_200m
CREATE TABLESPACE aptare_tbs_iot_200m DATAFILE <datafile path> SIZE 8G AUTOEXTEND ON NEXT 1G MAXSIZE UNLIMITED LOGGING ONLINE PERMANENT BLOCKSIZE 16K EXTENT MANAGEMENT LOCAL AUTOALLOCATE DEFAULT NOCOMPRESS SEGMENT SPACE MANAGEMENT AUTO /
- Create two database schema users: portal and aptare_ro.
The Portal password must be portal and the password of aptare_ro user must be aptaresoftware123. You can change both the passwords after the NetBackup IT Analytics Portal setup is complete.
See Assign custom passwords during user creation to change these passwords at user creation time due to password policies configured on Oracle.
- Create the following required database directories with the required permissions:
CREATE OR REPLACE DIRECTORY UNIX_DIR AS '/u01/aptare/database'; CREATE OR REPLACE DIRECTORY LOGFILE_DIR AS '/tmp'; GRANT READ,WRITE ON DIRECTORY UNIX_DIR to portal; GRANT READ,WRITE ON DIRECTORY LOGFILE_DIR to portal;
Note that he folder path on the database server filesystem can be changed to other path as well.
- Grant the following privileges to the respective user schema:
User-specific Schema
Grants required for the schema
APTARE_RO
GRANT CONNECT TO aptare_ro; GRANT CREATE ANY CONTEXT TO aptare_ro; GRANT CREATE SYNONYM TO aptare_ro;
PORTAL
GRANT CONNECT TO PORTAL; GRANT RESOURCE TO PORTAL; GRANT CREATE TABLESPACE TO PORTAL; GRANT UNLIMITED TABLESPACE TO PORTAL; GRANT QUERY REWRITE TO PORTAL; GRANT SELECT_CATALOG_ROLE TO PORTAL; GRANT SELECT ANY DICTIONARY TO PORTAL; GRANT CREATE ANY LIBRARY TO PORTAL; GRANT SELECT ON dba_free_space TO PORTAL; GRANT SELECT ON dba_data_files TO PORTAL; GRANT SELECT ON dba_temp_files TO PORTAL; GRANT CREATE SESSION, CREATE ANY CONTEXT TO PORTAL;
Statement to execute the dbms_session package:
GRANT EXECUTE ON DBMS_SESSION TO PORTAL; GRANT EXECUTE ON DBMS_LOCK TO PORTAL;
Statement to execute the dbms_utility package
GRANT EXECUTE ON DBMS_UTILITY TO PORTAL; GRANT CREATE VIEW TO PORTAL; GRANT CREATE TABLE TO PORTAL;
Statement to create materialized views
GRANT CREATE MATERIALIZED VIEW TO PORTAL;
Statement to set up the logging directory
GRANT CREATE ANY DIRECTORY TO PORTAL;
Statement to add for Oracle 19c
GRANT CREATE JOB TO PORTAL; GRANT EXECUTE ON DBMS_SCHEDULER TO PORTAL;
Statement to add security
GRANT EXECUTE ON SYS.DBMS_LOB TO PORTAL; GRANT EXECUTE ON SYS.UTL_FILE TO PORTAL; GRANT EXECUTE ON SYS.DBMS_RANDOM TO PORTAL; GRANT EXECUTE ON SYS.DBMS_JOB TO PORTAL; GRANT EXECUTE ON SYS.DBMS_SQL TO PORTAL; GRANT READ ON SYS.ALL_DIRECTORIES TO PORTAL; GRANT READ ON SYS.DUAL TO PORTAL;
Statement to enable FIPS compliance
GRANT EXECUTE ON DBMS_CRYPTO TO PORTAL;
If DBAs want to assign custom passwords for portal and aptare_ro during user creation, ensure the following changes are made to the scripts and config files so that the schema creation will succeeded.
To assign custom passwords during user creation:
- Copy the content of Portal ISO to a local directory in the Portal server so that files can be edited.
# mount -o loop itanalytics_installer_11300_linux.iso /mnt/diska # mkdir /tmp/portal # cp -r /mnt/diska/* /tmp/portal
- Run the Portal installer
Itanalyticsinstaller.sh
.When the installer prompts for Oracle SID, provide the Service Name for the database.
Reject running the
create_itanalytics_schema_objects.sh
when prompted by entering n.If the test connection to the database fails for any reason, verify and edit the values of HOST, PORT, SERVICE_NAME, and SID in
/tmp/portal/oracle/tnsnames.ora
file and again runItanalyticsinstaller.sh
.
- Update the
/tmp/portal/create_itanalytics_schema_objects.sh
script at the following places.ORACLE_PORTAL_SEC_CODE=<password for portal user> ORACLE_APTARE_RO_SEC_CODE=<password for aptare_ro user>
- Update the file
<INSTALL_PATH>/aptare/portalconf/portal.properties
at the following placesdb.password=<unencrypted password for portal user> db.password.encrypted=<keep this field empty> db.ro_user_password=<unencrypted password for aptare_ro user> db.ro_user_password.encrypted=<keep this field empty>
- Update the file
<INSTALL_PATH>/aptare/datarcvrconf/datrarcvrproperties.xml
at the following places. Note that these passwords will be encrypted once the portal service is started.<Passwrod>unencrypted password for portal user</Password> <ro_passwrod>unencrypted password for aptare_ro user</ro_password>
If the SID and Service Name of the database are not the same, verify that the URL and oracle_service_name tags are updated with the Service Name instead of the SID.
<URL>jdbc:oracle:thin:@//10.xx.yy.zz:1521/Service_Name</URL> <oracle_service_name>Service_Name</oracle_service_name>
- Edit the
<INSTALL_PATH>/aptare/database/load_scripts/load_nbu_data.plb
file and comment out the call to load_discovery.-- @../load_scripts/load_discovery
Note:
The path
<INSTALL_PATH>/aptare/database/
will not exist until you run create_itanalytics_schema_objects.sh as mentioned below at least once. - Ensure that database supports NVARCHAR2 size upto 2048. In case it is not possible to make changes, edit the below file as follows:
# vi /opt/aptare/database/stored_procedures/cmv/create_cmv_schema.plb
Change the below line (no 9) for table apt_cmv_reason.
description NVARCHAR2(2048)
to
description NVARCHAR2(2000)
- Run the schema creation script as aptare user. Ensure there are no "ORA-" errors generated in the log file.
# su - aptare # create_itanalytics_schema_objects.sh -h <Oracle database server IP address> -p <Oracle database listener port>
- Install the license.
# <INSTALL_PATH>/aptare/utils/installlicenseUI.sh /mnt/diska/foundation_license.slf
- Start the services.
# <INSTALL_PATH>/aptare/bin/aptare start