Instance crashes after clone with ORA-07445 [ksxp_rm_check()+26]

After the database clone completion, instance was crashing frequently and we observed the below error in the alert log file

ORA-07445: exception encountered: core dump [ksxp_rm_check()+26] [SIGSEGV] [ADDR:0x18C8] [PC:0x4BD174C] [Address not mapped to object] []

PMON (ospid: 20890): terminating the instance due to error 602

System state dump requested by (instance=1, osid=20890 (PMON)), summary=[abnormal instance termination].

System State dumped to trace file /schc/app01/app/diag/rdbms/schc/SCHC/trace/SCHC_diag_20901_20160423233812.trc

Dumping diagnostic data in directory=[cdmp_20160423233812], requested by (instance=1, osid=20890 (PMON)), summary=[abnormal instance termination].

Instance terminated by PMON, pid = 20890



We have checked the ORA 07445 error lookup tool for this error and we observed that the document 2044334.1 matches the issue we are facing, As  per the document id we need to increase AQ_TM_PROCESSES to greater than or equal to 1.
1.      First we checked the instance for current number of processes

Before setting parameter
 SQL> show parameter AQ_TM_PROCESSES;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
aq_tm_processes                      integer     0
SQL>
2.In Next step we need to check whether the database is running with pfile or spfile
SQL> show parameter spfile;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
spfile                               string      +OCR01_DG/test/parameterfile/s
                                                 pfile.258.909915713
SQL>
3.If the database is running with SPFILE,then run the below command to increase the processes and check the processes again
SQL> alter system set AQ_TM_PROCESSES=1;
System altered.
SQL> show parameter AQ_TM_PROCESSES;
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
aq_tm_processes                      integer     1



Comments

Post a Comment

Popular posts from this blog

Steps to run Autoconfig for patch File system 12.2

1.       To run Autoconfig from the patch file system you must disable trigger ebs_login prior to running autoconfig. SQL> show user; USER is "SYSTEM" SQL> alter trigger ebs_logon disable; Trigger altered. 2.       Now run autoconfig with the patch env sourced [appltest@test001]$ echo $FILE_EDITION [appltest@test001]$patch [appltest@test001]$ adautocfg.sh Make sure Autoconfig completes ok      3. Enable the login trigger “alter trigger ebs_logon enable”                  SQL> conn system/Oracle4u                  Connected.                SQL> SQL> alter trigger ebs_logon enable;                 Trigger altered.
Read more

txkCfgUtlfileDir.pl -mode=getUtlFileDir as per Cloning Oracle E-Business Suite Release 12.1 with Multitenant Database using Rapid Clone (Doc ID 2560690.1) errors with ERRORMSG: Invalid APPS database user credentials

 txkCfgUtlfileDir.pl -mode=getUtlFileDir as per Cloning Oracle E-Business Suite Release 12.1 with Multitenant Database using Rapid Clone (Doc ID 2560690.1) errors with ERRORMSG: Invalid APPS database user credentials validate_apps_password.log Pattern found... ================ EXIT STATUS: 1 Invalid APPS database user credentials. Solution Check  lsnrctl status <listener_name>,check files under $TNS_ADMIN,check environment,Check if case sensitive login is enabled and if enabled,disable it
Read more

ADOP fs_clone failing with ERROR: Managed Server's are not in sync between file system context and DB context

 adop fs_clone failing with below error. +++++++++++++++++++++++++ configProperty id = Server11 Count for NodeIterator nextNode = 3 ERROR: Managed Server's are not in sync between file system context and DB context ERROR: Update Moveplan Fail START: Inside exitClone.... Updating status INCOMPLETE for ApplywlsTechStack START: Updating status INCOMPLETE for action ApplywlsTechStack END: Updated status INCOMPLETE for action ApplywlsTechStack SOLUTION Please follow the solution in  Doc ID 2232990.1  and advise accordingly To resolve the issue test the following steps in a development instance and then migrate accordingly: 1. Unlock the configuration in the weblogic console via the following steps: A. Open a browser and enter the weblogic console URL eg: https ://localhost:port/console as the administrator. B. Navigate to the weblogic server administration Applications Configuration console. C. Unlock the weblogic server configuration by clicking 'Release Configuration' option.
Read more