Thanks
> This shutdown state will persist across reboots of ASE.
Ah - That explains why the db was unavailable after a reboot (although a little odd for it to say it was online in the first place).
The transaction log in the database 'tempdb_xxxx' will use I/O size of 32 Kb.
Database 'tempdb_xxxx' is now online
Although we're now wondering why it was shutdown in the first place.
No one can remember if it was shutdown deliberately after we had a 834 Error
Would you expect any of these errors to make a db unavailable.
Error 834, Error 3478 or Error 6103 Error.
(BTW, we've opened a case on the 834 error but nothing useful found)
00:0005:00000:02377:2015/05/05 02:57:39.91 server Error: 834,Severity: 20, State: 3
00:0005:00000:02377:2015/05/05 02:57:39.91 server Illegal attempt to clean buffer: BUF=0x0x00002b12b63ed4c8, MASS=0x0x00002b12b63ed4c8,Buf#=0, page=0x0x00002b1014c10000, dbid=93, Mass vdevno=127,vpage=4103856, Buf lpage=982, Mass stat=0x4010001, Buf stat=0x2,size=16384, cid=3 ('tempdb_cache1'), Pinned xdes=0x(nil), spid=0.
00:0005:00000:02377:2015/05/05 02:57:39.91 kernel
...
00:0012:00000:02377:2015/05/05 02:57:39.94 server WARNING - Fatal Error 3478 occurred at May 5 2015 2:57AM. Please note the error and time, and contact a user with System Administrator (SA) authorization. 00:0012:00000:02377:2015/05/05 02:57:39.94 server Error: 3478,Severity: 21, State: 1 |