Crs-4013 this command is not supported in a single-node configuration

Merhaba single node yapıda ki bir cluster sistemi durdururken aldıgım bir hatadan ve çözümünden bahsedecegim.

Hata aşagıda da görüldügü gibi,cluster servislerini durdurmaya çalışırken alıyorum.Hataya baktıgımız da hatanın nedeni olarak single instance bir cluster yapının bu şelkilde durdurulamayıcagı ile ilgilidir.Hata aşagıda ki gibidir.

[root@asm-test ~]# /u01/app/11.2.0/grid/bin/crsctl stop crs
CRS-4013: This command is not supported in a single-node configuration.
CRS-4000: Command Stop failed, or completed with errors.

Bunun çözümü olarak cluster servisini single node oldugunda aşagıda ki gibi kapatmalıyız.

[root@asm-test ~]# /u01/app/11.2.0/grid/bin/crsctl stop resource -all
CRS-2500: Cannot stop resource ‘ora.diskmon’ as it is not running
CRS-2500: Cannot stop resource ‘ora.ons’ as it is not running
CRS-2673: Attempting to stop ‘ora.LISTENER.lsnr’ on ‘asm-test’
CRS-2673: Attempting to stop ‘ora.evmd’ on ‘asm-test’
CRS-2673: Attempting to stop ‘ora.DGDATA.dg’ on ‘asm-test’
CRS-2673: Attempting to stop ‘ora.DGFRA.dg’ on ‘asm-test’
CRS-2673: Attempting to stop ‘ora.DGINDEX.dg’ on ‘asm-test’
CRS-2673: Attempting to stop ‘ora.asmorcl.db’ on ‘asm-test’
CRS-2677: Stop of ‘ora.DGINDEX.dg’ on ‘asm-test’ succeeded
CRS-2677: Stop of ‘ora.evmd’ on ‘asm-test’ succeeded
CRS-2677: Stop of ‘ora.LISTENER.lsnr’ on ‘asm-test’ succeeded
CRS-2677: Stop of ‘ora.DGDATA.dg’ on ‘asm-test’ succeeded
CRS-2677: Stop of ‘ora.DGFRA.dg’ on ‘asm-test’ succeeded
CRS-2677: Stop of ‘ora.asmorcl.db’ on ‘asm-test’ succeeded
CRS-2673: Attempting to stop ‘ora.asm’ on ‘asm-test’
CRS-2677: Stop of ‘ora.asm’ on ‘asm-test’ succeeded
CRS-2673: Attempting to stop ‘ora.cssd’ on ‘asm-test’
CRS-2677: Stop of ‘ora.cssd’ on ‘asm-test’ succeeded
CRS-4000: Command Stop failed, or completed with errors.

NOT : Aynı durum single instance da start için de geçerlidir.

Yararlı olması Dilegiyle…
Yazar : Mustafa Bektaş Tepe

 21,584 total views,  2 views today

당신은 주제를 찾고 있습니까 “crs-4013 this command is not supported in a single-node configuration – code: ‘MODULE_NOT_FOUND’ | Bug Report | NODE JS | Beginners“? 다음 카테고리의 웹사이트 https://chewathai27.com/you 에서 귀하의 모든 질문에 답변해 드립니다: https://chewathai27.com/you/blog. 바로 아래에서 답을 찾을 수 있습니다. 작성자 Debugger 이(가) 작성한 기사에는 조회수 32,556회 및 좋아요 169개 개의 좋아요가 있습니다.

• crs-4013 this command is not supported in a single-node configuration 주제에 대한 동영상 보기
• d여기에서 code: ‘MODULE_NOT_FOUND’ | Bug Report | NODE JS | Beginners – crs-4013 this command is not supported in a single-node configuration 주제에 대한 세부정보를 참조하세요
• crs-4013 this command is not supported in a single-node configuration 주제에 대한 자세한 내용은 여기를 참조하세요.
  • CRS-4013: This command is not supported in a single-node …
  • GRID Infrastructure startup on one node encounters CRS-4013
  • CRS-4013: This command is not supported in a single-node …
  • CRS-4013: This command is not supported in a single-node …
  • CRS-4013: This command is not supported in a … – 文章整合
  • CRS-4013: This command is not supported in a … – 墨天轮
  • Starting and Stopping Grid Infrastructure on a Standalone GI …
  • تويتر \ Andrejs Karpovs on Twitter: “”crsctl stop crs” resulted in …
  • CRS-4013: This command is not supported in a single-node …
  • [INS-40719]IP address configured for Single Client Access …
• 주제와 관련된 이미지 crs-4013 this command is not supported in a single-node configuration
• 주제에 대한 기사 평가 crs-4013 this command is not supported in a single-node configuration
  • How do I turn off CRS in single node?
  • How do I start CRS on all nodes?
  • How do I turn off Oracle grid infrastructure?
  • What does Crsctl stop has do?
  • How do I turn off CRS?
  • How do I disable CRS?
  • How do I manually start CRS?
  • How do I check CRS services?
  • What is difference between CRS and cluster?
  • How do I start an ASM in single node?
  • How do I start and stop Oracle RAC database 12c?
  • How do I start and stop Oracle Service in Linux?
  • How do I run a Crsctl command?
  • How do you stop a database using Crsctl?
  • What is Crsctl and Srvctl?
  • How do you stop a database using Crsctl?
  • How do I stop clusters on all nodes?
  • How do I check my CRS status?
  • How do I run a Crsctl command?
• CRS-4013: This command is not supported in a single-node configuration – DBACLASS
• GRID Infrastructure startup on one node encounters CRS-4013: This command is not supported in a single-node configuration.
• Remote Oracle Database Support : CRS-4013: This command is not supported in a single-node configuration
• CRS-4013: This command is not supported in a single-node configuration.
• CRS-4013: This command is not supported in a single-node configuration.
• KunLun Mission Critical Server Oracle Database Oracle 11g (RAC) Best Practice 02
• crsctl start crs
• How to Stop Processes in an Existing Oracle RAC Database
• whats the difference between crsctl stop has and crsctl stop crs
• CRS-4013: This command is not supported in a single-node configuration.
• Starting and Stopping Grid Infrastructure on a Standalone GI Installation
• 키워드에 대한 정보 crs-4013 this command is not supported in a single-node configuration
• 사람들이 주제에 대해 자주 검색하는 키워드 code: ‘MODULE_NOT_FOUND’ | Bug Report | NODE JS | Beginners

여기에서 이 주제에 대한 비디오를 시청하십시오. 주의 깊게 살펴보고 읽고 있는 내용에 대한 피드백을 제공하세요!

d여기에서 code: ‘MODULE_NOT_FOUND’ | Bug Report | NODE JS | Beginners – crs-4013 this command is not supported in a single-node configuration 주제에 대한 세부정보를 참조하세요

This video is about removing the bug of the module not found. There can be many cases which programmers used to face. Here are some possibilities for this error that may helpful for beginners.
Error Name:
‘MODULE_NOT_FOUND’
Some solutions related to this error:
https://stackoverflow.com/questions/47083351/node-module-not-found
https://stackoverflow.com/questions/16163176/module-not-found-error-in-node-js

Follow me on Instagram.
https://www.instagram.com/im_debugger/

crs-4013 this command is not supported in a single-node configuration 주제에 대한 자세한 내용은 여기를 참조하세요.

CRS-4013: This command is not supported in a single-node …

PROBLEM: While shutting down crs, got below error. [[email protected]]# ./crsctl stop crs CRS-4013: This command is not supported in a single-node configuration.

+ 여기에 표시

Source: dbaclass.com

Date Published: 3/9/2021

View: 6503

GRID Infrastructure startup on one node encounters CRS-4013

GRID Infrastructure startup on one node encounters CRS-4013: This command is not supported in a single-node configuration. (Doc ID 1672116.1).

+ 더 읽기

Source: support.oracle.com

Date Published: 4/7/2022

View: 1237

CRS-4013: This command is not supported in a single-node …

CRS-4013: This command is not supported in a single-node configuration · 1. Error while starting up cluster on problematic node( · 2. Check …

+ 여기에 자세히 보기

Source: www.moreajays.com

Date Published: 1/23/2022

View: 8665

CRS-4013: This command is not supported in a single-node …

In 11gR2 RAC configuration, after planned shutdown I wanted to start the Gr infrastructure. So I issued crsctl start crs command, …

+ 여기에 자세히 보기

Source: oraclehandson.wordpress.com

Date Published: 7/25/2022

View: 3262

CRS-4013: This command is not supported in a … – 文章整合

crsctl stop crs CRS-4013: This command is not supported in a single-node configuration. CRS-4000: Command Stop failed, or completed with …

+ 여기에 표시

Source: chowdera.com

Date Published: 8/2/2022

View: 128

CRS-4013: This command is not supported in a … – 墨天轮

Problem: While start up crs, got below error. $ crsctl start crs. CRS-4013: This command is not supported in a single-node configuration.

+ 여기에 자세히 보기

Source: www.modb.pro

Date Published: 11/20/2022

View: 3234

Starting and Stopping Grid Infrastructure on a Standalone GI …

[[email protected]~]$ /u01/app/11203/gr/bin/crsctl stop crs. CRS-4013: This command is not supported in a single-node configuration. CRS-4000: Command …

+ 여기를 클릭

Source: www.oraclenext.com

Date Published: 6/20/2021

View: 4753

تويتر \ Andrejs Karpovs on Twitter: “”crsctl stop crs” resulted in …

“crsctl stop crs” resulted in CRS-4013: This command is not supported in a single-node configuration, while “crsctl stop has” worked fine.

+ 여기에 보기

Source: twitter.com

Date Published: 6/27/2021

View: 6475

CRS-4013: This command is not supported in a single-node …

[[email protected] ~]# /u01/app/11.2.0/gr/bin/crsctl stop crs. CRS-4013: This command is not supported in a single-node configuration.

+ 여기에 자세히 보기

Source: www.mustafabektastepe.com

Date Published: 12/5/2021

View: 2112

[INS-40719]IP address configured for Single Client Access …

Was ASM configured in this Oracle home (y|n) [n]: y Is OCR/Voting Disk … Restart CRS-4013: This command is not supported in a single-node …

+ 여기에 자세히 보기

Source: blog.csdn.net

Date Published: 3/23/2022

View: 7589

주제와 관련된 이미지 crs-4013 this command is not supported in a single-node configuration

주제와 관련된 더 많은 사진을 참조하십시오 code: ‘MODULE_NOT_FOUND’ | Bug Report | NODE JS | Beginners. 댓글에서 더 많은 관련 이미지를 보거나 필요한 경우 더 많은 관련 기사를 볼 수 있습니다.

주제에 대한 기사 평가 crs-4013 this command is not supported in a single-node configuration

• Author: Debugger
• Views: 조회수 32,556회
• Likes: 좋아요 169개
• Date Published: 2021. 4. 28.
• Video Url link: https://www.youtube.com/watch?v=TsHqAZgQtOc

How do I turn off CRS in single node?

To stop cluster resources of the local node, run the following command: [[email protected] ~]# /u01/app/11.2. 0/grid/bin/crsctl stop crs CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.

How do I start CRS on all nodes?

1. Step 1: Prepare the New Cluster Nodes.
2. Step 2: Deploy the Oracle Grid Infrastructure Home on the Destination Nodes.
3. Step 3: Run the clone.pl Script on Each Destination Node.
4. Step 4: Launch the Configuration Wizard.

How do I turn off Oracle grid infrastructure?

To stop Oracle Clusterware and Oracle ASM instances on all nodes in the cluster, you can enter a single command: crsctl stop cluster -all . Note: The crsctl stop crs command is used to stop Oracle Restart services for single-instance databases.

What does Crsctl stop has do?

Use the crsctl stop has command to stop Oracle High Availability Services on the local server. Use the crsctl stop crs command to stop Oracle High Availability Services on the local server. For me is the same action about what the commands do. You must use the proper command depending of your environment.

How do I turn off CRS?

If you need to manually stop CRS outside of VCS control, run the following command: # $CRS_HOME/bin/crsctl stop crs Stopping resources.

How do I disable CRS?

CRSCTL utility present in Grid_home/bin location.

1. Check the Clusterware on all nodes or single node. …
2. Start and stop the Clusterware on all nodes or Single node. …
3. Get hostname with CRSCTL. …
4. Add and Delete resource with Crsctl commands. …
5. Get the cluster configuration. …
6. Get cluster name. …
7. Configure the CRS. …
8. Enable and disable the CRS.

How do I manually start CRS?

The basic steps to start the CRS include these startup actions:.

1. Enable the crs, css, and evm daemons in /etc/inittab.
2. Execute /etc/init.d/init.crs enable.
3. Execute /etc/init.d/init.crs start.
4. Execute $ORA_CRS_HOME/bin/crsctl start crs.

How do I check CRS services?

1. Step 1: Prepare the New Cluster Nodes.
2. Step 2: Deploy the Oracle Grid Infrastructure Home on the Destination Nodes.
3. Step 3: Run the clone.pl Script on Each Destination Node.
4. Step 4: Launch the Configuration Wizard.

What is difference between CRS and cluster?

Despite crsctl start/stop crs manage entire Oracle Clusterware stack on local node crsctl start/stop crs not allow you to manage remote nodes, unlike crsctl start/stop cluster that allows you to manage all the nodes, but if the process OASH is runing.

How do I start an ASM in single node?

Startup and shutdown the Oracle ASM instance

1. Set the default Oracle_home environment variable to grid home where ASM is installed. EXPORT ORACLE_HOME=/up1/grid/12.2.0/dbhome_1. …
2. Connect with sqlplus. SQLPLUS / as sysasm.
3. Start up the Oracle ASM Instance. SQL> STARTUP. …
4. Check the spfile location or otherwise set it with.

How do I start and stop Oracle RAC database 12c?

Stopping and Starting RAC Services

1. emctl stop dbconsole.
2. srvctl stop listener -n racnode1.
3. srvctl stop database -d RACDB.
4. srvctl stop asm -n racnode1 -f.
5. srvctl stop asm -n racnode2 -f.
6. srvctl stop nodeapps -n racnode1 -f.
7. crsctl stop crs.

How do I start and stop Oracle Service in Linux?

Do one of the following:

1. On Windows: Click Start, point to Programs (or All Programs), point to Oracle Database 11g Express Edition, and then select Stop Database.
2. On Linux with Gnome: In the Applications menu, point to Oracle Database 11g Express Edition, and then select Stop Database.

How do I run a Crsctl command?

You can run these commands from any node in the cluster on another node in the cluster, or on all nodes in the cluster, depending on the operation.
…
Clusterized commands include the following:

1. crsctl check cluster.
2. crsctl start cluster.
3. crsctl stop cluster.

How do you stop a database using Crsctl?

It’s really easy to use “crsctl stop cluster -all” followed by “dcli -l root -g ~/dbs_group /u01/app/11.2. 0.4/grid/bin/crsctl stop crs” to get everything down quickly.

What is Crsctl and Srvctl?

crsctl start cluster -all. Starts the cluster in all nodes. SRVCTL Commands :- Database Related Commands.

How do you stop a database using Crsctl?

It’s really easy to use “crsctl stop cluster -all” followed by “dcli -l root -g ~/dbs_group /u01/app/11.2. 0.4/grid/bin/crsctl stop crs” to get everything down quickly.

How do I stop clusters on all nodes?

To stop Oracle Clusterware and Oracle ASM instances on all nodes in the cluster, you can enter a single command: crsctl stop cluster -all .

How do I check my CRS status?

1. Querying CRS Resource Status.
2. Starting Cluster Resources by Using the crsctl Command.
3. Stopping Cluster Resources by Using the crsctl Command.
4. Starting Database Instances by Using the srvctl Command.
5. Stopping Database Instances by Using the srvctl Command.

How do I run a Crsctl command?

You can run these commands from any node in the cluster on another node in the cluster, or on all nodes in the cluster, depending on the operation.
…
Clusterized commands include the following:

1. crsctl check cluster.
2. crsctl start cluster.
3. crsctl stop cluster.

CRS-4013: This command is not supported in a single-node configuration – DBACLASS

PROBLEM:

While shutting down crs, got below error.

[[email protected]]# ./crsctl stop crs CRS-4013: This command is not supported in a single-node configuration. CRS-4000: Command Stop failed, or completed with errors.

SOLUTION:

In case of standalone grid, there will not be any crs . Only has component will be there.

So use the below command to shutdown the service.s

GRID Infrastructure startup on one node encounters CRS-4013: This command is not supported in a single-node configuration.

GRID Infrastructure startup on one node encounters CRS-4013: This command is not supported in a single-node configuration. (Doc ID 1672116.1)

Last updated on APRIL 19, 2022

Applies to:

Symptoms

Grid Infrastructure cannot start on one node of a cluster with following error:

Changes

Cause

Sign In To view full details, sign in with your My Oracle Support account. Register Don’t have a My Oracle Support account? Click to get started!

Remote Oracle Database Support : CRS-4013: This command is not supported in a single-node configuration

Issue: Getting CRS-4013 , CRS-4000 error while starting up cluster services

CRS-4013: This command is not supported in a single-node configuration.

CRS-4000: Command Start failed, or completed with errors.

One of the cluster node is reporting the CRS-4013 , CRS-4000 error while other node is up in 2 node RAC cluster

Solution:

1. Error while starting up cluster on problematic node( mytestlab1283)

[[email protected] ~]$ ps -ef | grep pmon ora12c 8572 8540 0 10:59 pts/0 00:00:00 grep –color=auto pmon [[email protected] ~]$ . ./.bash_profile_asm [[email protected] ~]$ which crsctl /rdbms/app/12.1.0.2/grid/bin/crsctl [[email protected] ~]$ sudo /rdbms/app/12.1.0.2/grid/bin/crsctl start crs CRS-4013: This command is not supported in a single-node configuration. CRS-4000: Command Start failed, or completed with errors.

2. Check resource status on working node ( mytestlab12834)

[[email protected] ~]$ ps -ef | grep pmon

ora12c 2601 2550 0 11:09 pts/0 00:00:00 grep –color=auto pmon

ora12c 23415 1 0 May09 ? 00:10:50 asm_pmon_+ASM2

ora12c 23517 1 0 May09 ? 00:12:00 ora_pmon_oemdbmn2

[[email protected] ~]$ sudo /rdbms/app/12.1.0.2/grid/bin/crsctl stop crs -f

CRS-4013: This command is not supported in a single-node configuration.

CRS-4000: Command Stop failed, or completed with errors.

[[email protected] ~]$ crsctl check css

CRS-4639: Could not contact Oracle High Availability Services

CRS-4000: Command Check failed, or completed with errors.

[[email protected] ~]$ crsctl check crs

CRS-4638: Oracle High Availability Services is online

CRS-4537: Cluster Ready Services is online

CRS-4529: Cluster Synchronization Services is online

CRS-4533: Event Manager is online

[[email protected] ~]$ crsctl status res -t

————————————————————

Name Target State Server State details Local Resources

————————————————————-

ora.DATA.dg ONLINE ONLINE mytestlab1284 STABLE

ora.FRA.dg ONLINE ONLINE mytestlab1284 STABLE

ora.LISTENER.lsnr ONLINE ONLINE mytestlab1284 STABLE

ora.OCR_VOTING.dg ONLINE ONLINE mytestlab1284 STABLE

ora.asm ONLINE ONLINE mytestlab1284 Started,STABLE

ora.net1.network ONLINE ONLINE mytestlab1284 STABLE

ora.ons ONLINE ONLINE mytestlab1284 STABLE

——————————————————————–

Cluster Resources

——————————————————————–

ora.LISTENER_SCAN1.lsnr 1 ONLINE ONLINE mytestlab1284 STABLE

ora.LISTENER_SCAN2.lsnr 1 ONLINE ONLINE mytestlab1284 STABLE

ora.LISTENER_SCAN3.lsnr 1 ONLINE ONLINE mytestlab1284 STABLE

ora.MGMTLSNR 1 OFFLINE OFFLINE STABLE

ora.cvu 1 ONLINE ONLINE mytestlab1284 STABLE

ora.mytestlab1283.vip 1 ONLINE INTERMEDIATE mytestlab1284 FAILED OVER,STABLE

ora.mytestlab1284.vip 1 ONLINE ONLINE mytestlab1284 STABLE

ora.oc4j 1 ONLINE ONLINE mytestlab1284 STABLE

ora.oemdbmn.db 1 ONLINE OFFLINE STABLE

2 ONLINE ONLINE mytestlab1284 Open,STABLE

ora.scan1.vip 1 ONLINE ONLINE mytestlab1284 STABLE

ora.scan2.vip 1 ONLINE ONLINE mytestlab1284 STABLE

ora.scan3.vip 1 ONLINE ONLINE mytestlab1284 STABLE

——————————————————————-

[[email protected] trace]$ srvctl config database -d oemdbmn Database unique name: oemdbmn Database name: oemdbmn Oracle home: /rdbms/app/oracle/12.1.0.2/db Oracle user: ora12c Spfile: +DATA/OEMDBMN/PARAMETERFILE/spfile.268.943049417 Password file: +DATA/OEMDBMN/PASSWORD/pwdoemdbmn.256.943049111 Domain: Start options: open Stop options: immediate Database role: PRIMARY Management policy: AUTOMATIC Server pools: Disk Groups: DATA Mount point paths: Services: Type: RAC Start concurrency: Stop concurrency: OSDBA group: dba OSOPER group: dba Database instances: oemdbmn1,oemdbmn2 Configured nodes: mytestlab1283,mytestlab1284

Database is administrator managed

3. Stop crs on working node ( mytestlab12834)

[[email protected] ~]$ sudo /rdbms/app/12.1.0.2/grid/bin/crsctl stop crs [sudo] password for ora12c:

CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on ‘mytestlab1284’

CRS-2673: Attempting to stop ‘ora.crsd’ on ‘mytestlab1284’

CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on ‘mytestlab1284’

CRS-2673: Attempting to stop ‘ora.oemdbmn.db’ on ‘mytestlab1284’

CRS-2673: Attempting to stop ‘ora.oc4j’ on ‘mytestlab1284’

CRS-2673: Attempting to stop ‘ora.LISTENER_SCAN2.lsnr’ on ‘mytestlab1284’

.

.

.

CRS-2677: Stop of ‘ora.cluster_interconnect.haip’ on ‘mytestlab1284’ succeeded

CRS-2673: Attempting to stop ‘ora.cssd’ on ‘mytestlab1284’

CRS-2677: Stop of ‘ora.cssd’ on ‘mytestlab1284’ succeeded

CRS-2673: Attempting to stop ‘ora.gipcd’ on ‘mytestlab1284’

CRS-2677: Stop of ‘ora.gipcd’ on ‘mytestlab1284’ succeeded

CRS-2793: Shutdown of Oracle High Availability Services-managed resources on ‘mytestlab1284’ has completed

CRS-4133: Oracle High Availability Services has been stopped.

[[email protected] ~]$ ps -ef | grep pmon

ora12c 6311 5970 0 11:29 pts/1 00:00:00 grep –color=auto pmon

4. Execute below on problematic node ( mytestlab1283)

[[email protected] ~]$ sudo /rdbms/app/12.1.0.2/grid/bin/crsctl start crs

CRS-4013: This command is not supported in a single-node configuration.

CRS-4000: Command Start failed, or completed with errors.

sudo /rdbms/app/12.1.0.2/grid/crs/install/rootcrs.sh -deconfig -force

sudo /rdbms/app/12.1.0.2/grid/root.sh

5. Verify logs and crs process status on OS

[[email protected] ~]$ ps -ef | grep -i crs

root 25735 25646 0 12:55 pts/0 00:00:00 /bin/sh /rdbms/app/12.1.0.2/grid/crs/config/rootconfig.sh

root 25744 25735 0 12:55 pts/0 00:00:00 /rdbms/app/12.1.0.2/grid/perl/bin/perl -I/rdbms/app/12.1.0.2/grid/perl/lib -I/rdbms/app/12.1.0.2/grid/crs/install /rdbms/app/12.1.0.2/grid/crs/install/rootcrs.pl

root 25763 25744 0 12:55 pts/0 00:00:00 /bin/sh /rdbms/app/12.1.0.2/grid/crs/install/tfa_setup -silent -crshome /rdbms/app/12.1.0.2/grid

ora12c 26600 26372 0 12:57 pts/1 00:00:00 grep –color=auto -i crs

[[email protected] ~]$ ps -ef | grep -i crs

root 25735 25646 0 12:55 pts/0 00:00:00 /bin/sh /rdbms/app/12.1.0.2/grid/crs/config/rootconfig.sh

root 25744 25735 0 12:55 pts/0 00:00:00 /rdbms/app/12.1.0.2/grid/perl/bin/perl -I/rdbms/app/12.1.0.2/grid/perl/lib -I/rdbms/app/12.1.0.2/grid/crs/install /rdbms/app/12.1.0.2/grid/crs/install/rootcrs.pl

root 28153 25744 0 12:58 pts/0 00:00:00 sh -c /bin/su ora12c -c ‘ echo CLSRSC_START; /rdbms/app/12.1.0.2/grid/bin/cluutil -ckpt -oraclebase /rdbms/app/oracle -chkckpt -name ROOTCRS_INITRES ‘ 2>&1

root 28154 28153 0 12:58 pts/0 00:00:00 /bin/su ora12c -c echo CLSRSC_START; /rdbms/app/12.1.0.2/grid/bin/cluutil -ckpt -oraclebase /rdbms/app/oracle -chkckpt -name ROOTCRS_INITRES

ora12c 28155 28154 0 12:58 ? 00:00:00 bash -c echo CLSRSC_START; /rdbms/app/12.1.0.2/grid/bin/cluutil -ckpt -oraclebase /rdbms/app/oracle -chkckpt -name ROO CRS_INITRES

ora12c 28156 28155 0 12:58 ? 00:00:00 /bin/sh /rdbms/app/12.1.0.2/grid/bin/cluutil -ckpt -oraclebase /rdbms/app/oracle -chkckpt -name ROOTCRS_INITRES

ora12c 28159 28156 0 12:58 ? 00:00:00 /rdbms/app/12.1.0.2/grid/jdk/bin/java -DTRACING.ENABLED=true -DTRACING.LEVEL=2 -classpath /rdbms/app/12.1.0.2/grid/jlib/srvm.jar:/rdbms/app/12.1.0.2/grid/jlib/srvmhas.jar:/rdbms/app/12.1.0.2/grid/oui/jlib/OraCheckPoint.jar:/rdbms/app/12.1.0.2/grid/oui/jlib/OraInstaller.jar:/rdbms/app/12.1.0.2/grid/oui/jlib/xmlparserv2.jar oracle.ops.util.ClusterUtil -ckpt -oraclebase /rdbms/app/oracle -chkckpt -name ROOTCRS_INITRES

ora12c 28172 26372 0 12:58 pts/1 00:00:00 grep –color=auto -i crs

[[email protected] ~]$ tail -f /rdbms/app/12.1.0.2/grid/install/root_mytestlab1283.vsnl.co.in_2017-08-10_13-01-13.log

Copying coraenv to /usr/local/bin …

Entries will be added to the /etc/oratab file as needed by

Database Configuration Assistant when a database is created

Finished running generic part of root script.

Now product-specific root actions will be performed.

Relinking oracle with rac_on option

Using configuration parameter file: /rdbms/app/12.1.0.2/grid/crs/install/crsconfig_params

2017/08/10 13:01:14 CLSRSC-4001: Installing Oracle Trace File Analyzer (TFA) Collector.

2017/08/10 13:03:00 CLSRSC-4002: Successfully installed Oracle Trace File Analyzer (TFA) Collector.

2017/08/10 13:03:01 CLSRSC-363: User ignored prerequisites during installation

2017/08/10 13:04:06 CLSRSC-330: Adding Clusterware entries to file ‘oracle-ohasd.service’

CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on ‘mytestlab1283’

CRS-2673: Attempting to stop ‘ora.gpnpd’ on ‘mytestlab1283’

CRS-2673: Attempting to stop ‘ora.mdnsd’ on ‘mytestlab1283’

CRS-2673: Attempting to stop ‘ora.gipcd’ on ‘mytestlab1283’

CRS-2673: Attempting to stop ‘ora.evmd’ on ‘mytestlab1283’

CRS-2677: Stop of ‘ora.gpnpd’ on ‘mytestlab1283’ succeeded

CRS-2677: Stop of ‘ora.mdnsd’ on ‘mytestlab1283’ succeeded

CRS-2677: Stop of ‘ora.evmd’ on ‘mytestlab1283’ succeeded

CRS-2677: Stop of ‘ora.gipcd’ on ‘mytestlab1283’ succeeded

CRS-2793: Shutdown of Oracle High Availability Services-managed resources on ‘mytestlab1283’ has completed

.

.

.

.

CRS-2672: Attempting to start ‘ora.LISTENER.lsnr’ on ‘mytestlab1283’

CRS-2676: Start of ‘ora.LISTENER_SCAN3.lsnr’ on ‘mytestlab1283’ succeeded

CRS-2676: Start of ‘ora.LISTENER_SCAN2.lsnr’ on ‘mytestlab1283’ succeeded

CRS-2676: Start of ‘ora.LISTENER.lsnr’ on ‘mytestlab1283’ succeeded

CRS-2672: Attempting to start ‘ora.oemdbmn.db’ on ‘mytestlab1283’

CRS-2676: Start of ‘ora.oc4j’ on ‘mytestlab1283’ succeeded

CRS-2676: Start of ‘ora.oemdbmn.db’ on ‘mytestlab1283’ succeeded

CRS-6016: Resource auto-start has completed for server mytestlab1283

CRS-6024: Completed start of Oracle Cluster Ready Services-managed resources

CRS-4123: Oracle High Availability Services has been started.

2017/08/10 13:07:53 CLSRSC-343: Successfully started Oracle Clusterware stack

PRKO-2190 : VIP exists for node mytestlab1283, VIP name mytestlab1283-vip.vsnl.co.in

PRKZ-1072 : SCAN name “XPDBoemdbmn” is already registered on network 1

PRCS-1028 : Single Client Access Name (SCAN) listener resources already exist on network 1

PRCN-3004 : Listener MGMTLSNR already exists

PRCR-1086 : resource ora.cvu is already registered

PRCC-1014 : scan1 was already running

PRCR-1004 : Resource ora.scan1.vip is already running

PRCR-1079 : Failed to start resource ora.scan1.vip

CRS-5702: Resource ‘ora.scan1.vip’ is already running on ‘mytestlab1283’

.

.

PRCC-1014 : cvu was already running

PRCR-1004 : Resource ora.cvu is already running

PRCR-1079 : Failed to start resource ora.cvu

CRS-5702: Resource ‘ora.cvu’ is already running on ‘mytestlab1283’

Preparing packages…

cvuqdisk-1.0.9-1.x86_64

PRCN-3004 : Listener LISTENER already exists

PRCC-1015 : LISTENER was already running on mytestlab1283

PRCR-1004 : Resource ora.LISTENER.lsnr is already running

2017/08/10 13:08:36 CLSRSC-325: Configure Oracle Grid Infrastructure for a Cluster … succeeded

CRS-4013: This command is not supported in a single-node configuration.

In 11gR2 RAC configuration, after planned shutdown I wanted to start the Grid infrastructure. So I issued crsctl start crs command, which resulted in following error

# crsctl start crs CRS-4013: This command is not supported in a single-node configuration. CRS-4000: Command Start failed, or completed with errors.

Being a development cluster, initially I thought someone have messed up with the RAC configuration by switching OFF the RAC. So to check the current configuration I issued following commands.

cd $GRID_HOME/rdbms/lib ar -t libknlopt.a | grep -c kcsm.o (return 0 if RAC is disabled or a number >0 if enabled)

This command returned value 1. Which means RAC was ON.

There was nothing obvious in the log, which points to the cause of this error. Also CRS was running on other node.

Tried with few more things

# crsctl start resource -all # /etc/init.d/ohasd start

But still could not start the CRS.

Finally deconfigured the CRS

# /oragrid/crs/install rootcrs.pl -deconfig -force

Then again configured it

# /oragrid/root.sh

Last approach worked, but I could not ascertain the root cause of this error.

CRS-4013: This command is not supported in a single-node configuration.

crsctl stop crs CRS – 4013 : This command is not supported in a single – node configuration . CRS – 4000 : Command Stop failed , or completed with errors .

crsctl stop has CRS – 2791 : Starting shutdown of Oracle High Availability Services – managed resources on ‘lhr2019ocpasm’ CRS – 2673 : Attempting to stop ‘ora . asm’ on ‘lhr2019ocpasm’ CRS – 2673 : Attempting to stop ‘ora . lhr19sdb . db’ on ‘lhr2019ocpasm’ CRS – 2673 : Attempting to stop ‘ora . LISTENER . lsnr’ on ‘lhr2019ocpasm’ CRS – 2677 : Stop of ‘ora . LISTENER . lsnr’ on ‘lhr2019ocpasm’ succeeded CRS – 2677 : Stop of ‘ora . lhr19sdb . db’ on ‘lhr2019ocpasm’ succeeded CRS – 2677 : Stop of ‘ora . asm’ on ‘lhr2019ocpasm’ succeeded CRS – 2673 : Attempting to stop ‘ora . evmd’ on ‘lhr2019ocpasm’ CRS – 2677 : Stop of ‘ora . evmd’ on ‘lhr2019ocpasm’ succeeded CRS – 2673 : Attempting to stop ‘ora . cssd’ on ‘lhr2019ocpasm’ CRS – 2677 : Stop of ‘ora . cssd’ on ‘lhr2019ocpasm’ succeeded CRS – 2793 : Shutdown of Oracle High Availability Services – managed resources on ‘lhr2019ocpasm’ has completed CRS – 4133 : Oracle High Availability Services has been stopped .

KunLun Mission Critical Server Oracle Database Oracle 11g (RAC) Best Practice 02

To stop cluster resources of the local node, run the following command:

[[email protected] ~]# /u01/app/11.2.0/grid/bin/crsctl stop crs CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.crsd’ on ‘dbn01’ CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.LISTENER_SCAN1.lsnr’ on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.oc4j’ on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.OCR.dg’ on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.registry.acfs’ on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.dbn.db’ on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.cvu’ on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.LISTENER.lsnr’ on ‘dbn01’ CRS-2677: Stop of ‘ora.cvu’ on ‘dbn01’ succeeded CRS-2672: Attempting to start ‘ora.cvu’ on ‘dbn02’ CRS-2677: Stop of ‘ora.LISTENER_SCAN1.lsnr’ on ‘dbn01’ succeeded CRS-2673: Attempting to stop ‘ora.scan1.vip’ on ‘dbn01’ CRS-2677: Stop of ‘ora.LISTENER.lsnr’ on ‘dbn01’ succeeded CRS-2673: Attempting to stop ‘ora.dbn01.vip’ on ‘dbn01’ CRS-2676: Start of ‘ora.cvu’ on ‘dbn02’ succeeded CRS-2677: Stop of ‘ora.registry.acfs’ on ‘dbn01’ succeeded CRS-2677: Stop of ‘ora.dbn.db’ on ‘dbn01’ succeeded CRS-2673: Attempting to stop ‘ora.DATA.dg’ on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.FRA.dg’ on ‘dbn01’ CRS-2677: Stop of ‘ora.DATA.dg’ on ‘dbn01’ succeeded CRS-2677: Stop of ‘ora.FRA.dg’ on ‘dbn01’ succeeded CRS-2677: Stop of ‘ora.dbn01.vip’ on ‘dbn01’ succeeded CRS-2672: Attempting to start ‘ora.dbn01.vip’ on ‘dbn02’ CRS-2677: Stop of ‘ora.scan1.vip’ on ‘dbn01’ succeeded CRS-2672: Attempting to start ‘ora.scan1.vip’ on ‘dbn02’ CRS-2677: Stop of ‘ora.oc4j’ on ‘dbn01’ succeeded CRS-2672: Attempting to start ‘ora.oc4j’ on ‘dbn02’ CRS-2676: Start of ‘ora.dbn01.vip’ on ‘dbn02’ succeeded CRS-2676: Start of ‘ora.scan1.vip’ on ‘dbn02’ succeeded CRS-2672: Attempting to start ‘ora.LISTENER_SCAN1.lsnr’ on ‘dbn02’ CRS-2676: Start of ‘ora.LISTENER_SCAN1.lsnr’ on ‘dbn02’ succeeded CRS-2677: Stop of ‘ora.OCR.dg’ on ‘dbn01’ succeeded CRS-2673: Attempting to stop ‘ora.asm’ on ‘dbn01’ CRS-2677: Stop of ‘ora.asm’ on ‘dbn01’ succeeded CRS-2676: Start of ‘ora.oc4j’ on ‘dbn02’ succeeded CRS-2673: Attempting to stop ‘ora.ons’ on ‘dbn01’ CRS-2677: Stop of ‘ora.ons’ on ‘dbn01’ succeeded CRS-2673: Attempting to stop ‘ora.net1.network’ on ‘dbn01’ CRS-2677: Stop of ‘ora.net1.network’ on ‘dbn01’ succeeded CRS-2792: Shutdown of Cluster Ready Services-managed resources on ‘dbn01’ has completed CRS-2677: Stop of ‘ora.crsd’ on ‘dbn01’ succeeded CRS-2673: Attempting to stop ‘ora.mdnsd’ on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.crf’ on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.ctssd’ on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.evmd’ on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.asm’ on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.drivers.acfs’ on ‘dbn01’ CRS-2677: Stop of ‘ora.mdnsd’ on ‘dbn01’ succeeded CRS-2677: Stop of ‘ora.crf’ on ‘dbn01’ succeeded CRS-2677: Stop of ‘ora.evmd’ on ‘dbn01’ succeeded CRS-2677: Stop of ‘ora.ctssd’ on ‘dbn01’ succeeded CRS-2677: Stop of ‘ora.asm’ on ‘dbn01’ succeeded CRS-2673: Attempting to stop ‘ora.cluster_interconnect.haip’ on ‘dbn01’ CRS-2677: Stop of ‘ora.cluster_interconnect.haip’ on ‘dbn01’ succeeded CRS-2673: Attempting to stop ‘ora.cssd’ on ‘dbn01’ CRS-2677: Stop of ‘ora.cssd’ on ‘dbn01’ succeeded CRS-2673: Attempting to stop ‘ora.gipcd’ on ‘dbn01’ CRS-2677: Stop of ‘ora.gipcd’ on ‘dbn01’ succeeded CRS-2673: Attempting to stop ‘ora.gpnpd’ on ‘dbn01’ CRS-2677: Stop of ‘ora.drivers.acfs’ on ‘dbn01’ succeeded CRS-2677: Stop of ‘ora.gpnpd’ on ‘dbn01’ succeeded CRS-2793: Shutdown of Oracle High Availability Services-managed resources on ‘dbn01’ has completed CRS-4133: Oracle High Availability Services has been stopped.

To stop cluster resources of all nodes, run the following command:

[[email protected] ~]# /u01/app/11.2.0/grid/bin/crsctl stop cluster -all CRS-2673: Attempting to stop ‘ora.crsd’ on ‘dbn01’ CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.OCR.dg’ on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.registry.acfs’ on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.dbn.db’ on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.LISTENER.lsnr’ on ‘dbn01’ CRS-2677: Stop of ‘ora.LISTENER.lsnr’ on ‘dbn01’ succeeded CRS-2673: Attempting to stop ‘ora.dbn01.vip’ on ‘dbn01’ CRS-2677: Stop of ‘ora.registry.acfs’ on ‘dbn01’ succeeded CRS-2677: Stop of ‘ora.dbn.db’ on ‘dbn01’ succeeded CRS-2673: Attempting to stop ‘ora.DATA.dg’ on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.FRA.dg’ on ‘dbn01’ CRS-2677: Stop of ‘ora.dbn01.vip’ on ‘dbn01’ succeeded CRS-2677: Stop of ‘ora.DATA.dg’ on ‘dbn01’ succeeded CRS-2677: Stop of ‘ora.FRA.dg’ on ‘dbn01’ succeeded CRS-2673: Attempting to stop ‘ora.crsd’ on ‘dbn02’ CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on ‘dbn02’ CRS-2673: Attempting to stop ‘ora.oc4j’ on ‘dbn02’ CRS-2673: Attempting to stop ‘ora.LISTENER_SCAN1.lsnr’ on ‘dbn02’ CRS-2673: Attempting to stop ‘ora.cvu’ on ‘dbn02’ CRS-2673: Attempting to stop ‘ora.OCR.dg’ on ‘dbn02’ CRS-2673: Attempting to stop ‘ora.registry.acfs’ on ‘dbn02’ CRS-2673: Attempting to stop ‘ora.dbn.db’ on ‘dbn02’ CRS-2673: Attempting to stop ‘ora.LISTENER.lsnr’ on ‘dbn02’ CRS-2677: Stop of ‘ora.cvu’ on ‘dbn02’ succeeded CRS-2677: Stop of ‘ora.LISTENER_SCAN1.lsnr’ on ‘dbn02’ succeeded CRS-2673: Attempting to stop ‘ora.scan1.vip’ on ‘dbn02’ CRS-2677: Stop of ‘ora.LISTENER.lsnr’ on ‘dbn02’ succeeded CRS-2673: Attempting to stop ‘ora.dbn02.vip’ on ‘dbn02’ CRS-2677: Stop of ‘ora.registry.acfs’ on ‘dbn02’ succeeded CRS-2677: Stop of ‘ora.scan1.vip’ on ‘dbn02’ succeeded CRS-2677: Stop of ‘ora.dbn02.vip’ on ‘dbn02’ succeeded CRS-2677: Stop of ‘ora.dbn.db’ on ‘dbn02’ succeeded CRS-2673: Attempting to stop ‘ora.DATA.dg’ on ‘dbn02’ CRS-2673: Attempting to stop ‘ora.FRA.dg’ on ‘dbn02’ CRS-2677: Stop of ‘ora.DATA.dg’ on ‘dbn02’ succeeded CRS-2677: Stop of ‘ora.FRA.dg’ on ‘dbn02’ succeeded CRS-2677: Stop of ‘ora.oc4j’ on ‘dbn02’ succeeded CRS-2677: Stop of ‘ora.OCR.dg’ on ‘dbn01’ succeeded CRS-2673: Attempting to stop ‘ora.asm’ on ‘dbn01’ CRS-2677: Stop of ‘ora.asm’ on ‘dbn01’ succeeded CRS-2673: Attempting to stop ‘ora.ons’ on ‘dbn01’ CRS-2677: Stop of ‘ora.ons’ on ‘dbn01’ succeeded CRS-2673: Attempting to stop ‘ora.net1.network’ on ‘dbn01’ CRS-2677: Stop of ‘ora.net1.network’ on ‘dbn01’ succeeded CRS-2792: Shutdown of Cluster Ready Services-managed resources on ‘dbn01’ has completed CRS-2677: Stop of ‘ora.crsd’ on ‘dbn01’ succeeded CRS-2673: Attempting to stop ‘ora.ctssd’ on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.evmd’ on ‘dbn01’ CRS-2673: Attempting to stop ‘ora.asm’ on ‘dbn01’ CRS-2677: Stop of ‘ora.OCR.dg’ on ‘dbn02’ succeeded CRS-2673: Attempting to stop ‘ora.asm’ on ‘dbn02’ CRS-2677: Stop of ‘ora.asm’ on ‘dbn02’ succeeded CRS-2673: Attempting to stop ‘ora.ons’ on ‘dbn02’ CRS-2677: Stop of ‘ora.evmd’ on ‘dbn01’ succeeded CRS-2677: Stop of ‘ora.ons’ on ‘dbn02’ succeeded CRS-2673: Attempting to stop ‘ora.net1.network’ on ‘dbn02’ CRS-2677: Stop of ‘ora.net1.network’ on ‘dbn02’ succeeded CRS-2792: Shutdown of Cluster Ready Services-managed resources on ‘dbn02’ has completed CRS-2677: Stop of ‘ora.crsd’ on ‘dbn02’ succeeded CRS-2673: Attempting to stop ‘ora.ctssd’ on ‘dbn02’ CRS-2673: Attempting to stop ‘ora.evmd’ on ‘dbn02’ CRS-2673: Attempting to stop ‘ora.asm’ on ‘dbn02’ CRS-2677: Stop of ‘ora.evmd’ on ‘dbn02’ succeeded CRS-2677: Stop of ‘ora.asm’ on ‘dbn01’ succeeded CRS-2673: Attempting to stop ‘ora.cluster_interconnect.haip’ on ‘dbn01’ CRS-2677: Stop of ‘ora.cluster_interconnect.haip’ on ‘dbn01’ succeeded CRS-2677: Stop of ‘ora.asm’ on ‘dbn02’ succeeded CRS-2673: Attempting to stop ‘ora.cluster_interconnect.haip’ on ‘dbn02’ CRS-2677: Stop of ‘ora.ctssd’ on ‘dbn02’ succeeded CRS-2677: Stop of ‘ora.ctssd’ on ‘dbn01’ succeeded CRS-2673: Attempting to stop ‘ora.cssd’ on ‘dbn01’ CRS-2677: Stop of ‘ora.cssd’ on ‘dbn01’ succeeded CRS-2677: Stop of ‘ora.cluster_interconnect.haip’ on ‘dbn02’ succeeded CRS-2673: Attempting to stop ‘ora.cssd’ on ‘dbn02’ CRS-2677: Stop of ‘ora.cssd’ on ‘dbn02’ succeeded

crsctl start crs

Specify the -cssonly parameter to start CSSD, only.

Specify the -nocrs parameter to start Oracle Clusterware in exclusive mode without starting CRSD.

Starts Oracle Clusterware in exclusive mode with two options:

-wait | -waithas | -nowait

How to Stop Processes in an Existing Oracle RAC Database

Before you shut down any processes that are monitored by Oracle Enterprise Manager Cloud Control, set a blackout in Oracle Enterprise Manager Cloud Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime, rather than an unplanned system outage.

Shut down any processes in the Oracle home on each node that might be accessing a database, for example, the Oracle Enterprise Manager Cloud Control agent or an Oracle Net Services listener.

Shut down all Oracle RAC instances on all nodes. To shut down all Oracle RAC instances for a database, enter the following command, where db_name is the name of the database:

Stop all Oracle Clusterware node applications node applications and resources on all nodes. To stop node applications running on a node, enter the following command, where u01/app/grid/12.1.0 is the Grid home, and node is the name of the node where the applications run:

Shut down the Oracle Clusterware processes and the Oracle ASM instance on each node by entering the following command on all nodes as the root user:

# crsctl stop cluster

To stop Oracle Clusterware and Oracle ASM instances on all nodes in the cluster, you can enter a single command: crsctl stop cluster -all .

whats the difference between crsctl stop has and crsctl stop crs

Hi,

Can someone explain the difference between “crsctl stop has” and “crsctl stop crs”? both seem to stop all cluster in one node.

thanks

CRS-4013: This command is not supported in a single-node configuration.

Problem:

While start up crs, got below error.

$ crsctl start crs

CRS-4013: This command is not supported in a single-node configuration.

CRS-4000: Command Start failed, or completed with errors.

Solution:

In the standalone grid, there will not any crs. Only has component will be there.

$ ./crsctl start has

CRS-4123: Oracle High Availability Services has been started.

Starting and Stopping Grid Infrastructure on a Standalone GI Installation

This document explains how to start and stop an Oracle cluster. To start and stop Grid Infrastructure services for a standalone installation, there are slightly different commands. Using same commands as RAC to start and stop the GI resources would return errors as follows

[[email protected]~]$ /u01/app/11203/grid/bin/crsctl stop crs CRS-4013: This command is not supported in a single-node configuration. CRS-4000: Command Stop failed, or completed with errors. [[email protected] ~]$ /u01/app/11203/grid/bin/crsctl stop cluster -all CRS-4013: This command is not supported in a single-node configuration. CRS-4000: Command Stop failed, or completed with errors.

Let’s see how to start and stop the services. First, check status of currently running services

grid ~]$ crsctl stat res -t ——————————————————————————– NAME TARGET STATE SERVER STATE_DETAILS ——————————————————————————– Local Resources ——————————————————————————– ora.LISTENER.lsnr ONLINE ONLINE dbserver01 ora.ORADATA.dg ONLINE ONLINE dbserver01 ora.ORAFRA.dg ONLINE ONLINE dbserver01 ora.ORAREDO.dg ONLINE ONLINE dbserver01 ora.asm ONLINE ONLINE dbserver01 Started ora.ons OFFLINE OFFLINE dbserver01 ——————————————————————————– Cluster Resources ——————————————————————————– ora.myproddb.myservice.svc 1 ONLINE ONLINE dbserver01 ora.myproddb.db 1 ONLINE ONLINE dbserver01 Open ora.cssd 1 ONLINE ONLINE dbserver01 ora.diskmon 1 OFFLINE OFFLINE ora.evmd 1 ONLINE ONLINE dbserver01

Stopping Grid Infrastructure and HAS (High Availability Service)

To stop all services (including database services running from database home registered with this Grid Infrastructure), use following command. After stopping all resources, we will also stop High Availability Service (has).

grid ~]$ crsctl stop res -all CRS-2500: Cannot stop resource ‘ora.diskmon’ as it is not running CRS-2500: Cannot stop resource ‘ora.ons’ as it is not running CRS-2673: Attempting to stop ‘ora.evmd’ on ‘dbserver01’ CRS-2673: Attempting to stop ‘ora.ORADATA.dg’ on ‘dbserver01’ CRS-2673: Attempting to stop ‘ora.ORAFRA.dg’ on ‘dbserver01’ CRS-2673: Attempting to stop ‘ora.ORAREDO.dg’ on ‘dbserver01’ CRS-2673: Attempting to stop ‘ora.myproddb.myservice.svc’ on ‘dbserver01’ CRS-2673: Attempting to stop ‘ora.LISTENER.lsnr’ on ‘dbserver01’ CRS-2677: Stop of ‘ora.myproddb.myservice.svc’ on ‘dbserver01’ succeeded CRS-2673: Attempting to stop ‘ora.myproddb.db’ on ‘dbserver01’ CRS-2677: Stop of ‘ora.LISTENER.lsnr’ on ‘dbserver01’ succeeded CRS-2677: Stop of ‘ora.evmd’ on ‘dbserver01’ succeeded CRS-2677: Stop of ‘ora.myproddb.db’ on ‘dbserver01’ succeeded CRS-2677: Stop of ‘ora.ORADATA.dg’ on ‘dbserver01’ succeeded CRS-2677: Stop of ‘ora.ORAREDO.dg’ on ‘dbserver01’ succeeded CRS-2677: Stop of ‘ora.ORAFRA.dg’ on ‘dbserver01’ succeeded CRS-2673: Attempting to stop ‘ora.asm’ on ‘dbserver01’ CRS-2677: Stop of ‘ora.asm’ on ‘dbserver01’ succeeded CRS-2673: Attempting to stop ‘ora.cssd’ on ‘dbserver01’ CRS-2677: Stop of ‘ora.cssd’ on ‘dbserver01’ succeeded CRS-4000: Command Stop failed, or completed with errors.

