@@ERROR not set upon following error in Sybase ASE

Question

I am faced with the following error -

Number (213) Severity (16) State (5) Server (ASED052) Insert error: column name or number of supplied values does not match table definition.

and I am trying to catch it with -

IF @@ERROR != 0
BEGIN
-- Do stuff
END

However, I have found out that this error does not set the global @@ERROR variable. As such is the case, does anyone know of another method to catch this error?

Are you sure it proceeds after the error? in mssql Sev. 16 will terminate the batch — Alex K., Nov 09 '12 at 14:58

score 0 · Answer 1 · answered Nov 09 '12 at 14:53

0

Have you tried using the following functions?

ERROR_LINE()
ERROR_MESSAGE()
ERROR_NUMBER()
ERROR_PROCEDURE()
ERROR_SEVERITY()
ERROR_STATE()

Or you could use a try/catch block :

BEGIN TRY
...
END TRY
BEGIN CATCH
...
END CATCH

answered Nov 09 '12 at 14:53

Dominic Goulet

7,983
7
28
56

Yes it's sometimes SYBASE :) – Robert Nov 09 '12 at 19:06

Robert · Answer 2 · 2012-11-09T19:24:57.353

0

Try this solution:

I. Create a procedure with the code that generates error.

create procedure Proc1
as
begin
  insert into tab(Fake_Column) 
  values ('aaa')
end

II. Run procedure Proc1 and catch error:

exec Proc1

IF @@error <> 0
begin
    print 'ERROR!'    
end

edited Nov 09 '12 at 19:24

answered Nov 09 '12 at 18:54

Robert

25,425
8
67
81

If `@@error = 0` will print when there is no error, right? Not a SYBASE guy as I proved up there tho. – Dominic Goulet Nov 09 '12 at 19:13
@Parado, I do not wish to nest SPROCS like that. Thanks though. – czchlong Nov 09 '12 at 19:25
@czchlong I'm not sure there is another way, It's SYBASE. – Robert Nov 09 '12 at 20:05

score 0 · Accepted Answer · answered Nov 13 '12 at 19:48

0

Apparently there is no way to catch the specified error using the global @@ERROR variable.

answered Nov 13 '12 at 19:48

czchlong

2,434
10
51
65

@@ERROR not set upon following error in Sybase ASE

3 Answers3