Tag Info

Hot answers tagged

2

You're issuing a "recover database" command, which will recover the database as far as possible. If that includes the archivelogs/redo logs which contain your "truncate" command, then this will also be re-played and the table truncated again. Try doing the restore on it's own, or recovering to a specific time using RECOVER UNTIL... then opening the DB ...


1

I have no idea what I'm doing™, but the following, equivalent query seems to do the trick for me (at least, it was equivalent before you had edited your query to use a LEFT JOIN...): SELECT m.id, sub.cnt FROM m JOIN ( SELECT d.m_id, COUNT(1) AS cnt -- (+ other functions) FROM d WHERE d.m_id IN ( SELECT COLUMN_VALUE FROM TABLE( NEW ...


1

Hmmm.... this is an interesting one. The Oracle optimizer is a bit of a black box as far as mere mortals like myself are concerned... Jonathan Lewis wrote a 536 page book on the topic and that's just the **fundamentals* (and it ain't bedtime reading!). Two questions. a) Did you flush the caches before/after each query - maybe the first affects the second - ...



Only top voted, non community-wiki answers of a minimum length are eligible