SDBTech-KSS-SHM in /tmp causes UNKNOWN state when deleted

Question

MaxDB puts a file in the /tmp directory on HPUX:
-rw-rw----   1 sdb        sdba           168 Apr 18 07:12 SDBTech-KSS-SHM-<SID>
By it's nature, the /tmp file system is routinely cleaned and files are deleted at random by our Unix Admin Team.  If this file is deleted, the DBM GUI will show an UNKNOWN state.  That means this file needs to be protected but why would you put a protected file in a /tmp file system.
Are there options to this?  How are others avoiding their Production liveCache going into an UNKNOWN state?

Answer 1

Hello,
1. The /etc/opt/sdb is file of the database register.
    In /usr/spool/sql/ini is the location of the database register file too.
    The database register files will be written to "config" directory as of database 7.5 installation.
2. "SDBTech-KSS-SHM-<SID>' files - located in /tmp on HP server.
      The liveCache kernel creates a "mapping object" during startup, which is addressed via a regular file "/tmp/SDBTech-KSS-SHM-<SID>".
The shared memory KSS (Kernel Shared Segment) is owned by sdb/sdba with permissions::
-rw-rw       1 sdb        sdba
The file /tmp/SDBTech-KSS-SHM-<SID> could be removed by "root" during running a custom script to delete files in /tmp.
The liveCache <SID>  then need to be restarted for the missing file to be created properly.
3. You could modify the script to exclude deletion of the files with name started with string 'SDBTech-KSS-SHM' in /tmp directory, for example.
May be you have a master file exemption list used by your cleanup script, and you could add SDBTech-KSS-SHM* to the list so that none of your liveCache systems will have this file deleted. 
What is your SAP message number?
Thank you and best regards, Natalia Khlopina