So, what type of machine is "mercury"?
I've never seen a theme-based naming scheme that didn't eventually run into ambiguities like this.
It's not hard to have DNS CNAME and TXT records for machines, so that you can have both a naming theme for certain classes of servers, as well as descriptive names that indicate function, location, etc.
The way I handle the problem is pretty simple. Functionality gets a subnet 'name' under the root, and there are TXT records and aliases within that to handle description. So, if you have a datacenter in Sacramento, your DB and web machines would be named and alised:
johnny.sac.mycorp.com => db1.sac.mycorp.com TXT Rack 1, Slot 1-4
devi.sac.mycorp.com => db2.sac.mycorp.com TXT Rack 1, Slot 5-8
spooky.sac.mycorp.com => db3.sac.mycorp.com TXT Rack 1, Slot 9-12
tenna.sac.mycorp.com => db4.sac.mycorp.com TXT Rack 1, Slot 13-16
zim.sac.mycorp.com => web1.sac.mycorp.com TXT Rack 2, Slot 1
gir.sac.mycorp.com => web2.sac.mycorp.com TXT Rack 2, Slot 2
For ambiguous names (like 'mercury' existing in both { planets } and { elements }), only one copy of that name can exist on the network. The people who work with that machine will know it's theirs, and for everybody else, there's CNAME and TXT records for when they're not sure.
The confusion this causes for new hires and non-natives is real, albeit somewhat comical.
edit: ServerXX is no better-the names should give a clue to what function they perform (i.e. IRV-FNP01 = located in irvine, file and print server, 01 [oldest server])
The big win, though, for a more clinical naming is that shared context/training can be easier, and in a larger org the standardization of course makes things a lot easier to deal with. But of course, standardization can be done with the more whimsical names. And a lot of the time the naming scheme that is drawn up by committee takes just as long to learn as the more fun ones (mostly because they need to be abbreviated a bunch).
I suppose the one thing you can say for formal naming systems that is fairly inarguable is that once you understand the rules, you can look at an unfamiliar machine name and know instantly what it does. For machines named after fictional characters that's only true if you read/watch the same books/shows as the people doing the naming.
I have nothing against naming things in such a manner (my computers at home are cartoon characters), but the problem is that it doesn't scale. The company I work for is under 10 years old, and while a bit too old to still be called a startup, we already have more print servers than there are planets, let alone DB, dev, QA, and web servers. The last couple start-ups I had also had hundreds of boxes, and I'd go insane if "db-35" was actually named "WASP-18b" and I had to remember a list of 50-ish planets.
If you had a Pluto before the IAU changed its classification from planet to "ball of rock" you have a nice excuse to use whatever spherical lumps of rock you feel like.
It may not solve your problem forever, but, then, you can expand the naming to "potato-shaped lumps of stuff". That should give you some mileage.
I personally have very nearly experienced a disaster because the official naming convention had only one character difference between production and UAT...
Anyway, you've missed my point a bit. It doesn't matter much in the grand scheme of things what the boxes are called. It DOES matter than your company is employing people to impose pointless, trivial changes and policies on people with real work to do.