Error 4706

From: Gavin Trigg 

> I have a 3rd party package (Prophecy from CSP) that is getting an INGRES error
> 4706 message. Where do I find this error documented? CSP is just passing along
> the error number it gets from the server.
> --
> Charlie Lancaster - Information Resources
> Texas Natural Resource Conservation Commission
> Phone:512-239-0795 FAX:512-239-0888 
> e-mail:clancast@irgate.tnrcc.texas.gov 
> 
Look at $II_SYSTEM/ingres/files/english/messages.txt:

E_US1262_4706:E_GEC2EC_SERIALIZATION

Your transaction has been aborted due to the transaction log file
having reached one of the limits set by the system administrator.
These limits are log_full, force_abort, and 90 percent of force_abort
when using the fast_commit option to start DBMS servers.

-- 
Gavin Trigg	Internet: gavin@asis.unimelb.EDU.AU
		Telephone: +61 3 344 6003 	Fax +61 3 347 4803
Data Base Administrator, Information Technology Services (ASIS),
The University of Melbourne, Parkville, Australia.  3052.





From comp.databases.ingres Fri Jan  6 15:07:50 1995
From: johna65@netcom.com (John Ainsworth)
Subject: Re: INGRES Error 4706

4706 is one of the errors mapped to the 'serialization' generic error. i.e. the
server was not able to complete the transaction for some reason and so has
aborted it (rolled it back). Specifically, 4706 maps to the fact that your
transaction was holding open the beginning-of-log marker and was selected for
abort when the logging system reached the 'force-abort-limit'.

E_US1262_4706:E_GEC2EC_SERIALIZATION
"Your transaction has been aborted due to the transaction log file having
reached one of the limits set by the system administrator"

Other errors treated this way include 4700 which maps to deadlock and 4702,
which I believe maps to lock timeout.

E_US125C_4700:E_GEC2EC_SERIALIZATION
"Deadlock detected, your single or multi-query transaction has been aborted"

E_US125_4702:E_GEC2EC_SERIALIZATION
"Timeout occurred on lock request (see SET LOCKMODE command)."

You might want to check the value of II_EMBED_SET, to determine if you have a
different value for error types than that expected by the application. Possible
values are "dbmserror" to return the INGRES errors (like 4706) and 
"genericerror" to get the generic error code (49900 for SERIALIZATION).

These errors are documented (I think) in the SQL reference manual, but I am not
at work so I cannot check.

Hope this helps.

John
------------------------------------------------------------------------------
John Ainsworth              johna65@netcom.com (home)             My Opinions.
                             johna@ingres.com (work)
------------------------------------------------------------------------------
Ingres Q & A
To William's Home Page
Email William