Archivelog VS Noarchivelog

In order to perform an online Full database backup. The database has to be in ARCHIVELOG mode. Am I right ?
I just wanna find out why the Database canot be in NOARCHIVELOG to perform Full database backup ?
What happen if i try to perform Full backup while my database is in NOARCHIVELOG ?
Thanks

In order to perform an online Full database backup. The database has to be in ARCHIVELOG mode. Am I right ?..YES
I just wanna find out why the Database canot be in NOARCHIVELOG to perform Full database backup ? ..due to the following reasons;
When you want to take the online backup you need to keep tablespaces in backup mode, which is only possible if your DB is in Archivelog mode. You can't put tablespace in backup mode if your DB is in noarchive log mode.
you can also take online backups via RMAN utility, if your db is in archivelog mode.
What happen if i try to perform Full backup while my database is in NOARCHIVELOG ?Say, your database in noarchive mode and you have copied all you datafiles via copy command or anything. If any of the datafile got corrupted you just can't copy only that particular datafile to recover your database. The copies which you take are invalid and useless without archivelogs.
SJH
OCP DBA

Similar Messages

Changing database to noarchivelog mode during impdp

Hi Guys,
I am using Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production on RHEL5.
I am in the middle on the impdp and I want my database to run on noarchivelog as it creates a lot of archivelogs.
Will it be proper if I stop the import:
e.g Import> STOP_JOB=IMMEDIATE
and shutdown the database put the database on noarchivelog mode.
then opne database and
impdp hr/hr@mydb ATTACH=myfulljob Will these work fine?
Or should I execute:
alter system archive log stop;
Please Help !!!!!!!!!!!

Vinod Dhandapani wrote:
Running the database in Noarchivelog mode means you should be ready to lose data incase there is any crash. I would recommend you to change the size of the redologs so that it will not create frequent archivelogs. Which does nothing about the space required for the archivelogs. If you are generating redo at the rate of 1gb/hour, you will consume archivelog dest space at the rate of 1gb/hour. Doesn't matter if those files are 10mb each or 100mb each.
If space is the problem then use a shell script to move the archivelog to another location (Tape)....And hopefully that shell script is invoking rman to do the work, so that in the event of recovery, rman will know that backups were taken and where they are located.
>
Incase you want to convert the database from archivelog to noarchivelog, follow the steps provided in the following link.
http://racadmin.blogspot.com/2011/06/convert-archivelog-mode-to-noarchivelog.html
Thanks

ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode

Hi All
Its my first time to use RMAN in our ERP EBSR12
our database version is 11g
Please help how to resolv and make successfully backup
RMAN> backup database;
Starting backup at 24-JAN-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 01/24/2011 11:18: 25
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
channel ORA_DISK_1: starting piece 1 at 24-JAN-11
channel ORA_DISK_1: finished piece 1 at 24-JAN-11
piece handle=/oracle/mybackup_db/PROD2/backupset/2011_01_24/o1_mf_ncnnf_TAG20110 124T111824_6msvw4cv_.bkp tag=TAG20110124T111824 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 01/24/2011 11:18: 25
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
RMAN>
Thanks

ORA-19602: cannot backup or copy active file in NOARCHIVELOG modeIs your database in archivelog or noarchivelog mode?
How to Turn Archiving ON and OFF [ID 69739.1]
Please also see these docs/links.
ORA-19602 Using RMAN to Backup Database [ID 246183.1]
COLD RMAN backup fails: Ora-19602 even after SHUTDOWN IMMEDIATE and STARTUP MOUNT [ID 373828.1]
Backup & Recovery
http://www.oracle.com/pls/db112/portal.portal_db?selected=14&frame=#backup_and_recovery
Thanks,
Hussein

Question about import in archive log mode

Hello.
I am a developer, I have ordered to write a script that makes the import of a schema of a database (release 9.2.0.7). That import will be done once a day. I have seen that in my development environment the import creates 54 archivers files (10M aprox. each), that means more that half a Gb a day, it seems too much to me.
I cannot see why all those archivers can be useful. Would a good way of proceeding the following?
1. Forcing an archiver just before the import (I do not know how to do that) so that a backup could be done to the state before the import.
2. Disabling archive log mode during the import and enabling it just after the import (I do not know how to do that).
3. Forcing a new archiver just after the import (I do not know how to do that).
Thanks in advance.

540M is not that much.
One would question why you need to import every day,
there must be better ways to do this.
The three steps you propose look like an awful
scenario, as it would require the database to switch
from archivelog to noarchivelog and vice versa.
This would require the database to close twice a
day.
The scenario is also incomplete as one would need to
take a backup after the import
If you can convince your DBA to close the database
twice a day, he should write the script, which he can
easily derive from the docs.
But likely he will visit Billy Verreynne to borrow
his lead pipe, and rightly so ;)
Sybrand Bakker
Senior Oracle DBAThanks for the answer.
A few things:
- Sorry for my ignorance, I have no experience in database backups, I do not understand why I need to backup just after the import.
- That database is not critical, it is just for a team who will test on that database several applications, so the database will only need to be open during the office schedule.
- I have no dba. The client has a dba for several databases but I have no contact with him/her nor my boss has.

Regarding force archiving

Dear all,
When I need to take the backup of latest archive log file, which commad from the below two is better
1. ALTER SYSTEM ARCHIVE LOG CURRENT;
2. ALTER SYSTEM SWITCH LOGFILE;
Does both the commands give the same result ?
Regards,
Charan

Hi Charan;
alter system switch logfile -- > switches to the next logfile, irrespective of what mode the database is in ARCHIVELOG or NOARCHIVELOG mode.If in archivelog mode alter system swicth logfile will generate the archive of the redolog that was switched.
alter system archive log current --> Here oracle switches the current log and archives it as well as all other unarchived logs.It can be fired on only the database which is in ARCHIVELOG mode.
[http://download.oracle.com/docs/cd/B10501_01/server.920/a96519/backup.htm]
Source:
Diff between switch logfile and archive log current
Regard
Helios

ORA-00255: error archiving log

When i changing noarchivelog mode on archivelog and online logs must archiveing
I send this message from trace file.
*** SESSION ID:(3.1) 2005.02.15.12.09.15.000
ARCH: Archival stopped, error occurred. Will continue retrying
ARCH:
ORA-00255: error archiving log 1 of thread 1, sequence # 51
ORA-00312: online log 1 thread 1: 'WORK:ORANW803\DATABASE\TEST\LOG1TEST.ORA'
ORA-00312: online log 1 thread 1: 'WORK:ORANW803\DATABASE\TEST\LOG2TEST.ORA'
ORA-00334: archived log: 'WORK:ORANW803\DATABASE\TEST\ARCHIVE\TESTT001S00051.ARC'
ORA-00270: error creating archive log WORK:ORANW803\DATABASE\TEST\ARCHIVE\TESTT001S00051.ARC
ORA-19504: failed to create file "WORK:ORANW803\DATABASE\TEST\ARCHIVE\TESTT001S00051.ARC"
ORA-09200: sfccf: error creating file
OSD-02070: unable to create file (OS 1)
Tue Feb 15 12:10:02 2005 -

well, your question was not clear, though, what I understand is, you want to move your DB from archivelog mode to NOARCHIVELOG mode, right?
First of all, check whether do you have sufficient space to archiving on your hard-disk.
Secondly, try the following, alter system archive log all;
also, give the steps that you are implementing or implemented to switch from ARCHIVELOG TO NOARCHIVELOG.
SJH
OCP DBA

SID changing

Hi all,
We are planning to create a new test system from Dev and in process we have to change the SID and Logical name of the system, how to change the SID and LSN. After creating the syetm we have to upgrade the system is itpossibule to change he Logical system name after upgrade thru BDLS.
Please suggest..
Thanks,
Subhash.G

Hi Subhash,
You need to backup the system and reinstall - as homogeneous system copy. Check the bellow URL and notes 224266,11692.
http://service.sap.com/systemcopy
Any how this is the another simple method you can follow(if you are expert in DBA)
First of all, you need to make a full offline backup of your system (DB + FS).
As oraSID, start sqlplus session
SQL> alter database backup controlfile to trace;
This command will generate a trace file (available in /oracle/SID/saptrace/usertrace) which will contain a script to recreate you database controlfile.
Edit this script, keep the part ARCHIVELOG or NOARCHIVELOG, replace every old-SID with new-SID.
Save the script as cntrlfileSID.sql
Shutdown SAP and oracle.
Umount all SID-name-related filesystems, change them and re-mount everything.
(You can also use soft-links to gain time)
Change user SIDadm and oraSID (user name, groups, limits, environment profile).
Change SAP profile files in /sapmnt/SID/profile.
Modify the soft links in /usr/sap/SID/SYS ...
You will need to relink all oracle software (as oraSID)
As oraSID recreate your controlfile with the script cntrlfileSID.sql
=>use the resetlogs option to open you DB
Check oracle is OK
Modify you OPS$ users
This should work for an ABAP standalone system.
Good luck
Hari.
PS: Points are welcome.

Export is not / Backup

I found in oracle docs that export is the logical backup my question is can we use this as Backup. If this used for small database which database is small, are not they critical?. And if i have export what may be the corruption,worst senerio or how long i can keep it for import.
Since I can make large files(more than 50gb) export and keep it for years, then can i expect them to import correctly.
finally, should i rely on export.exp or expdp.

Hi,
>>If this used for small database which database is small, are not they critical?
Well, If so, I think there is no problem in make logical backups depending of the purpose of this database (production ?, development ?) but they need to be validated. (A backup is just a backup when it is valid). Otherwise, you need to know whether the users that use this database can support a lost of data in case of a media failure or corruption of some important database files, because in this case, no way in recover this database because you just have an option to create the database again and import your last valid logical backup. By the way, this database is working in ARCHIVELOG or NOARCHIVELOG mode ?
Cheers

Hot backup cloning in ebs r12

HI i was doing the hot backup cloning in ebsr12.
i have backed up the control files and datafiles and the trace file also.
i have done the steps till copying the db and apps tier.
next is
2) Create the target database control file manually
Open the backed up control file
a. remove all lines before the startup nomount statement
b. Modify the REUSE to SET
c. Modify Source DB SID to Target SID (Here PROD to TEST)
d. Modify NORESETLOGS TO RESETLOGS
e. delete all lines after the CHARACTER SET statement
i am not sure about editing the control file ....
I am a started in db's
can anyone help me in this?

