Client home /usr/lib/oracle/client Start execution of command /opt/cm/v12/test/1_hotfix_test/24.85342_CLOUD_301374_install_2_install.sh Client home /usr/lib/oracle/client Installation started at: 2024-06-21 22:17:41 The following directories are used: CMiC Home: "/opt/cm", as specified in /home/oracle/.cms/cms.conf. Oracle Home: "D:/as10g2/midtier", default value. JSP Oracle Home: "/u01/app/oracle/midtierjsp", as specified in /home/oracle/.cms/cms.conf. Mobile Oracle Home: "/u01/app/oracle/midtiermobile", as specified in /home/oracle/.cms/cms.conf. Oracle Client Home: "/usr/lib/oracle/client", as specified in /home/oracle/.cms/cms.conf. /usr/lib/oracle/client/jdbc/lib/ojdbc7.jar /usr/lib/oracle/client/jdbc/lib/ojdbc6.jar /usr/lib/oracle/client/jdbc/lib/ojdbc8.jar Connection string: jdbc:oracle:oci:da/********@test Warning: Issue 24.85342, has been installed 11 times on the application server while it is installed 3 times on the database! - File: UIG/SQL/JSR_2485342_7.sql: __________________________________ The new copy of the file "/opt/cm/v12/test/UIG/SQL/JSR_2485342_7.sql", shipped with the package, is different from the current copy on disk, but the timestamps on both files are the same! Updating: /opt/cm/v12/test/UIG/SQL/JSR_2485342_7.sql - size (on disk): 2367 bytes - last modified (on disk): 2024-06-07 18:48:12.0 - size (new file): 2427 bytes - last modified (new file): 2024-06-07 18:48:12.0 Warning: The file was not modified. Entryname Update:JSR_PYSTB07U_3P.vw@UIG/SQL - File: UIG/SQL/JSR_PYSTB07U_3P.vw: ___________________________________ Updating: /opt/cm/v12/test/UIG/SQL/JSR_PYSTB07U_3P.vw - size (on disk): 8512 bytes - last modified (on disk): 2024-06-03 11:55:18.0 -project (on disk): - version (on disk): - size (new file): 7881 bytes - last modified (new file): 2024-06-07 15:52:00.0 deployment dir /opt/cm/ias/j2ee/test/deployment/deploy Case 4 Issue 24.85342 was successfully installed, but with warnings. As specified with --no-deploy option, JSPs did not get deployed. Deploy JSPs manually As specified with --skip-database-update option, the database was not updated. Update the database manually by running the appropriate sql script. Installation Log Review: ======================== ---------SUMMARY--------- Critical Errors: 0 Warning Errors: 0 Informative Errors: 0 ---------CRITICAL ERRORS--------- ---------WARNINGS--------- ---------INFORMATIONAL ISSUES--------- =============================== End of Installation Log Review ===============================