Oracle instance has been activated, but an Oracle instance resource has entered Warning.
[Case 1]
An Oracle instance resource enters Warning when
The Oracle SYSTEM user password is not registered in PRIMECLUSTER Wizard for Oracle
The Oracle SYSTEM user password is registered in PRIMECLUSTER Wizard for Oracle, but it is incorrect
The correct Oracle SYSTEM user password is registered in PRIMECLUSTER Wizard for Oracle, but it is disabled
If ORA-01017 is output to syslog, you can determine the cause of this problem.
Register the correct SYSTEM user password again. Refer to "3.3 Oracle SYSTEM user Password Change ".
[Case 2]
An Oracle instance resource enters Warning when the Oracle SYSTEM user account is locked, so you are not allowed to connect to Oracle instance.
If ORA-28000 is output to syslog, you can determine the cause of this problem.
You can also check the SYSTEM user account by referring to the following SQL statement.
If the "account_status" column indicates "LOCKED(TIMED)" or "LOCKED", you can determine the cause of this problem.
# su - <Oracle user> $ sqlplus /nolog SQL> connect / as sysdba SQL> select username, account_status from dba_users;
Access Oracle instance using sysdba privileges then release account locking of the SYSTEM user.
# su - <Oracle user> $ sqlplus /nolog SQL> connect / as sysdba SQL> alter user system account unlock;
If ORA-01017 is output to syslog as well as ORA-28000, an incorrect password might have been registered. In this case, correct the SYSTEM user password. Refer to "3.3 Oracle SYSTEM user Password Change ". Then, release account locking using the procedure above.
[Case 3]
An Oracle instance resource enters Warning when instance monitoring is discontinued.
Check the monitoring status by executing "clorainfo -m" command. Refer to "4.6 clorainfo - Display Resource Configuration and Monitoring Status".
If instance monitoring has been discontinued, check if the Oracle instance has been activated with the OPEN status then restart monitoring. Refer to "4.2 hvoraenable - Restart Monitoring Resources".
[Case 4]
In Oracle instance monitoring, an Oracle instance resource enters Warning if there is no reply from SQL statement(e.g. INSERT, UPDATE, etc.) within a specified time, but you can access Oracle instance, and the instance indicates OPEN.
Take corrective action on Oracle.
In Oracle instance monitoring of PRIMECLUSTER Wizard for Oracle, if there is no reply from Oracle instance within a specified time, monitoring timeout will be considered and the following error message will also be output to syslog:
ERROR: 0226: Watch Timeout occurred
At the first monitoring timeout, the resource will only enter Warning, however, if it occurs twice in a row, a resource failure will be determined.
[Case 5]
In Oracle instance monitoring, an Oracle instance resource enters Warning if you cannot access Oracle instance because of a max session error or max process error.
If ORA-00018 or ORA-00020 is output to syslog, you can determine the cause of this problem.
For the maximum number of sessions that are set in the Oracle SESSIONS parameter, or the maximum number of processes that are set in the PROCESSES parameter, estimate enough values considering monitoring sessions for PRIMECLUSTER Wizard for Oracle.
[Case 6]
An Oracle instance resource enters Warning when the SYSTEM user's password has expired, so Oracle instance connection is not allowed.
If ORA-28001 is output to syslog, you can determine the cause of this problem.
You can also check it by referring to the following SQL statement
If the ORA-28001 error message appears, you can determine the cause of this problem.
# su - <Oracle user>
$ sqlplus /nolog
SQL> connect system/password
ERROR:
ORA-28001: the password has expired
Changing password for system
New password:In this case, change the SYSTEM user's password. After that, register the password with "clorapass" command. Refer to "3.3 Oracle SYSTEM user Password Change ".
See
For details refer to the Oracle Database manual.