HI i was doing the hot backup cloning in ebsr12.
i have backed up the control files and datafiles and the trace file also.
i have done the steps till copying the db and apps tier.Looks like you are doing cold backup and not hot backup! Was the database cleanly shutdown before copying the database files?
a. remove all lines before the startup nomount statementCorrect -- Or you could leave those lines if they are commented.
b. Modify the REUSE to SETCorrect.
c. Modify Source DB SID to Target SID (Here PROD to TEST)Correct.
d. Modify NORESETLOGS TO RESETLOGSCorrect.
You will also have to change ARCHIVELOG to NOARCHIVELOG -- If your source instance is in ARCHIVELOG mode.
e. delete all lines after the CHARACTER SET statementKeep the lines/command that open the database and create the temporary tablespace.
Thanks,
Hussein

Accidently Deleted Archive Logs

Hi all,
I'm no expert and have a poor knowledge in Oracle 9i and I look forward for a possible solution from all of you.
Previously, we had our Oracle 9.0.2 database running in NOARCHIVELOG mode. Last week, we have changed it to ARCHIVELOG mode and we haven't done any backup since we're still waiting for our vendors to set up the backup software.
As of today, we've noticed that the archive logs were increasing, and resulted in a low disk space. We have moved the archive logs to another location as a backup option, in order to free up the disk space. While doing so, we have accidently deleted a few portion of the archive logs. Following are the archive logs (both available and missing) since the DB was switched to ARCHIVELOG mode :
ARCH05507.LOG ~ ARCH05915.LOG <-- AVAILABLE
ARCH05916.LOG ~ ARCH05926.LOG <-- MISSING!!!
ARCH05915.LOG ~ onwards <- AVAILABLE
We would like to re-locate the database to a different server. My questions are as follows :
1. Is it possible to recover the database although there are a few missing archive log files?
2. I've heard about incomplete recovery, can i use this option to do so?
3. What is the worst case scenario, or possible option that we could use?
4. Is there any way to disregard the missing archive logs, and apply to the database using only the available archive logs?
Please help. Thank You
Sathyan Ram

