Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Data Base running too fast ???

RE: Data Base running too fast ???

From: Jain, Akshay <Akshay.Jain_at_cit.com>
Date: Wed, 14 Jun 2000 10:45:47 -0400
Message-Id: <10528.109233@fatcity.com>


How do you feel about creating another table as a copy of this table, but add a field of system milliseconds, or a sequence capture. This field would be added to the primary key.

Then create a view to replace the original table. This view could have an insert trigger to insert the data to the table, but to stick on the sequence number, thus accomplishing uniqueness.

Such a solution is still a kluge, but perhaps it might work for now, and not depend on the application level fix, which is what is really required.

Akshay Jain



Newcourt-CIT
Tel. (416) 507-5385
mailto:Akshay.Jain_at_cit.com

-----Original Message-----
From: Chris Royce [mailto:Chris_at_Royce.net] Sent: Tuesday, June 13, 2000 3:51 PM
To: Multiple recipients of list ORACLE-L Subject: Data Base running too fast ???

Anyone had problems with a database running too fast. It was a first for me. I recently, upon gaining additional disk and memory, was able to re-archetect several of my production instances. I also tuned the heck out of them and optimized to the maximum that our physical configuration would allow.

One of our 'canned' applications captures employee clock punches at our manufacturing plants and sends them to an Oracle database where they are processed before going to our HR application. Shortly after the database re-org we started encountering duplicate records in a transaction table
(no unique key constraint). The application Vendor spent a bunch of time
debugging the problem and it was discovered that the clock punches are captured only down to the second and as a result the processing speed of our system allows duplicate records when multiple punches are captured. Prior to the reorganization this had not been an issue. The Vendor complained that the database was too fast !!! Sometimes you can't win. We declined to 'slow down' the database and suggested that the onus be on them to refine the degree of granularity that the time records are captured.

Much better situation than some of the incredibly interesting disaster stories that have appeared lately.

Chris Royce
Jamestown NC

-- 
Author: Chris Royce
  INET: Chris_at_Royce.net

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L

(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
Received on Wed Jun 14 2000 - 09:45:47 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US