Start a conversation
  1. Pivotal Support
  2. Pivotal Articles
  3. Articles

PBS 6.6.4.*: Patched <code>rda.dll</code> Shows Lower Windows File Version (Expected Behavior)

Contents

Overview

In Pivotal Business Server (PBS) 6.6.4.*, you may notice an apparent DLL “downgrade” after applying the official performance patch: the patched rda.dll reports a lower Windows file version (for example, 6.6.1.602) than the original file (for example, 6.6.4.251).

This is expected and does not indicate the patch is incorrect or incompatible. The fix is to deploy the rda.dll from the official patch ZIP referenced by the KB (KB: “Resolving Performance Issues in Pivotal Business Server Version 6.6.4.8”) and validate performance in Test before promoting to Production.

Solution

Issue

You apply the PBS 6.6.4.* performance patch (from the official KB ZIP) and then notice that the patched rda.dll shows a lower Windows file version than the existing DLL.

What you observe (verbatim examples)

  • Patched rda.dll Windows file version: "6.6.1.602"
  • Original rda.dll Windows file version: "6.6.4.251"

Affected versions

  • Pivotal Business Server: 6.6.4.* (including 6.6.4.0)

Cause / Why this happens

The Windows “File version” shown in DLL properties is internal metadata and does not reliably increase in lockstep with the PBS product version. The patched rda.dll can display a lower file version even though it contains the intended fix (the SQL execution plan caching/performance regression fix for PBS 6.6.4.x).

Resolution

Use the rda.dll shipped in the official patch ZIP referenced by the KB article for PBS 6.6.4.* (KB: “Resolving Performance Issues in Pivotal Business Server Version 6.6.4.8”). The fact that the file version appears lower (for example, 6.6.1.602) is expected.

Implementation steps (recommended rollout)

  1. Validate in a non-production environment first
    • Apply the patch to Test/Staging and verify performance and stability before promoting to Production.
  2. Stop services
    • Stop the Pivotal Business Server service on the application server(s).
  3. Back up the existing DLL
    • Create a backup copy of the current rda.dll (store it with a timestamp and change record reference).
  4. Deploy the patched DLL
    • Extract the official patch ZIP referenced by the KB.
    • Copy the patched rda.dll from the ZIP into the PBS installation location, replacing the existing file.
  5. Restart and validate
    • Start the Pivotal Business Server service.
    • Re-test key user workflows (common forms/operations) that previously showed performance degradation.
    • Confirm there are no new errors and that performance is improved/acceptable.
  6. Promote to Production
    • Repeat the same procedure in Production using your normal change management process.

How to confirm the fix is in place

  • The deployed rda.dll matches the one from the official patch ZIP referenced by the KB.
  • Previously slow/high-impact screens or operations show the expected performance improvement.
  • No new functional regressions are observed in routine workflows.

If results are not as expected

If performance does not improve or new errors appear after applying the patched rda.dll, collect:

  • Which screens/operations are slow
  • Approximate data volume/dataset size involved
  • Any exact error messages shown
  • Relevant server/application logs from the time of reproduction

Then proceed with deeper investigation.

Frequently Asked Questions

1. Is it safe to replace rda.dll in PBS 6.6.4.0 using the patch described for PBS 6.6.4.8?

Yes. The patch described for PBS 6.6.4.8 is intended to apply to PBS 6.6.4.* installations (including 6.6.4.0) when addressing the 6.6.4.x SQL plan-caching/performance regression. Use the rda.dll from the official patch ZIP referenced by the KB.

2. Why does the patched rda.dll show a lower Windows file version (for example, "6.6.1.602") than my original file?

The Windows file version is internal metadata and does not necessarily track the PBS product version. A lower displayed file version does not mean the DLL is older or incompatible if it came from the official patch ZIP.

3. How do I verify I used the correct DLL?

Confirm the deployed rda.dll was copied directly from the official patch ZIP referenced by the KB (not from another environment or older hotfix bundle). Then validate via functional testing and performance testing of the affected operations.

4. What are the minimum steps to apply the patch?

Stop the PBS service → back up the existing rda.dll → copy in the patched rda.dll from the official KB patch ZIP → restart the PBS service → re-test key operations.

5. What should I do if performance is still poor after applying the patched DLL?

Re-test using a representative dataset size and capture details of the slow operations (screens/actions, data volume) plus any logs/error messages. If the issue reproduces only with large datasets, include that detail as it can affect whether the SQL plan-caching regression is the primary bottleneck.

Choose files or drag and drop files
ai_initiated
atlas_studio
kb_automation
Was this article helpful?
Yes
No

  1. Priyanka Bhotika

  2. Posted

Comments