2. Stop CUBRID manager process using the following command:
> cubrid manager stop @ cubrid manager server stop ++ cubrid manager server stop: success
3. Copy CUBRID\bin\cub_cmserver.exe and CUBRID\bin\cub_js.exe in patch to %CUBRID%\bin\, replacing the original cub_cmserver.exe and cub_js.exe file.
In Linux, Copy CUBRID/bin/cub_cmserver and CUBRID/bin/cub_js in patch to $CUBRID/bin/, replacing the original cub_cmserver and cub_js file.
4. Copy CUBRID\share\webmanager in patch to %CUBRID%\share\, replacing the original webmanager directory.
In Linux, Copy CUBRID/share/webmanager in patch to $CUBRID/share/, replacing the original webmanager directory.
5. Start CUBRID manager process using the following command:
> cubrid manager start @ cubrid manager server start ++ cubrid manager server start: success
Please close web manager in your browser before patching, otherwise maybe some unpredictable errors will happen.
There would not be happened this issue if you have not used CUBRID Web Manager by support_web_manager=NO option in cm.conf file.
If user used exportdb to exprot database for many times, the exported files would store in $CUBRID/share/webmanager/files forever until free disk being 0. CMS should give a validating machanism to check free disk is enough or not. This issue should be fixed in next cms version.