Database in recovery mode

The last log for my database in sql error log is
Recovery of database 'DBNAME' (37) is 18% complete (approximately 111 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Its been more than 7hrs now & still the recovery is not completed. My database is 7gb in size. When I check sp_who2 " i see the the DBCC session is blocked by -3 spid. The session is not getting killed & i don't get any info on how i can kill session
blocked by spid -3. Any thoughts on this

all sql folders/db files are exempted from antivirus scan. there is no update in sql error log on percentage completed,
the last update was 7hrs ago (18%).
sql version SQL 2008 R2 SP1 enterprise edition. cannot find what is running against spid -3, dbcc inputbuffer (-3) gives invalid spid error. I referred this link http://www.sqlskills.com/BLOGS/PAUL/post/Disaster-recovery-101-dealing-with-negative-SPIDS-(-2-and-3).aspx.
as mentioned in link I don't get deferred transaction that has a transaction status with the 0x80000. I did not find much information on resolving spid -3
blocks even after lot of search. As last measure we have decided to drop the database & restore from the backup.

Similar Messages

Restore a database in recovery mode sql server 2005

Please i need some help. My database has been marked in recovery in sql 2005 management studio and i can't connect to it how do i bring it back to normal

if your database is marked in recovery this means that SQL Server is recoverying the database typically after a sql server restart.
If the database is marked restoring, do this restore database databasename with recovery
Otherwise, you need to check the status of the recovery - Check this query: SELECT state_desc FROM sys.databases WHERE name = 'ProblemDatabaseName'; If this returns recovery_pending you have to wait. Check the SQL Server log for messages about the
state of the recovery.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

Unable to sqlplus as user system to a standby db in recovery mode

Getting "ORA-01033: ORACLE initialization or shutdown in progress".
When trying to sqlplus system user on a standby instance that is in recovery mode.
Where as able to log in as sqlplus "/ as sysdba"
I checked the db it is not shuting down or starting it is in recovery mode.. no errors in alert log..
1) --------------------
$ sqlplus system@TEST1
SQL*Plus: Release 9.2.0.6.0 - Production on Sun Feb 26 04:47:35 2006
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Enter password:
ERROR:
ORA-01033: ORACLE initialization or shutdown in progress
$ ps -ef | grep mrp
oracle 26759 1 0 04:24:19 ? 0:00 ora_mrp0_TEST1
2) -------------
$ sqlplus "/ as sysdba"
SQL*Plus: Release 9.2.0.6.0 - Production on Sun Feb 26 04:50:14 2006
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production
3)--------
$ sqlplus "/ as sysdba"
SQL*Plus: Release 9.2.0.6.0 - Production on Sun Feb 26 04:50:14 2006
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production
4)----------
SQL> select process, status from v$managed_standby;
PROCESS STATUS
ARCH CONNECTED
ARCH CONNECTED
MRP0 WAIT_FOR_LOG
RFS RECEIVING

A standby database in recovery mode is only accessible as sysdba for administrative purposes. You have to open the DB in read only mode to access it as "normal" user.
See http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96653/manage_ps.htm#1014483

SP 2013 - Database Recovery Mode When Using SQL Server Mirroring

Hello Community,
Our DBA is configuring a High Availability Architecture for our SharePoint 2013 Farm. Essentially he is using SQL Server Database mirroring with a clustered automatic failover using a witness server. He has informed me that mirroring requires
that the databases are set to Full Recovery Mode, but that several of the databases are set to Simple Recovery Mode, the databases are the following:
SearchService_DB
SearchService_DB_CrawlStore
SearchService_DB_AnalyticsReportingStore
SearchService_DB_LinksStore
WSS_UsageApplication
User_Profile_DB
User_Sync_DB
User_Social_DB
However, when I checked the following article -
http://technet.microsoft.com/en-us/library/cc678868.aspx - I see that Simple Recovery Mode is the default configuration for these databases. So, finally, here is my question - will it be detrimental to these databases to set them to the Full Recovery
Mode?
Thanks!
Tom
Tom Molskow - Senior SharePoint Architect - Microsoft Community Contributor 2011 and 2012 Award -
Linked-In - SharePoint Gypsy

This really depends on your recovery objectives. The main reason for taking log backups, aside from truncating the log, is to be able to recover to a specific point-in-time. This is very helpful in mission-critical, highly transactional systems. I have not
seen a SharePoint environment require a point-in-time restore of the content or application service database. So for this case, you can overwrite the LDF bakups. Just make sure that you can recover your databases appropriately and meet your recovery objectives
on the farm level.
As far as the log file growth is concerned, you are correct. If you cap the size of your LDF file to let's say 10 GB, regular log backups will truncate the log, thereby, having space for additional transaction log records. The only risk here is when your
log backups are not frequent enough that the LDF file fills up before the next log backup runs to truncate the log. You run the risk of your database behaving as read-only and that will affect the site collections/applications using those databases
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

To open the database which is in recovery mode

Hi Folks
Could some one help me in opening a database which is in the recovery mode .
I applied a wrong archive log and come out of it
now when i try to apply the correct archive log it says its in recovery
could some suggest me in solving this problem. alter database recover until cancel using backup controlfile
2 ;
alter database recover until cancel using backup controlfile
ERROR at line 1:
ORA-00275: media recovery has already been started
cheers
alter database recover until cancel using backup controlfile

Oracle doesn't allow you to "apply a wrong archive log".
What commands did you execute to "apply" the archive log ? What messages did Oracle return ?
You can either
a. SHUTDOWN
or
b. ALTER DATABASE RECOVER CANCEL
to stop it from recovering
Then, (if you want to restart "recoveyr mode") issue
a. STARTUP MOUNT
b. ALTER DATABASE RECOVER UNTIL CANCEL USING BACKUP CONTROLFILE
I presume that this is not a "Managed Standby" database but a manually scripted database ?
Hemant K Chitale
http://hemantoracledba.blogspot.com
Edited by: Hemant K Chitale on Aug 19, 2010 11:10 AM

Change SharePoint_Config Database to simple recovery mode. Risk.

Hello,
we have SBS 2008 with Exchnage and OWA-Service.
The Logfile of SharePoint is very large (30 GB).
But we don't use SharePoint.
I want to change the recovery mode of SharePoint_Config Database to simple.
But i don't know, what of Application/Services/Programms use SharePoint Database.
What are the risks of changing SharePoint_Config Database to Simple Mode?
What of the Sevices/Programms use SharePoint Database ?
Thank You

Hi ,
As Dimitri pointed out, SharePoint DB is in SQL database, the change of it won't affect Exchange and Outlook Web Access.
If you use SharePoint in future, you may take a look at the following article about the effect to SharePoint database with simple recovery mode.
http://searchwinit.techtarget.com/tip/How-SQL-Server-recovery-models-impact-your-SharePoint-databases
Thanks
Daniel Yang
TechNet Community Support

If your database in Full Recovery mode, can you use Bulk Insert Task to load data

If your database in Full Recovery mode, can you use Bulk Insert Task to load data

If your database in Full Recovery mode, can you use Bulk Insert Task to load data
Yes you can ofourse but dont be in idea that logging will be mininal. Loggign will be as per recovery model full. Every thing will be logged. If you are going to use bulk insert task you can consider switching recovery model to Bulk logged but you will not
have option to do point in time recovery.
PS: please dont create duplicate threads
If you read first Note section in below link it clearly states that yes logging will be full and you can use
http://technet.microsoft.com/en-us/library/ms191244(v=sql.105).aspx
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Shrink Log file in log shipping and change the database state from Standby to No recovery mode

