创建相关存储过程时导致sybase异常报错，请教是什么原因

wind1211 发表于 2009-02-06 13:10

00:00000:00001:2009/02/05 16:12:05.05 serverConfiguration file '/home/sybase/ASE-12_5/zxmmlog.cfg' has been written and the previous version has been renamed to '/home/sybase/ASE-12_5/zxmmlog.001'.
03:00000:00001:2009/02/05 16:12:05.09 serverThe configuration option 'SQL batch capture' has been changed by 'sa' from '0' to '1'.
01:00000:00069:2009/02/05 16:12:16.99 kernelCurrent process (0xe600023) infected with signal 11 (SIGSEGV)
00:00000:00138:2009/02/05 16:12:16.99 kernelCurrent process (0xf51004e) infected with signal 11 (SIGSEGV)
00:00000:00138:2009/02/05 16:12:17.02 kernelAddress 0x0x085af7f6 (oh_get_obfuscated+0x226), siginfo (code, address) = (2, 0x0xbe833000)
00:00000:00138:2009/02/05 16:12:17.02 kernel************************************
00:00000:00138:2009/02/05 16:12:17.02 kernelSQL causing error : sp_configure 'enable monitoring', 1

00:00000:00138:2009/02/05 16:12:17.02 kernel************************************
01:00000:00069:2009/02/05 16:12:17.03 kernelAddress 0x0x085af7f6 (oh_get_obfuscated+0x226), siginfo (code, address) = (2, 0x0xbe833000)
01:00000:00069:2009/02/05 16:12:17.03 kernel************************************
01:00000:00069:2009/02/05 16:12:17.03 kernelSQL causing error : select getdate()
01:00000:00069:2009/02/05 16:12:17.03 kernel************************************
01:00000:00069:2009/02/05 16:12:17.03 serverSQL Text: select getdate()
00:00000:00138:2009/02/05 16:12:17.03 serverSQL Text: sp_configure 'enable monitoring', 1
00:00000:00138:2009/02/05 16:12:17.03 kernelcurdb = 1 tempdb = 2 pstat = 0x10000
00:00000:00138:2009/02/05 16:12:17.03 kernellasterror = 0 preverror = 0 transtate = 1
00:00000:00138:2009/02/05 16:12:17.03 kernelcurcmd = 0 program = isql
01:00000:00069:2009/02/05 16:12:17.03 kernelcurdb = 1 tempdb = 2 pstat = 0x10000
01:00000:00069:2009/02/05 16:12:17.04 kernellasterror = 0 preverror = 0 transtate = 1
01:00000:00069:2009/02/05 16:12:17.04 kernelcurcmd = 0 program =
00:00000:00138:2009/02/05 16:12:17.07 kernelpc: 0x088ed247 pcstkwalk+0x2b(0x40e2acac, 0x40e2aa68, 0x0000270f, 0x00000002, 0x093798d0)
00:00000:00138:2009/02/05 16:12:17.07 kernelpc: 0x088ed182 ucstkgentrace+0x1b6(0x0f51004e, 0x00000002, 0x0000270f, (nil), (nil))
00:00000:00138:2009/02/05 16:12:17.07 kernelpc: 0x08888b8c ucbacktrace+0xa0((nil), 0x00000001, 0x093798d0, 0x40e2b584, (nil))
00:00000:00138:2009/02/05 16:12:17.07 kernelpc: 0x0819ce29 terminate_process+0xcb1((nil), 0xffffffff, 0x400567a0, (nil), 0x0000000b)
00:00000:00138:2009/02/05 16:12:17.07 kernelpc: 0x088b8003 kisignal+0x1ff(0x0000000b, 0x40e2d5e8, 0x40e2d668, 0xffffffff, 0xffffffff)
01:00000:00069:2009/02/05 16:12:17.07 kernelpc: 0x088ed247 pcstkwalk+0x2b(0x40b4f94c, 0x40b4f708, 0x0000270f, 0x00000002, 0x093798d0)
01:00000:00069:2009/02/05 16:12:17.07 kernelpc: 0x088ed182 ucstkgentrace+0x1b6(0x0e600023, 0x00000002, 0x0000270f, (nil), (nil))
01:00000:00069:2009/02/05 16:12:17.07 kernelpc: 0x08888b8c ucbacktrace+0xa0((nil), 0x00000001, 0x093798d0, 0x40b50224, (nil))
01:00000:00069:2009/02/05 16:12:17.07 kernelpc: 0x0819ce29 terminate_process+0xcb1((nil), 0xffffffff, 0x400567a0, (nil), 0x0000000b)
01:00000:00069:2009/02/05 16:12:17.07 kernelpc: 0x088b8003 kisignal+0x1ff(0x0000000b, 0x40b52288, 0x40b52308, 0xffffffff, 0xffffffff)
00:00000:00138:2009/02/05 16:12:17.08 kernelpc: 0x40054179 init_dummy+0x373d3109(0x0000000b, 0x40e2d5e8, 0x40e2d668, 0x0000000b, (nil))
00:00000:00138:2009/02/05 16:12:17.08 kernelpc: 0xffffe440 init_dummy+0xf737d3d0(0x4a77fe0c, 0x40e2dad8, 0x40e2dac8, 0x40e2d9c8, (nil))
00:00000:00138:2009/02/05 16:12:17.08 kernelpc: 0x08696474 copy_sqltext+0x1dc(0x093798d0, (nil), (nil), 0xffffffff, 0xffffffff)
01:00000:00069:2009/02/05 16:12:17.08 kernelpc: 0x40054179 init_dummy+0x373d3109(0x0000000b, 0x40b52288, 0x40b52308, 0x0000000b, (nil))
01:00000:00069:2009/02/05 16:12:17.08 kernelpc: 0xffffe440 init_dummy+0xf737d3d0(0x494e7e0c, 0x40b5277c, 0x40b5276c, 0x40b5266c, (nil))
01:00000:00069:2009/02/05 16:12:17.08 kernelpc: 0x08696474 copy_sqltext+0x1dc(0x093798d0, (nil), (nil), 0xffffffff, 0xffffffff)
01:00000:00069:2009/02/05 16:12:17.08 kernel
01:00000:00069:2009/02/05 16:12:17.09 kernelpc: 0x08695c81 sqlpars+0x7f5(0x093798d0, (nil), (nil), 0x081b15d2, 0x093798d0)
00:00000:00138:2009/02/05 16:12:17.08 kernel
00:00000:00138:2009/02/05 16:12:17.08 kernelpc: 0x08695c81 sqlpars+0x7f5(0x093798d0, (nil), (nil), 0x081b15d2, 0x093798d0)
00:00000:00138:2009/02/05 16:12:17.09 kernelpc: 0x081d1954 tdsrecv_language+0x170((nil), (nil), (nil), (nil), (nil))
00:00000:00138:2009/02/05 16:12:17.09 kernel
00:00000:00138:2009/02/05 16:12:17.09 kernel
00:00000:00138:2009/02/05 16:12:17.09 kernel
00:00000:00138:2009/02/05 16:12:17.09 kernelpc: 0x081e1c85 conn_hdlr+0x2c35(0x0000000e, 0x40e2ff34, 0x895eed31, (nil), (nil))
00:00000:00138:2009/02/05 16:12:17.09 kernelpc: 0x088dd63c kpexit((nil), (nil), (nil), 0x408f0900, 0x0000004f)
00:00000:00138:2009/02/05 16:12:17.09 kernelend of stack trace, spid 138, kpid 256966734, suid 1
01:00000:00069:2009/02/05 16:12:17.09 kernelpc: 0x081d1954 tdsrecv_language+0x170((nil), (nil), (nil), (nil), (nil))
01:00000:00069:2009/02/05 16:12:17.09 kernel
01:00000:00069:2009/02/05 16:12:17.09 kernel
01:00000:00069:2009/02/05 16:12:17.09 kernel
01:00000:00069:2009/02/05 16:12:17.09 kernelpc: 0x081e1c85 conn_hdlr+0x2c35(0x0000002b, 0x40b54bd8, 0x895eed31, (nil), (nil))
01:00000:00069:2009/02/05 16:12:17.09 kernelpc: 0x088dd63c kpexit((nil), (nil), (nil), 0x408f0900, 0x00000024)
01:00000:00069:2009/02/05 16:12:17.09 kernelend of stack trace, spid 69, kpid 241172515, suid 1
00:00000:00028:2009/02/05 16:12:24.26 kernelCurrent process (0xf52002a) infected with signal 11 (SIGSEGV)
00:00000:00028:2009/02/05 16:12:24.26 kernelAddress 0x0x085af7f6 (oh_get_obfuscated+0x226), siginfo (code, address) = (2, 0x0xbe833000)
00:00000:00028:2009/02/05 16:12:24.26 kernel************************************
00:00000:00028:2009/02/05 16:12:24.26 kernelSQL causing error : set quoted_identifier on set textsize 2147483647
00:00000:00028:2009/02/05 16:12:24.26 kernel************************************
00:00000:00028:2009/02/05 16:12:24.26 serverSQL Text: set quoted_identifier on set textsize 2147483647
00:00000:00028:2009/02/05 16:12:24.26 kernelcurdb = 1 tempdb = 2 pstat = 0x10000
00:00000:00028:2009/02/05 16:12:24.26 kernellasterror = 0 preverror = 0 transtate = 1
00:00000:00028:2009/02/05 16:12:24.26 kernelcurcmd = 0 program =
00:00000:00028:2009/02/05 16:12:24.26 kernelpc: 0x088ed247 pcstkwalk+0x2b(0x40bc69dc, 0x40bc6798, 0x0000270f, 0x00000002, 0x093798d0)
00:00000:00028:2009/02/05 16:12:24.26 kernelpc: 0x088ed182 ucstkgentrace+0x1b6(0x0f52002a, 0x00000002, 0x0000270f, (nil), (nil))
00:00000:00028:2009/02/05 16:12:24.26 kernelpc: 0x08888b8c ucbacktrace+0xa0((nil), 0x00000001, 0x093798d0, 0x40bc72b4, (nil))
00:00000:00028:2009/02/05 16:12:24.26 kernelpc: 0x0819ce29 terminate_process+0xcb1((nil), 0xffffffff, 0x400567a0, 0x40e2d5d4, 0x0000000b)
00:00000:00028:2009/02/05 16:12:24.26 kernelpc: 0x088b8003 kisignal+0x1ff(0x0000000b, 0x40bc9318, 0x40bc9398, 0xffffffff, 0xffffffff)
00:00000:00028:2009/02/05 16:12:24.26 kernelpc: 0x40054179 init_dummy+0x373d3109(0x0000000b, 0x40bc9318, 0x40bc9398, 0x0000000b, (nil))
00:00000:00028:2009/02/05 16:12:24.26 kernelpc: 0xffffe440 init_dummy+0xf737d3d0(0x4cfd060c, 0x40bc9808, 0x40bc97f8, 0x40bc96f8, (nil))
00:00000:00028:2009/02/05 16:12:24.26 kernelpc: 0x08696474 copy_sqltext+0x1dc(0x093798d0, (nil), (nil), 0xffffffff, 0xffffffff)
00:00000:00028:2009/02/05 16:12:24.26 kernel
00:00000:00028:2009/02/05 16:12:24.26 kernelpc: 0x08695c81 sqlpars+0x7f5(0x093798d0, (nil), (nil), 0x081b15d2, 0x093798d0)
00:00000:00028:2009/02/05 16:12:24.26 kernelpc: 0x081d1954 tdsrecv_language+0x170((nil), (nil), (nil), (nil), (nil))
00:00000:00028:2009/02/05 16:12:24.26 kernel
00:00000:00028:2009/02/05 16:12:24.26 kernel
00:00000:00028:2009/02/05 16:12:24.26 kernel
00:00000:00028:2009/02/05 16:12:24.26 kernelpc: 0x081e1c85 conn_hdlr+0x2c35(0x00000054, 0x40bcbc64, 0x895eed31, (nil), (nil))
00:00000:00028:2009/02/05 16:12:24.26 kernelpc: 0x088dd63c kpexit((nil), (nil), (nil), 0x408f0900, 0x0000002b)
00:00000:00028:2009/02/05 16:12:24.26 kernelend of stack trace, spid 28, kpid 257032234, suid 1
01:00000:00039:2009/02/05 16:12:47.52 kernelCurrent process (0xf53007c) infected with signal 11 (SIGSEGV)
01:00000:00039:2009/02/05 16:12:47.52 kernelAddress 0x0x085af7f6 (oh_get_obfuscated+0x226), siginfo (code, address) = (2, 0x0xbe833000)
01:00000:00039:2009/02/05 16:12:47.52 kernel************************************
01:00000:00039:2009/02/05 16:12:47.52 kernelSQL causing error : ited. This program may also be protected under the copyright
**and trade secret laws of non-U.S. countries.All rights reserved.
**
**
*/
if exists
01:00000:00039:2009/02/05 16:12:47.52 kernel************************************
01:00000:00039:2009/02/05 16:12:47.52 serverSQL Text: ited. This program may also be protected under the copyright
**and trade secret laws of non-U.S. countries.All rights reserved.
**
**
*/
if exists (select *
from master.dbo.sysdatabases
where name = 'sybsystemprocs')
begin
print "Installing sp_patrol_monitor on sybsystemprocs..."
use sybsystemprocs
end
else
begin
print "Installing sp_patrol_monitor on master..."
use master
end
.................
从日志上看出貌似是因为接收到 signal 11 (SIGSEGV)而报错

