- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Error message with Oralce 9.0.1.4 RAC with 2 insta...
Operating System - HP-UX
1753885
Members
7335
Online
108809
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-20-2005 11:04 AM
тАО07-20-2005 11:04 AM
This is Oracle 9.0.1.4 RAC with 2 instances.
While instance 2 abnormally down, the alert files are as below,
-----------------------------
instance 1 alert.log....
Wed Jul 20 18:28:27 2005
Reconfiguration complete
Wed Jul 20 18:28:27 2005
Instance recovery: looking for dead threads
Instance recovery: lock domain invalid but no dead threads
---------------------------
instance 2 alert.log....
Wed Jul 20 18:28:27 2005
Reconfiguration complete
LCK0 started with pid=17
Wed Jul 20 18:28:33 2005
Successful mount of redo thread 2, with mount id 912391497.
Wed Jul 20 18:28:33 2005
Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE).
Completed: ALTER DATABASE MOUNT
Wed Jul 20 18:28:33 2005
ALTER DATABASE OPEN
--------------------------------
Why did instance 1 show ....
Instance recovery: looking for dead threads
Instance recovery: lock domain invalid but no dead threads
What's going on?
Thanks
Eric
While instance 2 abnormally down, the alert files are as below,
-----------------------------
instance 1 alert.log....
Wed Jul 20 18:28:27 2005
Reconfiguration complete
Wed Jul 20 18:28:27 2005
Instance recovery: looking for dead threads
Instance recovery: lock domain invalid but no dead threads
---------------------------
instance 2 alert.log....
Wed Jul 20 18:28:27 2005
Reconfiguration complete
LCK0 started with pid=17
Wed Jul 20 18:28:33 2005
Successful mount of redo thread 2, with mount id 912391497.
Wed Jul 20 18:28:33 2005
Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE).
Completed: ALTER DATABASE MOUNT
Wed Jul 20 18:28:33 2005
ALTER DATABASE OPEN
--------------------------------
Why did instance 1 show ....
Instance recovery: looking for dead threads
Instance recovery: lock domain invalid but no dead threads
What's going on?
Thanks
Eric
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-20-2005 12:11 PM
тАО07-20-2005 12:11 PM
Re: Error message with Oralce 9.0.1.4 RAC with 2 instance
hi,
may i know what is db_block_size? also, is this the first time it encounter the problem?
have u also apply any patch with regard to this problem?
u may also like to do something about your assigment of points, it is 3 pages and counting:
http://forums2.itrc.hp.com/service/forums/pageList.do?userId=CA951816&listType=unassigned&forumId=1
regards.
may i know what is db_block_size? also, is this the first time it encounter the problem?
have u also apply any patch with regard to this problem?
u may also like to do something about your assigment of points, it is 3 pages and counting:
http://forums2.itrc.hp.com/service/forums/pageList.do?userId=CA951816&listType=unassigned&forumId=1
regards.
what you do not see does not mean you should not believe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-20-2005 12:33 PM
тАО07-20-2005 12:33 PM
Solution
Hi Eric,
Refer MetaLink Doc ID: 188704.1
This message is just for information. If you don't use replication, you simply can ignore it.
The "replication_dependency_tracking" message is normal acc to Metalink document. "'REPLICATION_DEPENDENCY_TRACKING turned off' message seen in alert logfile" for details on this message.
The parameter REPLICATION_DEPENDENCY_TRACKING enables or disables dependency
tracking for read/write operations to the database. Dependency tracking is essential for propagating changes in a replicated environment.
The parameter REPLICATION_DEPENDENCY_TRACKING which is probable set to TRUE (default setting) inside INIT.ORA or SPFILE. This parameter has been introduced with Oracle8i, however no message was logged in alert logfile with this release.
Lock Domain is a catch all term for resources and DLM locks. This information is distributed among all the active nodes. When instances start or are stopped, This information needs to be redistributed across the new set of active instances. This is done automatically and there is no need for manual intervention.
This is a very common message and can be ignored unless followed by any 'ORA-xxx' errors.
Indira A
Refer MetaLink Doc ID: 188704.1
This message is just for information. If you don't use replication, you simply can ignore it.
The "replication_dependency_tracking" message is normal acc to Metalink document. "'REPLICATION_DEPENDENCY_TRACKING turned off' message seen in alert logfile" for details on this message.
The parameter REPLICATION_DEPENDENCY_TRACKING enables or disables dependency
tracking for read/write operations to the database. Dependency tracking is essential for propagating changes in a replicated environment.
The parameter REPLICATION_DEPENDENCY_TRACKING which is probable set to TRUE (default setting) inside INIT.ORA or SPFILE. This parameter has been introduced with Oracle8i, however no message was logged in alert logfile with this release.
Lock Domain is a catch all term for resources and DLM locks. This information is distributed among all the active nodes. When instances start or are stopped, This information needs to be redistributed across the new set of active instances. This is done automatically and there is no need for manual intervention.
This is a very common message and can be ignored unless followed by any 'ORA-xxx' errors.
Indira A
Never give up, Keep Trying
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2005 12:30 PM
тАО07-27-2005 12:30 PM
Re: Error message with Oralce 9.0.1.4 RAC with 2 instance
Eric,
From the alert logs you showed, it seems you tried starting up the inst2, the one that terminated abnormally, at that point the instance recovery was carried out by inst1, the surviving instance. Essentially, the SMON process of the surviving instance remasters all locks held by the departing-joining instance. In this case this was executed by inst1's SMON process, and that's what you see in the alert log of inst1. This is expected behavior and is a difference in RAC environments.
HTH,
ARC
From the alert logs you showed, it seems you tried starting up the inst2, the one that terminated abnormally, at that point the instance recovery was carried out by inst1, the surviving instance. Essentially, the SMON process of the surviving instance remasters all locks held by the departing-joining instance. In this case this was executed by inst1's SMON process, and that's what you see in the alert log of inst1. This is expected behavior and is a difference in RAC environments.
HTH,
ARC
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP