ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Websphere broker cores

Post new topic  Reply to topic
 Websphere broker cores « View previous topic :: View next topic » 
Author Message
go_ram
PostPosted: Thu Dec 07, 2006 1:34 pm    Post subject: Websphere broker cores Reply with quote

Novice

Joined: 28 Oct 2004
Posts: 13

We are running Wbi 6 with fix pack 3 we are getting cores such as this
SuccessGeneral warning. Disconnect error.String data, right truncated.Privilege not revoked.Privilege not granted.Invalid connection string attribute.Error in row.Option value changed.No rows updated or deleted.More than one row updated or deleted.Cancel treated as SQLFreeStmt with the SQL_CLOSE option .Attempt to fetch before the result set returned the first rowset.Fractional t runcation.Wrong number of parameters.Prepared statement not a cursor-specification.Restricted data type attribute violation.Invalid descriptor count.Invalid descriptor index.Invalid use of default parameter .Client unable to establish connection.Connection name in use. Connection does not exist.Server rejected the connection.Connection failure.Connection failure during transaction.Communication link failure.Loc ator exception - invalid specification.Locator exception - indirect locators are not updatable. Insert value list does not match column list.Degree of derived table does not match column list.String data, right truncated.Indicator variable required but not supplied.Numeric value out of range.Invalid interval format.Invalid datetime format.Datetime field overflow.Substring Error.Division by zero.Interval field overflow.Invalid character value.String data, length mismatch.Integrity constraint violation.Invalid cursor state.Invalid transaction state.Invalid authorization specification.Invalid cursor name.Syntax err or or access violation.Duplicate cursor name.Serialization failure.Syntax error or access violation.Base table or view already exists.Base table or view not found.Index already exists.Index not found.Column already exists.Column not found.No default for column.Operation aborted.General error.Memory allocation error.Invalid application buffer type.Invalid SQL data type.Associated statement is not prepared.Oper ation cancelled.Invalid use of null pointer.Function sequence error.Attribute cannot be set now.Invalid transaction operation code.Memory management error.Limit on the number of handles exceeded.No cursor n ame available.Cannot modify an implementation row descriptor.Invalid use of an automatically allocated descriptor handle.Server declines cancel request.Non-character or non-binary data sent in pieces.Attemp t to concatenate a null value.Inconsistent descriptor information.Descriptor invalid or indirect reference.Invalid attribute value.Invalid locator operation code.Invalid string or buffer length.Invalid desc riptor field identifier.Invalid attribute/option identifier.Invalid parameter number.Function type out of range.Invalid information type.Column type out of range.Scope type out of range.Nullable type out of range.Uniqueness option type out of range.Accuracy option type out of range.Invalid retrieval code.Invalid precision value.Invalid parameter type.Fetch type out of range.Row value out of range.Concurrency option out of range.Invalid cursor position.Invalid driver completion.Invalid bookmark value.Optional feature not implemented.Timeout expired.Driver does not support this function.Data source name not found and no default driver specified.Specified driver could not be loaded.Driver's SQLAllocEnv failed.Driver's SQLAllocConnect failed.Driver's SQLSetConnectAttr failed.No data source or driver specified; dialog prohibitedDialog failed.Unable to load translation DLL.Data source name too long.Driver name too long.DRIVER keyword syntax error.Trace file error.Cursor operation conflict.This is the fudge message.Distri buted transaction enlistment failed.Load of XA library failed.Unable to communicate with DTC.RequestNewResourceManager failed.xa_open() failed.TranslateTridToXid faile

Any body can help me with this. We opened a pmr with ibm they suggested to upgraded to fix pack 3 from fix pack 1 but still we are getting the core.

Thanks in advance,
Back to top
View user's profile Send private message
go_ram
PostPosted: Thu Dec 07, 2006 2:05 pm    Post subject: Reply with quote

Novice

Joined: 28 Oct 2004
Posts: 13

i suspect something with the network dropping or the database connections any thoughts ..



Back to top
View user's profile Send private message
whocares61
PostPosted: Thu Dec 07, 2006 2:55 pm    Post subject: Reply with quote

Newbie

Joined: 06 Dec 2006
Posts: 7
Location: New Zealand

Looks like ODBC problem to me - what it basically tries to tell you is that Broker tries to read data from the empty cursor, so there's obviously sync issues... Which database you are using? Have you tried to change ODBC driver? Or probably try to play with ODBC settings - like enable scrollable cursors, catalog functions include synonyms, etc.

HTH

Cheers

Ray
Back to top
View user's profile Send private message Visit poster's website
go_ram
PostPosted: Fri Dec 08, 2006 6:34 am    Post subject: Reply with quote

Novice

Joined: 28 Oct 2004
Posts: 13

This happens only in load . The database which we are using is Oracle 10.The execution groups stops and restarts itself after the core and it starts processing.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Fri Dec 08, 2006 6:50 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

I'm really confused here. Which product are you running? Message Broker v6?

If you're getting a core file, you need to report this to IBM by opening a PMR.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
go_ram
PostPosted: Fri Feb 02, 2007 7:52 am    Post subject: Reply with quote

Novice

Joined: 28 Oct 2004
Posts: 13

This seems to be the case of the issues with oracle driver which we are using as per IBM.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Websphere broker cores
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.