[peacefuleye]

CAUSE DETERMINATION
===================
The issue is caused by the following setup: The gc3env.sh (OTM Environment setting script) was not run in the specified format
.
The command should be run as . ./gc3env.sh from the Application server directory, <otm_install dir>/install.

CAUSE JUSTIFICATION
===================
The setup causes the issue because the OTM environment was not set up correctly before the dbpatch_55.sql was run.
The dbpatch_55.sql also invokes the update_content process that uploads PUBLIC data into OTM. Part of this PUBLIC data are the refer
ences to various OTM screens.
Since the OTM environment was not set correctly, the Update_content failed to run and hence no screen information was loaded into the database.
Hence, when the user tried to access the Order screens, they got a HTTP 404 error.

PROPOSED SOLUTION(S)
====================
Change the setup for running the gc3env.sh file by running it as . ./gc3env.sh

PROPOSED SOLUTION JUSTIFICATION(S)
==================================
The setup will do the following:
1.The set up change will enable the successful uploading of PUBLIC data when the update_content script is run as part of the dbpatch_55.sql

SOLUTION / ACTION PLAN
======================
-- To implement the solution, please execute the following steps::
1. Log on to the Application server
2. Navigate to <Otm_install_directory>/install

3. Run the following command as it is . ./gc3env.sh (please note that the script should be run as dot space dot slash gc3env.sh)
Then change directory into, <otm_install_directory>/glog/oracle/script8.
SQLPLUS into the database with the following command,
sqlplus glogowner/glogowner@<OTM Database Connect String>
Run the SQL, @dbpatch_55.sql
Make sure that the DB Patch runs successfully. Verify the Update_content log shows that CSV files are uploaded succ
essfully.
Re-start the web and application servers.

4. Retest the issue.