SQL Log Shipping Error after full disk issue

ricge01

Getting the following: 5/26/2019 6:00:01 PM: Error 890: RESTORE DATABASE permission denied for database:  (databasename)
5/26/2019 6:00:01 PM: SQL error 945: Database 'databasename' cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.

We have increased the diskspace, but database is still in Recovery Pending/Standby state

Originally got message:

5/26/2019 6:12:56 AM: SQL Server error
 
5/26/2019 6:12:56 AM: SQL error 3013: RESTORE LOG is terminating abnormally.
5/26/2019 6:12:56 AM: SQL error 3441: During startup of warm standby database 'databasename' (database ID 8), its standby file ('D:\HCHB_IMPORT\LogShip.dat') was inaccessible to the RESTORE statement. The operating system error was '112(There is not
 enough space on the disk.)'. Diagnose the operating system error, correct the problem, and retry startup.
5/26/2019 6:12:56 AM: Processed 0 pages for database 'databasename', file 'HCHB_TSCH_Data' on file 1.
5/26/2019 6:12:56 AM: Processed 551188 pages for database 'databasename', file 'HCHB_TSCH_log' on file 1.

What is the proper syntax to run and startup up the standby database?  I will continue to see if I can find the startup syntax

Dan B

Hi ricge01,

Thanks for posting on the Redgate forums.

The article here should get the database online https://sqlandsql.wordpress.com/2014/11/05/sql-server-bringing-a-database-online-from-restoring-or-standby-modes/, please do let me know if you need any further assistance.

ricge01

Thanks, I actually tried to do the restore with Standby and found that mssql had the file still in use, so I stopped and started the services and this put the database back into a restoring mode and I was able to continue with my restores and then got the database back to Standby/Read Only mode when it completed.