nosbod
asked on
installation issues on fedora core2
Hi I have downloaded the free version of ASE for linux and am installing on fedora core2. During installation I opt to configure, accept the default settings and start the servers. The installation wizard produces the following output. Any ideas?
Building Adaptive Server 'RICHARD':
Writing entry into directory services...
Directory services entry complete.
Building master device...
Master device complete.
Writing RUN_RICHARD file...
RUN_RICHARD file complete.
Starting server...
Server started.
Building sysprocs device and sybsystemprocs database...
sybprocs device and sybsystemprocs database created.
Running installmaster script to install system stored procedures...
Task failed
Open Client message: 'ct_send(): network packet layer: internal Client Library
error: State error: trying to write when connection is expecting a read.
'. Open Client message: 'ct_cancel(): network packet layer: internal net
library error: Net-Library operation terminated due to disconnect
'.
Open Client message: 'ct_cmd_drop(): user api layer: external error: The
connection has been marked dead.
'.
Error in query: 'select sum(size) * (@@maxpagesize / 1024) / 1024 from
sysusages where dbid = 1'.
Open Client message: 'ct_cmd_alloc(): user api layer: external error: The
connection has been marked dead.
'.
Error: Command alloc failed
Open Client message: 'ct_cmd_alloc(): user api layer: external error: The
connection has been marked dead.
'.
Error: Command alloc failed
Server 'RICHARD' was not created.
thanks in advance
Rich
Building Adaptive Server 'RICHARD':
Writing entry into directory services...
Directory services entry complete.
Building master device...
Master device complete.
Writing RUN_RICHARD file...
RUN_RICHARD file complete.
Starting server...
Server started.
Building sysprocs device and sybsystemprocs database...
sybprocs device and sybsystemprocs database created.
Running installmaster script to install system stored procedures...
Task failed
Open Client message: 'ct_send(): network packet layer: internal Client Library
error: State error: trying to write when connection is expecting a read.
'. Open Client message: 'ct_cancel(): network packet layer: internal net
library error: Net-Library operation terminated due to disconnect
'.
Open Client message: 'ct_cmd_drop(): user api layer: external error: The
connection has been marked dead.
'.
Error in query: 'select sum(size) * (@@maxpagesize / 1024) / 1024 from
sysusages where dbid = 1'.
Open Client message: 'ct_cmd_alloc(): user api layer: external error: The
connection has been marked dead.
'.
Error: Command alloc failed
Open Client message: 'ct_cmd_alloc(): user api layer: external error: The
connection has been marked dead.
'.
Error: Command alloc failed
Server 'RICHARD' was not created.
thanks in advance
Rich
did you update you "shared memory max" ?
ASKER
yes, i did.up to 64mb
I always use 500MB or more (guess that depends what you machine has available).
Have you done other sybase/linux installations before (eg RedHat or Fedora core 1) ?
Have you done other sybase/linux installations before (eg RedHat or Fedora core 1) ?
ASKER
no, I haven't. I just increased to 64 as that was all that was recommended in the install instructions.
i'll give it another try at a higher amount
i'll give it another try at a higher amount
ASKER
I just increased in to 256 and it made no difference....
the error tends to point to the network comms:
- does the entries in you interfaces file match your machines IP ?
- is that eth0 interface running ?
what version of Sybase are you installing ?
- does the entries in you interfaces file match your machines IP ?
- is that eth0 interface running ?
what version of Sybase are you installing ?
Try doing the install in two pieces: install the software first and decline to configure a server. Then go back and configure the server seperately.
You know, of course, that Sybase 12.5.x is not certified on any RedHat version other than 2.1/3.0 ES (AS/WS).
Bill
You know, of course, that Sybase 12.5.x is not certified on any RedHat version other than 2.1/3.0 ES (AS/WS).
Bill
ASKER
hi, yes, the interface works fine.
I am installing 12.5 ASE.
ok, i'll try the installation in 2 steps.....
I am installing 12.5 ASE.
ok, i'll try the installation in 2 steps.....
ASKER
unfortunately the 2 step approach to the installation had no further success....
Building Adaptive Server 'RICHARD':
Writing entry into directory services... Directory services entry complete.
Building master device... Master device complete.
Writing RUN_RICHARD file...
RUN_RICHARD file complete.
Starting server... Server started.
Building sysprocs device and sybsystemprocs database... sybprocs device and sybsystemprocs database created.
Running installmaster script to install system stored procedures... Task failed
Open Client message: 'ct_send(): network packet layer: internal Client Library
error: State error: trying to write when connection is expecting a read.
'. Open Client message: 'ct_cancel(): network packet layer: internal net
library error: Net-Library operation terminated due to disconnect
'.
Open Client message: 'ct_cmd_drop(): user api layer: external error: The
connection has been marked dead.
'.
Error in query: 'select sum(size) * (@@maxpagesize / 1024) / 1024 from sysusages
where dbid = 1'.
Open Client message: 'ct_cmd_alloc(): user api layer: external error: The
connection has been marked dead.
'.
Error: Command alloc failed
Open Client message: 'ct_cmd_alloc(): user api layer: external error: The
connection has been marked dead.
'.
Error: Command alloc failed
Server 'RICHARD' was not created.
Building Backup Server 'RICHARD_back':
Writing entry into directory services... Directory services entry complete.
Writing RUN_RICHARD_back file...
RUN_RICHARD_back file complete.
Starting server... Server started.
Server 'RICHARD_back' was successfully created.
Building Monitor Server 'RICHARD_mon':
Writing entry into directory services... Directory services entry complete.
Writing RUN_RICHARD_mon file...
RUN_RICHARD_mon file complete.
Unable to log in to Adaptive Server 'RICHARD'.
Unable to boot 'RICHARD_mon' because Monitor Server must be able to log in to
Adaptive Server.
Server 'RICHARD_mon' was not created.
Building XP Server 'RICHARD_XP':
Writing entry into directory services... Directory services entry complete.
Server 'RICHARD_XP' was successfully created.
'RICHARD_XP' will be started when needed by the Adaptive Server.
Done
Here are a couple of ideas since this looks more and more like a network/interfaces file problem:
1) Can you veryfy that the port you are using is not being used by another facility on the machine?
I would try using port numbers way up out of the range like 11001, 11011, 11021 for ASE,
BACKUP_SERVER, and XP_SERVER
2) Does your system get it's IP address using DHCP or RARP? If so, it is probably not getting the
same address each time. There are a couple of ways around that problem. One way is to use
the machine (host) name rather than the IP address in the INTERFACES file. You have to make
sure that the system will actually resolve the IP address from the name; try PING <hostname>
and see what it says the IP address is.
The other approach is to hardcode an IP address for your server. Personally, this is the path
I would take at least short term in order to facilitate debugging. It removes one more
variable from the equation.
One other variation on a theme is when there is an entry in the HOSTS file that for LOCALHOST
that resolves to 127.0.0.1 I have found that, at least for debugging purposes, it is best to have
a static IP address for the machine and the IP address (rather than hostname) coded into the
INTERFACES file.
Bill
1) Can you veryfy that the port you are using is not being used by another facility on the machine?
I would try using port numbers way up out of the range like 11001, 11011, 11021 for ASE,
BACKUP_SERVER, and XP_SERVER
2) Does your system get it's IP address using DHCP or RARP? If so, it is probably not getting the
same address each time. There are a couple of ways around that problem. One way is to use
the machine (host) name rather than the IP address in the INTERFACES file. You have to make
sure that the system will actually resolve the IP address from the name; try PING <hostname>
and see what it says the IP address is.
The other approach is to hardcode an IP address for your server. Personally, this is the path
I would take at least short term in order to facilitate debugging. It removes one more
variable from the equation.
One other variation on a theme is when there is an entry in the HOSTS file that for LOCALHOST
that resolves to 127.0.0.1 I have found that, at least for debugging purposes, it is best to have
a static IP address for the machine and the IP address (rather than hostname) coded into the
INTERFACES file.
Bill
ASKER
1) the ports aren't assigned to any other service in /etc/services. I tried to rerun the adaptive server config using different ports with the same result
2) the machine has a static ip.
I've tried giving the server the address of
192.168.1.x
127.0.0.1
'HOSTNAME' (from /etc/hosts)
When using 192.168.1.141 instead of the HOSTNAME which I had been using before the message to the console looks somewhat better:
Building Adaptive Server 'RICHARD':
Writing entry into directory services... Directory services entry complete.
Building master device... Master device complete.
Writing RUN_RICHARD file...
RUN_RICHARD file complete.
Starting server... Task failed
Unable to boot server 'RICHARD'.
Server 'RICHARD' was not created.
but it's still failing. The log file looks like this:
00:00000:00000:2004/09/28 09:56:58.75 kernel Adaptive Server Enterprise Express Edition (Limits: 1 Engine, 2GB Memory, 5GB Disk space).
00:00000:00000:2004/09/28 09:56:58.79 kernel Using config area from primary master device.
00:00000:00000:2004/09/28 09:56:58.80 kernel Warning: Using default file '/usr/local/sybase/RICHARD
not specified. Specify a configuration file name in the RUNSERVER file to avoid this message.
00:00000:00000:2004/09/28 09:56:58.81 kernel Internal run-time model set for Linux - Native
00:00000:00000:2004/09/28 09:56:58.81 kernel Using 1024 file descriptors.
00:00000:00000:2004/09/28 09:56:58.81 kernel Adaptive Server Enterprise/12.5.2/EBF 12123/P/Linux Intel/Enterprise Linux/ase1252/1839/32
-bit/OPT(Express Edition)/Fri Aug 13 08:27:18 2004
00:00000:00000:2004/09/28 09:56:58.81 kernel Confidential property of Sybase, Inc.
00:00000:00000:2004/09/28 09:56:58.81 kernel Copyright 1987, 2004
00:00000:00000:2004/09/28 09:56:58.81 kernel Sybase, Inc. All rights reserved.
00:00000:00000:2004/09/28 09:56:58.81 kernel Unpublished rights reserved under U.S. copyright laws.
00:00000:00000:2004/09/28 09:56:58.81 kernel
00:00000:00000:2004/09/28 09:56:58.81 kernel This software contains confidential and trade secret information of Sybase,
00:00000:00000:2004/09/28 09:56:58.81 kernel Inc. Use, duplication or disclosure of the software and documentation by
00:00000:00000:2004/09/28 09:56:58.81 kernel the U.S. Government is subject to restrictions set forth in a license
00:00000:00000:2004/09/28 09:56:58.81 kernel agreement between the Government and Sybase, Inc. or other written
00:00000:00000:2004/09/28 09:56:58.81 kernel agreement specifying the Government's rights to use the software and any
00:00000:00000:2004/09/28 09:56:58.81 kernel applicable FAR provisions, for example, FAR 52.227-19.
00:00000:00000:2004/09/28 09:56:58.81 kernel Sybase, Inc. One Sybase Drive, Dublin, CA 94568, USA
00:00000:00000:2004/09/28 09:56:58.81 kernel ASE booted on Linux release 2.6.5-1.358 version #1 Sat May 8 09:04:50 EDT 2004.
00:00000:00000:2004/09/28 09:56:58.81 kernel Using '/usr/local/sybase/RICHARD
00:00000:00000:2004/09/28 09:56:58.81 kernel Logging ASE messages in file '/usr/local/sybase/ASE-12_
00:00000:00000:2004/09/28 09:56:58.82 kernel Platform TCP network is forced to IPv4-only.
00:00000:00000:2004/09/28 09:56:58.82 kernel SQL Server booted with TCP_NODELAY enabled.
00:00000:00000:2004/09/28 09:56:58.82 kernel SSL Plus v3.0.8 security modules loaded successfully.
00:00000:00000:2004/09/28 09:56:58.82 kernel Network and device connection limit is 1014.
00:00000:00000:2004/09/28 09:56:58.95 server Number of blocks left for proc headers: 3232.
00:00000:00000:2004/09/28 09:56:58.95 server Proc header memory allocated 1616 pages for each per engine cache
00:00000:00000:2004/09/28 09:56:58.98 server Size of the 2K memory pool: 8192 Kb
00:00000:00000:2004/09/28 09:56:58.98 server Memory allocated for the default data cache cachelet 1: 8192 Kb
00:00000:00000:2004/09/28 09:56:58.98 kernel Extended cache size '0' is invalid. Provide the appropriate size value.
00:00000:00000:2004/09/28 09:56:58.99 kernel Enabling Linux Kernel asynchronous disk I/O strategy.
00:00000:00000:2004/09/28 09:56:58.99 kernel Initializing virtual device 0, '/usr/local/sybase/master.
00:00000:00000:2004/09/28 09:56:58.99 kernel Virtual device 0 started using asynchronous (with O_DIRECT) i/o.
00:00000:00000:2004/09/28 09:56:58.99 kernel Worker Thread Manager is not enabled for use in SQL Server.
00:00000:00000:2004/09/28 09:56:58.99 kernel Either the config parameter 'use security services' is set to 0, or ASE does not support u
se of external security mechanisms on this platform. The Security Control Layer will not be initialized. No external security mechanisms
will be supported.
00:00000:00000:2004/09/28 09:56:58.99 kernel Unix interval timer enabled for sysclk interrupts.
00:00000:00000:2004/09/28 09:56:59.00 kernel engine 0, os pid 5986 online
00:00000:00000:2004/09/28 09:56:59.00 server Active traceflags: 1623
00:00000:00001:2004/09/28 09:56:59.00 kernel libomni1 - Component Integration Services loaded; version 'libomni1 - Component Integratio
n Services/12.5.2/EBF 12123/P/Linux Intel/Enterprise Linux/ase1252/1/32-bit/OPT
00:00000:00001:2004/09/28 09:56:59.00 kernel libomni1 - Component Integration Services: using 'Sybase Client-Library/12.5.1/P-EB
ESD #2/DRV.12.5.1.0/Linux Intel/Linux 2.4.18-18.7.xsmp i686/BUILD1251-002/OPT/Tue
00:00000:00001:2004/09/28 09:56:59.00 server The logical pagesize of the server is 2 Kb.
00:00000:00001:2004/09/28 09:56:59.00 server Database 'master' appears to be at an older revision than the present installation; SQL Se
rver will assess it, and upgrade it as required.
00:00000:00001:2004/09/28 09:56:59.01 server Database 'master': beginning upgrade step [ID 1]: Initialize disk and create empty all
ocation units on master device.
00:00000:00001:2004/09/28 09:56:59.35 server Database 'master': beginning upgrade step [ID 2]: Bootstrap basic system catalogs in d
atabase.
00:00000:00001:2004/09/28 09:56:59.37 server Database 'master': beginning upgrade step [ID 3]: creating index (table systypes, inde
x ncsystypes)
00:00000:00001:2004/09/28 09:56:59.37 server Database 'master': beginning upgrade step [ID 4]: creating index (table sysobjects, in
dex ncsysobjects)
00:00000:00001:2004/09/28 09:56:59.38 server Database 'master': beginning upgrade step [ID 20]: creating table (table sysusages)
00:00000:00001:2004/09/28 09:56:59.39 server Database 'master': beginning upgrade step [ID 21]: creating table (table sysdatabases)
00:00000:00001:2004/09/28 09:56:59.40 server Database 'master': beginning upgrade step [ID 22]: creating table (table sysdevices)
00:00000:00001:2004/09/28 09:56:59.41 server Database 'master': beginning upgrade step [ID 23]: creating table (table sysmessages)
00:00000:00001:2004/09/28 09:56:59.42 server Database 'master': beginning upgrade step [ID 24]: creating table (table sysconfigures)
00:00000:00001:2004/09/28 09:56:59.44 server Database 'master': beginning upgrade step [ID 25]: creating table (table syscharsets)
00:00000:00001:2004/09/28 09:56:59.46 server Database 'master': beginning upgrade step [ID 26]: creating table (table sysprocedures)
00:00000:00001:2004/09/28 09:56:59.47 server Database 'master': beginning upgrade step [ID 27]: creating table (table syscomments)
00:00000:00001:2004/09/28 09:56:59.49 server Database 'master': beginning upgrade step [ID 28]: creating table (table syssegments)
00:00000:00001:2004/09/28 09:56:59.50 server Database 'master': beginning upgrade step [ID 29]: creating table (table sysprotects)
00:00000:00001:2004/09/28 09:56:59.51 server Database 'master': beginning upgrade step [ID 30]: creating table (table sysusers)
00:00000:00001:2004/09/28 09:56:59.52 server Database 'master': beginning upgrade step [ID 31]: creating table (table sysalternates)
00:00000:00001:2004/09/28 09:56:59.53 server Database 'master': beginning upgrade step [ID 32]: creating table (table sysdepends)
00:00000:00001:2004/09/28 09:56:59.54 server Database 'master': beginning upgrade step [ID 33]: creating table (table syskeys)
00:00000:00001:2004/09/28 09:56:59.55 server Database 'master': beginning upgrade step [ID 35]: creating table (table sysprocesses)
00:00000:00001:2004/09/28 09:56:59.56 server Database 'master': beginning upgrade step [ID 36]: creating table (table syslogins)
00:00000:00001:2004/09/28 09:56:59.57 server Database 'master': beginning upgrade step [ID 37]: creating table (table syslocks)
00:00000:00001:2004/09/28 09:56:59.58 server Database 'master': beginning upgrade step [ID 38]: creating table (table syscurconfigs)
00:00000:00001:2004/09/28 09:56:59.58 server Database 'master': beginning upgrade step [ID 39]: creating table (table sysservers)
00:00000:00001:2004/09/28 09:56:59.60 server Database 'master': beginning upgrade step [ID 40]: creating table (table sysremotelogin
s)
00:00000:00001:2004/09/28 09:56:59.60 server Database 'master': beginning upgrade step [ID 41]: creating table (table sysmonitors)
00:00000:00001:2004/09/28 09:56:59.61 server Database 'master': beginning upgrade step [ID 42]: creating table (table sysengines)
00:00000:00001:2004/09/28 09:56:59.61 server Database 'master': beginning upgrade step [ID 43]: creating table (table syslanguages)
00:00000:00001:2004/09/28 09:56:59.63 server Database 'master': beginning upgrade step [ID 44]: creating table (table systestlog)
00:00000:00001:2004/09/28 09:56:59.63 server Database 'master': beginning upgrade step [ID 45]: creating table (table syssrvroles)
00:00000:00001:2004/09/28 09:56:59.65 server Database 'master': beginning upgrade step [ID 46]: creating table (table sysloginroles)
00:00000:00001:2004/09/28 09:56:59.66 server Database 'master': beginning upgrade step [ID 80]: creating table (table sysattributes)
00:00000:00001:2004/09/28 09:56:59.68 server Database 'master': beginning upgrade step [ID 81]: Load initial set of attribute-defini
tion rows into SYSATTRIBUTES.
00:00000:00001:2004/09/28 09:57:00.75 server Warning: Using only the first 30 characters for password
00:00000:00001:2004/09/28 09:57:01.80 server Database 'master': beginning upgrade step [ID 251]: creating table (table syslogshold)
00:00000:00001:2004/09/28 09:57:01.80 server Database 'master': beginning upgrade step [ID 252]: creating table (table syslisteners)
00:00000:00001:2004/09/28 09:57:01.81 server Database 'master': beginning upgrade step [ID 253]: creating table (table syssecmechs)
00:00000:00001:2004/09/28 09:57:01.82 server Database 'master': beginning upgrade step [ID 600]: creating table (table sysreferences)
00:00000:00001:2004/09/28 09:57:01.84 server Database 'master': beginning upgrade step [ID 601]: creating table (table sysconstraints
)
00:00000:00001:2004/09/28 09:57:01.86 server Database 'master': beginning upgrade step [ID 602]: creating table (table sysusermessage
s)
00:00000:00001:2004/09/28 09:57:01.87 server Database 'master': beginning upgrade step [ID 603]: creating table (table systhresholds)
00:00000:00001:2004/09/28 09:57:01.89 server Database 'master': beginning upgrade step [ID 604]: creating table (table sysroles)
00:00000:00001:2004/09/28 09:57:01.91 server Database 'master': beginning upgrade step [ID 605]: executing SQL statement (declare @ri
d smallint delete sysro)
00:00000:00001:2004/09/28 09:57:01.96 server Database 'master': beginning upgrade step [ID 606]: executing SQL statement (select lct_
admin('lastchance', db_i)
00:00000:00001:2004/09/28 09:57:01.97 server Database 'master': beginning upgrade step [ID 1013]: creating table (table syspartitions)
00:00000:00001:2004/09/28 09:57:01.98 server Database 'master': beginning upgrade step [ID 1025]: creating table (table systimeranges)
00:00000:00001:2004/09/28 09:57:01.99 server Database 'master': beginning upgrade step [ID 1026]: executing SQL statement (if not exis
ts (select 1 from systim)
00:00000:00001:2004/09/28 09:57:02.00 server Database 'master': beginning upgrade step [ID 1027]: creating table (table sysresourcelim
its)
00:00000:00001:2004/09/28 09:57:02.01 server Database 'master': beginning upgrade step [ID 1082]: executing SQL statement (if not exis
ts (select 1 from sysatt)
00:00000:00001:2004/09/28 09:57:02.02 server Database 'master': beginning upgrade step [ID 1124]: creating table (table systabstats)
00:00000:00001:2004/09/28 09:57:02.05 server Database 'master': beginning upgrade step [ID 1125]: creating table (table sysstatistics)
00:00000:00001:2004/09/28 09:57:02.08 server Database 'master': beginning upgrade step [ID 1126]: Initialize systabstats with valid st
atistics
00:00000:00001:2004/09/28 09:57:02.17 server Database 'master': beginning upgrade step [ID 1131]: Creating/Updating the last chance th
reshold for logsegment.
00:00000:00001:2004/09/28 09:57:02.18 server Database 'master': beginning upgrade step [ID 1201]: creating table (table sysxtypes)
00:00000:00001:2004/09/28 09:57:02.21 server Database 'master': beginning upgrade step [ID 1205]: creating table (table sysjars)
00:00000:00001:2004/09/28 09:57:02.24 server Database 'master': beginning upgrade step [ID 1206]: executing SQL statement (if not exis
ts (select 1 from systyp)
00:00000:00001:2004/09/28 09:57:02.25 server Database 'master': beginning upgrade step [ID 1212]: creating table (table systransaction
s)
00:00000:00001:2004/09/28 09:57:02.26 server Database 'master': beginning upgrade step [ID 1213]: executing SQL statement (update syso
bjects set sysstat2 = sy)
00:00000:00001:2004/09/28 09:57:02.27 server Database 'master': beginning upgrade step [ID 1214]: executing SQL statement (if not exis
ts (select 1 from syssrv)
00:00000:00001:2004/09/28 09:57:02.27 server Database 'master': beginning upgrade step [ID 1226]: executing SQL statement (insert sysa
ttributes (class, attrib)
00:00000:00001:2004/09/28 09:57:02.29 server Database 'master': beginning upgrade step [ID 1240]: creating table (table sysqueryplans)
00:00000:00001:2004/09/28 09:57:02.31 server Database 'master': beginning upgrade step [ID 1241]: executing SQL statement (insert into
sysattributes (class, )
00:00000:00001:2004/09/28 09:57:02.32 server Database 'master': beginning upgrade step [ID 1242]: creating table (table syssessions)
00:00000:00001:2004/09/28 09:57:02.33 server Database 'master': beginning upgrade step [ID 1245]: executing SQL statement (if not exis
ts (select 1 from syssrv)
00:00000:00001:2004/09/28 09:57:02.34 server Database 'master': beginning upgrade step [ID 1249]: executing SQL statement (if (select
suser_id('sa')) is not n)
00:00000:00001:2004/09/28 09:57:02.35 server Database 'master': beginning upgrade step [ID 1274]: executing SQL statement (declare @ri
d smallint set nocount )
00:00000:00001:2004/09/28 09:57:02.36 server Database 'master': beginning upgrade step [ID 1338]: executing SQL statement (delete from
sysconfigures where con)
00:00000:00001:2004/09/28 09:57:02.37 server Database 'master': beginning upgrade step [ID 1339]: creating table (table syscertificate
s)
00:00000:00001:2004/09/28 09:57:02.38 server Database 'master': beginning upgrade step [ID 1340]: executing SQL statement (update syst
ypes set length=@@maxpag)
00:00000:00001:2004/09/28 09:57:02.39 server Database 'master': beginning upgrade step [ID 1344]: executing SQL statement (if not exis
ts (select 1 from sysatt)
00:00000:00001:2004/09/28 09:57:02.40 server Database 'master': beginning upgrade step [ID 1345]: executing SQL statement (if not exis
ts (select 1 from sysatt)
00:00000:00001:2004/09/28 09:57:02.40 server Database 'master': beginning upgrade step [ID 1348]: executing SQL statement (if not exis
ts (select 1 from sysatt)
00:00000:00001:2004/09/28 09:57:02.41 server Database 'master': beginning upgrade step [ID 1349]: executing SQL statement (grant selec
t on syslogins(procid) t)
00:00000:00001:2004/09/28 09:57:02.42 server Database 'master': beginning upgrade step [ID 1400]: noting the present database upgrade
level
00:00000:00001:2004/09/28 09:57:02.42 server Database 'master': beginning upgrade step [ID 1401]: Update syscharsets with Unicode sort
orders.
00:00000:00001:2004/09/28 09:57:02.43 server Database 'master': beginning upgrade step [ID 1402]: executing SQL statement (if not exis
ts (select 1 from systyp)
00:00000:00001:2004/09/28 09:57:02.43 server Database 'master': beginning upgrade step [ID 1403]: executing SQL statement (if not exis
ts (select 1 from systyp)
00:00000:00001:2004/09/28 09:57:02.43 server Database 'master': beginning upgrade step [ID 1404]: executing SQL statement (if not exis
ts (select 1 from systyp)
00:00000:00001:2004/09/28 09:57:02.44 server Database 'master': beginning upgrade step [ID 1405]: executing SQL statement (if not exis
ts (select 1 from systyp)
00:00000:00001:2004/09/28 09:57:02.44 server Database 'master': beginning upgrade step [ID 1406]: executing SQL statement (if exists (
select 1 from sysindexes)
00:00000:00001:2004/09/28 09:57:02.45 server Database 'master': beginning upgrade step [ID 1407]: Grant default permissions on system
tables.
00:00000:00001:2004/09/28 09:57:02.52 server Database 'master': beginning upgrade step [ID 1408]: executing SQL statement (update sysu
sers set suid = -2 where)
00:00000:00001:2004/09/28 09:57:02.52 server Database 'master': beginning upgrade step [ID 1409]: executing SQL statement (if not exis
ts (select 1 from syssrv)
00:00000:00001:2004/09/28 09:57:02.53 server Database 'master': beginning upgrade step [ID 1411]: executing SQL statement (declare @ri
d int set nocount on d)
00:00000:00001:2004/09/28 09:57:02.54 server Database 'model' appears to be at an older revision than the present installation; SQL Ser
ver will assess it, and upgrade it as required.
00:00000:00001:2004/09/28 09:57:02.54 server Database 'model': beginning upgrade step [ID 1]: Initialize disk and create empty allo
cation units on master device.
00:00000:00001:2004/09/28 09:57:02.74 server Database 'model': beginning upgrade step [ID 2]: Bootstrap basic system catalogs in da
tabase.
00:00000:00001:2004/09/28 09:57:02.86 server Database 'model': beginning upgrade step [ID 3]: creating index (table systypes, index
ncsystypes)
00:00000:00001:2004/09/28 09:57:02.87 server Database 'model': beginning upgrade step [ID 4]: creating index (table sysobjects, ind
ex ncsysobjects)
00:00000:00001:2004/09/28 09:57:02.87 server Database 'model': beginning upgrade step [ID 26]: creating table (table sysprocedures)
00:00000:00001:2004/09/28 09:57:02.88 server Database 'model': beginning upgrade step [ID 27]: creating table (table syscomments)
00:00000:00001:2004/09/28 09:57:02.89 server Database 'model': beginning upgrade step [ID 28]: creating table (table syssegments)
00:00000:00001:2004/09/28 09:57:02.90 server Database 'model': beginning upgrade step [ID 29]: creating table (table sysprotects)
00:00000:00001:2004/09/28 09:57:02.91 server Database 'model': beginning upgrade step [ID 30]: creating table (table sysusers)
00:00000:00001:2004/09/28 09:57:02.92 server Database 'model': beginning upgrade step [ID 31]: creating table (table sysalternates)
00:00000:00001:2004/09/28 09:57:02.93 server Database 'model': beginning upgrade step [ID 32]: creating table (table sysdepends)
00:00000:00001:2004/09/28 09:57:02.95 server Database 'model': beginning upgrade step [ID 33]: creating table (table syskeys)
00:00000:00001:2004/09/28 09:57:02.96 server Database 'model': beginning upgrade step [ID 80]: creating table (table sysattributes)
00:00000:00001:2004/09/28 09:57:03.00 server Database 'model': beginning upgrade step [ID 600]: creating table (table sysreferences)
00:00000:00001:2004/09/28 09:57:03.02 server Database 'model': beginning upgrade step [ID 601]: creating table (table sysconstraints)
00:00000:00001:2004/09/28 09:57:03.04 server Database 'model': beginning upgrade step [ID 602]: creating table (table sysusermessages
)
00:00000:00001:2004/09/28 09:57:03.05 server Database 'model': beginning upgrade step [ID 603]: creating table (table systhresholds)
00:00000:00001:2004/09/28 09:57:03.07 server Database 'model': beginning upgrade step [ID 604]: creating table (table sysroles)
00:00000:00001:2004/09/28 09:57:03.08 server Database 'model': beginning upgrade step [ID 605]: executing SQL statement (declare @rid
smallint delete sysro)
00:00000:00001:2004/09/28 09:57:03.11 server Database 'model': beginning upgrade step [ID 606]: executing SQL statement (select lct_a
dmin('lastchance', db_i)
00:00000:00001:2004/09/28 09:57:03.12 server Database 'model': beginning upgrade step [ID 1013]: creating table (table syspartitions)
00:00000:00001:2004/09/28 09:57:03.14 server Database 'model': beginning upgrade step [ID 1124]: creating table (table systabstats)
00:00000:00001:2004/09/28 09:57:03.16 server Database 'model': beginning upgrade step [ID 1125]: creating table (table sysstatistics)
00:00000:00001:2004/09/28 09:57:03.18 server Database 'model': beginning upgrade step [ID 1126]: Initialize systabstats with valid sta
tistics
00:00000:00001:2004/09/28 09:57:03.25 server Database 'model': beginning upgrade step [ID 1131]: Creating/Updating the last chance thr
eshold for logsegment.
00:00000:00001:2004/09/28 09:57:03.25 server Database 'model': beginning upgrade step [ID 1201]: creating table (table sysxtypes)
00:00000:00001:2004/09/28 09:57:03.28 server Database 'model': beginning upgrade step [ID 1205]: creating table (table sysjars)
00:00000:00001:2004/09/28 09:57:03.31 server Database 'model': beginning upgrade step [ID 1206]: executing SQL statement (if not exist
s (select 1 from systyp)
00:00000:00001:2004/09/28 09:57:03.32 server Database 'model': beginning upgrade step [ID 1240]: creating table (table sysqueryplans)
00:00000:00001:2004/09/28 09:57:03.34 server Database 'model': beginning upgrade step [ID 1241]: executing SQL statement (insert into
sysattributes (class, )
00:00000:00001:2004/09/28 09:57:03.36 server Database 'model': beginning upgrade step [ID 1274]: executing SQL statement (declare @rid
smallint set nocount )
00:00000:00001:2004/09/28 09:57:03.37 server Database 'model': beginning upgrade step [ID 1340]: executing SQL statement (update systy
pes set length=@@maxpag)
00:00000:00001:2004/09/28 09:57:03.37 server Database 'model': beginning upgrade step [ID 1400]: noting the present database upgrade l
evel
00:00000:00001:2004/09/28 09:57:03.38 server Database 'model': beginning upgrade step [ID 1402]: executing SQL statement (if not exist
s (select 1 from systyp)
00:00000:00001:2004/09/28 09:57:03.38 server Database 'model': beginning upgrade step [ID 1403]: executing SQL statement (if not exist
s (select 1 from systyp)
00:00000:00001:2004/09/28 09:57:03.38 server Database 'model': beginning upgrade step [ID 1404]: executing SQL statement (if not exist
s (select 1 from systyp)
00:00000:00001:2004/09/28 09:57:03.40 server Database 'model': beginning upgrade step [ID 1405]: executing SQL statement (if not exist
s (select 1 from systyp)
00:00000:00001:2004/09/28 09:57:03.40 server Database 'model': beginning upgrade step [ID 1406]: executing SQL statement (if exists (s
elect 1 from sysindexes)
00:00000:00001:2004/09/28 09:57:03.40 server Database 'model': beginning upgrade step [ID 1407]: Grant default permissions on system t
ables.
00:00000:00001:2004/09/28 09:57:03.43 server Database 'model': beginning upgrade step [ID 1408]: executing SQL statement (update sysus
ers set suid = -2 where)
00:00000:00001:2004/09/28 09:57:03.44 server Database 'model': beginning upgrade step [ID 1411]: executing SQL statement (declare @rid
int set nocount on d)
00:00000:00001:2004/09/28 09:57:03.45 server CREATE DATABASE: allocating 1024 logical pages (2.0 megabytes) on disk 'master'.
00:00000:00001:2004/09/28 09:57:03.45 server Warning: The database 'sybsystemdb' is using an unsafe virtual device 'master'. The recove
ry of this database can not be guaranteed.
00:00000:00001:2004/09/28 09:57:04.23 server Database sybsystemdb successfully created.
00:00000:00001:2004/09/28 09:57:04.28 server Recovering database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:04.28 server Started estimating recovery log boundaries for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:04.28 server Completed estimating recovery log boundaries for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:04.28 server Started ANALYSIS pass for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:04.28 server Completed ANALYSIS pass for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:04.28 server Started REDO pass for database 'sybsystemdb'. The total number of log records to process i
s 56.
00:00000:00001:2004/09/28 09:57:04.28 server Redo pass of recovery has processed 2 committed and 0 aborted transactions.
00:00000:00001:2004/09/28 09:57:04.28 server Completed REDO pass for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:04.28 server Recovery of database 'sybsystemdb' will undo incomplete nested top actions.
00:00000:00001:2004/09/28 09:57:04.28 server Started recovery checkpoint for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:04.29 server Completed recovery checkpoint for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:04.29 server Started filling free space info for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:04.29 server Completed filling free space info for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:04.32 server Started cleaning up the default data cache for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:04.32 server Completed cleaning up the default data cache for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:04.32 server Boot Count: 1
00:00000:00001:2004/09/28 09:57:04.36 server Checking external objects.
00:00000:00001:2004/09/28 09:57:04.38 server Database 'sybsystemdb' is now online.
00:00000:00001:2004/09/28 09:57:04.38 server Now loading SQL Server's new default sort order and character set
00:00000:00001:2004/09/28 09:57:04.38 server Checking sysobjects: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.38 server Checking systypes: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.38 server Checking sysusers: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.38 server Checking sysreferences: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.38 server Checking sysreferences: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.38 server Checking sysreferences: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.38 server Checking sysattributes: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.38 server Checking sysattributes: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.38 server Checking sysxtypes: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.38 server Checking sysjars: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.38 server Checking sysobjects: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.38 server Checking systypes: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.38 server Checking sysusers: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.39 server Checking sysreferences: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.39 server Checking sysreferences: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.40 server Checking sysreferences: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.40 server Checking sysattributes: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.40 server Checking sysattributes: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.41 server Checking sysxtypes: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.41 server Checking sysjars: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.42 server Checking sysobjects: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.42 server Checking systypes: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.42 server Checking sysusers: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.42 server Checking sysreferences: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.42 server Checking sysreferences: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.42 server Checking sysreferences: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.42 server Checking sysattributes: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.42 server Checking sysattributes: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.42 server Checking sysxtypes: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.42 server Checking sysjars: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.42 server Checking sysdatabases: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.42 server Checking syslogins: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.42 server Checking sysdevices: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.42 server Checking sysconfigures: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.42 server Checking sysservers: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.42 server Checking sysremotelogins: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.42 server Checking syslanguages: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.42 server Checking syslanguages: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.42 server Checking syscharsets: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.42 server Checking sysresourcelimits: Logical pagesize is 2048 bytes
00:00000:00001:2004/09/28 09:57:04.43 server Default Sort Order successfully changed.
00:00000:00001:2004/09/28 09:57:04.43 server SQL Server shutdown after verifying System Indexes.
00:00000:00001:2004/09/28 09:57:04.43 kernel ueshutdown: exiting
00:00000:00000:2004/09/28 09:57:04.48 kernel Adaptive Server Enterprise Express Edition (Limits: 1 Engine, 2GB Memory, 5GB Disk space).
00:00000:00000:2004/09/28 09:57:04.49 kernel Using config area from primary master device.
00:00000:00000:2004/09/28 09:57:04.50 kernel Internal run-time model set for Linux - Native
00:00000:00000:2004/09/28 09:57:04.50 kernel Using 1024 file descriptors.
00:00000:00000:2004/09/28 09:57:04.50 kernel Adaptive Server Enterprise/12.5.2/EBF 12123/P/Linux Intel/Enterprise Linux/ase1252/1839/32
-bit/OPT(Express Edition)/Fri Aug 13 08:27:18 2004
00:00000:00000:2004/09/28 09:57:04.50 kernel Confidential property of Sybase, Inc.
00:00000:00000:2004/09/28 09:57:04.50 kernel Copyright 1987, 2004
00:00000:00000:2004/09/28 09:57:04.50 kernel Sybase, Inc. All rights reserved.
00:00000:00000:2004/09/28 09:57:04.50 kernel Unpublished rights reserved under U.S. copyright laws.
00:00000:00000:2004/09/28 09:57:04.50 kernel
00:00000:00000:2004/09/28 09:57:04.50 kernel This software contains confidential and trade secret information of Sybase,
00:00000:00000:2004/09/28 09:57:04.50 kernel Inc. Use, duplication or disclosure of the software and documentation by
00:00000:00000:2004/09/28 09:57:04.50 kernel the U.S. Government is subject to restrictions set forth in a license
00:00000:00000:2004/09/28 09:57:04.50 kernel agreement between the Government and Sybase, Inc. or other written
00:00000:00000:2004/09/28 09:57:04.50 kernel agreement specifying the Government's rights to use the software and any
00:00000:00000:2004/09/28 09:57:04.50 kernel applicable FAR provisions, for example, FAR 52.227-19.
00:00000:00000:2004/09/28 09:57:04.50 kernel Sybase, Inc. One Sybase Drive, Dublin, CA 94568, USA
00:00000:00000:2004/09/28 09:57:04.51 kernel ASE booted on Linux release 2.6.5-1.358 version #1 Sat May 8 09:04:50 EDT 2004.
00:00000:00000:2004/09/28 09:57:04.51 kernel Using '/usr/local/sybase/ASE-12_
00:00000:00000:2004/09/28 09:57:04.51 kernel Logging ASE messages in file '/usr/local/sybase/ASE-12_
00:00000:00000:2004/09/28 09:57:04.52 kernel Platform TCP network is forced to IPv4-only.
00:00000:00000:2004/09/28 09:57:04.52 kernel SQL Server booted with TCP_NODELAY enabled.
00:00000:00000:2004/09/28 09:57:04.52 kernel SSL Plus v3.0.8 security modules loaded successfully.
00:00000:00000:2004/09/28 09:57:04.52 kernel Network and device connection limit is 1014.
00:00000:00000:2004/09/28 09:57:04.63 server Number of blocks left for proc headers: 3232.
00:00000:00000:2004/09/28 09:57:04.64 server Proc header memory allocated 1616 pages for each per engine cache
00:00000:00000:2004/09/28 09:57:04.67 server Size of the 2K memory pool: 8192 Kb
00:00000:00000:2004/09/28 09:57:04.67 server Memory allocated for the default data cache cachelet 1: 8192 Kb
00:00000:00000:2004/09/28 09:57:04.67 kernel Extended cache size '0' is invalid. Provide the appropriate size value.
00:00000:00000:2004/09/28 09:57:04.67 kernel Enabling Linux Kernel asynchronous disk I/O strategy.
00:00000:00000:2004/09/28 09:57:04.67 kernel Initializing virtual device 0, '/usr/local/sybase/master.
00:00000:00000:2004/09/28 09:57:04.67 kernel Virtual device 0 started using asynchronous (with O_DIRECT) i/o.
00:00000:00000:2004/09/28 09:57:04.67 kernel Worker Thread Manager is not enabled for use in SQL Server.
00:00000:00000:2004/09/28 09:57:04.67 kernel Either the config parameter 'use security services' is set to 0, or ASE does not support u
se of external security mechanisms on this platform. The Security Control Layer will not be initialized. No external security mechanisms
will be supported.
00:00000:00000:2004/09/28 09:57:04.67 kernel Unix interval timer enabled for sysclk interrupts.
00:00000:00000:2004/09/28 09:57:04.68 kernel engine 0, os pid 5989 online
00:00000:00000:2004/09/28 09:57:04.68 server Active traceflags: 1623
00:00000:00001:2004/09/28 09:57:04.68 kernel libomni1 - Component Integration Services loaded; version 'libomni1 - Component Integratio
n Services/12.5.2/EBF 12123/P/Linux Intel/Enterprise Linux/ase1252/1/32-bit/OPT
00:00000:00001:2004/09/28 09:57:04.68 kernel libomni1 - Component Integration Services: using 'Sybase Client-Library/12.5.1/P-EB
ESD #2/DRV.12.5.1.0/Linux Intel/Linux 2.4.18-18.7.xsmp i686/BUILD1251-002/OPT/Tue
00:00000:00001:2004/09/28 09:57:04.68 server Opening Master Database ...
00:00000:00001:2004/09/28 09:57:04.96 server Loading SQL Server's default sort order and character set
00:00000:00001:2004/09/28 09:57:04.98 server Loaded default Unilib conversion handle.
00:00000:00001:2004/09/28 09:57:04.98 server Recovering database 'master'.
00:00000:00001:2004/09/28 09:57:04.99 server Started estimating recovery log boundaries for database 'master'.
00:00000:00001:2004/09/28 09:57:05.01 server Completed estimating recovery log boundaries for database 'master'.
00:00000:00001:2004/09/28 09:57:05.01 server Started ANALYSIS pass for database 'master'.
00:00000:00001:2004/09/28 09:57:05.01 server Completed ANALYSIS pass for database 'master'.
00:00000:00001:2004/09/28 09:57:05.01 server Started REDO pass for database 'master'. The total number of log records to process is 21.
00:00000:00001:2004/09/28 09:57:05.02 server Redo pass of recovery has processed 4 committed and 0 aborted transactions.
00:00000:00001:2004/09/28 09:57:05.02 server Completed REDO pass for database 'master'.
00:00000:00001:2004/09/28 09:57:05.02 server Recovery of database 'master' will undo incomplete nested top actions.
00:00000:00001:2004/09/28 09:57:05.02 server Started recovery checkpoint for database 'master'.
00:00000:00001:2004/09/28 09:57:05.02 server Completed recovery checkpoint for database 'master'.
00:00000:00001:2004/09/28 09:57:05.02 server Started filling free space info for database 'master'.
00:00000:00001:2004/09/28 09:57:05.11 server Completed filling free space info for database 'master'.
00:00000:00001:2004/09/28 09:57:05.11 server Started cleaning up the default data cache for database 'master'.
00:00000:00001:2004/09/28 09:57:05.11 server Completed cleaning up the default data cache for database 'master'.
00:00000:00001:2004/09/28 09:57:05.14 server Checking external objects.
00:00000:00001:2004/09/28 09:57:05.15 server Database 'master' is now online.
00:00000:00001:2004/09/28 09:57:05.16 server The transaction log in the database 'master' will use I/O size of 2 Kb.
00:00000:00001:2004/09/28 09:57:05.16 server Warning: ASE_HA has no valid license and therefore is not initialized.
00:00000:00001:2004/09/28 09:57:05.17 server server is unnamed
00:00000:00001:2004/09/28 09:57:05.32 server Recovering database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:05.32 server Started estimating recovery log boundaries for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:05.33 server Completed estimating recovery log boundaries for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:05.33 server Started ANALYSIS pass for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:05.33 server Completed ANALYSIS pass for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:05.33 server Started REDO pass for database 'sybsystemdb'. The total number of log records to process i
s 1.
00:00000:00001:2004/09/28 09:57:05.33 server Completed REDO pass for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:05.33 server Recovery of database 'sybsystemdb' will undo incomplete nested top actions.
00:00000:00001:2004/09/28 09:57:05.33 server Started recovery checkpoint for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:05.33 server Completed recovery checkpoint for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:05.33 server Started filling free space info for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:05.36 server Completed filling free space info for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:05.36 server Started cleaning up the default data cache for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:05.36 server Completed cleaning up the default data cache for database 'sybsystemdb'.
00:00000:00001:2004/09/28 09:57:05.36 server Boot Count: 2
00:00000:00001:2004/09/28 09:57:05.37 server Checking external objects.
00:00000:00001:2004/09/28 09:57:05.38 server The transaction log in the database 'sybsystemdb' will use I/O size of 2 Kb.
00:00000:00001:2004/09/28 09:57:05.39 server Database 'sybsystemdb' is now online.
00:00000:00001:2004/09/28 09:57:05.43 server Recovering database 'model'.
00:00000:00001:2004/09/28 09:57:05.43 server Started estimating recovery log boundaries for database 'model'.
00:00000:00001:2004/09/28 09:57:05.43 server Completed estimating recovery log boundaries for database 'model'.
00:00000:00001:2004/09/28 09:57:05.43 server Started ANALYSIS pass for database 'model'.
00:00000:00001:2004/09/28 09:57:05.43 server Completed ANALYSIS pass for database 'model'.
00:00000:00001:2004/09/28 09:57:05.43 server Started REDO pass for database 'model'. The total number of log records to process is 4.
00:00000:00001:2004/09/28 09:57:05.44 server Redo pass of recovery has processed 1 committed and 0 aborted transactions.
00:00000:00001:2004/09/28 09:57:05.44 server Completed REDO pass for database 'model'.
00:00000:00001:2004/09/28 09:57:05.44 server Recovery of database 'model' will undo incomplete nested top actions.
00:00000:00001:2004/09/28 09:57:05.44 server Started recovery checkpoint for database 'model'.
00:00000:00001:2004/09/28 09:57:05.44 server Completed recovery checkpoint for database 'model'.
00:00000:00001:2004/09/28 09:57:05.44 server Started filling free space info for database 'model'.
00:00000:00001:2004/09/28 09:57:05.46 server Completed filling free space info for database 'model'.
00:00000:00001:2004/09/28 09:57:05.46 server Started cleaning up the default data cache for database 'model'.
00:00000:00001:2004/09/28 09:57:05.47 server Completed cleaning up the default data cache for database 'model'.
00:00000:00001:2004/09/28 09:57:05.47 server Checking external objects.
00:00000:00001:2004/09/28 09:57:05.48 server The transaction log in the database 'model' will use I/O size of 2 Kb.
00:00000:00001:2004/09/28 09:57:05.50 server Database 'model' is now online.
00:00000:00001:2004/09/28 09:57:05.50 server The logical pagesize of the server is 2 Kb.
00:00000:00001:2004/09/28 09:57:05.50 server 0 dump conditions detected at boot time
00:00000:00001:2004/09/28 09:57:05.53 server Resident Node id: f73efd3f2fa0
00:00000:00001:2004/09/28 09:57:05.53 server Transaction coordinator initialized.
00:00000:00001:2004/09/28 09:57:05.53 server Clearing temp db
00:00000:00001:2004/09/28 09:57:06.27 server The transaction log in the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2004/09/28 09:57:06.28 server Database 'tempdb' is now online.
00:00000:00009:2004/09/28 09:57:26.29 kernel ninit: cannot find host 192.168.1.141
00:00000:00009:2004/09/28 09:57:26.29 kernel Cannot allocate resources for listener with protocol tcp, host 192.168.1.141, port 4100, e
ngine 0.
00:00000:00009:2004/09/28 09:57:26.29 kernel Cannot start any network listeners.
00:00000:00009:2004/09/28 09:57:26.29 kernel ueshutdown: exiting
thanks in advance
The error message ,
************ 00:00000:00009:2004/09/28 09:57:26.29 kernel ninit: cannot find host 192.168.1.141 ************
00:00000:00009:2004/09/28 09:57:26.29 kernel Cannot allocate resources for listener with protocol tcp, host 192.168.1.141, port 4100, engine 0.
00:00000:00009:2004/09/28 09:57:26.29 kernel Cannot start any network listeners.
pretty much says it. There is something wrong with your DNS entries/server, your INTERFACES file entries, and or your HOSTS file entries.
What happens when you try to ping 192.168.1.141 ?
From the address, I would guess you are running on a small network behind a Linksys/Dlink/etc broadband router/firewall and are using it for DHCP. I would hard code the IP address of the database server so you don't have to worry about floating addresses.
Bill
************ 00:00000:00009:2004/09/28 09:57:26.29 kernel ninit: cannot find host 192.168.1.141 ************
00:00000:00009:2004/09/28 09:57:26.29 kernel Cannot allocate resources for listener with protocol tcp, host 192.168.1.141, port 4100, engine 0.
00:00000:00009:2004/09/28 09:57:26.29 kernel Cannot start any network listeners.
pretty much says it. There is something wrong with your DNS entries/server, your INTERFACES file entries, and or your HOSTS file entries.
What happens when you try to ping 192.168.1.141 ?
From the address, I would guess you are running on a small network behind a Linksys/Dlink/etc broadband router/firewall and are using it for DHCP. I would hard code the IP address of the database server so you don't have to worry about floating addresses.
Bill
ASKER
pinging is fine. I don't run DHCP here so have a static ip. My /etc/hosts file looks like:
127.0.0.1 RICHARD localhost.localdomain localhost
192.168.1.141 RICHARD.
My DNS servers are external to my firewall but surely with the entries in the hosts file, the DNS servers are removed from the equation?
thanks for the help so far!
127.0.0.1 RICHARD localhost.localdomain localhost
192.168.1.141 RICHARD.
My DNS servers are external to my firewall but surely with the entries in the hosts file, the DNS servers are removed from the equation?
thanks for the help so far!
remove the "RICHARD" from the 127.0.0.1 line
the name should only be bound to one ip address
the name should only be bound to one ip address
ASKER
sorry, yes, that was a typo.
damn, that might have explained it
ASKER
Hi, i'm still interested and still haven't resolved. Would love some more help but it feels like we cam up against a brick wall
cheers
understood
No comment has been added to this question in more than 21 days, so it is now classified as abandoned..
I will leave the following recommendation for this question in the Cleanup topic area:
PAQ/Refund
Any objections should be posted here in the next 4 days. After that time, the question will be closed.
leonstryker
EE Cleanup Volunteer
I will leave the following recommendation for this question in the Cleanup topic area:
PAQ/Refund
Any objections should be posted here in the next 4 days. After that time, the question will be closed.
leonstryker
EE Cleanup Volunteer
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.