SYBASE補丁安裝指南

Blackrose

一.        確認當前SYBASE ASE服務器版本：
1．        用isql登入Server，使用如下命令獲知當前Server版本號：
select @@version
例：Adaptive Server Enterprise/11.9.2.5/1234/P/SWR 9676 ESD 1/RS6000/AIX 4.2.1/FBO/Tue Jul 24 04:43:25 2001
可以看到當前Server的版本號為11.9.2.5,目前補丁號為SWR后的數字 9676 ESD 1,平臺為RS6000,操作系統為 AIX4.2.1。
2．        在Unix環(huán)境中可以使用如下命令:
cd $SYBASE
cd bin(如為12版本，則為cd ASE-12_0/bin)
./dataserver –v
可以得到如1同樣的版本輸出結果

二.        下載補丁
補丁可以從SYBASE的門戶網站獲得。
1.        網址為www.sybase.com
2.        點擊download鏈接
3.        點擊EBFs / Updates
4.        輸入已注冊的合法用戶和口令，如果沒有，可以點擊create a new account創(chuàng)建一個新的下載賬號后再行登錄。
5.        登錄后成功后，將能看見一個Product Families的產品列表，從中選擇需要下載補丁的產品類型（如Adaptive Server Enterprise）
6.        選擇Adaptive Server Enterprise后，會顯示不同平臺，不同操作系統版本的可下載補丁列表。根據實際情況選擇相應的平臺、操作系統版本（特別是操作系統是32位還是64位）及SYBASE數據庫服務器版本，點擊下載鏈接。如果有疑問，可以先通過察看補丁文件鏈接前的info鏈接中的說明文件了解補丁信息
7.        同意SYBASE軟件下載協議的條款
8.        下載（下載過程中不要關閉網頁，否則Cookie將過期，導致下在中斷）

三.        補丁安裝
基于不同平臺不同操作系統，補丁的文件類型可能有不同，一般為ZIP(NT),TGZ(UNIX),TAR(UNIX)，安裝補丁的方法也因而有所不同。
1．        全備份SYBASE數據庫。包括用戶數據庫及master數據庫。如果有條件，還可以將用戶庫數據使用bcp工具進行備份，以預防數據庫本身已存在的故障導致load失敗。
2．        關閉所有的SYBASE服務器，包括數據庫服務器，備份服務器，監(jiān)控服務器等，關閉所有SYBASE的應用程序，包括isql(DOS)、wisql(ver10)、SQL Advantage(ver11.5以上)、jisql(ver12)、SYBASE CENTRAL，SQLEDIT(ver10)、DSEDIT(ver11以上)，還包括等所有使用的SYBASE系統文件的應用程序，包括數據庫應用系統及開發(fā)環(huán)境等。
3．        備份SYBASE原安裝目錄，如/usr/Sybase(UNIX)或者是c:\sybase(WINNT)。
4．        安裝補丁（解包）
UNIX：
a.        將下載得到的補丁通過網絡使用ftp或者其他方式拷貝到需安裝補丁的主機上
b.        如果下載的補丁為tgz格式，使用操作系統下適當的命令進行解壓縮得到類型為tar的打包文件，如gunzip,unzip等，具體命令格式見操作系統的管理員手冊。如為WINNT環(huán)境，此步略過。
c.       
UNIX平臺：
將解壓縮得到的tar文件拷貝到SYBASE產品的安裝目錄下，使用如下命令格式進行解包，對SYBASE文件進行覆蓋實現文件替換，達到安裝補丁的目的：
tar –xvf EBFxxxx
其中xxxx為補丁號，如9299。關于tar命令的使用請詳見操作系統命令指南
WINNT平臺:
將下載得到的zip文件拷貝到SYBASE產品的安裝目錄下，使用winzip或者其他解壓縮工具解包到當前目錄，對SYBASE文件進行覆蓋實現文件替換，達到安裝補丁的目的。解壓縮過程中應該有文件覆蓋的提示信息。

d.        解包成功后在SYBASE安裝目錄下將看到文件名如Cover.ROLL.xxxx的說明文件（xxxx為補丁號），此文件中詳細的說明了補丁包含文件內容、安裝的詳細操作步驟以及補丁對那些BUG進行了修正等，請使用文本閱讀器打開此文件仔細閱讀。
e.        驗證是否補丁文件正確安裝：
進入SYBASE安裝目錄下dataserver(Unix)/sqlsrvr(Nt)所在的目錄察看版本信息
cd $sybase 進入Sybase ASE 安裝目錄
cd ASE-12_0/bin[12版本以上](或者cd bin[1192版本以下])
./dataserver –v(Unix)
sqlsrvr –v（Nt）
在顯示的版本信息中應該可以看到所安裝的補丁信息，如
Adaptive Server Enterprise/11.9.2.5/1234/P/SWR 9676 ESD 1/RS6000/AIX 4.2.1/FBO/Tue Jul 24 04:43:25 2001
中的9676 ESD 1信息。如果沒有看到，則說明補丁解包過程中的覆蓋有問題，請檢查解包路徑，目錄大小寫等相關問題，之后重新解包，直到安裝正確。
f.        啟動SYBASE各服務器，注意監(jiān)控啟動過程中的啟動信息，察看是否有警告，錯誤等信息，察看服務器是否能夠正常啟動和使用。
g.        根據不同的補丁需求，可能此后操作步驟稍有不同：
一般情況下，需要對SYBASE的系統存儲過程及系統提示信息進行更新。是否需要執(zhí)行更新，根據Cover.ROLL.xxxx中的說明。
cd $SYBASE/scripts(12版本為cd $SYBASE/ASE-12_0/scripts)
isql –Usa –Ppasswd -i installmaster
isql –Usa –Ppasswd -i instmsgs.ebf
如在此過程中出現意外中斷（停電等），請在故障排除后保證此過程重新順利完成，以免留下隱患。
至此。補丁安裝順利完成，對應用系統進行全面的測試。





