Ora error 471

Terminating the Instance Due to Error 471 Out-Of-Memory(OOM) Killer Crashes Oracle Database (Doc ID 1622379.1) Last updated on JANUARY 30, 2022 Applies to: Oracle Database Cloud Schema Service — Version N/A and laterOracle Database Exadata Express Cloud Service — Version N/A and laterOracle Database Exadata Cloud Machine — Version N/A and laterOracle Cloud Infrastructure […]

Содержание

  1. Terminating the Instance Due to Error 471 Out-Of-Memory(OOM) Killer Crashes Oracle Database (Doc ID 1622379.1)
  2. Applies to:
  3. Symptoms
  4. Changes
  5. Cause
  6. To view full details, sign in with your My Oracle Support account.
  7. Don’t have a My Oracle Support account? Click to get started!
  8. ORA-00600 [504] ORA-00600 [25010] Standby terminating the instance due to error 471 (Doc ID 2642984.1)
  9. Applies to:
  10. Symptoms
  11. Changes
  12. Cause
  13. To view full details, sign in with your My Oracle Support account.
  14. Don’t have a My Oracle Support account? Click to get started!
  15. Pmon Terminating Instance Due To Error 471
  16. terminating the instance due to error 471 Out-Of-Memory .
  17. PMON: terminating instance due to error 471. database down .
  18. PMON (ospid: 26463): terminating the instance due to error 471
  19. Terminating The Instance Due To Error 471 — Oracle
  20. Oracle crash; «Instance terminated by PMON» — Ex Libris .
  21. Pmon terminated instance due to LGWR termination ORA-470
  22. Terminating the instance due to error 474 tips
  23. PMON (ospid: 8143): terminating the instance due to error 472
  24. Instance terminated by PMON in Oracle — IT Tutorial
  25. PMON terminating the instance due to 56710 — DBRM died .
  26. Pmon Terminating Instance Due To Error 471 Fixes & Solutions
  27. Dbw0 Terminating Instance Due To Error 471
  28. terminating the instance due to error 471 Out-Of-Memory .
  29. PMON: terminating instance due to error 471. database down .
  30. 2858460 — Oracle shutdown randomly — NetWeaver SAP .
  31. crash — Oracle: Why is DBW terminating my Instance .
  32. OraFAQ Forum: Server Administration » ORA-00471: DBWR .
  33. ORA-600 [1433], [60] Error from FBDA/DBW0 Leading to .
  34. ORA-00600 [kjbwrdone:!op] And Instance Crash by DBWR
  35. Oracle crash; «Instance terminated by PMON» — Ex Libris .
  36. Dbw0 Terminating Instance Due To Error 471 Fixes & Solutions
  37. ORA-00600 [kcbbxsv_2] Errors And DBW0: Terminating Instance Due To Error 471 (Doc ID 1461704.1)
  38. Applies to:
  39. Symptoms
  40. Changes
  41. Cause
  42. To view full details, sign in with your My Oracle Support account.
  43. Don’t have a My Oracle Support account? Click to get started!

Terminating the Instance Due to Error 471 Out-Of-Memory(OOM) Killer Crashes Oracle Database (Doc ID 1622379.1)

Last updated on JANUARY 30, 2022

Applies to:

Oracle Database Cloud Schema Service — Version N/A and later
Oracle Database Exadata Express Cloud Service — Version N/A and later
Oracle Database Exadata Cloud Machine — Version N/A and later
Oracle Cloud Infrastructure — Database Service — Version N/A and later
Oracle Database Backup Service — Version N/A and later
Generic Linux

Symptoms

Instance terminated due to death of background process. In this case, it was DBWR.

No more information in alert / traces why DBWR process dead.

Tue Feb 04 13:00:03 2014
LNS: Standby redo logfile selected for thread 1 sequence 6206 for destination LOG_ARCHIVE_DEST_2
Archived Log entry 10547 added for thread 1 sequence 6205 ID 0x77e10623 dest 1:
Tue Feb 04 13:05:09 2014
LGWR waiting for instance termination
Tue Feb 04 13:05:15 2014
System state dump requested by (instance=1, osid=13406 (PMON)), summary=[abnormal instance termination].
System State dumped to trace file /opt/oracle/diag/rdbms/ / /trace/ _diag_13429.trc
Tue Feb 04 13:05:21 2014
PMON (ospid: 13406): terminating the instance due to error 471
Tue Feb 04 13:05:21 2014