wind1211 发表于 2009-02-06 18:04

自己顶一下

sybase的troubleshooting 提到了一点，但方法觉的有点够呛
..........
Current process infected with 11
A value of 11 means that the operating system detected a segment violation error.

Sometimes this error occurs in conjunction with stack overflow or data corruption. For more information on stack overflow, refer to Stack Guardword Error.

The message appears in the Adaptive Server error log followed by a stack trace. The SQL causing error or the lasterror displayed in the Server error log may be the underlying cause for this error. But they can also be just the last data Adaptive Server had in its cache space.

In order to identify the lasterror (except in the cases where the lasterror is 0), get the number displayed by Adaptive Server in the lasterror field from the Adaptive Server error log and consult this manual for more information on this error number.

In the following example, the value for lasterror is 614.

00: 94/02/14 11:32:26.02 kernel: current process (0x1fb001d)
infected with 11
00: 94/02/14 11:32:26.07 kernel: Address 0x808a6ef
(closetable+0x2f7), siginfo (code, address) = (2, 0x30)
00: 94/02/14 11:32:26.07 kernel: ************************************
00: 94/02/14 11:32:26.07 kernel: SQL causing
error : CREATE TRIGGER
00: 94/02/14 11:32:26.07 kernel: curdb = 22 pstat = 0x10018 lasterror = 614

