ORA-00845: MEMORY_TARGET not supported on this system

Are you receiving the "ORA-00845: MEMORY_TARGET not supported on this system" error while issuing the startup command for an Oracle database ?  This error message is actually misleading because even though the MEMORY_TARGET initialization parameter (automatic memory management) may be supported on the server, the server may not have enough memory to startup one more database instance. 

So please review the already started Oracle database instances and shutdown one or more less priority Oracle database instances.

Short-term solution

1) Login to the Oracle database server

2) ps  -ef    |   grep  -i   "pmon"   (To find the running database instance names)

3) Then set the environment of one of these running database instances.

4) sqlplus  /   as   sysdba

5) shutdown immediate;   (After getting approval that it is OK to shutdown the instance.)

6) exit;

7) Now set the environment of the database instance that you wish to startup.

8) sqlplus  /  as   sysdba

9) startup   (This time you should not receive the ORA-00845 error.)

10) exit

Long-term solution

A long term solution is to assign more memory to the database server so that you do not have to shutdown some database instances to startup other database instances.

beeline Error: Could not open client transport with JDBC Uri

Introduction

Are you receiving the Connection refused  error (or)  Error: Could not open client transport with JDBC Uri when you try to start the beeline command prompt as part of the Cloudera distribution for Apache Hadoop (CDH) ?

beeline –u jdbc:hive2://localhost:10000

Though the above syntax should work without any problem, this issue still exists in the Cloudera Quickstart VM 5.5 version.

Solution

Just put a  /  at the end of the syntax and the issue goes away. It is an easy solution.  So please try to start beeline with the beeline –u jdbc:hive2://localhost:10000/ syntax

Oracle R12 frmweb: error while loading shared libraries

Problem

Are you receiving the following errors while launching Oracle R12 forms session after an instance cloning exercise ? One of the reasons why this could happen is when you have a Linux root / file system that is 100% full with no free space available.

formsweb: Forms session <1> aborted: runtime process failed during startup with errors. frmweb: error while loading shared libraries: libdeb.so.0: cannot open shared object file: No such file or directory.

Solution

1) Source the applications environment file of the Oracle R12 instance. i.e, BASE DIRECTORY/apps/apps_st/appl/APPSINSTANCENAME_appserver.env

2) cd  BASE DIRECTORY/apps/tech_st/10.1.2/bin

3) ldd frmweb.  Notice the libdeb.so.0 => not found error.

4) Now run the relink all command.

5) One of the reasons why the relink command may fail is due to the lack of free space on the root / file system on Linux operating system. If that is the case, please delete unnecessary files or directories in the root / file system.

6) Now retry running the relink all command and it should complete successfully. 

7) Verify the  ldd frmweb command output again. Notice that it now links libdeb.so.0 successfully.

ldd frmweb | grep -i "libdeb.so.0"

        libdeb.so.0 => BASE DIRECTORY/apps/tech_st/10.1.2/lib/libdeb.so.0

8) Re-launch the Oracle R12 forms session and this time you should not receive any more errors.

Oracle Execution of GI Install script is failed on nodes

Introduction

Are you facing errors during running root.sh in one of the cluster nodes managed by Oracle VirtualBox while installing Oracle 12c R1 Grid Infrastructure software ?

Cause - Installer has failed to execute the specified script on one or more nodes. This might be because of exception occurred while executing the script on nodes.  Action - Review the log files '/u01/app/oraInventory/logs/installActions2016-04-07_11-26-02PM.log' and '/u01/app/12.1.0/grid/cfgtoollogs/crsconfig/rootcrs_<nodename>_<timestamp>.log' for further details.  More Details

Execution of GI Install script is successful on nodes : [oraracn1]  Execution of GI Install script is failed on nodes : [oraracn2]  Exception details  - PRCZ-2009 : Failed to execute command "/u01/app/12.1.0/grid/root.sh" as root within 3,600 seconds on nodes "oraracn2"

The command '/u01/app/12.1.0/grid/perl/bin/perl -I/u01/app/12.1.0/grid/perl/lib -I/u01/app/12.1.0/grid/crs/install /u01/app/12.1.0/grid/crs/install/rootcrs.pl -auto' execution failed

This issue is known to occur with a combination of VirtualBox 5.x version and AMD CPU  (Phenom X4, AM3 slot) in conjunction with Oracle 12c R1 Grid Infrastructure.

Solution

1) Uninstall Oracle VM VirtualBox software from Control Panel of your PC.

2) Then install Oracle VM VirtualBox 4.3.36. This old build of VirtualBox can be downloaded here.

3) Now perform the installation of Oracle 12c R1 Grid Infrastructure software and it should be completed successfully on all the nodes of the cluster.

Oracle may fix this issue in one of the future versions of the VirtualBox hypervisor software.

Sony Vaio - How to enable virtualization in BIOS

In Sony Vaio laptop perform the following steps to enable virtualization in BIOS. These steps have been tested in Windows 7 operating system.

1) Shutdown the laptop

2) Restart using the Assist button

3) Then before startup of the operating system press F2 button. 

4) The Bios menu will come up. 

5) Now go to Advanced tab and enable virtualization.