Shulou(Shulou.com)05/31 Report--

This article mainly explains the "crs_stat-t error can not find the command how to solve", the article explains the content is simple and clear, easy to learn and understand, the following please follow the editor's train of thought slowly in depth, together to study and learn "crs_stat-t error can not find the command how to solve" it!

Crs_stat-t reported an error and could not find the command: the user was wrong and did not go to the home directory to solve the problem 1:

[root@node2 ~] # find /-name crs_stat

/ u01/11.2.0/grid/bin/crs_stat

[root@node2 ~] # cd / u01/11.2.0/grid/bin/

[root@node2 bin] # crs_stat

NAME=ora.LISTENER.lsnr

TYPE=ora.listener.type

TARGET=ONLINE

STATE=ONLINE on node1

...

PS:

[root@node2 bin] # crs_stat

If not, try this one below.

[root@node2 bin] #. / crs_stat

The best way is to configure the environment variables directly under the corresponding user.

For example:

You can execute the command directly under the corresponding user.

For example:

[grid@node2 ~] $crs_stat

NAME=ora.LISTENER.lsnr

TYPE=ora.listener.type

TARGET=ONLINE

STATE=ONLINE on node1

NAME=ora.LISTENER_SCAN1.lsnr

TYPE=ora.scan_listener.type

TARGET=ONLINE

STATE=ONLINE on node1

Thank you for your reading, the above is the content of "crs_stat-t error can not find the command how to solve". After the study of this article, I believe you have a deeper understanding of how to solve this problem when you can not find the command in crs_stat-t. The specific use of the situation also needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.