ORA-01034 and ORA-27101 on WIndows machines

Subtitle: Overthinking the problem

Every site on the net which references these two errors:

ERROR:

ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist

seems to suggest that they are symptoms of either the ORACLE_SID not being set correctly or the ORACLE_HOME not being set correctly. Beyond that, they recommend checking the alert log to see if, possibly, there is some more serious problem with the database.I recently encountered these errors on a database whose windows service had started successfully. On a server with the ORACLE_SID and ORACLE_HOME set correctly; with an alert log which had no errors.

I have a simple solution to these two errors which does not involve any of these recommended approaches.

Check to ensure the database is started ;-$ FML

CI Setup part 2

BerliOS uses an old version of subversion (1.2) which may explain my inability to set it up with TortoiseSVN. In any case, I found a much faster, more up to date, and richer host for my Subversion server at BeanStalkApp.com. Setup was a breeze, soup to nuts in about 15 minutes and there were no problems integrating with TortoiseSVN. In fact, they offer instructions on integrating with 9 other products (including Twitter).
Next: Building my CIFactory script...

Continuous Integration

I decided to implement a Continuous Integration project. I downloaded a copy of CI Factory and went looking for a free subversion server.
Berlios.de has a good plan so I signed up and started to configure my environment. I also downloaded TortiseSVN with the hope of integrating Windows Explorer with Subversion.

Here is where the trouble began...

BerliOS uses ssh so I decided to use Putty for this. I went into TortiseSVN settings and pointed it at Putty.exe. This resulted in "Invalid Port Number" errors popping up one after the other in a stream of modal windows. Fortunately, I resolved that error by just removing the TortiseSVN ssh client setting and leaving it blank.

Now I get the username and password login, but it finds no repository. I'm going to track down that error as well - dammit!