grid ~]$ crsctl stop has CRS-4133: Oracle High Availability Services has been stopped.

Stopping Grid Infrastructure and HAS (High Availability Service)

grid ~]$ crsctl start has CRS-4123: Oracle High Availability Services has been started.

grid ~]$ crsctl start res -all CRS-5702: Resource ‘ora.evmd’ is already running on ‘dbserver01’ CRS-2501: Resource ‘ora.ons’ is disabled CRS-2672: Attempting to start ‘ora.LISTENER.lsnr’ on ‘dbserver01’ CRS-2672: Attempting to start ‘ora.cssd’ on ‘ dbserver 01’ CRS-2672: Attempting to start ‘ora.diskmon’ on ‘dbserver01’ CRS-2676: Start of ‘ora.diskmon’ on ‘dbserver01’ succeeded CRS-2676: Start of ‘ora.LISTENER.lsnr’ on ‘dbserver01’ succeeded CRS-2676: Start of ‘ora.cssd’ on ‘dbserver01’ succeeded CRS-2672: Attempting to start ‘ora.asm’ on ‘dbserver01’ CRS-2676: Start of ‘ora.asm’ on ‘dbserver01’ succeeded CRS-2672: Attempting to start ‘ora.ORADATA.dg’ on ‘dbserver01’ CRS-2672: Attempting to start ‘ora.ORAFRA.dg’ on ‘dbserver01’ CRS-2672: Attempting to start ‘ora.ORAREDO.dg’ on ‘dbserver01’ CRS-2676: Start of ‘ora.ORADATA.dg’ on ‘dbserver01’ succeeded CRS-2676: Start of ‘ora.ORAFRA.dg’ on ‘dbserver01’ succeeded CRS-2676: Start of ‘ora.ORAREDO.dg’ on ‘dbserver01’ succeeded CRS-2672: Attempting to start ‘ora.myproddb.db’ on ‘dbserver01’ CRS-2676: Start of ‘ora.myproddb.db’ on ‘dbserver01’ succeeded CRS-2672: Attempting to start ‘ora.myproddb.myservice.svc’ on ‘dbserver01’ CRS-2676: Start of ‘ora.myproddb.myservice.svc’ on ‘dbserver01’ succeeded

