Shulou(Shulou.com)05/31 Report--

This article mainly shows you "how to deal with ORA-00845 errors in the Oracle11g RAC environment", the content is easy to understand, clear, hope to help you solve your doubts, the following let the editor lead you to study and learn "how to deal with ORA-00845 errors in the Oracle11g RAC environment" this article.

Due to the power outage of the air conditioner in the computer room, the temperature in the computer room is too high, which leads to the automatic shutdown of the Oracle11G RAC database server of the two nodes. After starting the server, it is found that the database cannot be started, as shown below:

[oracle@DB-2 ~] $sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Wed Aug 2 10:35:31 2017

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

Connected to an idle instance.

SQL > startup

ORA-00845: MEMORY_TARGET not supported on this system

SQL > exit

The reason is that the initialization parameter MEMORY_TARGET or MEMORY_MAX_TARGET cannot be larger than the shared memory (/ dev/shm). In order to solve this problem, it is necessary to adjust the Oracle initialization parameter without increasing / dev/shm.

The parameter files related to the original parameter file of Oracle are as follows:

Orcl2.memory_max_target=68719476736

Orcl1.memory_max_target=68719476736

* .memory_target=30558650368

Orcl2.memory_target=68719476736

Orcl1.memory_target=6871947673

The shared memory (/ dev/shm) parameters of the operating system are as follows:

[oracle@DB-1 shm] $cat / etc/fstab | grep tmpfs

Tmpfs / dev/shm tmpfs defaults,size=131072M 0 0

Modify the size of the two nodes to 64G through the vi / etc/fstab command, as follows:

Tmpfs / dev/shm tmpfs defaults,size=64G 0 0

[oracle@CRXJ-DB-1] $df-h

Filesystem Size Used Avail Use% Mounted on

/ dev/mapper/vg_crxjdb1-LogVol02

2.3T 1.3T 882G 60% /

Tmpfs 64G 34G 30G 54% / dev/shm

/ dev/sda1 194M 33m 152m 18% / boot

/ dev/mapper/vg_crxjdb1-LogVol01

9.9G 151m 9.2G 2% / tmp

Try to start the database again or report an ORA-00845 error, so edit and regenerate the spfile after exporting the initialization parameter file spfile to pfile as follows:

[oracle@DB-1 ~] $sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Wed Aug 2 10:36:33 2017

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

Connected to an idle instance.

SQL > create spfile from pfile='/home/oracle/pfile_yu.ora'

File created.

Elapsed: 00:00:00.21

The editing content is as follows:

Orcl2.memory_max_target=64424509440

Orcl1.memory_max_target=64424509440

* .memory_target=64424509440

Orcl2.memory_target=64424509440

Orcl1.memory_target=64424509440

Regenerate the spfile and start the database:

SQL > create spfile from pfile='/home/oracle/pfile_yu.ora'

File created.

Elapsed: 00:00:00.18

SQL > exit

Disconnected

[oracle@DB-1 ~] $sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Wed Aug 2 10:40:30 2017

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

Connected to an idle instance.

SQL > startup

ORACLE instance started.

Total System Global Area 6.4137E+10 bytes

Fixed Size 2219552 bytes

Variable Size 3.8118E+10 bytes

Database Buffers 2.5770E+10 bytes

Redo Buffers 247029760 bytes

Database mounted.

Database opened.

SQL >

The database started successfully.

A similar operation is carried out on another node, the databases of both nodes are started and running normally, and the application can be accessed normally.

Note: after the node has completed spfile in its lifetime, an attempt was made to start the database on Node 2, but an error was reported:

[oracle@DB-2 ~] $sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Wed Aug 2 10:35:31 2017

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

Connected to an idle instance.

SQL > startup

ORA-00845: MEMORY_TARGET not supported on this system

View operating system information:

[oracle@DB-2 ~] $df-h | grep shm

Tmpfs 64G 397M 63G 1% / dev/shm

[oracle@DB-2 ~] $sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Wed Aug 2 10:46:28 2017

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

Connected to an idle instance.

SQL > create pfile='/home/oracle/pfile_yu.ora' from spfile

Create pfile='/home/oracle/pfile_yu.ora' from spfile

*

ERROR at line 1:

ORA-01565: error in identifying file'? / dbs/spfile@.ora'

ORA-27037: unable to obtain file status

Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

For the above problems, copy the parameter file from the node and generate spfile directly.

[oracle@DB-1 ~] $scp pfile_yu.ora DB-2:/home/oracle/pfile_yu.ora 100% 1929 1.9KB/s 00:00

[oracle@DB-2 ~] $sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Wed Aug 2 10:54:48 2017

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

Connected to an idle instance.

SQL > create spfile from pfile='/home/oracle/pfile_yu.ora'

File created.

SQL > startup

ORACLE instance started.

Total System Global Area 6.4137E+10 bytes

Fixed Size 2219552 bytes

Variable Size 3.3554E+10 bytes

Database Buffers 3.0333E+10 bytes

Redo Buffers 247029760 bytes

Database mounted.

Database opened.

SQL > exit

The above is all the contents of the article "how to deal with ORA-00845 errors in Oracle11g RAC". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.