There’s a command called: ORADEBUG SETORAPNAME in 11g.
It allows you to attach to a named background process as shown below, so you don’t need to figure out what’s the PID or SPID of the target process.
SQL> oradebug setorapname dbw0 Oracle pid: 9, Unix process pid: 5506, image: oracle@linux03 (DBW0) SQL> SQL> oradebug setorapname pmon Oracle pid: 2, Unix process pid: 5490, image: oracle@linux03 (PMON) SQL>
Even though you probably don’t want to mess around with background processes in production DBs, in demos and just Oracle research it can help you save couple of seconds every now and then.
NB! I am running one more Advanced Oracle Troubleshooting training in 2018! You can attend the live online training and can download personal video recordings too. The Part 1 starts on 29th January 2018 - sign up here!