NetBackup IT Analytics Installation and Upgrade Guide for Linux
- Install the NetBackup IT Analytics Portal on a Linux server
- Installer-based deployment
- 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
Installing the Oracle patch
- 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 command:mv p35742413_190000_Linux-x86-64.zip /opt/aptare/oracle mv p35638318_190000_Linux-x86-64.zip /opt/aptare/oracle
- Navigate to
/opt/aptare/oracle
folder and unzip the file.cd /opt/aptare/oracle unzip p35742413_190000_Linux-x86-64.zip
The above command will create a 35742413 folder in
/opt/aptare/oracle
folder.unzip p35638318_190000_Linux-x86-64.zip
The above command will create a 35638318 folder in /opt/aptare/oracle folder.
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
- Set permission on patch folders 35742413 and 35638318
4. chown -R aptare:dba 35742413 chown -R aptare:dba 35638318
Note:
If you have already installed an Oracle patch previously, skip the following steps from 4 through 10.
- 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
- 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
- Check if
oraInventory
folder is available under/opt/
. If the folder is not available, thencd /opt/aptare/upgrade cp oraInventory.zip /opt/ unzip oraInventory
- Check permission on
/opt/oraInventory
folder if it is aptare:dba else change the permissioncd /opt/ chown -R aptare:dba oraInventory
- Execute su -aptare command.
- 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"
Note:
If the oracle home is already attached, Oracle Home already exists at this location. Select another location message is displayed. Ignore this message.
- 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
- Connect as user aptare, if continuing from step-3 by using the below command else proceed to next step.
su - aptare
- 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
- Check for any
OPatch
conflicts.This will check for conflicts for both the database RU patch and OJVM patches.
cd /opt/aptare/oracle/35742413 /opt/aptare/oracle/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -ph ./
- If no conflicts are detected, execute the following command to apply database RU patch from
/opt/aptare/oracle/35742413/35648110
folder.cd /opt/aptare/oracle/35742413/35648110 /opt/aptare/oracle/OPatch/opatch apply Verifying environment and performing prerequisite checks... OPatch continues with these patches: 35648110 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... Sub-set patch [33806152] has become inactive due to the application of a super-set patch [34133642]. Please refer to Doc ID 2161861.1 for any possible further required actions. Log file location: /opt/aptare/oracle/cfgtoollogs/opatch/opatch2022-07-20_20-44-05PM_1.log Backing up files... Applying interim patch '35648110' 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 35648110 successfully applied. Log file location: /opt/aptare/oracle/cfgtoollogs/opatch/opatch2023-11-06_18-23-46PM_1.log OPatch succeeded.
- Run the following commands to apply OJVM patch from /opt/aptare/oracle/35742413/35643107 folder.
Note:
Ignore any warnings related to rollback of patch 30565805. This message shows up when no prior Oracle security patches were applied.
cd /opt/aptare/oracle/35742413/35643107 /opt/aptare/oracle/OPatch/opatch apply Verifying environment and performing prerequisite checks... OPatch continues with these patches: 35643107 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 35354406 successfully applied. Patching component oracle.jdk, 1.8.0.201.0... Patch 35643107 successfully applied. Sub-set patch [31281355] has become inactive due to the application of a super-set patch [35643107]. Sub-set patch [30565805] has become inactive due to the application of a super-set patch [35643107]. Please refer to Doc ID 2161861.1 for any possible further required actions. Log file location: /opt/aptare/oracle/cfgtoollogs/opatch/opatch2023-11-06_18-29-12PM_1.log OPatch succeeded.
- Navigate to /opt/aptare/oracle/35638318 and check for any OPatch conflicts for the JDK bundle patch.
cd /opt/aptare/oracle/35638318 /opt/aptare/oracle/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -ph ./
- If no conflicts are detected, execute the following commands to apply JDK patch from /opt/aptare/oracle/35336174 folder.
cd /opt/aptare/oracle/35638318 /opt/aptare/oracle/OPatch/opatch apply Verifying environment and performing prerequisite checks... OPatch continues with these patches: 35638318 Do you want to proceed? [y|n] y Patching component oracle.jdk, 1.8.0.201.0... Patch 35638318 successfully applied. Log file location: /opt/aptare/oracle/cfgtoollogs/opatch/opatch2023-11-06_18-44-12PM_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."
- 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.
- Connect to SQL Plus using following command:
-bash-4.2$ sqlplus /nolog
SQL*Plus: Release 19.0.0.0.0 - Production on Mon Nov 6 18:55:33 2023
Version 19.21.0.0.0
Copyright (c) 1982, 2022, Oracle. All rights reserved.
- Connect as sysdba
SQL> connect / as sysdba
Connected to an idle instance.
- Start the database.
SQL> startup
ORACLE instance started.
:
:
Database mounted.
Database opened.
- Open all pluggable database.
SQL> alter pluggable database all open;
Pluggable database altered.
- Exit from SQL prompt.
SQL> quit
- Datapatch is run to complete the post-install SQL deployment for the patch being installed.
Execute the following command 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: 6 Validating logfiles...done Patch 35643107 apply (pdb CDB$ROOT): SUCCESS logfile: /opt/aptare/cfgtoollogs/sqlpatch/35643107/25405995/ 35643107_apply_SCDBCNTR_CDBROOT_2023Nov06_18_58_52.log (no errors) Patch 35648110 apply (pdb CDB$ROOT): SUCCESS logfile: /opt/aptare/cfgtoollogs/sqlpatch/35648110/25365038/ 35648110_apply_SCDBCNTR_CDBROOT_2023Nov06_18_58_52.log (no errors) Patch 35643107 apply (pdb PDB$SEED): SUCCESS logfile: /opt/aptare/cfgtoollogs/sqlpatch/35643107/25405995 /35643107_apply_SCDBCNTR_PDBSEED_2023Nov06_19_02_41.log (no errors) Patch 35648110 apply (pdb PDB$SEED): SUCCESS logfile: /opt/aptare/cfgtoollogs/sqlpatch/35648110/25365038 /35648110_apply_SCDBCNTR_PDBSEED_2023Nov06_19_02_41.log (no errors) Patch 35643107 apply (pdb SCDB): SUCCESS logfile: /opt/aptare/cfgtoollogs/sqlpatch/35643107/25405995/ 35643107_apply_SCDBCNTR_SCDB_2023Nov06_19_02_41.log (no errors) Patch 35648110 apply (pdb SCDB): SUCCESS logfile: /opt/aptare/cfgtoollogs/sqlpatch/35648110/25365038/ 35648110_apply_SCDBCNTR_SCDB_2023Nov06_19_02_41.log (no errors) Automatic recompilation incomplete; run utlrp.sql to revalidate. PDBs: PDB$SEED SQL Patching tool complete on Mon Nov 6 19:05:08 2023
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 Mon Nov 6 19:09:46 2023 Version 19.21.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.21.0.0.0 SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql Session altered. : : PL/SQL procedure successfully completed.
- Check the log files in
/opt/aptare/cfgtoollogs/sqlpatch/
for errors. The log file name includes the current timestamp:Example:
/opt/aptare/cfgtoollogs/sqlpatch/ sqlpatch_15535_2023_11_06_18_57_54/sqlpatch_invocation.log
- Start all services as root user.
/opt/aptare/bin/aptare start