Yesterday I got the strangest feeling. I scrawled the internet and then the name nCube pupped up in my mind. “In the old days” this was really a machine on which I wanted to have the privileges to work on (Oracle database wise). In those days I had the luck to work on a Oracle Parallel Server, Oracle version 7.x – I forgot the specs, implementation for dutch banking cooperation.
The machine we used was a 12 node (RS6000) IBM SP2 machine. I got the chance to work for 1 1/2 months with it, I guess this was in 1995, until they decided that the concepts of working on such a machine were to complex, so they decommissioned the hardware. The 12 RS6000 machines were dismantled and dedicated to different project teams working on the same paying chip card project.
The SP series are probably best remembered by “Deep Blue“, the chess program that challenged and defeated Garry Kasparov in 1997.
A long long time ago (during my Oracle 7 days), I once needed to update base table SYS.PROPS$. This action was needed to change the database NLS characterset of US7ASCII to a characterset that would support GERMAN. Based on a metalink note, updating the SYS.PROPS$ base table, was the only way to achieve this (or completely rebuild the environment) in those Oracle 7 days.
This procedure was tricky. If you updated it with the wrong, an unsupported character set or with a typo in the string, the database would be corrupted and could not be started up again (so be warned if you want to fiddle around with the method)
Since those days, I always lookup NLS settings via a quick select on that table. The last time I did this, was a long time ago and to my surprise, while looking up settings, I noticed that this table does contain more data then only NLS parameters these days…
Output of a full (demo) clean database Oracle 11g installation gives:
Did it. At last I managed to install Oracle V188.8.131.52 on MSDOS 6.22 under VMware Server 1.04. You probably think I am nuts. As someone said on our way home from Miracle Open World: “I would spend my time learning Oracle 11g”. Maybe. The person who said it, by the way, is an Oracle trainer, so what would I expect…
I / we (Bert Jan Meinders, an old colleague of mine) did our first attempt almost 1, 1 1/2 years ago. Our first attempt was based on VMware GSX software after we succesfully installed Oracle 4.1 on MSDOS. This was the first time (and until now the last time) I saw a total crash of VMware software. Oracle V5 was shipped under DOS with a memory manager called SQLPME (SQL Protected Mode Executive) V1.2.1.
SQLPME was aggressive enough with its peeking and poking in memory that it crashed the VMware GSX environment at the time. Under VMware Server 1.04 it just hung itself up / nothing happened.
Click on the image to enlarge
After you have read the blog posts the websites of Sergio Leunissen, Eddie Awad or the “Ask Mr. Ed” website, you may wonder, if that was all you could do with those “magic” double quotes… Probably not, I know of at least one other neat “trick” you can do with it…
Ever tried the following?
SQL> CREATE USER "=:Marco:=" IDENTIFIED BY "Username is Invalid";
You won’t make life easy though, because now you will have to use the double quotes to login as follows:
SQL> CONNECT "=:Marco:="/"Username is Invalid"
And if you want to connect via an extra [ENTER], than you must not to forget also to type in your double quotes…
We had some nice KC-DBA (expertise meetings) meetings in 2005. One of them was about virtual machines (VMware basically). To show how you could use virtual machine technology to implement an environment which would be almost undoable nowadays to realize, a virtual machine environment was demonstrated with Oracle 4.1 installed based on DOS. Thanks to Carel Jan Engel (one the infamous OAKTable guys) – i was able to build a default Oracle 4.1 database environment with all the goodies like the UFI (the user friendly interface).
The old DOS disks where recovered from some boxes on my attic, so with some extra effort, the installation wasn’t so difficult (i still remembered how to do the ansi.sys, autoexec.bat and config.sys upper and lower memory stuff ) All in all it was good fun.
Strange enough you need(ed) the first oracle floppy in the floppy disk to start the database. I can not remember this from my Oracle 6 days.
Yesterday i was reading nice discussions on Asktom about the dual table. Afterwards somehow a “undocumented” Oracle feature popped into my mind again. Last time I used is at least in those days I worked with Oracle 7.0 /7.1. So I tried It out on Oracle database version 10.1.0.4 and it still works…
Maybe it is (still) usefull to someone. See hence my example: