rasputin.dnsalias.com

Help Is On The Way... Not!

Posted on January 26, 2006 4:08 PM

Just recently we did a restore of a DB2 database from one AIX system to another. The restore wasn't due to any disaster. We're setting up a new development system and we wanted to use this as an opportunity to test our recovery strategy. Lots of good stuff is going on. I learned how to get the new system to pull the backup straight out of TSM using the -fromnode and -fromowner options. This means I don't have to restore the backup file to the filesystem, then ftp it over to the new system, then restore the database from the file. One of the problems I did encounter was when I tried to rollforward the database using the log files that are also in TSM. For some reason, even though DB2 knows how to get the backup, it is having some problem retrieving the log files. My suspicion is that there is something else that needs to be done in the TSM configuration or that something with the configuration is not correct. After trying twice with no luck, I decided to give up for now ™, and rollforward with log files retrieved manually. With the database up and working, I alerted the development team that it was ready for them to do some damage.

The lead developer came back quickly, saying that he got an error message from DB2 when he tried to connect:

Code:

SQL0969N There is no message text corresponding to SQL error "-2079391743" in
the message file on this workstation. The error was returned from module
"SQLEUCCM" with original tokens "".


That's a beauty, isn't it?

Anyone who has worked with DB2 for a while is probably used to error messages that, to say the least, are no help at all. The really aggravating ones are the messages that are simply telling you that DB2 doesn't really know what the problem is, like this one is doing in a way. The great thing about this error message is that it points to this "SQLEUCCM" module, but if you do a quick search on Google, you'll find that there aren't too many websites that contain that particular string of characters. The IBM DB2 Help Center website returns no results if you search for it there. I find it perplexing that DB2 will spit out an error message that you can find no reference to on the support website. Well, now there's one more website that does mention it.

I did find a useful link to the International DB2 Users Group website, which points to a problem with file permissions. In my own defense, I had assumed that the problem had to be permission related, because I could connect with no problem to the database using my own account and DB2 credentials, but if I used another user's account (one that was not SYSADM) I had the same problem, even when I tried to use my own DB2 credentials. This seemed to suggest that the problem was not connected to the AUTHID but to the actual account using the AUTHID. After some detective work, I found that only the group and the owner of the root database directory had read and execute on the directory. So if you're reading this because you have this message staring you in the face, check the permissions of the directories where your database is located, and any directories that will hold the tablespaces, if you put them in a different location.

Add/View Comments (2)

Tags: , , , , ,