Changes

Cause

To view full details, sign in with your My Oracle Support account.

Don’t have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Oracle offers a comprehensive and fully integrated stack of cloud applications and platform services. For more information about Oracle (NYSE:ORCL), visit oracle.com. пїЅ Oracle | Contact and Chat | Support | Communities | Connect with us | | | | Legal Notices | Terms of Use

Источник

ORA-00600 [504] ORA-00600 [25010] Standby terminating the instance due to error 471 (Doc ID 2642984.1)

Last updated on NOVEMBER 24, 2021

Applies to:

Symptoms

NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data
from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material.

Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure.

Database name: STBY_SID

Standby database was crashed with following errors in Alert.log:

Changes

On Primary database, empty Tablespace was dropped and recreated.

Cause

To view full details, sign in with your My Oracle Support account.

Don’t have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Oracle offers a comprehensive and fully integrated stack of cloud applications and platform services. For more information about Oracle (NYSE:ORCL), visit oracle.com. пїЅ Oracle | Contact and Chat | Support | Communities | Connect with us | | | | Legal Notices | Terms of Use

Источник

Pmon Terminating Instance Due To Error 471

We have collected for you the most relevant information on Pmon Terminating Instance Due To Error 471, as well as possible solutions to this problem. Take a look at the links provided and find the solution that works. Other people have encountered Pmon Terminating Instance Due To Error 471 before you, so use the ready-made solutions.

terminating the instance due to error 471 Out-Of-Memory .

    https://support.oracle.com/knowledge/Oracle%20Database%20Products/1622379_1.html
    Aug 04, 2018 · terminating the instance due to error 471 Out-Of-Memory(OOM) Killer Crashes Oracle Database terminating the instance due to error 471 Out-Of-Memory(OOM) Killer Crashes Oracle Database (Doc ID 1622379.1) Last updated on AUGUST 04, 2018

PMON: terminating instance due to error 471. database down .

    http://www.deskdr.com/dr/pmon-terminating-instance-due-to-error-471-database-down.html
    PMON: terminating instance due to error 472 Instance terminated by PMON, pid = 5581 This database had earlier on been affected by abrupt power shutdown. It was going on and off.

PMON (ospid: 26463): terminating the instance due to error 471

    https://blog.csdn.net/cuanjian2673/article/details/100430853
    PMON (ospid: 26463): terminating the instance due to error 471 д»Љж—©ж•°жЌ®еє“ж„Џе¤–е®•еє“пјЊз»Џ.

Terminating The Instance Due To Error 471 — Oracle

    https://support.oracle.com/knowledge/Oracle%20Database%20Products/2653221_1.html
    Oracle Database — Enterprise Edition — Version 11.2.0.4 and later: Terminating The Instance Due To Error 471

Oracle crash; «Instance terminated by PMON» — Ex Libris .

    https://knowledge.exlibrisgroup.com/Aleph/Knowledge_Articles/Oracle_crash%3B_%22Instance_terminated_by_PMON%22
    1. «DBWR process terminated with error» 2. «Instance terminated by PMON» Cause: 1. swap does not address Oracle requirements — it should be equal to the size of the RAM (in case RAM is between 2 and 16 GB). 2. kernel.shmmax is set to 2147483648 which is too small. Oracle requirements say: Minimum of the following values:

Pmon terminated instance due to LGWR termination ORA-470

    https://support.oracle.com/knowledge/Oracle%20Database%20Products/431246_1.html
    Mar 21, 2019 · Pmon terminated instance due to LGWR termination ORA-470 (Doc ID 431246.1) Last updated on MARCH 21, 2019. Applies to: Oracle Database — Enterprise Edition — Version 9.2.0.1 to 10.2.0.3 [Release 9.2 to 10.2] Oracle Database Cloud Schema Service — Version N/A and later Oracle Database Exadata Cloud Machine — Version N/A and later

