Assertion Error on INSERT

[rshapiro]

I am getting the following error when trying to INSERT into a Postgresql view across a linked server connection. Here is the error being reported in SQL Server.

#account 360
Msg 0, Sev 0, State 1: Unspecified error occurred on SQL Server. Connection may have been terminated by the server. [SQLSTATE HY000]
Msg 3624, Sev 20, State 1, Line 63 : A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support. [SQLSTATE HY000]
Msg 0, Sev 20, State 1, Line 52 : process_error_log 0 [SQLSTATE 01000]
Msg 3624, Sev 20, State 1, Line 63 : Location: "e:\\sql9_sp2_t\\sql\\ntdbms\\msql\\utils\\oledblob.cpp":819 Expression: hr == S_OK SPID: 59 Process ID: 3780 [SQLSTATE 01000]
Msg 3624, Sev 20, State 1, Line 63 : Location: qxcntxt.cpp:1069 Expression: cref == 0 SPID: 59 Process ID: 3780 [SQLSTATE 01000]

I found the following message in the Server Event Application log from the time this error occured:

Exception occurred in destructor of RowsetNewSS 0x0000000081EBC250. This error may indicate a problem related to releasing pre-allocated disk blocks used during bulk-insert operations. Restart the server to resolve this problem.

Any idea what could be causing this? I have had inserts work in the past but they have started giving me these errors. The DBCC CHECKDB does not show any problems with the database. I have had to restart the server to clear the problem, which I can not keep doing. Can you give me an idea of what is going on in this section of the driver so that I can adjust my design?

[Moderator]

Would you please send the following information?:
1. Current PGNP version/build.
2. Postgres table(s) schema and the insert statement used on the linked server.

It is possible that a bug was introduced in the provider in the build you have.

Thank you!

[rshapiro]

Version: PGNP64-1.3.0.2136.exe

I have attached a backup of the Postgresql development database.

I have also attached the SQL of the stored procedure. The insert statement in the stored procedure will work once after a restart of the server and then start to fail.

[Moderator]

I cannot find the attachment. Would you check if it was attached?

Feel free to send e-mail to support@pgoledb.com as well.

Thank you!

[rshapiro]

I have attempted to email you the file but the email box is full. Let me know when I can retry.

[rshapiro]

Let's see if this zip file will upload.

[Moderator]

I have received e-mail with the attachment and working on the issue. What statement is failing?

[rshapiro]

The Insert statement of the stored procedure.

[Moderator]

We have not been able to reproduce the issue. The stored procedure was executed many times without the error, and the PGNP Profiler did not catch errors.

Is your SQL Server having all the latest updates?

[rshapiro]

We have SP3 installed and plan to apply the updates through patch 9. I'll let you know if that resolves the issue.