Stopping and Starting a single Grid Infrastructure Resource

A single resources, such as Listener can be stopped and started as follows.

키워드에 대한 정보 crs-4013 this command is not supported in a single-node configuration

다음은 Bing에서 crs-4013 this command is not supported in a single-node configuration 주제에 대한 검색 결과입니다. 필요한 경우 더 읽을 수 있습니다.

이 기사는 인터넷의 다양한 출처에서 편집되었습니다. 이 기사가 유용했기를 바랍니다. 이 기사가 유용하다고 생각되면 공유하십시오. 매우 감사합니다!

사람들이 주제에 대해 자주 검색하는 키워드 code: ‘MODULE_NOT_FOUND’ | Bug Report | NODE JS | Beginners

• code: 'MODULE_NOT_FOUND'
• Error: Cannot find module
• nodejs
• mongodb
• module not found
• reducing error
• no error
• clean code
• mern stack
• mern
• react

code: #’MODULE_NOT_FOUND’ #| #Bug #Report #| #NODE #JS #| #Beginners

YouTube에서 crs-4013 this command is not supported in a single-node configuration 주제의 다른 동영상 보기

주제에 대한 기사를 시청해 주셔서 감사합니다 code: ‘MODULE_NOT_FOUND’ | Bug Report | NODE JS | Beginners | crs-4013 this command is not supported in a single-node configuration, 이 기사가 유용하다고 생각되면 공유하십시오, 매우 감사합니다.

How do I turn off CRS in single node?

How do I start CRS on all nodes?

How do you stop a grid in Oracle?

What is Crsctl stop?