Terminating the instance due to error 474 tips

    http://www.dba-oracle.com/t_terminating_the_instance_due_to_error_474.htm
    Instance terminated by PMON, pid = nnnn ORA-474 : opidrv aborting process S000 ospid (nnnn_nnnn) For a related issue, see MOSC for bug: 8310931 which is fixed in 11.2.

PMON (ospid: 8143): terminating the instance due to error 472

    https://kudaykir.blogspot.com/2014/08/pmon-ospid-8143-terminating-instance.html
    Aug 18, 2014 · Resuming block recovery (PMON) for file 4 block 180627 Block recovery from logseq 125, block 70 to scn 10132192035480 Recovery of Online Redo …

Instance terminated by PMON in Oracle — IT Tutorial

    https://ittutorial.org/instance-terminated-by-pmon-oracle/
    Apr 16, 2019 · I am Founder of SysDBASoft IT and IT Tutorial and Certified Expert about Oracle & SQL Server database, Goldengate, Exadata Machine, Oracle Database Appliance administrator with 10+years experience.I have OCA, OCP, OCE RAC Expert Certificates I have worked 100+ Banking, Insurance, Finance, Telco and etc. clients as a Consultant, Insource or Outsource.I have done 200+ Operations …

PMON terminating the instance due to 56710 — DBRM died .

    https://support.oracle.com/knowledge/Oracle%20Database%20Products/2554632_1.html
    PMON terminating the instance due to 56710 — DBRM died unexpectedly (Doc ID 2554632.1) Last updated on JANUARY 30, 2020. Applies to: Oracle Database — Enterprise Edition — Version 12.1.0.2 and later Information in this document applies to any platform. Symptoms. Instance Critical Process (pid: 7, ospid: 299752, DBRM) died unexpectedly

Pmon Terminating Instance Due To Error 471 Fixes & Solutions

We are confident that the above descriptions of Pmon Terminating Instance Due To Error 471 and how to fix it will be useful to you. If you have another solution to Pmon Terminating Instance Due To Error 471 or some notes on the existing ways to solve it, then please drop us an email.

Источник

Dbw0 Terminating Instance Due To Error 471

We have collected for you the most relevant information on Dbw0 Terminating Instance Due To Error 471, as well as possible solutions to this problem. Take a look at the links provided and find the solution that works. Other people have encountered Dbw0 Terminating Instance Due To Error 471 before you, so use the ready-made solutions.

terminating the instance due to error 471 Out-Of-Memory .

    https://support.oracle.com/knowledge/Oracle%20Database%20Products/1622379_1.html
    Aug 04, 2018 · terminating the instance due to error 471 Out-Of-Memory(OOM) Killer Crashes Oracle Database (Doc ID 1622379.1) Last updated on AUGUST 04, 2018. Applies to: Oracle Database — Enterprise Edition — Version 11.2.0.3 and later Oracle Database — Standard Edition — Version 12.1.0.1 to 12.1.0.1 [Release 12.1]

PMON: terminating instance due to error 471. database down .

    http://www.deskdr.com/dr/pmon-terminating-instance-due-to-error-471-database-down.html
    Similar Messages. PMON: terminating instance due to error 28. Hi , OS : AIX 5.3 Oracle : 10.2.0.4 Problem : Database instance crashed . Alert log shows :

2858460 — Oracle shutdown randomly — NetWeaver SAP .

    https://apps.support.sap.com/sap/support/knowledge/en/2858460
    Sat Jun 15 21:57:15 2019. Instance Critical Process (pid: 7, ospid: 2158, DBW0) died unexpectedly. PMON (ospid: 2136): terminating the instance due to error 471. Sat Jun 15 21:57:25 2019. System state dump requested by (instance=1, osid=2136 (PMON)), summary= [abnormal instance termination].

crash — Oracle: Why is DBW terminating my Instance .

    https://dba.stackexchange.com/questions/135082/oracle-why-is-dbw-terminating-my-instance
    00472, 00000, «PMON process terminated with error» // *Cause: The process cleanup process died // *Action: Warm start instance PMON died, so DBWR terminated the instance. If any process dies from SMON, PMON, LGWR, DBWR, CKPT, the remaining processes will terminate the instance.

