Skip to main content

ORA-00845: MEMORY_TARGET not supported on this system

Issue:

While creating a database 12c using dbca the database creation GUI gives error message in a pop up window,
ORA-00845: MEMORY_TARGET not supported on this system from where you can ignore the error message and perform the solution mentioned below and retry the failed steps during installation.


The similar scenario also occur whenever you try to start your database then startup shows error message like below.

SQL> STARTUP
ORA-00845: MEMORY_TARGET not supported on this system 



Cause:

1)If the shared memory which is mapped to /dev/shm directory is less than the size of MEMORY_TARGET or MEMORY_MAX_TARGET.

2)If the shared memory is not mapped to /dev/shm directory.


Solution:

Make sure /dev/shm is properly mounted. You can see it by,
#df -h or #df -k command.


[root@testing shm]# df -kh
Filesystem            Size  Used Avail Use% Mounted on
shmfs                 5.0G  815M  4.3G  16% /dev/shm

We see here for /dev/shm we have assigned 5G memory. Now if you set MEMORY_TARGET more than 5G then above ORA-845 will arise. For example if you have MEMORY_TARGET or MEMORY_MAX_TARGET set to 10G then you can mount shared memory to 11g like below.

From root user, fire the following command:

mount -t tmpfs shmfs -o size=11g /dev/shm
In order to make the settings persistence so that it will affect after restarting machine add an entry in /etc/fstab similar to the following:

shmfs /dev/shm tmpfs size=11g 0

Comments

Popular posts from this blog

Node id does not exist for the current application server id

Issue: After completing cloning procedure, you generally may across the following issue. "Node id does not exist for the current application server id". Solution: First stop the application. Run adgendbc.sh script to configure apps tier dbc file with the correct id from the database instance. Start the application and test your issue. Location of script: 11i: $COMMON_TOP/admin/install/$CONTEXT_NAME R12: $INST_TOP/admin/install [appldev@erptest install]$ sh adgendbc.sh (Note: It will prompt you to give apps username and apps password.)

How to change EBS R12 database and application port number

On Database Tier 1. Logon as oracle database user and source environment for R12 RDBMS ORACLE_HOME 2. Start database instance for which you want to change R12 port 3. Backup contextfile 4. Change as below in contextfile         dbport  : Change database port from 1521 to 1541         db_ons_localport : 6300 to 6320         db_ons_remoteport : 6400 to 6420         cmanport : 1521 to 1541 5. Run adautocfg.sh On Apps Tier Change Application port from 8000 to 8020 1. Logon as application manager user and source environment for R12 2. Backup contextfile 3. Run adpreclone    $ perl ./adpreclone.pl appsTier 4. Run adcfgclone and choose new port pool    $ cd $COMMON_TOP/clone/bin    $ perl ./adcfgclone.pl appsTier 5. Check new application URL SQL> select home_url from icx_parameters; HOME_URL ----------...

Oracle R12 : You are trying to access a page that is no longer active

Login fails “You are trying to access a page that is no longer active.” The issue can be reproduced at will with the following steps: Issue : After cloning process the login page of Oracle E-Business Suite R12 show the above error. Solution :  For this you need to update the new hostname in the  icx_parameteres table 1.   SQL> SELECT SESSION_COOKIE_DOMAIN FROM icx_parameters; SESSION_COOKIE_DOMAIN --------------------- erp.local.com (This is hostname of Source Application Tier) 2. SQL>update icx_parameters set SESSION_COOKIE_DOMAIN = ‘target.local.com’; 1 row updated. SQL> commit; Commit complete. (This has changed the SESSION_COOKIE_DOMAIN of target application to target hostname.domain_name) 3. SQL> SELECT SESSION_COOKIE_DOMAIN FROM icx_parameters; SESSION_COOKIE_DOMAIN --------------------- target.local.com