【YashanDB知识库】YAS-02605 the current instance is not master role

简介: 【YashanDB知识库】YAS-02605 the current instance is not master role

本文内容来自YashanDB官网,原文内容请见 https://www.yashandb.com/newsinfo/7849018.html?templateId=1718516

【标题】错误码处理

【问题分类】恢复YAC数据库报错

【关键字】YAS-02605

【问题描述】在共享集群架构数据库上实施恢复,触发报错

【问题原因分析】执行恢复的节点不是master节点。

【解决/规避方法】

执行以下sql,确定master role:
select INST_ID,HOST_NAME,INSTANCE_ROLE from gv$instance;
示例输出类似:

在master role上执行恢复,如果数据库备份与master role不在同一节点,则关闭其他节点,使得本节点成为新的master role。

相关文章
|
1月前
|
安全 网络安全 数据库
【YashanDB知识库】单机部署报错:prohibited operation, please check if the IP and username are correct
【YashanDB知识库】单机部署报错:prohibited operation, please check if the IP and username are correct
|
28天前
|
SQL
【YashanDB知识库】YAS-04115 "SELECT" expected but missing
【YashanDB知识库】YAS-04115 "SELECT" expected but missing
|
29天前
|
SQL 数据库
【YashanDB知识库】YAS-02605 the current instance is not master role
【YashanDB知识库】在共享集群架构数据库上实施恢复,触发报错
|
1月前
|
SQL 数据库
【YashanDB 知识库】YAS-02605 the current instance is not master role
【YashanDB 知识库】YAS-02605 the current instance is not master role
|
29天前
|
SQL
【YashanDB 知识库】YAS-04115 "SELECT" expected but missing
【YashanDB 知识库】YAS-04115 "SELECT" expected but missing
|
1月前
|
数据库
【YashanDB知识库】YAS-02507 base incremental backup set does not exist
【YashanDB知识库】YAS-02507 base incremental backup set does not exist
|
29天前
|
运维
【YashanDB知识库】YAS-05534 unsupport operation
【YashanDB知识库】YAS-05534 unsupport operation
|
1月前
|
数据库
【YashanDB知识库】YAS-00004 feature "create user" has not been implemented yet
【YashanDB知识库】YAS-00004 feature "create user" has not been implemented yet
|
2月前
|
安全 网络安全 数据库
【YashanDB 知识库】单机部署报错:prohibited operation, please check if the IP and username are correct
在部署过程中,第1步install成功,但第2步deploy时出现“prohibited operation”错误。原因是主机配置文件(hosts.toml)中的SSH登录IP非本机地址,崖山数据库部署禁止远程操作。解决方法:将SSH登录IP改为本地IP及端口。
|
1月前
|
数据库
【YashanDB知识库】YAS-02547 there is a gap in the restored archived logs on instance 1, reason: start of restored archive 35 is greater than database last archive 21
【YashanDB知识库】YAS-02547 there is a gap in the restored archived logs on instance 1, reason: start of restored archive 35 is greater than database last archive 21