OraFAQ Forum: Server Administration » ORA-00471: DBWR .

    http://www.orafaq.com/forum/t/95071/
    DBW0: terminating instance due to error 471 Fri Jan 04 03:37:36 2008 Errors in file d:oracleadminsamidbbdumpsamidb_lgwr_1632.trc: ORA-00471: DBWR process terminated with error Fri Jan 04 03:37:36 2008 Errors in file d:oracleadminsamidbbdumpsamidb_pmon_632.trc: ORA-00471: DBWR process terminated with error Fri Jan 04 03:37:37 2008

ORA-600 [1433], [60] Error from FBDA/DBW0 Leading to .

    https://support.oracle.com/knowledge/Oracle%20Database%20Products/1105654_1.html
    This can occur in FBDA and/or DBW0 process followed by DBW0 crashing the instance with: DBW0 (ospid: ): terminating the instance due to error 471 ORA-00471: DBWR process terminated …

ORA-00600 [kjbwrdone:!op] And Instance Crash by DBWR

    https://support.oracle.com/knowledge/Oracle%20Database%20Products/2286167_1.html
    ORA-00600 [kjbwrdone:!op] And Instance Crash by DBWR (Doc ID 2286167.1) Last updated on FEBRUARY 19, 2019. Applies to: Oracle Database — Enterprise Edition — Version 11.2.0.2 to …

Oracle crash; «Instance terminated by PMON» — Ex Libris .

    https://knowledge.exlibrisgroup.com/Aleph/Knowledge_Articles/Oracle_crash%3B_%22Instance_terminated_by_PMON%22
    1. «DBWR process terminated with error» 2. «Instance terminated by PMON» Cause: 1. swap does not address Oracle requirements — it should be equal to the size of the RAM (in case RAM is between 2 and 16 GB). 2. kernel.shmmax is set to 2147483648 which is too small. Oracle requirements say: Minimum of the following values:

Dbw0 Terminating Instance Due To Error 471 Fixes & Solutions

We are confident that the above descriptions of Dbw0 Terminating Instance Due To Error 471 and how to fix it will be useful to you. If you have another solution to Dbw0 Terminating Instance Due To Error 471 or some notes on the existing ways to solve it, then please drop us an email.

Источник

ORA-00600 [kcbbxsv_2] Errors And DBW0: Terminating Instance Due To Error 471 (Doc ID 1461704.1)

Last updated on JANUARY 30, 2022

Applies to:

Oracle Database — Enterprise Edition — Version 10.2.0.4 and later
Oracle Database Cloud Schema Service — Version N/A and later
Oracle Database Exadata Express Cloud Service — Version N/A and later
Oracle Database Exadata Cloud Machine — Version N/A and later
Oracle Cloud Infrastructure — Database Service — Version N/A and later
Information in this document applies to any platform.

Symptoms

1.В The following error is being reported in the alert.log:

ORA-00600: internal error code, arguments: [kcbbxsv_2], [], [], [], [], [], [], []
DBW0: terminating instance due to error 471

2.В The call stack will resemble the following:

Changes

Cause

To view full details, sign in with your My Oracle Support account.

Don’t have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Oracle offers a comprehensive and fully integrated stack of cloud applications and platform services. For more information about Oracle (NYSE:ORCL), visit oracle.com. пїЅ Oracle | Contact and Chat | Support | Communities | Connect with us | | | | Legal Notices | Terms of Use

Источник

Источник

При попытке обновить данные в таблице через dbForge Studio остановилась база, теперь при запуске выдает:

Код:

ORA-00471: DBWR process terminated with error

База в архивлоге. Как его победить?
в алерте

