NetBackup IT Analytics Installation and Upgrade Guide for Linux

Last Published:
Product(s): NetBackup IT Analytics (11.1)
  1. Install the NetBackup IT Analytics Portal on a Linux server
    1.  
      Introduction
    2.  
      Multi-language support and locale considerations (Linux)
    3.  
      OVA-based deployment on VMware ESXi
    4. Installer-based deployment
      1.  
        Task 1: Portal and database deployment strategies (Linux)
      2.  
        Task 2: Pre-installation configuration (Linux)
      3.  
        Task 3: Install Oracle database application binaries (Linux)
      4.  
        Task 4: Install the Portal application binaries (Linux)
      5.  
        Task 5: Installing the database schema (Linux)
      6.  
        Task 6: Start the Portal services (Linux)
      7.  
        Task 7: Request the license key file (Linux)
      8.  
        Task 8: Log into the Portal
      9.  
        Task 9: Install the license key file (Linux)
      10.  
        Task 10: Performing a cold backup of the database (Linux)
      11.  
        Recommended database backup process
    5.  
      Supported third-party and open source products
    6.  
      Uninstall the NetBackup IT Analytics Portal
  2. 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.  
      Collector updates from the NetBackup IT Analytics Portal
  3. Oracle patches for the database server
    1.  
      Apply Oracle-recommended patches
    2. Apply Oracle 19c April 2023 patch application on Linux
      1.  
        Pre-Install setup
      2.  
        OPatch installation steps
      3.  
        Installing the patches
      4.  
        Validate the database and OJVM patch
      5.  
        Validate the JDK version update
  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)

