11.0.3.3 to 11.5.1 (NT4.0)

I'm trying an upgrade in place on a test server and all is fine until the
upgrade process tries to start the SQL server.  It passed the eligibility
test, then reported that there is one conflict with 11.5 reserved words.  I
figured I could find that and tend to it afterwards.  I clicked OK and got a
window saying it is proceeding with the upgrade at which point it fails and
says "Failed to boot server ..."   I tried to start it manually in Sybase
Central and it fails with "Procedure entry point uniutf8_unistrNFromUTF8
could not be loaded in the DLL libunic.dll."   I re-booted NT, tried using
Server Config to restart/complete the upgrade and have the same problem.

This is the bottom of the upgrade error log - everthing looks OK until this:

11/23/99 10:59:52 AM Sending the following SQL command to the server: 'use
                     tempdb'.
11/23/99 10:59:52 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:52 AM Sending the following SQL command to the server: 'use
                     vsreport'.
11/23/99 10:59:52 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:52 AM Sending the following SQL command to the server: 'exec
                     sp_configure 'allow updates', 1'.
11/23/99 10:59:52 AM Sending the following SQL command to the server:
                     'reconfigure with override'.
11/23/99 10:59:52 AM Sending the following SQL command to the server:
                     'shutdown'.
11/23/99 10:59:53 AM Waiting 10 seconds for the operating system to reclaim
                     resources before rebooting.
11/23/99 11:00:15 AM Calling the shell with 'C:\SYBASE\bin\sqlsrvr.exe
                     -dC:\SYBASE\DATA\MASTER.DAT -sGARDBA
                     -eC:\SYBASE\upgrade\errorlog.upg -iC:\SYBASE\ini
                     -MC:\SYBASE'.
11/23/99 11:00:15 AM waiting for server 'GARDBA' to boot...
11/23/99 11:00:53 AM SERVER ERROR: Failed to boot server 'GARDBA'.
11/23/99 11:00:55 AM Task failed: upgrade the Adaptive Server. Terminating
                     configuration.
11/23/99 11:00:55 AM Configuration failed.
11/23/99 11:00:57 AM Exiting.
11/23/99 11:00:57 AM The log file for this session is
                     'C:\SYBASE\init\logs\log1123.003'.
11/23/99 11:00:57 AM Log close.


Have no idea where to go from here ...

RD





0
Ray
11/23/1999 4:16:34 PM
sybase.sqlserver.configuration 393 articles. 0 followers. Follow

5 Replies
981 Views

Similar Articles

[PageSpeed] 54
Get it on Google Play
Get it on Apple App Store

Hi Ray,

Take a look at the log file shown below for clues.  You may want to post any
of the error messages on this newsgroup.

Jason

"Ray DiMarcello" <rdimarcello@ingva.com> wrote in message
news:5BqAG8cN$GA.203@forums.sybase.com...
> 11/23/99 11:00:57 AM The log file for this session is
>                      'C:\SYBASE\init\logs\log1123.003'.



0
Jason
11/23/1999 5:27:20 PM
What I included is from 'C:\SYBASE\init\logs\log1123.003' ... here's the
entire thing ...




11/23/99 10:56:40 AM SyBatch/11.5.1/P/PC INTEL/Windows NT 4.0/3/OPT
11/23/99 10:56:40 AM Confidential property of Sybase, Inc.
                     Copyright Sybase Inc., 1987, 1998.
                     Sybase, Inc. All rights reserved.
                     Unpublished rights reserved under U.S. copyright laws

                     This software contains confidential and trade secret
                     information of Sybase, Inc. Use, duplication, or
diclosure
                     of the software and documentation by the U.S.
Government
                     is subject to restrictions as set forth in a license
                     agreement
                     between the Government and Sybase,Inc. or other written
                     agreement specifying the Government's rights to use the
                     software and any applicable FAR provisions, for
example,
                     FAR 52.227-19.
                     Sybase, Inc. 6475 Christie Avenue, Emeryville, CA 94608
                     USA.

11/23/99 10:56:40 AM BEGIN ENVIRONMENT INFORMATION

USER ENVIRONMENT
----------------------------------------
current directory:             C:\SYBASE
character set:                 iso_1
language:                      us_english
auditinit release directory:   C:\SYBASE
working release directory:     C:\SYBASE

DSQUERY:                       GARDBA
DSLISTEN:                      GARDBA

11/23/99 10:56:40 AM END ENVIRONMENT INFORMATION
11/23/99 10:57:56 AM Calling the shell with 'C:\SYBASE\upgrade\preupgrd.exe
                     -SGARDBA -P -N '.
11/23/99 10:58:56 AM Calling the shell with '0 = return code.'.
11/23/99 10:58:56 AM Done
11/23/99 10:58:56 AM Begin output from 'preupgrd':
 Starting preupgrade of Adaptive Server.
 Checking status in all existing databases.
 Checking space in all existing databases.
  Database ABSTRACT has sufficient space.
  Database DBADB has sufficient space.
  Database DOCUMENT has sufficient space.
  Database FILES has sufficient space.
  Database GA01ABS has sufficient space.
  Database GA01DOC has sufficient space.
  Database GA01FIL has sufficient space.
  Database GAL has sufficient space.
  Database GALQUEUE has sufficient space.
  Database GF01ABS has sufficient space.
  Database GF01DOC has sufficient space.
  Database GF01FIL has sufficient space.
  Database GL01ABS has sufficient space.
  Database GL01DOC has sufficient space.
  Database GL01FIL has sufficient space.
  Database GREFABS has sufficient space.
  Database GREFDOC has sufficient space.
  Database GREFFIL has sufficient space.
  Database POLNO has sufficient space.
  Database SYSFILES has sufficient space.
  Database VSUSER has sufficient space.
  Database WORKFLOW has sufficient space.
  Database audit_history has sufficient space.
  Database master has sufficient space.
  Database model has sufficient space.
  Database sybsecurity has sufficient space.
  Database sybsystemprocs has sufficient space.
  Database tempdb has sufficient space.
  Database vsreport has sufficient space.
 Clearing reused columns in all existing databases.
 Preupgrade of Adaptive Server to 11.5.1.0 is complete.
11/23/99 10:58:56 AM End output from 'preupgrd'.
11/23/99 10:59:18 AM Server 'GARDBA' passed preupgrade eligibility test.
11/23/99 10:59:19 AM Done
11/23/99 10:59:19 AM Sending the following SQL command to the server: 'use
                     ABSTRACT'.
11/23/99 10:59:19 AM Sending the following SQL command to the server: 'use
                     DBADB'.
11/23/99 10:59:20 AM Sending the following SQL command to the server: 'use
                     DOCUMENT'.
11/23/99 10:59:20 AM Sending the following SQL command to the server: 'use
                     FILES'.
11/23/99 10:59:20 AM Sending the following SQL command to the server: 'use
                     GA01ABS'.
11/23/99 10:59:20 AM Sending the following SQL command to the server: 'use
                     GA01DOC'.
11/23/99 10:59:21 AM Sending the following SQL command to the server: 'use
                     GA01FIL'.
11/23/99 10:59:21 AM Sending the following SQL command to the server: 'use
GAL'.
11/23/99 10:59:22 AM Sending the following SQL command to the server: 'use
                     GALQUEUE'.
11/23/99 10:59:23 AM Sending the following SQL command to the server: 'use
                     GF01ABS'.
11/23/99 10:59:23 AM Sending the following SQL command to the server: 'use
                     GF01DOC'.
11/23/99 10:59:24 AM Sending the following SQL command to the server: 'use
                     GF01FIL'.
11/23/99 10:59:24 AM Sending the following SQL command to the server: 'use
                     GL01ABS'.
11/23/99 10:59:24 AM Sending the following SQL command to the server: 'use
                     GL01DOC'.
11/23/99 10:59:25 AM Sending the following SQL command to the server: 'use
                     GL01FIL'.
11/23/99 10:59:25 AM Sending the following SQL command to the server: 'use
                     GREFABS'.
11/23/99 10:59:26 AM Sending the following SQL command to the server: 'use
                     GREFDOC'.
11/23/99 10:59:26 AM Sending the following SQL command to the server: 'use
                     GREFFIL'.
11/23/99 10:59:27 AM Sending the following SQL command to the server: 'use
                     POLNO'.
11/23/99 10:59:27 AM Sending the following SQL command to the server: 'use
                     SYSFILES'.
11/23/99 10:59:27 AM Sending the following SQL command to the server: 'use
                     VSUSER'.
11/23/99 10:59:28 AM Sending the following SQL command to the server: 'use
                     WORKFLOW'.
11/23/99 10:59:28 AM Sending the following SQL command to the server: 'use
                     audit_history'.
11/23/99 10:59:29 AM Sending the following SQL command to the server: 'use
                     master'.
11/23/99 10:59:29 AM Sending the following SQL command to the server: 'use
                     model'.
11/23/99 10:59:29 AM Sending the following SQL command to the server: 'use
                     sybsecurity'.
11/23/99 10:59:30 AM Sending the following SQL command to the server: 'use
                     sybsystemprocs'.
11/23/99 10:59:30 AM Sending the following SQL command to the server: 'use
                     tempdb'.
11/23/99 10:59:30 AM Sending the following SQL command to the server: 'use
                     vsreport'.
11/23/99 10:59:31 AM The log file for sp_checkreswords output is
                     'C:\SYBASE\init\logs\checkres.dmp'.
11/23/99 10:59:49 AM Running task: upgrade the Adaptive Server.
11/23/99 10:59:49 AM Checkpointing all databases.
11/23/99 10:59:49 AM Sending the following SQL command to the server: 'use
                     ABSTRACT'.
11/23/99 10:59:49 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:49 AM Sending the following SQL command to the server: 'use
                     DBADB'.
11/23/99 10:59:49 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:49 AM Sending the following SQL command to the server: 'use
                     DOCUMENT'.
11/23/99 10:59:49 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:49 AM Sending the following SQL command to the server: 'use
                     FILES'.
11/23/99 10:59:49 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:49 AM Sending the following SQL command to the server: 'use
                     GA01ABS'.
