err = -27003 :internal inconsistency detected
Posted in 2008
Topics: Platform-Specific Issues
Hi,
IDS 11.10 FC2W4 on Solaris 10
I've been getting err -27003 in the online.log on one of my instance.
this error is reported in the online.log for some time and then there is no
more of this error.
This instance is used for reporting so i restore it every week with the
production level 0 and today morning i found that the restoration which was
suppose to be finished 2 hours ago was still is in progress ( onstat -u/D )
the online.log was written with
09:50:44 listener-thread: err = -27003: oserr = 0: errstr = : Internal
Communications Error: internal inconsistency detected
.
Finally the restoration was completed but it took almost 2hrs and 30 more
minutes than it should have taken to finish.
At the end of restoration my script restarts the db and now even after the db
reboot i see the same error in online.log
I've checked
-27003 Internal Communications Error: internal inconsistency detected.
The IBM Informix client/server communication system has detected an
internal inconsistency. Typically, a client application reports this
error. This error might be a memory-corruption error due to a
programming bug. If the database server or a utility reported the
error, it is an Informix internal error. When an Informix internal
error occurs, note all circumstances and contact Technical Support
at tsmail@us.ibm.com.
Could any one pls let me know what results in this error as i dont get this on
any other instance. is it the application that need to be checked for but then
i got this today in between the restoration.
Any sugesstions would be thankful
Regards
Vikas
SO, do as the error text suggests and open a case with IBM tech support.
Art
On Mon, Nov 17, 2008 at 4:46 AM, VIKAS HIVARKAR
<vikas.hivarkar@gmail.com>wrote:
> Hi,
>
> IDS 11.10 FC2W4 on Solaris 10
>
> I've been getting err -27003 in the online.log on one of my instance.
> this error is reported in the online.log for some time and then there is no
> more of this error.
>
> This instance is used for reporting so i restore it every week with the
> production level 0 and today morning i found that the restoration which was
> suppose to be finished 2 hours ago was still is in progress ( onstat -u/D )
> the online.log was written with
>
> 09:50:44 listener-thread: err = -27003: oserr = 0: errstr = : Internal
> Communications Error: internal inconsistency detected
> ..
> Finally the restoration was completed but it took almost 2hrs and 30 more
> minutes than it should have taken to finish.
> At the end of restoration my script restarts the db and now even after the
> db
> reboot i see the same error in online.log
>
> I've checked
> -27003 Internal Communications Error: internal inconsistency detected.
>
> The IBM Informix client/server communication system has detected an
> internal inconsistency. Typically, a client application reports this
> error. This error might be a memory-corruption error due to a
> programming bug. If the database server or a utility reported the
> error, it is an Informix internal error. When an Informix internal
> error occurs, note all circumstances and contact Technical Support
> at tsmail@us.ibm.com.
>
> Could any one pls let me know what results in this error as i dont get this
> on
> any other instance. is it the application that need to be checked for but
> then
> i got this today in between the restoration.
>
> Any sugesstions would be thankful
>
> Regards
> Vikas
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--
Art S. Kagel
Oninit (www.oninit.com)
IIUG Board of Directors (art@iiug.org)
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Oninit, the IIUG, nor any other organization
with which I am associated either explicitly or implicitly. Neither do
those opinions reflect those of other individuals affiliated with any entity
with which I am affiliated nor those of the entities themselves.
Thank you Mr Kagel ! >SO, do as the error text suggests and open a case with IBM tech support. >Art