Код:

Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
  processes                = 400
  sessions                 = 445
  timed_statistics         = TRUE
  sga_max_size             = 5368709120
  __shared_pool_size       = 1073741824
  shared_pool_size         = 1073741824
  __large_pool_size        = 1073741824
  large_pool_size          = 1073741824
  __java_pool_size         = 1073741824
  java_pool_size           = 1073741824
  trace_enabled            = FALSE
  control_files            = D:ORACLEORADATAKAMAVTOCONTROL01.CTL, D:ORACLEORADATAKAMAVTOCONTROL02.CTL, D:ORACLEORADATAKAMAVTOCONTROL03.CTL
  db_block_size            = 8192
  __db_cache_size          = 1073741824
  db_cache_size            = 1073741824
  db_recycle_cache_size    = 67108864
  db_cache_advice          = OFF
  compatible               = 10.2.0.3.0
  log_archive_start        = TRUE
  db_recovery_file_dest    = E:backup_log
  db_recovery_file_dest_size= 966367641600
  fast_start_mttr_target   = 600
  transactions_per_rollback_segment= 1
  undo_management          = AUTO
  undo_tablespace          = UNDOTBS1
  undo_retention           = 10800
  recyclebin               = off
  O7_DICTIONARY_ACCESSIBILITY= TRUE
  remote_login_passwordfile= EXCLUSIVE
  audit_sys_operations     = FALSE
  db_domain                = 
  instance_name            = KAMAVTO
  job_queue_processes      = 10
  background_dump_dest     = D:ORACLEADMINKAMAVTOBDUMP
  user_dump_dest           = D:ORACLEADMINKAMAVTOUDUMP
  max_dump_file_size       = 5000000
  core_dump_dest           = D:ORACLEADMINKAMAVTOCDUMP
  commit_write             = batch,nowait
  optimizer_features_enable= 10.2.0.4
  audit_trail              = XML
  sort_area_size           = 4194304
  db_name                  = KAMAVTO
  open_cursors             = 300
  star_transformation_enabled= FALSE
  query_rewrite_enabled    = FALSE
  query_rewrite_integrity  = stale_tolerated
  pga_aggregate_target     = 1048576000
  optimizer_dynamic_sampling= 2
Deprecated system parameters with specified values:
  log_archive_start        
End of deprecated system parameter listing
PMON started with pid=2, OS id=5508
PSP0 started with pid=4, OS id=3368
MMAN started with pid=6, OS id=5520
DBW0 started with pid=8, OS id=4952
DBW1 started with pid=10, OS id=3176
LGWR started with pid=12, OS id=3604
CKPT started with pid=14, OS id=5676
SMON started with pid=16, OS id=5688
RECO started with pid=18, OS id=5416
CJQ0 started with pid=20, OS id=2616
MMON started with pid=22, OS id=3732
MMNL started with pid=24, OS id=6112
Tue Oct 09 18:48:02 2018
alter database mount exclusive
Tue Oct 09 18:48:06 2018
Setting recovery target incarnation to 1
Tue Oct 09 18:48:06 2018
Successful mount of redo thread 1, with mount id 377811490
Tue Oct 09 18:48:06 2018
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Tue Oct 09 18:48:06 2018
alter database open
Tue Oct 09 18:48:06 2018
Beginning crash recovery of 1 threads
 parallel recovery started with 15 processes
Tue Oct 09 18:48:06 2018
Started redo scan
Tue Oct 09 18:48:07 2018
Completed redo scan
 54948 redo blocks read, 4095 data blocks need recovery
Tue Oct 09 18:48:08 2018
Started redo application at
 Thread 1: logseq 324781, block 92874
Tue Oct 09 18:48:08 2018
Recovery of Online Redo Log: Thread 1 Group 1 Seq 324781 Reading mem 0
  Mem# 0: D:ORACLEORADATAKAMAVTOREDO01.LOG
Tue Oct 09 18:48:08 2018
Recovery of Online Redo Log: Thread 1 Group 2 Seq 324782 Reading mem 0
  Mem# 0: D:ORACLEORADATAKAMAVTOREDO02.LOG
Tue Oct 09 18:48:08 2018
Completed redo application
Tue Oct 09 18:48:08 2018
Hex dump of (file 9, block 59382) in trace file d:oracleadminkamavtobdumpkamavto_dbw0_4952.trc
Corrupt block relative dba: 0x0240e7f6 (file 9, block 59382)
Bad header found during preparing block for write
Data in bad block:
 type: 6 format: 2 rdba: 0x0240e7f6
 last change scn: 0x0001.0eb628d8 seq: 0x2 flg: 0x28
 spare1: 0x0 spare2: 0x0 spare3: 0x540e
 consistency value in tail: 0x28d80602
 check value in block header: 0x0
 block checksum disabled
