關(guān)于startserver顯示的項目內(nèi)容

aokzhu

使用startserver顯示出的內(nèi)容中有TTY一項，該項的含義是什么意思�。�
如果有值顯示為 "pts/6"，是否正常，其他數(shù)據(jù)庫的值都為"?" 。

另、今天創(chuàng)建SERVER時，backup數(shù)據(jù)庫沒有創(chuàng)建成功，于是想使用手工進(jìn)行創(chuàng)建，
以下操作是否正確？
  1. 創(chuàng)建RUN_DB_back的文件，內(nèi)容參考其他bakcup的內(nèi)容；
  2. interfaces文件中追加RUN_DB_back的信息；
  3. 使用sp_addserver 將DB_back添加到DB數(shù)據(jù)庫中；
  4. load數(shù)據(jù)；

還有沒有其他更好的辦法來創(chuàng)建backup數(shù)據(jù)庫��？

wfcjz

創(chuàng)建不成功的錯誤日志貼出來!看看是什么原因創(chuàng)建不成功

chuxu

TTY的意思和你用ps 看的含義一樣，只這個進(jìn)程啟動在哪個終端上，至于帶？也是正常的。
手工創(chuàng)建backup，應(yīng)該執(zhí)行了1，修改好RUN_DB_back后，執(zhí)行srvbuildres -f RUN_DB_back
就可以了。后面的2，3不用手工做。
等備份服務(wù)器起來之后，才能執(zhí)行l(wèi)oad

andkylee

TTY的意思和你用ps 看的含義一樣，只這個進(jìn)程啟動在哪個終端上，至于帶？也是正常的。
手工創(chuàng)建backup，應(yīng) ...
chuxu 發(fā)表于 2010-02-03 09:36

修改一下！
    手工創(chuàng)建backup,也就是用資源文件創(chuàng)建備份服務(wù)器。應(yīng)該用srvbuildres -r srvbuild.backup_server.rs
srvbuildres實用程序的命令語法：
---------------------------------------------------------------------------------------------------------------
-bash-3.00$ srvbuildres --help
Usage: srvbuildres [-s <Sybase Dir>] [-I <Interfaces file>] [-r <Resource file>] [-v]
---------------------------------------------------------------------------------------------------------------

啟動備份服務(wù)的話，可以手動啟動:startserver -f RUN_DB_back
---------------------------------------------------------------------------------------------------------------
-bash-3.00$ startserver --help
usage: startserver [-f RUN_name1 [-m]] [-f RUN_name2 [-m]]...
---------------------------------------------------------------------------------------------------------------

aokzhu

回復(fù) 4# andkylee


    謝謝andkylee，昨天客戶催得急，把數(shù)據(jù)庫重建創(chuàng)建了（教育庫），數(shù)據(jù)總算是load成功了。

   但，今天load其他日期的數(shù)據(jù)庫時，由于沒有啟動backup數(shù)據(jù)庫，load出現(xiàn)錯誤后，用戶數(shù)據(jù)庫就被標(biāo)記為suspect（可疑）狀態(tài)了。
   該怎么恢復(fù)該狀態(tài)�。繌木W(wǎng)上參考了一下操作辦法，但還是沒辦法成功修改。。。

   大家有何有效的方法��？

wfcjz

suspect（可疑）狀態(tài),你可以看日志,如果不出意外,應(yīng)該報926錯誤,

ahjf

還是先看一下日志，找到原因后處理吧，sybooks里面有處理辦法的

andkylee

回復(fù)  andkylee


    謝謝andkylee，昨天客戶催得急，把數(shù)據(jù)庫重建創(chuàng)建了（教育庫），數(shù)據(jù)總算是load成 ...
aokzhu 發(fā)表于 2010-02-03 11:31

【 由于沒有啟動backup數(shù)據(jù)庫，load出現(xiàn)錯誤后，用戶數(shù)據(jù)庫就被標(biāo)記為】

懷疑中。。。
   
backup服務(wù)沒有啟動，你在load數(shù)據(jù)庫的時候會提示你沒有啟動備份服務(wù)。相應(yīng)的你load的數(shù)據(jù)庫不應(yīng)該被置疑。都沒開始往里面寫數(shù)據(jù)，何來suspect？

sunlan

你不能用srvbuild或srvbuildres來創(chuàng)建backup server嗎？

aokzhu

