I'm a bit suss on ignoring them. The mem
in use from glance doesn't increase.
Might be a side effect of something else?
Dunno, it's got me stumped. Been happening
since we moved from 8.0.5.2 to 8.0.6.0.
Maybe I should just slap on the 8.0.6.2 patch?
Going back to 8.0.5 is no option, not
We do daily exports, but our largest
table is not that large. And they all
complete, no errors. Heaps of tables, though.
Also, this is 8.0.6. I'd expect the darn thing
to be fixed by now! Thanks for the info.
Cheers
Nuno Souto
[EMAIL PROTECTED]
http://www.users.bigpond.net.au/the_Den
-
In the alert log?
HP9K, HP-UX, Oracle 8.0.6.0.
I'm getting about 6 a day.
No apparent harm to the DB.
Metalink as usual says: can't reproduce
problem to most of these bugs.
Couldn't find a concrete fix to this anywhere.
Nope, I'm not using direct export.
TIA for any feedback.
Cheers
Nuno Souto
getting ORA-00600
[729] [space leak] on a
regular base?`
05/02/01 09
It is relating to incomplete/terminated export of database or any large
table. You may check this happening to your systemOracle patch 7.3.4.5
claims that it is fixed but it is still the problem...
Regards
Rafiq
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L
That error is in their knowledge and they can check in patchset note for
7.3.4.5 for fixes and they claim it is fixed but problem still exist
while terminating export while database goes down. We have this problem
with HP-10.20 and version 7.3.4.5
Regards
Rafiq
Reply-To: [EMAIL PROTECTED]
Space leaks = Oracle malloced memory and did not free it when done.
There is actually an init.ora event that can be set to ignore memory leaks so
you don't have to see them in your alert log.
10262, 0, Don't check for memory leaks
// *Cause:Setting this event to level one causes memory
