NetBackup IT Analytics Installation and Upgrade Guide for Linux

Last Published:
Product(s): NetBackup IT Analytics (11.4)
  1. Installation overview
    1.  
      Introduction
    2.  
      NetBackup IT Analytics components
    3.  
      Standard or Shared Services licensing edition
    4.  
      Install options
    5.  
      Multi-language support and locale considerations (Linux)
    6.  
      Supported third-party and open source products
  2. Install NetBackup IT Analytics on a Linux server
    1.  
      Step-1: Get the NetBackup IT Analytics license key file
    2.  
      Step-2: Portal and database deployment strategies
    3.  
      Step-3: Portal and database prerequisites
    4. Step-4: Install Oracle database application binaries (Linux)
      1.  
        Create database and users in existing Oracle farm in a Split Architecture deployment
    5.  
      Step-5: Install the Portal application binaries (Linux)
    6.  
      Step-6: Start the Portal services (Linux)
    7.  
      Step-7: Log into the Portal
    8.  
      Step-8: Install a license
    9. Verify the current license configuration
      1.  
        Run the License Summary report
      2.  
        About NetBackup IT Analytics version and license
      3.  
        View License Details
    10. Next steps
      1.  
        Performing a cold backup of the database
      2.  
        Recommended database backup process
  3. Upgrade NetBackup IT Analytics Portal on Linux
    1.  
      Overview
    2.  
      Upgrade path
    3.  
      Before upgrading
    4. Upgrade NetBackup IT Analytics Portal
      1.  
        Upgrade a shared services environment
      2.  
        Run the upgrade utility installer (Linux)
      3.  
        Known issues
      4.  
        Run the upgrade utility
      5.  
        After the upgrade
      6.  
        Upgrade methods to incorporate enterprise objects
      7. Attribute merging during the Portal upgrade
        1.  
          Attribute Management During the Portal Upgrade
        2.  
          Example of a Merge of Attribute Values
        3.  
          Steps to Rename Duplicate Attributes
        4.  
          Best Practice for Attributes in Multi-Tenancy Environments
    5. Data Collector upgrades
      1.  
        Mandatory prerequisites
    6.  
      Troubleshoot - Manual Data Collector upgrades
    7.  
      Troubleshoot Data Collector upgrade manager upgrade failure and collector bundle download failure on Linux
    8.  
      Collector updates from the NetBackup IT Analytics Portal
  4. Upgrade and Migrate to a new server
    1. Upgrade and migrate to a new server
      1.  
        Install the latest release of NetBackup IT Analytics on the new server
      2.  
        Perform an export of the database on the existing server
      3.  
        Stop Portal and agent services on the new server
      4.  
        Drop and re-create the existing portal user on the new server
      5.  
        Import the database onto the new server
      6.  
        Start Portal and agent services on the new server
      7.  
        Download, install, and execute to upgrade the database schema
    2.  
      Testing
    3.  
      Update Data Collector binaries (if necessary)
  5. Appendix A. X Virtual Frame Buffer
    1.  
      Configure X Virtual Frame Buffer (Xvfb)
  6. Appendix B. Oracle patches for the database server
    1. Apply Oracle 19c October 2024 patch application
      1.  
        Pre-Install setup
      2.  
        OPatch installation steps
      3.  
        Installing the Oracle patches
      4.  
        Validate the database and OJVM patches
      5.  
        Validating JDK version update

Installing the Oracle patches

  1. As a root user, create a copy of Oracle database combo patch and JDK bundle patch files from /tmp to /opt/aptare/oracle folder using following commands:
    mv p36866623_190000_Linux-x86-64.zip /opt/aptare/oracle
    mv p36866578_190000_Linux-x86-64.zip /opt/aptare/oracle
  2. Navigate to /opt/aptare/oracle folder and unzip the file.
    cd /opt/aptare/oracle
    unzip p36866623_190000_Linux-x86-64.zip
    

    The above command will create a 36866623 folder in /opt/aptare/oracle folder.

    unzip p36866578_190000_Linux-x86-64.zip

    The above command will create a 36866578 folder in /opt/aptare/oracle.

    During the unzip if you see the below message put 'y' as shown below.

    replace PatchSearch.xml? [y]es, [n]o, [A]ll, [N]one, [r]ename: y
  3. Set permission on patch folders 36866623 and 36866578
    chown -R aptare:dba 36866623
    chown -R aptare:dba 36866578
    

    Note:

    If you have already installed an Oracle patch previously, skip the following steps from 4 through 10.

  4. As root user copy the two jar files from /tmp to /opt/aptare/oracle/sqldeveloper/sqldeveloper/lib folder.
    mv xdb6.jar /opt/aptare/oracle/sqldeveloper/sqldeveloper/lib
    mv xmlparserv2-sans-jaxp-services.jar 
    /opt/aptare/oracle/sqldeveloper/sqldeveloper/lib
    
  5. Change permissions on the jar files and perl
    cd /opt/aptare/oracle/sqldeveloper/sqldeveloper/lib
    chown -R aptare:dba xdb6.jar
    chown -R aptare:dba xmlparserv2-sans-jaxp-services.jar
    cd /opt/aptare/oracle
    chown -R aptare:dba perl
    chmod -R 775 perl
    
  6. Check if oraInventory folder is available under /opt/. If the folder is not available, then
    cd /opt/aptare/upgrade
    cp oraInventory.zip /opt/
    unzip oraInventory
    
  7. Check permission on /opt/oraInventory folder if it is aptare:dba else change the permission
    cd /opt/
    chown -R aptare:dba oraInventory
    
  8. Run su - aptare command.
  9. Run the following command to attach the Oracle home
    $ORACLE_HOME/oui/bin/runInstaller -silent -ignoreSysPrereqs -invPtrLoc "/opt/aptare/oracle/oraInst.loc" -attachHome ORACLE_HOME="/opt/aptare/oracle" ORACLE_HOME_NAME="OraDB19c_home" INVENTORY_LOCATION="/opt/oraInventory"

    Note:

    If the oracle home is already attached, Oracle Home already exists at this location. Select another location message is displayed. Ignore this message.

  10. Follow the steps to make changes for fuser if you see the fuser error 'Missing command :fuser'
    cd /opt/aptare/oracle/bin/
    touch fuser
    chmod 755 fuser
    
  11. Connect as user aptare, if continuing from step 3 by using the below command else proceed to next step.

    su - aptare

  12. Set PATH. Make sure you set all the paths else patch application might fail.
    export PATH=$PATH:/opt/aptare/oracle/OPatch
    export PATH=$PATH:/usr/ccs/bin
    PATH=$PATH:/opt/aptare/oracle/sqldeveloper/sqldeveloper/lib
    
  13. Check for any OPatch conflicts.

    This will check for conflicts for both the database RU patch and OJVM patches.

    cd /opt/aptare/oracle/36866623
    /opt/aptare/oracle/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -ph ./
    
  14. If no conflicts are detected, run the following command to apply database RU patch from /opt/aptare/oracle/36866623/36912597 folder.
    cd /opt/aptare/oracle/36866623/36912597
       
    /opt/aptare/oracle/OPatch/opatch apply
    
    Verifying environment and performing prerequisite checks...
    OPatch continues with these patches:36912597
    Do you want to proceed? [y|n]
    y
    Is the local system ready for patching? [y|n]
    y
    Backing up files...
    Applying interim patch 36912597 to OH '/opt/aptare/oracle'
    Patching component oracle.rdbms.rsf, 19.0.0.0.0...
    Patching component oracle.rdbms.util, 19.0.0.0.0...
    Patching component oracle.rdbms, 19.0.0.0.0...
    Patching component oracle.assistants.acf, 19.0.0.0.0...
    Patching component oracle.assistants.deconfig, 19.0.0.0.0...
    Patch 36912597 successfully applied.
    Sub-set patch [36538667] has become inactive due to the application of a super-set patch [36912597].
    Sub-set patch [36582781] has become inactive due to the application of a super-set patch [36912597].
    Please refer to Doc ID 2161861.1 for any possible further required actions.
    Log file location: /opt/aptare/oracle/cfgtoollogs/opatch/opatch2024-10-25_14-26-18PM_1.log
    OPatch succeeded.
    
    
  15. Note:

    Ignore any warnings related to rollback of patch. This message shows up when no prior Oracle security patches were applied.

    Run the following commands to apply OJVM patch from /opt/aptare/oracle/36866623/36878697 folder.
    cd /opt/aptare/oracle/36866623/36878697
        /opt/aptare/oracle/OPatch/opatch apply
    Verifying environment and performing prerequisite checks...
    OPatch continues with these patches:36878697
    Do you want to proceed? [y|n]
    y
    Is the local system ready for patching? [y|n]
    y
    Backing up files...
    Applying interim patch '36878697' to OH '/opt/aptare/oracle'
    Patching component oracle.javavm.server, 19.0.0.0.0...
    Patching component oracle.javavm.server.core, 19.0.0.0.0...
    Patching component oracle.rdbms.dbscripts, 19.0.0.0.0...
    Patching component oracle.rdbms, 19.0.0.0.0...
    Patching component oracle.javavm.client, 19.0.0.0.0...
    Patch 36878697 successfully applied.
    Sub-set patch [36414915] has become inactive due to the application of a super-set patch [36878697].
    Refer to Doc ID 2161861.1 for any possible further required actions.
    Log file location: /opt/aptare/oracle/cfgtoollogs/opatch/opatch2024-10-25_14-44-43PM_1.log
    OPatch succeeded.
    
    
    
  16. Navigate to /opt/aptare/oracle/36866578 and check for any OPatch conflicts for the JDK bundle patch.
    cd /opt/aptare/oracle/36866578
    /opt/aptare/oracle/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -ph ./
    
  17. If no conflicts are detected, execute the following commands to apply JDK patch from /opt/aptare/oracle/36866578 folder.
    cd /opt/aptare/oracle/36866578
       
    /opt/aptare/oracle/OPatch/opatch apply
    Verifying environment and performing prerequisite checks...
    OPatch continues with these patches:36866578
    Do you want to proceed? [y|n]
    y
    
    All checks passed.
    Backing up files...
    Applying interim patch '36866578' to OH '/opt/aptare/oracle'
    
    ApplySession: Optional component(s) [ oracle.jdk, 1.8.0.191.0 ], [ oracle.jdk, 1.8.0.391.11]
    not present in the Oracle Home or a higher version is found.
    Patching component oracle.jdk, 1.8.0.201.0...
    Patch 36866578 successfully applied.
    Log file location: /opt/aptare/oracle/cfgtoollogs/opatch/opatch2024-10-25_15-28-55PM_1.log
    
    OPatch succeeded.
    

    Ignore any messages about JDK not present or higher version present, "ApplySession: Optional component(s) [ oracle.jdk, 1.8.0.191.0 ] not present in the Oracle Home or a higher version is found."

  18. Verify OPatch succeeded with the following commands which will display the OPatch application results for the database, OJVM and JDK bundle patches:
    /opt/aptare/oracle/OPatch/opatch lsinventory -detail
        .
        .
        .
    OPatch succeeded.
    
  19. Connect to SQL Plus using following command:

    -bash-4.2$ sqlplus /nolog

    SQL*Plus: Release 19.0.0.0.0 - Production on Mon Oct 26 1:50:12 2024

    Version 19.25.0.0.0

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

  20. Connect as sysdba

    SQL> connect / as sysdba

    Connected to an idle instance.

  21. Start the database.

    SQL> startup

    ORACLE instance started.

    :

    :

    Database mounted.

    Database opened.

  22. Open all pluggable database.

    SQL> alter pluggable database all open;

    Pluggable database altered.

  23. Exit from SQL prompt.

    SQL> quit

  24. Datapatch is run to complete the post-install SQL deployment for the patch being installed.

    Run the following command to apply the patch to the pluggable database (This may take few minutes)

    /opt/aptare/oracle/OPatch/datapatch -verbose
    

    Note:

    If run utlrp.sql message is displayed, to re-validate, run it

    -bash-4.2$ sqlplus / as sysdba
    SQL*Plus: Release 19.0.0.0.0 - Production on Wed Jul 17 13:09:16 2024
    Version 19.24.0.0.0
    Copyright (c) 1982, 2022, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 19c Standard Edition 2 Release 19.0.0.0.0 - Production
    Version 19.24.0.0.0
    SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql
    Session altered.
    :
    :
    
    Installing patches...
    Patch installation complete.  Total patches installed: 9
    Validating logfiles...done
    
    Patch 36414915 rollback (pdb CDB$ROOT): SUCCESS
    logfile: /opt/aptare/cfgtoollogs/sqlpatch/36414915/25700138/36414915_
    rollback_SCDBCNTR_CDBROOT_2024Oct26_01_56_18.log (no errors)
    
    Patch 36912597 apply (pdb CDB$ROOT): SUCCESS
    
    logfile: /opt/aptare/cfgtoollogs/sqlpatch/36912597
    /25871884/36912597_apply_SCDBCNTR_CDBROOT_2024Oct26_01_56_18.log (no errors)  
    
    Patch 36878697 apply (pdb CDB$ROOT): SUCCESS
    
    logfile: /opt/aptare/cfgtoollogs/sqlpatch/36878697
    /25797620/36878697_apply_SCDBCNTR_CDBROOT_2024Oct26_01_56_18.log (no errors)
    
    Patch 36414915 rollback (pdb PDB$SEED): SUCCESS
    
    logfile: /opt/aptare/cfgtoollogs/sqlpatch/36414915
    /25700138/36414915_rollback_SCDBCNTR_PDBSEED_2024Oct26_01_56_59.log (no errors)
    
    Patch 36912597 apply (pdb PDB$SEED): SUCCESS
    
    
    logfile: /opt/aptare/cfgtoollogs/sqlpatch/36912597
    /25871884/36912597_apply_SCDBCNTR_PDBSEED_2024Oct26_01_56_59.log (no errors)
    
    Patch 36878697 apply (pdb PDB$SEED): SUCCESS
    
    logfile: /opt/aptare/cfgtoollogs/sqlpatch/36878697
    /25797620/36878697_apply_SCDBCNTR_PDBSEED_2024Oct26_01_56_59.log (no errors)
    
    Patch 36414915 rollback (pdb SCDB): SUCCESS
    
    logfile: /opt/aptare/cfgtoollogs/sqlpatch/36414915
    /25700138/36414915_rollback_SCDBCNTR_SCDB_2024Oct26_01_56_59.log (no errors)
    
    Patch 36912597 apply (pdb SCDB): SUCCESS
    logfile: /opt/aptare/cfgtoollogs/sqlpatch/36912597
    /25871884/36912597_apply_SCDBCNTR_SCDB_2024Oct26_01_56_59.log (no errors)
    
    Patch 36878697 apply (pdb SCDB): SUCCESS
    
    logfile: /opt/aptare/cfgtoollogs/sqlpatch/36878697
    /25797620/36878697__apply_SCDBCNTR_SCDB_2024Oct26_01_56_59.log (no errors)
    
    SQL Patching tool complete on Sat Oct 26 01:57:38 2024
    
    
    
    
  25. Check the log files in /opt/aptare/cfgtoollogs/sqlpatch/ for errors. The log file name includes the current timestamp:

    Example:

    Log file for this invocation: 
    /opt/aptare/cfgtoollogs/sqlpatch/sqlpatch_20899_2024_10_26_01_55_09/sqlpatch_invocation.log
    
  26. Start all the services as a root user.
    /opt/aptare/bin/aptare start