core dump in /var/core owned by Oracle
Hi all,
We have database 10.2.0.4.0 on Solaris 10. One fine day, we see that /var is 100% and there are around 22 core files (name as below) sizing around 300-400MB each cause of it. Though the files are owned by root, they have oracle's name stamp. Looked at the alert log and database is behaving normal. Log switching info were in the alert logfile few minutes prior to this core dump and around an hour after core dump. Database or listener did not go down.
What I understand of core is: because of "some" platform inconsistencies, system could dump its memory footprint to /var/core. But, in this case, why Oracle name? What does Oracle has to do with this core? If Oracle was involved, there could have some entries in its alert or any other bdump/udump log. Is there any tool available to peek into core, if that could give any hints.
We have database 10.2.0.4.0 on Solaris 10. One fine day, we see that /var is 100% and there are around 22 core files (name as below) sizing around 300-400MB each cause of it. Though the files are owned by root, they have oracle's name stamp. Looked at the alert log and database is behaving normal. Log switching info were in the alert logfile few minutes prior to this core dump and around an hour after core dump. Database or listener did not go down.
What I understand of core is: because of "some" platform inconsistencies, system could dump its memory footprint to /var/core. But, in this case, why Oracle name? What does Oracle has to do with this core? If Oracle was involved, there could have some entries in its alert or any other bdump/udump log. Is there any tool available to peek into core, if that could give any hints.
0