-346 UPDATE ERROR
Posted in 2000
Topics: High Availability & Replication, Error Codes & Troubleshooting
Hi,
I am getting repeatedly hit by error
-346:
Could not update a row in the table.
While the database server was processing an UPDATE, it received an
unexpected error. Check the accompanying ISAM error code for more detailed
information on the cause. Possible causes include hardware errors and
locking conflicts.
the update statement is a simple one with one set and where clause.
env:
DU 4.0F
DB-Access Version 7.31.FC2
INFORMIX-SQL Version 6.05.UD1
onstat -k:
Informix Dynamic Server Version 7.31.FC2 -- On-Line -- Up 1 days 02:14:30
-- 327680 Kbytes
Locks
address wtlist owner lklist type
tblsnum rowid key#/bsiz
200111b48 0 20785c148 0 S
100002 20b 0
200111ba0 0 207886928 0 S
100002 20b 0
200111c50 0 207862958 0 S
100002 20b 0
200111ca8 0 20785d618 0 S
100002 20b 0
200111d00 0 207863e28 0 S
100002 20b 0
200111d58 0 2078652f8 0 S
100002 20b 0
200111db0 0 207867c98 0 HDR+S
100002 207 0
200111e08 0 207869168 0 S
100002 20b 0
200111e60 0 20786a638 0 S
100002 20b 0
200111eb8 0 20786bb08 0 S
100002 20b 0
200111f10 0 20786e4a8 0 S
100002 20b 0
2001120c8 0 20786cfd8 0 S
100002 20b 0
200112120 0 20786f978 0 S
100002 20b 0
200112178 0 207870e48 0 S
100002 20b 0
2001121d0 0 207872318 0 S
100002 20b 0
200112bc8 0 207880ef8 0 S
100002 20b 0
200112cd0 0 207876f68 0 S
100002 20b 0
2001132a8 0 207887018 0 S
100002 20b 0
2001133b0 0 207884678 0 S
100002 20b 0
200113ca0 0 207877658 0 S
100002 20b 0
200113f60 0 20785cf28 0 S
100002 20b 0
200113fb8 0 20787bbb8 0 S
100002 20b 0
200114068 0 207876188 0 S
100002 20b 0
200114538 0 2078667c8 0 S
100002 20b 0
2001146f0 0 20787e558 0 S
100002 20b 0
200114c70 0 2078737e8 0 S
100002 20b 0
2001153a8 0 20787a6e8 0 S
100002 20b 0
200115458 0 20785c838 0 S
100002 20b 0
2001154b0 0 207880808 0 S
100002 20b 0
200115980 0 20787f338 0 S
100002 20b 0
200115ae0 0 207886238 0 S
100002 20b 0
2001163d0 0 20785eae8 0 S
100002 207 0
20046d0f0 0 20785ba58 0 HDR+S
100002 20b 0
20046d250 0 20785dd08 0 S
100002 20b 0
20046d3b0 0 207863048 0 S
100002 20b 0
20046d408 0 207861b78 0 S
100002 20b 0
20046d460 0 207864518 0 S
100002 20b 0
20046d568 0 2078659e8 0 S
100002 20b 0
20046d670 0 207869858 0 S
100002 20b 0
20046d6c8 0 20786c1f8 0 S
100002 20b 0
20046d720 0 20786d6c8 0 S
100002 20b 0
20046d778 0 207870068 0 S
100002 20b 0
20046d828 0 207866eb8 0 S
100002 20b 0
20046d880 0 207868388 0 S
100002 20b 0
20046d8d8 0 20786eb98 0 S
100002 20b 0
20046da90 0 20787d778 0 S
100002 20b 0
20046dbf0 0 2078831a8 0 S
100002 20b 0
20046e010 0 20787c998 0 S
100002 20b 0
20046e380 0 207872a08 0 S
100002 207 0
20046e850 0 20785f8c8 0 S
100002 20b 0
20046e9b0 0 207879908 0 S
100002 20b 0
20046f400 0 20785ffb8 0 S
100002 20b 0
20046f458 0 207883898 0 S
100002 20b 0
20046f560 0 207878b28 0 S
100002 20b 0
2004708f8 0 20786ad28 0 S
100002 20b 0
200470a58 0 20787d088 0 S
100002 20b 0
200470dc8 0 207880118 0 S
100002 20b 0
2004716b8 0 207879218 0 S
100002 20b 0
200471ce8 0 207862268 0 S
100002 20b 0
2004723c8 0 20787fa28 0 S
100002 20b 0
200472420 0 207887708 0 S
100002 20b 0
2007c86f0 0 20785a588 0 S
100002 20b 0
2007c87f8 0 20786f288 0 S
100002 20b 0
2007c88a8 0 20785e3f8 0 S
100002 20b 0
2007c8958 0 207860d98 0 S
100002 20b 0
2007c8a08 0 207863738 0 S
100002 20b 0
2007c8a60 0 207869f48
Hi,
If your update statement is in an ESQLC program you have to print out
sqlca.sqlerrd[1] to know wich ISAM error occours. With ISAM error code,
you can know the cause (-144 for example is key value locked). It could
be a syntax error, too.
bye
fabio
"Bhaskarla, Sunil" ha scritto:
>
> Hi,
> I am getting repeatedly hit by error
> -346:
> Could not update a row in the table.
> While the database server was processing an UPDATE, it received an
> unexpected error. Check the accompanying ISAM error code for more detailed
> information on the cause. Possible causes include hardware errors and
> locking conflicts.
>
> the update statement is a simple one with one set and where clause.
>
> env:
>
> DU 4.0F
> DB-Access Version 7.31.FC2
> INFORMIX-SQL Version 6.05.UD1
>
> onstat -k:>
> Informix Dynamic Server Version 7.31.FC2 -- On-Line -- Up 1 days 02:14:30
> -- 327680 Kbytes
>
> Locks
> address wtlist owner lklist type
> tblsnum rowid key#/bsiz
> 200111b48 0 20785c148 0 S
> 100002 20b 0
> 200111ba0 0 207886928 0 S
> 100002 20b 0
> 200111c50 0 207862958 0 S
> 100002 20b 0
> 200111ca8 0 20785d618 0 S
> 100002 20b 0
> 200111d00 0 207863e28 0 S
> 100002 20b 0
> 200111d58 0 2078652f8 0 S
> 100002 20b 0
> 200111db0 0 207867c98 0 HDR+S
> 100002 207 0
> 200111e08 0 207869168 0 S
> 100002 20b 0
> 200111e60 0 20786a638 0 S
> 100002 20b 0
> 200111eb8 0 20786bb08 0 S
> 100002 20b 0
> 200111f10 0 20786e4a8 0 S
> 100002 20b 0
> 2001120c8 0 20786cfd8 0 S
> 100002 20b 0
> 200112120 0 20786f978 0 S
> 100002 20b 0
> 200112178 0 207870e48 0 S
> 100002 20b 0
> 2001121d0 0 207872318 0 S
> 100002 20b 0
> 200112bc8 0 207880ef8 0 S
> 100002 20b 0
> 200112cd0 0 207876f68 0 S
> 100002 20b 0
> 2001132a8 0 207887018 0 S
> 100002 20b 0
> 2001133b0 0 207884678 0 S
> 100002 20b 0
> 200113ca0 0 207877658 0 S
> 100002 20b 0
> 200113f60 0 20785cf28 0 S
> 100002 20b 0
> 200113fb8 0 20787bbb8 0 S
> 100002 20b 0
> 200114068 0 207876188 0 S
> 100002 20b 0
> 200114538 0 2078667c8 0 S
> 100002 20b 0
> 2001146f0 0 20787e558 0 S
> 100002 20b 0
> 200114c70 0 2078737e8 0 S
> 100002 20b 0
> 2001153a8 0 20787a6e8 0 S
> 100002 20b 0
> 200115458 0 20785c838 0 S
> 100002 20b 0
> 2001154b0 0 207880808 0 S
> 100002 20b 0
> 200115980 0 20787f338 0 S
> 100002 20b 0
> 200115ae0 0 207886238 0 S
> 100002 20b 0
> 2001163d0 0 20785eae8 0 S
> 100002 207 0
> 20046d0f0 0 20785ba58 0 HDR+S
> 100002 20b 0
> 20046d250 0 20785dd08 0 S
> 100002 20b 0
> 20046d3b0 0 207863048 0 S
> 100002 20b 0
> 20046d408 0 207861b78 0 S
> 100002 20b 0
> 20046d460 0 207864518 0 S
> 100002 20b 0
> 20046d568 0 2078659e8 0 S
> 100002 20b 0
> 20046d670 0 207869858 0 S
> 100002 20b 0
> 20046d6c8 0 20786c1f8 0 S
> 100002 20b 0
> 20046d720 0 20786d6c8 0 S
> 100002 20b 0
> 20046d778 0 207870068 0 S
> 100002 20b 0
> 20046d828 0 207866eb8 0 S
> 100002 20b 0
> 20046d880 0 207868388 0 S
> 100002 20b 0
> 20046d8d8 0 20786eb98 0 S
> 100002 20b 0
> 20046da90 0 20787d778 0 S
> 100002 20b 0
> 20046dbf0 0 2078831a8 0 S
> 100002 20b 0
> 20046e010 0 20787c998 0 S
> 100002 20b 0
> 20046e380 0 207872a08 0 S
> 100002 207 0
> 20046e850 0 20785f8c8 0 S
> 100002 20b 0
> 20046e9b0 0 207879908 0 S
> 100002 20b 0
> 20046f400 0 20785ffb8 0 S
> 100002 20b 0
> 20046f458 0 207883898 0 S
> 100002 20b 0
> 20046f560 0 207878b28 0 S
> 100002 20b 0
> 2004708f8 0 20786ad28 0 S
> 100002 20b 0
> 200470a58 0 20787d088 0 S
> 100002 20b 0
> 200470dc8 0 207880118 0 S
> 100002 20b 0
> 2004716b8 0 207879218 0 S
> 100002 20b 0
> 200471ce8 0 207862268 0 S
> 100002 20b 0
> 2004723c8 0 20787fa28 0 S
> 100002 20b 0
> 200472420 0 207887708 0
Related threads
- record locked
- who locks a record?
- Regarding Non-Default Page Sizes
- Don't Understand Table's Space Requirement