Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XPCG7-0005xD-Ph for pgsql-admin@arkaria.postgresql.org; Wed, 03 Sep 2014 15:14:07 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XPCG7-00016h-8P for pgsql-admin@arkaria.postgresql.org; Wed, 03 Sep 2014 15:14:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XPCG5-00014B-P1; Wed, 03 Sep 2014 15:14:05 +0000 Received: from mailfilter.invera.com ([198.168.207.50]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XPCFz-0003bJ-TL; Wed, 03 Sep 2014 15:14:04 +0000 Received: from epgate.invera.com (localhost.localdomain [127.0.0.1]) by epgate.invera.com (Postfix-out) with ESMTP id DD41D3C5BC1; Wed, 3 Sep 2014 11:13:59 -0400 (EDT) X-Propel-Return-Path: Received: from mailfilter.invera.com ([172.20.200.19]) by [127.0.0.1] ([127.0.0.1]) (port 7027) (Abaca EPG outproxy filter 3.1.1.9369 $Rev: 9262 $) id rfTOre93fdX1; Wed, 03 Sep 2014 11:13:59 -0400 Received: from Exch2.invera.com (exch2.invera.com [172.20.35.3]) by epgate.invera.com (Postfix-out) with ESMTP id B068A3C5BCB; Wed, 3 Sep 2014 11:13:59 -0400 (EDT) Received: from EXCH2.invera.com (172.20.35.3) by Exch2.invera.com (172.20.35.3) with Microsoft SMTP Server (TLS) id 15.0.913.22; Wed, 3 Sep 2014 11:13:57 -0400 Received: from EXCH2.invera.com ([fe80::3999:28ea:6cf1:1e83]) by Exch2.invera.com ([fe80::3999:28ea:6cf1:1e83%12]) with mapi id 15.00.0913.011; Wed, 3 Sep 2014 11:13:57 -0400 From: Alanoly Andrews To: "'pgsql-admin@postgresql.org'" CC: "'pgsql-general@postgresql.org'" Subject: Cannot retrieve images inserted through VB and odbc, after a table reorganization. Thread-Topic: Cannot retrieve images inserted through VB and odbc, after a table reorganization. Thread-Index: Ac/Hia3+YDipKaLyQWm1/m+XnLu8SA== Date: Wed, 3 Sep 2014 15:13:56 +0000 Message-ID: <6909b219ecae4d41b431efdaf6c953a3@Exch2.invera.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.20.200.88] Content-Type: multipart/alternative; boundary="_000_6909b219ecae4d41b431efdaf6c953a3Exch2inveracom_" MIME-Version: 1.0 X-Propel-ID: rfTOre93fdX1 X-Pg-Spam-Score: -3.4 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org --_000_6909b219ecae4d41b431efdaf6c953a3Exch2inveracom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, We have an issue with images (TIFF files) that are loaded into a postgres d= atabase table (where the image field is defined as type "lo"). The code to = load the images is written in VB and the connection to the database is thro= ugh postgres odbc installed on the PC. All images inserted through the VB = program are retrievable also through odbc/VB, as long as the table rows at = the backend are not reorganized in any way. If the table data is unloaded/r= eloaded or clustered (on an index) or reloaded through a pg_dump and restor= e, then on trying to retrieve the images, the VB program gets the error : "= Multiple-step OLE DB operation generated errors. Check each OLE DB status v= alue......etc". The data in the backend database is still readable through other image retr= ieval programs connecting directly to the server (not through ODBC or VB). The database is on an AIX server (version 6.1). Postgres version is 9.1.4. I'd welcome any input towards the resolution of this problem. Thanks. Alanoly Andrews alanolya@invera.com ________________________________ If you no longer wish to receive any of our emails, click on UNSUBSCRIBE. This e-mail may b= e privileged and/or confidential, and the sender does not waive any related= rights and obligations. Any distribution, use or copying of this e-mail or= the information it contains by other than an intended recipient is unautho= rized. If you received this e-mail in error, please advise me (by return e-= mail or otherwise) immediately. Si vous ne d?sirez plus recevoir de nos courriels, veuillez appuyer sur D?S= ABONNEMENT. Ce c= ourriel est confidentiel et prot?g?. L'exp?diteur ne renonce pas aux droits= et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie d= e ce message ou des renseignements qu'il contient par une personne autre qu= e le (les) destinataire(s) d?sign?(s) est interdite. Si vous recevez ce cou= rriel par erreur, veuillez m'en aviser imm?diatement, par retour de courrie= l ou par un autre moyen. --_000_6909b219ecae4d41b431efdaf6c953a3Exch2inveracom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hello,
 
We have an issue with images (TIFF files) that are loaded in= to a postgres database table (where the image field is defined as type = “lo”). The code to load the imag= es is written in VB and the connection to the database is through postgres odbc installed on the PC. <= b>All images inserted through the VB program are retrievable also through o= dbc/VB, as long as the table rows at the backend are not reorganized in any way. If the table data is unloaded/reloaded or clustered = (on an index) or reloaded through a pg_dump and restore, then on trying to retrieve the images, the VB program gets the error : <= /b>“Multiple-step OLE DB operation generated errors. Check each OLE DB status value= ……etc”.
 
The data in the backend database is still readable through other im= age retrieval programs connecting directly to the server (not throug= h ODBC or VB).
&nbs= p;
The database is on an AIX server (version 6.1). Postgres ver= sion is 9.1.4.
 
I’d welcome any input towards the= resolution of this problem.
 
Thanks.
 
Alanoly Andrews
alanolya@invera.com
&nbs= p;

  ________________________________  
<= span style=3D"font-size:12pt;">If you no longer wish to receive any of our = emails, click on UNSUBSCRIBE. This e-mail may be privileged and/or confidential, and the sender does not = waive any related rights and obligations. Any distribution, use or copying = of this e-mail or the information it contains by other than an intended rec= ipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) imme= diately.
 

<= span style=3D"font-size:12pt;">Si vous ne désirez plus recevoir de n= os courriels, veuillez appuyer sur DÉSABONNEMENT.= Ce courriel est confidentiel et protégé. L'expéditeur = ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusio= n, utilisation ou copie de ce message ou des renseignements qu'il contient = par une personne autre que le (les) destinataire(s) désigné(s= ) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser= immédiatement, par retour de courriel ou par un autre moyen.
--_000_6909b219ecae4d41b431efdaf6c953a3Exch2inveracom_--