Action
In order to correct this error, try to eliminate the lasterror first, as this might be one of the causes for this error (except when lasterror is 0).

Also, try rerunning the command referenced in the SQL causing error to see if the problem reoccurs.

If the process is infected with 11 and the problem can be reproduced, try and correct it as follows:

If the SQL causing error is a compiled object such as a stored procedure, trigger, or view, drop and recreate the object.

If the SQL causing error is ad hoc rather than a compiled object, moving the data may fix the problem. Use one of these options:

Select the table data into a new table, drop the old table, and rename the new table to the old table name.

Bulk copy the affected table out, drop and re-create the table, and bulk copy back in. This is the most efficient solution for a very large table.

If moving the data corrects the problem, the data may have been corrupt. Be aware that moving corrupted data can lead to a data loss.

Check your hardware error log as this error can be caused by hardware failure as well.

Additional information
If this error occurs frequently, contact Sybase Technical Support. It would be useful to have a reproduction case (for example, a query which always causes the "infected" message) before calling Technical Support.

Before calling Technical Support for assistance, have the following available:

Server version and SWR version level

Server error log

Operating system error log

Text of all the error messages

Reproducible case (if possible)

.............

wind1211 发表于 2009-02-06 18:07

补充一下系统环境

SUSE9
Adaptive Server Enterprise/12.5.4/EBF 14926 ESD#7/P/Linux Intel/Enterprise Linux/ase1254/2093/32-bit/OPT/Wed Oct 10 22:41:12 2007

WFCJZ 发表于 2009-02-06 18:22

怎么感觉是你的硬盘问题导致辞的！不敢确定，期待高人吧！

http://wfcjz.gnway.net:8080/chen.swf

camham 发表于 2009-02-10 13:17

错误是否每次创建procedure都出现？
如果不是，建议reboot，对于一般出现进程infected，sybase建议reboot，故障消失

wind1211 发表于 2009-02-10 14:03

不是每次，首次出现的，不清楚为什么会出现。
现在用户不让我们登陆数据库，害怕再次会出现
还有一点就是不知道那三个存储过程有没创建成功

[ 本帖最后由 wind1211 于 2009-2-10 14:05 编辑 ]

wind1211 发表于 2009-02-10 14:19

不清楚和配置文件是否有关

recovery interval in minutes = DEFAULT
print recovery information = DEFAULT
tape retention in days = DEFAULT
max concurrently recovered db = DEFAULT
number of checkpoint tasks = DEFAULT

number of oam trips = DEFAULT
number of index trips = DEFAULT
memory alignment boundary = DEFAULT
global async prefetch limit = DEFAULT
global cache partition number = DEFAULT
extended cache size = DEFAULT

cache size = 828190
cache status = default data cache
cache replacement policy = DEFAULT
local cache partition number = DEFAULT

