Archive logs cutting early

Hello, I have a 11g 11.1.0.7 database running on Windows Server 2003 64bit. This is a new server and database that will be replacing our 10g 32bit system. Everything is running fine on it, the only weird thing I have noticed is that the Redo logs cut early. I have them set to 50mb and they seem to always cut at 25mb. Once in a while I will get one that is around 44mb. I do not have the ARCHIVE_LAG_TARGET parameter set. I am confused as to why I can only get 25mb into an Archive log. I have Automatic Memory Management enabled and the Maximum Memory size is set to 15gb. I also have Large Page support enabled.
On my current 10g server, the archive logs are being cut about every 5 minutes and I am trying to set this new server to cut 1 or 2 an hour. Having these logs cut early is making it difficult to determine what size Redo logs I need. I guess I could set them to a much larger size and then set the ARCHIVE_LAG_TARGET parameter to cut every 60 minutes but I want to make sure something isn't set incorrectly to cause the early cut of the Redo log. My Redo Buffer size is 61665280 bytes when I check "Show SGA". Any help with this would be appreciated.

I checked the Archive_Lag_target parameter again and it is set to '0'. There is not much activity on the database right now since people don't start training on it until next week so it looks like it cuts an archive log just under 4 hours apart. When I was upgrading the database with our 10g data I had it in archive mode and it was cutting 25mb logs every few minutes since I was putting a pretty heavy load on it. I have never seen this behavior before, I am hoping my vendor who we get our Oracle support through puts in a SR with Oracle. Unfortunately I can't get direct support from Oracle.
Could Automatic Memory Management have anything to do with it? This is the only real difference between my 10g and 11g databases that I can think of. I also have set a much larger SGA/PGA than my 10g database.

Similar Messages

Rman backup archive log

Hi Guys,
Can advise on the syntax to perform rman backup of archive logs generated in last 2 days?
Should it be 1 or 2?
thanks!
1. BACKUP ARCHIVELOG UNTIL TIME 'SYSDATE-2';
2. BACKUP ARCHIVELOG FROM TIME 'SYSDATE-2';

What prevents you from trying both?
I'm not trying to be difficult here but why take the time to ask people in a forum, not even supplying a version number, and not just find out?
It took me less than 60 seconds to cut-and-paste both of your command lines into RMAN and look at the output.
Edited by: damorgan on Jan 19, 2013 4:11 PM

RMAN-06054: media recovery requesting unknown archived log

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/16/2013 09:03:43
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 34751 and starting SCN of 8923445274I am receiving the error above on performing RMAN Active cloning, please advise how to resolve this

In addition to what was said, I can think of two other possibilities for RMAN-6054 during duplicate: bugs such as 12625205 (also see 8554110); duplicate was run earlier without removing the old restored files (Note 1549172.1). In the first case, just specify SCN or find the actual log file and speficy log sequence, instead of time. In the latter case, remove the old restored files or speficy noresume.
Edited by: user11989003 on May 29, 2013 10:17 AM

Need to restore a table which is del by mistake my archive log is on

Hi Guru's
i took full backup through RMAN. My archive log in ON.
After taking backup one of table is deleted by mistake ,how can i restore it ?
Thanks

Hello,
The solution depends on your Oracle Release and if you enabled RECYCLE BIN and/or FLASHBACK LOG.
If the Table was dropped and you are in Oracle *9.2* or earlier release, you need to Restore/Recover the Database (from the RMAN BACKUP) to a time before the Table was dropped, somewhere else (another server,...). Then from this Database you may export the Table and import it to the original Database.
If the rows of the Table were just Deleted (so the Table still exists), you may (in 9.2) use FLASHBACK QUERY to get back the deleted rows.
If you are in *10.1* or later release, then if the Table was dropped you may use FLASHBACK DROP to get it back (see the previous post from Kamran). If the rows were just deleted (so the Table still exists) you may use FLASHBACK QUERY or more efficiently FLASHBACK TABLE:
http://www.oracle-developer.net/display.php?id=313
About FLASHBACK QUERY, it depends on the Undo Retention time (it should be large enough), and the table shouldn't have Column of specific Datatype like LONG or LOB:
http://www.orafaq.com/node/50
Hope this help.
Best regards,
Jean-Valentin

Archive log mode in 3 node rac database

Sir I am using oracle 10.2.0.1 and created 3 node cluster setup on.OS i am using linux 4
I am too much confuse in setting up this cluster in archive log mode bec why we need to false cluater_database parameter to setup cluster in archive log mode.
I have search lot of documents but all are saying we not need setting this parameter flase perior to 10.2.But what is the actual concept behind setting this parameter to false in early release and why we need not to set it false.Please help me.
I know how to set up in archive log mode but this parameter create confusion.
Thanks sir in advance

I also dont't know all the details about this but I'll try to explain what I know. Setting cluster_database to false in a rac environment is usually done when you need to mount the database from one instance exclusively. This is still needed when you upgrade the catalog, for example during release update (from 10.2.0.1 to 10.2.0.4 for example). Now with switching archivelog mode someone at oracle must have discovered that it is sufficient when the database is mounted by only one instance and you can actually save one step.
As I (and propably most of you) don't switch archiving on or off on a daily basis, I don't worry about this a lot, simply turn this on when I create a new database and then leave it on forever.
Bjoern

Recovery in archive mode, but no archived logs

Hi,
I hope someone can help me with the following question.
I have a 9.2 database in archive mode. Suppose on t=t0 I make an online backup. At the end of this run, I will do an "alter system switch logfile" statement to capture the latest transactions (more or less also at t=t0). Later, at t=t1 we do some transaction and more archived redologs are created. At t-t2 I need to restore the complete database, but I have LOST all the archive files as from t=t0. Now the question is, is it still possible to recover (even it means to go back to t=t0)? I have tried it, but always the system suggests to apply the (missing) archived redo's, and it seems I cannot escape this. But, Is it possible to get back to t=t0?
Thanks a lot, for any clue or pointer !

If you take a hot backup and you lose the redo logs, you have a fundamentally inconsistent backup. Each tablespace will be internally consistent, but they probably won't have the same SCN as the control files, so you'll get this message.
Do you have an earlier hot backup and the archived logs that would restore that backup to the point in time (t=0) where you took the latest hot backup? Personally, I generally like to keep at least 2 or 3 old backups, with archived log files, just in case something goes wrong with the most recent backup.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

DB backup and removal of archive log files?

I have an application that uses Oracle 10gR2 on Linux RedHat EL 4.5. The DB is fairly simple, so backing up daily or weekly by using expdp (Datapump) is fine for our needs. We have an install that uses Data Guard, which in archivelog mode is filling up the disks fast.
What is the best way to clean up archive log files in a Data Guard configuration? I have seen posts that indicate RMAN is tough to work with and has problems with recovery, so I would rather avoid it.
I would like script something on a daily or weekly basis.
Thanks,

RMAN not easy? Lets see how hard it is:
rman target /
RMAN> backup database;Surely that isn't too challenging.
Now if you want to do it properly you are talking about setting up a repository ... much more complex:
-- on the repository database server
CREATE USER repos
IDENTIFIED BY oracl1
DEFAULT TABLESPACE users
TEMPORARY TABLESPACE temp
QUOTA UNLIMITED on users;
GRANT create session, recovery_catalog_owner TO repos;
-- on the target server (your production db)
rman target / catalog repos/oracle1@<tnsnames_entry_for_your repository>
RMAN> create catalog;
RMAN> register database;
RMAN> backup database;If this is too much perhaps you should look into MS Access. <g>
All of this is documented at the top of the RMAN page in Morgan's Library at www.psoug.org so you can cut-and-paste your way through it if you want.
How is an export not a backup you ask?
The Oracle docs can be found at http://tahiti.oracle.com. You should consider reading them some time.
As I said before ... an export can NOT be used to recover ... ever. That says it all.
Your resistance to change. Your resistance to doing things properly. Your resistance to reading the docs. You'd better watch out. There are people who would like to have your job ... a lot of them.

Too many archived logs when trying a backup

