Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: ORA-16014: log 3 sequence# 492 not archived
On Thu, 03 Mar 2005 07:14:29 -0800, ejsanchez wrote:
>
> after that everything is working again, the problem is that I can't
> issue a full import because of the redologs got out of space or
> something...
> Also, yesterday we didn't tried a full import, nobody is using the
> database and
> today we are facing the same problem, but with the log 2
> any advice on this?
> thanks in advance...
Well, defining parameters like log_archive_dest_1...10 and reading about them in the reference manual is very complicated. To avoid that nuisance, you can also do the following:
CONNECT / AS SYSDBA
STARTUP FORCE NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "ORACLE" RESETLOGS NOARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 454
LOGFILE
GROUP 1 '/oradata/10g/oracle/redo01.log' SIZE 64M, GROUP 2 '/oradata/10g/oracle/redo02.log' SIZE 64M, GROUP 3 '/oradata/10g/oracle/redo03.log' SIZE 64MDATAFILE
'/oradata/10g/oracle/system01.dbf', '/oradata/10g/oracle/undotbs01.dbf', '/oradata/10g/oracle/sysaux01.dbf', '/oradata/10g/oracle/users01.dbf', '/oradata/10g/ORACLE/datafile/o1_mf_lobs_0szv1bfw_.dbf', '/oradata/10g/ORACLE/datafile/o1_mf_indx_0szv4dbg_.dbf', '/oradata/10g/ORACLE/datafile/o1_mf_statspac_0t032zh4_.dbf'CHARACTER SET WE8ISO8859P1
-- A clean tie attracts the soup du jour.Received on Thu Mar 03 2005 - 22:42:44 CST