SQL Performance (MOSC)

MOSC Banner

What is the performance impact of updating the hash key in a hash partitioned table?

Oracle Database 19.12

Exadata

Goldengate 19.1

Scenario:

Site to site replication has been configured to maintain a secondary database as a logical copy of the primary database using Goldengate. There is no filtering or transformation, its simple like for like copying. The databases are on identical releases and exadatas.

An update that executes in 1 millisecond on a table in the Primary database is reformatted by Goldengate and takes 2 seconds to execute when replicated to the secondary database.

The table is called ACCOUNT, has a primary key of ACC_ID and is hash partitioned on that key.

So the Update goes from something like this on the Primary...

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center