ORA-1578 Cant open Database.

Hi. i am recieving the Error ORA-1578 CANT OPEN DATABASE.
Please tell me how i can rebuild the database.

a 1578 is often accompanied by another error message number that tells us why it can't open the database.
in any case - search for the alert log (alert.log or alert_sid.log).
More than that we can't say until we get such minor tidbits as operating system and version of oracle, as well as a cut and paste of the console session during which you are attempting to open the system.
by the way - if you have support, you should have already opened a service request. unlimited oracle support calls are free with the support contract.

Similar Messages

Can not open Database

HI,
When I try to open the database it gives an error message
ORA 604, Cannot open database.
I am using Personal Oracle 8. What should i do now to open the database.
Thanks in Advance
- Muks

check the path of init.ora.
find the svrmgr*.exe file.
run it.
connect as internal or sys.
and then
write : startup pfile = <path of init.ora>\<init.ora>
null

Getting ora-01113 error while opening Database after recovery

HI all,
we have a test database. I lost my entire database including DBFs, controlfiles, Archived logs, redo log files.
But I have a hot backup copy of the lost database.
I tried to recover database using backup copy
I restored my control files and all dbfs and then when i tried to recover database I got the following message
RMAN-00571: ==============================
RMAN-00569: =ERROR MESSAGE STACK FOLLOWS =
RMAN-00571: ===============================
RMAN-03002: failure of recover command at 04/01/2005 14:14:43
RMAN-06054: media recovery requesting unknown log: thread 1 scn 32230460
still i tried to open database resetlogs but i got following eror
RMAN> alter database open resetlogs:
ORA-01113: file 5 needs media recovery
ORA-01110: data file 5: C:\DB11\ORADATA\DB11\system01.dbf
I dont have any redo logs and archivelogs. Can anyone help me how to open the database
thanks and regards
VENKAT

no there is no other way allowresetlogs_corruption is one of the last resort unless oracle dont recommend,usually you got this error when restored datafile is far behind then others datafile CKPT SCN+COntrolfile CKPT SCN header.
SQL> select controlfile_change#,checkpoint_change#
2    from v$database
3 /
CONTROLFILE_CHANGE# CHECKPOINT_CHANGE#
             675632             675775
SQL> select substr(name,1,51) fname,checkpoint_change#
2    from v$datafile_header
3 /
FNAME                                               CHECKPOINT_CHANGE#
F:\ORACLE\PRODUCT\10.1.0\ORADATA\PROD\SYSTEM01.DBF              675775
F:\ORACLE\PRODUCT\10.1.0\ORADATA\PROD\UNDOTBS01.DBF             675775
F:\ORACLE\PRODUCT\10.1.0\ORADATA\PROD\SYSAUX01.DBF              675775
F:\ORACLE\PRODUCT\10.1.0\ORADATA\PROD\USERS01.DBF               675775
F:\ORACLE\PRODUCT\10.1.0\ORADATA\PROD\USERS02.DBF[b]               675418user02.dbf CKPT SCN header 675418 is earlier/oldest CKPT SCN header to others datafile as well to controilfile CKPT SCN header.
You will have to apply enough redo to that datafile either from archivelog or from online redo log file,if you cant then no way you can open the database except using allowresetlogs_corruption with the oracle recommendation.
Think why archivelog backup ,database backup and online redo log file, controlfile redundency is recommended.
Khurram

Cant open the database

hi
i ve two server... test1 and test2
i have shutdown instance and copy all files redo, control , and init from TEST1 TO TEST2 at same location.
now i cant up the database..
i tried to backup controlfile to trace of TEST1 and tried to open database on TEST2
but it i cant open the db
here is some example ...
SQL> CREATE CONTROLFILE REUSE DATABASE "AMD751" RESETLOGS NOARCHIVELOG
2 MAXLOGFILES 20
3 MAXLOGMEMBERS 5
4 MAXDATAFILES 999
5 MAXINSTANCES 1
MAXLOGHISTORY 292
6 7 LOGFILE
8 GROUP 1 (
9 '/oravl04/oradata/amd751/rdl/redo01a.log',
10 '/oravl03/oradata/amd751/rdl/redo01b.log'
11 ) SIZE 50M,
12 GROUP 2 (
13 '/oravl04/oradata/amd751/rdl/redo02a.log',
14 '/oravl03/oradata/amd751/rdl/redo02b.log'
15 ) SIZE 50M,
16 GROUP 3 (
'/oravl04/oradata/amd751/rdl/redo03a.log',
17 18 '/oravl03/oradata/amd751/rdl/redo03b.log'
19 ) SIZE 50M
-- STANDBY LOGFILE
20 21 DATAFILE
22 '/oravl04/oradata/amd751/dfl/system01.dbf',
23 '/oravl04/oradata/amd751/dfl/undotbs01.dbf',
24 '/oravl04/oradata/amd751/dfl/sysaux01.dbf',
25 '/oravl04/oradata/amd751/dfl/users01.dbf'
26 CHARACTER SET AL32UTF8
27 ;
-- Commands to re-create incarnation table
-- Below log names MUST be changed to existing filenames on
-- disk. Any one log file from each branch can be used to
-- re-create incarnation records.
-- Recovery is required if any of the datafiles are restored backups,
-- or if the last shutdown was not normal or immediate.
RECOVER DATABASE USING BACKUP CONTROLFILE
-- Database can now be opened zeroing the online logs.
ALTER DATABASE OPEN RESETLOGS;
Control file created.
SQL> SQL> SQL> SQL> SQL> SQL> SQL> ORA-00279: change 2797632 generated at 09/22/
2009 12:36:30 needed for thread 1
ORA-00289: suggestion : /oravl01/oracle/10.2.0.1/dbs/arch1_1_698243790.dbf
ORA-00280: change 2797632 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log '--'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00308: cannot open archived log 'ALTER'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00308: cannot open archived log
'/oravl01/oracle/10.2.0.1/dbs/arch1_1_698243790.dbf'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-00308: cannot open archived log
'/oravl01/oracle/10.2.0.1/dbs/arch1_1_698243790.dbf'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
SQL> select open_mode from v$database;
OPEN_MODE
MOUNTED
SQL> alter database noarchive log;
alter database noarchive log
ERROR at line 1:
ORA-02231: missing or invalid option to ALTER DATABASE
SQL> alter database noarchivelog;
Database altered.
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '/oravl04/oradata/amd751/dfl/system01.dbf'
============================================
============================================
specially
'/oravl01/oracle/10.2.0.1/dbs/arch1_1_698243790.dbf' this file don exist on test1 or test2
any idea guys how to open db in this situations.....
Edited by: jignesh kankrecha on Sep 22, 2009 2:24 AM

SQL> connect / as sysdba
Connected to an idle instance.
SQL> startup nomount;
ORACLE instance started.
Total System Global Area 687865856 bytes
Fixed Size 1981192 bytes
Variable Size 369100024 bytes
Database Buffers 314572800 bytes
Redo Buffers 2211840 bytes
SQL> CREATE CONTROLFILE REUSE DATABASE "AMD751" RESETLOGS NOARCHIVELOG
2 MAXLOGFILES 20
3 MAXLOGMEMBERS 5
4 MAXDATAFILES 999
5 MAXINSTANCES 1
6 MAXLOGHISTORY 292
7 LOGFILE
8 GROUP 1 (
9 '/oravl04/oradata/amd751/rdl/redo01a.log',
10 '/oravl03/oradata/amd751/rdl/redo01b.log'
) SIZE 50M,
GROUP 2 (
11 12 13 '/oravl04/oradata/amd751/rdl/redo02a.log',
14 '/oravl03/oradata/amd751/rdl/redo02b.log'
15 ) SIZE 50M,
16 GROUP 3 (
17 '/oravl04/oradata/amd751/rdl/redo03a.log',
18 '/oravl03/oradata/amd751/rdl/redo03b.log'
19 ) SIZE 50M
20 -- STANDBY LOGFILE
21 DATAFILE
22 '/oravl04/oradata/amd751/dfl/system01.dbf',
23 '/oravl04/oradata/amd751/dfl/undotbs01.dbf',
24 '/oravl04/oradata/amd751/dfl/sysaux01.dbf',
25 '/oravl04/oradata/amd751/dfl/users01.dbf'
26 CHARACTER SET AL32UTF8
27 ;
Control file created.
SQL> recover database until cancel;
ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
SQL> RECOVER DATABASE USING BACKUP CONTROLFILE
ORA-00279: change 2797631 generated at 09/16/2009 18:13:06 needed for thread 1
ORA-00289: suggestion : /oravl01/oracle/10.2.0.1/dbs/arch1_70_681310441.dbf
ORA-00280: change 2797631 for thread 1 is in sequence #70
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
Media recovery cancelled.
SQL> ALTER DATABASE OPEN RESETLOGS;
ALTER DATABASE OPEN RESETLOGS
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '/oravl04/oradata/amd751/dfl/system01.dbf'
HI HEMANT THIS WAT I GOT AFTER RUNNING COMMANDS....
IS THERE ANY BAD SEQUENCE OF COMMANDS ????

ORA-01116: error in opening database

I am trying to run a query in UNIX via sqlplus and I am getting this error
sqlplus username/password @querymane.sql
ORA-00604: error occurred at recursive SQL level 1
ORA-01116: error in opening database file 1
ORA-01110: data file 1: '/u01/app/oracle/oradata/PNTR/system01.dbf'
ORA-27092: size of file exceeds file size limit of the process
Additional information: 262143
Additional information: 537089
I will appreciate any hint!

Check "ulimit" and set it to "unlimited".

XSL Database Functions throwing "ORA-01000: maximum open cursors exceeded"

In my BPEL process, I have a large dataset requiring enrichment of the data by looking up values in a database. I'm doing this in an XSL transformation using either; orcl:lookup-table() or orcl:query-database() functions. This works ok for a number of records, but then fails with "ORA-01000: maximum open cursors exceeded".
This implies that these functions are not closing down open cursors after use. Is this a bug, or can I configure the data-sources to handle this?
Thanks.

I don't see any settings to fix this on the data-source itself.
http://download-uk.oracle.com/docs/cd/B31017_01/integrate.1013/b28988/trouble.htm#BABCBFHA
4.11.2 ORA-00604: Error Occurred at Recursive SQL Level 1 ORA-01000: Maximum Open Cursors Exceeded
If i see this..Oracle just advices just to set the PROCESSES parameter on the database high enough so it wont happen :)

Oracle Error code: 1116, message: ORA-01116: error in opening database file

Hi ,
Please advise on this error message
Oracle Error code: 1116, message: ORA-01116: error in opening database file 202 ORA-01110: data file 202: '/u02/app/oracle/oradata/ubidev12/dbf/temp02.dbf'
All these while, the dashboard working well in my local computer application with server database.
Just discovered this error when I refresh the data.
Kindly advise.
Thanks,
Kim Yoke

the more detail error is
Oracle Error code: 1116, message: ORA-01116: error in opening database file 203 ORA-01110: data file 203: '/u02/app/oracle/oradata/ubidev12/dbf/temp03.dbf' ORA-27041: unable to open file SVR4 Error: 2: No such file or directory Additional information

ORA-20100: ORA-01116: error in opening database file

Hi -
I'm hitting this error for the first time. Anyone encountered this before? Any suggestions will be very appreciated. Thanks!
141 EXCEPTION
142
143 when others then
144 raise_application_error('-20100',SQLERRM);
145 End;
146 /
20080207
20080312
Declare
ERROR at line 1:
ORA-20100: ORA-01116: error in opening database file
ORA-06512: at line 144

Thanks Satish for your reply.
I let the DBA know and he was first suspecting a corrupted data file, but found no errors in the log. So, he was not sure why we got the error.
We just re-ran and it went through fine the next time. strange though...

LAST ORA-1578 RECOVERY METHOD

제품 : ORACLE SERVER
작성날짜 : 2002-04-12
LAST ORA-1578 RECOVERY METHOD
=============================
Purpose
Ora-1578 error 에 대한 조치 방법에 대해 이해하도록 합니다.
Problem Description
일반적으로
ORA-1578 : ORACLE data block corrupted (file # num,block # num)
은 해당 objects를 drop하고 recreate하여 처리할 수 있읍니다.
하지만, backup이 안되어 있거나 되어 있더라도 시점에 문제가 생기면,
당황할 수 밖에 없습니다.
Solution Description
이 자료에서는 손상된 db block만을 제외한 다른 block들을 recover하는
방법을 알려 드립니다.
1. 손상된 table과 똑같은 spec의 new table생성
2. 아래의 pl/sql 실행
** This program uses a cursor to select the ROWID from INDEX
** for the corrupted table. And insert the all of the normal rows
** into the new table.
DECLARE
CURSOR c1 is
SELECT ROWID FROM corrupted_table
WHERE indexed_column > smallest_value_of_the_indexes
AND SUBSTR(ROWID,1,8) != '000005DA';
/* Here,the value of '000005DA' is displayed in decimal
when ORA-1578 error happens. */
rowid_value CHAR(18);
count_value NUMBER;
BEGIN
OPEN c1;
FOR i IN 1..total_number_of_the_rows_from_corrupted_table LOOP
FETCH c1 INTO rowid_value;
EXIT WHEN c1%NOTFOUND;
INSERT INTO new_table
SELECT * FROM corrupted_table WHERE ROWID = rowid_value;
count_value := count_value + 1;
IF count_value = 10000 THEN /* Let's think commit per 10000 rows */
COMMIT;
count_value := 0;
END-IF;
END LOOP;
CLOSE c1;
END;
3. new table의 data건수등 확인후에 기존 table을 다른 이름으로
rename한 후 new table을 original table name으로 rename
SQL> rename corrupted_table to table_save;
SQL> rename new_table to corrupted_table;
4. 필요한 index생성이나 constraint enable
5. 손상된 row에 대한 내용은,
최소한 primary key나 indexed columns에 대한 내용을
SQL> spool chk.log
SQL> select rowid,indexed_column1,indexed_column2,indexed_column3...
from corrupted_table
where indexed_column1 > smallest_value_of_the_index;
SQL> spool off
를 통하여 chk.log에 저장후,
SQL> select count(*) from corrupted_table;
혹은 table export등을 통하여 확인된 rowid의 block number를 비교하여
보면 됩니다.
주의사항은 여기에서 ora-1578과 동반되는 block number는 decimal이니,
hexa로 환산해야 합니다.

you did not try to recover the datafile until get syncronyns with the controlfile ?
RECOVER
RECOVER {general | managed | END BACKUP}
where the general clause has the following syntax:
[AUTOMATIC] [FROM location]
{ {full_database_recovery | partial_database_recovery |LOGFILE filename}
[ {TEST | ALLOW integer CORRUPTION } [TEST | ALLOW integer CORRUPTION ]...]
|CONTINUE [DEFAULT]|CANCEL}
where the full_database_recovery clause has the following syntax:
[STANDBY] DATABASE
[ {UNTIL {CANCEL | TIME date | CHANGE integer} | USING BACKUP CONTROLFILE}
[UNTIL {CANCEL | TIME date | CHANGE integer} | USING BACKUP CONTROLFILE]...]
where the partial_database_recovery clause has the following syntax:
{TABLESPACE tablespace [, tablespace]... | DATAFILE datafilename [, datafilename]...
| STANDBY
{TABLESPACE tablespace [, tablespace]... | DATAFILE datafilename [, datafilename]...}
UNTIL [CONSISTENT] [WITH] CONTROLFILE }
where the managed clause has the following syntax:
MANAGED STANDBY DATABASE
[ {NODELAY | [TIMEOUT] integer | CANCEL [IMMEDIATE] [NOWAIT]}
| [DISCONNECT [FROM SESSION] ] [FINISH [NOWAIT] ] ]
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a90842/ch13.htm#1010523
Joel P�rez

Can not open database after restore...

Hi,
I am doing a system copy from a online backup of our production system to our qas system. It is AIX and Oracle 10.2.0.2.0 on both systems.
I have done the restore using the backup log file from the production system. I have run the control.sql script, applied 4 archive log files using "recover database using backup controlfile until cancel;". Last I run "alter database open resetlogs;", but here my problems start....
Here is what happends...
I apply the archive logs:
ORA-00279: change 65129304 generated at 01/22/2008 19:50:35 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8210_632565567.dbf
ORA-00280: change 65129304 for thread 1 is in sequence #8210
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8209_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
From the alert log:
ALTER SYSTEM ARCHIVE LOG ALL USING BACKUP CONTROLFILE start
Database is not in archivelog mode
ALTER SYSTEM ARCHIVE LOG ALL USING BACKUP CONTROLFILE complete
2008-02-23 01:00:23.810
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Have somebody had this problem? Hope you can help me :-).
Best regards Henrik

