Psp0 Terminating The Instance Due To Error 472
Contents |
Sign in Expand/collapse global hierarchy Home
Ora-472
Aleph Knowledge Articles Expand/collapse global location Instance terminated terminating the instance due to error 472 oracle by PSP0 due to error 472 Last updated 23:06, 8 Dec 2015 Save user ospid terminating the instance due to error 472 as PDF Share Share Share Tweet Share No headers Article Type: General Product: Aleph Product Version: 20 Problem Symptoms:In the Oracle alert log there is the error message:PSP0
Reco : Terminating The Instance Due To Error 472
(ospid: 14734): terminating the instance due to error 472Cause:Part of the DB could be invalid (specifically XDB).Resolution:Contact Ex Libris support Category: ALEPHADM (500) Article last edited: 10/8/2013 Back to top Installing third-party products as part of service pack Institution Symbol length Was this article helpful?YesNo Recommended articles There are no recommended articles. Article type topic Content Type Knowledge_Article Language english Product aleph Tags 20 ALEPHADM (500) contype:kba Prod:Aleph Type:General © Copyright 2016 Ex Libris Knowledge Center Powered by MindTouch
to friend DB is Down!! ORA-00472: PMON process terminated with error [message #397559] Sun, 12 April 2009 12:00 nfernandes Messages: 19Registered: April 2009 Junior Member ora-00472 Hello, We are using Oracle 10G (10.2.0.2.0) and after creating a oracle error 472 materialized view (with aprox 32 GB in the TEMP Tablespace) we are getting the error ORA-00472: PMON
Arc0: Terminating Instance Due To Error 472
process terminated with error, and we cannot make any transaction on the database. We can startup the database, however after aprox 51 sec the database shutdowns itself. The https://knowledge.exlibrisgroup.com/Aleph/Knowledge_Articles/Instance_terminated_by_PSP0_due_to_error_472 alert log shows the following: Starting ORACLE instance (normal) LICENSE_MAX_SESSION = 0 LICENSE_SESSIONS_WARNING = 0 Picked latch-free SCN scheme 2 Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST Autotune of undo retention is turned on. IMODE=BR ILAT =18 LICENSE_MAX_USERS = 0 SYS auditing is disabled ksdpec: called for event 13740 prior to event group initialization Starting up ORACLE http://www.orafaq.com/forum/t/143528/ RDBMS Version: 10.2.0.2.0. System parameters with non-default values: processes = 150 __shared_pool_size = 150994944 __large_pool_size = 4194304 __java_pool_size = 12582912 __streams_pool_size = 4194304 sga_target = 775946240 control_files = C:\PROGRAMAS\ORACLE\PRODUCT\10.2.0\ORADATA\BIEPME\CONTROL01.CTL, C:\PROGRAMAS\ORACLE\PRODUCT\10.2.0\ORADATA\BIEPME\CONTROL02.CTL, C:\PROGRAMAS\ORACLE\PRODUCT\10.2.0\ORADATA\BIEPME\CONTROL03.CTL db_block_size = 8192 __db_cache_size = 595591168 compatible = 10.2.0.2.0 db_file_multiblock_read_count= 16 db_recovery_file_dest = c:\Programas\oracle\product\10.2.0\flash_recovery_area db_recovery_file_dest_size= 2147483648 undo_management = AUTO undo_tablespace = UNDOTBS1 remote_login_passwordfile= EXCLUSIVE db_domain = dispatchers = (PROTOCOL=TCP) (SERVICE=BIEPMEXDB) job_queue_processes = 10 audit_file_dest = C:\PROGRAMAS\ORACLE\PRODUCT\10.2.0\ADMIN\BIEPME\ADUMP background_dump_dest = C:\PROGRAMAS\ORACLE\PRODUCT\10.2.0\ADMIN\BIEPME\BDUMP user_dump_dest = C:\PROGRAMAS\ORACLE\PRODUCT\10.2.0\ADMIN\BIEPME\UDUMP core_dump_dest = C:\PROGRAMAS\ORACLE\PRODUCT\10.2.0\ADMIN\BIEPME\CDUMP db_name = BIEPME open_cursors = 300 pga_aggregate_target = 256901120 PMON started with pid=2, OS id=4668 PSP0 started with pid=3, OS id=4952 MMAN started with pid=4, OS id=4080 DBW0 started with pid=5, OS id=4956 LGWR started with pid=6, OS id=2964 CKPT started with pid=7, OS id=4972 SMON started with pid=8, OS id=4228 RECO started with pid=9, OS id=4692 CJQ0 started with pid=10, OS id=3356 MMON started with pid=11, OS id=3828 MMNL started with pid=12, OS id=3728 Thu Apr 09 20:17:37 2009 starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... starting up 1 shared ser
Links Monday, 25 February 2013 terminating instance due to error 472/ORA-00472 Cause: When user killed pmon process http://abduulwasiq.blogspot.com/2013/02/terminating-instance-due-to-error.html using kill -9
and receive notifications of new posts by email. Join 4,587 other followers Follow Pavan DBA's Blog on WordPress.com Visitor Count hit counter Categories Admin (49) Enterprise Manager (4) Bkp n Recovery (15) cloning (4) Certification (3) Dataguard (6) export/import/Datapump (11) Freshers (1) General (22) Installation (5) Interview Questions (1) RMAN, backup n recovery (1) Jobs (1,700) Networking with Oracle (5) Perf Tuning (1) RAC (1) RMAN (8) Scripts (73) Administration (33) backup and recovery (9) Dataguard (2) Performance Tuning (28) RAC (1) Training (23) upgradation (10) User management (3) Vote your opinion… Take Our Poll TechMaster Training TechMaster Training My Facebook Page My Facebook Page My Tweets TechMaster announcing SQL Server DBA online training by Venkat New batch starting from 7th Nov 2016 @ 7 AM IST... fb.me/1AFmsoANU 18hoursago Installing 12c (12 1 0 2) on OEL 7 2 fb.me/62LUdmy27 2daysago 12c Installation video on Oracle Linux 7.2 fb.me/5K9eOxGMr 2daysago Follow @pavandba My DBA links 4shared Akadia Asktom Website Database Journal DBA Oracle DBA Pool DBA Support DBA Village Devshed IXORA My Oracle Support Orabyte Oracle articles Oracle Base Oracle DBA Online Oracle Forums ORACLE RAC SIG ORAFAQ Orakhoj Oraperf Scribd Searchoracle Techtarget Statspack Analyzer Other DBA Blogs All Things Oracle Aman's Blog Arup Nanda's blog Dmitry's Blog Gavin Soorma's blog Hemanth Jonathan Lewis Julian Dyke's blog Kamran Kevin's blog Mario's Blog Rafi's blog Richard foote Satish Blog Sudhakar Blog Tanelpoder's blog Tom Kyte's blog Uwe Hesse Blog Posts Tagged ‘PMON: terminating instance due to error 490' How to resolve ORA-00490error? Posted by Pavan DBA on October 17, 2011 Yesterday in one post (https://pavandba.com/2011/10/16/which-process-starts-first-when-instance-is-started/) I explained about PSP0 process which is introduced in 10g Sometimes all of a sudden our Instance will be crashed and when looked at alert log file we found below error message ORA-00490: