| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2589.1 | hazy memories | DUCATI::LASTOVICA | Is it possible to be totally partial? | Thu Jan 23 1997 16:01 | 3 |
| 2589.2 | | NOVA::R_ANDERSON | Oracle Corporation (603) 881-1935 | Fri Jan 24 1997 08:00 | 8 |
| This error is returned for a huge number of reasons, most representing a really
whacked out system (as Norm indicated) but also caused by things such as lock
remastering, etc.
This error is properly handled in the newer DBMS versions (probably v6.0 &
higher).
Rick
|
| 2589.3 | 'Whacked up'? | M5::BLITTIN | | Fri Jan 24 1997 09:33 | 5 |
|
I saw the help/mess and had the customer look at this, and suggested
he/she have the sysmgr look at it as well. I kinda came to the same
conclusion, but don't know enough about systemy stuff...what exactly
do you mean by 'whacked up'?
|
| 2589.4 | | HOTRDB::LASTOVICA | Is it possible to be totally partial? | Fri Jan 24 1997 09:56 | 4 |
| I'd have the customer get in touch with digital. In the past, I've
seen this error when there is something wrong with the SECURITY_SERVER
process or due to plain bad programming (that DBMS would never be
involved in :-)
|