Friday 25 July 2014

/u01/app/oracle/product/11.2.0/db_1/bin/clsecho: No such file or directory





Error: /u01/app/oracle/product/11.2.0/db_1/bin/clsecho: No such file or directory

Reason: 
This error occurs when we perform commands on ASM prompt. This is not a major issue to worry. This error causes because of improper set up of ASM environment variables.

    [oracle@node1-rac1 ~]$ asmcmd
    Connected to an idle instance.
    sh: /u01/app/oracle/product/11.2.0/db_1/bin/clsecho: No such file or directory
    ASMCMD> ls
    Can't exec "/u01/app/oracle/product/11.2.0/db_1/bin/clsecho": No such file or directory at /u01/app/oracle/product/11.2.0/db_1/lib/asmcmdshare.pm line 493, <STDIN> line 1.
    Use of uninitialized value $buf in string ne at /u01/app/oracle/product/11.2.0/db_1/lib/asmcmdshare.pm line 497, <STDIN> line 1.
    ASMCMD>

To set the proper environment variables follow the below steps:

    [oracle@rac1 ~]$ cat /etc/oratab | grep ASM
    # a database or ASM Configuration Assistant while creating ASM instance.
    +ASM1:/u01/app/11.2.0/grid:N          # line added by Agent

Action: 
set the env variables as below
    [oracle@rac1 ~]$ . oraenv
    ORACLE_SID = [RAC1]?  +ASM1   ----> enter as +ASM1 here if it is your node-1, +ASM2 if it is node-2 instance
    The Oracle base remains unchanged with value /u01/app/oracle
    [oracle@rac1 ~]$ asmcmd
    ASMCMD>
    ASMCMD>
    ASMCMD> ls
    DATA/
    ASMCMD>

                Now the issue is solved. We can list and check files using basic unix commands like ls,cat spfile.ora.

Note: Don’t forget to perform this on all nodes as well.

ORA-600 [kwqitnmphe:ltbagi], [1], [0] reported in the alert log file.

ORA-00600 [kwqitnmphe:ltbagi] Cause: This issue arises in 12.1.0.2. The error occurs because there are still Historical Messages without...