Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Database Crashing Due To Memory Issues

User_YQF7SFeb 2 2018 — edited Feb 3 2018

Hello everyone!!  We are having major problems with one of our production database that we recently migrated from 10.2.0.2 on a Suse box to Oracle 12.1.0.2 on a CentOS server.  Since the migration, our database crashes daily.  The current CentOS server is a VM, with 4G of memory.  This is a very lightly used database.  The server chugs along fine, and then after 12 hours or so, we start to see these errors in the alert log:

Thu Feb 01 04:51:18 2018

Process m001 died, see its trace file

Process m000 died, see its trace file

Process m001 died, see its trace file

Thu Feb 01 05:03:47 2018

Process J004 died, see its trace file

Thu Feb 01 05:03:47 2018

kkjcre1p: unable to spawn jobq slave process

The database eventually crashes.  Here are some of our database parameters:

memory_max_target                    big integer 3008M

memory_target                        big integer 3008M

parallel_servers_target              integer     10

pga_aggregate_target                 big integer 30M

sga_target                           big integer 0

java_pool_size                       big integer 0

large_pool_size                      big integer 0

olap_page_pool_size                  big integer 0

shared_pool_reserved_size            big integer 32715571

shared_pool_size                     big integer 0

streams_pool_size                    big integer 608M

Do you think we should get away from AMM, and set the pga and sga manually?  Any help would be greatly appreciated.  Thanks so much.

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Mar 3 2018
Added on Feb 2 2018
18 comments
2,162 views