OpsCenter DataBase temporary files out of /tmp

[LuisLiendo]

OpsCenter 7.1.0.2 running on Linux SUSE creates some temporary files under /tmp/.SQLAnywhere which look like

./opscenter_plsys
./opscenter_plsys/shmem
./opscenter_plsys/shmem/shm_00000001
./opscenter_plsys/shmem/shm_00000002
./opscenter_plsys/fifos
./opscenter_plsys/tmp
./opscenter_plsys/tmp/tmp_000000
./opscenter_plsys/lock
./opscenter_plsys/pid
./opscenter_plsys/p.31649
./opscenter_plsys/lrm_socket
./__SQLAny__
 

Any suggestions as for how to relocate this directory (/tmp/..SQLAnywhere) out of /tmp filesystem and if it is advisable to do so.

This directory has been growing up filling up /tmp filesystem

[thesanman]

I had a similar issue; see http://www.symantec.com/business/support/index?page=content&id=TECH162418 which gives you an idea on how to move the SQL tmp area to a different location.  There are other examples out there.

If not clear add -dt /a-directory/somewhere-else/ to the end of the command options.

e.g. -dt /d1/SQLAnywhere-tmp/

I made the folder owned by root but chmod 777

Worked for me.

[LuisLiendo · Accepted solution]

Thank you for sharing the technote information.  We were running into same situation after wich OpsCenter will generate a core dump and crash accordingly.

We implemented the change using the sqlanywhere parameters described on

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.sqlanywhere.11.0.1/dbadmin_en11/da-dbserver.html

The parameter that did the trick for us was to set the Variable SATMP to the new location.

The variable was set into the OpsCenter start script located under /etc/init.d

i.e SATMP=/var/opscenter/tmp ; export SATMP

Did notice the same variable has to be set in the environment of any account connecting to OpsCenter Data Base directly. Just update the environment start file of the SHELL being used to connect.

i.e .bashrc

Working well.