Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qrJsG-003g1f-2M for pgsql-odbc@arkaria.postgresql.org; Fri, 13 Oct 2023 15:14:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qrJsD-001yEx-Ju for pgsql-odbc@arkaria.postgresql.org; Fri, 13 Oct 2023 15:14:46 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qrJsD-001yEp-Ce for pgsql-odbc@lists.postgresql.org; Fri, 13 Oct 2023 15:14:46 +0000 Received: from mail-io1-xd34.google.com ([2607:f8b0:4864:20::d34]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qrJs7-000JIb-3M for pgsql-odbc@postgresql.org; Fri, 13 Oct 2023 15:14:44 +0000 Received: by mail-io1-xd34.google.com with SMTP id ca18e2360f4ac-79fca042ec0so83588939f.3 for ; Fri, 13 Oct 2023 08:14:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697210078; x=1697814878; darn=postgresql.org; h=mime-version:subject:references:in-reply-to:message-id:cc:to:from :date:from:to:cc:subject:date:message-id:reply-to; bh=CAlm6wDXRdkKcLvFDVG7XJxUPrIkz8gQLQ7nUdKTKHk=; b=Ou0eZtZYIlMZyg0Sz+R2Uzt8mwUIELsR+fIBm5D1hKp44sFlh5ORJtM0GfgcSyvAmQ nO9AABGwyRAlwivtj7x8eOnDyZTtxyttNDSerFzlphJeWlfvhZFL2RWUW0Aq0AMZ/FFm AZvvkLcxrezkJgNMgObywiDsphRjMaD8FcSsURYf0myXxbEqNDf2yIQb8y11nOYLymLi FQzAL/veQSo1qNZgDedkD02W0qh3UXDGmahGUC+N3ZEtHB9aDSs/+NYavdFfgRJCYM1L 8gJ07GZeqH8BEkgtlUB+O9FitS+pIgm93IIM3m73sZYmVxs0xNxJfJhJ39pvZUCoyQay jvhg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697210078; x=1697814878; h=mime-version:subject:references:in-reply-to:message-id:cc:to:from :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=CAlm6wDXRdkKcLvFDVG7XJxUPrIkz8gQLQ7nUdKTKHk=; b=ILW2zVWrLCLXHjPUodrZo+QTqYsGX3m+OsESUDXRIIR0HPzhX/FztFp7JF5hJuRpUb gwWiNo7FVmXBx8DvRk7UVOadrxvqHu9dTjnM4irffsCXMmShc3GcIuHLNXsRjvbjMgGC PMbqIaoQYZqHq8fHPG8A8F2daXxY9IYP4t9/QIypxlwxKPTJoCjRKxOj50grSxKzjTog SDv0B3kvOmt7F1E5OYJvRF1gUR1+YS6ayPJXuf3inpLcsR7X7wV3LKneICoOLgxmLwH5 xLm6pX3EAHXZXk21Kp11DWSSVIJE/uYnsKN18cC41GrtoqwjsqKopd5VzkjBSGJMOw+b b2og== X-Gm-Message-State: AOJu0YxbmukrXRONMBbjcc7U73fJP0lzkuK8nqhtkEqWXeuUZeXHC/nM 6pvwaOr7nWX8otSyJ+F7w1E= X-Google-Smtp-Source: AGHT+IF8QAV1qHnQU4j4sRQC6V6Aunw+RFW1YS7h8qECu2nsccZNZO790q7Qpr6Pksz1XFuUGcK21g== X-Received: by 2002:a05:6602:220c:b0:786:fff8:13c2 with SMTP id n12-20020a056602220c00b00786fff813c2mr29773900ion.11.1697210077531; Fri, 13 Oct 2023 08:14:37 -0700 (PDT) Received: from email.client.edison.tech ([2607:fb91:7e3:85ec:7d04:d61f:29d1:a22f]) by smtp.gmail.com with ESMTPSA id go11-20020a0566382c8b00b0043a1656964bsm4484221jab.37.2023.10.13.08.14.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 13 Oct 2023 08:14:37 -0700 (PDT) Date: Fri, 13 Oct 2023 10:14:35 -0500 From: b55white To: Dave Cramer , "Victor K." Cc: pgsql-odbc Message-ID: <81726013-177b-4251-913c-fe04583b056f@edison> In-Reply-To: References: Subject: Re: ODBC error MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="EdoMail65295edc_4d617651_191d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --EdoMail65295edc_4d617651_191d Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline > > On Oct 13, 2023 at 3:48 AM, Victor K. wrote: > ODBC driver x64 Postrge on linux ver 15 ODBC psqlodbc_16_00_0000-x64 Error OLE DB or ODBC error. An error occurred while processing table 'Query'. The current operation was cancelled because another operation in the transaction failed. and The commit or rollback request cannot be completed because there is no active transaction in this session. On small tables everything is okay I would suggest looking at the server logs. Dave Cramer www.postgres.rocks > > > > > > On servers side logs > > could not receive data from client connection timed out > // > (,'')> why? > <( )' > | | > ,,_ _,, > > > Client side logs would probably be useful. > > Turm on through the DSN settings. > > Unless you specify a directory, they'll be in the users home dir. > > Remember to shut them off when finished as they gobble space quickly. > > > > Brad. > > > > --EdoMail65295edc_4d617651_191d Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
On Oct 13, = 2023 at 3:48 AM, Victor K. <= ptahin=40gmail.com> wrote:
ODBC driver x64
Postrge on linux ver 15
ODBC psq= lodbc=5F16=5F00=5F0000-x64
Error<= /div>
OLE DB or ODBC error. An error oc= curred while processing table 'Query'. The current operation was cancelle= d because another operation in the transaction failed.
and 
T= he commit or rollback request cannot be completed because there is no act= ive transaction in this session.
= On small tables everything is okay

I would suggest looking at = the server logs. 
Dave Crame= r
www.postgres.rocks
On servers side logs 
could not receive data from client connection tim= ed out
 //
  (,'')&g= t; why=3F
<(   )'
   =7C =7C
,,=5F =5F,,<= /div>

Client side logs wo= uld probably be useful.
Turm on through the DSN settings. 
Unless you specify a directory, they'll = be in the users home dir.
Remember to shut them off when finished as they gobble space q= uickly. 
<= br>
Brad. =
--EdoMail65295edc_4d617651_191d--