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

Rman encryption and other techniques

Today I will demonstrate Recovery Manager features, especially encryption and some other techniques. First of all let me note about RMAN backup encryption. Staring from Oracle 10g RMAN now creates encrypted backups that cannot be restored by unauthorized people. There are 3 modes of backup encryption: * Transparent encryption * Password encryption * Dual-mode encryption using either transparent or password encryption All RMAN backups are not encrypted but you can encrypt any RMAN backup in the form of a backup set. In this tutorial I will show you how to configure Password encryption. Let`s finish talking and start to demonstrate. check parameters with "SHOW ALL" command, by default encryption is OFF RMAN> show all; RMAN configuration parameters are: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTR...

ORA-03206: maximum file size of (5242880) blocks in AUTOEXTEND clause is out of range

Today when I want to change max size of datafile I got strange error. ALTER DATABASE DATAFILE '/u01/app/oracle/oradata/MYDB/users01.dbf' AUTOEXTEND ON NEXT 1280K MAXSIZE 32GB ORA-03206: maximum file size of (5242880) blocks in AUTOEXTEND clause is out of range Here is reason: The maximum file size for an autoextendable file has exceeded the maximum number of blocks allowed. After research internet I found that instead of using 32GB we can use 32767M. (same values but in MB). Or you may use 31GB too. ALTER DATABASE DATAFILE '/u01/app/oracle/oradata/MYDB/users01.dbf' AUTOEXTEND ON NEXT 1280K MAXSIZE 32767M;

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...