Tue Oct 09 18:48:09 2018
Errors in file d:oracleadminkamavtobdumpkamavto_dbw0_4952.trc:
ORA-00600: internal error code, arguments: [kcbzpbuf_1], [4], [1], [], [], [], [], []

Tue Oct 09 18:48:09 2018
Errors in file d:oracleadminkamavtobdumpkamavto_dbw0_4952.trc:
ORA-00600: internal error code, arguments: [kcbzpbuf_1], [4], [1], [], [], [], [], []

DBW0: terminating instance due to error 471
Tue Oct 09 18:48:09 2018
Errors in file d:oracleadminkamavtobdumpkamavto_p014_4676.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:09 2018
Errors in file d:oracleadminkamavtobdumpkamavto_p013_980.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:09 2018
Errors in file d:oracleadminkamavtobdumpkamavto_p012_584.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:09 2018
Errors in file d:oracleadminkamavtobdumpkamavto_p011_5700.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:10 2018
Errors in file d:oracleadminkamavtobdumpkamavto_p010_6044.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:10 2018
Errors in file d:oracleadminkamavtobdumpkamavto_p009_4592.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:10 2018
Errors in file d:oracleadminkamavtobdumpkamavto_p008_2152.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:10 2018
Errors in file d:oracleadminkamavtobdumpkamavto_p007_4488.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:10 2018
Errors in file d:oracleadminkamavtobdumpkamavto_p002_3936.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:10 2018
Errors in file d:oracleadminkamavtobdumpkamavto_p000_5588.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:10 2018
Errors in file d:oracleadminkamavtobdumpkamavto_p001_3408.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:11 2018
Errors in file d:oracleadminkamavtobdumpkamavto_pmon_5508.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:11 2018
Errors in file d:oracleadminkamavtobdumpkamavto_p004_4588.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:11 2018
Errors in file d:oracleadminkamavtobdumpkamavto_psp0_3368.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:11 2018
Errors in file d:oracleadminkamavtobdumpkamavto_mman_5520.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:11 2018
Errors in file d:oracleadminkamavtobdumpkamavto_ckpt_5676.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:11 2018
Errors in file d:oracleadminkamavtobdumpkamavto_dbw1_3176.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:11 2018
Errors in file d:oracleadminkamavtobdumpkamavto_lgwr_3604.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:12 2018
Errors in file d:oracleadminkamavtobdumpkamavto_p003_5956.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:13 2018
Errors in file d:oracleadminkamavtobdumpkamavto_p005_5872.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:14 2018
Errors in file d:oracleadminkamavtobdumpkamavto_p006_5272.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:14 2018
Errors in file d:oracleadminkamavtobdumpkamavto_reco_5416.trc:
ORA-00471: DBWR process terminated with error

Tue Oct 09 18:48:14 2018
Errors in file d:oracleadminkamavtobdumpkamavto_smon_5688.trc:
ORA-00471: DBWR process terminated with error

сейчас статус

Код:

INSTANCE_NAME    STATUS
---------------- ------------
kamavto          MOUNTED

при попытке startup open;

Код:

SQL> startup open;
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.

Total System Global Area 5368709120 bytes
Fixed Size                  2171616 bytes
Variable Size            4221361440 bytes
Database Buffers         1140850688 bytes
Redo Buffers                4325376 bytes
Database mounted.
ORA-03113: end-of-file on communication channel

судя по всему не смог записать

Код:

Hex dump of (file 9, block 59382) in trace file d:oracleadminkamavtobdumpkamavto_dbw1_4188.trc
Corrupt block relative dba: 0x0240e7f6 (file 9, block 59382)
Bad header found during preparing block for write
Data in bad block:
 type: 6 format: 2 rdba: 0x0240e7f6
 last change scn: 0x0001.0eb628d8 seq: 0x2 flg: 0x28
 spare1: 0x0 spare2: 0x0 spare3: 0x540e
 consistency value in tail: 0x28d80602
 check value in block header: 0x0
 block checksum disabled

Источник

April 11, 2020

Hi,