I entered cancel when the log files had been restored and then I did "alter database open resetlogs;"
Here is what I did:
orasrq> sqlplus "/ as sysdba"
SQL*Plus: Release 10.2.0.2.0 - Production on Fri Feb 22 13:01:38 2008
Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
Connected to an idle instance.
SQL> startup nomount
ORACLE instance started.
Total System Global Area 4714397696 bytes
Fixed Size                  2077560 bytes
Variable Size            2365590664 bytes
Database Buffers         2332033024 bytes
Redo Buffers               14696448 bytes
SQL> @controlSRQ.sql
Control file created.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/SRQ/sapdata1/system_1/system.data1'
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 65088663 generated at 01/22/2008 18:30:19 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8203_632565567.dbf
ORA-00280: change 65088663 for thread 1 is in sequence #8203
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65091816 generated at 01/22/2008 18:35:25 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8204_632565567.dbf
ORA-00280: change 65091816 for thread 1 is in sequence #8204
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8203_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65094835 generated at 01/22/2008 18:39:16 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8205_632565567.dbf
ORA-00280: change 65094835 for thread 1 is in sequence #8205
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8204_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65101797 generated at 01/22/2008 18:56:03 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8206_632565567.dbf
ORA-00280: change 65101797 for thread 1 is in sequence #8206
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8205_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65108888 generated at 01/22/2008 19:05:31 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8207_632565567.dbf
ORA-00280: change 65108888 for thread 1 is in sequence #8207
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8206_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 65108888 generated at 01/22/2008 19:05:31 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8207_632565567.dbf
ORA-00280: change 65108888 for thread 1 is in sequence #8207
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65115833 generated at 01/22/2008 19:20:32 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8208_632565567.dbf
ORA-00280: change 65115833 for thread 1 is in sequence #8208
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8207_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 65115833 generated at 01/22/2008 19:20:32 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8208_632565567.dbf
ORA-00280: change 65115833 for thread 1 is in sequence #8208
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65122618 generated at 01/22/2008 19:35:37 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8209_632565567.dbf
ORA-00280: change 65122618 for thread 1 is in sequence #8209
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8208_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 65129304 generated at 01/22/2008 19:50:35 needed for thread 1
ORA-00289: suggestion : /oracle/SRQ/oraarch/SRQarch1_8210_632565567.dbf
ORA-00280: change 65129304 for thread 1 is in sequence #8210
ORA-00278: log file '/oracle/SRQ/oraarch/SRQarch1_8209_632565567.dbf' no longer
needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cn
ORA-00308: cannot open archived log 'cn'
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection force

Can not open database - 10g

Dear experts,
I have a problem to open my database. ORA-01033: ORACLE initialization or shutdown in progress. I have restarted server many times. I tried several ways but no joy. Please see the steps I did to solve this -
SQL> connect dmadmin /mypwdx89 as sysdba
Connected.
SQL> STARTUP MOUNT
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> ALTER DATABASE OPEN;
ALTER DATABASE OPEN
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: 'C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\SYSTEM01.DBF'
SQL> RECOVER DATABASE;
ORA-00279: change 149935494 generated at 06/10/2009 17:05:33 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ZUMA\ARCHIVELOG\2009_06_23\O1_MF_1_
673_%U_.ARC
ORA-00280: change 149935494 for thread 1 is in sequence #673
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ZUMA\ARCHIVELOG\2009_06_10\O1_MF_1
_673_530WXF9P_.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
SQL> select * from v$controlfile;
STATUS
NAME
IS_
C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\CONTROL01.CTL
NO
C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\CONTROL02.CTL
NO
STATUS
NAME
IS_
C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\CONTROL03.CTL
NO
SQL> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup nomount
ORACLE instance started.
Total System Global Area 171966464 bytes
Fixed Size 787988 bytes
Variable Size 145750508 bytes
Database Buffers 25165824 bytes
Redo Buffers 262144 bytes
SQL> select name from v$controlfile;
no rows selected
SQL>
SQL> alter database mount;
Database altered.
SQL> select name from v$controlfile;
NAME
C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\CONTROL01.CTL
C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\CONTROL02.CTL
C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\CONTROL03.CTL
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: 'C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\SYSTEM01.DBF'
SQL>
The I tried to recover datafile
SQL> Recover datafile '<datafile-name>';
again error - even can not open data file ...i restarted server .. no use..same error.
Please help to resolve this issue.
Regards,
Ranjith John

Hi All,
Please see the alert log file ..file size is already few GBs now. There are errors in the file.
It says - ORA-19815: WARNING: db_recovery_file_dest_size of 10048576000 bytes is 100.00% used, and has 0 remaining bytes available.
so, i guess the back up was not done .please help to resovle this issue.
ARC1: Error 19809 Creating archive log file to 'C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ZUMA\ARCHIVELOG\2009_04_14\O1_MF_1_37_U_.ARC'
ARC1: All standby destinations failed; successful archival assumed
ARC1: Failed to archive log 1 thread 1 sequence 37 (19809)
Tue Apr 14 11:46:51 2009
Errors in file c:\oracle\product\10.1.0\admin\zuma\bdump\zuma_arc1_1352.trc:
ORA-16038: log 1 sequence# 37 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1: 'C:\ORACLE\PRODUCT\10.1.0\ORADATA\ZUMA\REDO01.LOG'
Tue Apr 14 11:46:51 2009
ARC0: Evaluating archive log 1 thread 1 sequence 37
Tue Apr 14 11:46:51 2009
Errors in file c:\oracle\product\10.1.0\admin\zuma\bdump\zuma_arc0_3828.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 10048576000 bytes is 100.00% used, and has 0 remaining bytes available.
You have the following choices to free up space from
flash recovery area:
1. Consider changing your RMAN retention policy.
If you are using dataguard, then consider changing your
RMAN archivelog deletion policy.
2. Backup files to tertiary device such as tape using the
RMAN command BACKUP RECOVERY AREA.
3. Add disk space and increase the db_recovery_file_dest_size
parameter to reflect the new space.
4. Delete unncessary files using the RMAN DELETE command.
If an OS command was used to delete files, then use
RMAN CROSSCHECK and DELETE EXPIRED commands.
Tue Apr 14 11:46:51 2009
Errors in file c:\oracle\product\10.1.0\admin\zuma\bdump\zuma_arc0_3828.trc:
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 10017792 bytes disk space from 10048576000 limit
ARC0: Error 19809 Creating archive log file to 'C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ZUMA\ARCHIVELOG\2009_04_14\O1_MF_1_37_U_.ARC'
ARC0: All standby destinations failed; successful archival assumed
ARC0: Failed to archive log 1 thread 1 sequence 37 (19809)
Regards,
Ranjith John

