Skip to Main Content

Database Software

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!

errors during incremental rman backups

Dan AApr 25 2014 — edited Apr 30 2014

Hello Gurus.

My rman incremental is set off this way:

BACKUP INCREMENTAL LEVEL 1 DATABASE PLUS ARCHIVELOG;

It completes in half an hour. However, the box seems very slow (waits, cpu and swap are normal however) and connecting to the db takes 1 minute or more.

The alert log is throwing out the following:

ORA-00445: background process "J000" did not start after 120 seconds

and

kkjcre1p: unable to spawn jobq slave process

and

ORA-00445: background process "m001" did not start after 120 seconds

The trace files themselves include:

*** 2014-04-24 22:00:00.064
*** SESSION ID:(156.11) 2014-04-24 22:00:00.064
*** CLIENT ID:() 2014-04-24 22:00:00.064
*** SERVICE NAME:(SYS$BACKGROUND) 2014-04-24 22:00:00.064
*** MODULE NAME:() 2014-04-24 22:00:00.064
*** ACTION NAME:() 2014-04-24 22:00:00.064

Setting Resource Manager plan SCHEDULER[0x64EC0]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Closing scheduler window

*** 2014-04-25 02:00:00.032
Closing Resource Manager plan via scheduler window
Clearing Resource Manager plan via parameter
Waited for process J000 to initialize for 60 seconds

*** 2014-04-25 13:32:55.271

*** 2014-04-25 13:33:12.814
Process diagnostic dump for J000, OS id=24438
-------------------------------------------------------------------------------
os thread scheduling delay history: (sampling every 1.000000 secs)
  0.000000 secs at [ 13:33:12 ]
    NOTE: scheduling delay has not been sampled for 0.179745 secs  0.000000 secs from [ 13:33:08 - 13:33:13 ], 5 sec avg
  0.000000 secs from [ 13:32:13 - 13:33:13 ], 1 min avg
  0.000000 secs from [ 13:28:13 - 13:33:13 ], 5 min avg

*** 2014-04-25 13:33:27.859
loadavg : 2.20 1.35 1.33

*** 2014-04-25 13:33:30.355
Memory (Avail / Total) = 132.80M / 24096.92M
Swap (Avail / Total) = 0.00M /  0.00M
skgpgcmdout: read() for cmd /bin/ps -elf | /bin/egrep 'PID | 24438' | /bin/grep -v grep timed out after 15.000 seconds
Stack:
skgpgpstack: failed to access /usr/bin/gdb with errno=2

At this stage I am only testing. But if this happened in LIVE then the performance drag woulc be unacceptable.

I will raise an SR if this isnt something others have seen.

Thanks.

11.2.0.3

Linux RHEL 5.5

DA

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on May 28 2014
Added on Apr 25 2014
8 comments
4,732 views