Home PC Games Linux Windows Database Network Programming Server Mobile  
  Home \ Database \ ORA-00845: MEMORY_TARGET not supported on this system Problem     - 10 Best Swift Tutorial examples (Programming)

- Linux Learning --- disk partition / relational representation + mount (Linux)

- JSON Introduction and Usage Summary (Programming)

- FileZilla install on Ubuntu 14.10 (Linux)

- OGG-03510 Problem (Database)

- How to use the Docker Machine cluster deployment Swarm (Server)

- Oracle 11G R2 DataGuard structures (Database)

- Command line tool Tmux (Linux)

- 32-bit and 64-bit integer in PHP and MySQL range (Database)

- Oracle View index and use indexes Precautions (Database)

- Udev: Device Manager for Linux Fundamentals (Linux)

- Command-line based tools for better alternatives (Linux)

- SVN common commands (Linux)

- printf PHP string operations () built-in function usage (Programming)

- Thunderbird 24.4.2 has been released for use with PPA updates (Linux)

- Linux remote connectivity tools -OpenSSH (Linux)

- Windows 7 hard disk installation notes Debian (Linux)

- Oracle to start to solve the error ORA-27102 (Database)

- Save the database data files into Oracle Learning (Database)

- Ubuntu ADSL dial-up Internet access (Linux)

  ORA-00845: MEMORY_TARGET not supported on this system Problem
  Add Date : 2018-11-21      
  1, Oracle 11g archive log in again to start setting error

SQL> startup;
ORA-00845: MEMORY_TARGET not supported on this system
2, see Oracle's official explanation is:

Starting with Oracle Database 11g, the Automatic Memory Management feature requires more shared memory (/ dev / shm) and file descriptors. The size of the shared memory should be at least the greater of MEMORY_MAX_TARGET and MEMORY_TARGET for each Oracle instance on the computer. If MEMORY_MAX_TARGET or MEMORY_TARGET is set to a non zero value, and an incorrect size is assigned to the shared memory, it will result in an ORA-00845 error at startup.

That MEMORY_MAX_TARGET setting can not exceed the / dev / shm size parameter MEMORY_TARGET in oracle11g add automatic memory management, which can automatically adjust the SGA and PGA, this feature need to use / dev / shm shared file system, and requires / dev / shm must be greater than MEMORY_TARGET, if / dev / shm MEMORY_TARGET smaller than an error.

3. Solution

2 Modify place:
In the / etc / fstab inside, one modification back into a swap defaults, size = 11G, the second is to modify the back tmpfs defaults, size = 11G, modifying as follows

[Root @ testoracle1 oracle] # vim / etc / fstab

# / Etc / fstab
# Created by anaconda on Tue Aug 18 16:46:25 2015
# Accessible filesystems, by reference, are maintained under '/ dev / disk'
# See man pages fstab (5), findfs (8), mount (8) and / or blkid (8) for more info
/ Dev / mapper / vg_testoracle1-lv_root / ext4 defaults 1 1
UUID = e10af7be-cb8b-4454-965d-0c2275fe75b9 / boot ext4 defaults 1 2
/ Dev / mapper / vg_testoracle1-lv_swap swap swap defaults, size = 11G 0 0
tmpfs / dev / shm tmpfs defaults, size = 11G 0 0
devpts / dev / pts devpts gid = 5, mode = 620 0 0
sysfs / sys sysfs defaults 0 0
proc / proc proc defaults 0 0
After modification, you need to remount it, to take effect:

[Root @ testoracle1 oracle] # mount -o remount, size = 11G / dev / shm
[Root @ testoracle1 oracle] #
3 to restart the database, it is not being given the normal startup:

SQL> startup;
ORACLE instance started.

Total System Global Area 1.1358E + 10 bytes
Fixed Size 2216744 bytes
Variable Size 8925482200 bytes
Database Buffers 2415919104 bytes
Redo Buffers 13946880 bytes
Database mounted.
Database opened.
4, the standard prohibits archive mode:

SQL> alter system set log_archive_start = false scope = spfile; # disable self-archiving

SQL> shutdown immediate;
SQL> startup mount; # to restart the database to mount mode
SQL> alter database noarchivelog; # amend non-archive mode
SQL> alter database open; # playing data file
SQL> archive log list; # View mode again before archiving

SQL> alter database noarchivelog;
alter database noarchivelog
ERROR at line 1:
ORA-38774: can not disable media recovery - flashback database is enabled


Check whether to open flashback:

SQL> select flashback_on from v $ database;


Close to flashback features:

SQL> alter database flashback off;

Database altered.


SQL> alter database flashback off;

Database altered.
Then close the archive.

SQL> alter database noarchivelog;

Database altered.

SQL> archive log list;
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination / oracle / app / oracle / flash_recovery_area / archivelog
Oldest online log sequence 337
Current log sequence 339
- Dynamic programming Android (Programming)
- Number JavaScript type system (Programming)
- Linux shell script under the use of randomly generated passwords (Programming)
- HTTPS and SSH and use the difference between the way: Git User's Manual (Linux)
- Installation Yarock 1.1.4 Music Player in Ubuntu (Linux)
- C # C ++ Java interface type conversion (Programming)
- Linux System Getting Started Tutorial: How to update outdated version of Ubuntu (Linux)
- How to network to share files between Windows, MAC and Linux (Linux)
- CentOS 6.5 opens the Xmanager Remote Desktop login (Linux)
- Spark build standalone version cluster (Server)
- Linux delete duplicate files Artifact: dupeGuru (Linux)
- New features of Java 9 HTTP2 and REPL (Programming)
- Linux system security mechanisms to share (Linux)
- How to install and use the Snort in Ubuntu 15.04 (Linux)
- MariaDB database storage path modify configuration issues (Database)
- IP configuration under Linux (Linux)
- How to migrate MySQL to MariaDB under linux (Database)
- C ++ Replication Control: Assignment operators and destructors (Programming)
- Linux network security backdoor technology and advanced skill practice (Linux)
- Linux OOM killer mechanism (Linux)
  CopyRight 2002-2022 newfreesoft.com, All Rights Reserved.