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? :)
DataAging - Failed to Prune Job Histories [32:313]
+4- Commvault Certified Expert
- 12 replies
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
+23- Vaulter
- 4996 replies
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).
+4- Commvault Certified Expert
- 12 replies
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!
+19- Commvault Certified Expert
- 1252 replies
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
+4- Commvault Certified Expert
- 12 replies
Thanks Onno, I just updated to 11.28.14 this morning, so the fix should be in there.
However no luck...
+19- Commvault Certified Expert
- 1252 replies
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!
+4- Commvault Certified Expert
- 12 replies
- Answer
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
+19- Commvault Certified Expert
- 1252 replies
Thanks for sharing
+23- Vaulter
- 4996 replies
+19- Commvault Certified Expert
- 1252 replies
Thanks for the heads-up!
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.