number of open databases = 20
number of open objects = 1000
open object spinlock ratio = DEFAULT
number of open indexes = 1000
open index hash spinlock ratio = DEFAULT
open index spinlock ratio = DEFAULT
partition groups = DEFAULT
partition spinlock ratio = DEFAULT

disk i/o structures = DEFAULT
number of large i/o buffers = DEFAULT
page utilization percent = DEFAULT
number of devices = 100
disable disk mirroring = DEFAULT
allow sql server async i/o = 1

disable character set conversions = DEFAULT

enable unicode normalization = DEFAULT
enable surrogate processing = DEFAULT
enable unicode conversions = DEFAULT
size of unilib cache = DEFAULT

default network packet size = DEFAULT
max network packet size = DEFAULT
remote server pre-read packets = DEFAULT
number of remote connections = DEFAULT
number of remote logins = DEFAULT
number of remote sites = DEFAULT
max number network listeners = DEFAULT
tcp no delay = 1
send doneinproc tokens = DEFAULT
allow sendmsg = DEFAULT
syb_sendmsg port number = DEFAULT
allow remote access = DEFAULT

max async i/os per engine = DEFAULT
max async i/os per server = DEFAULT

number of worker processes = 4
memory per worker process = DEFAULT
max parallel degree = DEFAULT
max scan parallel degree = DEFAULT

max memory = 1035238
additional network memory = DEFAULT
shared memory starting address = DEFAULT
allocate max shared memory = 1
dynamic allocation on demand = 0
lock shared memory = DEFAULT
heap memory per user = DEFAULT
compression memory size = DEFAULT

max online engines = 4
number of engines at startup = 4
statement cache size = DEFAULT

procedure cache size = 207047
default database size = DEFAULT
identity burning set factor = 1
allow nested triggers = DEFAULT
allow updates to system tables = DEFAULT
default fill factor percent = DEFAULT
default exp_row_size percent = DEFAULT
number of mailboxes = DEFAULT
number of messages = DEFAULT
number of alarms = DEFAULT
number of pre-allocated extents = DEFAULT
event buffers per engine = DEFAULT
cpu accounting flush interval = DEFAULT
i/o accounting flush interval = DEFAULT
sql server clock tick length = DEFAULT
runnable process search count = DEFAULT
i/o polling process count = DEFAULT
time slice = DEFAULT
cpu grace time = 3000
number of sort buffers = DEFAULT
size of auto identity column = DEFAULT
identity grab size = DEFAULT
housekeeper free write percent = DEFAULT
enable housekeeper GC = DEFAULT
allow resource limits = DEFAULT
number of aux scan descriptors = DEFAULT
SQL Perfmon Integration = DEFAULT
allow backward scans = DEFAULT
license information = 100
enable sort-merge join and JTC = DEFAULT
abstract plan load = DEFAULT
abstract plan dump = DEFAULT
abstract plan replace = DEFAULT
abstract plan cache = DEFAULT
text prefetch size = DEFAULT
enable HA = DEFAULT
number of histogram steps = DEFAULT
sampling percent = DEFAULT
i/o batch size = DEFAULT
enable xml = DEFAULT
enable webservices = DEFAULT
enable job scheduler = DEFAULT
job scheduler tasks = DEFAULT
job scheduler interval = DEFAULT
percent database for history = DEFAULT
percent history free = DEFAULT
percent database for output = DEFAULT
percent output free = DEFAULT
maximum job output = DEFAULT

number of user connections = 100
stack size = DEFAULT
stack guard size = DEFAULT
permission cache entries = DEFAULT
user log cache size = DEFAULT
user log cache spinlock ratio = DEFAULT
max native threads per engine = DEFAULT
messaging memory = DEFAULT
enable real time messaging = DEFAULT
histogram tuning factor = DEFAULT
rtm thread idle wait period = DEFAULT

number of locks = 100000
deadlock checking period = DEFAULT
lock spinlock ratio = DEFAULT
lock address spinlock ratio = DEFAULT
lock table spinlock ratio = DEFAULT
lock hashtable size = DEFAULT
lock scheme = DEFAULT
lock wait period = DEFAULT
read committed with lock = DEFAULT
print deadlock information = DEFAULT
deadlock retries = DEFAULT
page lock promotion HWM = DEFAULT
page lock promotion LWM = DEFAULT
page lock promotion PCT = DEFAULT
row lock promotion HWM = DEFAULT
row lock promotion LWM = DEFAULT
row lock promotion PCT = DEFAULT