回復(fù) 8# andkylee


    對load數(shù)據(jù)時沒有啟動backup服務(wù)，導(dǎo)致數(shù)據(jù)庫被標(biāo)記為可疑狀態(tài)，我也很不解。
   因為以前如果沒有啟動backup服務(wù)的話，只是提示信息，啟動backup服務(wù)后，就可以正常接著load數(shù)據(jù)了。
   但昨天數(shù)據(jù)庫卻被標(biāo)記為suspect狀態(tài)，可能也有其他原因?qū)е碌摹?br />
   以下是啟動數(shù)據(jù)庫時的log，請大家?guī)兔υ\斷下：

  00:00000:00001:2010/02/03 08:59:27.62 server  Loaded default Unilib conversion handle.
00:00000:00007:2010/02/03 09:09:09.90 server  Configuration file '/raid5/sybase/MINIDB.cfg' has been written and the previous version has been renamed to '/raid5/sybase/MINIDB.111'.
00:00000:00007:2010/02/03 09:09:09.90 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '1' to '1'.
00:00000:00007:2010/02/03 09:11:16.69 server  Configuration file '/raid5/sybase/MINIDB.cfg' has been written and the previous version has been renamed to '/raid5/sybase/MINIDB.112'.
00:00000:00007:2010/02/03 09:11:16.69 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '1' to '0'.
00:00000:00010:2010/02/03 17:17:25.82 server  Process id 7 killed by Hostname gpymacdb, Host process id 19349.
00:00000:00011:2010/02/03 17:19:06.41 server  Shutdown with nowait detected - SQL Server process level execution bindings will be cleared on startup.
00:00000:00011:2010/02/03 17:19:06.42 server  SQL Server shutdown by request.
00:00000:00011:2010/02/03 17:19:06.42 kernel  ueshutdown: exiting
00:00000:00000:2010/02/03 17:19:39.24 kernel  Max fd 65536 exceeds internal limit of 10000
00:00000:00000:2010/02/03 17:19:39.24 kernel  Max fd 65536 exceeds internal limit of 10000
00:00000:00000:2010/02/03 17:19:39.25 kernel  Using config area from primary master device.
00:00000:00000:2010/02/03 17:19:39.26 kernel  Warning: Using default file '/raid5/sybase/MINIDB.cfg' since a configuration file was not specified. Specify a configuration file name in the RUNSERVER file to avoid this message.
00:00000:00000:2010/02/03 17:19:39.26 kernel  Max fd 65536 exceeds internal limit of 10000
00:00000:00000:2010/02/03 17:19:39.26 kernel  Max fd 65536 exceeds internal limit of 10000
00:00000:00000:2010/02/03 17:19:39.26 kernel  Max fd 65536 exceeds internal limit of 10000
00:00000:00000:2010/02/03 17:19:39.26 kernel  Max fd 65536 exceeds internal limit of 10000
00:00000:00000:2010/02/03 17:19:44.11 kernel  Max fd 65536 exceeds internal limit of 10000
00:00000:00000:2010/02/03 17:19:44.11 kernel  Using 10000 file descriptors.
00:00000:00000:2010/02/03 17:19:44.11 kernel  Adaptive Server Enterprise/11.9.2.4/1165/P/SWR 9434 INSTRUMENTED/Sun_svr4/OS 5.5.1/FBO/Tue Dec 26 02:34:20 2000
00:00000:00000:2010/02/03 17:19:44.11 kernel  Confidential property of Sybase, Inc.
00:00000:00000:2010/02/03 17:19:44.11 kernel  Copyright 1987, 2000
00:00000:00000:2010/02/03 17:19:44.11 kernel  Sybase, Inc.  All rights reserved.
00:00000:00000:2010/02/03 17:19:44.11 kernel  Unpublished rights reserved under U.S. copyright laws.
00:00000:00000:2010/02/03 17:19:44.11 kernel  
00:00000:00000:2010/02/03 17:19:44.11 kernel  This software contains confidential and trade secret information of Sybase,
00:00000:00000:2010/02/03 17:19:44.11 kernel  Inc.   Use,  duplication or disclosure of the software and documentation by
00:00000:00000:2010/02/03 17:19:44.11 kernel  the  U.S.  Government  is  subject  to  restrictions set forth in a license
00:00000:00000:2010/02/03 17:19:44.11 kernel  agreement  between  the  Government  and  Sybase,  Inc.  or  other  written
00:00000:00000:2010/02/03 17:19:44.11 kernel  agreement  specifying  the  Government's rights to use the software and any
00:00000:00000:2010/02/03 17:19:44.11 kernel  applicable FAR provisions, for example, FAR 52.227-19.
00:00000:00000:2010/02/03 17:19:44.11 kernel  Sybase, Inc. 6475 Christie Avenue, Emeryville, CA 94608, USA
00:00000:00000:2010/02/03 17:19:44.11 kernel  Using '/raid5/sybase/MINIDB.cfg' for configuration information.
00:00000:00000:2010/02/03 17:19:44.11 kernel  Logging SQL Server messages in file '/raid5/sybase/mini/MINIDB.log'.
00:00000:00000:2010/02/03 17:19:44.15 kernel  kdcl_init: connectivity library supports master/query syntax
00:00000:00000:2010/02/03 17:19:44.15 kernel  Directory Control Layer (DCL) using directory driver: InterfacesDriver
00:00000:00000:2010/02/03 17:19:44.15 kernel  Network and device connection limit is 9990.
00:00000:00000:2010/02/03 17:19:44.24 server  Number of proc buffers allocated: 402758.
00:00000:00000:2010/02/03 17:19:44.34 server  Proc header memory allocated 201379 pages for each per engine cache
00:00000:00000:2010/02/03 17:19:44.35 server  Number of blocks left for proc headers: 403238.
00:00000:00000:2010/02/03 17:19:44.35 server  Memory allocated for the default data cache cache: 3033656 Kb
00:00000:00000:2010/02/03 17:19:44.92 server  Size of the 2K memory pool: 3033652 Kb
00:00000:00000:2010/02/03 17:19:44.94 kernel  Initializing virtual device 0, '/raid5/sybase/mini/master.dat'
00:00000:00000:2010/02/03 17:19:44.94 kernel  Virtual device 0 started using standard unix i/o.
00:00000:00000:2010/02/03 17:19:44.94 kernel  Worker Thread Manager is not enabled for use in SQL Server.
00:00000:00000:2010/02/03 17:19:44.94 kernel  Either the config parameter 'use security services' is set to 0, or ASE does not support use of external security mechanisms on this platform. The Security Control Layer will not be initialized. No external security mechanisms will be supported.
00:00000:00000:2010/02/03 17:19:44.94 kernel  engine 0, os pid 19403  online
00:00000:00000:2010/02/03 17:19:44.94 server  No active traceflags
00:00000:00001:2010/02/03 17:19:44.94 kernel  Component Integration Services loaded; version 'Component Integration Services/11.9.2.4/1165/P/SWR 9434 INSTRUMENTED/Sun_svr4/OS 5.5.1/FBO/Tue Dec 26 02:34:20 2000'.
00:00000:00001:2010/02/03 17:19:44.94 kernel  Component Integration Services: using 'Sybase Client-Library/11.1.1/P-EBF9284/sun_svr4/SPARC Solaris 2.5.1/1/OPT/Fri Sep 29 19:44:56 2000'
00:00000:00001:2010/02/03 17:19:44.94 server  Opening Master Database ...
00:00000:00001:2010/02/03 17:19:45.00 server  Loading SQL Server's default sort order and character set
00:00000:00002:2010/02/03 17:19:45.01 kernel  ninit:0: listener type: master
00:00000:00002:2010/02/03 17:19:45.01 kernel  ninit:0: listener endpoint: /dev/tcp
00:00000:00002:2010/02/03 17:19:45.01 kernel  ninit:0: listener raw address: \x00020c1cac1738010000000000000000
00:00000:00002:2010/02/03 17:19:45.01 kernel  ninit:0: transport provider: T_COTS_ORD
00:00000:00001:2010/02/03 17:19:45.02 server  Recovering database 'master'
00:00000:00001:2010/02/03 17:19:45.04 server  Redo pass of recovery has processed 1 committed and 0 aborted transactions.
00:00000:00001:2010/02/03 17:19:46.06 server  Checking external objects.
00:00000:00001:2010/02/03 17:19:46.08 server  Database 'master' is now online.
00:00000:00001:2010/02/03 17:19:46.08 server  The transaction log in the database 'master' will use I/O size of 2 Kb.
00:00000:00001:2010/02/03 17:19:46.81 server  0 dump conditions detected at boot time
00:00000:00001:2010/02/03 17:19:46.81 server  server is unnamed
00:00000:00001:2010/02/03 17:19:46.81 server  Activating disk 'ciimlog1'.
00:00000:00001:2010/02/03 17:19:46.81 kernel  Initializing virtual device 2, '/raid5/sybase/mini/ciimlog1.dat'
00:00000:00001:2010/02/03 17:19:46.81 kernel  Virtual device 2 started using standard unix i/o.
00:00000:00001:2010/02/03 17:19:46.81 server  Activating disk 'ciimlog2'.
00:00000:00001:2010/02/03 17:19:46.81 kernel  Initializing virtual device 3, '/raid5/sybase/mini/ciimlog2.dat'
00:00000:00001:2010/02/03 17:19:46.81 kernel  Virtual device 3 started using standard unix i/o.
00:00000:00001:2010/02/03 17:19:46.82 server  Activating disk 'ciimlog3'.
00:00000:00001:2010/02/03 17:19:46.82 kernel  Initializing virtual device 4, '/raid5/sybase/mini/ciimlog3.dat'
00:00000:00001:2010/02/03 17:19:46.82 kernel  Virtual device 4 started using standard unix i/o.
00:00000:00001:2010/02/03 17:19:46.82 server  Activating disk 'datadev1'.
00:00000:00001:2010/02/03 17:19:46.82 kernel  Initializing virtual device 5, '/raid5/sybase/mini/datadev1.dat'
00:00000:00001:2010/02/03 17:19:46.82 kernel  Virtual device 5 started using standard unix i/o.
00:00000:00001:2010/02/03 17:19:46.82 server  Activating disk 'datadev10'.
00:00000:00001:2010/02/03 17:19:46.82 kernel  Initializing virtual device 14, '/raid5/sybase/mini/datadev10.dat'
00:00000:00001:2010/02/03 17:19:46.82 kernel  Virtual device 14 started using standard unix i/o.
00:00000:00001:2010/02/03 17:19:46.82 server  Activating disk 'datadev11'.
00:00000:00001:2010/02/03 17:19:46.82 kernel  Initializing virtual device 15, '/raid5/sybase/mini/datadev11.dat'
00:00000:00001:2010/02/03 17:19:46.82 kernel  Virtual device 15 started using standard unix i/o.
00:00000:00001:2010/02/03 17:19:46.82 server  Activating disk 'datadev12'.
00:00000:00001:2010/02/03 17:19:46.82 kernel  Initializing virtual device 16, '/raid5/sybase/mini/datadev12.dat'
00:00000:00001:2010/02/03 17:19:46.82 kernel  Virtual device 16 started using standard unix i/o.
00:00000:00001:2010/02/03 17:19:46.82 server  Activating disk 'datadev2'.
00:00000:00001:2010/02/03 17:19:46.82 kernel  Initializing virtual device 6, '/raid5/sybase/mini/datadev2.dat'
00:00000:00001:2010/02/03 17:19:46.82 kernel  Virtual device 6 started using standard unix i/o.
00:00000:00001:2010/02/03 17:19:46.82 server  Activating disk 'datadev3'.
00:00000:00001:2010/02/03 17:19:46.82 kernel  Initializing virtual device 7, '/raid5/sybase/mini/datadev3.dat'
00:00000:00001:2010/02/03 17:19:46.82 kernel  Virtual device 7 started using standard unix i/o.
00:00000:00001:2010/02/03 17:19:46.82 server  Activating disk 'datadev4'.
00:00000:00001:2010/02/03 17:19:46.82 kernel  Initializing virtual device 8, '/raid5/sybase/mini/datadev4.dat'
00:00000:00001:2010/02/03 17:19:46.82 kernel  Virtual device 8 started using standard unix i/o.
00:00000:00001:2010/02/03 17:19:46.82 server  Activating disk 'datadev5'.
00:00000:00001:2010/02/03 17:19:46.82 kernel  Initializing virtual device 9, '/raid5/sybase/mini/datadev5.dat'
00:00000:00001:2010/02/03 17:19:46.82 kernel  Virtual device 9 started using standard unix i/o.
00:00000:00001:2010/02/03 17:19:46.82 server  Activating disk 'datadev6'.
00:00000:00001:2010/02/03 17:19:46.82 kernel  Initializing virtual device 10, '/raid5/sybase/mini/datadev6.dat'
00:00000:00001:2010/02/03 17:19:46.82 kernel  Virtual device 10 started using standard unix i/o.
00:00000:00001:2010/02/03 17:19:46.82 server  Activating disk 'datadev7'.
00:00000:00001:2010/02/03 17:19:46.82 kernel  Initializing virtual device 11, '/raid5/sybase/mini/datadev7.dat'
00:00000:00001:2010/02/03 17:19:46.82 kernel  Virtual device 11 started using standard unix i/o.
00:00000:00001:2010/02/03 17:19:46.82 server  Activating disk 'datadev8'.
00:00000:00001:2010/02/03 17:19:46.82 kernel  Initializing virtual device 12, '/raid5/sybase/mini/datadev8.dat'
00:00000:00001:2010/02/03 17:19:46.82 kernel  Virtual device 12 started using standard unix i/o.
00:00000:00001:2010/02/03 17:19:46.82 server  Activating disk 'datadev9'.
00:00000:00001:2010/02/03 17:19:46.82 kernel  Initializing virtual device 13, '/raid5/sybase/mini/datadev9.dat'
00:00000:00001:2010/02/03 17:19:46.82 kernel  Virtual device 13 started using standard unix i/o.
00:00000:00001:2010/02/03 17:19:46.82 server  Activating disk 'sysprocsdev'.
00:00000:00001:2010/02/03 17:19:46.82 kernel  Initializing virtual device 1, '/raid5/sybase/mini/sybprocs.dat'
00:00000:00001:2010/02/03 17:19:46.82 kernel  Virtual device 1 started using standard unix i/o.
00:00000:00001:2010/02/03 17:19:46.82 server  Activating disk 'tempdev'.
00:00000:00001:2010/02/03 17:19:46.82 kernel  Initializing virtual device 17, '/raid5/sybase/mini/tempdev.dat'
00:00000:00001:2010/02/03 17:19:46.82 kernel  Virtual device 17 started using standard unix i/o.
00:00000:00001:2010/02/03 17:19:46.84 server  Recovering database 'model'.
00:00000:00001:2010/02/03 17:19:47.60 server  Checking external objects.
00:00000:00001:2010/02/03 17:19:47.60 server  The transaction log in the database 'model' will use I/O size of 2 Kb.
00:00000:00001:2010/02/03 17:19:48.36 server  Database 'model' is now online.
00:00000:00001:2010/02/03 17:19:48.36 server  Clearing temp db
00:00000:00001:2010/02/03 17:19:49.49 server  The transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2010/02/03 17:19:50.24 server  The transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2010/02/03 17:19:51.01 server  Database 'tempdb' is now online.
00:00000:00001:2010/02/03 17:19:51.01 server  The transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2010/02/03 17:19:51.72 server  Recovering database 'sybsystemprocs'.
00:00000:00001:2010/02/03 17:19:52.59 server  Checking external objects.
00:00000:00001:2010/02/03 17:19:52.59 server  The transaction log in the database 'sybsystemprocs' will use I/O size of 2 Kb.
00:00000:00001:2010/02/03 17:19:53.35 server  Database 'sybsystemprocs' is now online.
00:00000:00001:2010/02/03 17:19:53.37 server  Error: 8211, Severity: 26, State: 1
00:00000:00001:2010/02/03 17:19:53.37 server  Mismatch found between the name and id descriptor hash table. Descriptor hashed by name = 0x0 and hashed by id = 0x11837618.
00:00000:00001:2010/02/03 17:19:53.78 server  Error: 834, Severity: 20, State: 4
00:00000:00001:2010/02/03 17:19:53.78 server  Illegal attempt to clean buffer: BUF pointer = '0xdfc753c', MASS pointer = '0xdfc753c', (Buf#: '0'), page ptr = '0xfdbda800', dbid = '5', Mass virtpage = '31754', Buffer page = '6', Mass status = '0x1008', Buffer status = '0x1', size = '2048', cache (id: 0) = 'default data cache'.
00:00000:00001:2010/02/03 17:19:53.78 server  Unable to proceed with the recovery of dbid <5> because of previous errors.  Continuing with the next database.
00:00000:00001:2010/02/03 17:19:53.78 server  Recovery complete.
00:00000:00001:2010/02/03 17:19:53.78 server  SQL Server's default sort order is:
00:00000:00001:2010/02/03 17:19:53.78 server          'bin_iso_1' (ID = 50)
00:00000:00001:2010/02/03 17:19:53.78 server  on top of default character set:
00:00000:00001:2010/02/03 17:19:53.78 server          'iso_1' (ID = 1).
00:00000:00001:2010/02/03 17:19:53.78 server  Loaded default Unilib conversion handle.
00:00000:00007:2010/02/04 10:26:12.42 server  Configuration file '/raid5/sybase/MINIDB.cfg' has been written and the previous version has been renamed to '/raid5/sybase/MINIDB.113'.
00:00000:00007:2010/02/04 10:26:12.43 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '0' to '1'.