Sometimes you can get ” ORA-00471: DBWR process terminated with error ” error.

Details of error are as follows.

ORA-00471: DBWR process terminated with error

Cause: The database writer process died

Action: Warm start instance

To solve the problem, please execute the following steps:

Reduce the database db_files parameter to reduce file descriptors usage (requires a database restart)

OR

Increase the number of file descriptors value specific to your UNIX kernel ( File descriptor limit is per process.)

 set kernel.shmmax to 4G

The latest solution is startup or restart instance again.

Do you want to learn Oracle Database for Beginners, then read the following articles.

https://ittutorial.org/oracle-database-19c-tutorials-for-beginners/

 1,684 views last month,  1 views today

About Mehmet Salih Deveci

I am Founder of SysDBASoft IT and IT Tutorial and Certified Expert about Oracle & SQL Server database, Goldengate, Exadata Machine, Oracle Database Appliance administrator with 10+years experience.I have OCA, OCP, OCE RAC Expert Certificates I have worked 100+ Banking, Insurance, Finance, Telco and etc. clients as a Consultant, Insource or Outsource.I have done 200+ Operations in this clients such as Exadata Installation & PoC & Migration & Upgrade, Oracle & SQL Server Database Upgrade, Oracle RAC Installation, SQL Server AlwaysOn Installation, Database Migration, Disaster Recovery, Backup Restore, Performance Tuning, Periodic Healthchecks.I have done 2000+ Table replication with Goldengate or SQL Server Replication tool for DWH Databases in many clients.If you need Oracle DBA, SQL Server DBA, APPS DBA,  Exadata, Goldengate, EBS Consultancy and Training you can send my email adress [email protected].-                                                                                                                                                                                                                                                 -Oracle DBA, SQL Server DBA, APPS DBA,  Exadata, Goldengate, EBS ve linux Danışmanlık ve Eğitim için  [email protected] a mail atabilirsiniz.

Источник

Our site suffered the crash of an Avaloq test database. The following information was found in the alert log:

PMON (ospid: 1112): terminating the instance due to error 471
TIMESTAMP
System state dump requested by (instance=1, osid=1112 (PMON)), summary=[abnormal instance termination].
System State dumped to trace file /u00/oracle/orabase/diag/rdbms/XXX/trace/XXX_diag_1221_20151231063902.trc
Dumping diagnostic data in directory=[cdmp_20151231063902], requested by (instance=1, osid=1112 (PMON)), summary=[abnormal instance termination].
Instance terminated by PMON, pid = 1112

I looked into the pmon trace XXX_pmon_1112.trc and found out that the PMON terminated the instance because the database writer process DBW2 was not running any more:

Background process DBW2 found dead
Oracle pid = 12
OS pid (from detached process) = 1234
OS pid (from process state) = 1234

Note here the OS pid of the DBW process – 1234. This is an important clue for later.

There weren’t any trace files left by the process 1234, so I assumed that the sudden death was due to some external impact. To find out the cause I used the kill.d dtrace script by Gregg Brendan. The culprit was indeed revealed next day when I harvested the kill.d results :

...
26804   aaafile.sh     9 1234   -1
27913   aaafile.sh     9 1234   -1
28988   aaafile.sh     9 1234   -1
28509   aaafile.sh     9 1234   -1
27393   aaafile.sh     9 1234   -1
29964   aaafile.sh     9 1234   -1
...

The avaloq program aaafile.sh was killing the 1234 process. In this case, the victim happened to be a database writer.

But why would Avaloq do this?

To answer this question I correlated the information in alert log with the Avaloq aaafile log files.

Thu Jan 07 15:19:58 2016
ALTER SYSTEM enable restricted session;
Immediate Kill Session#: 811, Serial#: 3
Immediate Kill Session: sess: 316711c00  OS pid: 12280
Immediate Kill Session#: 1084, Serial#: 77
Immediate Kill Session: sess: 314742c68  OS pid: 11927
Immediate Kill Session#: 1142, Serial#: 1179
Immediate Kill Session: sess: 3167a1f68  OS pid: 12020
Thu Jan 07 15:20:01 2016
opiodr aborting process unknown ospid (12068) as a result of ORA-28
Thu Jan 07 15:20:22 2016
opidrv aborting process J099 ospid (28486) as a result of ORA-28
Thu Jan 07 15:23:30 2016
Completed checkpoint up to RBA [0xd.2.10], SCN: 85281115086

