Skip to main content
Solved

DataAging - Failed to Prune Job Histories [32:313]


Marcel
Commvault Certified Expert
Forum|alt.badge.img+4
  • Commvault Certified Expert
  • 12 replies

We upgraded from FR26 to FR28.10 last thursday
Since then we have a DataAging error:

5624  27e4  08/02 13:39:27 2935891 CVSimpleDBConnObject::execQuery() - Failure executing SQL. 
    SDB Error Code: [5]. 
    Error message: [INFO: [XML parsing: line 1, character 38, unable to switch the encoding] [RecNum:1, Object:daDeleteJobOptions, State:42000, NativeErr:9402, Proc:daDeleteJobOptions, RowNum:1, Severity:16, LineNum:232, Spid:59] ]. 
    SQL Query:[EXEC DaDeleteJobOptions ?, ?, ?....]
5624  27e4  08/02 13:39:27 2935891 DBBase-SQL() - dbcursors.cpp:335, Input parameters:
5624  27e4  08/02 13:39:27 2935891 DBBase-SQL() - dbcursors.cpp:336, [1]:[7]
5624  27e4  08/02 13:39:27 2935891 DBBase-SQL() - dbcursors.cpp:336, [2]:[90]
5624  27e4  08/02 13:39:27 2935891 DBBase-SQL() - dbcursors.cpp:336, [3]:[15]
5624  27e4  08/02 13:39:27 2935891 ArchPruneBase::pruneJobHistory() - Failed to delete job options and job resource history with database error [1000]: [INFO: [XML parsing: line 1, character 38, unable to switch the encoding] [RecNum:1, Object:daDeleteJobOptions, State:42000, NativeErr:9402, Proc:daDeleteJobOptions, RowNum:1, Severity:16, LineNum:232, Spid:59] ]. Proc return Code [0]
5624  27e4  08/02 13:39:27 2935891 DATA AGING() - JOB [2935891]: Failed to Prune Job Histories.


I already upgraded SQL 2016 to latest SP3 and security patch.
Anyone? :)

Best answer by Marcel

I found a patch that fixed my issue: https://cloud.commvault.com/webconsole/browse/MyDrive.do?shareFolderId=776493&path=1c76c70347da4d979e19e14952086d3c&iP=PUBLIC

It is supposed to be installed on top of 11.28.14

View original
Did this answer your question?

10 replies

Mike Struening
Vaulter
Forum|alt.badge.img+23

@Marcel , thanks for the post!  

I found (only) 2 cases with this exact error.

The one that mirrors yours (happened only after upgrading to 11.28) was closed by the customer without confirming.  Recommendation was to upgrade SQL 2012 to SQL 2019 (though 2016 in your case should be supported).

The other one (much older) was fixed by doing this:

Review of the database shows "Days to keep Job Options for a completed job" setting is set to 999999999 days. (2,739,726 years) This was reduced this to 9999 (27 years) and data aging run successfully.

Now, if the second one doesn’t apply to you, I would open a support case (and share the number here).


Marcel
Commvault Certified Expert
Forum|alt.badge.img+4
  • Author
  • Commvault Certified Expert
  • 12 replies
  • August 3, 2022

@Mike Struening , thanks for the reply!

I checked the setting, and the value is 7. I tried to change it to 9999 (as a test), however the maximum allowed number is 999. I changed it back to 7 after a DA test.
Unfortunately that was not the solution.

Then I think I will have to open a support case.

Thanks so far!


Onno van den Berg
Commvault Certified Expert
Forum|alt.badge.img+19

Not sure if those messages are also seen in the case of this KB article but did you apply the fix that is embedded in this KB article @Marcel https://kb.commvault.com/article/77146


Marcel
Commvault Certified Expert
Forum|alt.badge.img+4
  • Author
  • Commvault Certified Expert
  • 12 replies
  • August 3, 2022

Thanks Onno, I just updated to 11.28.14 this morning, so the fix should be in there.

However no luck...


Onno van den Berg
Commvault Certified Expert
Forum|alt.badge.img+19

Mmmmm :-( So I guess it's time to open a ticket. Curious to here more about the root cause, so I'll keep on following! Please keep us posted!


Marcel
Commvault Certified Expert
Forum|alt.badge.img+4
  • Author
  • Commvault Certified Expert
  • 12 replies
  • Answer
  • August 17, 2022

I found a patch that fixed my issue: https://cloud.commvault.com/webconsole/browse/MyDrive.do?shareFolderId=776493&path=1c76c70347da4d979e19e14952086d3c&iP=PUBLIC

It is supposed to be installed on top of 11.28.14


Onno van den Berg
Commvault Certified Expert
Forum|alt.badge.img+19

Thanks for sharing @Marcel! Any idea which maintenance release will contain the fix? 


Marcel
Commvault Certified Expert
Forum|alt.badge.img+4
  • Author
  • Commvault Certified Expert
  • 12 replies
  • August 17, 2022

Unfortunately, no


Mike Struening
Vaulter
Forum|alt.badge.img+23

@Onno van den Berg , I just checked and I can see it is being built, but no maintenance release has been finalized yet.


Onno van den Berg
Commvault Certified Expert
Forum|alt.badge.img+19
Mike Struening wrote:

@Onno van den Berg , I just checked and I can see it is being built, but no maintenance release has been finalized yet.

Thanks for the heads-up! 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings