Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Sorry, I didn't mean to imply all of OEM was based on Oratcl, just the Tcl extension used to access the database. I was listed in one of the OEM manuals in the copyright statement, along with the RBOC where I worked when I created Oratcl. I don't recall the names of the people at Oracle who contacted me to tell me they were using Oratcl, perhaps 'Mario' or 'Eric' ??

The funny part was when I got an email from someone at Oracle, perhaps in legal, who wanted me to sign an "indemnify and hold harmless" statement for my code, code that I shared freely, received no compensation for, and had no control on how it was used by Oracle in their product -- Rrriiight. I replied "no thanks", and if Oracle wanted to use my software, they simply should comply with the BSD license that it shipped with, including the attribution clause.



"OEM" == "Oracle Enterprise Manager" -- duh. I was thinking the other meaning of OEM.

memory fades. I don't remember how I did that anymore. Maybe we folded Oratcl into the OEM agent???

As you'll read in that article, the agent didn't work all that well, at first, and it was a particularly hellish time to be a manager.


Thanks to a Saturday afternoon, the awesome Wayback machine, and already got my hike in. See pages 2 and 44: https://docs.oracle.com/pdf/A85251_01.pdf

There's also a 'ps' listing on page 50, with a user id 'aholser', if that rings any bells.

I haven't used Oracle since about 1998, and never Oracle's Enterprise Manager or whatever agent, so no idea how well it worked. I'll read your article.


122 pages, huh? tl;dr

by 2000, my colleague Dimitris Nakos had cleaned it up, probably. I don't know who 'aholser' might be.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: