Page 1 of 1
TeraSession: cli rejected buffer : Any one encountered this.
Posted: Fri Oct 12, 2007 10:56 am
by DS_FocusGroup
Al_Address_Name_Link_FL,0: TeraSession: cli rejected buffer write, stall #0 of 0.
I am trying to FASTLOAD 30 million rows in teradata.It is failing
Any ideas.
For another table I put 9000 and it fails for the same reason
Serve is on UNIX
Re: TeraSession: cli rejected buffer : Any one encountered t
Posted: Fri Oct 12, 2007 12:06 pm
by wenfei.chen
Is that the only message you got from Director?
DS_FocusGroup wrote:Al_Address_Name_Link_FL,0: TeraSession: cli rejected buffer write, stall #0 of 0.
Re: TeraSession: cli rejected buffer : Any one encountered t
Posted: Fri Oct 12, 2007 12:14 pm
by wenfei.chen
Is that the only message you got from Director?
DS_FocusGroup wrote:Al_Address_Name_Link_FL,0: TeraSession: cli rejected buffer write, stall #0 of 0.
Posted: Sat Oct 13, 2007 12:39 am
by DS_FocusGroup
I got this as well : Al_Address_Name_Link_FL,0: TeraUtils:Put failed: Error Code = 350.
Al_Address_Name_Link_FL,0: DBCAREA msg_txt: Completed successfully.
and at the end
Al_Address_Name_Link_FL: TeraGenericQuery Error: Request Close failed: Error Code = 305 Session return code = 305 , DBC return code = 305
DBC message: CLI2: NOREQUEST(305): Specified request does not exist.
Posted: Sat Oct 13, 2007 1:01 am
by JoshGeorge
You might have to install a patch for resolving this. Pls. refer this
LINK for details.
Re: TeraSession: cli rejected buffer : Any one encountered t
Posted: Tue Oct 30, 2007 10:28 am
by ewaddell
I also experienced this error. Duplicate table rows was our issue.
[quote="DS_FocusGroup"]Al_Address_Name_Link_FL,0: TeraSession: cli rejected buffer write, stall #0 of 0.
I am trying to FASTLOAD 30 million rows in teradata.It is failing
Any ideas.
For another table I put 9000 and it fails for the same reason
Serve is on UNIX[/quote]
Posted: Thu Oct 29, 2009 4:16 am
by r.bhatia
Hi!
I did encounter the same problem while loading 37million rows on to a table.
The job was executing successfully previously but started failing one day and gave the same error with multiple trials.
The table had one of its column as varchar 8 we changed it to char 8 in dataset and table definition. The load completed successfully after this change.
Can someone tell me is this a known problem with this stage?
Thanks
Rakesh