Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Database marked suspect!

2 posts in Windows NT Last posting was on 2000-06-16 21:09:18.0Z
Anand Vidhyasekaran Posted on 2000-06-15 21:51:27.0Z
Reply-To: "Anand Vidhyasekaran" <vanand@micromation.com>
From: "Anand Vidhyasekaran" <vanand@micromatrion.com>
Subject: Database marked suspect!
Date: Thu, 15 Jun 2000 16:51:27 -0500
Lines: 11
Organization: Micromation
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID: <8KtSRUx1$GA.300@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.nt
NNTP-Posting-Host: 207.100.9.121
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:2025
Article PK: 1089483

We don't have any recent backups at this site. Sybase has marked the
database suspect. I already tried reseting the status flag. It does not
help. It comes with Severity 21, State : 1 Database "MM" (dbid 5): Recovery
Failed. Found some problem in an object page in the cache. How do I bring
this database online.

Thanks
Anand


Andy Price Posted on 2000-06-16 21:09:18.0Z
From: "Andy Price" <andy.price@canada.com>
References: <8KtSRUx1$GA.300@forums.sybase.com>
Subject: Re: Database marked suspect!
Date: Fri, 16 Jun 2000 22:09:18 +0100
Lines: 39
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Message-ID: <DBrFbh91$GA.238@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.nt
NNTP-Posting-Host: dyn25-ras54.screaming.net 212.188.149.25
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:2019
Article PK: 1089477

Anand,

From master, try

sp_forceonline_db dbname, "sa_on"

this should allow the database to come online so only an SA can use it. Dump
the transaction log immediately so that you can at least recover to this
point. Perform parallel DBCC (dbcc checkstorage) on the database looking for
errors and then attempt to repair them if possible. If all this works, dump
the database.

Incidently, start daily backups as soon as you can and frequent transaction
log dumps. It is suicide to run a production server without backups.

--
Andy Price
Sybase Certified Adaptive Server Administrator - Associate v11.5

Anand Vidhyasekaran <vanand@micromatrion.com> wrote in message
news:8KtSRUx1$GA.300@forums.sybase.com...
> We don't have any recent backups at this site. Sybase has marked the
> database suspect. I already tried reseting the status flag. It does not
> help. It comes with Severity 21, State : 1 Database "MM" (dbid 5):
Recovery
> Failed. Found some problem in an object page in the cache. How do I bring
> this database online.
>
> Thanks
> Anand
>
>
>