UR_ACCTINFO (释放)
3) 在sybase中有没有进行数据类型转换的函数
chinaunix.net/cgi-bin/
bbs/topic.cgi?forum=10&;topic=1346&;show=330
四舍五入用round,如round(123.4567,1)=123.5或round(123.4567,0)=123或round(123.67,0)=124
去尾用floor,如floor(123.4567)=123
进尾用ceiling,如ceiling(123.4567)=124
4) 新手问题:为什么我的SYBASE的RUN_BACKUP老是自己DOWN啊!?
chinaunix.net/cgi-bin/bbs/topic.cgi?forum=10&;topic=1335&;show=330
为什么我的SYBASE的RUN_BACKUP老是自己DOWN啊!?
我用NetTerm
登陆运行,但只要一退出NetTerm,BACKUP就自己DOWN了
加&;运行也不行,怎么办啊?
命令前加nohup 试试
那是因为你的backup进程是以你的登录用户起动的,所以当该用户退出unix时,
进程也跟着退出操作
系统了
5) 什么是BYPASS RECOVERY mode?
chinaunix.net/cgi-bin/bbs/topic.cgi?forum=10&;topic=1371&;show=300
在客户端出现提示:
Attempt to BEGIN TRANsaction in database "****" failed because database is in BYPASS RECOVERY mode.
请问如何解决?
select name,status from master..sysdatabases where db_name="你所说的数据库"
看status是否是-32768 ,若是,sysdatabases系统表相应记录的status字段改为0,reboot数据库服务器就可以了。
谢谢各位,
问题已解决。中午去SYBASE网站查找到有关这个问题的详细信息,包括问题成因及解决办法:
Error 3908
Severity
16
Error Message
Attempt to BEGIN TRANsaction in database '%.*s' failed because database is in BYPASS RECOVERY mode.
Explanation
Adaptive Server can start various types of transactions such as local (in response to a local command), internal (for the server's own use), external (started by an external client like a TP Monitor) and subordinate (child transactions started by a parent transaction in parallel).
Bypass recovery starts Adaptive Server without recovering one or more databases. A database in this mode can be accessed even though it is not recovered. You use this mode to allow access to the database for problem analysis, to copy out data, and so on.
Error 3908 is raised when a transaction is attempted while the database is in bypass r
ecovery. Although certain commands are per
missible in this mode, no transactions - regardless of type - can be started when the database is in bypass recovery.
Error 3908 is raised in the following states:
State Meaning
1 Attempted to start a transaction when the database is not available for update. Applies to all possible transaction types.
2 Attempted to start a subordinate transaction when the database is not available for update.
Action
Do not attempt to start a transaction while the database is in bypass recovery. Check if any automated jobs may have submitted a batch job that attempted such a transaction. First restore the database to the original working status it had (prior to bypass status) before attempting any transactions.
Use the following steps to reset the database status:
Note Although a status of zero is usually appropriate, it is not the only possible status value you can use. Reset the database to the actual, normal status it had prior to entering bypass recovery status.
1. Reset the database status to 0:
1>; sp_configure "allow updates", 1
2>; go
1>; begin tran
2>; go
1>; use master
2>; go
1>; update sysdatabases set status=0 where name=
;
2>; go
Check that the above update command affected only one row (if more than one row was affected, issue a rollback transaction.) Then commit the tr