Hello all,
I'm having a bit of trouble running a backup script on an Oracle instance (10g1, on Solaris).
As a normal DBA practice, I guess the backup should be scheduled and run from the very beginning of using a DB. Sometimes, from various reasons, this does not happen. In this case, before running the first (full) backup of the DB, there might be tens or hundreds of archived logs waiting to be backed up, and the flash recovery area might just not be able to handle all of them (at least that's how I see it, I might be wrong, I'm still fighting my way through Oracle's Backup and Recovery issues). In that case, a backup script containing the following RMAN sequence:
run{
allocate channel ch1 type disk;
backup
incremental
level = 0
database;
release channel ch1;
fails with the error message ORA-19804 (cannot reclaim disk space from the DB_RECOVERY_FILE_DEST_SIZE limit).
After this, the archived logs that were backed up are marked as obsolete, and I can delete them from RMAN with "delete obsolete". The script I'm using for backup runs fine afterwards. Before attempting a backup, however, no logs are reported as obsolete.
The retention policy is the default "redundancy 1" and the archivelog deletion policy is none.
How could I prevent the backup script from crashing? If I'm changing the archivelog deletion policy, will I be able to restore the DB properly from my backup set? (as earlier logs will be deleted before making a backup)
Thank you for any suggestions, your help is very much appreciated,
Adrian

I am having an impression that you are not using scheduled backups and let client decided when to take backup. Well this is not good, in this case you won't be able to get rid of this error bcz you never know when the next or even first backup is going to occur and without that you can't even think of deleting your logs. If you are not using tape drives then your archivelogs and backups both will sit in recovery area and you should have enough available space to hold both of them. I would say to schedule your backups and use DELETE INPUT clause of RMAN backup to delete the archivelogs after backing them up. And also delete the obsolete backups according to your recovery window. This is the proper way to manage recovery area space. You really need to tune the recovery area space by testing the amount of redo generation, backup size, retention policy etc etc and then come up with a figure of recovery area size which is suitable for your env to hold all of the required files for required time (recover window).
Daljit Singh

OVM 3.0 Database Creating Lots of Archive Logs

Greetings - ever since we initially installed OVM 3.0 earlier this fall (~October), the OVM database has generated archive logs at a very rapid rate. It continually threatens to fill up our 16 GB filesystem dedicated to archive logs, even after daily backup and purging.
Our OVM database itself is about 4-6 GB large, and we would need to increase the archive log filesystem to about 20-25 GB in size, which we see as unreasonable for such a small database.
What is causing OVM to generate so many redo logs? Our best guess is that OVM is continuously gathering guest VM CPU usage on each physical server.
Is there a way to configure the OVM application in order to reduce the amount of redo/archive logs being created?
We are currently running 3.0.3, having upgraded each time a 3.0.* patch was released. OVMM running on OEL 6.1, database running on latest HP-UX.

majedian21 wrote:
Greetings - ever since we initially installed OVM 3.0 earlier this fall (~October), the OVM database has generated archive logs at a very rapid rate. It continually threatens to fill up our 16 GB filesystem dedicated to archive logs, even after daily backup and purging.I would log an SR with Oracle Support for this, so that Development can look at it. Sounds like your environment has lots of VMs running and yes, collecting usage stats for all of those environments. However, there may be some old data from the previous versions that's causing more stats to be collected than necessary.

RAC online and archive logs question

Hello All,
I setup a RAC database instances prod1 and prod2 (10.2.0.4). Datafiles and onlinelogs are on ASM.
Does these results look good queried from two instances. I am kind of concerned about the Group3 that has the same name for both the members.
Also archived logs are going to the ASM, is this a good practice. I was reading Oracle RMAN book and it mentioned archived logs go to local disk.
Is it possible to archive to local disk for online that are on ASM? Please advice. Early reply appreciated.. Thanks San~
PROD1 Instance
SQL> select member from v$logfile;
MEMBER
+DATA/prod/onlinelog/group_2.264.706892209
+FLASH/prod/onlinelog/group_2.259.706892211
+DATA/prod/onlinelog/group_1.261.706892209
+FLASH/prod/onlinelog/group_1.260.706892209
+DATA/prod/onlinelog/group_3.258.706892235
+FLASH/prod/onlinelog/group_3.258.706892235
+DATA/prod/onlinelog/group_4.256.706892237
+FLASH/prod/onlinelog/group_4.257.706892237
8 rows selected.
PROD2 Instance
SQL> select member from v$logfile;
MEMBER
+DATA/prod/onlinelog/group_2.264.706892209
+FLASH/prod/onlinelog/group_2.259.706892211
+DATA/prod/onlinelog/group_1.261.706892209
+FLASH/prod/onlinelog/group_1.260.706892209
+DATA/prod/onlinelog/group_3.258.706892235
+FLASH/prod/onlinelog/group_3.258.706892235
+DATA/prod/onlinelog/group_4.256.706892237
+FLASH/prod/onlinelog/group_4.257.706892237
8 rows selected.
===
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 3
Next log sequence to archive 4
Current log sequence 4
====
Thanks
San

Hi San,
sannidhi wrote:
Also archived logs are going to the ASM, is this a good practice. I was reading Oracle RMAN book and it mentioned archived logs go to local disk.
Is it possible to archive to local disk for online that are on ASM? Please advice. Early reply appreciated.. Thanks San~
It is recommend to store archived log files on ASM and on Shared disk, check your archive log format which suppose to represent uniqueness across all instances.
Yes, technically it is possible to archive to local disk, but not recommended as if you loose local disk there will be gaps in the archived log files and also it increases the administration.
Regards,
Thota

DB Back to a Specific Time with Archive Logs (Until cancel or time?)

I'll try to be as clear as possible with my intended goals and the limitations of the system I'm working with:
1. We have a test instance of our Oracle DB that I would like to be able to refresh with data from the production instance at any time, without having to shut down the production database or put tablespaces into hot backup mode.
2. Both systems are HP Itanium boxes with differing numbers of CPUs and RAM. Those differences have been taken into account in the init.ora file for the DB instances.
3. The test and production instances are using a SAN to hold the following file systems: ora_redo1, ora_redo2, ora_archlog, oradata10g. The test instance is using SAN snapshots (HP EVA series SAN) of the production file systems to pull the data over when needed. The problem is that the only window to do this is when the production system is down for nightly maintenance which is about a 20 minute period. I want to escape this limitation.
What I've been doing is using the HP SAN to take snapshots of the file systems on the production system mentioned above. I do this while the production DB is up and running. I then import those snapshots into the test system, run an fsck to ensure file system integrity, then start up the Oracle instance as follows:
startup mount
Then I run the following query I found on line to determine the current redo log:
select member from v$logfile lf , v$log l where l.status='CURRENT' and lf.group#=l.group#;
Then I attempt to run a recovery as follows:
recover database using backup controlfile until cancel;
When prompted, I enter the path to the first of the current redo logs and hit enter. After waiting, sometimes it says that the recovery completed, other times it stops saying there was an error and that more files are needed to make the DB consistent.
I took the above route because doing a recover until time (which is what I really want to do) kept prompting me for the next archive log in sequence that didn't yet exist when I took the SAN snapshot. Here was my recover until time command:
recover database until time 'yyyy-mm-dd:hh:mm:ss' using backup controlfile;
What I would like to do is take the SAN snapshot and then recover the database to about a minute before the snapshot using the archive logs. I don't want to use RMAN since that seems to be overkill for this purpose. A simple recovery to a specific point in time seems to be all that is needed and I have archive logs which, I assume, SHOULD help me get there. Even if I have to lose the last hour's worth of transactions I could live with that. But my tests setting the specific time of recovery to even 12 hours earlier still resulted in a prompt for the next, non-existent archivelog.
I will also note that I even tried copying the next archive log over once it did exist and the recovery would then prompt me for the next archive log! I will admit right now that I really don't know a whole lot about Oracle or DBs, but it's my task to try and make it possible to "refresh" the test DB with the most recent data with no impact on the production DB.
The reason I don't want to use hot backup mode is that I don't know the DB schema other than there are probably 58 or more tablespaces. The goal is to use SAN snapshots for their speed instead of having to take RMAN files and copy them to the test instance. I'm sure I'm not the only person who has ever tried this. But most of what I've found on line refers to RMAN, hot backup mode, or down time. The first two don't take advantage of SAN snapshots for a quick swap of all the Oracle file systems and I can't afford downtime other than that window at night. Is there some reason that the recover to time didn't work even though I have archive logs?
One final point. The recover until cancel actually worked a couple of times, but it seems to be sporadic. It likely has something to do with what was happening on the production DB when I created the SAN snapshots. I actually thought I had a solution with recover until cancel last week until it didn't work three times in a row.

I haven't completely discounted it but it seems like I would need to back up to files, then restore from files. I don't want to do that. I want a full file system level SAN snapshot that I can just drop into place. The does work when the production base is shut down. However, considering that I do have archive logs, shouldn't it be possible to use them to recover to a specific scene without having to do an RMAN backup at all? It seems that doing an RMAN backup/recovery would just make this whole process a lot longer since the DB is 160 gigs in size (not huge, but the dump would take more time than I would like). With a SAN snapshot, if I can get this to work, I'm looking at about a 15-20 minute period of time to move the production DB over to test.
Since you are suggesting that RMAN may be a better approach I'll provide more details about what I'm trying to do. Essentially this is like trying to recover a DB from a server that had its power plug pulled. I was hoping that Oracle's automatic recovery would do the same thing it would do in that instance. But obviously that doesn't work. What I want to do is bring over all the datafiles, redo logs, and archive logs using the SAN snapshot. Then if possible use some aspect of Oracle (RMAN if it can do it) to mount the database, then recover to a specific time or SCN if using RMAN. However, when I tried using RMAN to do it, I got an error saying that it couldn't restore the data file because it already existed. Since I don't want to start from scratch and have RMAN rebuild files that I've already taken snapshots of (needless copying of data), I gave up on the RMAN approach. But, if you know of a way to use RMAN so that it can recover to a specific incarnation without needing to runm a backup first, I am completely open to trying it.

Archive Logs using more Space

May be you can help me out.
I have resized my redo logs, and when I checked my file system the log switchs were less frequent as expected, however if compared to the same period when the redo logs were smaller(1 hour earlier) the archive logs (db in archive log mode) had doubled the usual capacity on the file system.
Now Im sure Im being stupid here.
I had expect the file system usage would be the same but have bigger but fewer archive logs. I am sure the through put is the same. Is my theory correct, even through the facts are not matching up?

Thanks for confirming my thoughts. I was very surprised when the file system usage had changed and the last change was redo log size adjustment.
It is one of though times when you were the last to touch it and somthing is different you get the blame.
I suspect some process is being run that is generally not start at this time of day. just an unfortunate coincidence.
thanks I thought I was going mad.

Cleanup job to remove archive logs automatically through OEM Grid control

Hi All,
I am working on 11gR2 3node RAC database. we have enabled archivelog mode for the databases and don't have any backup processes (like rman) and not using ASM.
Please let me know how to cleanup the old archivelogs automatically through oem Grid control.
I have some idea how to do it in standalone database, but not sure how it works in RAC environment through OEM. Please let me know.
Thanks in advance.

Hari wrote:
Thanks for your reply and The requirement is, put the DB in archive log mode and cleanup the old archive logs which is more than 5days. We are doing this because of space issue and don't have backup for these files and the DB must be in archive log mode.
I have few question here.
1. Is it must to take the backup of the archive log files and before delete them?No, but if you aren't backing up, why create the archivelogs in the first place?
2. If i delete them without backup, what is the negative impact?If you aren't backing up the database in the first place (as you stated in an earlier post) then it really doesn't matter what you do with the archivelogs as they are worthless anyway.
3. What is the recommended process to do it?My recommendation is you first start using rman to backup the database
4. I need to setup this process through OEM grid control.
Please let me know.
Thanks,
HariIt all begs the question which has already been asked and you avoided answering . . . if you are not taking backups, why bother archiving? The archive logs have ZERO VALUE outside of a consistent backup strategy. So how is it you have a 'requirement' to run in archivelog mode but no requirement for backups?
Edited by: EdStevens on Dec 2, 2011 9:30 PM

Full backup and backup archive logs

Hello,
today in the early morning i did backup of my db with :
RMAN> backup as COMPRESSED BACKUPSET DATABASE format '/backup/%d_t%t_s%s_p%p';This command created two files :
[oracle@p1 backup]$ ls -l
total 1132680
-rw-r----- 1 oracle oinstall 1155940352 Sep 14 00:44 TEST_t697508918_s5_p1
-rw-r----- 1 oracle oinstall    2785280 Sep 14 00:44 TEST_t697509873_s6_p1Did i backed up archive logs also with this command ?
If I did not, do i have to i n order to have everything to do complete resterer and recovery ?
Is now to late to backup them?

Can you confirm that this backup will be placed in the FRA, it will backup all datafile, control files, spfile and control files all arhchivle logs and when backup finshes then will delete all archive logs ?+
after running that command yo can confirm it by yourself at RMAN prompt.
RMAN> list backup;
List of Backup Sets
===================
BS Key Type LV Size       Device Type Elapsed Time Completion Time
200     Full    509.78M    DISK        00:01:03     15-FEB-07
        BP Key: 202   Status: AVAILABLE Compressed: NO Tag: TAG20070215T171219
        Piece Name: /disk2/PROD/backupset/2007_02_15/o1_mf_nnndf_TAG20070215T171219_2xb17nbb_.bkp
List of Datafiles in backup set 200
File LV Type Ckp SCN    Ckp Time Name
1       Full 421946     15-FEB-07 /disk1/oradata/prod/system01.dbf
2       Full 421946     15-FEB-07 /disk1/oradata/prod/sysaux01.dbf
3       Full 421946     15-FEB-07 /disk1/oradata/prod/undotbs01.dbf
4       Full 421946     15-FEB-07 /disk1/oradata/prod/cwmlite01.dbf
5       Full 421946     15-FEB-07 /disk1/oradata/prod/drsys01.dbf
6       Full 421946     15-FEB-07 /disk1/oradata/prod/example01.dbf
7       Full 421946     15-FEB-07 /disk1/oradata/prod/indx01.dbf
8       Full 421946     15-FEB-07 /disk1/oradata/prod/tools01.dbf
9       Full 421946     15-FEB-07 /disk1/oradata/prod/users01.dbf
BS Key Type LV Size       Device Type Elapsed Time Completion Time
201     Full    7.98M      DISK        00:00:03     15-FEB-07
        BP Key: 203   Status: AVAILABLE Compressed: NO Tag: TAG20070215T171219
        Piece Name: /disk2/PROD/backupset/2007_02_15/o1_mf_ncsnf_TAG20070215T171219_2xb19prg_.bkp
SPFILE Included: Modification time: 15-FEB-07
SPFILE db_unique_name: PROD
Control File Included: Ckp SCN: 421968       Ckp time: 15-FEB-07
BS Key Size       Device Type Elapsed Time Completion Time
227     30.50M     SBT_TAPE    00:00:11     15-FEB-07
        BP Key: 230   Status: AVAILABLE Compressed: NO Tag: TAG20070215T171334
        Handle: 0bia4rtv_1_1   Media:
List of Archived Logs in backup set 227
Thrd Seq     Low SCN    Low Time Next SCN   Next Time
1    5       389156     15-FEB-07 411006     15-FEB-07
1    6       411006     15-FEB-07 412972     15-FEB-07
1    7       412972     15-FEB-07 417086     15-FEB-07
1    8       417086     15-FEB-07 417114     15-FEB-07
1    9       417114     15-FEB-07 417853     15-FEB-07
1    10      417853     15-FEB-07 421698     15-FEB-07
1    11      421698     15-FEB-07 421988     15-FEB-07list backup will show you everything.
Would then this be incremental level 0 backup ?
yes by default i think so.
so with this i must be able to flasback my database at least 3 day in the past if i understood correctly.
But i am little puzled about purging those flasback data ...
Can you point me please to some link or tell how can i purge logs that are not need for that flashback period... ?
please read this link
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/rpfbdb003.htm#sthref513
Khurram

Cannot reset archive log

Hi
My Oracle 11g is running on Windows Vista.
The database is on archive log mode. I like to set it to no archive log mode.
When I shutdown the database from SQLPLUS [as SYS], it does not start after that!
In Sqlplus, when I issue SHUTDOWN NORMAL - it shuts down database.
When I then run, STARTUP MOUNT
I get this message - ORA-12514: TNS:listener does not currently know of service requested in connect
The only way I can start it again via
net start OracleService<MYDB> command. Then it starts normally - not in mount mode. So I can't issue ALTER DATABASE NOARCHIVELOG command :(
How do I disable archive log?
Thanx for help.

When I then run, STARTUP MOUNT
I get this message - ORA-12514: TNS:listener does not currently know of service requested in connectSQL*net is not required to start the DB.
Log onto the system as the Oracle s/w owner & do the following:
set
sqlplus
/ as sysdba
startup mount
CUT the line above & paste into command window
CUT commands & results and PASTE back here

Archive logs cutting early

Similar Messages

Maybe you are looking for