Client home /usr/lib/oracle/client
Start execution of command /opt/cm/v12/test/1_hotfix_test/24.85129_CLOUD_117181_install_1_install.sh
Client home /usr/lib/oracle/client
You specified version v12
Installation started at: 2024-07-09 03:18:10

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


Entryname Update:flpm1900.vw@sql

- File: sql/flpm1900.vw:
________________________

	The new copy of the file "/opt/cm/v12/test/sql/flpm1900.vw", shipped with the package, is the same as the current copy on disk, and the project with revision on both files are the same!

	Updating: /opt/cm/v12/test/sql/flpm1900.vw
	  - size (on disk): 19953 bytes
	  - last modified (on disk): 2024-07-05 13:54:24.0
	  -project (on disk): V12
	  - version (on disk): 185128
	  - size (new file): 19953 bytes
	  - last modified (new file): 2024-07-05 13:54:24.0
	  -project (new file): V12
	  - version (new file): 185128
Warning: The file was not modified.

- File: sql/2485129_1.sql:
__________________________

	The new copy of the file "/opt/cm/v12/test/sql/2485129_1.sql", shipped with the package, is the same as the current copy on disk, and the timestamps on both files are the same!

	Updating: /opt/cm/v12/test/sql/2485129_1.sql
	  - size (on disk): 8062 bytes
	  - last modified (on disk): 2024-07-05 13:51:20.0
	  - size (new file): 8062 bytes
	  - last modified (new file): 2024-07-05 13:51:20.0
Warning: The file was not modified.








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