FS-CANT OPEN TEMPFILE issue in opening a concurrent program log file

Hi all,
I am working in Order Management authorization process in oracle apps 11i. After completion of order authorization , i did the shipping and delivery process in oracle Forms. During this Shipping and Delivery process the concurrent program gets error. (i.e status is : Completed -Error ).
Then i tried to open a concurrent program view log and view output file , but it shows following error in window.
Error: FS-CANT OPEN TEMPFILE.
I never did anything in server recently. But it throws the "FS-CANT OPEN TEMPFILE" error in forms while running the concurrent program.
Please Help How to resolve this issue.
Thanks
Prabu

Pl post details of OS, database and EBS versions, along with complete steps to reproduce the issue. Are there any errors in the database alert log or the concurrent manager log ? Has this ever worked before ? If so, what has changed since then ?
Pl see if these MOS Docs can help
"FS-CANT OPEN TEMPFILE" MESSAGE WHEN OPENING ANY VIEW LOGS OR OUTPUT LOGS [ID 462277.1]
Copy File functionality generates FS-CANT OPEN TEMPFILE [ID 780516.1]
FS-Cant Open Tempfile When Try to Send Output to Excel [ID 236311.1]
FS-CANT OPEN TEMPFILE in 11i
HTH
Srini

RMAN 11gr2 ORA-00308 when dulplicate database from active

Hi,
I'm trying to clone a production database (Oracle 11.2.0.3) from HP-UX IA64 to Solaris 10 (Sparc 64) (source on Filesystem, target on ASM)
the previous steps was done (same oracle software installation, same patches, sqlnet comunication, etc.)
but the RMAN fails at end of the process:
Recovery Manager: Release 11.2.0.3.0 - Production on Wed Aug 22 09:44:34 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: SIN (DBID=634625013)
connected to recovery catalog database
connected to auxiliary database: SIN (not mounted)
RMAN> run
+2> {+
+3> allocate channel c1 type disk;+
+4> allocate channel c2 type disk;+
+5> allocate channel c3 type disk;+
+6> allocate channel c4 type disk;+
+7> allocate auxiliary channel a1 type disk;+
+8> allocate auxiliary channel a2 type disk;+
+9> set newname for datafile 1 to '+DG_DATA';+
+10> set newname for datafile 2 to '+DG_DATA';+
+11> set newname for datafile 3 to '+DG_DATA';+
+12> set newname for datafile 4 to '+DG_DATA';+
+13> set newname for datafile 5 to '+DG_DATA';+
+14> set newname for datafile 6 to '+DG_DATA';+
+15> set newname for datafile 7 to '+DG_DATA';+
+16> set newname for datafile 8 to '+DG_DATA';+
+17> set newname for datafile 9 to '+DG_DATA';+
+18> set newname for datafile 10 to '+DG_DATA';+
+... to...+
+398> set newname for datafile 390 to '+DG_DATA';+
+399> set newname for datafile 391 to '+DG_DATA';+
+400> duplicate target database to "sin" from active database nofilenamecheck+
+401> DB_FILE_NAME_CONVERT=('/u10/oradata/sin/','+DG_DATA/',+
+402> '/u11/oradata/sin/','+DG_DATA/',+
+403> '/u07/oradata/sin/','+DG_DATA/',+
+404> '/u08/oradata/sin/','+DG_DATA/',+
+405> '/u09/oradata/sin/','+DG_DATA/');+
+406> }+
+407>+
starting full resync of recovery catalog
full resync complete
allocated channel: c1
channel c1: SID=1787 device type=DISK
allocated channel: c2
channel c2: SID=2406 device type=DISK
allocated channel: c3
channel c3: SID=850 device type=DISK
allocated channel: c4
channel c4: SID=1146 device type=DISK
allocated channel: a1
channel a1: SID=1325 device type=DISK
allocated channel: a2
channel a2: SID=1514 device type=DISK
executing command: SET NEWNAME
executing command: SET NEWNAME
+...+
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting Duplicate Db at 22-AUG-12
contents of Memory Script:
+{+
sql clone "create spfile from memory";
+}+
executing Memory Script
sql statement: create spfile from memory
contents of Memory Script:
+{+
shutdown clone immediate;
startup clone nomount;
+}+
executing Memory Script
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area    7317790720 bytes
Fixed Size                     2173456 bytes
Variable Size               3808433648 bytes
Database Buffers            3489660928 bytes
Redo Buffers                  17522688 bytes
allocated channel: a1
channel a1: SID=1325 device type=DISK
allocated channel: a2
channel a2: SID=758 device type=DISK
contents of Memory Script:
+{+
sql clone "alter system set control_files =
+''+DG_DATA/sin/controlfile/current.511.791978153'', ''+DG_DATA/sin/controlfile/current.562.791978153'' comment=+
+''Set by RMAN'' scope=spfile";+
+''+DG_DATA/sin/controlfile/current.511.791978153'', ''+DG_DATA/sin/controlfile/current.562.791978153'' comment=+
+''Set by RMAN'' scope=spfile";+
sql clone "alter system set db_name =
+''SIN'' comment=+
+''Modified by RMAN duplicate'' scope=spfile";+
+sql clone "alter system set db_unique_name =+
+''SIN'' comment=+
+''Modified by RMAN duplicate'' scope=spfile";+
+shutdown clone immediate;+
+startup clone force nomount+
+backup as copy current controlfile auxiliary format '+DG_DATA/sin/controlfile/current.512.791978153';+
+restore clone controlfile to '+DG_DATA/sin/controlfile/current.625.791978153' from+
+'+DG_DATA/sin/controlfile/current.512.791978153';+
+sql clone "alter system set control_files =+
+''+DG_DATA/sin/controlfile/current.512.791978153'', ''+DG_DATA/sin/controlfile/current.625.791978153'' comment=+
+''Set by RMAN'' scope=spfile";+
+shutdown clone immediate;+
+startup clone nomount;+
+alter clone database mount;+
+}+
+executing Memory Script+
+sql statement: alter system set control_files = ''+DG_DATA/sin/controlfile/current.511.791978153'', ''+DG_DATA/sin/controlfile/cu+
+rrent.562.791978153'' comment= ''Set by RMAN'' scope=spfile+
+sql statement: alter system set db_name = ''SIN'' comment= ''Modified by RMAN duplicate'' scope=spfile+
+sql statement: alter system set db_unique_name = ''SIN'' comment= ''Modified by RMAN duplicate'' scope=spfile+
+Oracle instance shut down+
+Oracle instance started+
+Total System Global Area 7317790720 bytes+
+Fixed Size 2173456 bytes+
+Variable Size 3808433648 bytes+
+Database Buffers 3489660928 bytes+
+Redo Buffers 17522688 bytes+
+allocated channel: a1+
+channel a1: SID=1514 device type=DISK+
+allocated channel: a2+
+channel a2: SID=2081 device type=DISK+
+Starting backup at 22-AUG-12+
+channel c1: starting datafile copy+
+copying current control file+
+output file name=/u06/tmpapp/rmanbkps/snapcf_sin.f tag=TAG20120822T094657 RECID=49 STAMP=791977621+
+channel c1: datafile copy complete, elapsed time: 00:00:01+
+Finished backup at 22-AUG-12+
+Starting restore at 22-AUG-12+
+channel a2: skipped, AUTOBACKUP already found+
+channel a1: copied control file copy+
+Finished restore at 22-AUG-12+
+sql statement: alter system set control_files = ''+DG_DATA/sin/controlfile/current.512.791978153'', ''+DG_DATA/sin/controlfile/cu+
+rrent.625.791978153'' comment= ''Set by RMAN'' scope=spfile+
+Oracle instance shut down+
+connected to auxiliary database (not started)+
+Oracle instance started+
+Total System Global Area 7317790720 bytes+
+Fixed Size 2173456 bytes+
+Variable Size 3808433648 bytes+
+Database Buffers 3489660928 bytes+
+Redo Buffers 17522688 bytes+
+allocated channel: a1+
+channel a1: SID=1514 device type=DISK+
+allocated channel: a2+
+channel a2: SID=2081 device type=DISK+
+database mounted+
+Using previous duplicated file +DG_DATA/sin/datafile/system.666.791914845 for datafile 1 with checkpoint SCN of 46164275052+
+Using previous duplicated file +DG_DATA/sin/datafile/undotbs1.678.791913821 for datafile 2 with checkpoint SCN of 46164227408+
+...+
+Using previous duplicated file +DG_DATA/sin/datafile/med_dat.498.791939115 for datafile 389 with checkpoint SCN of 46165353395+
+Using previous duplicated file +DG_DATA/sin/datafile/mytablespace.674.791914359 for datafile 390 with checkpoint SCN of 46164253329+
+Using previous duplicated file +DG_DATA/sin/datafile/med_dat.499.791939115 for datafile 391 with checkpoint SCN of 46165353396+
+contents of Memory Script:+
+{+
+sql 'alter system archive log current';+
+}+
+executing Memory Script+
+sql statement: alter system archive log current+
+contents of Memory Script:+
+{+
+backup as copy reuse+
+archivelog like "/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065832.ARC" auxiliary format+
+"+DG_DATA" archivelog like+
+"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065833.ARC" auxiliary format+
+"+DG_DATA" archivelog like+
+"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065834.ARC" auxiliary format+
+"+DG_DATA" archivelog like+
+"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065835.ARC" auxiliary format+
+"+DG_DATA" archivelog like+
+"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065836.ARC" auxiliary format+
+"+DG_DATA" ;+
+catalog clone start with "+DG_DATA";+
+catalog clone datafilecopy "+DG_DATA/sin/datafile/system.666.791914845",+
+"+DG_DATA/sin/datafile/undotbs1.678.791913821",+
+"+DG_DATA/sin/datafile/undotbs1.679.791913821",+
+"+DG_DATA/sin/datafile/undotbs1.689.791913821",+
+"+DG_DATA/sin/datafile/undotbs1.690.791913821",+
+"+DG_DATA/sin/datafile/undotbs1.677.791914357",+
+"+DG_DATA/sin/datafile/drsys.621.791939555",+
+"+DG_DATA/sin/datafile/high_idx.663.791914889",+
+"+DG_DATA/sin/datafile/tools.507.791939555",+
+...+
+"+DG_DATA/sin/datafile/bkptemp.497.791939113",+
+"+DG_DATA/sin/datafile/med_dat.498.791939115",+
+"+DG_DATA/sin/datafile/mytablespace.674.791914359",+
+"+DG_DATA/sin/datafile/med_dat.499.791939115";+
+switch clone datafile 1 to datafilecopy+
+"+DG_DATA/sin/datafile/system.666.791914845";+
+switch clone datafile 2 to datafilecopy+
+"+DG_DATA/sin/datafile/undotbs1.678.791913821";+
+switch clone datafile 3 to datafilecopy+
+...+
+"+DG_DATA/sin/datafile/med_dat.498.791939115";+
+switch clone datafile 390 to datafilecopy+
+"+DG_DATA/sin/datafile/mytablespace.674.791914359";+
+switch clone datafile 391 to datafilecopy+
+"+DG_DATA/sin/datafile/med_dat.499.791939115";+
+}+
+executing Memory Script+
+Starting backup at 22-AUG-12+
+channel c1: starting archived log copy+
+input archived log thread=1 sequence=65832 RECID=48339 STAMP=791913640+
+channel c2: starting archived log copy+
+input archived log thread=1 sequence=65833 RECID=48340 STAMP=791933223+
+channel c3: starting archived log copy+
+input archived log thread=1 sequence=65834 RECID=48341 STAMP=791939052+
+channel c4: starting archived log copy+
+input archived log thread=1 sequence=65835 RECID=48342 STAMP=791962351+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65834.515.791978259 RECID=0 STAMP=0+
+channel c3: archived log copy complete, elapsed time: 00:00:35+
+channel c3: starting archived log copy+
+input archived log thread=1 sequence=65836 RECID=48343 STAMP=791977692+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.791978259 RECID=0 STAMP=0+
+channel c1: archived log copy complete, elapsed time: 00:00:51+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65833.514.791978259 RECID=0 STAMP=0+
+channel c2: archived log copy complete, elapsed time: 00:01:41+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65836.581.791978295 RECID=0 STAMP=0+
+channel c3: archived log copy complete, elapsed time: 00:01:06+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65835.516.791978259 RECID=0 STAMP=0+
+channel c4: archived log copy complete, elapsed time: 00:01:41+
+Finished backup at 22-AUG-12+
+searching for all files that match the pattern +DG_DATA+
+List of Files Unknown to the Database+
+=====================================+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65832.513.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65833.514.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65834.515.791978259+
+...+
+File Name: +dg_data/SIN/DATAFILE/XDB.508.791939555+
+File Name: +dg_data/SIN/DATAFILE/DRSYS.621.791939555+
+File Name: +dg_data/SIN/CONTROLFILE/Current.691.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.692.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.703.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.704.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.511.791978153+
+File Name: +dg_data/SIN/CONTROLFILE/Current.562.791978153+
+File Name: +dg_data/ASM/ASMPARAMETERFILE/REGISTRY.253.790861037+
+cataloging files...+
+cataloging done+
+List of Cataloged Files+
+=======================+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65832.513.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65833.514.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65834.515.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65835.516.791978259+
+...+
+File Name: +dg_data/SIN/DATAFILE/XDB.508.791939555+
+File Name: +dg_data/SIN/DATAFILE/DRSYS.621.791939555+
+File Name: +dg_data/SIN/CONTROLFILE/Current.703.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.704.791913737+
+List of Files Which Where Not Cataloged+
+=======================================+
+File Name: +dg_data/SIN/CONTROLFILE/Current.691.791913737+
+RMAN-07517: Reason: The file header is corrupted+
+File Name: +dg_data/SIN/CONTROLFILE/Current.692.791913737+
+RMAN-07517: Reason: The file header is corrupted+
+File Name: +dg_data/SIN/CONTROLFILE/Current.511.791978153+
+RMAN-07517: Reason: The file header is corrupted+
+File Name: +dg_data/SIN/CONTROLFILE/Current.562.791978153+
+RMAN-07517: Reason: The file header is corrupted+
+File Name: +dg_data/ASM/ASMPARAMETERFILE/REGISTRY.253.790861037+
+RMAN-07518: Reason: Foreign database file DBID: 0 Database Name:+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/system.666.791914845 RECID=442 STAMP=791978374+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/undotbs1.678.791913821 RECID=443 STAMP=791978375+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/undotbs1.679.791913821 RECID=444 STAMP=791978375+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/undotbs1.689.791913821 RECID=445 STAMP=791978375+
+cataloged datafile copy+
+...+
+datafile copy file name=+DG_DATA/sin/datafile/med_dat.498.791939115 RECID=830 STAMP=791978408+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/mytablespace.674.791914359 RECID=831 STAMP=791978408+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/med_dat.499.791939115 RECID=832 STAMP=791978408+
+datafile 1 switched to datafile copy+
+input datafile copy RECID=442 STAMP=791978374 file name=+DG_DATA/sin/datafile/system.666.791914845+
+datafile 2 switched to datafile copy+
+input datafile copy RECID=443 STAMP=791978375 file name=+DG_DATA/sin/datafile/undotbs1.678.791913821+
+datafile 3 switched to datafile copy+
+input datafile copy RECID=444 STAMP=791978375 file name=+DG_DATA/sin/datafile/undotbs1.679.791913821+
+datafile 4 switched to datafile copy+
+input datafile copy RECID=445 STAMP=791978375 file name=+DG_DATA/sin/datafile/undotbs1.689.791913821+
+...+
+datafile 389 switched to datafile copy+
+input datafile copy RECID=830 STAMP=791978408 file name=+DG_DATA/sin/datafile/med_dat.498.791939115+
+datafile 390 switched to datafile copy+
+input datafile copy RECID=831 STAMP=791978408 file name=+DG_DATA/sin/datafile/mytablespace.674.791914359+
+datafile 391 switched to datafile copy+
+input datafile copy RECID=832 STAMP=791978408 file name=+DG_DATA/sin/datafile/med_dat.499.791939115+
+contents of Memory Script:+
+{+
+set until scn 46167049411;+
+recover+
+clone database+
+delete archivelog+
+;+
+}+
+executing Memory Script+
+executing command: SET until clause+
+Starting recover at 22-AUG-12+
+starting media recovery+
+archived log for thread 1 with sequence 65832 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.7+
+91978259+
+archived log for thread 1 with sequence 65833 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65833.514.7+
+91978259+
+archived log for thread 1 with sequence 65834 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65834.515.7+
+91978259+
+archived log for thread 1 with sequence 65835 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65835.516.7+
+91978259+
+archived log for thread 1 with sequence 65836 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65836.581.7+
+91978295+
+archived log file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.791978259 thread=1 sequence=65832+
+released channel: c1+
+released channel: c2+
+released channel: c3+
+released channel: c4+
+Oracle Error:+
+ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below+
+ORA-01194: file 1 needs more recovery to be consistent+
+ORA-01110: data file 1: '+DG_DATA/sin/datafile/system.666.791914845'+
*+released channel: a1+*
*+released channel: a2+*
*+RMAN-00571: ===========================================================+*
*+RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============+*
*+RMAN-00571: ===========================================================+*
*+RMAN-03002: failure of Duplicate Db command at 08/22/2012 09:52:27+*
*+RMAN-05501: aborting duplication of target database+*
*+RMAN-03015: error occurred in stored script Memory Script+*
*+RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '+DG_DATA/sin/archivelog/2012_08_22/thre+*
*+ad_1_seq_65832.513.791978259'+*
*+ORA-00308: cannot open archived log '+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.791978259'+*
+Recovery Manager complete.+
the error is always the same, a previous backup with RMAN was taken on tape on the source database (production).
Please help me to find what is wrong here!!

