The 0xdbaccee5 shmem will remain because it is for Texis monitor. Others may remain because they are owned by other users, e.g. Apache may use shmem as well. Were there any errors issued by the ipcs -m | ... command? Also, can you create a database now? If not, what is the error?
I tried this on 1 specific shmid and the status=dest:
-bash-4.1$ ipcrm -m 271253520
-bash-4.1$ ipcs -m
------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x00000000 0 rainmaker 666 202984 1 dest
0x00080045 32769 rainmaker 666 219056 3
0x0014025a 271187982 rainmaker 666 219056 2
0x00000000 271220751 rainmaker 666 219056 1 dest
0x00000000 271253520 rainmaker 666 219056 1 dest
0x00000000 271286289 rainmaker 666 219056 1 dest
0x00000000 271319058 rainmaker 666 219056 1 dest
0xdbaccee5 787711748 rainmaker 666 202984 3
-bash-4.1$ ipcs -m
------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x00000000 0 rainmaker 666 202984 1 dest
0x00080045 32769 rainmaker 666 219056 3
0x0014025a 271187982 rainmaker 666 219056 2
0x00000000 271220751 rainmaker 666 219056 1 dest
0x00000000 271253520 rainmaker 666 219056 1 dest
0x00000000 271286289 rainmaker 666 219056 1 dest
0x00000000 271319058 rainmaker 666 219056 1 dest
0xdbaccee5 787711748 rainmaker 666 202984 3
-bash-4.1$ lsof | grep 271319058
texis 7647 rainmaker DEL REG 0,4 271319058 /SYSV0014007d
There are times when I see monitor as the app result from lsof.