Client home /usr/lib/oracle/client
Start execution of command /opt/cm/v12/test/1_hotfix_test/24.84913_CLOUD_142988_install_2_install.sh
Client home /usr/lib/oracle/client
Installation started at: 2024-07-10 22:19:04

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.84913, has been installed 5 times on the application server while it is installed 1 times on the database!

- File: UIG/SQL/JSR_2484913_8.sql:
__________________________________

	Updating: /opt/cm/v12/test/UIG/SQL/JSR_2484913_8.sql
	  - This is a new file, no information available on disk
	  - size (new file): 2476 bytes
	  - last modified (new file): 2024-06-24 12:40:02.0
Entryname Update:JSR_JBPB_U10.vw@UIG/SQL

- File: UIG/SQL/JSR_JBPB_U10.vw:
________________________________

	The new copy of the file "/opt/cm/v12/test/UIG/SQL/JSR_JBPB_U10.vw", shipped with the package, is different from the current copy on disk, and the file on disk has a newer timestamp!

	Updating: /opt/cm/v12/test/UIG/SQL/JSR_JBPB_U10.vw
	  - size (on disk): 217916 bytes
	  - last modified (on disk): 2024-07-02 12:55:20.0
	  -project (on disk): 
	  - version (on disk): 
	  - size (new file): 218064 bytes
	  - last modified (new file): 2024-06-21 16:25:08.0
Warning: The file was not modified.

deployment dir /opt/cm/ias/j2ee/test/deployment/deploy
Case 4



Issue 24.84913 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
===============================