Certo mas aconteceu alguma coisa, o log nao iria pipocar sozinho... A conexao deve ter caído e voltado em seguida.. intervalo de tempo suficiente pra provocar algum erro
Olha, a mensagem da algumas outras dicas do que pode ter ocorrido => " O000" did not start after 120 secondsErrors" Você mesmo cuida do storage ou outra pessoa ? Sugiro olhar os logs por volta de 12:00 e 13:00 e claro, olhar o proprio log de eventos do servidor Windows Posso estar enganado, mas pra mim essa base parou na hora do almoço e por volta de 12:27 foi a hora fatidica.. até que teve intervenção manual para o banco voltar On 23 September 2016 at 15:05, 'Yahoo' alisson...@yahoo.com.br [oracle_br] < oracle_br@yahoogrupos.com.br> wrote: > > > Olá boa tarde! > > > > Ela tem um storage conectada a ela e é ASM, Stande Alone.. Tem backup sim. > > > > Na verdade o ASM estava ativo ... > > > > Fri Sep 23 12:27:02 2016 > > > > Errors in file > c:\app\administrator\diag\rdbms\bdeducar\bdeducar\trace\bdeducar_cjq0_6948.trc > (incident=684822): > > > > Olhei as conexões com o Storage tudo ok.. > > > > > > > > > > *De:* oracle_br@yahoogrupos.com.br [mailto:oracle_br@yahoogrupos.com.br] > *Enviada em:* sexta-feira, 23 de setembro de 2016 14:48 > *Para:* oracle_br@yahoogrupos.com.br > *Assunto:* Re: [oracle_br] Ajuda Erro ORA-00445: background process > "J000" did not start after 120 seconds > > > > > > Boa tarde > > > > Essa maquina está ligada a algum storage e usando ASM ? É RAC ou stand > alone ? Tem backup ? > > > > Parece que caiu a conexao com o ASM, por isso pipocando as mensagens de > erro.. > > > > ORA-15064: communication failure with ASM instance > > > > > > > > On 23 September 2016 at 14:14, alisson...@yahoo.com.br [oracle_br] < > oracle_br@yahoogrupos.com.br> wrote: > > > > boa tarde Senhores. > > > > Hoje comecei a receber erros (ORA-00445: background process "J000" did not > start after 120 seconds) e com isso o banco parou , tive que levanta-lo > novamente. > > > > Meu ambiente encontrasse em Windows server 2012 R2, temos 128G de > memorias. versão do Oracle Sendo a versão do oracle 11r . > > > > parallel_servers_target integer 224 > > memory_target big integer 78336M > > memory_max_target big integer 78336M > > > > > > RESOURCE_NAME CURRENT_UTILIZATION MAX_UTILIZATION > INITIAL_ALLOCATION LIMIT_VALUE > processes 388 453 3000 3000 > sessions 401 480 4536 4536 > enqueue_locks 532 590 52700 52700 > enqueue_resources 136 157 20176 UNLIMITED > ges_procs 0 0 0 0 > ges_ress 0 0 0 UNLIMITED > ges_locks 0 0 0 UNLIMITED > ges_cache_ress 0 0 0 UNLIMITED > ges_reg_msgs 0 0 0 UNLIMITED > ges_big_msgs 0 0 0 UNLIMITED > ges_rsv_msgs 0 0 0 0 > gcs_resources 0 0 0 0 > gcs_shadows 0 0 0 0 > dml_locks 3 3 19956 UNLIMITED > temporary_table_locks 0 0 UNLIMITED UNLIMITED > transactions 4 4 4989 UNLIMITED > branches 0 2 4989 UNLIMITED > cmtcallbk 0 1 4989 UNLIMITED > max_rollback_segments 24 24 4989 65535 > sort_segment_locks 92 103 UNLIMITED UNLIMITED > k2q_locks 0 0 9072 UNLIMITED > max_shared_servers 1 1 UNLIMITED UNLIMITED > parallel_max_servers 0 32 560 3600 > > > > > > > > Bom o erro começou aqui e no momento do erro não vi processamento e nem > memoria alta ... > > > > ORA-03113: end-of-file on communication channelORA-15064: communication > failure with ASM instanceErrors in file c:\app\administrator\diag\ > rdbms\bdeducar\bdeducar\trace\bdeducar_asmb_5144.trc:NOTE: ASMB > terminatingFri Sep 23 12:31:12 2016Incident details in: > c:\app\administrator\diag\rdbms\bdeducar\bdeducar\incident\incdir_684734\ > bdeducar_arc1_6372_i684734.trcORA-00240: control file enqueue held for > more than 120 secondsErrors in file c:\app\administrator\diag\ > rdbms\bdeducar\bdeducar\trace\bdeducar_arc1_6372.trc > (incident=684734):Fri Sep 23 12:31:11 2016Trace dumping is performing > id=[cdmp_20160923122908]Fri Sep 23 12:29:08 2016 Current log# 1 seq# > 184145 mem# 3: E:\BDEDUCAR\ONLINELOG\O1_MF_1_C54Q6NK8_.LOG Current log# > 1 seq# 184145 mem# 2: +DATA/bdeducar/onlinelog/group_1.355.896477093 > Current log# 1 seq# 184145 mem# 1: C:\APP\REDO\REDO01A.LOG Current log# 1 > seq# 184145 mem# 0: E:\REDO\REDO01A.LOGThread 1 advanced to log sequence > 184145 (LGWR switch)Incident details in: c:\app\administrator\diag\ > rdbms\bdeducar\bdeducar\incident\incdir_684623\bdeducar_lgwr_6700_i684623.trcORA-00445: > background process "O000" did not start after 120 secondsErrors in file > c:\app\administrator\diag\rdbms\bdeducar\bdeducar\trace\bdeducar_lgwr_6700.trc > (incident=684623):Fri Sep 23 12:29:07 2016Trace dumping is performing > id=[cdmp_20160923122759]Fri Sep 23 12:27:59 2016Incident details in: > c:\app\administrator\diag\rdbms\bdeducar\bdeducar\incident\incdir_684622\ > bdeducar_lgwr_6700_i684622.trcORA-00240: control file enqueue held for > more than 120 secondsErrors in file c:\app\administrator\diag\ > rdbms\bdeducar\bdeducar\trace\bdeducar_lgwr_6700.trc > (incident=684622):Fri Sep 23 12:27:58 2016Trace dumping is performing > id=[cdmp_20160923122703]Fri Sep 23 12:27:03 2016Errors in file > c:\app\administrator\diag\rdbms\bdeducar\bdeducar\trace\ > bdeducar_cjq0_6948.trc:kkjcre1p: unable to spawn jobq slave process > Incident details in: c:\app\administrator\diag\rdbms\bdeducar\bdeducar\ > incident\incdir_684822\bdeducar_cjq0_6948_i684822.trcORA-00445: > background process "J000" did not start after 120 secondsErrors in file > c:\app\administrator\diag\rdbms\bdeducar\bdeducar\trace\bdeducar_cjq0_6948.trc > (incident=684822):Fri Sep 22:23 17:02 2016 > > > > Alguem já passou por esse problema ? > > > > > > > > > > >