11/23/99 10:59:49 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:49 AM Sending the following SQL command to the server: 'use
                     GA01DOC'.
11/23/99 10:59:49 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:49 AM Sending the following SQL command to the server: 'use
                     GA01FIL'.
11/23/99 10:59:49 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:49 AM Sending the following SQL command to the server: 'use
GAL'.
11/23/99 10:59:50 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:50 AM Sending the following SQL command to the server: 'use
                     GALQUEUE'.
11/23/99 10:59:50 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:50 AM Sending the following SQL command to the server: 'use
                     GF01ABS'.
11/23/99 10:59:50 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:50 AM Sending the following SQL command to the server: 'use
                     GF01DOC'.
11/23/99 10:59:50 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:50 AM Sending the following SQL command to the server: 'use
                     GF01FIL'.
11/23/99 10:59:50 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:50 AM Sending the following SQL command to the server: 'use
                     GL01ABS'.
11/23/99 10:59:50 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:50 AM Sending the following SQL command to the server: 'use
                     GL01DOC'.
11/23/99 10:59:50 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:50 AM Sending the following SQL command to the server: 'use
                     GL01FIL'.
11/23/99 10:59:51 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:51 AM Sending the following SQL command to the server: 'use
                     GREFABS'.
11/23/99 10:59:51 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:51 AM Sending the following SQL command to the server: 'use
                     GREFDOC'.
11/23/99 10:59:51 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:51 AM Sending the following SQL command to the server: 'use
                     GREFFIL'.
11/23/99 10:59:51 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:51 AM Sending the following SQL command to the server: 'use
                     POLNO'.
11/23/99 10:59:51 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:51 AM Sending the following SQL command to the server: 'use
                     SYSFILES'.
11/23/99 10:59:51 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:51 AM Sending the following SQL command to the server: 'use
                     VSUSER'.
11/23/99 10:59:52 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:52 AM Sending the following SQL command to the server: 'use
                     WORKFLOW'.
11/23/99 10:59:52 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:52 AM Sending the following SQL command to the server: 'use
                     audit_history'.
11/23/99 10:59:52 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:52 AM Sending the following SQL command to the server: 'use
                     master'.
11/23/99 10:59:52 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:52 AM Sending the following SQL command to the server: 'use
                     model'.
11/23/99 10:59:52 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:52 AM Sending the following SQL command to the server: 'use
                     sybsecurity'.
11/23/99 10:59:52 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:52 AM Sending the following SQL command to the server: 'use
                     sybsystemprocs'.
11/23/99 10:59:52 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:52 AM Sending the following SQL command to the server: 'use
                     tempdb'.
11/23/99 10:59:52 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:52 AM Sending the following SQL command to the server: 'use
                     vsreport'.
11/23/99 10:59:52 AM Sending the following SQL command to the server:
                     'checkpoint'.
11/23/99 10:59:52 AM Sending the following SQL command to the server: 'exec
                     sp_configure 'allow updates', 1'.
11/23/99 10:59:52 AM Sending the following SQL command to the server:
                     'reconfigure with override'.
11/23/99 10:59:52 AM Sending the following SQL command to the server:
                     'shutdown'.
11/23/99 10:59:53 AM Waiting 10 seconds for the operating system to reclaim
                     resources before rebooting.
11/23/99 11:00:15 AM Calling the shell with 'C:\SYBASE\bin\sqlsrvr.exe
                     -dC:\SYBASE\DATA\MASTER.DAT -sGARDBA
                     -eC:\SYBASE\upgrade\errorlog.upg -iC:\SYBASE\ini
                     -MC:\SYBASE'.
11/23/99 11:00:15 AM waiting for server 'GARDBA' to boot...
11/23/99 11:00:53 AM SERVER ERROR: Failed to boot server 'GARDBA'.
11/23/99 11:00:55 AM Task failed: upgrade the Adaptive Server. Terminating
                     configuration.
11/23/99 11:00:55 AM Configuration failed.
11/23/99 11:00:57 AM Exiting.
11/23/99 11:00:57 AM The log file for this session is
                     'C:\SYBASE\init\logs\log1123.003'.
11/23/99 11:00:57 AM Log close.


Jason Froebe wrote in message <6nXxUidN$GA.268@forums.sybase.com>...
>Hi Ray,
>
>Take a look at the log file shown below for clues.  You may want to post
any
>of the error messages on this newsgroup.
>
>Jason
>
>"Ray DiMarcello" <rdimarcello@ingva.com> wrote in message
>news:5BqAG8cN$GA.203@forums.sybase.com...
>> 11/23/99 11:00:57 AM The log file for this session is
>>                      'C:\SYBASE\init\logs\log1123.003'.
>
>
>


0
Ray
11/23/1999 7:50:51 PM
Hi Ray,

This is what you need to do:

1. make a copy master.dat
2. search for any duplicates of libunic.dll on that machine.
libunic.dll should be in $Sybase\dll and most likely should be 238kb and have a
modified date of 01/05/1998
3. try to start the server after all cleanup
4. once you've started the server, stop it, restore master.dat, go to syconfig
and restart the upgrade process

Hope this helps,

AnaMaria Stirbet
Sybase TS


Ray DiMarcello wrote:

> I'm trying an upgrade in place on a test server and all is fine until the
> upgrade process tries to start the SQL server.  It passed the eligibility
> test, then reported that there is one conflict with 11.5 reserved words.  I
> figured I could find that and tend to it afterwards.  I clicked OK and got a
> window saying it is proceeding with the upgrade at which point it fails and
> says "Failed to boot server ..."   I tried to start it manually in Sybase
> Central and it fails with "Procedure entry point uniutf8_unistrNFromUTF8
> could not be loaded in the DLL libunic.dll."   I re-booted NT, tried using
> Server Config to restart/complete the upgrade and have the same problem.
>
> This is the bottom of the upgrade error log - everthing looks OK until this:
>
> 11/23/99 10:59:52 AM Sending the following SQL command to the server: 'use
>                      tempdb'.
> 11/23/99 10:59:52 AM Sending the following SQL command to the server:
>                      'checkpoint'.
> 11/23/99 10:59:52 AM Sending the following SQL command to the server: 'use
>                      vsreport'.
> 11/23/99 10:59:52 AM Sending the following SQL command to the server:
>                      'checkpoint'.
> 11/23/99 10:59:52 AM Sending the following SQL command to the server: 'exec
>                      sp_configure 'allow updates', 1'.
> 11/23/99 10:59:52 AM Sending the following SQL command to the server:
>                      'reconfigure with override'.
> 11/23/99 10:59:52 AM Sending the following SQL command to the server:
>                      'shutdown'.
> 11/23/99 10:59:53 AM Waiting 10 seconds for the operating system to reclaim
>                      resources before rebooting.
> 11/23/99 11:00:15 AM Calling the shell with 'C:\SYBASE\bin\sqlsrvr.exe
>                      -dC:\SYBASE\DATA\MASTER.DAT -sGARDBA
>                      -eC:\SYBASE\upgrade\errorlog.upg -iC:\SYBASE\ini
>                      -MC:\SYBASE'.
> 11/23/99 11:00:15 AM waiting for server 'GARDBA' to boot...
> 11/23/99 11:00:53 AM SERVER ERROR: Failed to boot server 'GARDBA'.
> 11/23/99 11:00:55 AM Task failed: upgrade the Adaptive Server. Terminating
>                      configuration.
> 11/23/99 11:00:55 AM Configuration failed.
> 11/23/99 11:00:57 AM Exiting.
> 11/23/99 11:00:57 AM The log file for this session is
>                      'C:\SYBASE\init\logs\log1123.003'.
> 11/23/99 11:00:57 AM Log close.
>
> Have no idea where to go from here ...
>
> RD

0
AnaMaria
11/23/1999 9:40:02 PM
Interesting ... guess I should have done the same with sybsecurity.  Now I'm
past the dll error but get an invalid log version message for sybsecurity
when it tries to start the server followed by a bunch of buffer errors for
default data cache. See log below.


/***************************************************************************
****************************************************************************
**********************/
00:1999/11/24 08:04:30.00 kernel  Using config area from primary master
device.
00:1999/11/24 08:04:30.18 kernel  Warning: Using default file
'C:\SYBASE.SAV\/GARDBA.cfg' since a configuration file was not specified.
Specify a configuration file name in the RUNSERVER file to avoid this
message.
00:1999/11/24 08:04:32.38 kernel  Kernel memory at 0x20000000, 172032 bytes
00:1999/11/24 08:04:32.38 kernel  Server part of first shared memory region
at 0x2002a000, 267280384 bytes
00:1999/11/24 08:04:32.38 kernel  Highest valid address is 0x2002a000
00:1999/11/24 08:04:32.38 kernel  Using 2048 file descriptors.
00:1999/11/24 08:04:32.43 kernel  SQL Server/11.0.3.3/P/PC Intel/Windows NT
3.5/SWR 8299 ESD 4/OPT/Thu Mar 11 1999 3:40:09.82
00:1999/11/24 08:04:32.43 kernel  (c) Copyright 1987, 1999.
00:1999/11/24 08:04:32.43 kernel  Sybase, Inc.  All rights reserved.
00:1999/11/24 08:04:32.43 kernel
00:1999/11/24 08:04:32.44 kernel  Unpublished rights reserved under U.S.
copyright laws.
00:1999/11/24 08:04:32.44 kernel  This software contains confidential and
trade secret information of Sybase,
00:1999/11/24 08:04:32.44 kernel  Inc.   Use,  duplication or disclosure of
the software and documentation by
00:1999/11/24 08:04:32.44 kernel  the  U.S.  Government  is  subject  to
restrictions set forth in a license
00:1999/11/24 08:04:32.44 kernel  agreement  between  the  Government  and
Sybase,  Inc.  or  other  written
00:1999/11/24 08:04:32.44 kernel  agreement  specifying  the  Government's
rights to use the software and any
00:1999/11/24 08:04:32.44 kernel  applicable FAR provisions, for example,
FAR 52.227-19.
00:1999/11/24 08:04:32.44 kernel
00:1999/11/24 08:04:32.44 kernel  Sybase, Inc. 6475 Christie Avenue,
Emeryville, CA 94608, USA.
00:1999/11/24 08:04:32.44 kernel  Using 'C:\SYBASE.SAV\/GARDBA.cfg' for
configuration information.
00:1999/11/24 08:04:32.49 kernel  Logging SQL Server messages in file
'C:\SYBASE\upgrade\errorlog.upg'
..
00:1999/11/24 08:04:32.89 kernel  *** WARNING ******************
00:1999/11/24 08:04:32.89 kernel  Operating system may favor the system
cache when memory is at a premium.
 To disable this warning, set the registry parameter 'LargeSystemCache' to 0
