ORA-00304 INSTANCE_NUMBER busy 处理

启动rac第二个节点报错

[oracle@rac2:/home/oracle]$ ora
SQL*Plus: Release 19.0.0.0.0 - Production on Mon May 16 09:54:02 2022
Version 19.7.0.0.0
Copyright (c) 1982, 2020, Oracle. All rights reserved.
Connected to an idle instance.
select
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0


alert日志

Using default pga_aggregate_limit of 2048 MB
2022-05-16T09:54:28.514621+08:00
Error: Shutdown in progress. Error: 304.
USER (ospid: 27810): terminating the instance due to ORA error 304

看下报错解释

[root@rac1 network-scripts]# oerr ora 304
00304, 00000, "requested INSTANCE_NUMBER is busy"
// *Cause: An instance tried to start by using a value of the
// initialization parameter INSTANCE_NUMBER that is already in use.
// *Action: Either
// a) specify another INSTANCE_NUMBER,
// b) shut down the running instance with this number
// c) wait for instance recovery to complete on the instance with
// this number.

实例2的alert确实使用了instance_number = 1

thread = 1
instance_number = 1

但1的实例号已经被实例1占用了，为什么2节点还会用这个呢

从节点1创建一份参数文件发现确实是只有单节点的参数

SQL> show parameter spfile;

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
spfile string +DATADG/TBCSA/PARAMETERFILE/sp
file.338.1093197679



SQL> create pfile='/home/oracle/pfile.bak' from spfile;

File created.
截取部分
[oracle@rac1:/home/oracle]$ cat pfile.bak`````
*.instance_number=1
*.thread=1
`````

问题解决

在活着的节点set下参数就行，根本原因就是参数文件不对，instance_number和thread没配置对，导致占用

SQL> alter system set instance_number=1 scope=spfile sid='tbcsa1';

System altered.

SQL> alter system set instance_number=2 scope=spfile sid='tbcsa2';

System altered.

SQL> alter system set thread=2 scope=spfile sid='tbcsa2';

System altered.

SQL> alter system set undo_tablespace='UNDOTBS2' scope=spfile sid='tbcsa2';System altered.