Home » Server Options » Data Guard » Looks like redo logs are being applied but seeing errors in logs
Looks like redo logs are being applied but seeing errors in logs [message #275789] Mon, 22 October 2007 12:49 Go to next message
ShaV
Messages: 20
Registered: July 2007
Junior Member
Hi everybody,

We're at ORACLE 9.2.0.7.0

Edit: Running on Solaris 8. (Sorry forgot to add this originally - I use SOLARIS so often I start to assume everybody else does as well)

I've been working to set up a physical standby database and everything appears to be working correctly. The primary is sending logs to the standby and they seem to be getting applied. However I'm seeing some strange errors in both the alert logs and subsequent trace files.

In the alert logs I see information such as:

Mon Oct 22 13:47:37 2007
Media Recovery Log /dbs/OraHome92/oradata/IAC/archive/stdby_1_19527.dbf
Media Recovery Waiting for thread 1 seq# 19528
Mon Oct 22 13:51:59 2007
Restarting dead background process QMN0
QMN0 started with pid=14
Mon Oct 22 13:58:03 2007
Restarting dead background process QMN0
QMN0 started with pid=14


When I check the trc files being created at about the same times I see:

/oracle/OraHome92/admin/IAC/bdump/iac_qmn0_19918.trc
Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
With the Partitioning, Oracle Label Security, OLAP and Oracle Data Mining options
JServer Release 9.2.0.7.0 - Production
ORACLE_HOME = /oracle/OraHome92
System name:	SunOS
Node name:	cgo-drtcas
Release:	5.8
Version:	Generic_117350-38
Machine:	sun4u
Instance name: IAC
Redo thread mounted by this instance: 1
Oracle process number: 14
Unix process pid: 19918, image: oracle@cgo-drtcas (QMN0)

*** 2007-10-22 14:03:03.660
*** SESSION ID:(11.607) 2007-10-22 14:03:03.660
SGA initialization / DB open not complete even after 5 minutes, QMN0exiting
error 604 detected in background process
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-00604: error occurred at recursive SQL level 1
ORA-01219: database not open: queries allowed on fixed tables/views only


Some initial investigation seemed to indicate that this is being caused by the fact that my "aq_tm_processes" parameter is set to "1" on the standby and that the error I'm seeing is not really causing any problems (and that the redo information is indeed being applied to the standby: ie: Nothing to worry about). Can anybody here confirm that for me or share some insight?

[Updated on: Mon, 22 October 2007 15:11]

Report message to a moderator

Re: Looks like redo logs are being applied but seeing errors in logs [message #275817 is a reply to message #275789] Mon, 22 October 2007 16:08 Go to previous messageGo to next message
ShaV
Messages: 20
Registered: July 2007
Junior Member
I've cancelled the standby recovery and opened in read only mode as shown in the Data Guard manual. I can confirm that updates made on the primary are indeed being applied to the standby.

So I guess at this point it's just the error messages that I'm concerned about.
Re: Looks like redo logs are being applied but seeing errors in logs [message #276014 is a reply to message #275817] Tue, 23 October 2007 12:20 Go to previous messageGo to next message
DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland
Senior Member
ORA-00447:	fatal error in background process
Cause:	One of the background processes died unexpectedly.
Action:	Warm start the system.
Re: Looks like redo logs are being applied but seeing errors in logs [message #276039 is a reply to message #276014] Tue, 23 October 2007 13:33 Go to previous message
ShaV
Messages: 20
Registered: July 2007
Junior Member
DreamzZ wrote on Tue, 23 October 2007 13:20

ORA-00447:	fatal error in background process
Cause:	One of the background processes died unexpectedly.
Action:	Warm start the system.



Warm start the system meaning the server? Or ORACLE?

This problem only happens when the database is in managed standby recovery mode. From the trc file error it seems that QMON is trying to run some kind of query against the database: "ORA-01219: database not open: queries allowed on fixed tables/views only". So I guess what I'm suspecting is that QMON isn't suppossed o be running at all on a standby database but am looking for confirmation.

I've found the below information on another site:

Getting 'Restarting dead background process QMN0' on Alert Log File
If you get many of this messages, just perform the following:
alter system set aq_tm_processes=0 scope=both;

http://www.pafumi.net/Standby_Concepts_Configuration.html

[Updated on: Tue, 23 October 2007 13:43]

Report message to a moderator

Previous Topic: log miner session not started
Next Topic: REDO log in STANDBY database
Goto Forum:
  


Current Time: Thu Dec 08 02:37:23 CST 2016

Total time taken to generate the page: 0.06761 seconds