Suddenly, the UVMS filesystem was full due to a huge .dat file that increased abnormally to several GB, like below:
<uvms>/data/data/uvmsdb/seg0/
-rw-r--r--. 1 username groupname 2.9G Nov 21 08:19 c1060.dat
The file could increase 1 GB each week for no clear reason.
No particular operation was done at the UVMS level.
While reading the file with a text editor, it seems that the file contained the content of the table UNI_UV_USERSETTINGS, but this table only contained 3 rows, so the size is completely abnormal.
Release : 6.9 and superior
Component: UVMS using the Internal Derby Database
Unknown, most likely a Derby database bug.
There are different procedures UVMS installed on Unix or Windows:
The reorganization procedure for the table UNI_UV_USERSETTINGS is the following:
. ./unienv.ksh
./unistopms
cp -R uvmsdb uvmsdb_<dateYYYYMMDD>
du -hs uvmsdb
./uniderby -q "call SYSCS_UTIL.SYSCS_COMPRESS_TABLE('SA','UNI_UV_USERSETTINGS', 0);"
du -hs uvmsdb
./unistartms
Test if UVMS is working correctly for some time. If this is the case the copy of the DB can be archived and removed from the filesystem to regain the space.
unienv.ksh
unistopms
rem echo READONLY ON; >> %SQLFILE%
uniderby -q "call SYSCS_UTIL.SYSCS_COMPRESS_TABLE('SA','UNI_UV_USERSETTINGS', 0);"
unistartms
Test if UVMS is working correctly for some time. If this is the case the copy of the DB can be archived and removed from the filesystem to regain the space.