Sql Error Message ID 3013 & 4305 for Standby / Read-Only database that we use for import data heavily

Sorry. I am not a DBA, but a SQL Developer, so I am trying to get some general support/feedback on my case (and when I Googled the issue, remedy seems so scattered so I decided to post here).

I got this error message on SQL Server Agent for one of "Standby / Read-Only" databases.

enter image description here

SQL Server Error 3013 and 4305.

Bottom is some of error messages:

6_Exec SQL Nightly_StandByReporting_Run0235AM_PST,Error,1, BNSQL2\PCCDAILY,6_Exec SQL Nightly_StandByReporting_Run0235AM_PST,Exec,,Executed as user:  BNSQL2\JDoh. ...0000001<c/>  which is too recent to apply to the database.  An earlier log backup that includes LSN 201999000000891200001 can be restored.  [SQLSTATE 42000] (Error 4305)  RESTORE LOG is terminating abnormally.  [SQLSTATE 42000] (Error 3013)  The log in this backup set begins at LSN  203741000000458400001<c/>  which is too recent to apply to the database. An earlier log backup that includes LSN  201999000000891200001 can be restored.  [SQLSTATE 42000] (Error 4305)  RESTORE LOG is terminating abnormally.  [SQLSTATE 42000] (Error 3013)  The log in this backup set begins at LSN  203744000000476800001<c/>  which is too recent to apply to the database. An earlier log backup that includes LSN  201999000000891200001 can be restored.  [SQLSTATE 42000] (Error 4305)  RESTORE LOG is terminating abnormally.  [SQLSTATE 42000] (Error 3013)  The log in this backup set begins at LSN  203749000000381600001<c/> which is too recent to apply to the database.  An earlier log backup that includes LSN 201999000000891200001 can be restored.  [SQLSTATE 42000] (Error 4305) RESTORE LOG is terminating abnormally.  [SQLSTATE 42000] (Error 3013) The log in this backup set begins at LSN  203788000000038400001<c/> which is too recent to apply to the database.  

When I Googled, this is brief reason. "BACKUP DATABASE is terminating abnormally"

I am not sure why this happened, but I can only guess that this happened due to some type of memory or hardware issues because we use this database heavily to import data (into other database).

When I searched more for remedies, following are given (from this site):

  • Check Security Permission for user
  • Delete the Previous Backup
  • Perform Full Backup Restoration

I am not sure how to apply for "Standby / Read-Only" database though.

I would appreciate for any help to fix the issue.

Disable autovacuum for one (pretty much read-only) database in a cluster

I’ve got a PostgreSQL cluster on my development system in which I’ve created several databases. I also have a dump of the last state of the DB of an old system imported in which I (very) occasionally need to look something up, so this database is pretty much read-only, while the others are live (if low traffic except for the Akonadi one).

I am finding lots of instructions for disabling autovacuum either globally (i.e. for the entire DB cluster) or for individual tables, but how can I permanently disable it for just one database in the cluster?

Can I make a short-lived readonly snapshot for reporting in Azure SQL DB?

I have an Azure SQL DB (OLTP), that is under considerable load, let’s call it AppDB. AppDB is transactionally consistent, but new rows are written to it constantly. Now I need to populate ReportingDB based on AppDB state every 30 minutes. Reporting population job runs several moderately big queries against AppDB, those queries, unfortunately, can’t be wrapped in a transaction but still have to all run on consistent data. That is, I can’t have situation Query 1 runs=> new rows inserted into AppDB => Query 2 runs. All my queries have to see data the way it was when Query 1 started.

I was hoping I can use Snapshots to create a read-only snapshot for Reporting job to use. From description, creation of such a snapshot should be fast and subsequent "copy on write" performance hit should be manageable. Snapshots lifetime would be under 10 minutes on average.

But now it looks like Azure SQL does not support CREATE DATABASE ... AS SNAPSHOT OF ..., it only supports CREATE DATABASE ... AS COPY OF ..., which I expect to be a lot slower (probably not meant to be used for reporting snapshot).

What would be a good way to create quick and short-lived read-only snapshots for reporting in Azure SQL DB?

P.S. We have considered replication, but it is not an option for us at the moment due to policy limitations.

Unable to set a People or Group field as Read-Only inside our edit form

I have a custom list inside sharepoint online site, and inside the list’s Edit form i want to disable a People or Group field named “Project Manager” using jQuery, but i am not sure if this is possible, here is a screen shot of the markup:-

enter image description here

now i already have a jQuery function added to my Edit form inside a script editor web part, and i am able to disable some Input and Select fields using the below code, but not sure how i need to disable the People or Group fields? as seems they do not have any input as shown in the above markup..

$  (function() {        $  ("input[id^='ProjectEstimatedDate_']").attr('disabled', 'disabled');       $  ("select[id^='ProjectPriority_']").attr('disabled', 'disabled');       //code goes here for other input and select fields     }); 

Excel Sheet Read-Only

we have an issue that the user once clicked on the excel/word/PPT file it opens as Read Only, the changes made on the file can not be saved to the original file located on the SharePoint library !! but when you open the file uploaded on the SharePoint from the using “open with Explorer” you can edit the file and save the changes. Any one can assist? enter image description here

Should read-only text appear as plain text or in a read-only textbox?

Should I use labels for read-only information, or should I use read-only text boxes to maintain the look of the fields?

It seems to me that if something is in a textbox it implies there is some way to edit it, whereas plain text is explicitly read-only.

Update: While my question is similar to Locking input form fields, does it make sense?, mine is different in that I’m referring to fields that are never editable by anyone. It’s not based on the user’s rights or role.

mockup

download bmml source – Wireframes created with Balsamiq Mockups

Should read-only text appear as plain text or in a read-only textbox?

Should I use labels for read-only information, or should I use read-only text boxes to maintain the look of the fields?

It seems to me that if something is in a textbox it implies there is some way to edit it, whereas plain text is explicitly read-only.

Update: While my question is similar to Locking input form fields, does it make sense?, mine is different in that I’m referring to fields that are never editable by anyone. It’s not based on the user’s rights or role.

mockup

download bmml source – Wireframes created with Balsamiq Mockups

HDD partition now read-only, don’t know why

I am new to Ubuntu and primarily home user. I have 100GB partition to store my files. My OS has recently upgraded to 18.04. Not sure what has happened but this 100GB partition has become readonly. Using explorer, I am unable to create new folder or file.

I have tried with MKDIR command on terminal but it returned with

dp-ubuntu@dpubuntu:/media/ubuntuhost/Ubuntu-Files$ sudo mkdir test [sudo] password for dp-ubuntu:
mkdir: cannot create directory ‘test’: Read-only file system

please help me with permanent solution.