Re: Interesting lesson on ARCHIVELOG mode
Hi James, Hopefully the other lesson you've learnt is the importance of training, even for "Junior DBAs" so that such fundamentally basic but potentially costly mistakes can be avoided. Cheers Richard - Original Message - To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]> Sent: Wednesday, April 02, 2003 11:58 PM > Some of you on the list might find this interesting. > > I just wanted to relate a story with respect to an incident experienced in > the last few days on one of our test databases. Environment is Compaq Tru64 > Unix / Oracle 8.1.7.4. > > A few days ago, I remember talking to a junior DBA who assists me in the > Oracle area, concerning excessive space usage on one of the Unix machines > running a test database environment. I noted that the database was running > in ARCHIVELOG mode with automatic archiving (of course), and generating a > great many archived logs since there was considerable activity on that > instance/database. We discussed the matter and agreed that there was no > need to have ARCHIVELOG mode turned on in this case. So I told my assistant > DBA to go ahead and make the database NOARCHIVELOG, which I thought she > understood. > > Yesterday, she comes to me with a host of problems she has been experiencing > on that test database, one of which was many failed attempts to import a 2 > Million row table from another database's export. It seemed that the import > would just hang after importing about 130,000 rows. She repeatedly > cancelled the import, resorted to cycling the database, creating a another > table with just a subset of the columns of the original, limiting the number > of rows imported at one time, fooling with the "buffer" parameters of the > import control file, trying SQL*LOADER, and so on. Quite frustrated, she > came to me for advice. > > I had forgotten about the ARCHIVELOG mode issue a few days earlier, so I > began scratching my head as I looked unsuccessfully for signs of trouble in > alert logs and traces. I thought maybe a rollback segment had run out of > room, lost its brains, or maybe temp space had become a problem. But again, > no sign of any of these issues in alerts or traces. Suspecting database > corruption, I took a full export to see if export would report any corrupted > blocks. That worked flawlessly. I began to wonder if we should just start > from scratch and recreate the database. Then something interesting became > apparant. > > Looking at V$DATABASE, I noticed that the database was still in ARCHIVELOG > mode! When I asked about this, it seems that she thought that simply > commenting out the init.ora parameters: > > log_archive_start=true > > log_archive_dest=whatever > > log_archive_format=whatever > and then recycling the database would take care of the whole issue of > ARCHIVELOG mode, making the database become NOARCHIVELOG mode. Well, guess > what.it didn't. > > The lesson learned was that with the database still in ARCHIVELOG mode and > automatic archiving turned off, obviously enough DML would cause the > database to hang whenever it did a log switch, awaiting us DBAs to manually > archive the filled redo logs. Realizing this, of course we then did the > prudent thing: > > alter database noarchivelog > and lived happily ever after. > > Had I continued to assume database corruption and just had her recreate the > database, it WOULD have indeed solved the problem BUT ONLY because the > database would have come up in NOARCHIVELOG mode. However, it certainly > would have bothered me as to why the database had become corrupted in the > first place. > > I am very happy to know what actually happened, that the database wasn't > corrupted at all. It was just someone's misunderstanding in not realizing > that "ARCHIVELOG mode" and "automatic archiving" are two related but totally > different things! > > Jim Damiano > > -- > Please see the official ORACLE-L FAQ: http://www.orafaq.net > -- > Author: James Damiano > 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: Interesting lesson on ARCHIVELOG mode
Good Posting, JIM . I had once gone thru the exactly same experience. Oracle database has some processes that work both independently , but again, they work in tandem. Here is the peice where LGWR (in Archivelog) and ARCH(s) are expected to work in tandem with each other (in ARCHIVELOG mode). In Noarchivelog mode, ARCH(s) are not needed. SO LGWR works independently of ARCHs. but you need to tell that to LGWR ( that archiving is NOT happening , the command "alter database noarchivelog" basically tells LGWR precisely that) so that LGWR can recycle the log files to do a log switch ( log1 --> log2 -->log1). In archivelogmode it will be log1 -->(arch_log2_ by arch) -->log2 -->( arch_log1_+1 by arch) --> log1 I think, a good understanding of the "Concepts DOC" is the most imporatnt thing for a Oracle DBA. Pradip -Original Message- Sent: Wednesday, April 02, 2003 7:29 PM To: Multiple recipients of list ORACLE-L Some of you on the list might find this interesting. I just wanted to relate a story with respect to an incident experienced in the last few days on one of our test databases. Environment is Compaq Tru64 Unix / Oracle 8.1.7.4. A few days ago, I remember talking to a junior DBA who assists me in the Oracle area, concerning excessive space usage on one of the Unix machines running a test database environment. I noted that the database was running in ARCHIVELOG mode with automatic archiving (of course), and generating a great many archived logs since there was considerable activity on that instance/database. We discussed the matter and agreed that there was no need to have ARCHIVELOG mode turned on in this case. So I told my assistant DBA to go ahead and make the database NOARCHIVELOG, which I thought she understood. Yesterday, she comes to me with a host of problems she has been experiencing on that test database, one of which was many failed attempts to import a 2 Million row table from another database's export. It seemed that the import would just hang after importing about 130,000 rows. She repeatedly cancelled the import, resorted to cycling the database, creating a another table with just a subset of the columns of the original, limiting the number of rows imported at one time, fooling with the "buffer" parameters of the import control file, trying SQL*LOADER, and so on. Quite frustrated, she came to me for advice. I had forgotten about the ARCHIVELOG mode issue a few days earlier, so I began scratching my head as I looked unsuccessfully for signs of trouble in alert logs and traces. I thought maybe a rollback segment had run out of room, lost its brains, or maybe temp space had become a problem. But again, no sign of any of these issues in alerts or traces. Suspecting database corruption, I took a full export to see if export would report any corrupted blocks. That worked flawlessly. I began to wonder if we should just start from scratch and recreate the database. Then something interesting became apparant. Looking at V$DATABASE, I noticed that the database was still in ARCHIVELOG mode! When I asked about this, it seems that she thought that simply commenting out the init.ora parameters: > log_archive_start=true > log_archive_dest=whatever > log_archive_format=whatever and then recycling the database would take care of the whole issue of ARCHIVELOG mode, making the database become NOARCHIVELOG mode. Well, guess what.it didn't. The lesson learned was that with the database still in ARCHIVELOG mode and automatic archiving turned off, obviously enough DML would cause the database to hang whenever it did a log switch, awaiting us DBAs to manually archive the filled redo logs. Realizing this, of course we then did the prudent thing: > alter database noarchivelog and lived happily ever after. Had I continued to assume database corruption and just had her recreate the database, it WOULD have indeed solved the problem BUT ONLY because the database would have come up in NOARCHIVELOG mode. However, it certainly would have bothered me as to why the database had become corrupted in the first place. I am very happy to know what actually happened, that the database wasn't corrupted at all. It was just someone's misunderstanding in not realizing that "ARCHIVELOG mode" and "automatic archiving" are two related but totally different things! Jim Damiano -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: James Damiano 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
Interesting lesson on ARCHIVELOG mode
Some of you on the list might find this interesting. I just wanted to relate a story with respect to an incident experienced in the last few days on one of our test databases. Environment is Compaq Tru64 Unix / Oracle 8.1.7.4. A few days ago, I remember talking to a junior DBA who assists me in the Oracle area, concerning excessive space usage on one of the Unix machines running a test database environment. I noted that the database was running in ARCHIVELOG mode with automatic archiving (of course), and generating a great many archived logs since there was considerable activity on that instance/database. We discussed the matter and agreed that there was no need to have ARCHIVELOG mode turned on in this case. So I told my assistant DBA to go ahead and make the database NOARCHIVELOG, which I thought she understood. Yesterday, she comes to me with a host of problems she has been experiencing on that test database, one of which was many failed attempts to import a 2 Million row table from another database's export. It seemed that the import would just hang after importing about 130,000 rows. She repeatedly cancelled the import, resorted to cycling the database, creating a another table with just a subset of the columns of the original, limiting the number of rows imported at one time, fooling with the "buffer" parameters of the import control file, trying SQL*LOADER, and so on. Quite frustrated, she came to me for advice. I had forgotten about the ARCHIVELOG mode issue a few days earlier, so I began scratching my head as I looked unsuccessfully for signs of trouble in alert logs and traces. I thought maybe a rollback segment had run out of room, lost its brains, or maybe temp space had become a problem. But again, no sign of any of these issues in alerts or traces. Suspecting database corruption, I took a full export to see if export would report any corrupted blocks. That worked flawlessly. I began to wonder if we should just start from scratch and recreate the database. Then something interesting became apparant. Looking at V$DATABASE, I noticed that the database was still in ARCHIVELOG mode! When I asked about this, it seems that she thought that simply commenting out the init.ora parameters: > log_archive_start=true > log_archive_dest=whatever > log_archive_format=whatever and then recycling the database would take care of the whole issue of ARCHIVELOG mode, making the database become NOARCHIVELOG mode. Well, guess what.it didn't. The lesson learned was that with the database still in ARCHIVELOG mode and automatic archiving turned off, obviously enough DML would cause the database to hang whenever it did a log switch, awaiting us DBAs to manually archive the filled redo logs. Realizing this, of course we then did the prudent thing: > alter database noarchivelog and lived happily ever after. Had I continued to assume database corruption and just had her recreate the database, it WOULD have indeed solved the problem BUT ONLY because the database would have come up in NOARCHIVELOG mode. However, it certainly would have bothered me as to why the database had become corrupted in the first place. I am very happy to know what actually happened, that the database wasn't corrupted at all. It was just someone's misunderstanding in not realizing that "ARCHIVELOG mode" and "automatic archiving" are two related but totally different things! Jim Damiano -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: James Damiano 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: archivelog mode
You are looking for ...dest_ = "location=" I would recommend that you utilize the new enumerated archive destination locations, due to the inherent benefits... one example: If you use two locations, enabling the first(1) and defer the second(2), then if dest_1 fills up, you can enable dest_2 and allow your database to overflow archive to dest_2, thereby preventing the "lockup" caused if your one and only destination is full. HTH, -Ron- > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Khedr, > Waleed > Sent: Friday, March 08, 2002 6:03 PM > To: Multiple recipients of list ORACLE-L > Subject: RE: archivelog mode > > > Try using: LOG_ARCHIVE_DEST instead of LOG_ARCHIVE_DEST_1 > If you would like using LOG_ARCHIVE_DEST_1 you have to read the in Oracle > Doc the syntax for it since more keywords are needed like 'location'. > > Waleed > > -Original Message- > Sent: Friday, March 08, 2002 6:09 PM > To: Multiple recipients of list ORACLE-L > > > Hi All > > While enabling automatic archiving on our 8.1.7 database I get the > following error :- > > ORA-00439: feature not enabled: Managed Standby > > ie the database is in archivelog mode and I edit the parameter file to > enable automatic archiving .. I get the error when trying to startup the > database .. these are the parameters that I change - > > # log_archive_start = true > # log_archive_dest_1 = "location=/u03/oradata/arch" > # log_archive_format = arch_%t_%s.arc > > > Due to this I have to start archiving whenever I restart, using 'alter > system archivelog start' > > Any ideas ? > > -- > Sajid Iqbal > > > > > -- > Please see the official ORACLE-L FAQ: http://www.orafaq.com > -- > Author: Sajid Iqbal > 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: Khedr, Waleed > 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: Ron Yount 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).
RE: archivelog mode
Try using: LOG_ARCHIVE_DEST instead of LOG_ARCHIVE_DEST_1 If you would like using LOG_ARCHIVE_DEST_1 you have to read the in Oracle Doc the syntax for it since more keywords are needed like 'location'. Waleed -Original Message- Sent: Friday, March 08, 2002 6:09 PM To: Multiple recipients of list ORACLE-L Hi All While enabling automatic archiving on our 8.1.7 database I get the following error :- ORA-00439: feature not enabled: Managed Standby ie the database is in archivelog mode and I edit the parameter file to enable automatic archiving .. I get the error when trying to startup the database .. these are the parameters that I change - # log_archive_start = true # log_archive_dest_1 = "location=/u03/oradata/arch" # log_archive_format = arch_%t_%s.arc Due to this I have to start archiving whenever I restart, using 'alter system archivelog start' Any ideas ? -- Sajid Iqbal -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Sajid Iqbal 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: Khedr, Waleed 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).
archivelog mode
Hi All While enabling automatic archiving on our 8.1.7 database I get the following error :- ORA-00439: feature not enabled: Managed Standby ie the database is in archivelog mode and I edit the parameter file to enable automatic archiving .. I get the error when trying to startup the database .. these are the parameters that I change - # log_archive_start = true # log_archive_dest_1 = "location=/u03/oradata/arch" # log_archive_format = arch_%t_%s.arc Due to this I have to start archiving whenever I restart, using 'alter system archivelog start' Any ideas ? -- Sajid Iqbal -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Sajid Iqbal 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).
Re: Shutdown and archivelog mode
Sajid, The db must be cleanly shutdown (normal or immediate) in order to change the archivelog mode. A shutdown immediate may not shutdown immediately for several reasons, most commonly: 1. There is an uncommitted transaction that needs to roll back. 2. SMON is deallocating temp segments and there are a very large # of them to deallocate (usually due to the default extent sizes for the temporary tablespace being too low). See metalink note 61997.1 for an excellent discussion on this. HTH, -- Anita --- Sajid Iqbal <[EMAIL PROTECTED]> wrote: > Hi > > Using Oracle 8.1.6.3 on solaris 2.7. > > I am trying to put my database in archivelog mode. > > When I try to shutdown the database using shutdown > immediate, it just sits > there for ages.. (left it for 30 mins). > > I've cancelled this and done a shutdown abort. > (tried normal shutdown > after that, same) > > Due to this when I try to put it archivelog mode > after shutdown abort I > get a message saying that the database can't be put > into archivelog mode > because recovery is needed. > > TIA > > -- > Sajid Iqbal __ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: A. Bardeen 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).
Re: Shutdown and archivelog mode
do a shutdown normal ALWAYS after issuing a shutdown abort. - Original Message - To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]> Sent: Monday, September 03, 2001 3:16 PM > Hi > > Using Oracle 8.1.6.3 on solaris 2.7. > > I am trying to put my database in archivelog mode. > > When I try to shutdown the database using shutdown immediate, it just sits > there for ages.. (left it for 30 mins). > > I've cancelled this and done a shutdown abort. (tried normal shutdown > after that, same) > > Due to this when I try to put it archivelog mode after shutdown abort I > get a message saying that the database can't be put into archivelog mode > because recovery is needed. > > TIA > > -- > Sajid Iqbal > > > > > > -- > Please see the official ORACLE-L FAQ: http://www.orafaq.com > -- > Author: Sajid Iqbal > 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: Saurabh Sharma 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).
Shutdown and archivelog mode
Hi Using Oracle 8.1.6.3 on solaris 2.7. I am trying to put my database in archivelog mode. When I try to shutdown the database using shutdown immediate, it just sits there for ages.. (left it for 30 mins). I've cancelled this and done a shutdown abort. (tried normal shutdown after that, same) Due to this when I try to put it archivelog mode after shutdown abort I get a message saying that the database can't be put into archivelog mode because recovery is needed. TIA -- Sajid Iqbal -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Sajid Iqbal 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).
Re: Database in archivelog mode
u must mount the database in exclusive mode, before putting the cmd for alter database. just give. shutdown immediate startup mount exclusive alter database archivelog; alter database open; or do another shutdown immediate startup will do the problem solved. i've done it several times. - Original Message - To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]> Sent: Friday, June 22, 2001 11:15 AM Well there is no need to specify the alter system archive log start as you have already done this by specifying the log_archive_start=true in the init.ora. Try 'alter system switch logfile' command a couple of times and see if anything is written to disk. Check using 'archive log list' command it should show u the status of archive. Regards murosa@bankin ter.es To: Multiple recipients of list ORACLE-L Sent by: <[EMAIL PROTECTED]> root@fatcity.cc: com Subject: Database in archivelog mode 22-Jun-2001 01:15 AM Please respond to ORACLE-L Sender Info: No Sender Info found in the address Book Hi folks. I have a very strange behavour in a database. I want to put database inarchivelogmode, I've changed log_archive_start to true, log_archive_dest_1 to a location where I can write and log_archive_start to true. Then I follow next sequence: shutdown immediate; startup mount alter database archivelog; alter database open; alter system archive log start; In third step I get: ERROR at line 1: ORA-01126: database must be mounted EXCLUSIVE and not open for this operation. Next two sentence are executed correctly. When I select * from v$instance; I've got SQL> select * from v$instance; INSTANCE_NUMBER INSTANCE_NAME --- HOST_NAME VERSION STARTUP_T STATUS PARTHREAD# ARCHIVE LOG_SWITCH_ - - --- --- -- --- --- LOGINS SHU DATABASE_STATUS INSTANCE_ROLE -- --- - -- 2 webspher2 ebkppr02 8.1.6.3.0 21-JUN-01 OPENYES 2 STARTED ALLOWEDNO ACTIVEPRIMARY_INSTANCE in both instance, because is an OPS. Initalization parameter remote_login_password is exclusive. I know that I have an error but I don't know which and why, but it doesn't work in archivelog mode. Anybody can help me?. Thank you very much in advance. Miguel Urosa. "Este mensaje y los documentos que, en su caso, lleve anexos, pueden contener información confidencial. Por ello, se informa a quien lo reciba por error que la información contenida en el mismo es reservada y su uso no autorizado está prohibido legalmente, por lo que en tal caso le rogamos que nos lo comunique por la misma vía o por teléfono (901 113 113) , se abstenga de realizar copias del mensaje o remitirlo o entregarlo a otra persona y proceda a borrarlo de inmediato." -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: 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). __ Visit us at www.singaporeair.com. __ -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: 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
Re: Database in archivelog mode
Well there is no need to specify the alter system archive log start as you have already done this by specifying the log_archive_start=true in the init.ora. Try 'alter system switch logfile' command a couple of times and see if anything is written to disk. Check using 'archive log list' command it should show u the status of archive. Regards murosa@bankin ter.es To: Multiple recipients of list ORACLE-L Sent by: <[EMAIL PROTECTED]> root@fatcity.cc: com Subject: Database in archivelog mode 22-Jun-2001 01:15 AM Please respond to ORACLE-L Sender Info: No Sender Info found in the address Book Hi folks. I have a very strange behavour in a database. I want to put database inarchivelogmode, I've changed log_archive_start to true, log_archive_dest_1 to a location where I can write and log_archive_start to true. Then I follow next sequence: shutdown immediate; startup mount alter database archivelog; alter database open; alter system archive log start; In third step I get: ERROR at line 1: ORA-01126: database must be mounted EXCLUSIVE and not open for this operation. Next two sentence are executed correctly. When I select * from v$instance; I've got SQL> select * from v$instance; INSTANCE_NUMBER INSTANCE_NAME --- HOST_NAME VERSION STARTUP_T STATUS PARTHREAD# ARCHIVE LOG_SWITCH_ - - --- --- -- --- --- LOGINS SHU DATABASE_STATUS INSTANCE_ROLE -- --- - -- 2 webspher2 ebkppr02 8.1.6.3.0 21-JUN-01 OPENYES 2 STARTED ALLOWEDNO ACTIVEPRIMARY_INSTANCE in both instance, because is an OPS. Initalization parameter remote_login_password is exclusive. I know that I have an error but I don't know which and why, but it doesn't work in archivelog mode. Anybody can help me?. Thank you very much in advance. Miguel Urosa. "Este mensaje y los documentos que, en su caso, lleve anexos, pueden contener información confidencial. Por ello, se informa a quien lo reciba por error que la información contenida en el mismo es reservada y su uso no autorizado está prohibido legalmente, por lo que en tal caso le rogamos que nos lo comunique por la misma vía o por teléfono (901 113 113) , se abstenga de realizar copias del mensaje o remitirlo o entregarlo a otra persona y proceda a borrarlo de inmediato." -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: 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 ORA
Database in archivelog mode THANX
I've got solution from 1062786.6 note of Metalink. Thank you very much to all who reply to me. Best regards. Miguel Urosa. "Este mensaje y los documentos que, en su caso, lleve anexos, pueden contener información confidencial. Por ello, se informa a quien lo reciba por error que la información contenida en el mismo es reservada y su uso no autorizado está prohibido legalmente, por lo que en tal caso le rogamos que nos lo comunique por la misma vía o por teléfono (901 113 113) , se abstenga de realizar copias del mensaje o remitirlo o entregarlo a otra persona y proceda a borrarlo de inmediato." -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: 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).
Database in archivelog mode
Hi folks. I have a very strange behavour in a database. I want to put database inarchivelogmode, I've changed log_archive_start to true, log_archive_dest_1 to a location where I can write and log_archive_start to true. Then I follow next sequence: shutdown immediate; startup mount alter database archivelog; alter database open; alter system archive log start; In third step I get: ERROR at line 1: ORA-01126: database must be mounted EXCLUSIVE and not open for this operation. Next two sentence are executed correctly. When I select * from v$instance; I've got SQL> select * from v$instance; INSTANCE_NUMBER INSTANCE_NAME --- HOST_NAME VERSION STARTUP_T STATUS PARTHREAD# ARCHIVE LOG_SWITCH_ - - --- --- -- --- --- LOGINS SHU DATABASE_STATUS INSTANCE_ROLE -- --- - -- 2 webspher2 ebkppr02 8.1.6.3.0 21-JUN-01 OPENYES 2 STARTED ALLOWEDNO ACTIVEPRIMARY_INSTANCE in both instance, because is an OPS. Initalization parameter remote_login_password is exclusive. I know that I have an error but I don't know which and why, but it doesn't work in archivelog mode. Anybody can help me?. Thank you very much in advance. Miguel Urosa. "Este mensaje y los documentos que, en su caso, lleve anexos, pueden contener información confidencial. Por ello, se informa a quien lo reciba por error que la información contenida en el mismo es reservada y su uso no autorizado está prohibido legalmente, por lo que en tal caso le rogamos que nos lo comunique por la misma vía o por teléfono (901 113 113) , se abstenga de realizar copias del mensaje o remitirlo o entregarlo a otra persona y proceda a borrarlo de inmediato." -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: 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).
