Skip to main content

ORA-00845: MEMORY_TARGET not supported on this system

sql> startup

ORA-00845: MEMORY_TARGET not supported on this system

Reason:
/dev/shm  also known as tmpfs i.e. temporary file system which keeps all the file system in virtual memory to speed up several processes.

Solution:
Increase the size of /dev/shm

Check the size of /dev/shm
# df -h

tmpfs         512M   76K   512M  1%     /dev/shm

To increase the size

# mount -o remount,size=3G /dev/shm

Verify the size
# df -h

tmpfs       3G      1007M  2.1G   33%   /dev/shm

To make these changes permanent, edit your /etc/fstab file
# vi /etc/fstab

tmpfs  /dev/shm  tmpfs  defaults,size=3G  0 0

Update the new fstab file
# mount -a

Startup the oracle instance

SQL> startup
ORACLE instance started.

Total System Global Area  535662592 bytes
Fixed Size                  1337720 bytes
Variable Size             494929544 bytes
Database Buffers           33554432 bytes
Redo Buffers                5840896 bytes
Database mounted.
Database opened.

SQL>

You are good to go.




Comments

Popular posts from this blog

OBIEE 11g Error "Selected item is not of valid selection type" In Agent When Select Dashboard Page For Content

OBIEE 11g Error"Selected item is not of valid selection type" This error applies to OBIEE - version 11.1.1.7.0 and later . When you try to choose a dashboard page for delivery content in an agent, it constantly fails with the error message " Selected item is not of valid selection type ”.  Solution: This error may happen, when there is an added extra space after the end of the name of the dashboard page. For example, instead of "PAGE", it is "PAGE   "  It may happen with a space at the beginning of the name also. Removal of the extra space by renaming the dashboard page will correct the error.

Setting User Defined JVM Memory Arguments in JDeveloper 11g Integrated WebLogic Server

Setting User Defined JVM Memory Arguments in JDeveloper 11g Integrated WebLogic Server This guide explains how to set your own predefined JVM memory arguments for the JDeveloper WebLogic container at startup for the integrated WebLogic server.   This will help avoid java.lang.OutOfMemoryError s experienced on heavy java processes and also improve on the integrated JDeveloper WebLogic server’s performance overall. Steps Locate the file: setDomainEnv.cmd which should be at: [JDeveloper Working Directory]\jdeveloper\system.xxx.xx.xx\DefaultDomain\bin                                 i.             Note: [JDeveloper Working Directory] will be "C:\Documents and Settings\<username>\Application...

Oracle BI Scheduler Error: [nqSError:76015]

Oracle BI Scheduler Error: [nqSError:76015]. The active Oracle BI Scheduler instance in the cluster could not be determined This solution applies to Oracle Business Intelligence Server Enterprise Edition - Version 11.1.1.7 and later The above error appears when a user is unable to save and edit an iBOT/Agent job This is because the data source details are incorrect and not matching with the data connection from tnsnames.ora file To resolve the error, 1.        Log in to Enterprise Manager 2.        Navigate to coreapplication 3.        Open the Deployment tab and navigate to scheduler 4.        Lock and Edit configuration 5.        Copy connection details from tnsnames.ora file NB Don’t include the TNS alias, only copy the connection string after the equal (=) sign. Spaces are OK: For example: (DESCRIPTION=(ADDRES...