Re: background process LGWR did not start
If rebooting is not an option then use the power off' switch. Mladen - Original Message - To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] Sent: Saturday, December 06, 2003 10:49 PM Maybe so. I've been in this same situation before where several business critical databases are on a single server. Rebooting was simply not an option. Isolate which memory segments to remove, remove them, restart the database. Jared On Fri, 2003-12-05 at 10:09, Mladen Gogala wrote: No, but in this case, it's exactly what they did. Good, old ctrlaltdel saved the day. I just thought I might suggest it. After all, they did have an oracle version of BSOD. On 12/05/2003 12:59:25 PM, Jared Still wrote: Rebooting is not always an option. On Fri, 2003-12-05 at 09:04, Mladen Gogala wrote: I can almost guarantee that the issue will go away if you reboot the machine. I cannot fathom how would shared memory segments survive reboot. On 12/05/2003 11:49:24 AM, [EMAIL PROTECTED] wrote: In regards to Bambi's comments about having a single instance on the server, this situation gets more complex if you have several instances on a server. There's also the possibility that the instance(s) shared memory is in more than one segment. You can use ipcs and oradebug to decipher which memory segments belong to which instance. Google for ipcs and oradebug, several helpful references showed up when I tried it. HTH Jared Bellow, Bambi [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 12/05/2003 08:34 AM Please respond to ORACLE-L To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] cc: Subject:RE: background process LGWR did not start Hi John! When I've run into this problem it was because there was a memory segment being forced open. If you have the same issue, I can hep. First, assuming that you're on Unix (if you're not, please ignore the rest of this email and just have a lovely day), and that your database is down (otherwise, if you wanted to do a shutdown abort, that wouldn't be such a bad thing), you can do an ipcs -mA If that was the only instance on your box, the rest is pretty easy, cuz the offending segment is the only one owned by oracle in the list. If it wasn't, and there are other oracle segments on the box, you have to find out which one is your guy. The memory segments associated with a particular instance should have very similar (but not exactly the same) CTIMEs. If there is one way out of whack, that's your guy. Now, this is where my memory gets a little fuzzy (age, doncha know?)... if the instances started up at nearly exactly the same time for some reason, you are looking for a 0 in the insert hem and haw segsz(?) column (anybody remember fersher on this one?). By now, you should know which memory segment to kill. To kill the offending memory segment, do an ipcrm -m segment on it. You, of course, want to be exceedingly careful here, and just assume that all the usual disclaimers apply. If you kill the wrong segment, your other database is not going to be very happy about it. But assuming you killed the right segment, your database with the LGWR problem should be well and truly down. Bring 'er on up and the LGWR process should come up just fine. Bambi. -Original Message- Sent: Thursday, December 04, 2003 8:34 AM To: Multiple recipients of list ORACLE-L Anyone know what might be causing this error? Oracle 8.1.7 on Solaris. background process LGWR did not start -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: John Dunn INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Bellow, Bambi INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services
Re: background process LGWR did not start
Yeah, that's helpful. Are you speaking for Mladen now? Jared On Sun, 2003-12-07 at 03:49, Yechiel Adar wrote: If rebooting is not an option then use the power off' switch. Mladen - Original Message - To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] Sent: Saturday, December 06, 2003 10:49 PM Maybe so. I've been in this same situation before where several business critical databases are on a single server. Rebooting was simply not an option. Isolate which memory segments to remove, remove them, restart the database. Jared On Fri, 2003-12-05 at 10:09, Mladen Gogala wrote: No, but in this case, it's exactly what they did. Good, old ctrlaltdel saved the day. I just thought I might suggest it. After all, they did have an oracle version of BSOD. On 12/05/2003 12:59:25 PM, Jared Still wrote: Rebooting is not always an option. On Fri, 2003-12-05 at 09:04, Mladen Gogala wrote: I can almost guarantee that the issue will go away if you reboot the machine. I cannot fathom how would shared memory segments survive reboot. On 12/05/2003 11:49:24 AM, [EMAIL PROTECTED] wrote: In regards to Bambi's comments about having a single instance on the server, this situation gets more complex if you have several instances on a server. There's also the possibility that the instance(s) shared memory is in more than one segment. You can use ipcs and oradebug to decipher which memory segments belong to which instance. Google for ipcs and oradebug, several helpful references showed up when I tried it. HTH Jared Bellow, Bambi [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 12/05/2003 08:34 AM Please respond to ORACLE-L To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] cc: Subject:RE: background process LGWR did not start Hi John! When I've run into this problem it was because there was a memory segment being forced open. If you have the same issue, I can hep. First, assuming that you're on Unix (if you're not, please ignore the rest of this email and just have a lovely day), and that your database is down (otherwise, if you wanted to do a shutdown abort, that wouldn't be such a bad thing), you can do an ipcs -mA If that was the only instance on your box, the rest is pretty easy, cuz the offending segment is the only one owned by oracle in the list. If it wasn't, and there are other oracle segments on the box, you have to find out which one is your guy. The memory segments associated with a particular instance should have very similar (but not exactly the same) CTIMEs. If there is one way out of whack, that's your guy. Now, this is where my memory gets a little fuzzy (age, doncha know?)... if the instances started up at nearly exactly the same time for some reason, you are looking for a 0 in the insert hem and haw segsz(?) column (anybody remember fersher on this one?). By now, you should know which memory segment to kill. To kill the offending memory segment, do an ipcrm -m segment on it. You, of course, want to be exceedingly careful here, and just assume that all the usual disclaimers apply. If you kill the wrong segment, your other database is not going to be very happy about it. But assuming you killed the right segment, your database with the LGWR problem should be well and truly down. Bring 'er on up and the LGWR process should come up just fine. Bambi. -Original Message- Sent: Thursday, December 04, 2003 8:34 AM To: Multiple recipients of list ORACLE-L Anyone know what might be causing this error? Oracle 8.1.7 on Solaris. background process LGWR did not start -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: John Dunn INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http
Re: background process LGWR did not start
Maybe so. I've been in this same situation before where several business critical databases are on a single server. Rebooting was simply not an option. Isolate which memory segments to remove, remove them, restart the database. Jared On Fri, 2003-12-05 at 10:09, Mladen Gogala wrote: No, but in this case, it's exactly what they did. Good, old ctrlaltdel saved the day. I just thought I might suggest it. After all, they did have an oracle version of BSOD. On 12/05/2003 12:59:25 PM, Jared Still wrote: Rebooting is not always an option. On Fri, 2003-12-05 at 09:04, Mladen Gogala wrote: I can almost guarantee that the issue will go away if you reboot the machine. I cannot fathom how would shared memory segments survive reboot. On 12/05/2003 11:49:24 AM, [EMAIL PROTECTED] wrote: In regards to Bambi's comments about having a single instance on the server, this situation gets more complex if you have several instances on a server. There's also the possibility that the instance(s) shared memory is in more than one segment. You can use ipcs and oradebug to decipher which memory segments belong to which instance. Google for ipcs and oradebug, several helpful references showed up when I tried it. HTH Jared Bellow, Bambi [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 12/05/2003 08:34 AM Please respond to ORACLE-L To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] cc: Subject:RE: background process LGWR did not start Hi John! When I've run into this problem it was because there was a memory segment being forced open. If you have the same issue, I can hep. First, assuming that you're on Unix (if you're not, please ignore the rest of this email and just have a lovely day), and that your database is down (otherwise, if you wanted to do a shutdown abort, that wouldn't be such a bad thing), you can do an ipcs -mA If that was the only instance on your box, the rest is pretty easy, cuz the offending segment is the only one owned by oracle in the list. If it wasn't, and there are other oracle segments on the box, you have to find out which one is your guy. The memory segments associated with a particular instance should have very similar (but not exactly the same) CTIMEs. If there is one way out of whack, that's your guy. Now, this is where my memory gets a little fuzzy (age, doncha know?)... if the instances started up at nearly exactly the same time for some reason, you are looking for a 0 in the insert hem and haw segsz(?) column (anybody remember fersher on this one?). By now, you should know which memory segment to kill. To kill the offending memory segment, do an ipcrm -m segment on it. You, of course, want to be exceedingly careful here, and just assume that all the usual disclaimers apply. If you kill the wrong segment, your other database is not going to be very happy about it. But assuming you killed the right segment, your database with the LGWR problem should be well and truly down. Bring 'er on up and the LGWR process should come up just fine. Bambi. -Original Message- Sent: Thursday, December 04, 2003 8:34 AM To: Multiple recipients of list ORACLE-L Anyone know what might be causing this error? Oracle 8.1.7 on Solaris. background process LGWR did not start -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: John Dunn INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Bellow, Bambi INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want
RE: background process LGWR did not start
Is it possible there are stuck memory segments (using ipcs -m when instance is shutdown) ?? Any other errors in alert log, etc ? - Babette -Original Message- Sent: 2003-12-04 9:34 AM To: Multiple recipients of list ORACLE-L Anyone know what might be causing this error? Oracle 8.1.7 on Solaris. background process LGWR did not start -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: John Dunn INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: [EMAIL PROTECTED] INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
RE: background process LGWR did not start
Hi John! When I've run into this problem it was because there was a memory segment being forced open. If you have the same issue, I can hep. First, assuming that you're on Unix (if you're not, please ignore the rest of this email and just have a lovely day), and that your database is down (otherwise, if you wanted to do a shutdown abort, that wouldn't be such a bad thing), you can do an ipcs -mA If that was the only instance on your box, the rest is pretty easy, cuz the offending segment is the only one owned by oracle in the list. If it wasn't, and there are other oracle segments on the box, you have to find out which one is your guy. The memory segments associated with a particular instance should have very similar (but not exactly the same) CTIMEs. If there is one way out of whack, that's your guy. Now, this is where my memory gets a little fuzzy (age, doncha know?)... if the instances started up at nearly exactly the same time for some reason, you are looking for a 0 in the insert hem and haw segsz(?) column (anybody remember fersher on this one?). By now, you should know which memory segment to kill. To kill the offending memory segment, do an ipcrm -m segment on it. You, of course, want to be exceedingly careful here, and just assume that all the usual disclaimers apply. If you kill the wrong segment, your other database is not going to be very happy about it. But assuming you killed the right segment, your database with the LGWR problem should be well and truly down. Bring 'er on up and the LGWR process should come up just fine. Bambi. -Original Message- Sent: Thursday, December 04, 2003 8:34 AM To: Multiple recipients of list ORACLE-L Anyone know what might be causing this error? Oracle 8.1.7 on Solaris. background process LGWR did not start -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: John Dunn INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Bellow, Bambi INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
RE: background process LGWR did not start
In regards to Bambi's comments about having a single instance on the server, this situation gets more complex if you have several instances on a server. There's also the possibility that the instance(s) shared memory is in more than one segment. You can use ipcs and oradebug to decipher which memory segments belong to which instance. Google for ipcs and oradebug, several helpful references showed up when I tried it. HTH Jared Bellow, Bambi [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 12/05/2003 08:34 AM Please respond to ORACLE-L To:Multiple recipients of list ORACLE-L [EMAIL PROTECTED] cc: Subject:RE: background process LGWR did not start Hi John! When I've run into this problem it was because there was a memory segment being forced open. If you have the same issue, I can hep. First, assuming that you're on Unix (if you're not, please ignore the rest of this email and just have a lovely day), and that your database is down (otherwise, if you wanted to do a shutdown abort, that wouldn't be such a bad thing), you can do an ipcs -mA If that was the only instance on your box, the rest is pretty easy, cuz the offending segment is the only one owned by oracle in the list. If it wasn't, and there are other oracle segments on the box, you have to find out which one is your guy. The memory segments associated with a particular instance should have very similar (but not exactly the same) CTIMEs. If there is one way out of whack, that's your guy. Now, this is where my memory gets a little fuzzy (age, doncha know?)... if the instances started up at nearly exactly the same time for some reason, you are looking for a 0 in the insert hem and haw segsz(?) column (anybody remember fersher on this one?). By now, you should know which memory segment to kill. To kill the offending memory segment, do an ipcrm -m segment on it. You, of course, want to be exceedingly careful here, and just assume that all the usual disclaimers apply. If you kill the wrong segment, your other database is not going to be very happy about it. But assuming you killed the right segment, your database with the LGWR problem should be well and truly down. Bring 'er on up and the LGWR process should come up just fine. Bambi. -Original Message- Sent: Thursday, December 04, 2003 8:34 AM To: Multiple recipients of list ORACLE-L Anyone know what might be causing this error? Oracle 8.1.7 on Solaris. background process LGWR did not start -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: John Dunn INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Bellow, Bambi INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
Re: background process LGWR did not start
I can almost guarantee that the issue will go away if you reboot the machine. I cannot fathom how would shared memory segments survive reboot. On 12/05/2003 11:49:24 AM, [EMAIL PROTECTED] wrote: In regards to Bambi's comments about having a single instance on the server, this situation gets more complex if you have several instances on a server. There's also the possibility that the instance(s) shared memory is in more than one segment. You can use ipcs and oradebug to decipher which memory segments belong to which instance. Google for ipcs and oradebug, several helpful references showed up when I tried it. HTH Jared Bellow, Bambi [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 12/05/2003 08:34 AM Please respond to ORACLE-L To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] cc: Subject:RE: background process LGWR did not start Hi John! When I've run into this problem it was because there was a memory segment being forced open. If you have the same issue, I can hep. First, assuming that you're on Unix (if you're not, please ignore the rest of this email and just have a lovely day), and that your database is down (otherwise, if you wanted to do a shutdown abort, that wouldn't be such a bad thing), you can do an ipcs -mA If that was the only instance on your box, the rest is pretty easy, cuz the offending segment is the only one owned by oracle in the list. If it wasn't, and there are other oracle segments on the box, you have to find out which one is your guy. The memory segments associated with a particular instance should have very similar (but not exactly the same) CTIMEs. If there is one way out of whack, that's your guy. Now, this is where my memory gets a little fuzzy (age, doncha know?)... if the instances started up at nearly exactly the same time for some reason, you are looking for a 0 in the insert hem and haw segsz(?) column (anybody remember fersher on this one?). By now, you should know which memory segment to kill. To kill the offending memory segment, do an ipcrm -m segment on it. You, of course, want to be exceedingly careful here, and just assume that all the usual disclaimers apply. If you kill the wrong segment, your other database is not going to be very happy about it. But assuming you killed the right segment, your database with the LGWR problem should be well and truly down. Bring 'er on up and the LGWR process should come up just fine. Bambi. -Original Message- Sent: Thursday, December 04, 2003 8:34 AM To: Multiple recipients of list ORACLE-L Anyone know what might be causing this error? Oracle 8.1.7 on Solaris. background process LGWR did not start -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: John Dunn INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Bellow, Bambi INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Mladen Gogala Oracle DBA Note: This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Wang Trading LLC and any of its subsidiaries each reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views
RE: background process LGWR did not start
also
'sysresv' will show which shared memory segments
and
semaphore sets belong to an instance.
Matt Adams - GE Appliances -
[EMAIL PROTECTED]Their fundamental design flaws are
completelyhidden by their superficial design
flaws. - Douglas
Adams
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]Sent: Friday, December 05, 2003 11:49
AMTo: Multiple recipients of list ORACLE-LSubject: RE:
background process "LGWR" did not startIn regards to Bambi's comments about having a single
instance on the server, this situation
gets more complex if you have several instances on a server.
There's also the possibility that the
instance(s) shared memory is in more than one segment. You can use
ipcs and oradebug to decipher which memory segments belong to which instance. Google for ipcs and oradebug,
several helpful references showed up
when I tried it. HTH
Jared
"Bellow, Bambi"
[EMAIL PROTECTED] Sent by: [EMAIL PROTECTED]
12/05/2003 08:34 AM Please
respond to ORACLE-L
To:
Multiple recipients of list ORACLE-L
[EMAIL PROTECTED] cc:
Subject:
RE: background process "LGWR" did not
startHi
John!When I've run into this problem it was because there was a memory
segmentbeing forced open. If you have the same issue, I can hep.
First, assumingthat you're on Unix (if you're not, please ignore the
rest of this email andjust have a lovely day), and that your database is
down (otherwise, if youwanted to do a shutdown abort, that wouldn't be such
a bad thing), you cando an ipcs -mAIf that was the only
instance on your box, the rest is pretty easy, cuz theoffending segment is
the only one owned by oracle in the list. If itwasn't, and there are
other oracle segments on the box, you have to find outwhich one is your guy.
The memory segments associated with a particularinstance should have
very similar (but not exactly the same) CTIMEs. Ifthere is one way out
of whack, that's your guy. Now, this is where mymemory gets a little
fuzzy (age, doncha know?)... if the instances startedup at nearly exactly
the same time for some reason, you are looking for a"0" in the insert
hem and haw segsz(?) column (anybody remember fersher onthis one?).
By now, you should know which memory segment to kill. To
kill the offending memory segment, do an ipcrm -m
segmenton it. You, of course, want to be exceedingly
careful here, and just assumethat all the usual disclaimers apply. If
you kill the wrong segment, yourother database is not going to be very happy
about it.But assuming you killed the right segment, your database with
the LGWRproblem should be well and truly down. Bring 'er on up and the
LGWR processshould come up just fine.Bambi.-Original
Message-Sent: Thursday, December 04, 2003 8:34 AMTo: Multiple
recipients of list ORACLE-LAnyone know what might be causing this
error? Oracle 8.1.7 on Solaris.background process "LGWR" did not
start-- Please see the official ORACLE-L FAQ:
http://www.orafaq.net-- Author: John DunnINET:
[EMAIL PROTECTED]Fat City Network Services --
858-538-5051 http://www.fatcity.comSan Diego, California
-- Mailing list and web hosting
services-To
REMOVE yourself from this mailing list, send an E-Mail messageto:
[EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and inthe message
BODY, include a line containing: UNSUB ORACLE-L(or the name of mailing list
you want to be removed from). You mayalso send the HELP command for
other information (like subscribing).-- Please see the official ORACLE-L
FAQ: http://www.orafaq.net-- Author: Bellow, BambiINET:
[EMAIL PROTECTED]Fat City Network Services --
858-538-5051 http://www.fatcity.comSan Diego, California
-- Mailing list and web hosting
services-To
REMOVE yourself from this mailing list, send an E-Mail messageto:
[EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and inthe message
BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed
from). You mayalso send the HELP command for other information (like
subscribing).
Re: background process LGWR did not start
Rebooting is not always an option. On Fri, 2003-12-05 at 09:04, Mladen Gogala wrote: I can almost guarantee that the issue will go away if you reboot the machine. I cannot fathom how would shared memory segments survive reboot. On 12/05/2003 11:49:24 AM, [EMAIL PROTECTED] wrote: In regards to Bambi's comments about having a single instance on the server, this situation gets more complex if you have several instances on a server. There's also the possibility that the instance(s) shared memory is in more than one segment. You can use ipcs and oradebug to decipher which memory segments belong to which instance. Google for ipcs and oradebug, several helpful references showed up when I tried it. HTH Jared Bellow, Bambi [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 12/05/2003 08:34 AM Please respond to ORACLE-L To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] cc: Subject:RE: background process LGWR did not start Hi John! When I've run into this problem it was because there was a memory segment being forced open. If you have the same issue, I can hep. First, assuming that you're on Unix (if you're not, please ignore the rest of this email and just have a lovely day), and that your database is down (otherwise, if you wanted to do a shutdown abort, that wouldn't be such a bad thing), you can do an ipcs -mA If that was the only instance on your box, the rest is pretty easy, cuz the offending segment is the only one owned by oracle in the list. If it wasn't, and there are other oracle segments on the box, you have to find out which one is your guy. The memory segments associated with a particular instance should have very similar (but not exactly the same) CTIMEs. If there is one way out of whack, that's your guy. Now, this is where my memory gets a little fuzzy (age, doncha know?)... if the instances started up at nearly exactly the same time for some reason, you are looking for a 0 in the insert hem and haw segsz(?) column (anybody remember fersher on this one?). By now, you should know which memory segment to kill. To kill the offending memory segment, do an ipcrm -m segment on it. You, of course, want to be exceedingly careful here, and just assume that all the usual disclaimers apply. If you kill the wrong segment, your other database is not going to be very happy about it. But assuming you killed the right segment, your database with the LGWR problem should be well and truly down. Bring 'er on up and the LGWR process should come up just fine. Bambi. -Original Message- Sent: Thursday, December 04, 2003 8:34 AM To: Multiple recipients of list ORACLE-L Anyone know what might be causing this error? Oracle 8.1.7 on Solaris. background process LGWR did not start -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: John Dunn INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Bellow, Bambi INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Mladen Gogala Oracle DBA Note: This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Wang Trading LLC and any of its subsidiaries each reserve the right to monitor
Re: background process LGWR did not start
No, but in this case, it's exactly what they did. Good, old ctrlaltdel saved the day. I just thought I might suggest it. After all, they did have an oracle version of BSOD. On 12/05/2003 12:59:25 PM, Jared Still wrote: Rebooting is not always an option. On Fri, 2003-12-05 at 09:04, Mladen Gogala wrote: I can almost guarantee that the issue will go away if you reboot the machine. I cannot fathom how would shared memory segments survive reboot. On 12/05/2003 11:49:24 AM, [EMAIL PROTECTED] wrote: In regards to Bambi's comments about having a single instance on the server, this situation gets more complex if you have several instances on a server. There's also the possibility that the instance(s) shared memory is in more than one segment. You can use ipcs and oradebug to decipher which memory segments belong to which instance. Google for ipcs and oradebug, several helpful references showed up when I tried it. HTH Jared Bellow, Bambi [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 12/05/2003 08:34 AM Please respond to ORACLE-L To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] cc: Subject:RE: background process LGWR did not start Hi John! When I've run into this problem it was because there was a memory segment being forced open. If you have the same issue, I can hep. First, assuming that you're on Unix (if you're not, please ignore the rest of this email and just have a lovely day), and that your database is down (otherwise, if you wanted to do a shutdown abort, that wouldn't be such a bad thing), you can do an ipcs -mA If that was the only instance on your box, the rest is pretty easy, cuz the offending segment is the only one owned by oracle in the list. If it wasn't, and there are other oracle segments on the box, you have to find out which one is your guy. The memory segments associated with a particular instance should have very similar (but not exactly the same) CTIMEs. If there is one way out of whack, that's your guy. Now, this is where my memory gets a little fuzzy (age, doncha know?)... if the instances started up at nearly exactly the same time for some reason, you are looking for a 0 in the insert hem and haw segsz(?) column (anybody remember fersher on this one?). By now, you should know which memory segment to kill. To kill the offending memory segment, do an ipcrm -m segment on it. You, of course, want to be exceedingly careful here, and just assume that all the usual disclaimers apply. If you kill the wrong segment, your other database is not going to be very happy about it. But assuming you killed the right segment, your database with the LGWR problem should be well and truly down. Bring 'er on up and the LGWR process should come up just fine. Bambi. -Original Message- Sent: Thursday, December 04, 2003 8:34 AM To: Multiple recipients of list ORACLE-L Anyone know what might be causing this error? Oracle 8.1.7 on Solaris. background process LGWR did not start -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: John Dunn INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Bellow, Bambi INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Mladen Gogala Oracle DBA Note: This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error
Re: background process LGWR did not start
alert/trace files ? - Original Message - To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED] Sent: Thursday, December 04, 2003 9:34 PM Anyone know what might be causing this error? Oracle 8.1.7 on Solaris. background process LGWR did not start -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: John Dunn INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: rahul sharma INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
RE: Background Process
Hi Raj, These are I/O slaves. You get them by setting 'dbwr_io_slaves' and possibly other similar parameters. @ Regards, @ Steve Adams @ http://www.ixora.com.au/ @ http://www.christianity.net.au/ -Original Message- Sent: Thursday, 12 April 2001 21:52 To: Multiple recipients of list ORACLE-L DBAs I facing severe IO on the server. I got no clue why. I find three oracle background processes which I never heard of. They are ora_i101_orcl, ora_i102_orcl, ora_i201_orcl. Any idea what is this? Thanks Raj -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Raj Gopalan INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Steve Adams INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