in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Memory Management.
00:1999/11/24 08:04:32.89 kernel  SQL Server NT process id is 0xd2.
00:1999/11/24 08:04:32.89 kernel  SQL Server was started as a Service.
00:1999/11/24 08:04:32.89 kernel  Network and device connection limit is
2040.
00:1999/11/24 08:04:32.95 server  Number of proc buffers allocated: 25487.
00:1999/11/24 08:04:33.06 server  Number of blocks left for proc headers:
25569.
00:1999/11/24 08:04:33.06 server  Memory allocated for the default data
cache cache: 193776 Kb
00:1999/11/24 08:04:33.14 server  Size of the 2K memory pool: 142576 Kb
00:1999/11/24 08:04:33.17 server  Size of the 16K memory pool: 51200 Kb
00:1999/11/24 08:04:33.18 kernel  Initializing virtual device 0,
'C:\SYBASE\DATA\MASTER.DAT'
00:1999/11/24 08:04:33.18 kernel  Virtual device 0 started using
asynchronous i/o.
00:1999/11/24 08:04:33.19 server  No active traceflags
00:1999/11/24 08:04:33.37 server  Opening Master Database ...
00:1999/11/24 08:04:33.54 server  Loading SQL Server's default sort order
and character set
00:1999/11/24 08:04:33.66 server  Recovering database 'master'
00:1999/11/24 08:04:33.69 server  Recovery dbid 1 ckpt (1488,9)
00:1999/11/24 08:04:33.69 server  Recovery no active transactions before
ckpt.
00:1999/11/24 08:04:33.98 server  Database 'master' is now online.
00:1999/11/24 08:04:33.99 server  The transaction log in the database
'master' will use I/O size of 2 Kb.
00:1999/11/24 08:04:34.05 server  0 dump conditions detected at boot time
00:1999/11/24 08:04:34.07 server  server name is 'GARDBA'
00:1999/11/24 08:04:34.11 server  Activating disk 'abstract_db_01'.
00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 5,
'e:\devices\abstract_db_01.dat'
00:1999/11/24 08:04:34.11 kernel  Virtual device 5 started using
asynchronous i/o.
00:1999/11/24 08:04:34.11 server  Activating disk 'abstract_log_01'.
00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 6,
'e:\devices\abstract_log_01.dat'
00:1999/11/24 08:04:34.11 kernel  Virtual device 6 started using
asynchronous i/o.
00:1999/11/24 08:04:34.11 server  Activating disk 'audit_history_db_01'.
00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 52,
'e:\devices\audit_history_db_01.dat'
00:1999/11/24 08:04:34.11 kernel  Virtual device 52 started using
asynchronous i/o.
00:1999/11/24 08:04:34.11 server  Activating disk 'audit_history_log_01'.
00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 53,
'e:\devices\audit_history_log_01.dat'
00:1999/11/24 08:04:34.11 kernel  Virtual device 53 started using
asynchronous i/o.
00:1999/11/24 08:04:34.11 server  Activating disk 'dbadb_db_01'.
00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 7,
'e:\devices\dbadb_db_01.dat'
00:1999/11/24 08:04:34.11 kernel  Virtual device 7 started using
asynchronous i/o.
00:1999/11/24 08:04:34.11 server  Activating disk 'dbadb_log_01'.
00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 8,
'e:\devices\dbadb_log_01.dat'
00:1999/11/24 08:04:34.11 kernel  Virtual device 8 started using
asynchronous i/o.
00:1999/11/24 08:04:34.11 server  Activating disk 'document_db_01'.
00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 9,
'e:\devices\document_db_01.dat'
00:1999/11/24 08:04:34.11 kernel  Virtual device 9 started using
asynchronous i/o.
00:1999/11/24 08:04:34.11 server  Activating disk 'document_log_01'.
00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 10,
'e:\devices\document_log_01.dat'
00:1999/11/24 08:04:34.11 kernel  Virtual device 10 started using
asynchronous i/o.
00:1999/11/24 08:04:34.11 server  Activating disk 'files_db_01'.
00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 11,
'e:\devices\files_db_01.dat'
00:1999/11/24 08:04:34.11 kernel  Virtual device 11 started using
asynchronous i/o.
00:1999/11/24 08:04:34.11 server  Activating disk 'files_log_01'.
00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 12,
'e:\devices\files_log_01.dat'
00:1999/11/24 08:04:34.11 kernel  Virtual device 12 started using
asynchronous i/o.
00:1999/11/24 08:04:34.11 server  Activating disk 'ga01abs_db_01'.
00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 13,
'e:\devices\ga01abs_db_01.dat'
00:1999/11/24 08:04:34.11 kernel  Virtual device 13 started using
asynchronous i/o.
00:1999/11/24 08:04:34.11 server  Activating disk 'ga01abs_db_02'.
00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 3,
'e:\devices\ga01abs_db_02.dat'
00:1999/11/24 08:04:34.11 kernel  Virtual device 3 started using
asynchronous i/o.
00:1999/11/24 08:04:34.11 server  Activating disk 'ga01abs_log_01'.
00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 14,
'e:\devices\ga01abs_log_01.dat'
00:1999/11/24 08:04:34.11 kernel  Virtual device 14 started using
asynchronous i/o.
00:1999/11/24 08:04:34.11 server  Activating disk 'ga01doc_db_01'.
00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 15,
'e:\devices\ga01doc_db_01.dat'
00:1999/11/24 08:04:34.11 kernel  Virtual device 15 started using
asynchronous i/o.
00:1999/11/24 08:04:34.12 server  Activating disk 'ga01doc_db_02'.
00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 55,
'e:\devices\ga01doc_db_02.dat'
00:1999/11/24 08:04:34.12 kernel  Virtual device 55 started using
asynchronous i/o.
00:1999/11/24 08:04:34.12 server  Activating disk 'ga01doc_log_01'.
00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 16,
'e:\devices\ga01doc_log_01.dat'
00:1999/11/24 08:04:34.12 kernel  Virtual device 16 started using
asynchronous i/o.
00:1999/11/24 08:04:34.12 server  Activating disk 'ga01fil_db_01'.
00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 17,
'e:\devices\ga01fil_db_01.dat'
00:1999/11/24 08:04:34.12 kernel  Virtual device 17 started using
asynchronous i/o.
00:1999/11/24 08:04:34.12 server  Activating disk 'ga01fil_log_01'.
00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 18,
'e:\devices\ga01fil_log_01.dat'
00:1999/11/24 08:04:34.12 kernel  Virtual device 18 started using
asynchronous i/o.
00:1999/11/24 08:04:34.12 server  Activating disk 'gal_db_01'.
00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 19,
'e:\devices\ga1_db_01.dat'
00:1999/11/24 08:04:34.12 kernel  Virtual device 19 started using
asynchronous i/o.
00:1999/11/24 08:04:34.12 server  Activating disk 'gal_log_01'.
00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 20,
'e:\devices\gal_log_01.dat'
00:1999/11/24 08:04:34.12 kernel  Virtual device 20 started using
asynchronous i/o.
00:1999/11/24 08:04:34.12 server  Activating disk 'galqueue_db_01'.
00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 21,
'e:\devices\ga1queue_db_01.dat'
00:1999/11/24 08:04:34.12 kernel  Virtual device 21 started using
asynchronous i/o.
00:1999/11/24 08:04:34.12 server  Activating disk 'galqueue_log_01'.
00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 22,
'e:\devices\galqueue_log_01.dat'
00:1999/11/24 08:04:34.12 kernel  Virtual device 22 started using
asynchronous i/o.
00:1999/11/24 08:04:34.12 server  Activating disk 'gf01abs_db_01'.
00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 23,
'e:\devices\gf01abs_db_01.dat'
00:1999/11/24 08:04:34.12 kernel  Virtual device 23 started using
asynchronous i/o.
00:1999/11/24 08:04:34.12 server  Activating disk 'gf01abs_log_01'.
00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 24,
'e:\devices\gf01abs_log_01.dat'
00:1999/11/24 08:04:34.12 kernel  Virtual device 24 started using
asynchronous i/o.
00:1999/11/24 08:04:34.12 server  Activating disk 'gf01doc_db_01'.
00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 25,
'e:\devices\gf01doc_db_01.dat'
00:1999/11/24 08:04:34.12 kernel  Virtual device 25 started using
asynchronous i/o.
00:1999/11/24 08:04:34.12 server  Activating disk 'gf01doc_log_01'.
00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 26,
'e:\devices\gf01doc_log_01.dat'
00:1999/11/24 08:04:34.13 kernel  Virtual device 26 started using
asynchronous i/o.
00:1999/11/24 08:04:34.13 server  Activating disk 'gf01fil_db_01'.
00:1999/11/24 08:04:34.13 kernel  Initializing virtual device 27,
'e:\devices\gf01fil_db_01.dat'
00:1999/11/24 08:04:34.13 kernel  Virtual device 27 started using
asynchronous i/o.
00:1999/11/24 08:04:34.13 server  Activating disk 'gf01fil_log_01'.
00:1999/11/24 08:04:34.13 kernel  Initializing virtual device 28,
'e:\devices\gf01fil_log_01.dat'
00:1999/11/24 08:04:34.13 kernel  Virtual device 28 started using
asynchronous i/o.
00:1999/11/24 08:04:34.13 server  Activating disk 'gl01abs_db_01'.
00:1999/11/24 08:04:34.13 kernel  Initializing virtual device 29,
'e:\devices\gl01abs_db_01.dat'
00:1999/11/24 08:04:34.13 kernel  Virtual device 29 started using
asynchronous i/o.
00:1999/11/24 08:04:34.13 server  Activating disk 'gl01abs_log_01'.
00:1999/11/24 08:04:34.13 kernel  Initializing virtual device 30,
'e:\devices\gl01abs_log_01.dat'
00:1999/11/24 08:04:34.13 kernel  Virtual device 30 started using
asynchronous i/o.
00:1999/11/24 08:04:34.13 server  Activating disk 'gl01doc_db_01'.
00:1999/11/24 08:04:34.13 kernel  Initializing virtual device 31,
'e:\devices\gl01doc_db_01.dat'
00:1999/11/24 08:04:34.13 kernel  Virtual device 31 started using
asynchronous i/o.
00:1999/11/24 08:04:34.13 server  Activating disk 'gl01doc_log_01'.
00:1999/11/24 08:04:34.13 kernel  Initializing virtual device 32,
'e:\devices\gl01doc_log_01.dat'
00:1999/11/24 08:04:34.13 kernel  Virtual device 32 started using
asynchronous i/o.
00:1999/11/24 08:04:34.14 server  Activating disk 'gl01fil_db_01'.
00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 33,
'e:\devices\gl01fil_db_01.dat'
00:1999/11/24 08:04:34.14 kernel  Virtual device 33 started using
asynchronous i/o.
00:1999/11/24 08:04:34.14 server  Activating disk 'gl01fil_log_01'.
00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 34,
'e:\devices\gl01fil_log_01.dat'
00:1999/11/24 08:04:34.14 kernel  Virtual device 34 started using
asynchronous i/o.
00:1999/11/24 08:04:34.14 server  Activating disk 'grefabs_db_01'.
00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 35,
'e:\devices\grefabs_db_01.dat'
00:1999/11/24 08:04:34.14 kernel  Virtual device 35 started using
asynchronous i/o.
00:1999/11/24 08:04:34.14 server  Activating disk 'grefabs_log_01'.
00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 36,
'e:\devices\grefabs_log_01.dat'
00:1999/11/24 08:04:34.14 kernel  Virtual device 36 started using
asynchronous i/o.
00:1999/11/24 08:04:34.14 server  Activating disk 'grefdoc_db_01'.
00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 37,
'e:\devices\grefdoc_db_01.dat'
00:1999/11/24 08:04:34.14 kernel  Virtual device 37 started using
asynchronous i/o.
00:1999/11/24 08:04:34.14 server  Activating disk 'grefdoc_log_01'.
00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 38,
'e:\devices\grefdoc_log_01.dat'
00:1999/11/24 08:04:34.14 kernel  Virtual device 38 started using
asynchronous i/o.
00:1999/11/24 08:04:34.14 server  Activating disk 'greffil_db_01'.
00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 39,
'e:\devices\greffil_db_01.dat'
00:1999/11/24 08:04:34.14 kernel  Virtual device 39 started using
asynchronous i/o.
00:1999/11/24 08:04:34.14 server  Activating disk 'greffil_log_01'.
00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 40,
'e:\devices\greffil_log_01.dat'
00:1999/11/24 08:04:34.14 kernel  Virtual device 40 started using
asynchronous i/o.
00:1999/11/24 08:04:34.14 server  Activating disk 'polno_db_01'.
00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 41,
'e:\devices\polno_db_01.dat'
00:1999/11/24 08:04:34.14 kernel  Virtual device 41 started using
asynchronous i/o.
00:1999/11/24 08:04:34.14 server  Activating disk 'polno_log_01'.
00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 42,
'e:\devices\polno_log_01.dat'
00:1999/11/24 08:04:34.14 kernel  Virtual device 42 started using
asynchronous i/o.
00:1999/11/24 08:04:34.14 server  Activating disk 'sybsecurity'.
00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 2,
'e:\devices\sybsecur.dat'
00:1999/11/24 08:04:34.14 kernel  Virtual device 2 started using
asynchronous i/o.
00:1999/11/24 08:04:34.14 server  Activating disk 'sysfiles_db_01'.
00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 43,
'e:\devices\sysfiles_db_01.dat'
00:1999/11/24 08:04:34.14 kernel  Virtual device 43 started using
asynchronous i/o.
00:1999/11/24 08:04:34.14 server  Activating disk 'sysfiles_log_01'.
00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 44,
'e:\devices\sysfiles_log_01.dat'
00:1999/11/24 08:04:34.14 kernel  Virtual device 44 started using
asynchronous i/o.
00:1999/11/24 08:04:34.14 server  Activating disk 'sysprocsdev'.
00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 1,
'C:\SYBASE\DATA\SYBPROCS.DAT'
00:1999/11/24 08:04:34.14 kernel  Virtual device 1 started using
asynchronous i/o.
00:1999/11/24 08:04:34.14 server  Activating disk 'tempdb_01'.
00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 51,
'e:\devices\tempdb_01.dat'
00:1999/11/24 08:04:34.14 kernel  Virtual device 51 started using
asynchronous i/o.
00:1999/11/24 08:04:34.14 server  Activating disk 'vsreport_db_01'.
00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 56,
'e:\devices\vsreport_db_01.dat'
00:1999/11/24 08:04:34.14 kernel  Virtual device 56 started using
asynchronous i/o.
00:1999/11/24 08:04:34.14 server  Activating disk 'vsreport_log_01'.
00:1999/11/24 08:04:34.15 kernel  Initializing virtual device 57,
'e:\devices\vsreport_log_01.dat'
00:1999/11/24 08:04:34.15 kernel  Virtual device 57 started using
asynchronous i/o.
00:1999/11/24 08:04:34.15 server  Activating disk 'vsuser_db_01'.
00:1999/11/24 08:04:34.15 kernel  Initializing virtual device 45,
'e:\devices\vsuser_db_01.dat'
00:1999/11/24 08:04:34.15 kernel  Virtual device 45 started using
asynchronous i/o.
00:1999/11/24 08:04:34.15 server  Activating disk 'vsuser_db_02'.
00:1999/11/24 08:04:34.15 kernel  Initializing virtual device 54,
'e:\devices\vsuser_db_02.dat'
00:1999/11/24 08:04:34.15 kernel  Virtual device 54 started using
asynchronous i/o.
00:1999/11/24 08:04:34.15 server  Activating disk 'vsuser_log_01'.
00:1999/11/24 08:04:34.15 kernel  Initializing virtual device 46,
'e:\devices\vsuser_log_01.dat'
00:1999/11/24 08:04:34.15 kernel  Virtual device 46 started using
asynchronous i/o.
00:1999/11/24 08:04:34.15 server  Activating disk 'vsuser_log_02'.
00:1999/11/24 08:04:34.15 kernel  Initializing virtual device 59,
'e:\devices\vsuser_log_02.dat'
00:1999/11/24 08:04:34.15 kernel  Virtual device 59 started using
asynchronous i/o.
00:1999/11/24 08:04:34.15 server  Activating disk 'workflow_db_01'.
00:1999/11/24 08:04:34.15 kernel  Initializing virtual device 47,
'e:\devices\workflow_db_01.dat'
00:1999/11/24 08:04:34.15 kernel  Virtual device 47 started using
asynchronous i/o.
00:1999/11/24 08:04:34.15 server  Activating disk 'workflow_db_02'.
00:1999/11/24 08:04:34.15 kernel  Initializing virtual device 49,
'e:\devices\workflow_db_02.dat'
00:1999/11/24 08:04:34.15 kernel  Virtual device 49 started using
asynchronous i/o.
00:1999/11/24 08:04:34.15 server  Activating disk 'workflow_db_03'.
00:1999/11/24 08:04:34.15 kernel  Initializing virtual device 58,
'e:\devices\workflow_db_03.dat'
00:1999/11/24 08:04:34.15 kernel  Virtual device 58 started using
asynchronous i/o.
00:1999/11/24 08:04:34.15 server  Activating disk 'workflow_log_01'.
00:1999/11/24 08:04:34.15 kernel  Initializing virtual device 48,
'e:\devices\workflow_log_01.dat'
00:1999/11/24 08:04:34.15 kernel  Virtual device 48 started using
asynchronous i/o.
00:1999/11/24 08:04:34.15 server  Activating disk 'workflow_log_02'.
00:1999/11/24 08:04:34.15 kernel  Initializing virtual device 50,
'e:\devices\workflow_log_02.dat'
00:1999/11/24 08:04:34.15 kernel  Virtual device 50 started using
asynchronous i/o.
00:1999/11/24 08:04:34.26 server  Recovering database 'model'.
00:1999/11/24 08:04:34.27 server  Recovery dbid 3 ckpt (443,16)
00:1999/11/24 08:04:34.27 server  Recovery no active transactions before
ckpt.
00:1999/11/24 08:04:34.38 server  The transaction log in the database
'model' will use I/O size of 2 Kb.
00:1999/11/24 08:04:34.48 server  Database 'model' is now online.
00:1999/11/24 08:04:34.50 server  Clearing temp db
00:1999/11/24 08:04:35.18 server  The transaction log in the database
'tempdb' will use I/O size of 2 Kb.
00:1999/11/24 08:04:35.25 server  The transaction log in the database
'tempdb' will use I/O size of 2 Kb.
00:1999/11/24 08:04:35.34 server  Database 'tempdb' is now online.
00:1999/11/24 08:04:35.46 server  Error: 3443, Severity: 16, State: 1
00:1999/11/24 08:04:35.46 server  Invalid log version found for database
'sybsecurity': '3'. A log version greater than '2' is from an later,
incompatible version of SQL Server. Database cannot be opened.
00:1999/11/24 08:04:35.49 server  Error: 834, Severity: 20, State: 4
00:1999/11/24 08:04:35.49 server  Illegal attempt to clean buffer: BUF
pointer = '0x2FC91840', MASS pointer = '0x2FC91840', (Buf#: '0'), page ptr =
'0x2C3FA800', dbid = '28', Mass virtpage = '33554456', Buffer page = '24',
Mass status = '0x4101008', Buffer status = '0x1', size = '2048', cache (id:
0) = 'default data cache'.
00:1999/11/24 08:04:35.51 server  Error: 834, Severity: 20, State: 4
00:1999/11/24 08:04:35.51 server  Illegal attempt to clean buffer: BUF
pointer = '0x2FC91840', MASS pointer = '0x2FC91840', (Buf#: '0'), page ptr =
'0x2C3FA800', dbid = '28', Mass virtpage = '33554456', Buffer page = '24',
Mass status = '0x4101008', Buffer status = '0x1', size = '2048', cache (id:
0) = 'default data cache'.
00:1999/11/24 08:04:35.52 server  Error: 834, Severity: 20, State: 4
00:1999/11/24 08:04:35.52 server  Illegal attempt to clean buffer: BUF
pointer = '0x2FC91840', MASS pointer = '0x2FC91840', (Buf#: '0'), page ptr =
'0x2C3FA800', dbid = '28', Mass virtpage = '33554456', Buffer page = '24',
Mass status = '0x4101008', Buffer status = '0x1', size = '2048', cache (id:
0) = 'default data cache'.
/***************************************************************************
****************************************************************************
**********************/


This buffer message repeats indefinitely and the upgrade processes
eventually times out - see log1124.001 below


/***************************************************************************
****************************************************************************
**********************/
11/24/99 08:04:22 AM SyBatch/11.5.1/P/PC INTEL/Windows NT 4.0/3/OPT
11/24/99 08:04:22 AM Confidential property of Sybase, Inc.
                     Copyright Sybase Inc., 1987, 1998.
                     Sybase, Inc. All rights reserved.
                     Unpublished rights reserved under U.S. copyright laws

                     This software contains confidential and trade secret
                     information of Sybase, Inc. Use, duplication, or
diclosure
                     of the software and documentation by the U.S.
Government
                     is subject to restrictions as set forth in a license
                     agreement
                     between the Government and Sybase,Inc. or other written
                     agreement specifying the Government's rights to use the
                     software and any applicable FAR provisions, for
example,
                     FAR 52.227-19.
                     Sybase, Inc. 6475 Christie Avenue, Emeryville, CA 94608
                     USA.

11/24/99 08:04:22 AM BEGIN ENVIRONMENT INFORMATION

USER ENVIRONMENT
----------------------------------------
current directory:             C:\SYBASE
character set:                 iso_1
language:                      us_english
auditinit release directory:   C:\SYBASE
working release directory:     C:\SYBASE

DSQUERY:                       GARDBA
DSLISTEN:                      GARDBA

11/24/99 08:04:22 AM END ENVIRONMENT INFORMATION
11/24/99 08:06:09 AM CONNECTIVITY ERROR: DB-Library error: 'SQL Server
                     connection timed out.'.
11/24/99 08:06:13 AM Please reenter the account and/or password for server
                     'GARDBA' and try again.
11/24/99 08:06:20 AM Exiting.
11/24/99 08:06:20 AM The log file for this session is
                     'C:\SYBASE\init\logs\log1124.001'.
11/24/99 08:06:20 AM Log close.
/***************************************************************************
****************************************************************************
**********************/

RD



AnaMaria Stirbet wrote in message <383B09B2.3D3FCC42@sybase.com.no.spam>...
>Hi Ray,
>
>This is what you need to do:
>
>1. make a copy master.dat
>2. search for any duplicates of libunic.dll on that machine.
>libunic.dll should be in $Sybase\dll and most likely should be 238kb and
have a
>modified date of 01/05/1998
>3. try to start the server after all cleanup
>4. once you've started the server, stop it, restore master.dat, go to
syconfig
>and restart the upgrade process
>
>Hope this helps,
>
>AnaMaria Stirbet
>Sybase TS
>
>
>Ray DiMarcello wrote:
>
>> I'm trying an upgrade in place on a test server and all is fine until the
>> upgrade process tries to start the SQL server.  It passed the eligibility
>> test, then reported that there is one conflict with 11.5 reserved words.
I
>> figured I could find that and tend to it afterwards.  I clicked OK and
got a
>> window saying it is proceeding with the upgrade at which point it fails
and
>> says "Failed to boot server ..."   I tried to start it manually in Sybase
>> Central and it fails with "Procedure entry point uniutf8_unistrNFromUTF8
>> could not be loaded in the DLL libunic.dll."   I re-booted NT, tried
using
>> Server Config to restart/complete the upgrade and have the same problem.
>>
>> This is the bottom of the upgrade error log - everthing looks OK until
this:
>>
>> 11/23/99 10:59:52 AM Sending the following SQL command to the server:
'use
>>                      tempdb'.
>> 11/23/99 10:59:52 AM Sending the following SQL command to the server:
>>                      'checkpoint'.
>> 11/23/99 10:59:52 AM Sending the following SQL command to the server:
'use
>>                      vsreport'.
>> 11/23/99 10:59:52 AM Sending the following SQL command to the server:
>>                      'checkpoint'.
>> 11/23/99 10:59:52 AM Sending the following SQL command to the server:
'exec
>>                      sp_configure 'allow updates', 1'.
>> 11/23/99 10:59:52 AM Sending the following SQL command to the server:
>>                      'reconfigure with override'.
>> 11/23/99 10:59:52 AM Sending the following SQL command to the server:
>>                      'shutdown'.
>> 11/23/99 10:59:53 AM Waiting 10 seconds for the operating system to
reclaim
>>                      resources before rebooting.
>> 11/23/99 11:00:15 AM Calling the shell with 'C:\SYBASE\bin\sqlsrvr.exe
>>                      -dC:\SYBASE\DATA\MASTER.DAT -sGARDBA
>>                      -eC:\SYBASE\upgrade\errorlog.upg -iC:\SYBASE\ini
>>                      -MC:\SYBASE'.
>> 11/23/99 11:00:15 AM waiting for server 'GARDBA' to boot...
>> 11/23/99 11:00:53 AM SERVER ERROR: Failed to boot server 'GARDBA'.
>> 11/23/99 11:00:55 AM Task failed: upgrade the Adaptive Server.
Terminating
>>                      configuration.
>> 11/23/99 11:00:55 AM Configuration failed.
>> 11/23/99 11:00:57 AM Exiting.
>> 11/23/99 11:00:57 AM The log file for this session is
>>                      'C:\SYBASE\init\logs\log1123.003'.
>> 11/23/99 11:00:57 AM Log close.
>>
>> Have no idea where to go from here ...
>>
>> RD
>


0
Ray
11/24/1999 1:10:23 PM
Yes.
You can drop sybsecurity now, if you want to continue the upgrade.

AnaMaria Stirbet
Sybase TS


Ray DiMarcello wrote:

> Interesting ... guess I should have done the same with sybsecurity.  Now I'm
> past the dll error but get an invalid log version message for sybsecurity
> when it tries to start the server followed by a bunch of buffer errors for
> default data cache. See log below.
>
> /***************************************************************************
> ****************************************************************************
> **********************/
> 00:1999/11/24 08:04:30.00 kernel  Using config area from primary master
> device.
> 00:1999/11/24 08:04:30.18 kernel  Warning: Using default file
> 'C:\SYBASE.SAV\/GARDBA.cfg' since a configuration file was not specified.
> Specify a configuration file name in the RUNSERVER file to avoid this
> message.
> 00:1999/11/24 08:04:32.38 kernel  Kernel memory at 0x20000000, 172032 bytes
> 00:1999/11/24 08:04:32.38 kernel  Server part of first shared memory region
> at 0x2002a000, 267280384 bytes
> 00:1999/11/24 08:04:32.38 kernel  Highest valid address is 0x2002a000
> 00:1999/11/24 08:04:32.38 kernel  Using 2048 file descriptors.
> 00:1999/11/24 08:04:32.43 kernel  SQL Server/11.0.3.3/P/PC Intel/Windows NT
> 3.5/SWR 8299 ESD 4/OPT/Thu Mar 11 1999 3:40:09.82
> 00:1999/11/24 08:04:32.43 kernel  (c) Copyright 1987, 1999.
> 00:1999/11/24 08:04:32.43 kernel  Sybase, Inc.  All rights reserved.
> 00:1999/11/24 08:04:32.43 kernel
> 00:1999/11/24 08:04:32.44 kernel  Unpublished rights reserved under U.S.
> copyright laws.
> 00:1999/11/24 08:04:32.44 kernel  This software contains confidential and
> trade secret information of Sybase,
> 00:1999/11/24 08:04:32.44 kernel  Inc.   Use,  duplication or disclosure of
> the software and documentation by
> 00:1999/11/24 08:04:32.44 kernel  the  U.S.  Government  is  subject  to
> restrictions set forth in a license
> 00:1999/11/24 08:04:32.44 kernel  agreement  between  the  Government  and
> Sybase,  Inc.  or  other  written
> 00:1999/11/24 08:04:32.44 kernel  agreement  specifying  the  Government's
> rights to use the software and any
> 00:1999/11/24 08:04:32.44 kernel  applicable FAR provisions, for example,
> FAR 52.227-19.
> 00:1999/11/24 08:04:32.44 kernel
> 00:1999/11/24 08:04:32.44 kernel  Sybase, Inc. 6475 Christie Avenue,
> Emeryville, CA 94608, USA.
> 00:1999/11/24 08:04:32.44 kernel  Using 'C:\SYBASE.SAV\/GARDBA.cfg' for
> configuration information.
> 00:1999/11/24 08:04:32.49 kernel  Logging SQL Server messages in file
> 'C:\SYBASE\upgrade\errorlog.upg'
> .
> 00:1999/11/24 08:04:32.89 kernel  *** WARNING ******************
> 00:1999/11/24 08:04:32.89 kernel  Operating system may favor the system
> cache when memory is at a premium.
>  To disable this warning, set the registry parameter 'LargeSystemCache' to 0
> in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
> Manager\Memory Management.
> 00:1999/11/24 08:04:32.89 kernel  SQL Server NT process id is 0xd2.
> 00:1999/11/24 08:04:32.89 kernel  SQL Server was started as a Service.
> 00:1999/11/24 08:04:32.89 kernel  Network and device connection limit is
> 2040.
> 00:1999/11/24 08:04:32.95 server  Number of proc buffers allocated: 25487.
> 00:1999/11/24 08:04:33.06 server  Number of blocks left for proc headers:
> 25569.
> 00:1999/11/24 08:04:33.06 server  Memory allocated for the default data
> cache cache: 193776 Kb
> 00:1999/11/24 08:04:33.14 server  Size of the 2K memory pool: 142576 Kb
> 00:1999/11/24 08:04:33.17 server  Size of the 16K memory pool: 51200 Kb
> 00:1999/11/24 08:04:33.18 kernel  Initializing virtual device 0,
> 'C:\SYBASE\DATA\MASTER.DAT'
> 00:1999/11/24 08:04:33.18 kernel  Virtual device 0 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:33.19 server  No active traceflags
> 00:1999/11/24 08:04:33.37 server  Opening Master Database ...
> 00:1999/11/24 08:04:33.54 server  Loading SQL Server's default sort order
> and character set
> 00:1999/11/24 08:04:33.66 server  Recovering database 'master'
> 00:1999/11/24 08:04:33.69 server  Recovery dbid 1 ckpt (1488,9)
> 00:1999/11/24 08:04:33.69 server  Recovery no active transactions before
> ckpt.
> 00:1999/11/24 08:04:33.98 server  Database 'master' is now online.
> 00:1999/11/24 08:04:33.99 server  The transaction log in the database
> 'master' will use I/O size of 2 Kb.
> 00:1999/11/24 08:04:34.05 server  0 dump conditions detected at boot time
> 00:1999/11/24 08:04:34.07 server  server name is 'GARDBA'
> 00:1999/11/24 08:04:34.11 server  Activating disk 'abstract_db_01'.
> 00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 5,
> 'e:\devices\abstract_db_01.dat'
> 00:1999/11/24 08:04:34.11 kernel  Virtual device 5 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.11 server  Activating disk 'abstract_log_01'.
> 00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 6,
> 'e:\devices\abstract_log_01.dat'
> 00:1999/11/24 08:04:34.11 kernel  Virtual device 6 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.11 server  Activating disk 'audit_history_db_01'.
> 00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 52,
> 'e:\devices\audit_history_db_01.dat'
> 00:1999/11/24 08:04:34.11 kernel  Virtual device 52 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.11 server  Activating disk 'audit_history_log_01'.
> 00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 53,
> 'e:\devices\audit_history_log_01.dat'
> 00:1999/11/24 08:04:34.11 kernel  Virtual device 53 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.11 server  Activating disk 'dbadb_db_01'.
> 00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 7,
> 'e:\devices\dbadb_db_01.dat'
> 00:1999/11/24 08:04:34.11 kernel  Virtual device 7 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.11 server  Activating disk 'dbadb_log_01'.
> 00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 8,
> 'e:\devices\dbadb_log_01.dat'
> 00:1999/11/24 08:04:34.11 kernel  Virtual device 8 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.11 server  Activating disk 'document_db_01'.
> 00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 9,
> 'e:\devices\document_db_01.dat'
> 00:1999/11/24 08:04:34.11 kernel  Virtual device 9 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.11 server  Activating disk 'document_log_01'.
> 00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 10,
> 'e:\devices\document_log_01.dat'
> 00:1999/11/24 08:04:34.11 kernel  Virtual device 10 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.11 server  Activating disk 'files_db_01'.
> 00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 11,
> 'e:\devices\files_db_01.dat'
> 00:1999/11/24 08:04:34.11 kernel  Virtual device 11 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.11 server  Activating disk 'files_log_01'.
> 00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 12,
> 'e:\devices\files_log_01.dat'
> 00:1999/11/24 08:04:34.11 kernel  Virtual device 12 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.11 server  Activating disk 'ga01abs_db_01'.
> 00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 13,
> 'e:\devices\ga01abs_db_01.dat'
> 00:1999/11/24 08:04:34.11 kernel  Virtual device 13 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.11 server  Activating disk 'ga01abs_db_02'.
> 00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 3,
> 'e:\devices\ga01abs_db_02.dat'
> 00:1999/11/24 08:04:34.11 kernel  Virtual device 3 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.11 server  Activating disk 'ga01abs_log_01'.
> 00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 14,
> 'e:\devices\ga01abs_log_01.dat'
> 00:1999/11/24 08:04:34.11 kernel  Virtual device 14 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.11 server  Activating disk 'ga01doc_db_01'.
> 00:1999/11/24 08:04:34.11 kernel  Initializing virtual device 15,
> 'e:\devices\ga01doc_db_01.dat'
> 00:1999/11/24 08:04:34.11 kernel  Virtual device 15 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.12 server  Activating disk 'ga01doc_db_02'.
> 00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 55,
> 'e:\devices\ga01doc_db_02.dat'
> 00:1999/11/24 08:04:34.12 kernel  Virtual device 55 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.12 server  Activating disk 'ga01doc_log_01'.
> 00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 16,
> 'e:\devices\ga01doc_log_01.dat'
> 00:1999/11/24 08:04:34.12 kernel  Virtual device 16 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.12 server  Activating disk 'ga01fil_db_01'.
> 00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 17,
> 'e:\devices\ga01fil_db_01.dat'
> 00:1999/11/24 08:04:34.12 kernel  Virtual device 17 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.12 server  Activating disk 'ga01fil_log_01'.
> 00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 18,
> 'e:\devices\ga01fil_log_01.dat'
> 00:1999/11/24 08:04:34.12 kernel  Virtual device 18 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.12 server  Activating disk 'gal_db_01'.
> 00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 19,
> 'e:\devices\ga1_db_01.dat'
> 00:1999/11/24 08:04:34.12 kernel  Virtual device 19 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.12 server  Activating disk 'gal_log_01'.
> 00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 20,
> 'e:\devices\gal_log_01.dat'
> 00:1999/11/24 08:04:34.12 kernel  Virtual device 20 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.12 server  Activating disk 'galqueue_db_01'.
> 00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 21,
> 'e:\devices\ga1queue_db_01.dat'
> 00:1999/11/24 08:04:34.12 kernel  Virtual device 21 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.12 server  Activating disk 'galqueue_log_01'.
> 00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 22,
> 'e:\devices\galqueue_log_01.dat'
> 00:1999/11/24 08:04:34.12 kernel  Virtual device 22 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.12 server  Activating disk 'gf01abs_db_01'.
> 00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 23,
> 'e:\devices\gf01abs_db_01.dat'
> 00:1999/11/24 08:04:34.12 kernel  Virtual device 23 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.12 server  Activating disk 'gf01abs_log_01'.
> 00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 24,
> 'e:\devices\gf01abs_log_01.dat'
> 00:1999/11/24 08:04:34.12 kernel  Virtual device 24 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.12 server  Activating disk 'gf01doc_db_01'.
> 00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 25,
> 'e:\devices\gf01doc_db_01.dat'
> 00:1999/11/24 08:04:34.12 kernel  Virtual device 25 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.12 server  Activating disk 'gf01doc_log_01'.
> 00:1999/11/24 08:04:34.12 kernel  Initializing virtual device 26,
> 'e:\devices\gf01doc_log_01.dat'
> 00:1999/11/24 08:04:34.13 kernel  Virtual device 26 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.13 server  Activating disk 'gf01fil_db_01'.
> 00:1999/11/24 08:04:34.13 kernel  Initializing virtual device 27,
> 'e:\devices\gf01fil_db_01.dat'
> 00:1999/11/24 08:04:34.13 kernel  Virtual device 27 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.13 server  Activating disk 'gf01fil_log_01'.
> 00:1999/11/24 08:04:34.13 kernel  Initializing virtual device 28,
> 'e:\devices\gf01fil_log_01.dat'
> 00:1999/11/24 08:04:34.13 kernel  Virtual device 28 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.13 server  Activating disk 'gl01abs_db_01'.
> 00:1999/11/24 08:04:34.13 kernel  Initializing virtual device 29,
> 'e:\devices\gl01abs_db_01.dat'
> 00:1999/11/24 08:04:34.13 kernel  Virtual device 29 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.13 server  Activating disk 'gl01abs_log_01'.
> 00:1999/11/24 08:04:34.13 kernel  Initializing virtual device 30,
> 'e:\devices\gl01abs_log_01.dat'
> 00:1999/11/24 08:04:34.13 kernel  Virtual device 30 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.13 server  Activating disk 'gl01doc_db_01'.
> 00:1999/11/24 08:04:34.13 kernel  Initializing virtual device 31,
> 'e:\devices\gl01doc_db_01.dat'
> 00:1999/11/24 08:04:34.13 kernel  Virtual device 31 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.13 server  Activating disk 'gl01doc_log_01'.
> 00:1999/11/24 08:04:34.13 kernel  Initializing virtual device 32,
> 'e:\devices\gl01doc_log_01.dat'
> 00:1999/11/24 08:04:34.13 kernel  Virtual device 32 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.14 server  Activating disk 'gl01fil_db_01'.
> 00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 33,
> 'e:\devices\gl01fil_db_01.dat'
> 00:1999/11/24 08:04:34.14 kernel  Virtual device 33 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.14 server  Activating disk 'gl01fil_log_01'.
> 00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 34,
> 'e:\devices\gl01fil_log_01.dat'
> 00:1999/11/24 08:04:34.14 kernel  Virtual device 34 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.14 server  Activating disk 'grefabs_db_01'.
> 00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 35,
> 'e:\devices\grefabs_db_01.dat'
> 00:1999/11/24 08:04:34.14 kernel  Virtual device 35 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.14 server  Activating disk 'grefabs_log_01'.
> 00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 36,
> 'e:\devices\grefabs_log_01.dat'
> 00:1999/11/24 08:04:34.14 kernel  Virtual device 36 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.14 server  Activating disk 'grefdoc_db_01'.
> 00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 37,
> 'e:\devices\grefdoc_db_01.dat'
> 00:1999/11/24 08:04:34.14 kernel  Virtual device 37 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.14 server  Activating disk 'grefdoc_log_01'.
> 00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 38,
> 'e:\devices\grefdoc_log_01.dat'
> 00:1999/11/24 08:04:34.14 kernel  Virtual device 38 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.14 server  Activating disk 'greffil_db_01'.
> 00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 39,
> 'e:\devices\greffil_db_01.dat'
> 00:1999/11/24 08:04:34.14 kernel  Virtual device 39 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.14 server  Activating disk 'greffil_log_01'.
> 00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 40,
> 'e:\devices\greffil_log_01.dat'
> 00:1999/11/24 08:04:34.14 kernel  Virtual device 40 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.14 server  Activating disk 'polno_db_01'.
> 00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 41,
> 'e:\devices\polno_db_01.dat'
> 00:1999/11/24 08:04:34.14 kernel  Virtual device 41 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.14 server  Activating disk 'polno_log_01'.
> 00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 42,
> 'e:\devices\polno_log_01.dat'
> 00:1999/11/24 08:04:34.14 kernel  Virtual device 42 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.14 server  Activating disk 'sybsecurity'.
> 00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 2,
> 'e:\devices\sybsecur.dat'
> 00:1999/11/24 08:04:34.14 kernel  Virtual device 2 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.14 server  Activating disk 'sysfiles_db_01'.
> 00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 43,
> 'e:\devices\sysfiles_db_01.dat'
> 00:1999/11/24 08:04:34.14 kernel  Virtual device 43 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.14 server  Activating disk 'sysfiles_log_01'.
> 00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 44,
> 'e:\devices\sysfiles_log_01.dat'
> 00:1999/11/24 08:04:34.14 kernel  Virtual device 44 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.14 server  Activating disk 'sysprocsdev'.
> 00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 1,
> 'C:\SYBASE\DATA\SYBPROCS.DAT'
> 00:1999/11/24 08:04:34.14 kernel  Virtual device 1 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.14 server  Activating disk 'tempdb_01'.
> 00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 51,
> 'e:\devices\tempdb_01.dat'
> 00:1999/11/24 08:04:34.14 kernel  Virtual device 51 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.14 server  Activating disk 'vsreport_db_01'.
> 00:1999/11/24 08:04:34.14 kernel  Initializing virtual device 56,
> 'e:\devices\vsreport_db_01.dat'
> 00:1999/11/24 08:04:34.14 kernel  Virtual device 56 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.14 server  Activating disk 'vsreport_log_01'.
> 00:1999/11/24 08:04:34.15 kernel  Initializing virtual device 57,
> 'e:\devices\vsreport_log_01.dat'
> 00:1999/11/24 08:04:34.15 kernel  Virtual device 57 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.15 server  Activating disk 'vsuser_db_01'.
> 00:1999/11/24 08:04:34.15 kernel  Initializing virtual device 45,
> 'e:\devices\vsuser_db_01.dat'
> 00:1999/11/24 08:04:34.15 kernel  Virtual device 45 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.15 server  Activating disk 'vsuser_db_02'.
> 00:1999/11/24 08:04:34.15 kernel  Initializing virtual device 54,
> 'e:\devices\vsuser_db_02.dat'
> 00:1999/11/24 08:04:34.15 kernel  Virtual device 54 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.15 server  Activating disk 'vsuser_log_01'.
> 00:1999/11/24 08:04:34.15 kernel  Initializing virtual device 46,
> 'e:\devices\vsuser_log_01.dat'
> 00:1999/11/24 08:04:34.15 kernel  Virtual device 46 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.15 server  Activating disk 'vsuser_log_02'.
> 00:1999/11/24 08:04:34.15 kernel  Initializing virtual device 59,
> 'e:\devices\vsuser_log_02.dat'
> 00:1999/11/24 08:04:34.15 kernel  Virtual device 59 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.15 server  Activating disk 'workflow_db_01'.
> 00:1999/11/24 08:04:34.15 kernel  Initializing virtual device 47,
> 'e:\devices\workflow_db_01.dat'
> 00:1999/11/24 08:04:34.15 kernel  Virtual device 47 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.15 server  Activating disk 'workflow_db_02'.
> 00:1999/11/24 08:04:34.15 kernel  Initializing virtual device 49,
> 'e:\devices\workflow_db_02.dat'
> 00:1999/11/24 08:04:34.15 kernel  Virtual device 49 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.15 server  Activating disk 'workflow_db_03'.
> 00:1999/11/24 08:04:34.15 kernel  Initializing virtual device 58,
> 'e:\devices\workflow_db_03.dat'
> 00:1999/11/24 08:04:34.15 kernel  Virtual device 58 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.15 server  Activating disk 'workflow_log_01'.
> 00:1999/11/24 08:04:34.15 kernel  Initializing virtual device 48,
> 'e:\devices\workflow_log_01.dat'
> 00:1999/11/24 08:04:34.15 kernel  Virtual device 48 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.15 server  Activating disk 'workflow_log_02'.
> 00:1999/11/24 08:04:34.15 kernel  Initializing virtual device 50,
> 'e:\devices\workflow_log_02.dat'
> 00:1999/11/24 08:04:34.15 kernel  Virtual device 50 started using
> asynchronous i/o.
> 00:1999/11/24 08:04:34.26 server  Recovering database 'model'.
> 00:1999/11/24 08:04:34.27 server  Recovery dbid 3 ckpt (443,16)
> 00:1999/11/24 08:04:34.27 server  Recovery no active transactions before
> ckpt.
> 00:1999/11/24 08:04:34.38 server  The transaction log in the database
> 'model' will use I/O size of 2 Kb.
> 00:1999/11/24 08:04:34.48 server  Database 'model' is now online.
> 00:1999/11/24 08:04:34.50 server  Clearing temp db
> 00:1999/11/24 08:04:35.18 server  The transaction log in the database
> 'tempdb' will use I/O size of 2 Kb.
> 00:1999/11/24 08:04:35.25 server  The transaction log in the database
> 'tempdb' will use I/O size of 2 Kb.
> 00:1999/11/24 08:04:35.34 server  Database 'tempdb' is now online.
> 00:1999/11/24 08:04:35.46 server  Error: 3443, Severity: 16, State: 1
> 00:1999/11/24 08:04:35.46 server  Invalid log version found for database
> 'sybsecurity': '3'. A log version greater than '2' is from an later,
> incompatible version of SQL Server. Database cannot be opened.
> 00:1999/11/24 08:04:35.49 server  Error: 834, Severity: 20, State: 4
> 00:1999/11/24 08:04:35.49 server  Illegal attempt to clean buffer: BUF
> pointer = '0x2FC91840', MASS pointer = '0x2FC91840', (Buf#: '0'), page ptr =
> '0x2C3FA800', dbid = '28', Mass virtpage = '33554456', Buffer page = '24',
> Mass status = '0x4101008', Buffer status = '0x1', size = '2048', cache (id:
> 0) = 'default data cache'.
> 00:1999/11/24 08:04:35.51 server  Error: 834, Severity: 20, State: 4
> 00:1999/11/24 08:04:35.51 server  Illegal attempt to clean buffer: BUF
> pointer = '0x2FC91840', MASS pointer = '0x2FC91840', (Buf#: '0'), page ptr =
> '0x2C3FA800', dbid = '28', Mass virtpage = '33554456', Buffer page = '24',
> Mass status = '0x4101008', Buffer status = '0x1', size = '2048', cache (id:
> 0) = 'default data cache'.
> 00:1999/11/24 08:04:35.52 server  Error: 834, Severity: 20, State: 4
> 00:1999/11/24 08:04:35.52 server  Illegal attempt to clean buffer: BUF
> pointer = '0x2FC91840', MASS pointer = '0x2FC91840', (Buf#: '0'), page ptr =
> '0x2C3FA800', dbid = '28', Mass virtpage = '33554456', Buffer page = '24',
> Mass status = '0x4101008', Buffer status = '0x1', size = '2048', cache (id:
> 0) = 'default data cache'.
> /***************************************************************************
> ****************************************************************************
> **********************/
>
> This buffer message repeats indefinitely and the upgrade processes
> eventually times out - see log1124.001 below
>
> /***************************************************************************
> ****************************************************************************
> **********************/
> 11/24/99 08:04:22 AM SyBatch/11.5.1/P/PC INTEL/Windows NT 4.0/3/OPT
> 11/24/99 08:04:22 AM Confidential property of Sybase, Inc.
>                      Copyright Sybase Inc., 1987, 1998.
>                      Sybase, Inc. All rights reserved.
>                      Unpublished rights reserved under U.S. copyright laws
>
>                      This software contains confidential and trade secret
>                      information of Sybase, Inc. Use, duplication, or
> diclosure
>                      of the software and documentation by the U.S.
> Government
>                      is subject to restrictions as set forth in a license
>                      agreement
>                      between the Government and Sybase,Inc. or other written
>                      agreement specifying the Government's rights to use the
>                      software and any applicable FAR provisions, for
> example,
>                      FAR 52.227-19.
>                      Sybase, Inc. 6475 Christie Avenue, Emeryville, CA 94608
>                      USA.
>
> 11/24/99 08:04:22 AM BEGIN ENVIRONMENT INFORMATION
>
> USER ENVIRONMENT
> ----------------------------------------
> current directory:             C:\SYBASE
> character set:                 iso_1
> language:                      us_english
> auditinit release directory:   C:\SYBASE
> working release directory:     C:\SYBASE
>
> DSQUERY:                       GARDBA
> DSLISTEN:                      GARDBA
>
> 11/24/99 08:04:22 AM END ENVIRONMENT INFORMATION
> 11/24/99 08:06:09 AM CONNECTIVITY ERROR: DB-Library error: 'SQL Server
>                      connection timed out.'.
> 11/24/99 08:06:13 AM Please reenter the account and/or password for server
>                      'GARDBA' and try again.
> 11/24/99 08:06:20 AM Exiting.
> 11/24/99 08:06:20 AM The log file for this session is
>                      'C:\SYBASE\init\logs\log1124.001'.
> 11/24/99 08:06:20 AM Log close.
> /***************************************************************************
> ****************************************************************************
> **********************/
>
> RD
>
> AnaMaria Stirbet wrote in message <383B09B2.3D3FCC42@sybase.com.no.spam>...
> >Hi Ray,
> >
> >This is what you need to do:
> >
> >1. make a copy master.dat
> >2. search for any duplicates of libunic.dll on that machine.
> >libunic.dll should be in $Sybase\dll and most likely should be 238kb and
> have a
> >modified date of 01/05/1998
> >3. try to start the server after all cleanup
> >4. once you've started the server, stop it, restore master.dat, go to
> syconfig
> >and restart the upgrade process
> >
> >Hope this helps,
> >
> >AnaMaria Stirbet
> >Sybase TS
> >
> >
> >Ray DiMarcello wrote:
> >
> >> I'm trying an upgrade in place on a test server and all is fine until the
> >> upgrade process tries to start the SQL server.  It passed the eligibility
> >> test, then reported that there is one conflict with 11.5 reserved words.
> I
> >> figured I could find that and tend to it afterwards.  I clicked OK and
> got a
> >> window saying it is proceeding with the upgrade at which point it fails
> and
> >> says "Failed to boot server ..."   I tried to start it manually in Sybase
> >> Central and it fails with "Procedure entry point uniutf8_unistrNFromUTF8
> >> could not be loaded in the DLL libunic.dll."   I re-booted NT, tried
> using
> >> Server Config to restart/complete the upgrade and have the same problem.
> >>
> >> This is the bottom of the upgrade error log - everthing looks OK until
> this:
> >>
> >> 11/23/99 10:59:52 AM Sending the following SQL command to the server:
> 'use
> >>                      tempdb'.
> >> 11/23/99 10:59:52 AM Sending the following SQL command to the server:
> >>                      'checkpoint'.
> >> 11/23/99 10:59:52 AM Sending the following SQL command to the server:
> 'use
> >>                      vsreport'.
> >> 11/23/99 10:59:52 AM Sending the following SQL command to the server:
> >>                      'checkpoint'.
> >> 11/23/99 10:59:52 AM Sending the following SQL command to the server:
> 'exec
> >>                      sp_configure 'allow updates', 1'.
> >> 11/23/99 10:59:52 AM Sending the following SQL command to the server:
> >>                      'reconfigure with override'.
> >> 11/23/99 10:59:52 AM Sending the following SQL command to the server:
> >>                      'shutdown'.
> >> 11/23/99 10:59:53 AM Waiting 10 seconds for the operating system to
> reclaim
> >>                      resources before rebooting.
> >> 11/23/99 11:00:15 AM Calling the shell with 'C:\SYBASE\bin\sqlsrvr.exe
> >>                      -dC:\SYBASE\DATA\MASTER.DAT -sGARDBA
> >>                      -eC:\SYBASE\upgrade\errorlog.upg -iC:\SYBASE\ini
> >>                      -MC:\SYBASE'.
> >> 11/23/99 11:00:15 AM waiting for server 'GARDBA' to boot...
> >> 11/23/99 11:00:53 AM SERVER ERROR: Failed to boot server 'GARDBA'.
> >> 11/23/99 11:00:55 AM Task failed: upgrade the Adaptive Server.
> Terminating
> >>                      configuration.
> >> 11/23/99 11:00:55 AM Configuration failed.
> >> 11/23/99 11:00:57 AM Exiting.
> >> 11/23/99 11:00:57 AM The log file for this session is
> >>                      'C:\SYBASE\init\logs\log1123.003'.
> >> 11/23/99 11:00:57 AM Log close.
> >>
> >> Have no idea where to go from here ...
> >>
> >> RD
> >

0
AnaMaria
11/24/1999 8:01:04 PM
Reply:

Similar Artilces:

Smoke [5.11.3] v5.11.3-3-gc3c0aa2 FAIL(XF) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.3 patch c3c0aa283b73660f84ae7e190dcbbd607facb512 v5.11.3-3-gc3c0aa2 p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 6 hours 47 minutes (average 50 minutes 57 seconds) Summary: FAIL(XF) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = ma...

Smoke [5.11.3] v5.11.3-5-g27bca32 FAIL(XF) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.3 patch 27bca3226281a592aed848b7e68ea50f27381dac v5.11.3-5-g27bca32 p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 6 hours 44 minutes (average 50 minutes 37 seconds) Summary: FAIL(XF) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = ma...

3.0.11 keeps updating 3.5 beta 4 to 3.0.11
Name: thomas sturges Email: tsturgesatearthlinkdotnet Product: Firefox Summary: 3.0.11 keeps updating 3.5 beta 4 to 3.0.11 Comments: see above Browser Details: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b4) Gecko/20090423 Firefox/3.5b4 (.NET CLR 3.5.30729) From URL: Note to readers: Hendrix gives no expectation of a response to this feedback but if you wish to provide one you must BCC (not CC) the sender for them to see it. ...

Smoke [5.11.3] v5.11.3-51-g4149198 FAIL(Fm) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.3 patch 4149198fba64273f3fea8fc073ccb5d080059f4a v5.11.3-51-g4149198 p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 4 hours 37 minutes (average 34 minutes 38 seconds) Summary: FAIL(Fm) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = m...

Smoke [5.11.3] v5.11.3-63-g3365b41 FAIL(XM) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.3 patch 3365b4123660b600293d3f9bd5054523f194b5b9 v5.11.3-63-g3365b41 p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 6 hours (average 45 minutes 7 seconds) Summary: FAIL(XM) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = make test-pre...

Smoke [5.11.3] v5.11.3-55-gb1b34a5 FAIL(XF) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.3 patch b1b34a557d6a0b1b784977e95bea3db696ad19c9 v5.11.3-55-gb1b34a5 p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 6 hours 36 minutes (average 49 minutes 35 seconds) Summary: FAIL(XF) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = m...

Smoke [5.11.3] v5.11.3-98-g83452f8 FAIL(XF) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.3 patch 83452f8ea6ad77da7b6d12f161eedb3db3e647f3 v5.11.3-98-g83452f8 p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 6 hours 35 minutes (average 49 minutes 27 seconds) Summary: FAIL(XF) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = m...

Smoke [5.11.3] v5.11.3-10-g9f815e2 FAIL(XF) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.3 patch 9f815e241cf04d04fc645970753438216a0ed024 v5.11.3-10-g9f815e2 p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 6 hours 46 minutes (average 50 minutes 51 seconds) Summary: FAIL(XF) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = m...

Smoke [5.11.3] v5.11.3-42-g06fc686 FAIL(XF) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.3 patch 06fc68671f70339bdc6ddf5b7367ae9db8b4cd2a v5.11.3-42-g06fc686 p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 6 hours 36 minutes (average 49 minutes 31 seconds) Summary: FAIL(XF) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = m...

Smoke [5.11.3] v5.11.3-17-g2dba5d6 FAIL(XF) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.3 patch 2dba5d6056865b047ab6a58cf258c870472b3fe2 v5.11.3-17-g2dba5d6 p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 6 hours 34 minutes (average 49 minutes 21 seconds) Summary: FAIL(XF) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = m...

Smoke [5.11.3] v5.11.3-22-gfd90943 FAIL(XM) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.3 patch fd909433c74372968d34d9cad8f4458ab60e19b4 v5.11.3-22-gfd90943 p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 5 hours 41 minutes (average 42 minutes 39 seconds) Summary: FAIL(XM) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = m...

Smoke [5.11.3] v5.11.3-34-gf099890 FAIL(XF) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.3 patch f09989092a6586d2bb4173c4c08882afef55b70f v5.11.3-34-gf099890 p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 6 hours 35 minutes (average 49 minutes 26 seconds) Summary: FAIL(XF) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = m...

Smoke [5.11.3] v5.11.3-126-g1f730e6 FAIL(XF) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.3 patch 1f730e6c11736bad913e605b064200a67117e898 v5.11.3-126-g1f730e6 p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 6 hours 35 minutes (average 49 minutes 29 seconds) Summary: FAIL(XF) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = ...

Smoke [5.11.3] v5.11.3-108-gcb4a303 FAIL(XF) netbsd 5.0.1 (i386/1 cpu)
Automated smoke report for 5.11.3 patch cb4a303650e05576b6797aaca1373576a2f37af7 v5.11.3-108-gcb4a303 p5netbsd: Intel 686-class (i386/1 cpu) on netbsd - 5.0.1 using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120) smoketime 6 hours 37 minutes (average 49 minutes 40 seconds) Summary: FAIL(XF) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = ...

Web resources about - 11.0.3.3 to 11.5.1 (NT4.0) - sybase.sqlserver.configuration

Windows 9x - Wikipedia, the free encyclopedia
Windows 9x is a generic term referring to a series of Microsoft Windows computer operating systems produced since 1995, which were based on the ...

Link Shell Extension
The NTFS file system implemented in NT4, Windows 2000, Windows XP, Windows XP64, and Windows7 supports a facility known as hard links (referred ...

Configuration Tool for Windows 95/98, ME, NT4, 2000, XP and Vista
Step 5. Returning to the Dial-Up Networking window, highlight with a left mouse click, and then right-click on this new icon to Properties to ...

RSS Compendium - RSS Editors
... compliant RSS 2.0 publisher that can be used to create RSS feeds from scratch or create them from reading an HTML page. Windows 98/Me/NT4/2000/XP ...

Storing Passwords - done right!
In very many - not to say almost all - Web applications user data is administered, from Web forum to Web shop. These user data encompass login ...

VirtualBox 4.2.2 maintenance release squashes bugs
... drivers Linux Additions now support X.Org Server 1.13, while Windows Additions has resolved an issue with automatic screen resize for NT4 guests. ...

Ethernet NIC NetXtreme Server Driver Downloads - Broadcom
... 5704, 5714, 5715, 5717, 5718, 5719, 5720, 5721, 5722, 5723, 5780 Previous driver versions can be found on our archive page . Windows NT4, ...

Yahoo! Messenger Translator Pro - Translate Yahoo conversation instantly
Yahoo! Messenger Translator Pro is professional Yahoo translation software which can translate Yahoo chatting instantly and automatically. With ...

Cygwin
a way to magically make native Windows apps aware of UNIX®functionality like signals, ptys, etc. Again, you need to build your apps from source ...

Services - DAG Tech - IT Support, IT Consulting, IT Services, Tech Support NYC DC
DAG's expert IT services include the following: IT Support End-to-End IT Services Network support Network installation Network security Business ...

Resources last updated: 12/16/2015 4:10:44 AM