Archive in Listerner.ora
An error occurs when I try to raise the Listener (call RED_240), the error is the following one:
LSNRCTL> start RED_240
Starting /oracle/app/oracle_10g/OraHome_1/bin/tnslsnr: please wait...
TNSLSNR for Linux IA64: Version 10.1.0.2.0 - Production
System parameter file is /oracle/app/oracle_10g/OraHome_1/network/admin/listener.ora
Log messages written to /oracle/app/oracle_10g/OraHome_1/network/log/red_240.logListening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.74.2.240)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC)))
TNS-01155: Incorrectly specified SID_LIST_RED_240 parameter in LISTENER.ORA
NL-00303: syntax error in NV string
Listener failed to start. See the error message(s) above...
LSNRCTL>
The listerner.ora is:
(ADDRESS = (PROTOCOL=IPC)(KEY=EXTPROC))
RED_240 =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.74.2.240)(PORT = 1521))
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
SID_LIST_RED_240 =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /oracle/app/oracle_10g/OraHome_1)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = mgwextproc)
(ENVS = EXTPROC_DLLS=/oracle/app/oracle_10g/OraHome_1/lib/libmgwagent.so, LD_LIBRARY_PATH=/oracle/app/oracle_10g/OraHome_1/jdk/jre/lib/ia64:/oracle/app/oracle_10g/OraHome_1/jdk/jre/lib/ia64/server:/oracle/app/oracle_10g/OraHome_1/lib)
(ORACLE_HOME = /oracle/app/oracle_10g/OraHome_1)
(PROGRAM = extproc)
Now well, seeking in the route, the file:, I give me account that itself is not found..
That that I can do??? or of where I can copy the file.
Thanks
Continue...
LSNRCTL> start RED_240
Starting /oracle/app/oracle_10g/OraHome_1/bin/tnslsnr: please wait...
TNSLSNR for Linux IA64: Version 10.1.0.2.0 - Production
System parameter file is /oracle/app/oracle_10g/OraHome_1/network/admin/listener.ora
Log messages written to /oracle/app/oracle_10g/OraHome_1/network/log/red_240.logListening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.74.2.240)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.74.2.240)(PORT=1521)))
STATUS of the LISTENER
Alias RED_240
Version TNSLSNR for Linux IA64: Version 10.1.0.2.0 - Production
Start Date 15-FEB-2005 15:26:03
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /oracle/app/oracle_10g/OraHome_1/network/admin/listener.ora
Listener Log File /oracle/app/oracle_10g/OraHome_1/network/log/red_240.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.74.2.240)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "mgwextproc" has 1 instance(s).
Instance "mgwextproc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
LSNRCTL> status
Connecting to (ADDRESS=(PROTOCOL=tcp)(PORT=1521))
TNS-12541: TNS:no listener
TNS-12560: TNS:protocol adapter error
TNS-00511: No listener
Linux IA64 Error: 111: Connection refused
LSNRCTL>
Now, How I startup the Oracle's service???
I try,
[root@localhost init.d]# ./dbora oracle
+ ORACLE_HOME=/oracle/app/oracle_10g/OraHome_1
+ ORACLE=oracle
+ PATH=/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin:/opt/intel/compiler70/ia64/bin:/oracle/app/oracle_10g/OraHome_1/bin
+ HOST=10.74.2.240
+ PLATFORM=Linux
+ export ORACLE_HOME PATH
+ '[' '!' '' = ORA_DB ']'
+ '[' Linux = HP-UX ']'
+ rsh 10.74.2.240 -l oracle ./dbora oracle ORA_DB
10.74.2.240: Connection refused
+ exit
[root@localhost init.d]#
I Want startup my database, and need known the steps ???
What are first, Oracle's Service o Listener.ora and I nedd How can do it???
I Apreciated your Help
Thanks
Similar Messages
-
Event test "Archive Full (%)" failed: ora-28009:
Trying to create an event that will send an email with OEM but Im getting this message
Event test "Archive Full (%)" failed: ora-28009: connection to sys should be as sysdba or sysoper in the event viewer.
Im not sure what this refers to though - to connect to Management Server it has to be sysman user. What "connection" is this referring to ???
Oracle 9.2.0.5.0 (due to migrate to 10g at years end hurrah!)
Windows XP (now, but AIX once in production)OK thanks for that. I went ahead and did this:
Configuration
Manage Administrators
Selected SYSMAN
Preferred Credentials
Selected target database and erased everything from the Database Credentials fields (where previously we had SYS/AS SYSDBA etc. )
I am getting the same darn error as before.
Anyway, the OEM help for this screen says
Role Select the role from the pull-down list. You need to login with the SYSDBA or SYSOPER role to start up or shut down a database.
Still stuck on this. I dont properly understand the error itself - it is telling me that the connection to sys should be as sysdba - and I am connecting as sysdba. ... . not sure what else I can do apart from try and write a script and forget this altogether.
Thanks
DA
Also, in the Event Viewer, according the documentation, there is an "advice" tab. I see no such tab. :(
When I try to create an event without any information supplied to the fields for SYSMAN Preferred Credentials, I get this in Event Viewer:
"Failed - ora-0:normal , successful completion."
Now I am really confused - a "failed, normal completion" ??
Message was edited by:
Dan A
Message was edited by:
Dan A -
Hi all,
I have a development database, oracle 10g R2 (10.2.0.1.0) on OEL 4 environment.
I had set the database in archivelog mode using this commands.
ALTER SYSTEM SET log_archive_start=TRUE SCOPE=spfile;
ALTER SYSTEM SET log_archive_dest_1='location=/arch/' SCOPE=spfile;
ALTER SYSTEM SET log_archive_format='arch_%r_%t_%s.arc' SCOPE=spfile;
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
ARCHIVE LOG START;
ALTER DATABASE ARCHIVELOG;
ALTER DATABASE OPEN;
alter system switch logfile;
but, it is not archiving the redologs. i have seen the following ora-error messages on my alert log file.
Sat Feb 5 10:50:15 2011
ARC0: Archiving not possible: No primary destinations
ARC0: Failed to archive thread 1 sequence 2907 (4)
Sat Feb 5 10:50:20 2011
ARC1: Archiving not possible: No primary destinations
ARC1: Failed to archive thread 1 sequence 2907 (4)
how can i resolve this problem. pls. help me.
thanks and regards.785092 wrote:
Hi chinar,
I have changed the ownership of the /arch mountpoint to oracle user. now the archs are generating.
now i want to edit the 'pfile' with arch destination details.
can i create the pfile using the spfile or should i do manually.
thanks very much chinar.
Edited by: 785092 on Feb 4, 2011 9:59 PMIf you use(started database with ) pfile then you need manually edit pfile and change LOG_ARCHIVE_DEST_1 parameter else just use ALTER SYSTEM SET LOG_ARCHIVE_DEST_1='location=....' -
ORA-19571: archived-log recid 118360 stamp not found in control file - help
Hi
Every backup I do I am getting an error like below at the bottom :, every backup I do, it's complaaining about DIFFERENT archive log.
ORA-19571: archived-log recid 118360 stamp 705446770 not found in control file.
I have set keep control file info to 14 days, my retention is 7 days in RMAN, so I don't know why it's complaining, below is the full log.
It seeems to be having problems with archive logs that have just been generated while it's doing the backup I think??
channel d3: specifying archive log(s) in backup set
input archive log thread=1 sequence=705 recid=124248 stamp=707103829
input archive log thread=1 sequence=706 recid=124249 stamp=707103830
input archive log thread=1 sequence=707 recid=124250 stamp=707103831
input archive log thread=1 sequence=708 recid=124251 stamp=707103831
input archive log thread=1 sequence=709 recid=124252 stamp=707103832
input archive log thread=1 sequence=710 recid=124253 stamp=707103832
input archive log thread=1 sequence=711 recid=124254 stamp=707103833
input archive log thread=1 sequence=712 recid=124255 stamp=707103833
input archive log thread=1 sequence=713 recid=124256 stamp=707103834
input archive log thread=1 sequence=714 recid=124257 stamp=707103835
input archive log thread=1 sequence=715 recid=124258 stamp=707103835
input archive log thread=1 sequence=716 recid=124259 stamp=707103836
input archive log thread=1 sequence=717 recid=124260 stamp=707103836
input archive log thread=1 sequence=718 recid=124261 stamp=707103837
input archive log thread=1 sequence=719 recid=124262 stamp=707103837
input archive log thread=1 sequence=720 recid=124263 stamp=707103838
input archive log thread=1 sequence=721 recid=124264 stamp=707103838
input archive log thread=1 sequence=722 recid=124265 stamp=707103839
input archive log thread=1 sequence=723 recid=124266 stamp=707103840
input archive log thread=1 sequence=724 recid=124267 stamp=707103840
input archive log thread=1 sequence=725 recid=124268 stamp=707103841
input archive log thread=1 sequence=726 recid=124269 stamp=707103841
RMAN-03009: failure of backup command on d3 channel at 01/01/2010 02:11:33
ORA-19571: archived-log recid 118360 stamp 705446770 not found in control file
continuing other job steps, job failed will not be re-run
channel d6: starting compressed archive log backupset
channel d6: specifying archive log(s) in backup set
input archive log thread=1 sequence=641 recid=124034 stamp=707077994
input archive log thread=1 sequence=642 recid=124035 stamp=707077994
...It's a rac, so shall I restart one instance at a time?? Or the whole thing? I am using an recovery catalog, so should I be connected to the recovery catalog Or control file to do a cross check backup, also when it's doing the backup do u recon it can't fing archivelog in controlfile file as it's not done a resync, should I force it to do a resync after a backup then backup the archive logs??? I really don't want to bounce the db as it's 24/7
-
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 -
ORA-16145: archival for thread# 1 sequence# 1424 in progress
Dear All,
I am configuring data guard between primary and DR databases. After giving "recover standby database" command it is display following error.
SQL> recover standby database;
ORA-00279: change 93766011 generated at 02/22/2013 00:30:05 needed for thread 1
ORA-00289: suggestion :
/u01/app/oracle/oradata/EGXTDR/archives/1_1424_805147492.arc
ORA-00280: change 93766011 for thread 1 is in sequence #1424
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-16145: archival for thread# 1 sequence# 1424 in progress
This is the already applied log file sequence:
SQL> select max(sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
1423
I have checked archive log path and found frequently copying archive logs from sequence# 1424 and later to the physical path.
I think this is the reason for "ORA-16145: archival for thread# 1 sequence# 1424 in progress" error.
Please anyone advice why this continuous copying same archive logs from primary to DR.
Thank you in advance.and found frequently copying archive logs from sequence# 1424 and later to the physical pathDo you mean that Oracle is automatically frequently copying the same archivelogs ? Which sequences -- e.g. does it start at 1424 and continue to 1430 and then restarts at 1424 again , running in a loop ?
Oracle is not known to do that.
OR do you have a background / cron / scripted job that copies the archivelogs --- and is looping ?
Hemant K Chitale -
ORA-00308: cannot open archived log '+DATA'
Hello all,
I created new physical standby but I facing problem with shipping archived file between primary and standby.
Primary : RAC (4 nodes)
Standby : single node with ASM
when I run :
alter database recover managed standby database disconnect from session;
in alert log file :
Managed Standby Recovery not using Real Time Apply
Parallel Media Recovery started with 24 slaves
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Waiting for thread 1 sequence 25738
Tue Mar 03 12:21:13 2015
Completed: alter database recover managed standby database disconnect from session
and when i checked archived files by
select max(sequence#) from v$archivanded_log;
It was null.
I understand thatno shipping between primary and standby till this point i deiced to use manual recovery by :
alter database recover automatic standby database;
But i get this error in alert log file :
alter database recover automatic standby database
Media Recovery Start
started logmerger process
Tue Mar 03 12:38:38 2015
Managed Standby Recovery not using Real Time Apply
Parallel Media Recovery started with 24 slaves
Media Recovery Log +DATA
Errors with log +DATA
Errors in file /u01/app/oracle/diag/rdbms/oracledrs/oracledrs/trace/oracledrs_pr00_4989.trc:
ORA-00308: cannot open archived log '+DATA'
ORA-17503: ksfdopn:2 Failed to open file +DATA
ORA-15045: ASM file name '+DATA' is not in reference form
ORA-279 signalled during: alter database recover automatic standby database..
when i opened oracledrs_pr00_4989.trc: file i find :
*** 2015-03-03 12:38:39.478
Media Recovery add redo thread 4
ORA-00308: cannot open archived log '+DATA'
ORA-17503: ksfdopn:2 Failed to open file +DATA
ORA-15045: ASM file name '+DATA' is not in reference form
When I created i set these parameter in duplicate command:
set db_file_name_convert='+ASM_ORADATA/oracle','+DATA/oracledrs'
set log_file_name_convert='+ASM_ARCHIVE/oracle','+DATA/oracledrs','+ASM_ORADATA/oracle','+DATA/oracledrs'
set control_files='+DATA'
set db_create_file_dest='+DATA'
set db_recovery_file_dest='+DATA'
What please the mistake here
Thanks in advance,Yes I have datafiles under +DATA
ASMCMD> cd +DATA/ORACLEDRS/DATAFILE
ASMCMD> ls
ASD.282.873258045
CATALOG.288.873258217
DEVTS.283.873258091
EXAMPLE.281.873258043
FEED.260.873227069
FEED.279.873257713
INDX.272.873251345
INDX.273.873252239
INDX.278.873257337
SYSAUX.262.873227071
SYSTEM.277.873256531
SYSTEM_2.280.873257849
TB_WEBSITE.284.873258135
TB_WEBSITE.285.873258135
TB_WEBSITE.286.873258181
TB_WEBSITE.287.873258183
UNDOTBS1.275.873253421
UNDOTBS2.276.873255247
UNDOTBS3.261.873227069
UNDOTBS4.271.873245967
USERS.263.873227071
USERS.264.873235507
USERS.265.873235893
USERS.266.873237079
USERS.267.873238225
USERS.268.873243661
USERS.269.873244307
USERS.270.873244931
USERS.274.873252585
asd01.dbf
catalog01
dev01.dbf
example.dbf
feed01.dbf
feed02.dbf
indx01.dbf
indx02.dbf
indx03.dbf
sysaux01.dbf
system01.dbf
system02.dbf
undotbs01.dbf
undotbs02.dbf
undotbs03.dbf
undotbs04.dbf
user1.dbf
users01.dbf
users02.dbf
users03.dbf
users04.dbf
users05.dbf
users06.dbf
users07.dbf
users08.dbf
website01.dbf
website02.dbf
website03.dbf
website04.dbf
ASMCMD>
Standby :
[root@oracledrs ~]# id oracle
uid=54321(oracle) gid=54321(oinstall) groups=54321(oinstall),54322(dba)
Primary :
[root@dbn-prod-1 disks]# id oracle
uid=54321(oracle) gid=54321(oinstall) groups=54321(oinstall),54322(dba)
1- yes i have needed archived files at my primary
2- select inst_id,thread#,group# from gv$log;
Primary :
INST_ID,THREAD#,GROUP#
1,1,1
1,1,2
1,2,3
1,2,4
1,3,5
1,3,6
1,4,7
1,4,8
1,1,9
1,2,10
1,3,11
1,4,12
3,1,1
3,1,2
3,2,3
3,2,4
3,3,5
3,3,6
3,4,7
3,4,8
3,1,9
3,2,10
3,3,11
3,4,12
2,1,1
2,1,2
2,2,3
2,2,4
2,3,5
2,3,6
2,4,7
2,4,8
2,1,9
2,2,10
2,3,11
2,4,12
4,1,1
4,1,2
4,2,3
4,2,4
4,3,5
4,3,6
4,4,7
4,4,8
4,1,9
4,2,10
4,3,11
4,4,12
Standby :
INST_ID,THREAD#,GROUP#
1,1,9
1,1,2
1,1,1
1,2,3
1,2,4
1,2,10
1,3,5
1,3,6
1,3,11
1,4,12
1,4,7
1,4,8
3- That's sample from alert log since i started the standby (for standby and primary)
Standby :
alter database mount standby database
NOTE: Loaded library: /opt/oracle/extapi/64/asm/orcl/1/libasm.so
NOTE: Loaded library: System
SUCCESS: diskgroup DATA was mounted
ERROR: failed to establish dependency between database oracledrs and diskgroup resource ora.DATA.dg
ARCH: STARTING ARCH PROCESSES
Tue Mar 03 18:38:16 2015
ARC0 started with pid=128, OS id=4461
ARC0: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Tue Mar 03 18:38:17 2015
Successful mount of redo thread 1, with mount id 1746490068
Physical Standby Database mounted.
Lost write protection disabled
Tue Mar 03 18:38:17 2015
ARC1 started with pid=129, OS id=4464
Tue Mar 03 18:38:17 2015
ARC2 started with pid=130, OS id=4466
Tue Mar 03 18:38:17 2015
ARC3 started with pid=131, OS id=4468
Tue Mar 03 18:38:17 2015
ARC4 started with pid=132, OS id=4470
Tue Mar 03 18:38:17 2015
ARC5 started with pid=133, OS id=4472
Tue Mar 03 18:38:17 2015
ARC6 started with pid=134, OS id=4474
Tue Mar 03 18:38:17 2015
ARC7 started with pid=135, OS id=4476
Completed: alter database mount standby database
Tue Mar 03 18:38:17 2015
ARC8 started with pid=136, OS id=4478
Tue Mar 03 18:38:17 2015
ARC9 started with pid=137, OS id=4480
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC8: Becoming the 'no FAL' ARCH
ARC2: Becoming the heartbeat ARCH
ARC2: Becoming the active heartbeat ARCH
Tue Mar 03 18:38:18 2015
Starting Data Guard Broker (DMON)
ARC9: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Tue Mar 03 18:38:23 2015
INSV started with pid=141, OS id=4494
Tue Mar 03 18:39:11 2015
alter database recover managed standby database disconnect from session
Attempt to start background Managed Standby Recovery process (oracledrs)
Tue Mar 03 18:39:11 2015
MRP0 started with pid=142, OS id=4498
MRP0: Background Managed Standby Recovery process started (oracledrs)
started logmerger process
Tue Mar 03 18:39:16 2015
Managed Standby Recovery not using Real Time Apply
Parallel Media Recovery started with 24 slaves
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Waiting for thread 1 sequence 25738
Completed: alter database recover managed standby database disconnect from session
Tue Mar 03 18:41:17 2015
WARN: ARCH: Terminating pid 4476 hung on an I/O operation
Killing 1 processes with pids 4476 (Process by index) in order to remove hung processes. Requested by OS process 4224
ARCH: Detected ARCH process failure
Tue Mar 03 18:45:17 2015
ARC2: STARTING ARCH PROCESSES
Tue Mar 03 18:45:17 2015
ARC7 started with pid=127, OS id=4586
Tue Mar 03 18:45:18 2015
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.4.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 03-MAR-2015 18:45:18
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 0
nt OS err code: 0
Client address: <unknown>
ARC7: Archival started
ARC2: STARTING ARCH PROCESSES COMPLETE
Tue Mar 03 18:47:14 2015
alter database recover managed standby database cancel
Tue Mar 03 18:48:18 2015
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.4.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 03-MAR-2015 18:48:18
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 0
nt OS err code: 0
Client address: <unknown>
Tue Mar 03 18:51:18 2015
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.4.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 03-MAR-2015 18:51:18
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 0
nt OS err code: 0
Client address: <unknown>
Error 12170 received logging on to the standby
FAL[client, USER]: Error 12170 connecting to oracle for fetching gap sequence
MRP0: Background Media Recovery cancelled with status 16037
Errors in file /u01/app/oracle/diag/rdbms/oracledrs/oracledrs/trace/oracledrs_pr00_4500.trc:
ORA-16037: user requested cancel of managed recovery operation
Recovery interrupted!
Tue Mar 03 18:51:18 2015
MRP0: Background Media Recovery process shutdown (oracledrs)
Tue Mar 03 18:51:19 2015
Managed Standby Recovery Canceled (oracledrs)
Completed: alter database recover managed standby database cancel
Tue Mar 03 18:51:56 2015
alter database recover automatic standby database
Media Recovery Start
started logmerger process
Tue Mar 03 18:51:56 2015
Managed Standby Recovery not using Real Time Apply
Parallel Media Recovery started with 24 slaves
Media Recovery Log +DATA
Errors with log +DATA
Errors in file /u01/app/oracle/diag/rdbms/oracledrs/oracledrs/trace/oracledrs_pr00_4617.trc:
ORA-00308: cannot open archived log '+DATA'
ORA-17503: ksfdopn:2 Failed to open file +DATA
ORA-15045: ASM file name '+DATA' is not in reference form
ORA-279 signalled during: alter database recover automatic standby database...
Tue Mar 03 18:53:06 2015
db_recovery_file_dest_size of 512000 MB is 0.13% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Primary :
Tue Mar 03 17:13:43 2015
Thread 1 advanced to log sequence 26005 (LGWR switch)
Current log# 1 seq# 26005 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 17:13:44 2015
Archived Log entry 87387 added for thread 1 sequence 26004 ID 0x66aa5a0d dest 1:
Tue Mar 03 18:00:18 2015
Thread 1 advanced to log sequence 26006 (LGWR switch)
Current log# 2 seq# 26006 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Tue Mar 03 18:00:18 2015
Archived Log entry 87392 added for thread 1 sequence 26005 ID 0x66aa5a0d dest 1:
Tue Mar 03 18:55:33 2015
Thread 1 advanced to log sequence 26007 (LGWR switch)
Current log# 9 seq# 26007 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26007 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Tue Mar 03 18:55:33 2015
Archived Log entry 87395 added for thread 1 sequence 26006 ID 0x66aa5a0d dest 1:
Tue Mar 03 19:14:22 2015
Dumping diagnostic data in directory=[cdmp_20150303191422], requested by (instance=4, osid=10234), summary=[incident=1692472].
Dumping diagnostic data in directory=[cdmp_20150303191425], requested by (instance=4, osid=10234), summary=[incident=1692473].
Tue Mar 03 20:00:06 2015
Thread 1 advanced to log sequence 26008 (LGWR switch)
Current log# 1 seq# 26008 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 20:00:07 2015
Archived Log entry 87401 added for thread 1 sequence 26007 ID 0x66aa5a0d dest 1:
Tue Mar 03 21:00:02 2015
Thread 1 advanced to log sequence 26009 (LGWR switch)
Current log# 2 seq# 26009 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Tue Mar 03 21:00:03 2015
Archived Log entry 87403 added for thread 1 sequence 26008 ID 0x66aa5a0d dest 1:
Thread 1 advanced to log sequence 26010 (LGWR switch)
Current log# 9 seq# 26010 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26010 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Tue Mar 03 21:00:06 2015
Archived Log entry 87404 added for thread 1 sequence 26009 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:00:00 2015
Setting Resource Manager plan SCHEDULER[0x32DA]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Tue Mar 03 22:00:00 2015
Starting background process VKRM
Tue Mar 03 22:00:00 2015
VKRM started with pid=184, OS id=4838
Tue Mar 03 22:00:07 2015
Begin automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK"
Tue Mar 03 22:00:25 2015
Thread 1 advanced to log sequence 26011 (LGWR switch)
Current log# 1 seq# 26011 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 22:00:26 2015
Archived Log entry 87408 added for thread 1 sequence 26010 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:00:58 2015
Thread 1 advanced to log sequence 26012 (LGWR switch)
Current log# 2 seq# 26012 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Tue Mar 03 22:01:00 2015
Archived Log entry 87412 added for thread 1 sequence 26011 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:02:37 2015
Thread 1 cannot allocate new log, sequence 26013
Checkpoint not complete
Current log# 2 seq# 26012 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Thread 1 advanced to log sequence 26013 (LGWR switch)
Current log# 9 seq# 26013 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26013 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Tue Mar 03 22:02:41 2015
Archived Log entry 87415 added for thread 1 sequence 26012 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:03:26 2015
Thread 1 cannot allocate new log, sequence 26014
Checkpoint not complete
Current log# 9 seq# 26013 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26013 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Thread 1 advanced to log sequence 26014 (LGWR switch)
Current log# 1 seq# 26014 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 22:03:29 2015
Archived Log entry 87416 added for thread 1 sequence 26013 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:05:50 2015
Thread 1 cannot allocate new log, sequence 26015
Checkpoint not complete
Current log# 1 seq# 26014 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 22:05:52 2015
End automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK"
Thread 1 advanced to log sequence 26015 (LGWR switch)
Current log# 2 seq# 26015 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Tue Mar 03 22:05:54 2015
Archived Log entry 87418 added for thread 1 sequence 26014 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:07:29 2015
Thread 1 cannot allocate new log, sequence 26016
Checkpoint not complete
Current log# 2 seq# 26015 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Thread 1 advanced to log sequence 26016 (LGWR switch)
Current log# 9 seq# 26016 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26016 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Tue Mar 03 22:07:33 2015
Archived Log entry 87421 added for thread 1 sequence 26015 ID 0x66aa5a0d dest 1:
Thread 1 cannot allocate new log, sequence 26017
Checkpoint not complete
Current log# 9 seq# 26016 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26016 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Thread 1 advanced to log sequence 26017 (LGWR switch)
Current log# 1 seq# 26017 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 22:07:39 2015
Archived Log entry 87422 added for thread 1 sequence 26016 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:16:36 2015
Thread 1 advanced to log sequence 26018 (LGWR switch)
Current log# 2 seq# 26018 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
Tue Mar 03 22:16:37 2015
Archived Log entry 87424 added for thread 1 sequence 26017 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:30:06 2015
Thread 1 advanced to log sequence 26019 (LGWR switch)
Current log# 9 seq# 26019 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
Current log# 9 seq# 26019 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
Tue Mar 03 22:30:07 2015
Archived Log entry 87427 added for thread 1 sequence 26018 ID 0x66aa5a0d dest 1:
Tue Mar 03 22:30:18 2015
Thread 1 advanced to log sequence 26020 (LGWR switch)
Current log# 1 seq# 26020 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
Tue Mar 03 22:30:19 2015
Archived Log entry 87428 added for thread 1 sequence 26019 ID 0x66aa5a0d dest 1:
Tue Mar 03 23:07:27 2015
Dumping diagnostic data in directory=[cdmp_20150303230727], requested by (instance=4, osid=25140), summary=[incident=1692496].
Dumping diagnostic data in directory=[cdmp_20150303230730], requested by (instance=4, osid=25140), summary=[incident=1692497].
Thanks in advance sir , -
Archived log application to a cold backup fails with ora-00328
I am testing backup and recovery scenario as mentioned in Metalink Doc id:69468.1 where a cold backup of one production server is restored on a separate machine. Some activity, say a table creation in some schema and insertion of rows in it is followed by a few log switches. Next I moved just the archived logs ( newly generated) to the test machine and proceed as follow to recover but log application is failing as below,any help would be appreciated!
SQL> startup mount;
ORACLE instance started.
Total System Global Area 205520896 bytes
Fixed Size 1248116 bytes
Variable Size 71304332 bytes
Database Buffers 130023424 bytes
Redo Buffers 2945024 bytes
Database mounted.
SQL> recover database until cancel using backup controlfile;
ORA-00279: change 581754 generated at 12/21/2007 02:35:04 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001
ORA-00280: change 581754 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00328: archived log ends at change 581535, need later change 581754
ORA-00334: archived log:
'C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001'
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 until cancel using backup controlfile;
ORA-00279: change 581754 generated at 12/21/2007 02:35:04 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001
ORA-00280: change 581754 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
C:\oracle\product\10.2.0\archive\ARC00001_0641874107.001
ORA-00328: archived log ends at change 581535, need later change 581754
ORA-00334: archived log:
'C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001'
SQL> recover database using backup controlfile;
ORA-00279: change 581754 generated at 12/21/2007 02:35:04 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001
ORA-00280: change 581754 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
C:\oracle\product\10.2.0\archive\ARC00001_0641874107.001
ORA-00328: archived log ends at change 581541, need later change 581754
ORA-00334: archived log:
'C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001'
Please HelpThe error displayed stated you are required to have an specific sequence:
ORA-00280: change 581754 for thread 1 is in sequence #1
Check the contents of the v$recover_file dynamic view and verify if you really have all required archivelog files.
~ Madrid -
ORA-12514: TNS:listener does not currently know of service requested
While connecting "sqlplus SYSADM/SYSADM@HCM" I am getting the below error:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Installation background:
Windows 7 l(64-bit) laptop.
Created linux virtualbox to installl peoplesoft VM templates.
so far installed: Oracle11gR2.vdi and HCMDB.vdi on the linux virtualbox.
Followed the steps exactly what it is in the link below: Got the above error in page 4 of the link at connecting to database via sqlplus.
http://bloggingaboutoracleapplications.org/running-oracle-vm-templates-oracle-enterprise-linux-guide-part-1-7/
Below provided initHCM.ora, tnsnames.ora, listerner.ora and some responses I tried. I could not figure out what causing the issue even after researching in web.
Your help would be highly appreciated.
tnsnames.ora:
=============
# tnsnames.ora Network Configuration File:
HCM =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = hcmdb91)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = HCM)
Listener.ora:
=============
# listener.ora Network Configuration File:
/u01/app/oracle/product/11.2.0.x/db_1/network/admin/listener.ora
# Generated by Oracle configuration tools.
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = hcmdb91)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
initHCM.ora:
============
DB_FILES =256
OPEN_CURSORS = 1000
db_block_size = 8192
remote_login_passwordfile = NONE
undo_tablespace=PSUNDOTS
NLS_LENGTH_SEMANTICS=CHAR
# Cache and I/O
#db_block_size=
db_file_multiblock_read_count=16
# Database Identification
# db_domain=us.oracle.com
# db_name=
# Diagnostics and Statistics
#background_dump_dest=
#core_dump_dest=
#user_dump_dest=
# Job Queues
job_queue_processes=10
# Processes and Sessions
processes=150
# SGA Memory
sga_target=287309824
# Security and Auditing
#audit_file_dest=
#remote_login_passwordfile=EXCLUSIVE
# Shared Server
dispatchers="(PROTOCOL=TCP) (SERVICE=XDB)"
# Sort, Hash Joins, Bitmap Indexes
pga_aggregate_target=95420416
# System Managed Undo and Rollback Segments
undo_management=AUTO
#undo_tablespace=
unnestsubquery=false
# Miscellaneous
compatible=11.2.0.2.0
control_files=(/u01/app/oracle/oradata/HCM/control01.ctl)
DB_NAME=HCM
[oracle@hcmdb91 ~]$ tnsping hcm
TNS Ping Utility for Linux: Version 11.2.0.2.0 - Production on 28-MAR-2013
07:40:37
Copyright (c) 1997, 2010, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST =
hcmdb91)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME =
HCM)))
OK (20 msec)
[oracle@hcmdb91 ~]$
[oracle@hcmdb91 ~]$ tnsping hcm
TNS Ping Utility for Linux: Version 11.2.0.2.0 - Production on 28-MAR-2013
07:40:37
Copyright (c) 1997, 2010, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST =
hcmdb91)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME =
HCM)))
OK (20 msec)
[oracle@hcmdb91 ~]$ lsnrctl start
LSNRCTL for Linux: Version 11.2.0.2.0 - Production on 28-MAR-2013 07:41:32
Copyright (c) 1991, 2010, Oracle. All rights reserved.
TNS-01106: Listener using listener name LISTENER has already been started
[oracle@hcmdb91 ~]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.2.0 - Production on 28-MAR-2013 07:42:20
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Connecting to
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=hcmdb91)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.2.0 - Production
Start Date 28-MAR-2013 07:29:21
Uptime 0 days 0 hr. 13 min. 1 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File
/u01/app/oracle/product/11.2.0.x/db_1/network/admin/listener.ora
Listener Log File
/u01/app/oracle/product/11.2.0.x/db_1/log/diag/tnslsnr/hcmdb91/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=hcmdb91.example.com
)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
The listener supports no services
The command completed successfully
[oracle@hcmdb91 ~]$ lsnrctl services
LSNRCTL for Linux: Version 11.2.0.2.0 - Production on 28-MAR-2013 07:42:44
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Connecting to
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=hcmdb91)(PORT=1521)))
The listener supports no services
The command completed successfully
[oracle@hcmdb91 ~]$
[oracle@hcmdb91 ~]$ sqlplus SYSADM/SYSADM@HCM
SQL*Plus: Release 11.2.0.2.0 Production on Thu Mar 28 07:44:25 2013
Copyright (c) 1982, 2010, Oracle. All rights reserved.
ERROR:
ORA-12514: TNS:listener does not currently know of service requested in
connect descriptor
My guess is that the database service "HCM" is not up and running but not sure how to make up and running. Even I could not find it listed in the linux services list.
Note: Able to login sqlplus using "sqlplus sys/sys as sysdba" but failing to access database table as "select * from PSRECDEFN;"
thanks
Espii.
Edited by: 995437 on Mar 28, 2013 6:52 AM
Edited by: 995437 on Mar 28, 2013 6:59 AMHi Nicolas,
I have no luck and the error still persists.
I have set the "export ORACLE_SID=HCM" from root user and oracle user too.
I guess, I have already loaded database when I ran the "cd /opt/oracle/psft/vm
./oraclevm-template.sh"
The outcome of the above script as similar as below:
Creating
ovm_configure_pre
CreateVirtualEnvironment
/u01/scripts/db-reconfig.sh: line 238: ovm_set_password: command not found
/u01/scripts/db-reconfig.sh: line 239: ovm_configure_network: command not found
INFO:
Starting Oracle database reconfiguration.
Oracle Database Configuration
This will configure on-boot properties of Oracle Database.
The following questions will determine whether the database should be
starting upon system boot, the ports it will use.
Press <Enter> to accept the defaults.
Do you want to relink binaries? (y/n) [n] y
Specify a port that will be used for the database listener [1521]:
Do you want Oracle Database to be started on boot (y/n) [y]:y
Wrote to /etc/sysconfig/oracle11g
Relinking Oracle Binaries...
Oracle Relinking Completed Successfully
Logs: /home/oracle/relink.log
Running orainstRoot.sh and root.sh...
set 2GB tmpfs
Enabling Oracle Database service
Configuration Completed Successfully.
Enter the name of the database SID [TESTDB]:HCM
ORACLE instance started.
Total System Global Area 288104448 bytes
Fixed Size 2225832 bytes
Variable Size 104859992 bytes
Database Buffers 176160768 bytes
Redo Buffers 4857856 bytes
Control file created.
Database altered.
Tablespace altered.
Tablespace altered.
Tablespace altered.
1 row updated.
160 rows updated.
Commit complete.
Kumar - I have found no sqlnet.ora file exist in the $ORACLE_HOME/NETWORK/ADMIN
Edited by: 995437 on Mar 28, 2013 9:15 AM -
Recover database from archive log: Time based recovery
Hi,
Could you pelase help regarding the following:
I have power outage in my machine running oracle 9i on Solaris OS 9
Oracle is mounted but failed to open
Once it is started showing the error message
SQL> startup;
ORACLE instance started.
Total System Global Area 9457089744 bytes
Fixed Size 744656 bytes
Variable Size 3154116608 bytes
Database Buffers 6291456000 bytes
Redo Buffers 10772480 bytes
Database mounted.
ORA-01113: file 4 needs media recovery
ORA-01110: data file 4: '/opt/oracle/oradata/sysdb/indx/indx01.dbf'
So I tried to recover the database
SQL> recover database;
ORA-00279: change 1652948240 generated at 12/03/2007 13:09:08 needed for thread
1
ORA-00289: suggestion : /opt/oracle/oradata/nobilldb/archive/1_183942.dbf
ORA-00280: change 1652948240 for thread 1 is in sequence #183942
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 1652948816 generated at 12/03/2007 13:09:19 needed for thread
1
ORA-00289: suggestion : /opt/oracle/oradata/nobilldb/archive/1_183943.dbf
ORA-00280: change 1652948816 for thread 1 is in sequence #183943
ORA-00278: log file '/opt/oracle/oradata/nobilldb/archive/1_183942.dbf' no
longer needed for this recovery
The power outage at 16:00pm and the recovery archive log file '/opt/oracle/oradata/nobilldb/archive/1_183942.dbf' at 11 am
Always I am applying the next sequence it is giving the same message and asking the next sequence. I have more than 900 archive log from 11am to 4pm and each of them having the size of 100mb and it take 1 minute to get back from each to provide this error message.
How I can start my recovery from say 15:45 onwards until 16:15?
I have all archive logs in the proper destination.
Still my database is not opened and it is starts applying archive log since 5 hours back, please help me regarding this
Thanks in advanceWrong forum. Post your question in the following forum:
General Database Discussions -
ORA-279 signalled during recovery of standby database
Hi All,
I am preparing standby database after taking hot backup and copying those datafiles to standby,
taken controlfile standby controlfile backup from primary
mounted the standby database using standby controlfile using
startup nomount pfile='/u01/stand.ora'
alter database mount standby database;
Now I have started applying archives on standby database after copying all archives from primary to standby box the archives generated during backup using..
recover standby database;
But I am getting the below warning on the recovery screen...
ORA-00279: change 51667629050 generated at 07/02/2009 00:59:43 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55118_652209172.arc
ORA-00280: change 51667629050 for thread 1 is in sequence #55118
ORA-00278: log file '/nodal-archive/archive/1_55117_652209172.arc' no longer
needed for this recovery
ORA-00279: change 51667703096 generated at 07/02/2009 01:06:04 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55119_652209172.arc
ORA-00280: change 51667703096 for thread 1 is in sequence #55119
ORA-00278: log file '/nodal-archive/archive/1_55118_652209172.arc' no longer
needed for this recovery
ORA-00279: change 51667767649 generated at 07/02/2009 01:12:28 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55120_652209172.arc
ORA-00280: change 51667767649 for thread 1 is in sequence #55120
ORA-00278: log file '/nodal-archive/archive/1_55119_652209172.arc' no longer
needed for this recovery
ORA-00279: change 51667831821 generated at 07/02/2009 01:19:40 needed for
thread 1
ORA-00289: suggestion : /nodal-archive/archive/1_55121_652209172.arc
ORA-00280: change 51667831821 for thread 1 is in sequence #55121
ORA-00278: log file '/nodal-archive/archive/1_55120_652209172.arc' no longer
needed for this recovery
and I am getting the below warning on the alert log..........
Sun Jul 5 18:37:36 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Sun Jul 5 18:37:36 2009
Media Recovery Log /nodal-archive/archive/1_55256_652209172.arc
Sun Jul 5 18:40:31 2009
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Sun Jul 5 18:40:31 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Sun Jul 5 18:40:31 2009
Media Recovery Log /nodal-archive/archive/1_55257_652209172.arc
Please suggest what to do now.............
Thanks in Advance,
Sukanta Paul.Hi Sukanta,
I didn't really understand what the problem is...
Let me explain, hope it will be clear.
You created a standby control file, and backed up the database (it doesn't matter in which order). Now, you have a standby database that is ready to apply logs. It will be able to apply log forever, until we will stop it.
The messages you see say the following:
ORA-00279: change 51667831821 generated at 07/02/2009 01:19:40 needed for thread 1 {color:blue} - this says that the recovery process is now at scn 51667831821 {color}
ORA-00289: suggestion : /nodal-archive/archive/1_55121_652209172.arc {color:blue} - the information needed for the recover is in this file (this is only the default name, you can choose other name if the file is called differently) {color}
ORA-00280: change 51667831821 for thread 1 is in sequence #55121 {color:blue} - same here, the needed archive is sequence 55121 {color}
ORA-00278: log file '/nodal-archive/archive/1_55120_652209172.arc' no longer needed for this recovery {color:blue} - this message is after Oracle has applied the log, and it means that this log is no longer needed {color}
Now it will wait for the next log. Again, this process is endless, this is how it is made to allow the standby database to be always synched with the primary.
Liron Amitzi
Senior DBA consultant
[www.dbsnaps.com]
[www.orbiumsoftware.com] -
ORA-10458: standby database requires recovery
hi
kindly help me... i got error when standby open in read only mode
SQL*Plus: Release 11.2.0.3.0 Production on Sat Jan 19 14:37:46 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup mount
ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
ORACLE instance started.
Total System Global Area 5344731136 bytes
Fixed Size 2237776 bytes
Variable Size 1275071152 bytes
Database Buffers 4060086272 bytes
Redo Buffers 7335936 bytes
Database mounted.
SQL> Alter Database Recover Managed Standby Database Disconnect;
Database altered.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
Database altered.
SQL> ALTER DATABASE OPEN READ ONLY;
ALTER DATABASE OPEN READ ONLY
ERROR at line 1:
ORA-10458: standby database requires recovery
ORA-01152: file 22 was not restored from a sufficiently old backup
ORA-01110: data file 22: '/archive/data/undo01.dbf'hi CKPT
I executed the action plan as you recommend and got below information;
SQL> recover standby database;
ORA-00279: change 5983485554580 generated at 01/01/2013 19:27:17 needed for
thread 1
ORA-00289: suggestion : /archive/PROD_1_750568044_45027.ARC
ORA-00280: change 5983485554580 for thread 1 is in sequence #45027
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
'/archive/PROD_1_750568044_45400.ARC'
ORA-00310: archived log contains sequence 45400; sequence 45027 required
ORA-00334: archived log: '/archive/PROD_1_750568044_45400.ARC'
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 22 was not restored from a sufficiently old backup
ORA-01110: data file 22: '/archive/data/undo01.dbf'
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01666: control file is for a standby database
SQL> alter system switch logfile;
alter system switch logfile
ERROR at line 1:
ORA-01109: database not open
---------------------------------- and some other activity but still not found any solution-------------
RMAN> recover database until sequence
2> 45026;
Starting recover at 23-JAN-13
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/23/2013 16:42:47
RMAN-06556: datafile 1 must be restored from backup older than SCN 5983484595990
RMAN> recover database until sequence 45027;
Starting recover at 23-JAN-13
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/23/2013 16:42:59
RMAN-06556: datafile 22 must be restored from backup older than SCN 5983485554580
RMAN> recover database until sequence 45025;
Starting recover at 23-JAN-13
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/23/2013 16:43:09
RMAN-06556: datafile 1 must be restored from backup older than SCN 5983484160276
RMAN> alter database open resetlogs;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 01/23/2013 16:43:25
ORA-01666: control file is for a standby database -
ORA-15001: diskgroup "FRA" does not exist or is not mounted
Dear Experts,
We noticed the error "ORA-15001: diskgroup "FRA" does not exist or is not mounted" on the 2nd node of our 4 nodes RAC database system.
During this weekend, we moved our system to a new data center. After the move was done, we were able to bring up the 4 instances around 3:00 AM. However, 4 hours later (7:00 AM), OEM Grid control alerted us with "archival error" on the 2nd instance. From our investigating, we saw the FRA was dismounted. Below is the oracle alert log file (For secuirty reson, the SID is modified):
Sat Feb 7 03:46:03 2009
Completed: ALTER DATABASE OPEN
Sat Feb 7 03:50:18 2009
Sat Feb 7 07:01:36 2009
Thread 2 advanced to log sequence 8534
Current log# 3 seq# 8534 mem# 0: +REDOGRPA/xyz/onlinelog/redo_03.log
Current log# 3 seq# 8534 mem# 1: +REDOGRPB/xyz/onlinelog/redo_03b.log
Sat Feb 7 07:01:39 2009
ARCH: Archival stopped, error occurred. Will continue retrying
Sat Feb 7 07:01:39 2009
ORACLE Instance XYZ2 - Archival Error
Sat Feb 7 07:01:39 2009
ORA-16038: log 11 sequence# 8533 cannot be archived
ORA-00254: error in archive control string ''
ORA-00312: online log 11 thread 2: '+REDOGRPA/xyz/onlinelog/redo_11.log'
ORA-00312: online log 11 thread 2: '+REDOGRPB/xyz/onlinelog/redo_11b.log'
ORA-15001: diskgroup "FRA" does not exist or is not mounted
ORA-15001: diskgroup "FRA" does not exist or is not mounted It is my understanding, that Oracle will automatically mount the diskgroups on the ASM when the instances are started. In our case, all other diskgroups are started OK but not the FRA diskgroup. Is this a bug with FRA where FRA can not be automatically started up after recycling the instance? Did anyone experience the same situation? Can someone advice?
Thanks!Hello,
We are running oracle 10.2.0.2.
Which section of the alert log file for +ASM2 we need here? I will paste it here the ones when "alter diskgroup all mounted" started at 3:00 AM all the way upto 4:00 AM on Saturday, Feb 7:
SQL> ALTER DISKGROUP ALL MOUNT
Sat Feb 7 03:44:15 2009
NOTE: cache registered group FRA' number=1 incarn=0x1e5bf0d2
NOTE: cache registered group DATAX number=2 incarn=0xbcabf0d1
NOTE: cache registered group REDO2 number=4 incarn=0x1e5bf0d3
NOTE: cache registered group REDOGRPA number=5 incarn=0xbcbbf0d4
NOTE: cache registered group REDOGRPB number=6 incarn=0xbcbbf0d5
NOTE: cache registered group TEMPX number=7 incarn=0xbcbbf0d6
NOTE: cache registered group TEMP number=8 incarn=0x1e6bf0d7
NOTE: cache registered group TIBDATA number=9 incarn=0xbcbbf0d8
NOTE: cache registered group TIBREDO number=10 incarn=0xbcbbf0d9
NOTE: cache registered group TIBTEMP number=11 incarn=0x1ebbf0da
Sat Feb 7 03:44:15 2009
ERROR: no PST quorum in group 1: required 2, found 0
Sat Feb 7 03:44:15 2009
NOTE: cache dismounting group 1/0x1E5BF0D2 (FRA')
NOTE: dbwr not being msg'd to dismount
ERROR: diskgroup FRA' was not mounted
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 2)
ERROR: no PST quorum in group 4: required 2, found 0
Sat Feb 7 03:44:15 2009
NOTE: cache dismounting group 4/0x1E5BF0D3 (REDO2)
NOTE: dbwr not being msg'd to dismount
ERROR: diskgroup REDO2 was not mounted
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 5)
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 6)
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 7)
ERROR: no PST quorum in group 8: required 2, found 0
Sat Feb 7 03:44:15 2009
NOTE: cache dismounting group 8/0x1E6BF0D7 (TEMP)
NOTE: dbwr not being msg'd to dismount
ERROR: diskgroup TEMP was not mounted
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 9)
Sat Feb 7 03:44:15 2009
NOTE: Hbeat: instance not first (grp 10)
ERROR: no PST quorum in group 11: required 2, found 0
Sat Feb 7 03:44:15 2009
NOTE: cache dismounting group 11/0x1EBBF0DA (TIBTEMP)
NOTE: dbwr not being msg'd to dismount
ERROR: diskgroup TIBTEMP was not mounted
NOTE: cache opening disk 0 of grp 2: DATAX_0000 path:/dev/raw/raw61
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 2/0xBCABF0D1 (DATAX)
Sat Feb 7 03:44:16 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:16 2009
NOTE: attached to recovery domain 2
Sat Feb 7 03:44:16 2009
NOTE: opening chunk 4 at fcn 0.1158090 ABA
NOTE: seq=54 blk=4821
Sat Feb 7 03:44:16 2009
NOTE: cache mounting group 2/0xBCABF0D1 (DATAX) succeeded
SUCCESS: diskgroup DATAX was mounted
NOTE: cache opening disk 0 of grp 5: REDOGRPA_0000 path:/dev/raw/raw20
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 5/0xBCBBF0D4 (REDOGRPA)
Sat Feb 7 03:44:16 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:16 2009
NOTE: recovering COD for group 2/0xbcabf0d1 (DATAX)
SUCCESS: completed COD recovery for group 2/0xbcabf0d1 (DATAX)
Sat Feb 7 03:44:16 2009
NOTE: attached to recovery domain 5
Sat Feb 7 03:44:16 2009
NOTE: opening chunk 4 at fcn 0.103802 ABA
NOTE: seq=43 blk=2123
Sat Feb 7 03:44:16 2009
NOTE: cache mounting group 5/0xBCBBF0D4 (REDOGRPA) succeeded
SUCCESS: diskgroup REDOGRPA was mounted
NOTE: cache opening disk 0 of grp 6: REDOGRPB_0000 path:/dev/raw/raw12
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 6/0xBCBBF0D5 (REDOGRPB)
Sat Feb 7 03:44:16 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:17 2009
NOTE: attached to recovery domain 6
Sat Feb 7 03:44:17 2009
NOTE: opening chunk 4 at fcn 0.75866 ABA
NOTE: seq=20 blk=1704
Sat Feb 7 03:44:17 2009
NOTE: cache mounting group 6/0xBCBBF0D5 (REDOGRPB) succeeded
SUCCESS: diskgroup REDOGRPB was mounted
NOTE: cache opening disk 0 of grp 7: TEMPX_0000 path:/dev/raw/raw71
NOTE: F1X0 found on disk 0 fcn 0.25328
NOTE: cache opening disk 1 of grp 7: TEMPX_0001 path:/dev/raw/raw7
NOTE: cache mounting (not first) group 7/0xBCBBF0D6 (TEMPX)
Sat Feb 7 03:44:17 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:17 2009
NOTE: attached to recovery domain 7
Sat Feb 7 03:44:17 2009
NOTE: opening chunk 4 at fcn 0.69473 ABA
NOTE: seq=42 blk=432
Sat Feb 7 03:44:17 2009
NOTE: cache mounting group 7/0xBCBBF0D6 (TEMPX) succeeded
SUCCESS: diskgroup TEMPX was mounted
NOTE: cache opening disk 0 of grp 9: TIBDATA path:/dev/raw/raw86
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 9/0xBCBBF0D8 (TIBDATA)
Sat Feb 7 03:44:17 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:17 2009
NOTE: attached to recovery domain 9
Sat Feb 7 03:44:17 2009
NOTE: opening chunk 4 at fcn 0.102912 ABA
NOTE: seq=12 blk=2050
Sat Feb 7 03:44:17 2009
NOTE: cache mounting group 9/0xBCBBF0D8 (TIBDATA) succeeded
SUCCESS: diskgroup TIBDATA was mounted
NOTE: cache opening disk 0 of grp 10: TIBREDO path:/dev/raw/raw87
NOTE: F1X0 found on disk 0 fcn 0.0
NOTE: cache mounting (not first) group 10/0xBCBBF0D9 (TIBREDO)
Sat Feb 7 03:44:18 2009
kjbdomatt send to node 0
kjbdomatt send to node 2
kjbdomatt send to node 3
Sat Feb 7 03:44:18 2009
NOTE: attached to recovery domain 10
Sat Feb 7 03:44:18 2009
NOTE: opening chunk 4 at fcn 0.18970 ABA
NOTE: seq=12 blk=6577
Sat Feb 7 03:44:18 2009
NOTE: cache mounting group 10/0xBCBBF0D9 (TIBREDO) succeeded
SUCCESS: diskgroup TIBREDO was mounted
Sat Feb 7 03:44:19 2009
NOTE: recovering COD for group 5/0xbcbbf0d4 (REDOGRPA)
SUCCESS: completed COD recovery for group 5/0xbcbbf0d4 (REDOGRPA)
NOTE: recovering COD for group 6/0xbcbbf0d5 (REDOGRPB)
SUCCESS: completed COD recovery for group 6/0xbcbbf0d5 (REDOGRPB)
NOTE: recovering COD for group 7/0xbcbbf0d6 (TEMPX)
SUCCESS: completed COD recovery for group 7/0xbcbbf0d6 (TEMPX)
NOTE: recovering COD for group 9/0xbcbbf0d8 (TIBDATA)
SUCCESS: completed COD recovery for group 9/0xbcbbf0d8 (TIBDATA)
NOTE: recovering COD for group 10/0xbcbbf0d9 (TIBREDO)
SUCCESS: completed COD recovery for group 10/0xbcbbf0d9 (TIBREDO)
Sat Feb 7 03:45:18 2009
Starting background process ASMB
ASMB started with pid=17, OS id=16122
Sat Feb 7 03:49:35 2009
NOTE: ASMB process exiting due to lack of ASM file activity
Starting background process ASMB
ASMB started with pid=18, OS id=25963
Sat Feb 7 03:54:34 2009
NOTE: ASMB process exiting due to lack of ASM file activity
Sat Feb 7 03:54:50 2009
Starting background process ASMB
ASMB started with pid=18, OS id=913
Sat Feb 7 03:57:55 2009
NOTE: ASMB process exiting due to lack of ASM file activity
Sat Feb 7 04:07:26 2009
Starting background process ASMB
ASMB started with pid=21, OS id=23012
Sat Feb 7 04:13:59 2009
NOTE: ASMB process exiting due to lack of ASM file activity
Starting background process ASMB
ASMB started with pid=22, OS id=31320
Sat Feb 7 04:36:43 2009
NOTE: ASMB process exiting due to lack of ASM file activity -
10g standard edition, create a manual standby without ORA-279 and ORA-308.
Hi,
I have a 10 g database 10g r2 on linux rhel 5.2. I've create a standby database from an rman backup on another server (same name, same path....).
every 10 minutes , i switch log on primary database and rsync them to the stanby path on stanby server.
every 10 minutes, i apply the new received archive to the standby database with this script :
sqlplus /nolog
connect / as sysdba
recover database until cancel using backup controlfile;
AUTO
recover database until cancel using backup controlfile;
CANCEL
exit
this script gives some ORA errors like this :
2010/03/31 Wed 11:30:03 Media Recovery Log /v4/db/oradata/LFEX/archives/1_61705_640182036.dbf
2010/03/31 Wed 11:30:03 ORA-308 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
2010/03/31 Wed 11:30:04 ORA-279 signalled during: ALTER DATABASE RECOVER database until cancel using backup controlfile ...
2010/03/31 Wed 11:40:01 ORA-279 signalled during: ALTER DATABASE RECOVER database until cancel using backup controlfile ...
I understand this error, the script is searching the next archive, which doesn't exist at this time, that's OK.
To avoid to have this error, i believe that i can do something like that:
sqlplus /nolog
connect / as sysdba
recover database until time 'sysdate-1/(24*4)' using backup controlfile;
AUTO
exit
i'm searching to replay the archive and stop 15 minutes before sysdate, Is it possible?
when i try this, i have this message :
SQL> recover database until time 'sysdate-1/(24*4)' using backup controlfile;
ORA-01841: L'année (complète) doit être comprise entre -4713 et +9999 et être
différente de 0.
I'm trying to change nls_date_format, nls_lang without any success.
thx.
Antoine.i found a script to do an automatic recover script like this :
recover database until time '2010-04-01:16:49:05' using backup controlfile;
ORA-00279: changement 2456430208 généré à 04/01/2010 16:31:01 requis pour thread 1
ORA-00289: suggestion : /v4/db/oradata/LFEX/archives/1_61853_640182036.dbf
ORA-00280: le changement 2456430208 pour le thread 1 se trouve au no de séquence 61853
ORA-00279: changement 2456432030 généré à 04/01/2010 16:39:01 requis pour thread 1
ORA-00289: suggestion : /v4/db/oradata/LFEX/archives/1_61854_640182036.dbf
ORA-00280: le changement 2456432030 pour le thread 1 se trouve au no de séquence 61854
ORA-00278: le fichier journal
'/v4/db/oradata/LFEX/archives/1_61853_640182036.dbf' n'est plus nécessaire pour cette récupération
So i continue to have some error like ORA-278.... but no more ORA-308 error, it's better, because ORA-278 279 and 280 are only information messages, so i can ignore it in alert.log files.
Only ORA-308 in this case interresting me, to see if an archive is really missing.
thx.
PS : the script standby_recover generate the recover.sql script :
[dblegu@dbback SQL]$ cat $PGLEGU/SQL/standby_recover.sql
connect sys/password as sysdba
set trimspool on linesize 200 head off feedback off sqlprompt "--" verify off
spool &1/SQL/recover.sql
select 'connect sys/password as sysdba'||chr(10)||
'set autorecovery on'||chr(10)||
'recover database until time '''||
to_char(sysdate - 1/(24*4),'YYYY-MM-DD:HH24:MI:SS')||''' using backup controlfile;'||chr(10)||
'exit;' from dual;
spool off
exit
the resul in recover.sql is :
connect sys/password as sysdba
set autorecovery on
recover database until time '2010-04-01:16:49:05' using backup controlfile;
exit;
i found this on site : http://erkanorclog.blogspot.com/2007/08/batch-scripts-to-set-up-asyncronous.html.
Edited by: fleuron on 1 avr. 2010 09:04 -
MANAGED RECOVERY AT STANDBY DATABASE REQURING OLD ARCHIVELOGS ORA-00308
Oracle 9.2.0.4
HP-UX 11.11i
The database in Archivelog mode, single standby database in managed recovery
mode.
keeping standby in sync with manual applying the ARCHIVELOG from primary to
standby database.
primary database was 3 REDO log members of 100 MB with 1 member each.
what i did, 1 drop and re-create the INACTIVE REDO group for all three, and
make them
5 REDO logs of 200 MB with 1 member each,
then in order to keep fresh copy of primary database onto standby database, i
send the cold backup after 15 days (last week) with standby controlfile.
now, with that standby controlfile and the database, i can mount the database
but while to open the database, receives messages as , it requiring the
ARCHIVELOGS generated log time ago.
changes the REDO groups from 3 to 5 and size 100 to 200 MB at INACTIVE state
### Workarounds Used ###
SQL> alter database mount standby database;
Database altered.
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-16004: backup database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/user01/oracle9i/oradata/iobasprd/system01.dbf'
SQL> alter database recover automatic standby database;
alter database recover automatic standby database
ERROR at line 1:
ORA-00279: change 1655989696 generated at 08/12/2005 12:46:25 needed for thread
1
ORA-00289: suggestion :
/user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf
ORA-00280: change 1655989696 for thread 1 is in sequence #16849
ORA-00278: log file
'/user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf' no longer needed
for this recovery
ORA-00308: cannot open archived log
'/user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf'
ORA-27037: unable to obtain file status
HP-UX Error: 2: No such file or directory
Additional information: 3
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /user02/oracle9i/oradata/iobasprd/archive
Oldest online log sequence 53052
Next log sequence to archive 53056
Current log sequence
53056
-----------------------AlertIOBASPRD.log----------------------------
alter database mount standby database
Mon Oct 24 12:05:05 2005
Successful mount of redo thread 1, with mount id 3283884781.
Mon Oct 24 12:05:05 2005
Standby Database mounted.
Completed: alter database mount standby database
Mon Oct 24 12:05:12 2005
alter database open read only
ORA-16004 signalled during: alter database open read only...
Mon Oct 24 12:05:23 2005
alter database recover automatic standby database
Mon Oct 24 12:05:23 2005
Media Recovery Start
Starting datafile 1 recovery in thread 1 sequence 52617
Datafile 1: '/user01/oracle9i/oradata/iobasprd/system01.dbf'
Starting datafile 2 recovery in thread 1 sequence 52617
Datafile 2: '/user01/oracle9i/oradata/iobasprd/TBMS_TS_005.dbf'
Starting datafile 3 recovery in thread 1 sequence 52617
Datafile 3: '/user01/oracle9i/oradata/iobasprd/drsys01.dbf'
Starting datafile 4 recovery in thread 1 sequence 52617
Datafile 132: '/user01/oracle9i/oradata/iobasprd/TBMS_TS_002.dbf'
Starting datafile 133 recovery in thread 1 sequence 52617
Datafile 133: '/user01/oracle9i/oradata/iobasprd/TBMS_TS_003.dbf'
Starting datafile 134 recovery in thread 1 sequence 52617
Datafile 134: '/user01/oracle9i/oradata/iobasprd/TBMS_TS_004.dbf'
Media Recovery Log
Media Recovery Log /user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf
Errors with log /user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf.
ORA-279 signalled during: alter database recover automatic standby database...
Mon Oct 24 12:06:01 2005
Restarting dead background process QMN0
QMN0 started with pid=9
The snap of alertIOBASPRD.log can understand me that it requiring the
ARCHIVELOG 52617 only
and its lying in LOG_ARCHIVE_DET location also as
$ pwd
/user02/oracle9i/oradata/iobasprd/archive
$ ls archive_5261*.dbf
archive_52610.dbf archive_52613.dbf archive_52616.dbf archive_52619.dbf
archive_52611.dbf archive_52614.dbf archive_52617.dbf
archive_52612.dbf archive_52615.dbf archive_52618.dbf
$
now, even the files are lying , why ORACLE requing the old archive logs ?????You haven't given any usefuly information on your problem.
show parameter log_archive_dest
show parameter fal
show parameter dg
What errors are in your alert logs ?
What command are you using to recover ?
Check the contents of v$archived_log
# run on primary to detect failures :-
select destination, status, fail_date, valid_now
from v$archive_dest
where status != 'VALID' or VALID_NOW != 'YES';
# run on standby to get exact position of rollforward :-
select thread#, to_char(snapshot_time,'dd-mon-yyyy:hh24:mi'),
to_char(applied_time,'dd-mon-yyyy:hh24:mi'),
to_char(newest_time,'dd-mon-yyyy:hh24:mi') from V$STANDBY_APPLY_SNAPSHOT;
Are you using dataguard broker ?
Maybe you are looking for
-
Parameter Field Value Elimination Based on Another Parameter
I'd like to make 3 grouping parameters with static values to produce 3 drop downs in the user prompt. The problem is, I'd like for the second drop down to eliminate the choice made from the first drop down and the third drop down to have been elimin
-
Problem in creating MATERIALIZED VIEW
Hello All, I am trying to create the following materialized view and getting this error SQL> CREATE MATERIALIZED VIEW system_active_loss_mv 2 BUILD IMMEDIATE 3 REFRESH FAST ON COMMIT 4 ENABLE QUERY REWRITE 5 AS 6 SELECT zone_name, 7 EXTRACT(YEAR FROM
-
Version: Sql Developer v1.2.1 (32.13) OS: Windows XP SP2 Database: Oracle 10g Symptoms: I have a table with a DATE field. In a record of this field a have a value such as : 12/31/0003 (I know this is a strange date value) but the problem is that if I
-
How to execute Show Desktop.scf in Labview?
Dear all,, Can anyone tell me how to excute Show Desktop.scf in labview? Regards, Santhosh Solved! Go to Solution.
-
Multiple Shipping notifications (Inb.Dlv) created via message type DESADV
Hello All, I'm working on implementing the below SAP Standard process for my client. Version is SAP 4.7. The below process has to be implemented for different legal entities working on Same SAP environment. PO -> SO (Created via IDoc) -> Outbound Del