Installing the patches

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

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

    unzip p35058163_190000_Linux-x86-64.zip

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

    If the below message is displayed while you unzip the file, enter y in its response.

    replace PatchSearch.xml? [y]es, [n]o, [A]ll, [N]one, [r]ename: is displayed.

  3. Set permission on patch folder 35004974 and 35058163.
    chown -R aptare:dba 35004974
    chown -R aptare:dba 35058163

    Note:

    If the Oracle patch is not Veritas provided and have already installed Oracle patch, skip the following steps from 4 through 10.

  4. As a root user, copy the two jar files from /tmp to /opt/aptare/oracle/sqldeveloper/sqldeveloper/lib folder.
    cd /tmp
    unzip /tmp/xdb6.zip
    unzip /tmp/xmlparserv2-sans-jaxp-services.zip
    
    mv /tmp/xdb6.jar /opt/aptare/oracle/sqldeveloper/sqldeveloper/lib
    mv /tmp/xmlparserv2-sans-jaxp-services.jar /opt/aptare/oracle
    /sqldeveloper/sqldeveloper/lib
  5. Change the permissions on the jar files and the 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/
    cd /opt
    unzip oraInventory.zip
    
  7. Check permission on /opt/oraInventory folder if it is aptare:dba else change the permission.
    cd /opt/
    chown -R aptare:dba oraInventory
    
  8. su - aptare
  9. Execute 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"

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

    Ignore the 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 aptare user, if continuing from step-3, by using the below command else go to step 12.

    su - aptare

  12. In this step, set the 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 step will verify for any conflicts on both the database RU patch and OJVM patches.
    cd /opt/aptare/oracle/35058163
    /opt/aptare/oracle/OPatch/opatch prereq 
    CheckConflictAgainstOHWithDetail -ph ./
    
  14. If no conflicts are detected, execute the following commands to apply database RU patch from /opt/aptare/oracle/35058163/35042068 folder.
    cd /opt/aptare/oracle/35058163/35042068
    /opt/aptare/oracle/OPatch/opatch apply
    
    Verifying environment and performing prerequisite checks...
    
    OPatch continues with these patches:   35042068
    
    Do you want to proceed? [y|n]
    y
    
    Is the local system ready for patching? [y|n]
    y
    
    Patching component oracle.jdk, 1.8.0.201.0...
    
    Patch 35042068 successfully applied.
    
    Sub-set patch [34777391] has become inactive due to the application of a 
    super-set patch [35042068]
    
    Sub-set patch [34765931] has become inactive due to the application of a 
    super-set patch [35042068].
    
    Please refer to Doc ID 2161861.1 for any possible 
    further required actions.
    
    Log file location: /opt/aptare/oracle/cfgtoollogs/opatch/
    opatch2023-04-28_15-54-13PM_1.log
    
     OPatch completed with warnings.
    

    Note:

    Ignore the warning message if it is related to rollback of patch 30565805. The message is displayed when no prior Oracle security patches were applied.

  15. Run the following commands to apply OJVM patch from /opt/aptare/oracle/35058163/35050341 folder.
    cd /opt/aptare/oracle/35058163/35050341
    /opt/aptare/oracle/OPatch/opatch apply
    Verifying environment and performing prerequisite checks...
    OPatch continues with these patches:   35050341
    Do you want to proceed? [y|n]
    y
    Is the local system ready for patching? [y|n]
    y
    Patching component oracle.javavm.server, 19.0.0.0.0...
    Patching component oracle.javavm.server.core, 19.0.0.0.0...
    .
    .
    Patch 35050341 successfully applied.
    Sub-set patch [34786990] has become inactive due to the application of 
    a super-set patch [35050341].
       
    
    Log file location: /opt/aptare/oracle/cfgtoollogs/opatch/
    opatch2023-04-28_16-02-35PM_1.log
    OPatch succeeded.
    

    Ignore any warnings related to rollback of patch 30565805. This message is displayed when no pror Oracle security patches are applied.

  16. Navigate to /opt/aptare/oracle/35004974 and check for any OPatch conflicts for the JDK bundle patch.

    cd /opt/aptare/oracle/35004974

    /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/35004974 folder

    cd /opt/aptare/oracle/35004974

    /opt/aptare/oracle/OPatch/opatch apply

    Verifying environment and performing prerequisite checks...
    OPatch continues with these patches:   35004974
    Do you want to proceed? [y|n]
    y
    Patching component oracle.jdk, 1.8.0.201.0...
    Patch 35004974 successfully applied.
    Log file location: /opt/aptare/oracle/cfgtoollogs/
    opatch/opatch2023-04-28_16-09-38PM_1.log
    OPatch succeeded.
    
  18. Verify OPatch succeeded with the following commands which will display the OPatch application results for the database, OJVM, and JDK bundle patches:

    Note:

    The commands will display the OPatch application of both the database and OJVM patches.

    cd /opt/aptare/oracle/OPatch/opatch lsinventory -detail
    .
    .
    .
    OPatch succeeded.
  19. Connect to sqlplus using the following command:
    -bash-4.2$ sqlplus /nolog
    SQL*Plus: Release 19.0.0.0.0 - Production on Fri Apr 28 16:20:21
    Version 19.19.0.0.0
    Copyright (c) 1982, 2022, 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. Run the database patch to complete the post-install SQL deployment for the patch being installed.

    Run the following commands to apply the patch to the pluggable database (this may take few minutes).

    /opt/aptare/oracle/OPatch/datapatch -verbose
    Patch installation complete.  Total patches installed: 9
    
    Validating logfiles...done
    
    Patch 34786990 rollback (pdb CDB$ROOT): SUCCESS
      logfile: /opt/aptare/cfgtoollogs/sqlpatch/34786990/25032666
    /34786990_rollback_SCDBCNTR_CDBROOT_2023Apr28_16_22_45.log (no errors)
    Patch 35042068 apply (pdb CDB$ROOT): SUCCESS
      logfile: /opt/aptare/cfgtoollogs/sqlpatch/35042068/25183678
    /35042068_apply_SCDBCNTR_CDBROOT_2023Apr28_16_22_45.log (no errors)
    Patch 35050341 apply (pdb CDB$ROOT): SUCCESS
      logfile: /opt/aptare/cfgtoollogs/sqlpatch/35050341/25148755
    /35050341_apply_SCDBCNTR_CDBROOT_2023Apr28_16_22_45.log (no errors)
    Patch 34786990 rollback (pdb PDB$SEED): SUCCESS
      logfile: /opt/aptare/cfgtoollogs/sqlpatch/34786990/25032666
    /34786990_rollback_SCDBCNTR_PDBSEED_2023Apr28_16_23_29.log (no errors)
    Patch 35042068 apply (pdb PDB$SEED): SUCCESS
      logfile: /opt/aptare/cfgtoollogs/sqlpatch/35042068/25183678
    /35042068_apply_SCDBCNTR_PDBSEED_2023Apr28_16_23_29.log (no errors)
    Patch 35050341 apply (pdb PDB$SEED): SUCCESS
      logfile: /opt/aptare/cfgtoollogs/sqlpatch/35050341/25148755
    /35050341_apply_SCDBCNTR_PDBSEED_2023Apr28_16_23_29.log (no errors)
    Patch 34786990 rollback (pdb SCDB): SUCCESS
      logfile: /opt/aptare/cfgtoollogs/sqlpatch/34786990/25032666
    /34786990_rollback_SCDBCNTR_SCDB_2023Apr28_16_23_29.log (no errors)
    Patch 35042068 apply (pdb SCDB): SUCCESS
      logfile: /opt/aptare/cfgtoollogs/sqlpatch/35042068/25183678
    /35042068_apply_SCDBCNTR_SCDB_2023Apr28_16_23_29.log (no errors)
    Patch 35050341 apply (pdb SCDB): SUCCESS
      logfile: /opt/aptare/cfgtoollogs/sqlpatch/35050341/25148755
    /35050341_apply_SCDBCNTR_SCDB_2023Apr28_16_23_29.log 
    (no errors)
    SQL Patching tool complete on Fri Apr 28 16:24:17 2023
  25. Check the log file in /opt/aptare/cfgtoollogs/sqlpatch/ for errors.

    The log file name includes the current timestamp:

    Example: /opt/aptare/cfgtoollogs/sqlpatch/sqlpatch_

    3378_2023_04_28_16_21_52/sqlpatch_invocation.log