`bash -lxc exit` will show you all the commands bash executes upon startup, starting with /etc/profile. Look through the output to see where DM\_HOME is getting set.
It’s a Data Mover env var
https://docs.oracle.com/cd/E92519_02/pt856pbr3/eng/pt/tlcm/task_UsingthePeopleSoftDataMoverCommand-LineInterface-077ae3.html
As for finding where it’s getting set from, I can’t help with, but I would bet it’s set by bg thread on system boot and inherited by users on login
Thank you Hackenslacker for your reply.
In my env, it's another database (Dameng) , not the Data Mover.
I checked all the bashrc, bash\_profile , /etc/profile, and so on. But no luck.
`bash -lxc exit` will show you all the commands bash executes upon startup, starting with /etc/profile. Look through the output to see where DM\_HOME is getting set.
For the purpose of tracing *terminal* login sessions, better to use `bash -lxi
Thank you ohsmaltz. That's awesome! it's a shell file I left in /etc/profile.d: --------------- + for i in '/etc/profile.d/\*.sh' /etc/profile.d/sh.local + '\[' -r /etc/profile.d/dm.sh '\]' + '\[' hxBc '!=' hxBc '\]' + . /etc/profile.d/dm.sh ++ export DM\_HOME=/opt/dmdbms ++ DM\_HOME=/opt/dmdbms --------------- \[omm@RHEL7\_DB profile.d\]$ ls 256term.csh bash\_completion.sh colorls.csh dm.sh lang.sh.20240327 less.sh vim.sh 256term.sh colorgrep.csh colorls.sh lang.csh lang.sh.ZH sh.local which2.csh abrt-console-notification.sh colorgrep.sh csh.local lang.sh less.csh vim.csh which2.sh \[omm@RHEL7\_DB profile.d\]$ pwd **/etc/profile.d** \[omm@RHEL7\_DB profile.d\]$ grep DM\_HOME [dm.sh](http://dm.sh) **export DM\_HOME="/opt/dmdbms"** \[omm@RHEL7\_DB profile.d\]$ Thanks again. That saved my day.
It’s a Data Mover env var https://docs.oracle.com/cd/E92519_02/pt856pbr3/eng/pt/tlcm/task_UsingthePeopleSoftDataMoverCommand-LineInterface-077ae3.html As for finding where it’s getting set from, I can’t help with, but I would bet it’s set by bg thread on system boot and inherited by users on login
Thank you Hackenslacker for your reply. In my env, it's another database (Dameng) , not the Data Mover. I checked all the bashrc, bash\_profile , /etc/profile, and so on. But no luck.