Client home /usr/lib/oracle/client
Start execution of command /opt/cm/v12/test/1_hotfix_test/24.83499_CLOUD_128596_install_1_install.sh
Client home /usr/lib/oracle/client
You specified version v12
Installation started at: 2024-07-09 22:19:48

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

Entryname Update:pmchange.pb@sql

- File: sql/pmchange.pb:
________________________

	Updating: /opt/cm/v12/test/sql/pmchange.pb
	  - size (on disk): 1411564 bytes
	  - last modified (on disk): 2024-01-19 14:53:24.0
	  -project (on disk): ERPV12-019-2_V12
	  - version (on disk): 172459
	  - size (new file): 1442085 bytes
	  - last modified (new file): 2024-05-09 11:32:02.0
	  -project (new file): C_GEN_V12
	  - version (new file): 1.1

- File: sql/2483499_3.sql:
__________________________

	The new copy of the file "/opt/cm/v12/test/sql/2483499_3.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/2483499_3.sql
	  - size (on disk): 7515 bytes
	  - last modified (on disk): 2024-05-09 11:33:04.0
	  - size (new file): 7515 bytes
	  - last modified (new file): 2024-05-09 11:33:04.0
Warning: The file was not modified.




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




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