DELETE anomaly

Our shop has two production jobs that generate several reports by loading many thousands of rows of potential items into a table, then deleting the items that are of no interest. After the load steps there are about 200,000 rows. After the DELETE step, about 200 remain.

The jobs have run just fine for several years. When they ran this last time, the DELETE step found no rows to delete.

The DELETE statement finds no rows to delete. None. Though it has for years. The client makes no difference. (A Copy/Paste of that statement from the batch script that runs via SQL*PLUS into TOAD makes no difference.) "0 rows found".

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Featured Post

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

From the Oracle SQL Reference (http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/queries006.htm) we are told that a join is a query that combines rows from two or more tables, views, or materialized views. This article provides a glimps…

Have you ever had to make fundamental changes to a table in Oracle, but haven't been able to get any downtime? I'm talking things like:
* Dropping columns
* Shrinking allocated space
* Removing chained blocks and restoring the PCTFREE
* Re-or…