Ivan,
As you mentioned, to perform a cold backup, you will need to shutdown the database, and that the same concept can be applied when changing from archivelog to noarchivelog. But I would like to know what are the consequences I will be facing if I do so? Will there be data consistency issues? Will the database fail to open during the next clean restart?
As for your second question, we assumed that changing no noarchivelog will make it easier for us to re-locate the database to another server, i.e. the process of setting up the database will be much easier. Then we can switch the DB back to archivelog.
The actual problem I'm facing at the moment is that, after we encountered the missing archive logs (i.e. Monday), we're not in a situation to perform a COLD backup because of our corporate restrictions. Either way, I'm not confident performing a HOT backup, because I haven't got any experience, neither do I have any test database to perform such tasks. The only possible time we could perform a COLD backup is on this weekend (Saturday/Sunday), but I believe this will be lead to a total of 5 days of data loss. (The missing log files started on Monday, and production ends on every Friday)
I've came across an article (Terry Sutton, Database Sepcialists, Inc.) regarding on how to recover an Oracle Database with Missing Archived Logs. But this method is totally not supported/recommended by Oracle, and will lead to database inconsistency issues. Considering my situation, will I be able to use this method instead?
Thank You.
Sathyan Ram

数据库归档模式与非归档模式下各种加载数据方式对redo的影响

