Commit causes rows to disappear [solved: rogue client]
557616Aug 22 2012 — edited Aug 24 2012I just ran into the strangest thing.
Running XE 11g on Linux and Apex. My apex app was acting strange so I went into SQLDeveloper to run the raw commands that the apex app was supposed to be running.
I ran two insert statements, inserting data into a table (insert into a table using a select).
Then I did a select from the table to verify that the rows were there.
The two rows were there. They looked exactly as I had inserted them.
Then I issued a commit.
Guess what happened? My two rows were GONE!
I did this multiple times, each time I got the same result, the rows were gone AFTER the commit! There were no errors thrown in sqlDeveloper and nothing in the alert_XE.log.
Not knowing what else to do, I restarted the database (shutdown immediate; startup;). I reconnected and ran the exact same inserts and commits an it worked! The rows where there and my Apex app was working fine.
I've been an Oracle Programmer or DBA since 1994 and have never seen anything like this. The database has been up for 120 days and my only non-system generated tablespace is 20Meg.
The table in question has some unique constraints, but my statements didn't conflict and no errors were thrown. I'd try to open an SR, but there isn't a trace or anything to submit.
Anyone else seen this behavior in XE 11g?
Edited by: mcallister on Aug 24, 2012 8:29 AM