by Hi folks,
I have written scripts to upgrade our customers systems from Sybase492
to Sybase 11. When dealing with customer data we have to be very
careful. The upgrades we have been testing internally have been
pretty basic configurations. All but a few have upgraded successfully
Here is one of those failures...
In all failure cases the sybinit process has exited. Note: I am using
the
resource files to seamlessly run Sybinit.
e.g. ${SYBASE}/install/sybinit -r upgrade.rs
The error log has the most important info:
00:96/09/23 12:31:05.91 kernel Using 1024 file descriptors.
00:96/09/23 12:31:05.91 kernel SQL Server/11.0.1/P/Sun_svr4/OS
5.4/1/OPT/Tue Ap
r 9 21:25:40 PDT 1996
00:96/09/23 12:31:05.91 kernel Confidential property of Sybase, Inc.
00:96/09/23 12:31:05.91 kernel (c) Copyright Sybase Inc., 1987, 1996.
00:96/09/23 12:31:05.91 kernel All rights reserved.
00:96/09/23 12:31:05.91 kernel
00:96/09/23 12:31:05.91 kernel Use, duplication, or disclosure by the
United St
ates Government
00:96/09/23 12:31:05.91 kernel is subject to restrictions as set forth
in FAR s
ubparagraphs
00:96/09/23 12:31:05.91 kernel 52.227-19(a)-(d) for civilian agency
contracts a
nd DFARS
00:96/09/23 12:31:05.91 kernel 252.227-7013(c) (1) (ii) for Department
of Defen
se contracts.
00:96/09/23 12:31:05.91 kernel Sybase reserves all unpublished rights
under the
copyright
00:96/09/23 12:31:05.91 kernel laws of the United States.
00:96/09/23 12:31:05.91 kernel Sybase, Inc. 6475 Christie Avenue,
Emeryville, C
A 94608 USA.
00:96/09/23 12:31:05.91 kernel Using '/opt/sybase11/CASCADE.cfg' for
configurat
ion information.
00:96/09/23 12:31:05.91 kernel Logging SQL Server messages in file
'/opt/sybase
11/install/CASCADE_err.log'
.
00:96/09/23 12:31:05.92 kernel Network and device connection limit is
1014.
00:96/09/23 12:31:05.94 server Number of proc buffers allocated: 3042.
00:96/09/23 12:31:06.00 server Number of blocks left for proc headers:
3089.
00:96/09/23 12:31:06.00 server Memory allocated for the default data
cache cach
e: 23120 Kb
00:96/09/23 12:31:06.03 server Size of the 2K memory pool: 23120 Kb
00:96/09/23 12:31:06.04 kernel Initializing virtual device 0,
'/dev/rdsk/c0t1d0
s4'
00:96/09/23 12:31:06.04 kernel Virtual device 0 started using
asynchronous i/o.
00:96/09/23 12:31:06.05 server Opening Master Database ...
00:96/09/23 12:31:06.07 kernel dstartio: I/O request repeatedly
delayed; block
number: 284, vdn: 0
00:96/09/23 12:31:06.07 kernel dstartio: I/O request repeatedly
delayed; block
number: 284, vdn: 0
00:96/09/23 12:31:06.08 kernel dstartio: I/O request repeatedly
delayed; block
number: 284, vdn: 0
Goes on forever. I can't duplicate this on any other system. It's
always the
same block number. I figured there's smething wrong with the setup of
the system.
It's pretty basic though.
This was Sybase's reply, so far!
> cases came up with one possibility. The same "dstartio..." error with
> block number 284 and vdn 0 was reported when the memory configured for
> the SQL Server was greater than 75% of the shared memory on the machine.
> A couple things you may check are how much shared memory you have
> configured at the OS level and whether the memory configured for the
> SQL Server is greater than or equal to 75% of this number AND how does the
> shared memory configured on this machine compare to the shared memory
> configured on the other machines that do not have this problem? According
> to the documentation in the case I found, the server locks all of the
> memory for which it is configured and at the OS level only up to 75% of
> shared memory may be locked.
> I'll do more research tomorrow morning, but in the meantime you may want
> to check on the shared memory configured at the OS level and compare it
> to the SQL Server memory.
set shmsys:shminfo_shmmax=131072000
It doesn't sound like the problem.
My sybinit process gives the following:
****************************************
The log file for this session is '/tmp/sybase.264'.
Running task: upgrade the SQL Server.
Copying old interfaces file '/opt/sybase/interfaces' to
'/opt/sybase11/interfaces'.
Testing SQL Server 'CASCADE' for eligibility to upgrade to release
'11.0.1'.
...................Done
Server 'CASCADE' passed preupgrade eligibility test. Proceeding.
Checkpointing all databases.
...Done
The log file for sp_checkreswords output is
'/opt/sybase11/init/logs/checkres.dmp'.
Running script '/opt/sybase11/upgrade/usage.sql' to save Database
segment information
Successfully saved database segment information
Shutting down the SQL Server 'CASCADE'
waiting for server 'CASCADE' to boot...
goes on forever...
Log Output for lower layer debug
================================
09/23/96 12:30:15 PM Sybinit/11.0.1/P/Sun_svr4/OS 5.4/1/OPT/Tue Mar 5
02:41:31
PST 1996
09/23/96 12:30:15 PM Confidential property of Sybase, Inc. (c) Copyright
Sybase
Inc. 1993, 1996. All rights reserved. Use,
duplication, or
disclosure by the United States Government is
subject to
restrictions as set forth in FAR subparagraphs
52.227-19
(a)-(d) for civilian agency contracts and DFARS
252.227-7013 (c)(1)(ii) for Department of Defense
contracts. Sybase reserves all unpublished rights
under the
copyright laws of the United States. Sybase, Inc.
6475
Christie Avenue, Emeryville, CA 94608 USA.
09/23/96 12:30:15 PM BEGIN ENVIRONMENT INFORMATION
USER ENVIRONMENT
----------------------------------------
user name: root
current directory: /opt/scripts
character set: iso_1
language: us_english
sybinit release directory: /opt/sybase11
working release directory: /opt/sybase11
DSQUERY: CASCADE
09/23/96 12:30:15 PM END ENVIRONMENT INFORMATION
09/23/96 12:30:16 PM Using resource file '/opt/scripts/upgrade.rs.2' for
product
attributes.
09/23/96 12:30:17 PM Running task: upgrade the SQL Server.
09/23/96 12:30:17 PM Copying old interfaces file
'/opt/sybase/interfaces' to
'/opt/sybase11/interfaces'.
09/23/96 12:30:17 PM Calling the shell with
'/opt/sybase11/upgrade/preupgrade
-SCASCADE -P -N >
/opt/sybase11/init/logs/tmp 2>&1
'.
09/23/96 12:30:17 PM Testing SQL Server 'CASCADE' for eligibility to
upgrade to
release '11.0.1'.
09/23/96 12:30:36 PM Done
09/23/96 12:30:36 PM Begin output from 'preupgrade':
Starting preupgrade of SQL Server
Checking status in all existing databases.
Checking space in all existing databases.
Database cascview has sufficient space.
Database master has sufficient space.
Database model has sufficient space.
Database tempdb has sufficient space.
Clearing reused columns in09/23/96 12:30:36 PM End output from
'preupgrade'.
Preupgrade of SQL Server to 11.0.1 is complete.
09/23/96 12:30:36 PM Server 'CASCADE' passed preupgrade eligibility
test.
Proceeding.
09/23/96 12:30:36 PM Checkpointing all databases.
09/23/96 12:30:36 PM Sending the following SQL command to the server:
'use
cascview'.
09/23/96 12:30:36 PM Sending the following SQL command to the server:
'checkpoint'.
09/23/96 12:30:36 PM Sending the following SQL command to the server:
'use
master'.
09/23/96 12:30:36 PM Sending the following SQL command to the server:
'checkpoint'.
09/23/96 12:30:36 PM Sending the following SQL command to the server:
'use
model'.
09/23/96 12:30:36 PM Sending the following SQL command to the server:
'checkpoint'.
09/23/96 12:30:36 PM Sending the following SQL command to the server:
'use
tempdb'.
09/23/96 12:30:36 PM Sending the following SQL command to the server:
'checkpoint'.
09/23/96 12:30:46 PM Done
09/23/96 12:30:46 PM Sending the following SQL command to the server:
'use
cascview'.
09/23/96 12:30:48 PM Sending the following SQL command to the server:
'use
master'.
09/23/96 12:30:49 PM Sending the following SQL command to the server:
'use
model'.
09/23/96 12:30:50 PM Sending the following SQL command to the server:
'use
tempdb'.
09/23/96 12:30:50 PM The log file for sp_checkreswords output is
'/opt/sybase11/init/logs/checkres.dmp'.
09/23/96 12:30:50 PM Running script '/opt/sybase11/upgrade/usage.sql' to
save
Database segment information
09/23/96 12:30:50 PM Calling the shell with '/opt/sybase11/bin/isql
-P
-Usa -SCASCADE -i/opt/sybase11/upgrade/usage.sql
-o/opt/sybase11/init/logs/tmp >
/opt/sybase11/init/logs/tmp
2>&1 '.
09/23/96 12:30:51 PM Begin output from 'usage.sql':
urrent segment and size usage
name segmap usage
device_name MegaBytes
------------------------------ ----------- ------------------------
------------------------------ ---------
cascview 3 data only
cascview_device 20
cascview 4 log only
log_device 20
cascview 3 data only
cascview_device 30
model
...
read more »