Both of those options are server options, not dbsvc options. The dbsvc utility works as follows:

dbsvc[dbsvcswitches]-w<name>[serverexe][serverswitches]

The [server exe] part is not necessary on Unix. Any switch that appears before the -w is a dbsvc switch, meaning that it alters dbsvc's behaviour. Any switch that appears after the -w is a server switch, and dbsvc tells the service to use it. dbsvc itself doesn't know about server switches, which is why -oe is not documented as part of dbsvc.

The confusing part is that on Windows, -o is both a dbsvc switch and a server switch. If the -o switch appears before the -w, dbsvc uses it itself and writes its output there. If it appears after the -w, dbsvc passes it along to the service it creates. The -o switch is not supported by dbsvc on Linux.

You are trying to use the -o and -oe server switches, so they need to appear after the -w. Sorry my answer was so terse before. I hope this clarifies things.

Yes, I understand. I'm describing how dbsvc works because your original question seemed to be asking why -oe was not documented for dbsvc. I'm explaining that it's not a dbsvc switch at all. The documentation is correct.

Well, according to the docs on dbsvc for Windows, -o is also a dbsvc modifier option and gives the possibiliy to log the dbsvc execution itself, so its meaning depends on its position - cf. this sample:

Well, as Graeme and I try to explain: The server options are documented for the according server command (dbsrv12 etc.) and do not apply to dbsvc itself - and therefore don't appear in dbsvc's documention.