| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 245.1 | Enable BLR Logging | BROKE::PROTEAU | Jean-Claude Proteau | Mon Oct 14 1996 17:26 | 12 |
|
Taken at face value, the message says that Rdb/Dispatch (%RDB) ran into
some sort of problem while making a call to the operating system. What
is strange, of course, id the success message from the system. I've
not seen this before.
Assuming the problem is repeatable, have the customer enable BLR
logging in Rdb ($ DEFINE RDMS$DEBUG_FLAGS B) within the LOGIN.COM that
runs the copy process that executes the transfer. At least this will
show us what query was being performed prior to receiving this message.
Then, submit this information to the Rdb folks as a formal problem
report. It certainly looks like unusual behavior.
|
| 245.2 | | HOTRDB::PMEAD | Paul, [email protected], 719-577-8032 | Tue Oct 15 1996 09:46 | 6 |
| And before submitting anything to Rdb have them upgrade to the latest
Rdb ECO. I seem to vaguely remember some SORT error reporting that
would sometimes result in this kind of symptom. But when I went
looking for something on it I couldn't find anything (maybe I am just
dreaming). In any case, make sure they are running the latest Rdb
before sending anything to engineering.
|
| 245.3 | More information... | ORAREP::VAXRIO::63198::csantos | | Thu Oct 17 1996 15:02 | 20 |
|
Sorry for the delay, but we are having some trouble with
the log... I do not know why, but the log is being created,
but it is empty.
Another thing I found out is that the remote database actually
is DBI-gateway for DB2 database, so actually they are accessing
a remote IBM database. I just started wondering if that error
could not be from SNA... The reason I started thinking about
it is that I've seen other transfer like that failing with
network error and the only message we get form RDB is the
IO error, all the other messages come from SNA...
Am I dreaming or that makes any sense???
Thanks for helping
Claudia
|