Bset practises about Oracle database

General
, , , ,
1

We’ve just migrated PEGA database from DB2 to Oracle, and currently facing problems as below.
Would appreciate a lot if anyone can provide some advise.

  1. Long time network waiting/table lock - SQL*Net more data from client.
    Form the Oracle EM, we can see long time network waiting/table lock events.
    These sessions cannot be endded automically, has to be killed manually.
    And the Weblogic datasources have to reset manually at the same time.

  2. Poor performance after a certain idle time.
    Firt time excution of some the SQL query probably will take more than 30s (even more than 100s sometime), and then spped up to under 1s.
    After a while, the execution slowed down again - with excatly the came query SQL.

  3. Any other best practises about PEGA running with Oracle database?

The versions:
PEGA 23.1.4
Oracle 19c (not RAC)
Weblogic 14.1.1.0.0
JDBC dvier 18.3.0.0.0

We’ve checked instllation guide as below, seems no such information mentioned.

2

@GAVINHSU Are the DB server(s) and the App servers using the same network? Hopefully not a lot of network hops separating them.

Also unable to see your versions (blocked with “Proprietary information hidden”), maybe if you took a screenshot of them then you could post that image here?

3

For the network waiting issue, it’s resolved after upgrading the JDBC driver to latest version.

For the poor performance issue, it seems to be a Oracle 19c’s default behavior. We’re consulting our DB vender for further assistance.

4

I like that this new system doesn’t hide your software and driver versions.

This is a great example, if I could have seen the versions would have a chance to suggest if there were newer drivers available or not. Nice improvement there.