附錄
出 錯 處 理

如果在安裝補丁過程中出現故障，根據不同的錯誤程度和故障原因有不同的處理辦法。在最壞情況下，可按照下面的方法進行數據庫系統恢復:
1．        關閉所有數據庫服務器，如果它處于運行狀態(tài)
2．        關閉所有SYBASE應用程序和工具
3．        恢復原SYBASE安裝文件的備份目錄
4．        重新啟動老版本SYBASE，并將原數據庫備份進行l(wèi)oad恢復
5．        確定出錯原因，下載正確補丁或者更新補丁進行安裝

jazy

很好！


我想，這時很多人需要的，置為精華先！

rabbitdan

請問blackrose大俠：
    我在solaris下安裝了ASE12。5 但是在建一個服務的時候總是
失敗，我找不到問題的所在。詳細的過程如下。
我的pagesize＝8k
$ srvbuildres -r sql.rs
srvbuildres: Building Adaptive Server 'jcweb':
srvbuildres: Writing entry into directory services...
srvbuildres: Directory services entry complete.
srvbuildres: Building master device...
srvbuildres: Master device complete.
srvbuildres: Writing RUN_jcweb file...
srvbuildres: RUN_jcweb file complete.
srvbuildres: Starting server...
srvbuildres: Task failed
srvbuildres: Unable to boot server 'jcweb'.  
srvbuildres: Server 'jcweb' was not created.


我的日志文件有錯誤的記載如下：
00:00000:00001:2003/02/24 11:22:45.08 server  Database 'tempdb' is now online.
00:00000:00002:2003/02/24 11:22:45.09 kernel  ninit:0: listener type: master
00:00000:00002:2003/02/24 11:22:45.09 kernel  ninit:0: listener endpoint: /dev/tcp
00:00000:00002:2003/02/24 11:22:45.09 kernel  ninit:0: listener raw address: \x00021172c0a810050000000000000000
00:00000:00002:2003/02/24 11:22:45.09 kernel  ninit:0: transport provider: T_COTS_ORD
00:00000:00002:2003/02/24 11:22:45.09 kernel  ninit: t_bind, No Error
00:00000:00002:2003/02/24 11:22:45.09 kernel  ninit: All master network listeners have failed.  Shutting down.
00:00000:00002:2003/02/24 11:22:45.09 kernel  ueshutdown: exiting

整個日志文件如下：

