Database can't be started on Node 1 due to serverpool Max value is 1
2016-10-16 15:23
357 查看
Database can't be started on Node 1 due to serverpool Max value is 1
Problem Description:
数据库从node 1装的，在node 1 起不来，却在node 2 上是好好的.
DIAGNOSTIC ANALYSIS:
跑在rig7_svr_pool 这个serverpool里面,现在只有一个server,所以就只能起一个instance,所以要扩大serverpool.
当Active servers count 为1 的时候，db instance会自动在另外一个节点起来了。
Solution:
用srvctl modify serverpool -serverpool rig7_svr_pool -max 2。修改max之后 ,db instance 会在所有server上自动起来，若是instance在两个节点都在跑，说明DB 已经正常运行了。
Problem Description:
racusr@itqe-t4seville-1-ld1:~$ srvctl start database -db rig7_db PRCC-1014 : rig7_db was already running PRCR-1004 : Resource ora.rig7_db.db is already running PRCR-1079 : Failed to start resource ora.rig7_db.db CRS-5702: Resource 'ora.rig7_db.db' is already running on 'itqe-t4seville-2-ld1' racusr@itqe-t4seville-1-ld1:~$
数据库从node 1装的，在node 1 起不来，却在node 2 上是好好的.
DIAGNOSTIC ANALYSIS:
racusr@itqe-t4seville-1-ld1:~$ srvctl config serverpool -serverpool rig7_svr_pool Server pool name: rig7_svr_pool Importance: 0, Min: 0, Max: 1 Category: hub Candidate server names: racusr@itqe-t4seville-1-ld1:~$ srvctl status serverpool -serverpool rig7_svr_pool Server pool name: rig7_svr_pool Active servers count: 1
跑在rig7_svr_pool 这个serverpool里面,现在只有一个server,所以就只能起一个instance,所以要扩大serverpool.
当Active servers count 为1 的时候，db instance会自动在另外一个节点起来了。
Solution:
用srvctl modify serverpool -serverpool rig7_svr_pool -max 2。修改max之后 ,db instance 会在所有server上自动起来，若是instance在两个节点都在跑，说明DB 已经正常运行了。
eg. racusr@itqe-t4seville-1-ld1:~$ srvctl modify serverpool -serverpool rig7_svr_pool -max 2 racusr@itqe-t4seville-1-ld1:~$ srvctl status database -db rig7_db Instance rig7db_1 is running on node itqe-t4seville-2-ld1 Instance rig7db_2 is running on node itqe-t4seville-1-ld1
内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理 
相关文章推荐
- is present but cannot be translated into a null value due to being declared as a primitive type
- Optional int parameter 'folderId' is not present but cannot be translated into a null value due to b
- Optional int parameter 'version' is present but cannot be translated into a null value due to being
- A value is trying to be set on a copy of a slice from a DataFrame
- 服务器的日志一直报Packet for query is too large (7632997 > 4194304). You can change this value on the server by setting the max_allowed_packet' variable.的解决方法
- An explicit value for the identity column in table can only be specified when a column list is used and IDENTITY_INSERT is ON
- Optional int parameter 'topicId' is present but cannot be translated into a null value due to being
- Optional int parameter 'page' is present but cannot be translated into a null value due to being dec
- Optional int parameter 'id' is present but cannot be translated into a null value due to being decla
- dataframe插入数据报错SettingWithCopyWarning: A value is trying to be set on a copy of a slice from a
- MySQL5中大数据错误：Packet for query is too large (****** > ******). You can change this value on the server by setting the max_allowed_packet' variable.;
- Optional int parameter 'pageNumber' is present but cannot be translated into a null value due to bei
- Optional int parameter 'projectId' is present but cannot be translated into a null value due to bein
- Optional int parameter 'rip' is present but cannot be translated into a null value due to being decl
- Access restriction: The type Node is not accessible due to restriction on required library C: \Prog
- Linux服务器上日志报com.mysql.jdbc.PacketTooBigException: Packet for query is too large (1783 > 1024). You can change this value on the server by setting the max_allowed_packet' variable.
- DB can't be started due to Memory lack
- Packet for query is too large (1986748 > 1048576). You can change this value on the server by setting the max_allowed_pa
- PRVF-7593 : CRS is not found to be installed on node "rac2"
- Optional int parameter 'id' is present but cannot be translated into a null value due to being decla