RDBPROD: Slow Performance After Upgrading Oracle Rdb
(Doc ID 1955869.1)
Last updated on FEBRUARY 21, 2019
Applies to:Oracle Rdb Server on OpenVMS - Version 126.96.36.199 to 188.8.131.52 [Release 7.3]
HP OpenVMS Itanium
HP OpenVMS Alpha
Upgraded from Oracle Rdb 184.108.40.206 running on OpenVMS Itanium V8.3-1H1 to Oracle Rdb 220.127.116.11 running on OpenVMS Itanium V8.4.
After running a particular application, the cardinality of a table updated by the application gets set to 0 rather than the correct value, some tens of thousands. You have hit BUG 19611808 "RDB$CARDINALITY TURNED TO 0 AFTER RUNNING A PROCEDURE WITH AN UPDATE STATEMENT".
BUG 19611808 has been corrected in Oracle Rdb 18.104.22.168, but is there a way to work around this bug without upgrading to the new release?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document