Please help me to analyze the Sybase errorlog

Please help me to analyze the Sybase errorlog

Post by joh » Fri, 11 Jul 2003 21:13:25



I cannot restart my Sybase db now and some data are lost.
Please analyze:

00:00000:00000:2003/01/08 04:17:06.09 kernel  Using config area from
primary master device.
00:00000:00000:2003/01/08 04:17:06.09 kernel  Configuration Error:
Configuration file, 'C:\Sybase\HPSERVER.cfg', does not exist.
00:00000:00000:2003/01/08 04:17:06.12 kernel  Warning: A configuration
file was not specified and the default file 'C:\Sybase\HPSERVER.cfg'
does not exist. SQL Server creates the default file with the default
configuration.
00:00000:00000:2003/01/08 04:17:06.28 kernel  Kernel memory at
0x20000000, 200704 bytes
00:00000:00000:2003/01/08 04:17:06.29 kernel  Server part of first
shared memory region at 0x20031000, 28119223 bytes
00:00000:00000:2003/01/08 04:17:06.29 kernel  Highest valid address is
0x20031000
00:00000:00000:2003/01/08 04:17:06.29 kernel  Using 100000 file
descriptors.
00:00000:00000:2003/01/08 04:17:06.34 kernel  Adaptive Server
Enterprise/11.9.2/1031/P/NT (IX86)/OS 3.51,4.0/FBU/Fri Aug 14 01:42:41
1998
00:00000:00000:2003/01/08 04:17:06.34 kernel  Confidential property of
Sybase, Inc.
00:00000:00000:2003/01/08 04:17:06.34 kernel  Copyright 1987, 1998
00:00000:00000:2003/01/08 04:17:06.34 kernel  Sybase, Inc.  All rights
reserved.
00:00000:00000:2003/01/08 04:17:06.34 kernel  Unpublished rights
reserved under U.S. copyright laws.
00:00000:00000:2003/01/08 04:17:06.34 kernel  
00:00000:00000:2003/01/08 04:17:06.34 kernel  This software contains
confidential and trade secret information of Sybase,
00:00000:00000:2003/01/08 04:17:06.34 kernel  Inc.   Use,  duplication
or disclosure of the software and documentation by
00:00000:00000:2003/01/08 04:17:06.34 kernel  the  U.S.  Government
is  subject  to  restrictions set forth in a license
00:00000:00000:2003/01/08 04:17:06.34 kernel  agreement  between  the
Government  and  Sybase,  Inc.  or  other  written
00:00000:00000:2003/01/08 04:17:06.34 kernel  agreement  specifying
the  Government's rights to use the software and any
00:00000:00000:2003/01/08 04:17:06.34 kernel  applicable FAR
provisions, for example, FAR 52.227-19.
00:00000:00000:2003/01/08 04:17:06.34 kernel  Sybase, Inc. 6475
Christie Avenue, Emeryville, CA 94608, USA
00:00000:00000:2003/01/08 04:17:06.34 kernel  Using
'C:\Sybase\HPSERVER.cfg' for configuration information.
00:00000:00000:2003/01/08 04:17:06.34 kernel  Logging SQL Server
messages in file 'C:\Sybase\install\errorlog'.
00:00000:00000:2003/01/08 04:17:06.39 kernel  Directory Control Layer
(DCL) using directory driver: InterfacesDriver
00:00000:00000:2003/01/08 04:17:06.39 kernel  *** WARNING
******************
00:00000:00000:2003/01/08 04:17:06.39 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:00000:00000:2003/01/08 04:17:06.39 kernel  SQL Server NT process id
is 0x448.
00:00000:00000:2003/01/08 04:17:06.39 kernel  SQL Server was started
as a Service.
00:00000:00000:2003/01/08 04:17:06.39 kernel  Network and device
connection limit is 99992.
00:00000:00000:2003/01/08 04:17:06.42 server  Number of proc buffers
allocated: 1945.
00:00000:00000:2003/01/08 04:17:06.45 server  Proc header memory
allocated 972 pages for each per engine cache
00:00000:00000:2003/01/08 04:17:06.45 server  Number of blocks left
for proc headers: 1991.
00:00000:00000:2003/01/08 04:17:06.45 server  Memory allocated for the
default data cache cache: 14660 Kb
00:00000:00000:2003/01/08 04:17:06.46 server  Size of the 2K memory
pool: 14660 Kb
00:00000:00000:2003/01/08 04:17:06.46 kernel  Initializing virtual
device 0, 'e:\DATA\MASTER.DAT'
00:00000:00000:2003/01/08 04:17:06.46 kernel  Virtual device 0 started
using asynchronous i/o.
00:00000:00000:2003/01/08 04:17:06.46 kernel  Worker Thread Manager is
not enabled for use in SQL Server.
00:00000:00000:2003/01/08 04:17:06.46 kernel  Either the config
parameter 'use security services' is set to 0, or ASE does not support
use of external security mechanisms on this platform. The Security
Control Layer will not be initialized. No external security mechanisms
will be supported.
00:00000:00000:2003/01/08 04:17:06.87 kernel  engine 0, os pid 164
online
00:00000:00000:2003/01/08 04:17:06.90 server  No active traceflags
00:00000:00001:2003/01/08 04:17:07.00 server  Opening Master Database
...
00:00000:00001:2003/01/08 04:17:07.20 server  Loading SQL Server's
default sort order and character set
00:00000:00003:2003/01/08 04:17:07.23 kernel  network name jtyserver1,
type ether, port 5000
00:00000:00001:2003/01/08 04:17:07.26 server  Recovering database
'master'
00:00000:00001:2003/01/08 04:17:07.31 server  Redo pass of recovery
has processed 1 committed and 0 aborted transactions.
00:00000:00001:2003/01/08 04:17:07.40 server  Database 'master' is now
online.
00:00000:00001:2003/01/08 04:17:07.40 server  The transaction log in
the database 'master' will use I/O size of 2 Kb.
00:00000:00001:2003/01/08 04:17:07.40 server  0 dump conditions
detected at boot time
00:00000:00001:2003/01/08 04:17:07.40 server  server is unnamed
00:00000:00001:2003/01/08 04:17:07.40 server  Warning: The
'sysconfigures' table is not updated since the SQL Server is started
with the default configuration.
00:00000:00001:2003/01/08 04:17:07.42 server  Recovering database
'model'.
00:00000:00001:2003/01/08 04:17:07.43 server  The transaction log in
the database 'model' will use I/O size of 2 Kb.
00:00000:00001:2003/01/08 04:17:07.43 server  Database 'model' is now
online.
00:00000:00001:2003/01/08 04:17:07.43 server  Clearing temp db
00:00000:00001:2003/01/08 04:17:07.65 server  The transaction log in
the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2003/01/08 04:17:07.68 server  The transaction log in
the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2003/01/08 04:17:07.68 server  Database 'tempdb' is now
online.
00:00000:00001:2003/01/08 04:17:07.68 server  The transaction log in
the database 'tempdb' will use I/O size of 2 Kb.
00:00000:00001:2003/01/08 04:17:07.68 server  Recovery complete.
00:00000:00001:2003/01/08 04:17:07.70 server  SQL Server's default
sort order is:
00:00000:00001:2003/01/08 04:17:07.70 server    'bin_cp850' (ID = 50)
00:00000:00001:2003/01/08 04:17:07.70 server  on top of default
character set:
00:00000:00001:2003/01/08 04:17:07.70 server    'cp850' (ID = 2).
00:00000:00001:2003/01/08 04:17:07.70 server  Loaded default Unilib
conversion handle.
00:00000:00001:2003/01/08 04:17:36.23 kernel  Initializing virtual
device 1, 'e:\DATA\SYBPROCS.DAT'
00:00000:00001:2003/01/08 04:17:36.23 kernel  Virtual device 1 started
using asynchronous i/o.
00:00000:00001:2003/01/08 04:17:43.25 server  Configuration file
'C:\Sybase\HPSERVER.cfg' has been written and the previous version has
been renamed to 'C:\Sybase/HPSERVER.001'.
00:00000:00001:2003/01/08 04:17:43.25 server  The configuration option
'allow updates to system tables' has been changed by 'sa' from '0' to
'1'.
00:00000:00001:2003/01/08 04:21:00.06 server  Configuration file
'C:\Sybase\HPSERVER.cfg' has been written and the previous version has
been renamed to 'C:\Sybase/HPSERVER.002'.
00:00000:00001:2003/01/08 04:21:00.06 server  The configuration option
'allow updates to system tables' has been changed by 'sa' from '1' to
'0'.
00:00000:00001:2003/01/08 04:21:00.10 server  Configuration file
'C:\Sybase\HPSERVER.cfg' has been written and the previous version has
been renamed to 'C:\Sybase/HPSERVER.003'.
00:00000:00001:2003/01/08 04:21:00.12 server  The configuration option
'allow updates to system tables' has been changed by 'sa' from '0' to
'1'.
00:00000:00001:2003/01/08 04:21:00.34 server  Configuration file
'C:\Sybase\HPSERVER.cfg' has been written and the previous version has
been renamed to 'C:\Sybase/HPSERVER.004'.
00:00000:00001:2003/01/08 04:21:00.35 server  The configuration option
'allow updates to system tables' has been changed by 'sa' from '1' to
'0'.
00:00000:00010:2003/01/08 04:21:00.40 server  Configuration file
'C:\Sybase\HPSERVER.cfg' has been written and the previous version has
been renamed to 'C:\Sybase/HPSERVER.005'.
00:00000:00010:2003/01/08 04:21:00.42 server  The configuration option
'allow updates to system tables' has been changed by 'sa' from '0' to
'1'.
00:00000:00010:2003/01/08 04:21:00.43 server  Configuration file
'C:\Sybase\HPSERVER.cfg' has been written and the previous version has
been renamed to 'C:\Sybase/HPSERVER.006'.
00:00000:00010:2003/01/08 04:21:00.43 server  The configuration option
'allow updates to system tables' has been changed by 'sa' from '1' to
'0'.
00:00000:00010:2003/01/08 04:21:00.46 server  Configuration file
'C:\Sybase\HPSERVER.cfg' has been written and the previous version has
been renamed to 'C:\Sybase/HPSERVER.007'.
00:00000:00010:2003/01/08 04:21:00.48 server  The configuration option
'allow updates to system tables' has been changed by 'sa' from '0' to
'1'.
00:00000:00010:2003/01/08 04:21:00.50 server  Configuration file
'C:\Sybase\HPSERVER.cfg' has been written and the previous version has
been renamed to 'C:\Sybase/HPSERVER.008'.
00:00000:00010:2003/01/08 04:21:00.50 server  The configuration option
'allow updates to system tables' has been changed by 'sa' from '1' to
'0'.
00:00000:00010:2003/01/08 04:21:01.82 server  Configuration file
'C:\Sybase\HPSERVER.cfg' has been written and the previous version has
been renamed to 'C:\Sybase/HPSERVER.009'.
00:00000:00010:2003/01/08 04:21:01.84 server  The configuration option
'allow updates to system tables' has been changed by 'sa' from '0' to
'1'.
00:00000:00010:2003/01/08 04:21:01.87 server  Configuration file
'C:\Sybase\HPSERVER.cfg' has been written and the previous version has
been renamed to 'C:\Sybase/HPSERVER.010'.
00:00000:00010:2003/01/08 04:21:01.89 server  The configuration option
'allow updates to system tables' has been changed by 'sa' from ...

read more »

 
 
 

Please help me to analyze the Sybase errorlog

Post by Anthony Mandi » Sat, 12 Jul 2003 12:38:05



> I cannot restart my Sybase db now and some data are lost.

        You'd better contact Sybase Technical Support.

-am     ? 2003

 
 
 

1. Copy SQL Server ErrorLog Contents to NT ErrorLog

HI All,
     Iam working with SQL 7.0.
From T-SQL ,how can I trap an error from the SQL Server ErrorLog and copy to
the
NT Error Log.Since my application checks the errors from NT Error Log and
displays to the user.
Is there an extended stored_procedure for acheving this.

Any help will be highly appreciated.

Regards
Shamim Rasheed

2. R95 over UNIX comments plez

3. COMBO BOX, PLEASE HELP, PLEASE HELP, PLEASE HELP!

4. CBT for 8i

5. sybase 12 errorlog

6. Looking for a Senior SQL Server DBA

7. Sybase errorlog meaning, anyone??

8. SQL Server notification

9. kernel error in Sybase errorlog

10. emergency please help me please please please

11. APPROACH QUERY-PLEASE PLEASE PLEASE PLEASE HELP

12. Sybase CPU UTILIZATION -- Analyze (BMC Patrol)

13. Help to understand an errorlog message