PRVF-7565 : Could Not Perform The Runlevel

Installing a patch this morning I get the following error;

Run Level – This is a prerequisite condition to test whether the system is running with proper run level. Details:

An internal error occurred within cluster verification framework The command executed was “/usr/bin/who -r”. The output from the command was “who: Cannot open /etc/inittab: Permission denied ”  – Cause: Cause Of Problem Not Available  – Action: User Action Not Available

PRVF-7565 : Could not perform the runlevel verification check on node “marmotac” PRVG-2043 : Command “/usr/bin/who -r” failed on node “saturn” and produced the following output: who: Cannot open /etc/inittab: Permission denied  – Cause:  Errors were encountered when trying to obtain the runlevel set on the system.  – Action:  Ensure that the command used to obtain the runlevel value ”who -r” can be run on the specified node and the file accessed by this command ”/var/run/utmp” has read access for the current user.

The problem is the /etc/inittab, This file have access only for root user. Grant read permission on other groups solve the problem.



OPatch Failed With Error Code 73

Today I was installing patches, and run the opatch gives me the following message;

Prerequisite check “CheckSystemSpace” failed.
Log file location: /cloudteldev/dev/server/product/12.1.0/dbhome_1/cfgtoollogs/opatch/opatch2015-09-25_13-29-32PM_1.log

OPatch failed with error code 73

The solution, of course, has been free space filesystem.



Legato Exit Code 268435458 When Perform Archive Backup

The control center sends me the next error, reported from Legato tool;

Exited with exit code: 268435458, completion severity: INFORMATION(10), completion status: unexpectedly exited(2)

This error occurs when an archive backup of a database is done. I must say that this database is in OpenVMS and the issue of logs is quite different regarding Unix/Linux or Windows platforms. In this case the best option is launch RMAN script manually to see if it is a problem of Oracle, Legato, the integration of both or Operating System.

When throwing error manually it is clearly seen. The problem is that few archives have been restored to clone this database on another machine, then them have been manually deleted. The obvious solution is to run a consistency command and validate what exits physically on the disk and so do ignore if it not physically exists. We can do from RMAN with the following command;

RMAN> crosscheck archivelog all;

In this case there is no danger of ignoring archives for which they are in the tape (in my case there are two different sets/pool of tapes with the same backup, in case one tape fails I have the other pool) so the problem is solved. The archives backup is working again without problem.


ORA-07217: sltln: environment variable cannot be evaluated

Today I am getting this error when a startup;

SQL> startup nomount
ORA-07217: sltln: environment variable cannot be evaluated.
ORA-07217: sltln: environment variable cannot be evaluated.
SQL> exit

The problem is that this environment is OpenVMS. And I have connected as follows;

$ sqlplus ‘/ as sysdba’

Everything works fine when I connect as follows;

$ sqlplus "/ as sysdba"
SQL*Plus: Release - Production on Thu Sep 17 21:06:51 2015
Copyright (c) 1982, 2005, Oracle.  All Rights Reserved.
Connected to an idle instance.
SQL> startup nomount
ORACLE instance started.
Total System Global Area 8690597888 bytes
Fixed Size                  2068376 bytes
Variable Size            7046434920 bytes
Database Buffers         1627389952 bytes
Redo Buffers               14704640 bytes

Things from operating system.


How To Remove The Enterprise Manager Database Control?

Oracle Enterprise Manager Database Control  is no longer used in 12c, so that a migration process to 12c drop the repository of Database Control. For this task Oracle includes the script /rdbms/admin/emremove.sql that performs the drop.

For the migration process it is necessary, but could be interesting in versions 11 or 10 to play or probe and after restoring the repository, tables, scheme, etc. Besides we want to do other tests.

Enjoy It.


What Is The Unix EPOCH?

The Unix EPOCH is the (or Unix time or POSIX time or Unix timestamp), is the number of seconds that have elapsed since January 1.

You can calculate it in MySQL with;

SELECT unix_timestamp(now())

On PL/SQL with;

SELECT (SYSDATE – TO_DATE(’01/01/1970 00:00:00′, ‘MM-DD-YYYY HH24:MI:SS’)) *
24 * 60 * 60 FROM DUAL

On SQL Server;

SELECT DATEDIFF(s, ‘1970-01-01 00:00:00’, GETUTCDATE())SELECT DATEDIFF(s, ‘1970-01-01 00:00:00’, GETUTCDATE())

On  Postgre;

SELECT extract(epoch FROM now());