00:00000:00000:2003/02/24 11:19:54.06 kernel  Use license file /export/home/sybase/SYSAM-1_0/licenses/license.d
at.
00:00000:00000:2003/02/24 11:19:54.06 kernel  Checked out license ASE_SERVER
00:00000:00000:2003/02/24 11:19:54.11 kernel  Using config area from primary master device.
00:00000:00000:2003/02/24 11:19:54.13 kernel  Warning: Using default file '/export/home/sybase/jcweb.cfg' since
a configuration file was not specified. Specify a configuration file name in the RUNSERVER file to avoid this
message.
00:00000:00000:2003/02/24 11:19:54.33 kernel  Using 1024 file descriptors.
00:00000:00000:2003/02/24 11:19:54.33 kernel  Adaptive Server Enterprise/12.5/SWR 9610 GA/P/Sun_svr4/OS 5.8/mai
n/1647/64-bit/FBO/Sat Jun  2 01:55:25 2001
00:00000:00000:2003/02/24 11:19:54.33 kernel  Confidential property of Sybase, Inc.
00:00000:00000:2003/02/24 11:19:54.33 kernel  Copyright 1987, 2001
00:00000:00000:2003/02/24 11:19:54.33 kernel  Sybase, Inc.  All rights reserved.
00:00000:00000:2003/02/24 11:19:54.33 kernel  Unpublished rights reserved under U.S. copyright laws.
00:00000:00000:2003/02/24 11:19:54.33 kernel  
00:00000:00000:2003/02/24 11:19:54.33 kernel  This software contains confidential and trade secret information
of Sybase,
00:00000:00000:2003/02/24 11:19:54.33 kernel  Inc.   Use,  duplication or disclosure of the software and docume
ntation by
00:00000:00000:2003/02/24 11:19:54.33 kernel  the  U.S.  Government  is  subject  to  restrictions set forth in
a license
00:00000:00000:2003/02/24 11:19:54.33 kernel  agreement  between  the  Government  and  Sybase,  Inc.  or  othe
r  written
00:00000:00000:2003/02/24 11:19:54.33 kernel  agreement  specifying  the  Government's rights to use the softwa
re and any
00:00000:00000:2003/02/24 11:19:54.33 kernel  applicable FAR provisions, for example, FAR 52.227-19.
00:00000:00000:2003/02/24 11:19:54.33 kernel  Sybase, Inc. 6475 Christie Avenue, Emeryville, CA 94608, USA
00:00000:00000:2003/02/24 11:19:54.33 kernel  Using '/export/home/sybase/jcweb.cfg' for configuration informati
on.
00:00000:00000:2003/02/24 11:19:54.33 kernel  Logging ASE messages in file '/export/home/sybase/ASE-12_5/instal
l/jcweb.log'.
00:00000:00000:2003/02/24 11:19:54.37 kernel  kdcl_sess_open: connectivity library supports master/query syntax
.
00:00000:00000:2003/02/24 11:19:54.38 kernel  Directory Control Layer (DCL) using directory driver: InterfacesD
river
00:00000:00000:2003/02/24 11:19:54.38 kernel  SSL Plus security modules loaded successfully.
00:00000:00000:2003/02/24 11:19:54.38 kernel  Network and device connection limit is 1014.
00:00000:00000:2003/02/24 11:19:54.56 server  Number of blocks left for proc headers: 3192.
00:00000:00000:2003/02/24 11:19:54.57 server  Proc header memory allocated 1596 pages for each per engine cache
00:00000:00000:2003/02/24 11:19:54.60 server  Memory allocated for the default data cache cachelet 1: 8192 Kb
00:00000:00000:2003/02/24 11:19:54.60 server  Size of the 8K memory pool: 8192 Kb
00:00000:00000:2003/02/24 11:19:54.60 kernel  Enabling Sun Kernel asynchronous disk I/O strategy
00:00000:00000:2003/02/24 11:19:54.60 kernel  Initializing virtual device 0, '/databasefile/jcweb/db/master.dat
' with dsync 'on'.
00:00000:00000:2003/02/24 11:19:54.60 kernel  Virtual device 0 started using asynchronous i/o.
00:00000:00000:2003/02/24 11:19:54.60 kernel  Worker Thread Manager is not enabled for use in SQL Server.
00:00000:00000:2003/02/24 11:19:54.60 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 n
ot be initialized. No external security mechanisms will be supported.
00:00000:00000:2003/02/24 11:19:54.60 kernel  engine 0, os pid 550  online
00:00000:00000:2003/02/24 11:19:54.60 server  No active traceflags
00:00000:00001:2003/02/24 11:19:54.61 kernel  libomni1 - Component Integration Services loaded; version 'libomn
i1 - Component Integration Services/12.5/SWR 9610 GA/P/Sun_svr4/OS 5.8/main/1647/64-bit/FBO/Sat Jun  2 01:55:25
2001'.
00:00000:00001:2003/02/24 11:19:54.61 kernel  libomni1 - Component Integration Services: using 'Sybase Client-L
ibrary/12.5/P/SPARC/Solaris 2.8/1/64bit/OPT/Sun Mar 25 08:30:37 2001'
00:00000:00001:2003/02/24 11:19:54.61 server  The logical pagesize of the server is 8 Kb.
00:00000:00001:2003/02/24 11:19:54.61 server  Database 'master' appears to be at an older revision than the pre
sent installation; SQL Server will assess it, and upgrade it as required.
00:00000:00001:2003/02/24 11:19:54.63 server  Database 'master': beginning upgrade step [ID     1]: Initialize
disk and create empty allocation units on master device.
00:00000:00001:2003/02/24 11:21:09.43 server  Database 'master': beginning upgrade step [ID     2]: Bootstrap b
asic system catalogs in database.
00:00000:00001:2003/02/24 11:21:09.78 server  Database 'master': beginning upgrade step [ID     3]: creating in
dex (table systypes, index ncsystypes)
00:00000:00001:2003/02/24 11:21:09.90 server  Database 'master': beginning upgrade step [ID     4]: creating in
dex (table sysobjects, index ncsysobjects)
00:00000:00001:2003/02/24 11:21:09.98 server  Database 'master': beginning upgrade step [ID    20]: creating ta
ble (table sysusages)
00:00000:00001:2003/02/24 11:21:10.26 server  Database 'master': beginning upgrade step [ID    21]: creating ta
ble (table sysdatabases)
00:00000:00001:2003/02/24 11:21:10.49 server  Database 'master': beginning upgrade step [ID    22]: creating ta
ble (table sysdevices)
00:00000:00001:2003/02/24 11:21:10.75 server  Database 'master': beginning upgrade step [ID    23]: creating ta
ble (table sysmessages)
00:00000:00001:2003/02/24 11:21:11.06 server  Database 'master': beginning upgrade step [ID    24]: creating ta
ble (table sysconfigures)
00:00000:00001:2003/02/24 11:21:11.39 server  Database 'master': beginning upgrade step [ID    25]: creating ta
ble (table syscharsets)
00:00000:00001:2003/02/24 11:21:11.61 server  Database 'master': beginning upgrade step [ID    26]: creating ta
ble (table sysprocedures)
00:00000:00001:2003/02/24 11:21:11.82 server  Database 'master': beginning upgrade step [ID    27]: creating ta
ble (table syscomments)
00:00000:00001:2003/02/24 11:21:11.97 server  Database 'master': beginning upgrade step [ID    28]: creating ta
ble (table syssegments)
00:00000:00001:2003/02/24 11:21:12.12 server  Database 'master': beginning upgrade step [ID    29]: creating ta
ble (table sysprotects)
00:00000:00001:2003/02/24 11:21:12.29 server  Database 'master': beginning upgrade step [ID    30]: creating ta
ble (table sysusers)
00:00000:00001:2003/02/24 11:21:12.59 server  Database 'master': beginning upgrade step [ID    31]: creating ta
ble (table sysalternates)
00:00000:00001:2003/02/24 11:21:12.71 server  Database 'master': beginning upgrade step [ID    32]: creating ta
ble (table sysdepends)
00:00000:00001:2003/02/24 11:21:12.94 server  Database 'master': beginning upgrade step [ID    33]: creating ta
ble (table syskeys)
00:00000:00001:2003/02/24 11:21:13.14 server  Database 'master': beginning upgrade step [ID    35]: creating ta
ble (table sysprocesses)
00:00000:00001:2003/02/24 11:21:13.17 server  Database 'master': beginning upgrade step [ID    36]: creating ta
ble (table syslogins)
00:00000:00001:2003/02/24 11:21:13.44 server  Database 'master': beginning upgrade step [ID    37]: creating ta
ble (table syslocks)
00:00000:00001:2003/02/24 11:21:13.47 server  Database 'master': beginning upgrade step [ID    38]: creating ta
ble (table syscurconfigs)
00:00000:00001:2003/02/24 11:21:13.64 server  Database 'master': beginning upgrade step [ID    39]: creating ta
ble (table sysservers)
00:00000:00001:2003/02/24 11:21:13.82 server  Database 'master': beginning upgrade step [ID    40]: creating ta
ble (table sysremotelogins)
00:00000:00001:2003/02/24 11:21:14.04 server  Database 'master': beginning upgrade step [ID    41]: creating ta
ble (table sysmonitors)
00:00000:00001:2003/02/24 11:21:14.08 server  Database 'master': beginning upgrade step [ID    42]: creating ta
ble (table sysengines)
00:00000:00001:2003/02/24 11:21:14.11 server  Database 'master': beginning upgrade step [ID    43]: creating ta
ble (table syslanguages)
00:00000:00001:2003/02/24 11:21:14.40 server  Database 'master': beginning upgrade step [ID    44]: creating ta
ble (table systestlog)
00:00000:00001:2003/02/24 11:21:14.44 server  Database 'master': beginning upgrade step [ID    45]: creating ta
ble (table syssrvroles)
00:00000:00001:2003/02/24 11:21:14.64 server  Database 'master': beginning upgrade step [ID    46]: creating ta
ble (table sysloginroles)
00:00000:00001:2003/02/24 11:21:14.82 server  Database 'master': beginning upgrade step [ID    80]: creating ta
ble (table sysattributes)
00:00000:00001:2003/02/24 11:21:15.13 server  Database 'master': beginning upgrade step [ID    81]: Load initia
l set of attribute-definition rows into SYSATTRIBUTES.
00:00000:00001:2003/02/24 11:21:19.38 server  Warning: Using only the first 30 characters for password
00:00000:00001:2003/02/24 11:21:22.74 server  Database 'master': beginning upgrade step [ID   251]: creating ta
ble (table syslogshold)
00:00000:00001:2003/02/24 11:21:22.87 server  Database 'master': beginning upgrade step [ID   252]: creating ta
ble (table syslisteners)
00:00000:00001:2003/02/24 11:21:22.93 server  Database 'master': beginning upgrade step [ID   253]: creating ta
ble (table syssecmechs)
00:00000:00001:2003/02/24 11:21:22.99 server  Database 'master': beginning upgrade step [ID   600]: creating ta
ble (table sysreferences)
00:00000:00001:2003/02/24 11:21:23.35 server  Database 'master': beginning upgrade step [ID   601]: creating ta
ble (table sysconstraints)
00:00000:00001:2003/02/24 11:21:23.66 server  Database 'master': beginning upgrade step [ID   602]: creating ta
ble (table sysusermessages)
00:00000:00001:2003/02/24 11:21:23.96 server  Database 'master': beginning upgrade step [ID   603]: creating ta
ble (table systhresholds)
00:00000:00001:2003/02/24 11:21:24.12 server  Database 'master': beginning upgrade step [ID   604]: creating ta
ble (table sysroles)
00:00000:00001:2003/02/24 11:21:24.40 server  Database 'master': beginning upgrade step [ID   605]: executing S
QL statement (declare @rid smallint  delete sysro)
00:00000:00001:2003/02/24 11:21:24.55 server  Database 'master': beginning upgrade step [ID   606]: executing S
QL statement (select lct_admin('lastchance', db_i)
00:00000:00001:2003/02/24 11:21:24.58 server  Database 'master': beginning upgrade step [ID  1013]: creating ta
ble (table syspartitions)
00:00000:00001:2003/02/24 11:21:24.82 server  Database 'master': beginning upgrade step [ID  1025]: creating ta
ble (table systimeranges)
00:00000:00001:2003/02/24 11:21:24.99 server  Database 'master': beginning upgrade step [ID  1026]: executing S
QL statement (if not exists (select 1 from systim)
00:00000:00001:2003/02/24 11:21:25.03 server  Database 'master': beginning upgrade step [ID  1027]: creating ta
ble (table sysresourcelimits)
00:00000:00001:2003/02/24 11:21:25.32 server  Database 'master': beginning upgrade step [ID  1082]: executing S
QL statement (if not exists (select 1 from sysatt)
00:00000:00001:2003/02/24 11:21:25.37 server  Database 'master': beginning upgrade step [ID  1124]: creating ta
ble (table systabstats)
00:00000:00001:2003/02/24 11:21:25.67 server  Database 'master': beginning upgrade step [ID  1125]: creating ta
ble (table sysstatistics)
00:00000:00001:2003/02/24 11:21:26.03 server  Database 'master': beginning upgrade step [ID  1126]: Initialize
systabstats with valid statistics
00:00000:00001:2003/02/24 11:21:26.92 server  Database 'master': beginning upgrade step [ID  1131]: Creating/Up
dating the last chance threshold for logsegment.
00:00000:00001:2003/02/24 11:21:26.94 server  Database 'master': beginning upgrade step [ID  1201]: creating ta
ble (table sysxtypes)
00:00000:00001:2003/02/24 11:21:27.39 server  Database 'master': beginning upgrade step [ID  1205]: creating ta
ble (table sysjars)
00:00000:00001:2003/02/24 11:21:27.75 server  Database 'master': beginning upgrade step [ID  1206]: executing S
QL statement (if not exists (select 1 from systyp)
00:00000:00001:2003/02/24 11:21:27.85 server  Database 'master': beginning upgrade step [ID  1212]: creating ta
ble (table systransactions)
00:00000:00001:2003/02/24 11:21:27.94 server  Database 'master': beginning upgrade step [ID  1213]: executing S
QL statement (update sysobjects set sysstat2 = sy)
00:00000:00001:2003/02/24 11:21:27.98 server  Database 'master': beginning upgrade step [ID  1214]: executing S
QL statement (if not exists (select 1 from syssrv)
00:00000:00001:2003/02/24 11:21:28.01 server  Database 'master': beginning upgrade step [ID  1226]: executing S
QL statement (insert sysattributes (class, attrib)
00:00000:00001:2003/02/24 11:21:28.05 server  Database 'master': beginning upgrade step [ID  1240]: creating ta
ble (table sysqueryplans)
00:00000:00001:2003/02/24 11:21:28.42 server  Database 'master': beginning upgrade step [ID  1241]: executing S
QL statement (insert into sysattributes         (class, )
00:00000:00001:2003/02/24 11:21:28.52 server  Database 'master': beginning upgrade step [ID  1242]: creating ta
ble (table syssessions)
00:00000:00001:2003/02/24 11:21:28.61 server  Database 'master': beginning upgrade step [ID  1245]: executing S
QL statement (if not exists (select 1 from syssrv)
00:00000:00001:2003/02/24 11:21:28.65 server  Database 'master': beginning upgrade step [ID  1249]: executing S
QL statement (if (select suser_id('sa')) is not n)
00:00000:00001:2003/02/24 11:21:28.69 server  Database 'master': beginning upgrade step [ID  1338]: executing S
QL statement (delete from sysconfigures where con)
00:00000:00001:2003/02/24 11:21:28.71 server  Database 'master': beginning upgrade step [ID  1339]: creating ta
ble (table syscertificates)
00:00000:00001:2003/02/24 11:21:28.98 server  Database 'master': beginning upgrade step [ID  1340]: executing S
QL statement (update systypes set length=@@maxpag)
00:00000:00001:2003/02/24 11:21:28.99 server  Database 'master': beginning upgrade step [ID  1344]: executing S
QL statement (update sysattributes set int_value=)
00:00000:00001:2003/02/24 11:21:29.03 server  Database 'master': beginning upgrade step [ID  1345]: executing S
QL statement (update sysattributes set int_value=)
00:00000:00001:2003/02/24 11:21:29.06 server  Database 'master': beginning upgrade step [ID  1400]: noting the
present database upgrade level
00:00000:00001:2003/02/24 11:21:29.10 server  Database 'model' appears to be at an older revision than the pres
ent installation; SQL Server will assess it, and upgrade it as required.
00:00000:00001:2003/02/24 11:21:29.10 server  Database 'model': beginning upgrade step [ID     1]: Initialize d
isk and create empty allocation units on master device.
00:00000:00001:2003/02/24 11:21:55.22 server  Database 'model': beginning upgrade step [ID     2]: Bootstrap ba
sic system catalogs in database.
00:00000:00001:2003/02/24 11:21:55.54 server  Database 'model': beginning upgrade step [ID     3]: creating ind
ex (table systypes, index ncsystypes)
00:00000:00001:2003/02/24 11:21:55.65 server  Database 'model': beginning upgrade step [ID     4]: creating ind
ex (table sysobjects, index ncsysobjects)
00:00000:00001:2003/02/24 11:21:55.70 server  Database 'model': beginning upgrade step [ID    26]: creating tab
le (table sysprocedures)
00:00000:00001:2003/02/24 11:21:55.89 server  Database 'model': beginning upgrade step [ID    27]: creating tab
le (table syscomments)
00:00000:00001:2003/02/24 11:21:56.03 server  Database 'model': beginning upgrade step [ID    28]: creating tab
le (table syssegments)
00:00000:00001:2003/02/24 11:21:56.09 server  Database 'model': beginning upgrade step [ID    29]: creating tab
le (table sysprotects)
00:00000:00001:2003/02/24 11:21:56.34 server  Database 'model': beginning upgrade step [ID    30]: creating tab
le (table sysusers)
00:00000:00001:2003/02/24 11:21:56.64 server  Database 'model': beginning upgrade step [ID    31]: creating tab
le (table sysalternates)
00:00000:00001:2003/02/24 11:21:56.78 server  Database 'model': beginning upgrade step [ID    32]: creating tab
le (table sysdepends)
00:00000:00001:2003/02/24 11:21:56.96 server  Database 'model': beginning upgrade step [ID    33]: creating tab
le (table syskeys)
00:00000:00001:2003/02/24 11:21:57.17 server  Database 'model': beginning upgrade step [ID    80]: creating tab
le (table sysattributes)
00:00000:00001:2003/02/24 11:21:57.51 server  Database 'model': beginning upgrade step [ID   600]: creating tab
le (table sysreferences)
00:00000:00001:2003/02/24 11:21:57.88 server  Database 'model': beginning upgrade step [ID   601]: creating tab
le (table sysconstraints)
00:00000:00001:2003/02/24 11:21:58.09 server  Database 'model': beginning upgrade step [ID   602]: creating tab
le (table sysusermessages)
00:00000:00001:2003/02/24 11:21:58.36 server  Database 'model': beginning upgrade step [ID   603]: creating tab
le (table systhresholds)
00:00000:00001:2003/02/24 11:21:58.57 server  Database 'model': beginning upgrade step [ID   604]: creating tab
le (table sysroles)
00:00000:00001:2003/02/24 11:21:58.72 server  Database 'model': beginning upgrade step [ID   605]: executing SQ
L statement (declare @rid smallint  delete sysro)
00:00000:00001:2003/02/24 11:21:58.94 server  Database 'model': beginning upgrade step [ID   606]: executing SQ
L statement (select lct_admin('lastchance', db_i)
00:00000:00001:2003/02/24 11:21:58.97 server  Database 'model': beginning upgrade step [ID  1013]: creating tab
le (table syspartitions)
00:00000:00001:2003/02/24 11:21:59.09 server  Database 'model': beginning upgrade step [ID  1124]: creating tab
le (table systabstats)
00:00000:00001:2003/02/24 11:21:59.34 server  Database 'model': beginning upgrade step [ID  1125]: creating tab
le (table sysstatistics)
00:00000:00001:2003/02/24 11:21:59.61 server  Database 'model': beginning upgrade step [ID  1126]: Initialize s
ystabstats with valid statistics
00:00000:00001:2003/02/24 11:22:00.14 server  Database 'model': beginning upgrade step [ID  1131]: Creating/Upd
ating the last chance threshold for logsegment.
00:00000:00001:2003/02/24 11:22:00.17 server  Database 'model': beginning upgrade step [ID  1201]: creating tab
le (table sysxtypes)
00:00000:00001:2003/02/24 11:22:00.51 server  Database 'model': beginning upgrade step [ID  1205]: creating tab
le (table sysjars)
00:00000:00001:2003/02/24 11:22:00.85 server  Database 'model': beginning upgrade step [ID  1206]: executing SQ
L statement (if not exists (select 1 from systyp)
00:00000:00001:2003/02/24 11:22:00.87 server  Database 'model': beginning upgrade step [ID  1240]: creating tab
le (table sysqueryplans)
00:00000:00001:2003/02/24 11:22:01.21 server  Database 'model': beginning upgrade step [ID  1241]: executing SQ
L statement (insert into sysattributes  (class, )
00:00000:00001:2003/02/24 11:22:01.26 server  Database 'model': beginning upgrade step [ID  1340]: executing SQ
L statement (update systypes set length=@@maxpag)
00:00000:00001:2003/02/24 11:22:01.28 server  Database 'model': beginning upgrade step [ID  1400]: noting the p
resent database upgrade level
00:00000:00001:2003/02/24 11:22:01.36 server  CREATE DATABASE: allocating 1024 logical pages (8.0 megabytes) on
disk 'master'.
00:00000:00001:2003/02/24 11:22:37.63 server  Database sybsystemdb successfully created.
00:00000:00001:2003/02/24 11:22:37.70 server  Recovering database 'sybsystemdb'.
00:00000:00001:2003/02/24 11:22:37.71 server  Redo pass of recovery has processed 2 committed and 0 aborted tra
nsactions.
00:00000:00001:2003/02/24 11:22:37.86 server  Boot Count: 1
00:00000:00001:2003/02/24 11:22:37.88 server  Checking external objects.
00:00000:00001:2003/02/24 11:22:37.89 server  Database 'sybsystemdb' is now online.
00:00000:00001:2003/02/24 11:22:37.90 server  Now loading SQL Server's new default sort order and character set
00:00000:00001:2003/02/24 11:22:37.90 server  Checking sysobjects: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.90 server  Checking systypes: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.90 server  Checking sysusers: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.90 server  Checking sysreferences: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.90 server  Checking sysreferences: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.90 server  Checking sysreferences: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.90 server  Checking sysattributes: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.90 server  Checking sysattributes: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.90 server  Checking sysxtypes: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.90 server  Checking sysjars: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.91 server  Checking sysobjects: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.91 server  Checking systypes: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.91 server  Checking sysusers: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.91 server  Checking sysreferences: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.91 server  Checking sysreferences: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.91 server  Checking sysreferences: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.91 server  Checking sysattributes: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.91 server  Checking sysattributes: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.91 server  Checking sysxtypes: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.91 server  Checking sysjars: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.91 server  Checking sysobjects: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.91 server  Checking systypes: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.91 server  Checking sysusers: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.91 server  Checking sysreferences: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.91 server  Checking sysreferences: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.91 server  Checking sysreferences: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.91 server  Checking sysattributes: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.92 server  Checking sysattributes: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.92 server  Checking sysxtypes: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.92 server  Checking sysjars: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.92 server  Checking sysdatabases: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.92 server  Checking syslogins: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.92 server  Checking sysdevices: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.92 server  Checking sysconfigures: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.92 server  Checking sysservers: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.92 server  Checking sysremotelogins: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.92 server  Checking syslanguages: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.92 server  Checking syslanguages: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.93 server  Checking syscharsets: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:37.93 server  Checking sysresourcelimits: Logical pagesize is 8192 bytes
00:00000:00001:2003/02/24 11:22:38.01 server  Default Sort Order successfully changed.
00:00000:00001:2003/02/24 11:22:38.01 server  SQL Server shutdown after verifying System Indexes.
00:00000:00001:2003/02/24 11:22:38.01 kernel  ueshutdown: exiting
00:00000:00000:2003/02/24 11:22:38.18 kernel  Use license file /export/home/sybase/SYSAM-1_0/licenses/license.d
at.
00:00000:00000:2003/02/24 11:22:38.18 kernel  Checked out license ASE_SERVER
00:00000:00000:2003/02/24 11:22:38.19 kernel  Using config area from primary master device.
00:00000:00000:2003/02/24 11:22:38.23 kernel  os_find_good_keyfile: Found shared memory segment: key 0xea00eb17
, id 1201
00:00000:00000:2003/02/24 11:22:38.25 kernel  os_find_good_keyfile: If SQL Server using it is not running, remo
ve it by hand
00:00000:00000:2003/02/24 11:22:38.25 kernel  os_find_good_keyfile: Trying a different key
00:00000:00000:2003/02/24 11:22:38.44 kernel  Using 1024 file descriptors.
00:00000:00000:2003/02/24 11:22:38.45 kernel  Adaptive Server Enterprise/12.5/SWR 9610 GA/P/Sun_svr4/OS 5.8/mai
n/1647/64-bit/FBO/Sat Jun  2 01:55:25 2001
00:00000:00000:2003/02/24 11:22:38.45 kernel  Confidential property of Sybase, Inc.
00:00000:00000:2003/02/24 11:22:38.45 kernel  Copyright 1987, 2001
00:00000:00000:2003/02/24 11:22:38.45 kernel  Sybase, Inc.  All rights reserved.
00:00000:00000:2003/02/24 11:22:38.45 kernel  Unpublished rights reserved under U.S. copyright laws.
00:00000:00000:2003/02/24 11:22:38.45 kernel  
00:00000:00000:2003/02/24 11:22:38.45 kernel  This software contains confidential and trade secret information
of Sybase,
00:00000:00000:2003/02/24 11:22:38.45 kernel  Inc.   Use,  duplication or disclosure of the software and docume
ntation by
00:00000:00000:2003/02/24 11:22:38.45 kernel  the  U.S.  Government  is  subject  to  restrictions set forth in
a license
00:00000:00000:2003/02/24 11:22:38.45 kernel  agreement  between  the  Government  and  Sybase,  Inc.  or  othe
r  written
00:00000:00000:2003/02/24 11:22:38.45 kernel  agreement  specifying  the  Government's rights to use the softwa
re and any
00:00000:00000:2003/02/24 11:22:38.45 kernel  applicable FAR provisions, for example, FAR 52.227-19.
00:00000:00000:2003/02/24 11:22:38.45 kernel  Sybase, Inc. 6475 Christie Avenue, Emeryville, CA 94608, USA
00:00000:00000:2003/02/24 11:22:38.45 kernel  Using '/export/home/sybase/ASE-12_5/jcweb.cfg' for configuration
information.
00:00000:00000:2003/02/24 11:22:38.45 kernel  Logging ASE messages in file '/export/home/sybase/ASE-12_5/instal
l/jcweb.log'.
00:00000:00000:2003/02/24 11:22:38.48 kernel  kdcl_sess_open: connectivity library supports master/query syntax
.
00:00000:00000:2003/02/24 11:22:38.49 kernel  Directory Control Layer (DCL) using directory driver: InterfacesD
river
00:00000:00000:2003/02/24 11:22:38.49 kernel  SSL Plus security modules loaded successfully.
00:00000:00000:2003/02/24 11:22:38.49 kernel  Network and device connection limit is 1014.
00:00000:00000:2003/02/24 11:22:38.68 server  Number of blocks left for proc headers: 3192.
00:00000:00000:2003/02/24 11:22:38.69 server  Proc header memory allocated 1596 pages for each per engine cache
00:00000:00000:2003/02/24 11:22:38.71 server  Memory allocated for the default data cache cachelet 1: 8192 Kb
00:00000:00000:2003/02/24 11:22:38.71 server  Size of the 8K memory pool: 8192 Kb
00:00000:00000:2003/02/24 11:22:38.71 kernel  Enabling Sun Kernel asynchronous disk I/O strategy
00:00000:00000:2003/02/24 11:22:38.71 kernel  Initializing virtual device 0, '/databasefile/jcweb/db/master.dat
' with dsync 'on'.
00:00000:00000:2003/02/24 11:22:38.71 kernel  Virtual device 0 started using asynchronous i/o.
00:00000:00000:2003/02/24 11:22:38.71 kernel  Worker Thread Manager is not enabled for use in SQL Server.
00:00000:00000:2003/02/24 11:22:38.72 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 n
ot be initialized. No external security mechanisms will be supported.
00:00000:00000:2003/02/24 11:22:38.72 kernel  engine 0, os pid 552  online
00:00000:00000:2003/02/24 11:22:38.72 server  No active traceflags
00:00000:00001:2003/02/24 11:22:38.72 kernel  libomni1 - Component Integration Services loaded; version 'libomn
i1 - Component Integration Services/12.5/SWR 9610 GA/P/Sun_svr4/OS 5.8/main/1647/64-bit/FBO/Sat Jun  2 01:55:25
2001'.
00:00000:00001:2003/02/24 11:22:38.72 kernel  libomni1 - Component Integration Services: using 'Sybase Client-L
ibrary/12.5/P/SPARC/Solaris 2.8/1/64bit/OPT/Sun Mar 25 08:30:37 2001'
00:00000:00001:2003/02/24 11:22:38.72 server  Opening Master Database ...
00:00000:00001:2003/02/24 11:22:38.80 server  Loading SQL Server's default sort order and character set
00:00000:00001:2003/02/24 11:22:38.80 server  Loaded default Unilib conversion handle.
00:00000:00001:2003/02/24 11:22:38.82 server  Recovering database 'master'.
00:00000:00001:2003/02/24 11:22:38.82 server  Redo pass of recovery has processed 3 committed and 0 aborted tra
nsactions.
00:00000:00001:2003/02/24 11:22:38.90 server  Checking external objects.
00:00000:00001:2003/02/24 11:22:38.92 server  Database 'master' is now online.
00:00000:00001:2003/02/24 11:22:38.92 server  The transaction log in the database 'master' will use I/O size of
8 Kb.
00:00000:00001:2003/02/24 11:22:38.92 server  Warning: ASE_HA has no valid license and therefore is not initial
ized.
00:00000:00001:2003/02/24 11:22:38.92 server  server is unnamed
00:00000:00001:2003/02/24 11:22:39.00 server  Recovering database 'sybsystemdb'.
00:00000:00001:2003/02/24 11:22:39.07 server  Boot Count: 2
00:00000:00001:2003/02/24 11:22:39.09 server  Checking external objects.
00:00000:00001:2003/02/24 11:22:39.09 server  The transaction log in the database 'sybsystemdb' will use I/O si
ze of 8 Kb.
00:00000:00001:2003/02/24 11:22:39.10 server  Database 'sybsystemdb' is now online.
00:00000:00001:2003/02/24 11:22:39.11 server  Recovering database 'model'.
00:00000:00001:2003/02/24 11:22:39.19 server  Checking external objects.
00:00000:00001:2003/02/24 11:22:39.20 server  The transaction log in the database 'model' will use I/O size of
8 Kb.
00:00000:00001:2003/02/24 11:22:39.21 server  Database 'model' is now online.
00:00000:00001:2003/02/24 11:22:39.21 server  The logical pagesize of the server is 8 Kb.
00:00000:00001:2003/02/24 11:22:39.21 server  0 dump conditions detected at boot time
00:00000:00001:2003/02/24 11:22:39.22 server  Resident Node id: bdc6785d508b
00:00000:00001:2003/02/24 11:22:39.22 server  Transaction coordinator initialized.
00:00000:00001:2003/02/24 11:22:39.22 server  Clearing temp db
00:00000:00001:2003/02/24 11:22:45.06 server  The transaction log in the database 'tempdb' will use I/O size of
8 Kb.
00:00000:00001:2003/02/24 11:22:45.08 server  Database 'tempdb' is now online.
00:00000:00002:2003/02/24 11:22:45.09 kernel  ninit:0: listener type: master
00:00000:00002:2003/02/24 11:22:45.09 kernel  ninit:0: listener endpoint: /dev/tcp
00:00000:00002:2003/02/24 11:22:45.09 kernel  ninit:0: listener raw address: \x00021172c0a810050000000000000000
00:00000:00002:2003/02/24 11:22:45.09 kernel  ninit:0: transport provider: T_COTS_ORD
00:00000:00002:2003/02/24 11:22:45.09 kernel  ninit: t_bind, No Error
00:00000:00002:2003/02/24 11:22:45.09 kernel  ninit: All master network listeners have failed.  Shutting down.
00:00000:00002:2003/02/24 11:22:45.09 kernel  ueshutdown: exiting

jazy

很奇怪！
前面都沒什么錯誤阿！怎么最后報一個All master network listeners 呢？

就只有這些日志信息嗎？

察看一下你的網絡配置信息，對比一下你的interfaces中文件的ip信息！看看有沒有什么出入！

rabbitdan

就這些日志阿！我的服務沒有建成，所以我的interfaces是一個空文件阿！
我的*.rs文件如下

sybinit.release_directory: /export/home/sybase
sybinit.product: sqlsrv
sqlsrv.server_name: jcweb
sqlsrv.new_config: yes
sqlsrv.do_add_server: yes
sqlsrv.network_protocol_list: tcp
sqlsrv.network_hostname_list: 192.168.16.5
sqlsrv.network_port_list: 4466
sqlsrv.server_page_size: 8k
sqlsrv.force_buildmaster: yes
sqlsrv.master_device_physical_name: /databasefile/jcweb/db/master.dat
sqlsrv.master_device_size: 250
sqlsrv.master_database_size: 150
sqlsrv.errorlog: USE_DEFAULT
sqlsrv.do_upgrade: no
sqlsrv.sybsystemprocs_device_physical_name: /databasefile/jcweb/db/sybprocs.dat
sqlsrv.sybsystemprocs_device_size: 250
sqlsrv.sybsystemprocs_database_size: 200
sqlsrv.default_backup_server: jcweb_backup


我也就是找不到錯誤在那里阿！

eastarwang

按照提示，系統是找不到sybase的服務，請問你在sybase用戶主目錄下，有沒有配置sybase用戶的環(huán)境變量

eastarwang

另外，報all network。。。。。fail

一般是你的ip地址或端口地址有錯誤
1、先檢查你的*.rs文件中的ip地址,是否在你的系統中存在
  #netstat -in
2、檢查你的端口是否已經被使用

shaotao27

風格

yaoliang

請教Blackrose:
    在安裝sybase12.5(NT4.0)后，我的服務器在開始啟動時，能夠自動啟動SYBASE服務，但以后在控制面板中無法重新啟動SYBASE服務，這是為何？

Blackrose

yaoliang ：
你說的自動啟動是不是指你已經把sybase服務設置為自動?
你把帖子新發(fā)一個吧！