Hello all,
I have configured sql server 2008 R2 log shipping for some databases and I have two issues:
can I shrink the log file for these databases: If I change the primary database from full to simple and shrink the log file then change it back to full recovery mode the log shipping will fail, I've seen some answers talked about using "No
Truncate" option, but as I know this option will not affect the log file and it will shrink the data file only.
I also can't create maintenance to reconfigure the log shipping every time I want to shrink the log file because the database size is huge and it will take time to restore in the DR site, so the reconfiguration
is not an option :(
how can I change the secondary database state from Standby to No recovery mode? I tried to change it from the wizard and wait until the next restore for the transaction log backup, but the job failed and the error was: "the step failed". I need
to do this to change the mdf and ldf file location for the secondary databases.
can any one help?
Thanks in advance,
Faris ALMasri
Database Administrator

1. can I shrink the log file for these databases: If I change the primary database from full to simple and shrink the log file then change it back to full recovery mode the log shipping will fail, I've seen some answers talked about using "No Truncate"
option, but as I know this option will not affect the log file and it will shrink the data file only.
I also can't create maintenance to reconfigure the log shipping every time I want to shrink the log file because the database size is huge
and it will take time to restore in the DR site, so the reconfiguration is not an option :(
2. how can I change the secondary database state from Standby to No recovery mode? I tried to change it from the wizard and wait until the next restore for the transaction log backup, but the job failed and the error was: "the step failed". I need to do
this to change the mdf and ldf file location for the secondary databases.
can any one help?
Thanks in advance,
Faris ALMasri
Database Administrator
1. If you change recovery model of database in logshipping to simple and back to full Logshipping will break and logs wont be resored on Secondary server as log chain will be broken.You can shrink log file of primary database but why would you need that
what is schedule of log backup. Frequent log backup is already taking care of log files why to shrink it and create performance load on system when log file will ultimately grow and since because instant file initilaization is not for Log files it takes time
to grow and thus slows performace.
You said you want to shrink as Database size is huge is it huge or does it have lots of free space. dont worry about data file free space it will eventually be utilized by SQL server when more data comes
2. You are following wrong method changing state to no recovery would not even allow you to run select queries which you can run in Standby mode. Please refer below link to move Secondary data and log files
http://www.mssqltips.com/sqlservertip/2836/steps-to-move-sql-server-log-shipping-secondary-database-files/
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

What is impact to MDF file size if change database to simple recovery mode

Hi,
Currently I have a Database with 27GB MDF and 80GB LDF.
If I change from Full recovery to Simple recovery mode, would LDF information be transfered to MDF file and make
MDF file size exceed 100GB?

Hi
May I know how to perform point in time recovery? Currently the only backup we perform every 4 hours is the server OS snapshot.
Example :
1. Now is 6pm and some error transaction occurred.
2. We can perform 3pm server OS snapshot recovery on the mdf file. ( We would lost 3 hours data in this case )
3. Could we apply the ldf transaction log after OS snapshot recovery and roll it forward till 5:50pm?
You would be able to perform point in time recovery if you have
1. Database configured in full recovery mode
2. You were taking transaction log backups.(of course with full backup or may be differential)
In your scenario applying snapshot wont help you.What you have to do it you should have full backup in place .If you had full backup ,like full backup at 3 PM then you would have restored it with no recovery.After that suppose you took tansaction log backups
every on hour then restore 1 PM ,2 PM and 3 PM log backup all in nore covery.
Now i should have mentioned first but before restoring full backup you can also take tail log backup read this article
http://technet.microsoft.com/en-us/library/ms179314.aspx
So now after full and all log backups are applied with no recobery apply tail log backup with recovery and its quite possible that you might not have a data loss or in some scenario very small data loss( not 3 hrs as you would have with snapshot)
hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

DB2 change the database recovery mode

Hi Friends,
We are doing an upgrade, in the process will be necessary to change the DB recovery mode.
Database is DB2 9.5 and the platform is Unix (AIX). I wold like to clarify the process of change the recovery mode, I underestand that it is to switch off the logg retain, but I have found in some forums that in order to switch on the logg retain, when the upgrade finished, I have to have an full backup of this database.
I need to plan this activity and its effects.
Please do you know something about it, can you clarify me the process?
Thanks a lot.
Regards
Enrique Sánchez

The process is pretty straightforward:
1. Shutdown SAP and deactivate the database.
2. Enable recovery mode by setting logarchmeth1 (as user db2<sid>)
db2 update db cfg for <SID> using logarchmeth1 disk:<archivepath> immediate
3. Perform an offline backup of the database (as user db2<sid>)
db2 backup database <sid> to <backuplocation> compress without prompting
The backup time depends on the size of your system. Once the backup is complete, you can activate the database and bring up SAP.
- Sameer

MacBook Pro won't start after upgrade, not even in recovery mode

So here is what happened:
Yesterday, the app store icon told me that one update was not installed yet,because I need to restart the computer first (hard for me to reconstruct now, because I didn't really read it carefully, which I should have done, but Apple"just works™", so hey, why should I ). So I restarted the computer. This is where things went very wrong. Eventually during reboot, text appeared on the grey Apple logo screen, it looked like verbose boot mode, but overlaid on the "regular" grey boot screen with the  logo. Before I could read, what was happening, I got a kernel panic with the "hold down the power button to restart".
Holding down the power button took me to the login/file vault unlock screen (I have my disk encrypted). Unfortunately neither keyboard nor trackpad worked. So I held down the power button again, which brought me back to the login/file vault unlock screen.
At this point I noticed that it said in the lower part of the screen that, in case I had problems to enter my login information, I should press the power button for a long time and then again for a short time to get into recovery mode (this is all from my memory, I might not recall it exactly as it happened).
This made things kind of worse, it showed me the Apple logo with the progress bar, which advanced to about a third or a quarter, then the progress stopped and I ended up on a grey screen with a grey crossed circle in the center (looks kind of like an european no parking sign).
I tried booting into recovery mode by holding down the R key. This brings me to the progress bar and the subsequent grey screen.
I tried to boot into my time machine, by holding down the option key. This gets me to the boot volume selection, I can choose my time machine volume (external FW800 drive), but it does not use this volume to boot (I can hear that the external disk is not spinning). Instead I get the above mentioned behavior (progress bar, grey screen).
I tried to boot into target disk mode by holding down the T key. This only works, when I connect an external USB keyboard. This way I could use another computer to recover my important files (which is good). I could also peek at the logs. It seems as if the failed boot attempts do not produce logs. But I have the system log from the "restart to install update" process. The last few seconds or so I get a lot of these messages:
Feb 3 14:33:51 Larss-MacBook-Pro kernel[0]: Refusing new kext com.apple.kpi.libkern, v14.1: already have loaded v14.0.
I use a Macbook Pro 13" early 2011. I don't know the processor speed, because I cannot boot it. I guess it has 8 GB Ram (pretty sure I maxed it out).
I have an SSD installed (I replaced the original HD with a 1GB Samsung SSD). There is another post here, which sounds similar, but I definitely did not use "Trim enabler" or similar third party software.
I use Yosemite, I think I was pretty much up to date, I suspect the reboot was for the 10.10.2 installation, but I am not sure (I simply didn't look when I hit that reboot to install button).
Yosemite on SSD wont boot and wont go in safe or recovery mode
Anyone any ideas? Any help is appreciated!

So I just went through the install.log.
First of all, there I found out that I have a MacBook Pro (13-inch, Mid 2010):
Feb 3 14:31:12 larsmbpro.domain.com suhelperd[336]: GetModel: model = MacBookPro; major rev = 7; minor rev = 1
I think it was indeed the upgrade to Yosemite 10.10.2:
Feb 3 14:31:18 larsmbpro.domain.com softwareupdated[334]: SoftwareUpdate: Added foreground transaction [0x1] for OSXUpd10.10.2-10.10.2
but there was also a firmware update included:
Feb 3 14:31:21 larsmbpro.domain.com installd[363]: PackageKit: packages=(
"PKLeopardPackage <file:///Library/Updates/031-17157/OSXUpd10.10.2Patch.pkg>",
"PKLeopardPackage <file:///Library/Updates/031-17157/FirmwareUpdate.pkg>"
The last messages in this log are:
Feb 3 14:33:07 larsmbpro.domain.com Software Update.app[2747]: Running /sbin/reboot
Feb 3 14:33:07 larsmbpro.domain.com softwareupdated[334]: Removing client SUUpdateServiceClient pid=2747, uid=0, installAuth=YES rights=(system.install.apple-software, system.install.apple-software.standard-user, system.install.software, com.apple.SoftwareUpdate.modify-settings), transactions=1 (/System/Library/CoreServices/Software Update.app/Contents/MacOS/Software Update)
According to the system.log, the shutdown happened 14:33:08. The boot time is 14:33:24, no log entries between 14:33:08 and that time. 16 seconds seems awfully long for a reboot:
Feb 3 14:33:08 larsmbpro kernel[0]: Kernel requests now disabled.
Feb 3 14:33:24 localhost bootlog[0]: BOOT_TIME 1422970404 0
Feb 3 14:33:46 localhost syslogd[19]: Configuration Notice:
ASL Module "com.apple.AccountPolicyHelper" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.

Database in Suspect Mode in SQL Server 2000 Log Shipping Environment

Hi All
We have movement of SQL Server 2000 at physical level. We have disable jobs and stop Agent and SQL Server services.
After moved the server we have started the server and then start SQL Server 2000 services.
All of databases in SUSPECT mode. Files are in correct folders as were before shutdown the server
What shall I do e.g. why databases come up in SUSPECT mode? what to check and how to get database live?
Pls help it is critical...
Thanks in Advance

All of databases in SUSPECT mode. Files are in correct folders as were before shutdown the server
What shall I do e.g. why databases come up in SUSPECT mode? what to check and how to get database live?
Pls help it is critical...
Thanks in Advance
Hello,
Did you made sure no transactions like restore logs were running when you stopped SQL server service or agent .I have seen in SQL 2000 an abrupt stop of SQL Server agent when its doing a process can sometimes force database in suspect mode.
I would like you to get your disk analyzed by vendor ASAP for any fault in disk at first go it seems to me an underlying hardware issue.
Please can you check errorlog and event viewer to find out any possible cause for database going into suspect mode
I always suggest to use Backup and restore method of recovery to get out from suspect database problem.If you dont have then you can move with DBCC Checkdb and various repair options but be sure
DATA LOSS might be possible when you use repair allow data loss and repair_rebuild removes constraints.
hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Database in suspect mode

i was going through this article about recovering a database in suspect mode :
http://www.mytechmantra.com/LearnSQLServer/Repair_Suspect_Database_P2.html
in the article the error seems to indicate corruption in the log :
Error: 9003, Severity: 20, State: 9. The log scan number (189624:16:2) passed to log scan in database
'BPO' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf
if the corruption is in the log, then is not the logical solution to bypass the recovery process and then truncate the log with no_log option and then bring the database online?
and dbcc checkdb (<db>,repair_allow_data_loss) repairs the data pages or the log pages?
and any other options/ways/articles about bringing a suspect database online?
appreciate the insights.

datafile corruption : put db in emergency mode / put db in single user mode / dbcc checkdb with REPAIR_ALLOW_DATA_LOSS/ dbcc checkdb on database
again/put db back in multi user mode.
There is no need to do this. This is totally not required.
You can
Switching the database to the Simple recovery model
Performing a checkpoint (which should clear the active log as long as nothing else requires the log to be kept active)
Switching back to the Full recovery model
Reestablishing the log backup chain by performing a full or differential backup
Or you can rebuild log as already pointed in my reply.
Or you can restore from known valid backup.
There is no need to move data as well because actually its not related to data.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode

Hi All,
Need help from the gurus.
Currently we are in state unable to do anything.
Was using a database and all of a sudden it crashed. Tried to mount the database, open it, it failed. Also tried the recover and alter database open, even that failed. Errors are as follows.
Errors in file e:\oracle\product\10.2.0 \admin\devrevdb\bdump\devrevdb_p000_2620.trc:
ORA-00603: ORACLE server session terminated by fatal error
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
ORA-00449: background process 'DBW0' unexpectedly terminated with error 1242
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
In my spfile, the administrator has set only two control files and there is no mirroring and hence do not have another control file that will help me boot the db.
Please let me know how I should go about it. I am only a timebeing person trying to carryout a db activity. Any help would be of great help.

Hemant,
thanks for the reply.
I tried the way you suggested and it threw an error.
ORA-01145: offline immediate disallowed unless media recovery enabled
I searched and found that an additional tag of drop needs to be added to the command which you suggested.
ALTER DATABASE DATAFILE '<filename>' OFFLINE DROP.
i don't know what will the drop command have an effect ?
i have copied the data file to another location. Since i don't know much, i just want to be sure of what im doing.
if the above command is successfull, will it drop the datafile or the tablespace and i can no more use it. How can i use the copied datafile.
Thanks,
Sachin
I

Changing database to noarchivelog mode during impdp

Hi Guys,
I am using Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production on RHEL5.
I am in the middle on the impdp and I want my database to run on noarchivelog as it creates a lot of archivelogs.
Will it be proper if I stop the import:
e.g Import> STOP_JOB=IMMEDIATE
and shutdown the database put the database on noarchivelog mode.
then opne database and
impdp hr/hr@mydb ATTACH=myfulljob Will these work fine?
Or should I execute:
alter system archive log stop;
Please Help !!!!!!!!!!!

Vinod Dhandapani wrote:
Running the database in Noarchivelog mode means you should be ready to lose data incase there is any crash. I would recommend you to change the size of the redologs so that it will not create frequent archivelogs. Which does nothing about the space required for the archivelogs. If you are generating redo at the rate of 1gb/hour, you will consume archivelog dest space at the rate of 1gb/hour. Doesn't matter if those files are 10mb each or 100mb each.
If space is the problem then use a shell script to move the archivelog to another location (Tape)....And hopefully that shell script is invoking rman to do the work, so that in the event of recovery, rman will know that backups were taken and where they are located.
>
Incase you want to convert the database from archivelog to noarchivelog, follow the steps provided in the following link.
http://racadmin.blogspot.com/2011/06/convert-archivelog-mode-to-noarchivelog.html
Thanks

Database in recovery mode

Similar Messages

Maybe you are looking for