Chacham's Journal: Verbiage: Some random debugging session

A team member from Chenai asked me why a script which EXECUTEd a PACKAGE i wrote wasn't working. First thing i did was run it myself via SQL*Plus, which is did splendidly, i might add. :) First thing accomplished, it's not a problem in QA, it's the script.

Logged onto the app server and sure enough received the same error. Copied the file and started to change things. Having seen this file before, i was able to skip all the variables and right to the code. The code looked okay..maybe it should be tested on the db server itself to mimic what that script was doing.

Logging on to the server reminded me that the password had changed. No idea what it was changed to, but it wasn't required anymore, so i didn't care. That was a problem here. Luckily, there are those variables.

The variable and variable handling take up probably most of the script. The variables themselves are loaded from files, which may include other files. Ultimately, usernames and passwords are in a script under ~/etc...easy enough.

Trying the first set, then realized that was the db login itself. I made sure the db user could indeed EXEC that PACKAGE via SQL*Plus, and it could. But that wasn't the server login. Looking again, there was a server login, which failed. I checked and double-checked. Something was wrong.

That was it, no more assumptions, just check which server it was connecting to straight. Sure enough, it was set to the server we were migrating to, but is not for general use yet. The TNS name pointed to it as well. Duh! Is your computer plugged in?

--

When writing this, i hit [ctrl]-[e] 2 or 3 times to go to the end of the line. Between my mac at home and just being on a Linux box, switching back to windows shortcuts takes a second. After switch back from Google, i found my window empty, luckily, i had Lazarus installed.