Category: SQL Error Messages

0

Introducing Parameter Wednesday – DBM CFG: NUMDB

This is a new blog post format I’m introducing. I’m declaring Wednesday Parameter Day. That means each Wednesday, I’ll pick a parameter and cover it in excruciating detail. Some of the details will come straight out of the info center, but I’ll add my own experiences and insight geared towards e-commerce databases and throw in specifics for WebSphere Commerce from...

1

How to restore a 64-bit database into a 32-bit instance using a compressed backup

This one seems to baffle some, though like redirected restores, it’s something that is only tough the first few times. If you attempt to restore a 64-bit database on a 32-bit instance using a compressed backup image, you get this scary error message: SQL2570N A database cannot be restored on a platform that does not match the platform on which...

7

Locks – Timeout vs. Deadlock

So questions in this area most often come from DBAs from other RDBMS’s or from developers. I’ll probably write other posts on locks, but here are the basics on deadlocks vs. timeouts. Why we get them confused at all Ah the wisdom that went into grouping these under a single error code with different return/reason codes. For whatever reason, both...

0

SQL0569 on Feature Pack – or any other time, really

Ok, so this is an issue I ran into recently. The Commerce guys were trying to install a Feature Pack, and got this: SQL0569N  Authorization ID “<authorization-name>” does not uniquely identify a user, a group or a role in the system. where the <authorization-name> was the id that Commerce uses to connect to the database. They thought they had an...

2

What to do when DB2 won’t work

This probably falls more in the DB2 newbie category, but I suspect I may have some readers who are DB2 newbies or at least not veterans. Several years ago (ok, probably more than 5), DB2 seemed to be considering a “Problem Determination Mastery” certification. I jumped on board and went through a series of free tutorials from IBM (which are still...

4

Stagingprop – SQL0803 – a rarer cause

I went through the most common cause of SQL0803 back in a previous post. There’s a rarer cause that can look very similar, and I thought I’d detail it. What this problem looks like: The following appears in the stagingprop log. The location and name of the stagingprop log can vary, but is most frequently on the application server where the stagingprop is run...