The second error code is -902. The following is the listing from the knldiag
file.

2002-06-05 08:18:36      0x270     19856 TASKING
XPARAM(fAutoRestartShutdown): 1
2002-06-05 08:18:36      0x270     19857 TASKING  ulStartupOptions: 2
2002-06-05 08:18:36      0x270     19858 TASKING  FORCE_AUTORESTARTSHUTDOWN:
4
2002-06-05 08:18:36      0x270     19859 TASKING  ulConnected: 1023229116
2002-06-05 08:18:36      0x270     19633 CONNECT  Connect req. (T5, Node:'',
PID:712)
2002-06-05 08:18:36      0x270     19615 DEVIO    Attaching devspace
'SYS_001'
2002-06-05 08:18:36      0x3DC     19613 DBSTATE  I/O thread for 'SYS_001'
started
2002-06-05 08:18:36      0x270     19617 DEVIO    Single I/O attach,
'SYS_001', UKT:3
2002-06-05 08:18:36      0x270 ERR 54001 I/O      page
0000000000000000...0000000000000000
2002-06-05 08:18:36      0x270     19616 DEVIO    Detaching devspace
'SYS_001'
2002-06-05 08:18:36      0x3DC     19614 DBSTATE  I/O thread for 'SYS_001'
stopped
2002-06-05 08:18:36      0x2EC     19618 DEVIO    Single I/O detach,
'SYS_001', UKT:3
2002-06-05 08:18:36      0x270 ERR 53017 I/O      SYSDEV DEVNO: 1
2002-06-05 08:18:36      0x270 ERR 53016 I/O      SYS_001
2002-06-05 08:18:36      0x270 ERR 53013 I/O      b15f_attach_dbdevice:
sys_dev offline
2002-06-05 08:18:36      0x270     19651 CONNECT  Connection released, T5
2002-06-05 08:18:43      0x270     19856 TASKING
XPARAM(fAutoRestartShutdown): 1
2002-06-05 08:18:43      0x270     19857 TASKING  ulStartupOptions: 2
2002-06-05 08:18:43      0x270     19858 TASKING  FORCE_AUTORESTARTSHUTDOWN:
4
2002-06-05 08:18:43      0x270     19859 TASKING  ulConnected: 1023229123
2002-06-05 08:18:43      0x270     19633 CONNECT  Connect req. (T5, Node:'',
PID:712)
2002-06-05 08:18:43      0x270     19615 DEVIO    Attaching devspace
'SYS_001'
2002-06-05 08:18:43      0x3D8     19613 DBSTATE  I/O thread for 'SYS_001'
started
2002-06-05 08:18:43      0x270     19617 DEVIO    Single I/O attach,
'SYS_001', UKT:3
2002-06-05 08:18:43      0x270 ERR 54001 I/O      page
0000000000000000...0000000000000000
2002-06-05 08:18:43      0x270     19616 DEVIO    Detaching devspace
'SYS_001'
2002-06-05 08:18:43      0x3D8     19614 DBSTATE  I/O thread for 'SYS_001'
stopped
2002-06-05 08:18:43      0x2EC     19618 DEVIO    Single I/O detach,
'SYS_001', UKT:3
2002-06-05 08:18:43      0x270 ERR 53017 I/O      SYSDEV DEVNO: 1
2002-06-05 08:18:43      0x270 ERR 53016 I/O      SYS_001
2002-06-05 08:18:43      0x270 ERR 53013 I/O      b15f_attach_dbdevice:
sys_dev offline
2002-06-05 08:18:43      0x270     19651 CONNECT  Connection released, T5



----- Original Message -----
From: "Vorsprach, Bernd" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 04, 2002 5:51 PM
Subject: RE: Error -24988 message not available


> From: Vernon [mailto:[EMAIL PROTECTED]]
>
> > I am trying to install a new database on the server
> > (sapdb 7.3.0.20 and Win2000) and I get this error when I
> > try and switch the database to hot. The funny thing is I have
> > another database running on the server without any problems.
> > I've tried droping the database and creating complete new ones,
> > but still the say error.
>
> The message -24988 is only a message class. You have to check
> the number in the second line against messages document
> (
>
http://www.sapdb.org/htmhelp/c5/e3c635d0998e4be10000009b38f839/frameset.htm
> )
>
> Here is an example for a -24988 message
>   ERR
>   -24988,ERR_SQL: sql error
>   -3008,Message not available
>
> Maybe there is also more information in the file knldiag in the
> so called rundirectory of the database instance.
>
> Bernd
> --
> SAP Labs Berlin
> _______________________________________________
> sapdb.general mailing list
> [EMAIL PROTECTED]
> http://listserv.sap.com/mailman/listinfo/sapdb.general


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.368 / Virus Database: 204 - Release Date: 29/05/2002

_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to