Skip to main content

How to fix ORA-00845: MEMORY_TARGET not supported on this system

One day I get request from my friend such as his database crashed and after restart he could not start it up.
His database version is Oracle 11g R2.
I tried to start up database but it raised :

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

Hmmmmm, that`s new for me, never faced before.

Checked disk space

[root@localhost ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/cciss/c0d0p3     209G   27G  171G  14% /
/dev/cciss/c0d1p1     903G  265G  592G  31% /oradata
/dev/cciss/c0d0p1      99M   24M   71M  26% /boot
tmpfs                 3.9G     0  3.9G   0% /dev/shm
[root@localhost ~]#

Increased tmpfs size. To do that open fstab file via any editable program (gedit, vi etc)


[root@localhost ~]# vi /etc/fstab
...
tmpfs      /dev/shm      tmpfs   defaults,size=8G


(Some one decreased this value that is was reason)



[root@localhost ~]# more /etc/fstab 
LABEL=/                 /                       ext3    defaults        1 1
LABEL=/oradata          /oradata                ext3    defaults        1 2
LABEL=/boot1            /boot                   ext3    defaults        1 2
tmpfs                   /dev/shm                tmpfs   defaults,size=8G        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
LABEL=SW-cciss/c0d0p2   swap                    swap    defaults        0 0
/swapfile swap swap defaults 0 0


To make change effective immediately run:

[root@localhost ~]# mount -o remount /dev/shm

Check
[root@localhost ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/cciss/c0d0p3     209G   27G  171G  14% /
/dev/cciss/c0d1p1     903G  265G  592G  31% /oradata
/dev/cciss/c0d0p1      99M   24M   71M  26% /boot
tmpfs                 8.0G     0  8.0G   0% /dev/shm
[root@localhost ~]# 

Let`s start a database

[oracle@localhost dbs]$ sqlplus "/as sysdba"

SQL*Plus: Release 11.2.0.1.0 Production on Wed Nov 30 10:17:30 2011

Copyright (c) 1982, 2009, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup
ORACLE instance started.

Total System Global Area 5277921280 bytes
Fixed Size    2213096 bytes
Variable Size 4496296728 bytes
Database Buffers  738197504 bytes
Redo Buffers   41213952 bytes
Database mounted.
Database opened.
SQL> exit




Comments

Post a Comment

Popular posts from this blog

Fix ORA-01139: RESETLOGS option only valid after an incomplete database recovery

While shutting down my TEST database process was hanged. Then I had to use shutdown abort. But when I wanted to start database it did not open. SQL> select name from v$database; NAME --------- TEST SQL> shut abort; ORACLE instance shut down. SQL> startup mount ORACLE instance started. Total System Global Area 6597406720 bytes Fixed Size 2265664 bytes Variable Size 3204451776 bytes Database Buffers 3372220416 bytes Redo Buffers 18468864 bytes Database mounted. SQL> alter database open; alter database open * ERROR at line 1: ORA-03113: end-of-file on communication channel Process ID: 6552 Session ID: 191 Serial number: 3  What`s wrong?  SQL> alter database open resetlogs; ERROR:    ORA-03114: not connected to ORACLE    SQL> exit Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Pr...

Fix: ORA-13639: The current operation was interrupted because it timed out.

Sometimes SQL Tuning Advisor interrupts cause time limit took more than defined. You have to analyze it or increase value. Here you can see increasing of value. Example result of sql select                  execution_name, advisor_name,                  to_char(execution_start,'dd-mon-yy hh:mi:ss') execution_start,                  to_char(execution_end,'dd-mon-yy hh:mi:ss') execution_end, status,error_message from dba_advisor_executions where task_name = 'SYS_AUTO_SQL_TUNING_TASK' order by execution_start; Check value of TIME_LIMIT`s parameter : SQL> column parameter_value for A35 SQL> select parameter_name, parameter_value from dba_advisor_parameters where task_name = 'SYS_AUTO_SQL_TUNING_TASK' and parameter_name in ('TIME_LIMIT', 'DEFAULT_EXECUTION_TYP...

How to fix ORA-26040: Data block was loaded using the NOLOGGING option

Today I faced with new ORA error. After solving I want to share this experience with yours. So, today 5`th datafile of my database was corrupted (/u01/app/oracle/oradata/ulfet_db/example01.dbf). After recover via RMAN I saw strange error. RMAN> recover datafile 5 block 443; Starting recover at 24-MAR-13 using channel ORA_DISK_1 channel ORA_DISK_1: restoring block(s) channel ORA_DISK_1: specifying block(s) to restore from backup set restoring blocks of datafile 00005 channel ORA_DISK_1: reading from backup piece /u01/app/oracle/flash_recovery_area/ULFET_DB/backupset/2013_03_24/o1_mf_nnndf_TAG20130324T223233_8nykp220_.bkp channel ORA_DISK_1: piece handle=/u01/app/oracle/flash_recovery_area/ULFET_DB/backupset/2013_03_24/o1_mf_nnndf_TAG20130324T223233_8nykp220_.bkp tag=TAG20130324T223233 channel ORA_DISK_1: restored block(s) from backup piece 1 channel ORA_DISK_1: block restore complete, elapsed time: 00:00:03 starting media recovery media recovery complete, elapsed ti...