Hi mseberg
that's exactly i'm doing:
1. Create an Oracle Password File for the Auxiliary Database
a. done, passwd file created*
2. Create the Directory Structure on the remote server
a. done, all the admin structure wa created.*
3. Oracle Net Setup ( you need an entry for the CLONE in your TNSNAMES.ORA on both servers ) ( I use SID_LIST_LISTENER entry for static )
a. done, i have the entries working on my tnsnames.ora (source and target with static listeners)*
4. Create an Initialization Parameter File for the Auxiliary Instance ( I use Parameters DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT to change locations)
a. done, this is my initialization file:*
*.audit_file_dest='/u01/app/oracle/admin/sin/adump'*
*.audit_trail='db'*
*.compatible='11.2.0.0.0'*
*.db_block_size=8192*
*.db_create_file_dest='DG_DATA'+*
*.db_domain=''*
*.db_files=2048*
*.db_name='sin'*
*.db_recovery_file_dest='DG_DATA'+*
*.db_recovery_file_dest_size=20G*
*.diagnostic_dest='/u01/app/oracle'*
*.dispatchers='(PROTOCOL=TCP) (SERVICE=sinXDB)'*
*.log_archive_format='%t_%s_%r.dbf'*
*.memory_target=7340032000*
*.open_cursors=300*
*.processes=2000*
*.remote_login_passwordfile='EXCLUSIVE'*
*.sessions=2205*
*.undo_tablespace='UNDOTBS1'*
DB_FILE_NAME_CONVERT=('/u10/oradata/sin/','DG_DATA/',+*
+'/u11/oradata/sin/','+DG_DATA/',+
+'/u07/oradata/sin/','+DG_DATA/',+
+'/u08/oradata/sin/','+DG_DATA/',+
+'/u09/oradata/sin/','+DG_DATA/')+
LOG_FILE_NAME_CONVERT=('/u04/oradata/sin/','DG_DATA/',+*
+'/u05/oradata/sin/','+DG_DATA/',+
+'/u03/oradata/sin/','+DG_DATA/',+
+'/u02/oradata/sin/','+DG_DATA/')+
and this is my command from RMAN:
run*
*+{+*
allocate channel c1 type disk;*
allocate channel c2 type disk;*
allocate channel c3 type disk;*
allocate channel c4 type disk;*
allocate auxiliary channel a1 type disk;*
allocate auxiliary channel a2 type disk;*
set newname for datafile 1 to 'DG_DATA';+*
set newname for datafile 2 to 'DG_DATA';+*
set newname for datafile 3 to 'DG_DATA';+*
set newname for datafile 4 to 'DG_DATA';+*
set newname for datafile 5 to 'DG_DATA';+*
set newname for datafile 6 to 'DG_DATA';+*
set newname for datafile 7 to 'DG_DATA';+*
set newname for datafile 8 to 'DG_DATA';+*
set newname for datafile 9 to 'DG_DATA';+*
set newname for datafile 10 to 'DG_DATA';+*
+...+
set newname for datafile 390 to 'DG_DATA';+*
set newname for datafile 391 to 'DG_DATA';+*
duplicate target database to "sin" from active database nofilenamecheck*
DB_FILE_NAME_CONVERT=('/u10/oradata/sin/','DG_DATA/',+*
+'/u11/oradata/sin/','+DG_DATA/',+
+'/u07/oradata/sin/','+DG_DATA/',+
+'/u08/oradata/sin/','+DG_DATA/',+
+'/u09/oradata/sin/','+DG_DATA/');+
+}+
do you think the problem may be in the name of the database?, I am using the same name in the auxiliary
and when I get the error, I have the same dbid in both databases (source and destination)
Thanks
MM