systemwide password expiration = DEFAULT
audit queue size = DEFAULT
curread change w/ open cursors = DEFAULT
allow procedure grouping = DEFAULT
select on syscomments.text = DEFAULT
auditing = DEFAULT
current audit table = DEFAULT
suspend audit when device full = DEFAULT
enable row level access = DEFAULT
check password for digit = DEFAULT
minimum password length = DEFAULT
maximum failed logins = DEFAULT
enable ssl = DEFAULT
unified login required = DEFAULT
use security services = DEFAULT
msg confidentiality reqd = DEFAULT
msg integrity reqd = DEFAULT
enable pam user auth = DEFAULT
enable ldap user auth = DEFAULT
secure default login = DEFAULT
enable encrypted columns = DEFAULT

esp unload dll = DEFAULT
esp execution priority = DEFAULT
esp execution stacksize = DEFAULT
xp_cmdshell context = DEFAULT
start mail session = DEFAULT

event logging = DEFAULT
log audit logon success = DEFAULT
log audit logon failure = DEFAULT
event log computer name = DEFAULT

enable rep agent threads = DEFAULT

enable cis = DEFAULT
cis connect timeout = DEFAULT
cis bulk insert batch size = DEFAULT
max cis remote connections = DEFAULT
cis packet size = DEFAULT
cis cursor rows = DEFAULT
enable snmp = DEFAULT
enable file access = DEFAULT
cis bulk insert array size = DEFAULT
enable full-text search = DEFAULT
cis rpc handling = DEFAULT

enable java = DEFAULT
size of process object heap = DEFAULT
size of shared class heap = DEFAULT
size of global fixed heap = DEFAULT
number of java sockets = DEFAULT
enable enterprise java beans = DEFAULT

enable DTM = DEFAULT
enable xact coordination = DEFAULT
xact coordination interval = DEFAULT
number of dtx participants = DEFAULT
strict dtm enforcement = DEFAULT
txn to pss ratio = DEFAULT
dtm lock timeout period = DEFAULT
dtm detach timeout period = DEFAULT

dump on conditions = DEFAULT
maximum dump conditions = DEFAULT
number of dump threads = DEFAULT
number of ccbs = DEFAULT
caps per ccb = DEFAULT
average cap size = DEFAULT
engine memory log size = DEFAULT

enable monitoring = DEFAULT
sql text pipe active = DEFAULT
sql text pipe max messages = DEFAULT
plan text pipe active = DEFAULT
plan text pipe max messages = DEFAULT
statement pipe active = DEFAULT
statement pipe max messages = DEFAULT
errorlog pipe active = DEFAULT
errorlog pipe max messages = DEFAULT
deadlock pipe active = DEFAULT
deadlock pipe max messages = DEFAULT
wait event timing = DEFAULT
process wait events = DEFAULT
object lockwait timing = DEFAULT
SQL batch capture = DEFAULT
statement statistics active = DEFAULT
per object statistics active = DEFAULT
max SQL text monitored = DEFAULT
performance monitoring option = DEFAULT
max online Q engines = DEFAULT
number of Q engines at startup = DEFAULT

wind1211 发表于 2009-02-10 15:05

个人觉得会不是因为首先设置sp_configure 'SQL batch capture' ,1时因系统或数据库等限制原因导致失败，而ASE接收到
Current process (0xe600023) infected with signal 11 (SIGSEGV)导致数据库挂起
然后接下来再设置sp_configure 'enable monitoring', 1时也同样失败.
查询了一下只有安装MDA表后，'SQL batch capture和'enable monitoring才有用，不知是否是因为设置上述两个参数引起系统宕库

chuxu 发表于 2009-02-10 16:38

原帖由 wind1211 于 2009-2-10 14:03 发表 http://bbs3.chinaunix.net/images/common/back.gif
不是每次，首次出现的，不清楚为什么会出现。
现在用户不让我们登陆数据库，害怕再次会出现
还有一点就是不知道那三个存储过程有没创建成功

看存储过程是否创建成功，可以在创建存储过程的db中，select* from sysobjects where name = proc_name and type='P'
看一下

wind1211 发表于 2009-02-10 16:47

谢谢chuxu,
现在sa不让我登陆数据库了，也没办法验证了:cry:

奇怪，我在测试库中的master..sysobjects中查询不到
但是是在sybsystemprocs中sp_help可以看到我创建的存储过程

[ 本帖最后由 wind1211 于 2009-2-10 16:58 编辑 ]

页: [1] 2

Chinaunix's Archiver