 |
 |
Archives of the TeradataForum
Message Posted: Wed, 27 Apr 2005 @ 19:00:36 GMT
| Subj: | | Re: CLI error 220 |
| |
| From: | | Diehl, Robert |
Nazy,
It was probably a problem with the network. Depending on what connection utility and settings, the utility will reconnect the session after
the connection is dropped and processes the work. It then gives you a warning like you received. The problem is Teradata does not know why the
connection dropped. Right now the default message is the DBC Crashed. It really should say 'the connection was lost for an unknown reason
possible a dbc restart'. I believe NCR has a DR to change the message to be more generic.
Thanks,
Bob Diehl
Travelcoity.com
| |