redo
重做日志文件（redo log file）对Oracle数据库来说至关重要，它们是数据库的事务日志。Oracle维护着两类重做日志文件：
在线（online）重做日志文件和归档（archived）重做日志文件。这两类重做日志文件都用于恢复；其主要目的是，
万一实例失败或介质失败，它们就能派上用场。
如果数据库所在主机掉电，导致实例失败，Oracle会使用在线重做日志将系统恰好恢复到掉电之前的那个时间点。
如果磁盘驱动器出现故障（这是一个介质失败），Oracle会使用归档重做日志以及在线重做日志将该驱动器上的
数据备份恢复到适当的时间点。
归档重做日志文件实际上就是已填满的"旧"在线重做日志文件的副本。系统将日志文件填满时，
ARCH进程会在另一个位置建立在线重做日志文件的一个副本，也可以在本地和远程位置上建立多个另外的副本.
如果由于磁盘驱动器损坏或者其他物理故障而导致失败,就会用这些归档重做日志文件来执行介质恢复.
Oracle拿到这些归档重做日志文件，并把它们应用于数据文件的备份，使这些数据文件能与数据库的其余部分保持一至.
归档重做日志文件是数据库的事务历史。
测量redo
redo管理是数据库中的一个串行点.任何Oracle实例都有一个LGWR，最终所有事务都会归于LGWR，要求这个进程管理它们的redo,
并COMMIT其事务,LGWR工作越忙,系统就会越慢.通过查看一个操作会生成多少redo,并对一个问题的多种解决方法进行测试,
可以从中找出最佳的方法。
与redo有关的视图
V$MYSTAT，其中有会话的提交信息
V$STATNAME，这个视图能告诉我们V$MYSTAT中的每一行表示什么（查看的统计名）。
查询redo大小的语句
SELECT a.NAME,
b.VALUE cur_size_byte,
round(b.VALUE / 1024, 3) || 'KB' cur_size_kb
FROM v$statname a, v$mystat b
WHERE a.statistic# = b.statistic#
AND lower(a.NAME) LIKE '%' || lower('redo size') || '%'
数据库归档模式
数据库归档用来保存redo的日志文件副本,一般安装时默认未开启数据库的归档模式。
在NOARCHIVELOG模式的数据库中,除了数据字典的修改外,CREATE TABLE不会记录日志.
如果你想在NOARCHIVELOG模式的数据库上看到差别,可以把对表T的DROP TABLE和CREATE TABLE换成DROP INDEX和CREATE INDEX。
默认情况下,不论数据库以何种模式运行，这些操作都会生成日志。
因为不同的模式可能导致不同的行为。你的生产系统可能采用ARCHIVELOG模式运行.
倘若你执行的大量操作在ARCHIVELOG模式下会生成redo,而在NOARCHIVELOG模式下不会生成redo,
你肯定想在测试时就发现这一点，而不要等到系统交付给用户时才暴露出来！
查看是否归档
查看数据库是否开启归档
select name,log_mode from v$database;
启用归档
startup mount
alter database archivelog;
alter database open;
禁止归档
shutdown immediate
startup mount
alter database noarchivelog
alter database open
force logging(强制日志)模式：
如果数据库强制日志模式开启后,则Oracle无论什么操作都进行redo的写入。
查看强制日志模式
通过
select force_logging from v$database
可以看到当前数据库是否开启了强制日志模式状态
开启强制日志模式
如果未开启数据库强制日志模式（默认未开启），则可以通过
alter database force logging开启,之后Oracle无论什么操作都进行redo的写入,不依赖于数据库的归档模式等其他因素.
关闭强制日志模式
如果已经开启了数据库强制日志模式，则可以通过
alter database no force logging关闭强制日志模式。
使数据库恢复先前的设置,数据库是否写入redo由数据库的归档模式等其他因素决定
disable_logging
那么在Oracle内部还存在一个内部参数：_disable_logging 默认是false
通过更改为true可以让Oracle在修改表中的记录的时候完全不记录redo,这个参数要甚用,平时,我们只作为性能测试用。
查看：show parameter disa /disable/_disable_logging
开启：alter system set "_disable_logging"=true scope=both;
禁用：alter system set "_disable_logging"=false
表的归档模式
查看表的logging模式
查看表是否是logging状态用如下SQL:
select table_name,logging from dba_tables where table_name='tablename';
修改表的logging模式
修改表的logging状态sql:
alter table table_name nologging/logging
减少redo写入
本节所讲的都是当数据库未开启强制日志模式时的操作。
对象的操作在执行时会产生重做日志,采用某种方式,生成的redo会比平常(即不使用NOLOGGING子句时)少得多.
注意,这里说"redo"少得多,而不是"完全没有redo".所有操作都会生成一些redo,不论数据库的日志模式是什么,
所有数据字典操作都会计入日志。
如何减少redo
create table时减少redo的方法
创建表时crate table as加入nolongging选项减少redo，格式如下
create table [table_name] nologging as [select表达式]。
insert into减少redo的方法
insert 大批量数据时加入/*+append */选项减少redo写入,格式如下
insert /*+append */ into [table_name] [select表达式]
数据库归档模式下生成redo规则
create table时nologging效果
归档模式下创建的表，默认为logging模式。
创建表时crate table as加入nolongging选项减少redo写入明显
验证
下面比较以下两种create table as时产生的redo size量。
SELECT a.NAME,
b.VALUE cur_size_byte,
round(b.VALUE / 1024, 3) || 'KB' cur_size_kb
FROM v$statname a, v$mystat b
WHERE a.statistic# = b.statistic#
AND lower(a.NAME) LIKE '%' || lower('redo size') || '%'
查询当前的重做日志大小记录下来
create table test_1 as select * from test;
SELECT a.NAME,
b.VALUE cur_size_byte,
round(b.VALUE / 1024, 3) || 'KB' cur_size_kb
FROM v$statname a, v$mystat b
WHERE a.statistic# = b.statistic#
AND lower(a.NAME) LIKE '%' || lower('redo size') || '%'
查询当前的重做日志大小减去前面记录下来的值计算刚才这个操作产生的redo大小标记为redo_1
SELECT a.NAME,
b.VALUE cur_size_byte,
round(b.VALUE / 1024, 3) || 'KB' cur_size_kb
FROM v$statname a, v$mystat b
WHERE a.statistic# = b.statistic#
AND lower(a.NAME) LIKE '%' || lower('redo size') || '%'
查询当前的重做日志大小记录下来
create table test_2 nologging as select * from test;
SELECT a.NAME,
b.VALUE cur_size_byte,
round(b.VALUE / 1024, 3) || 'KB' cur_size_kb
FROM v$statname a, v$mystat b
WHERE a.statistic# = b.statistic#
AND lower(a.NAME) LIKE '%' || lower('redo size') || '%'
查询当前的重做日志大小减去前面记录下来的值计算刚才这个操作产生的redo大小标记为redo_2
比较redo_1和redo_2的大小就知道crate table as加入nolongging或不加nologging选项的区别了
insert into时加入append效果
表模式logging
当表模式为logging状态时,无论是append模式还是no append模式,redo都会生成,即加入append选项无法生效。
验证
下面比较以下两种insert时产生的redo size量,可以看出redo量是差不多的。
计算重做大小的方法与上面的一样就不说了
1、insert /*+append */ into test_1 select * from test;
commit;
2、insert into test_1 select * from test;
commit;
表模式nologging
当表模式为nologging状态时,只有加入append模式会明显减少生成redo。
验证
1、insert /*+append */ into test_1 select * from test;
commit;
2、insert into test_1 select * from test;
commit;
数据库非归档模式生成redo规则
create table 使用nologging对产生redo的影响
非归档模式下创建的表，默认为nologging模式。
在NOARCHIVELOG模式的数据库中，除了数据字典的修改外，CREATE TABLE不会记录日志。
因此创建表时（crate table as）加入nologging选项减少redo写入不明显,即nologging选项加不加都差不多
验证
下面比较以下两种create table as时产生的redo size量。
create table test_1 as select * from test;
create table test_2 nologging as select * from test;
insert into时append效果
表模式logging
当表模式为logging状态时,加入append模式明显减少生成redo,而no append模式下不会减少生成。
验证
insert /*+append */ into test_1 select * from test;
commit;
insert into test_1 select * from test;
commit;
表模式nologging
当表模式为nologging状态时，append的模式会减少生成redo,而no append模式不会减少生成。
验证
insert /*+append */ into test_1 select * from test;
commit;
insert into test_1 select * from test;
commit;

