Re: TRUNCATE TABLE on V7R2 sometimes fails -- MIDRANGE-L

Subject: Re: TRUNCATE TABLE on V7R2 sometimes fails
From: John Yeung <gallium.arsenide@xxxxxxxxx>
Date: Fri, 16 Jul 2021 03:39:14 -0400
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On 2020-05-18, Patrik Schindler wrote:

Hello,

I'm fascinated about a glitch, that a TRUNCATE TABLE via ODBC and STRSQL returns no apparent error but the truncate itself failed. This happens sometimes, and it's not clear when it does. Once a day, the table is cleared and populated with (current) data fed via ODBC. From the IBM i side, the only application using this table is opening it read-only.

From reading https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/db2/rbafztruncate.htm I can't find any hint to what possibly could go wrong.

Any ideas how I can dig deeper to find the culprit?

:wq! PoC

Vern suggested calling IBM.

Patrik, did you ever find out anything more about this? I am
fascinated too, because it happens on our 7.3 system.

John Y.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: TRUNCATE TABLE on V7R2 sometimes fails , Patrik Schindler

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.