Quite interesting performance problem.

From: Howard Latham <howard.latham_at_gmail.com>
Date: Fri, 19 Jun 2015 13:06:07 +0100
Message-ID: <CAPCNhx1nQAVRr+x5v_+ehNowKF4LdWzEWa=8RDZturUPttsyMA_at_mail.gmail.com>

RH Linux 64bit E4
Oracle 11.2

In case anyone runs into this problem I thought I'd share it. We have some code that ran fine on Oracle in about 30 minutes - when we moved to it took over 3 hours.
It wrote 3/4 million rows to a temp table then wrote it to disk. Using UTL_FILE

Nothing in the traces no tuning fiddling with spin count, moving disks, analyzing tables, watching spotlight for hours, nothing helped.

Eventually our developer tried to reproduce the problem and discovered there was no commit after writing the temp table. Adding a commit returned the speed to what we used to get. I agree "commit little and often" is or should be a developer's mantra - along with "beware of nulls". However clearly some behaviour in a temporary buffer has been changed. But I ackknowledge that the code was 'wrong' in the first place.

Howard A. Latham
Received on Fri Jun 19 2015 - 14:06:07 CEST

Original text of this message