Run-time error -2147467259 (80004005) could not update. Currently locked....

Run-time error -2147467259 (80004005) could not update. Currently locked....

Post by Microsof » Tue, 11 Jan 2000 04:00:00

On updating several recordset we get the above mentioned error. After having
completed updating one table the programs starts updating the next table and
gets a run-time error because the database now's locked. We have reduced the
number of keyes with some effect so we think the database is busy opdating
indexes etc. How can we make the program wait untill the database is ready
for the next update ? We use ADO and have tried jet.provider  3.51 and 4.0
and ODBC with the same result.

With the ODBCprovider against sql-server 7.0  the program is running ok.


1. Strange Oracle error: ORA-06502 (and Microsoft run-time error -2147467259(80004005))

[Sorry if this post appears more than once. I ran into some trouble
with the Internet connection. Damn those corporate firewalls!]


I encounter a strange error when I try to call a stored procedure from
a Visual Basic application. After calling the procedure I get the
following error:

Run-time error '-2147467259(80004005)':

[Oracle][ODBC][Ora]ORA-06502: PL/SQL: numeric or value error
ORA-06512: at "SUSHI.SUSHI_HI_NI", line 153
ORA-06512: at line 1

Now, AFAIK, the run-time error is a Microsoft (VB) error while the
second is an Oracle error, correct?
I get this error when I use my laptop
Microsoft Windows 2000
Service Pack 2

x86 Family Model 8 Stepping 3
130.544 KB RAM

The Oracle server is 8i Enterprise Edition Release -

Now comes the strange part. When run the same application on a user
desktop of my client, then the procedure runs OK! No errors,

Desktop computer information:
Microsoft Windows NT

x86 Family 6 Model 8 Stepping 3
260.404 KB RAM

I've tried all I could localising the error, but I cannot find
anything. The ORA-06502 would suggest that a variable in the procedure
is not big enough for a certain value, but that does not explain why
it works on other computers. Besides, AFAIK, the variables are big
enough to hold the information (each defined variable has room for 100

Oh, and as a final touch to the mystery, when I directly call the
procedure in SQL Plus from my laptop (and enter the same values as I
do when I use the VB application) the procedure again works. I really
don't know what's happening here!

I hope the information presented here is clear enough. I personally
have a lot of difficulty to get any grip on the situation. Hopefully
you can help me out.

C ya!


2. Archiving data

3. REV G2B Problem with year 2000

4. Run Time Error '-2147467259 (80004005)': [DBNMPNTW] Connection Broken

5. Simple DMO questions

6. Run-time error '-2147467259 (80004005)'

7. AIR research study: Attn: Data Query Users

8. RUN-TIME ERROR -2147467259 (80004005)

9. Run-time error -2147467259 (80004005) using refresh method ADODC

10. Run-time error -2147467259 (80004005) when using adodc refresh method

11. Run-time error '-2147467259 (80004005)'