Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved Table blob cannot be found?

  1. Issue
0
Votes
Undo
  1. Mathias Jespers
    Mathias Jespers
  2. PowerBuilder
  3. Monday, 21 June 2021 10:48 AM UTC

Hello,

For our database driver we are switching to MS OLE DB.

During testing it came to my attention that datawindows containing table blobs are causing dwruntimeerrors.

I get the message "Select Error: Blob Column doesn't exist". Now I checked the blob object but key clause, table and column were all set correctly. These blobs are images and I checked the db and unsurprisingly the columns do exist. In our connection string PBMaxBlobSize is set to 2147483647

What's going on here?

  1. BLOB
  2. DataWindow
timer event not working
Deadlock by API_Cursor SQL Server
Accepted Answer
Mathias Jespers
Mathias Jespers Accepted Answer Pending Moderation
  1. Tuesday, 29 June 2021 13:15 PM UTC
  2. PowerBuilder
  3. # Permalink

I had to upgrade to Powerbuilder 2019 R3 and set the dbms to "MSOLEDBSQL SQL Server" instead of "OLE DB"

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Tuesday, 29 June 2021 17:59 PM UTC
Thanks for sharing the solution!
  1. Helpful
There are no comments made yet.
Responses (4)
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Tuesday, 22 June 2021 17:24 PM UTC
  2. PowerBuilder
  3. # 1

1. Does the column exist in the table, in the database to which you are connecting.
   - I'm sure it's in the DEV database, how about the TEST database?

2. If the column exists, is it defined properly?

3. If you use PUBLIC SYNONYMS, has one been defined for the table?
    If not, you will need to specify owner.table.column

4. Is there data in the column>

5. If all of the above is correct, then you don't have READ rights.

 

Good Luck,

Olan

Comment
There are no comments made yet.
Mathias Jespers
Mathias Jespers Accepted Answer Pending Moderation
  1. Tuesday, 22 June 2021 09:06 AM UTC
  2. PowerBuilder
  3. # 2
 

Hello,

I did the tracing and this is the output:

(1E9C5440): BLOB READ: COLUMN="logo" TABLE="ourcompany"."dossier" CLAUSE= FROM "ourcompany"."dossier" WHERE dossier_id=1 (70.104 MS / 3387.945 MS)
(1E9C5440): *** ERROR 999 ***(rc -1) : Blob Column doesn't exist.

Before that is the retrieval of the dossier datawindow, no problems there.

Is there anything unusual you see in the blob read? Is it a problem we used our own schema name and not the default dbo one?

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 22 June 2021 14:53 PM UTC
Check with your DBA ... your new Schema might not have the proper Read permissions set for the Table and/or Blob column.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 21 June 2021 18:51 PM UTC
  2. PowerBuilder
  3. # 3

Hi Mathias;

 Have you tried setting an SQL trace to see if that gives you more information if this DML command(s) are failing and why?

For example:

  • SQLCA.DBMS = "MSO"    // Change to  ...
  • SQLCA.DBMS = "TRACE MSO"

Regards ... Chris

 

 

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.