"DBS CRASHED OR SESSIONS RESET." error when using bteq on Solaris

Database

"DBS CRASHED OR SESSIONS RESET." error when using bteq on Solaris

Dear all,
I met a error when connecting Teradata server form a Solaris Teradata Client.
This only happen on Solaris, so I think the Teradata Server is working well.
I don't know what cause the problem and how to resolve it.
Waiting for advice.

========Error message on Solaris==========
=> bteq

Teradata BTEQ 08.02.02.00 for UNIX5.
Copyright 1984-2004, NCR Corporation. ALL RIGHTS RESERVED.
Enter your logon or BTEQ command:
logon dsserver/user1;

logon dsserver/user1
Password:

*** Warning: DBS CRASHED OR SESSIONS RESET. RECOVERY IN PROGRESS>

=========Success log on other platform========

=> bteq

Teradata BTEQ 08.02.03.00 for UNIX5.
Copyright 1984-2005, NCR Corporation. ALL RIGHTS RESERVED.
Enter your logon or BTEQ command:
logon dsserver/user1;

logon dsserver/user1
Password:

*** Logon successfully completed.
*** Transaction Semantics are BTET.
*** Character Set Name is 'ASCII'.

*** Total elapsed time was 3 seconds.

BTEQ -- Enter your DBC/SQL request or BTEQ command:

=========Sytem information:=======
SunOS 5.10 Generic_125100-10 sun4u sparc SUNW,Sun-Fire-V440

=========package information after install===========
-bash-3.00# pkginfo |grep Tera
system TeraGSS Teradata GSS client package
system TeraGSS32 Teradata GSS client package
application bteq Teradata BTEQ Application
application cliv2 Teradata CLIV2 Package
application cliv2so Teradata CLIV2so Package
library piom Teradata Data Connector Access Module API
library tdicu Shared common components for Internationalization for Teradata
application tdodbc Teradata ODBC Driver

==========Install log============

-bash-3.00# cat /var/ncr/logs/pkgadd.log
Tue Oct 14 16:47:37 CST 2008

Installation of was successful.

Installation of was successful.
Copyright (C) NCR Corporation, 2004
All Rights Reserved.

Adding TD_ICU_DATA environment variable to /etc/profile file.
Adding TD_ICU_DATA environment variable to /etc/.login file.

Installation of was successful.
Copyright (C) 2000-2003. NCR Corporation
All Rights Reserved.

Installation of was successful.
Copyright (C) NCR Corporation, 2003-2004
All Rights Reserved
Adding CLI COPLIB environment variable to /etc/profile file.
Adding CLI COPERR environment variable to /etc/profile file.

Installation of was successful.
WARNING: setting mode of to default mode (755)
Copyright (C) NCR Corporation, 2003-2004
All Rights Reserved
Keeping existing /usr/lib/clispb.dat file

Installation of was successful.
Copyright (C) NCR Corporation, 1984-2004
All Rights Reserved

Installation of was successful.
Copyright 1994-2004 by NCR Corporation
All Rights Reserved.
NCR CONFIDENTIAL and TRADE SECRET

Portions of this software are copyrighted
by DataDirect Technologies 1991-2004

Installation of was successful.

7 REPLIES
Junior Contributor

Re: "DBS CRASHED OR SESSIONS RESET." error when using bteq on Solaris

Based on DNS/hosts "dsserver" might resolve to a different (invalid) ip-address.
Try to "ping dsservercop1" to check if it's the correct ip-address.

Dieter

Re: "DBS CRASHED OR SESSIONS RESET." error when using bteq on Solaris

Thanks.

I have add a record in /etc/hosts and can ping dsservercop1, but problem still exist.

*.*.*.*(ip address) dsserver dsserverCOP1 #Teradata Server

=> ping dsservercop1

dsservercop1 is alive
Enthusiast

Re: "DBS CRASHED OR SESSIONS RESET." error when using bteq on Solaris

can you try login using ip address from bteq ?

.logon v.x.y.z/id;

Also compare the ip address you get via ping / nslookup to the actual IP address ( are they same)

Re: "DBS CRASHED OR SESSIONS RESET." error when using bteq on Solaris

Hi, thanks for reply. I tried your advice.
=================
=> ping -s dsserverCOP1
PING dsserverCOP1: 56 data bytes
64 bytes from **.**.**.com(1.23.45.67): icmp_seq=0. time=269. ms
64 bytes from **.**.**.com(1.23.45.67): icmp_seq=1. time=264. ms

the IP address(1.23.45.67 for example) is correct but I got this error when try to conncet using the ip address
============
=> bteq

Teradata BTEQ 08.02.02.00 for UNIX5.
Copyright 1984-2004, NCR Corporation. ALL RIGHTS RESERVED.
Enter your logon or BTEQ command:
.logon 1.23.45.67/user1

.logon 1.23.45.67/user1
Password:

*** CLI error: CLI2: BADLOGON(303): Invalid logon string.
*** Return code from CLI is: 303
*** Error: Logon failed!

*** Total elapsed time was 4 seconds.

Teradata BTEQ 08.02.02.00 for UNIX5. Enter your logon or BTEQ command:
Enthusiast

Re: "DBS CRASHED OR SESSIONS RESET." error when using bteq on Solaris

if there's teradata odbc installed in your system, try making use of the adhoc program in the examples folder to connect.

The other issue I could think of is a firewall problem between the two systems. which you will have to enlist the help of SA/Networking folks.

Re: "DBS CRASHED OR SESSIONS RESET." error when using bteq on Solaris

Thank you very much, this issue occured after Solaris IP address changed, I think it caused by network problem.

Re: "DBS CRASHED OR SESSIONS RESET." error when using bteq on Solaris

I have installed teradata dem0 12 vesrion on Windows XP.  I am getting the below error when I try to logon to BTEQ.

.LOGON localtd/tduser

.LOGON localtd/tduser

Password:

******

 *** Warning: DBS CRASHED OR SESSIONS RESET.  RECOVERY IN PROGRESS>

my hosts file has the below entry :

127.0.0.1       localhost  localtdcop1

Please let me know how can I resolve this?