Good Post! 代码注意用code模式，
如何使用code模式
请参考如何在OTN中文技术论坛提一个问题？

Trun off archiving without bouncing the database

Hello,
Is there a way to turn off archive log mode without bouncing the database in 9i? I know we can turn off automatic archival with out bringing down the db.
Thanks.

Hi,
One thing is ARCHIVELOG and NOARCHIVELOG, another thing is automatic or manual archiving. When the Database is configured in ARCHIVELOG mode, you can dinamically turn on or off automatic archiving, but you cannot switch from ARCHIVELOG to NOARCHIVELOG (or viceversa) without shutting down the DB : this change has to be done when the DB is mounted but not open.

DATAWAREHOUSING BACKUP PLAN

Hi,
I've DW enviornment and it's growing. What is the best practice for DW DB backup ? Does this DB required to run into ARCHIVED log mode.
Thanks

Hello,
It depends on your industry, directive from mangement (or client) and policies of the company. I have experienced both using archivelog and noarchivelog mode but both the industries were far apart. In financial based DW, we were using ARCHIVELOG mode and auditing enabled (I thnk you know the reason why :) ). In this case there was full backup periodically o monthly basis, and incremental RMAN backup taken every night.
In telecom based DW client was interested in end of month reports for finding revenue (like finding gold) so it was decided to use NONARCHIVELOG mode. We decide to backup datafile (nightly batches) on tape drives and use that for disaster recovery (75 Million rows -every nightly batch and 6 month retention and size for 1 day was around ~25 - 30 G). SLA for disaster recovery should be discussed with client/customer to determine the time frame for recovery.
Question: What's your sector is? Finance, telecom, retail,...? Is data used for just generating reports or more than that? Aer there any company policies regarding data security and retention? There are whole slew of similar questions you should come up to decide what is the best approach for you.
Regards

Adpatch in wait status

Pls help.
My patching has stopped for a long time.
When I used adctrl to show status of the workers, i got this:
Control
Worker Code Context Filename Status
1 Run AutoPatch R115 FIICAT1S.pls Running
2 Run AutoPatch R115 Wait
3 Run AutoPatch R115 FIICMSCS.pls Running
4 Run AutoPatch R115 FIICMT1S.pls Running
Review the messages above, then press [Return] to continue.
Why is 2 in wait status?
What do I have to do to get it working again? The log is not showing anything.
During patching , I changed the database from archivelog to noarchivelog mode. Could this be the problem?
Thanks

During patching , I changed the database from archivelog to noarchivelog modeDuring or before patching? If you have done this before patching then this should not be an issue.
Check the alert.log file for any errors. Also, verify that your tablespaces have sufficient space.

Archivelog VS Noarchivelog

Similar Messages

Maybe you are looking for