[HELP] ORA-01990 Error opening password file '/home/oracle/OraHome1/dbs/ora

Dear All,
I have changed the PWD file on oracle 9.2.04 under linux redhat advance server 2.1. but when i start to open database by issuing dbstart, i get
ORA-01990: Error opening password file '/home/oracle/OraHome1/dbs/orapw'
ORA-27037: unable to obtain file status
Linux Error: 2 : no such file or directory
additional information: 3
How to solve the problems?
thanks and regard
ER

Hai all...
I did it all..
but still I got
ORA-01990: Error opening password file '/home/oracle/OraHome1/dbs/orapw'
ORA-27037: unable to obtain file status
Linux Error: 2 : no such file or directory
additional information: 3
Help me...
Thanks
regard
ER

I am using I Photo 9.2.3 with OS 10.6.8 When I upgraded to current I photo some of my Iphoto books i put together disappeared. Cant find them anywhere, including in the time machine...I photo cant open older files...How can a find th book entitled "Mom"

I am using I Photo 9.2.3 with OS 10.6.8 When I upgraded to current I photo some of my Iphoto books i put together disappeared. Cant find them anywhere, including in the time machine...I photo cant open older files...How can a find the book entitled "Mom" ? Does Apple keep ordered books on file?

Apple keeps books for a short time (used to be 40 days. I've not seen a recent time frame)
What version did you have?
Books do nor exist except in the iPhoto database so you can not "find" a book vista TM. You restore a previous library (be sure NOT to overwrite your current library) and switch to it
LN

ORA-1578 Cant open Database.

Similar Messages

Maybe you are looking for