aaafile log:
svavr02a:2016-01-07_15-20:"":INFO: PARAMS: CMD = kill, FILE = 1234
...
svavr02a:2016-01-07_15-20:"":INFO: Processing Command: kill process (1234)
kill: 1234: no such process
...
svavr02a:2016-01-07_15-20:"":INFO: PARAMS: CMD = kill, FILE = 12112
...
svavr02a:2016-01-07_15-20:"":INFO: Processing Command: kill process (12112)
...
svavr02a:2016-01-07_15-20:"":INFO: PARAMS: CMD = kill, FILE = 1234
...
svavr02a:2016-01-07_15-20:"":INFO: Processing Command: kill process (1234)
kill: 1234: no such process
...
svavr02a:2016-01-07_15-20:"":INFO: PARAMS: CMD = kill, FILE = 28486
...
svavr02a:2016-01-07_15-20:"":INFO: Processing Command: kill process (28486)

From the information above the following can be deduced:
– the session and os kills were caused by setting the session level 0 (session level 0 is the application shutdown in Avaloq)
– every database session kill was followed by the kill -9 of the corresponding shadow process
– there were a lot of kill -9 1234 for no obvious reason

To find out where the kill -9 1234 was coming from, I traced the session which sets the session level to zero and found the following query on the v$process view:

      SELECT P.SPID
            ,S.PROCESS
            ,S.MACHINE
            ,S.PROGRAM
      FROM   V$SESSION  S
            ,V$PROCESS  P
      WHERE  S.SID      = :b0
        AND  S.SERIAL#  = :b1
        AND  P.ADDR (+) = S.PADDR;

This query was executed after almost every alter system disconnect session immediate.

Therefore, I concluded that Avaloq is quering the v$process.spid to find out the OS PID. However, as kill oracle session and kill -9 ar not atomic operations it can happen that the shadow process already disappears when by the time the query gets executed returning NULL for SPID.

Since Avaloq selects v$session.process in the same query I assumed that this value is used as a fallback if SPID is NULL. In the Oracle Documentation the column process is described as: “Operating system client process ID”. However, when I selected process from v$session I was suprised to see that for all the JDBC processes the value was set to 1234. The Metalink note “How to Set V$SESSION Properties Using the JDBC Thin Driver (Doc ID 147413.1)” explains that this is the expected behaviour. Hence, Avaloq will kill any process with this PID, if there are JDBC sessions coming from the database server itself. Avaloq doesn’t try to kill all the sessions, but just the ones from the users which are registered in the table SEC_USER. In our case it was the messaging agent which was logged in as user I. In particular, below is the query found in the trace files which selects the sessions for killing:

SELECT SID     SID
,SERIAL# SERIAL
FROM   GV$SESSION
WHERE  AUDSID   > 0
AND  AUDSID  != USERENV('sessionid')
AND  TYPE     = 'USER'
AND ',' || :b0 || ',' NOT LIKE '%,' || USERNAME || ',%'
AND  USERNAME IN (
SELECT ORACLE_USER
FROM   SEC_USER
WHERE  ORACLE_USER NOT IN ('SYS', 'K', 'K_READ')
)
AND  NVL(CLIENT_INFO,' ') NOT LIKE 'BGP_OS.%'
AND  PROGRAM  NOT LIKE 'amqzlaa%';

As a workaround, make sure that you close the JDBC connections of the users in K.SEC_USER – except for K, K_READ and SYS – coming from the database server prior to setting session level to zero.

Update 02/02/2016: Avaloq released the patch #1695233 in the release 3.9.1.5.0. The patch recreates the procedure k.kill_session. The patch is successfully tested in my envoironment.

Источник

Понравилась статья? Поделить с друзьями:

Читайте также:

  • Ora 600 internal error
  • Ora 01438 ошибка
  • Oracle insufficient privileges ошибка
  • Ora 39083 object type user failed to create with error
  • Ora 01427 ошибка

    • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии