|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||||||||||||||||
|
|||||||||||||||||
|
|||||||||||||||||
|
|||||||||||||||||
|
|||||||||||||||||
|
|
||||||||
|
|||||||||
|
|
|
|
Company
|
|
 SQL LINKS DEVELOPER SUPPORT
SEARCH Borland Online/Developer Support
Subject: Sybase raiserror from stored proc HighLevel overview: One possible cause of a Stored Proc not returning a raise error in Sybase System10, is the SYSDEPENDS table being 'corrupted'. One possible cause of 'corruption': Creating a storedprocedure1 that references a storedProcedure2 that does not exist will cause System10 to create a 'phantom' entry in SYSDEPENDS that associates storedProcedure1 with the non-existent storedProcedure2. storedProcedure2 can be created at a later date, but for some reason, raiseErrors within storedProcedure1 will not work. Solution: Delete storedProcedure1 and recreate it after storedProcedure2 has been created. Execute sp_recompile on one of the tables that is referenced within storedProcedure1. PUB SYB LINK ERROR CJ
|
|
||
|
|
|
|||
|
|||||
|
|
||||
 |
|||||
|
|||||
| Made in Borland® Copyright© 1994-2003 Borland Software Corporation. All rights reserved. Report Piracy, Legal Notices, Privacy Policy Last Modified Monday, 26-Mar-2001 16:27:04 PST |
|||||
