BUG REPORT: In NetBackup versions 6.5.2 and 6.5.3, attempts to update a policy through the GUI may result in a status code 238

Problem

BUG REPORT: In NetBackup versions 6.5.2 and 6.5.3, attempts to update a policy through the GUI may result in a status code 238

Solution

Bug:  1463161

Symptoms:  After deactivating or activating a policy, any attempt to make further policy changes results in a status 238  An example is below:
 

The log data shows messages similar to the following:

From the admin log:
08:23:56.583 [7664] <2> db_CLASS_Ex: db_end_sts() failed: the database contains conflicting or erroneous entries
08:23:56.583 [7664] <16> alterinfo: db_setCLASS_INFO failed: the database contains conflicting or erroneous entries (238)
08:23:56.583 [7664] <2> bpplinfo: EXIT status = 238

From the bpdbm log:
08:23:56.579 [7674] <16> class_db: Data for policy <policy_name> is stale: incoming generation: 7, existing generation: 8
08:23:56.579 [7674] <2> bpdbm: request complete: exit status 238 the database contains conflicting or erroneous entries
*Note that the generation number referenced in the above log snippet can be any number.

Workaround:
The work around for this issue is to manually refresh the policy prior to making changes by using the refresh button.  An example of that button is below:
 

ETA of Fix:
The formal resolution for this issue (Etrack 1463161) is included in the following patch release:
  • NetBackup 6.5 Release Update 4 (6.5.4)
This release is available at the Support web site at:
 http://www.symantec.com/business/support/downloads.jsp?pid=15143


Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)