Production Database Crashed

Dear Members
let see a scneario
i have a primary database and a standby database
my production database crashed
how can i recover my standby database until last comitted transaction. how can i get imy transactions from online redo logs which were on primary database
now my primary database server is crashed i cant login to primary database.
is standby database's redo logs synched with primary database's online redo logs?
please help me out
regards

Hi,
You need to check first whether all online Redo Logs till the point of time - are applied to DB.
Check for logs still need to apply or not - If all the logs are applied then you can stop the real time apply on standby and the cancel the recovery on standby and try to Open the DB in read write mode for access
Is there any other standby apart from this . ??
If not first take the backup of this standby immediately, then recover the DB on primary DB till the point of time of crash and try to mount the DB on primary.
then you can make it as standby.
- Pavan Kumar N
Oracle 9i/10g - OCP
http://oracleinternals.blogspot.com/

Similar Messages

ORACLE 9I DATABASE - CRASH & RECOVER

I AM USING ORACLE 9I FOR LINUX IN A DUAL XEON PROCESSOR SERVER. NOW DATABASE DOES NOT OPEN PROPERLY AND SHOW FOLLOWING MESSAGES:-
1) for SYSDBA user message for startup database
SQL*Plus: Release 9.2.0.1.0 - Production on Thu Aug 21 18:49:14 2003
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Enter user-name: sys as sysdba
Enter password:
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 621875780 bytes
Fixed Size 451140 bytes
Variable Size 335544320 bytes
Database Buffers 285212672 bytes
Redo Buffers 667648 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL>
2) Then we reset the logs the message is:
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/C/app/oracle9ir2/oradata/tepiapp/system01.dbf'
SQL>
3) When connecting with different user the message is :
Enter user-name: mis-dba
Enter password:
ERROR:
ORA-01033: ORACLE initialization or shutdown in progress
SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus
0;oracle@tepiapp:~[oracle@tepiapp oracle]$
Please guide me for detail solutions for this problem
Regards,
FSL

hmmm ok, so it seems that you dont use RMAN to backup your database...
It seems there that your have a controlfile problem after a disk crash. I hope your database is on ARCHIVELOG mode.
Does your database crashed during activity or was idle ?
1. Mount the database
2. set autorecovery on ;
recover database using backup controlfile ;
media recovery complete <= this means that all is ok now
3. alter database open resetlogs ;
if #2 doesnt work cause of redo log problem such as corrupted redo log, or some transactions "blocked" in theses redo log cause of a big crash during the database activity, Oracle will tell you that a redo log is corrupted and will give you the hour of the redo log log entry that Oracle need to recover.
So you will have to make an incomplete recovery (that means you will lose some datas, no much but some) until time.
For example, your redo entry has been corrupted at 12:00:50
1. recover database until time '2003-08-25:12:00:00' ;
2. alter database open resetlogs ;
3. Make a full backup of your database !
Fred

Database crashes when placed in Archivelog mode

My production database continues to crash when I place it in Archivelog mode. This happen especially during the period most of the heavy jobs is running. On the other hand, I created a clone of this very same database on another server in Archivelog mode and it is running great. It’s also honest to say the jobs that run on the production are not running in the clone.
Any advice will be appreciated.
Edited by: Albert Zaza on Apr 27, 2010 8:24 AM

>
Please post last 50 lines of the alert log (there should be a very readable error message).
Sun Jan 17 10:35:29 2010
Thread 1 advanced to log sequence 12834
Current log# 2 seq# 12834 mem# 0: J:\ORA_TPISG64A\TPISG64A\REDO02.LOG
Sun Jan 17 18:21:12 2010
Thread 1 advanced to log sequence 12835
Current log# 3 seq# 12835 mem# 0: J:\ORA_TPISG64A\TPISG64A\REDO03.LOG
Sun Jan 17 23:01:01 2010
Thread 1 advanced to log sequence 12836
Current log# 1 seq# 12836 mem# 0: J:\ORA_TPISG64A\TPISG64A\REDO01.LOG
Mon Jan 18 07:54:55 2010
Thread 1 advanced to log sequence 12837
Current log# 2 seq# 12837 mem# 0: J:\ORA_TPISG64A\TPISG64A\REDO02.LOG
Mon Jan 18 13:03:59 2010
KCF: write/open error block=0x22f online=1
file=2 J:\ORA_TPISG64A\TPISG64A\UNDOTBS01.DBF
error=27072 txt: 'OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 33) The process cannot access the file because another process has locked a portion of the file.'
Mon Jan 18 13:03:59 2010
Errors in file j:\oracle\product\10.2.0\admin\tpisg64a\bdump\tpisg64a_dbw0_4136.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
ORA-01114: IO error writing block to file 2 (block # 559)
ORA-01110: data file 2: 'J:\ORA_TPISG64A\TPISG64A\UNDOTBS01.DBF'
ORA-27072: File I/O error
OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 33) The process cannot access the file because another process has locked a portion of the file.
DBW0: terminating instance due to error 1242
Mon Jan 18 13:03:59 2010
Errors in file j:\oracle\product\10.2.0\admin\tpisg64a\bdump\tpisg64a_pmon_4588.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Mon Jan 18 13:04:00 2010
Errors in file j:\oracle\product\10.2.0\admin\tpisg64a\bdump\tpisg64a_lgwr_5068.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Mon Jan 18 13:04:00 2010
Errors in file j:\oracle\product\10.2.0\admin\tpisg64a\bdump\tpisg64a_j000_728.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Mon Jan 18 13:04:01 2010
Errors in file j:\oracle\product\10.2.0\admin\tpisg64a\bdump\tpisg64a_reco_4824.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Mon Jan 18 13:04:01 2010
Errors in file j:\oracle\product\10.2.0\admin\tpisg64a\bdump\tpisg64a_ckpt_4964.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Mon Jan 18 13:04:01 2010
Errors in file j:\oracle\product\10.2.0\admin\tpisg64a\bdump\tpisg64a_smon_4976.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Mon Jan 18 13:04:01 2010
Errors in file j:\oracle\product\10.2.0\admin\tpisg64a\bdump\tpisg64a_psp0_1584.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Mon Jan 18 13:04:02 2010
Errors in file j:\oracle\product\10.2.0\admin\tpisg64a\bdump\tpisg64a_mman_4364.trc:
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
Mon Jan 18 13:04:13 2010
Instance terminated by DBW0, pid = 4136
Tue Jan 19 07:31:47 2010
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.3.0.
System parameters with non-default values:
processes = 150
__shared_pool_size = 251658240
__large_pool_size = 16777216
__java_pool_size = 16777216
__streams_pool_size = 50331648
streams_pool_size = 50331648
nls_length_semantics = BYTE
resource_manager_plan =
sga_target = 5133828096
control_files = J:\ORA_TPISG64A\TPISG64A\CONTROL01.CTL, J:\ORA_TPISG64A\TPISG64A\CONTROL02.CTL, J:\ORA_TPISG64A\TPISG64A\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 4781506560
compatible = 10.2.0.2.0

Estimation/Indication of Database Crash

OS Information:Any version
OS Information:Windows and/or Linux
Estimation/Indication of Database Crash
Hello,
Its an open question that can you tell me the errors/warnings (at least 3) which are exists in alert log at present, whose meaning is that your database will be crashed in next one hour. I mean which ORA-NNNNN or other in alert log; whose indication is same that your database (not instance) is going to be crash within next one hour definately, so that i may get backup or export. Please let me know that question is clear or not.
If you can please elaborate in view of different oracle version and/or OS, it will additional helpful reply to question.
Regards
Girish Sharma

"there is already a service disruption"
If the archiver stops, then there is no service disruption until all redo log groups are full, so you do have time to fix the problem before then database hangs.
Most archiver hangs are due to disk full which you can avoid if you monitor disk usage, flashback area usage, and have automatic jobs to backup and purge archivelogs.
Archiver hung also happens due to bugs, controlfile locks, disk errors (NFS etc) or network errors (Dataguard), and in these cases you can't predict them with monitoring, so you won't know about them until you get alert log errors.
Another error with a similar result would be ORA-19809 :-
ARC0: Error 19809 Creating archive log file to '/oraexport/d1122/DB1122/archivelog/2010_01_06/o1_mf_1_240_%u_.arc'
Wed Jan 06 16:05:00 2010
Errors in file /opt/oracle/product/diag/rdbms/db1122/db1122/trace/db1122_arc2_3408.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 104857600 bytes is 100.00% used, and has 0 remaining bytes available.
You have following choices to free up space from recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
   then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
   BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
   reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
   system command was used to delete files, then use RMAN CROSSCHECK and
   DELETE EXPIRED commands.
Errors in file /opt/oracle/product/diag/rdbms/db1122/db1122/trace/db1122_arc2_3408.trc:
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 35865088 bytes disk space from 104857600 limit

SAP oracle database crash with errore:ORA-00490: PSP process terminated

Hi ALL,
Our oracle database crash with errore code in trace : ORA:00490; i started database again and it working fine; but could not fine reason of down and what is this erroe all about
can some help me
Errors in file /oracle/SRD/saptrace/background/srd_pmon_28096.trc:
ORA-00490: PSP process terminated with error
Tue Nov 25 09:00:57 2008
PMON: terminating instance due to error 490
Instance terminated by PMON, pid = 28096
Thanks,
Dinesh

Hi stefen,
please find the trace file as below
/oracle/SRD/saptrace/background/srd_pmon_28096.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
With the Partitioning and Data Mining options
ORACLE_HOME = /oracle/SRD/102_64
System name:    SunOS
Node name:      nzlsfn23
Release:        5.10
Version:        Generic_137111-01
Machine:        sun4u
Instance name: SRD
Redo thread mounted by this instance: 1
Oracle process number: 2
Unix process pid: 28096, image: oracle@nzlsfn23 (PMON)
2008-11-25 09:00:57.497
SERVICE NAME:(SYS$BACKGROUND) 2008-11-25 09:00:56.210
SESSION ID:(24.1) 2008-11-25 09:00:56.194
Background process PSP0 found dead
Oracle pid = 6
OS pid (from detached process) = 28098
OS pid (from process state) = 28098
dtp = 38000afd8, proc = 497000860
Dump of memory from 0x000000038000AFD8 to 0x000000038000B020
38000AFD0                   00000005 00000000          [........]
38000AFE0 00000004 97000860 00000000 00000000 [.......`........]
38000AFF0 00000000 50535030 00020000 00000000 [....PSP0........]
38000B000 00006DC2 00000000 00000000 48E50DA4 [..m.........H...]
38000B010 00000001 000E3273 00040081 00000000 [......2s........]
Dump of memory from 0x0000000497000860 to 0x0000000497001048
497000860 02010000 00000000 00000000 00000000 [................]
497000870 00000000 00000000 00000000 00000000 [................]
497000880 00000004 97042570 00000004 97047810 [......%p......x.]
497000890 00000004 97028E68 00000004 97045BE8 [.......h......[.]
4970008A0 00000000 00000000 00000004 97045C70 [..............\p]
4970008B0 00000004 97045C70 00000004 97047800 [......\p......x.]
4970008C0 01060000 00000000 00000004 97025ED8 [..............^.]
4970008D0 00000004 97028E68 00000006 00000000 [.......h........]
4970008E0 00000000 00000000 00000000 00000000 [................]
4970008F0 00000000 00000000 00000004 97042490 [..............$.]
497000900 00000004 970425A0 00000000 00000000 [......%.........]
497000910 00000000 00000000 00000000 00000000 [................]
        Repeat 3 times
497000950 00000003 00000000 00000000 00000000 [................]
        Repeat 1 times
497000970 00000000 00000000 00000000 00000000 [................]
497000980 00000004 00000000 00000000 00000000 [................]
497000990 00000003 00000000 00000000 00000000 [................]
        Repeat 1 times
4970009B0 00000004 00000000 00000000 00000000 [................]
4970009C0 00000005 00000000 00000000 00000000 [................]
4970009D0 00000003 00000000 00000000 00000000 [................]
4970009E0 00000000 00000000 00000000 00000000 [................]
        Repeat 8 times
497000A70 00000000 00000000 00000004 97000A78 [...............x]
497000A80 00000004 97000A78 00000000 00000000 [.......x........]
497000A90 00000000 00000000 00000004 97000A98 [................]
497000AA0 00000004 97000A98 00000000 00000000 [................]
497000AB0 00000000 00000000 00000000 00000000 [................]
        Repeat 2 times
497000AE0 00000000 00000000 00000018 00000030 [...............0]
497000AF0 00000001 00000B3D 00000004 970037D0 [.......=......7.]
497000B00 00000004 580096B0 00000001 00000000 [....X...........]
497000B10 00000000 00000000 00000000 00000000 [................]
        Repeat 2 times
497000B40 00006DC2 00000000 00000000 00000000 [..m.............]
497000B50 00000000 00000000 00000000 00000000 [................]
        Repeat 2 times
497000B80 00000004 97000860 00000000 00000000 [.......`........]
497000B90 00000000 00000000 00000000 00000000 [................]
        Repeat 7 times
497000C10 00000004 97000C10 00000004 97000C10 [................]
497000C20 00000000 00000000 00010000 00000000 [................]
497000C30 00000000 00000117 0000000A 00000000 [................]
497000C40 00006DC2 00000000 00000000 48E50DA4 [..m.........H...]
497000C50 00000001 00000000 00000000 00000000 [................]
497000C60 00000000 00000000 00000000 00000000 [................]
        Repeat 2 times
497000C90 00000000 00000000 00000003 FFFFFFFF [................]
497000CA0 00000000 00000000 00000000 00000000 [................]
        Repeat 13 times
497000D80 73726461 646D0000 00000000 00000000 [srdadm..........]
497000D90 00000000 00000000 00000000 00000000 [................]
497000DA0 00000000 00000006 6E7A6C73 666E3233 [........nzlsfn23]
497000DB0 00000000 00000000 00000000 00000000 [................]
        Repeat 2 times
497000DE0 00000000 00000000 00000000 00000008 [................]
497000DF0 554E4B4E 4F574E00 00000000 00000000 [UNKNOWN.........]
497000E00 00000000 00000000 00000000 00000000 [................]
497000E10 00000000 00000008 32383039 38000000 [........28098...]
497000E20 00000000 00000000 00000000 00000000 [................]
497000E30 00000000 00000005 6F726163 6C65406E [........oracle@n]
497000E40 7A6C7366 6E323320 28505350 30290000 [zlsfn23 (PSP0)..]
497000E50 00000000 00000000 00000000 00000000 [................]
497000E60 00000000 00000000 00000000 00000016 [................]
497000E70 00000000 00000002 00000000 00000000 [................]
497000E80 00000000 00000000 00000000 00000000 [................]
        Repeat 8 times
497000F10 00000000 00000000 00000000 00020000 [................]
497000F20 00000000 00000000 00000000 00000000 [................]
497000F30 00000000 00000000 00000003 9E1F6748 [..............gH]
497000F40 00000004 97001728 00000004 97000758 [.......(.......X]
497000F50 00000000 00000000 00000003 9E26B5B0 [.............&..]
497000F60 00000000 00000000 00000000 00000000 [................]
        Repeat 1 times
497000F80 00000004 97000F80 00000004 97000F80 [................]
497000F90 00000000 00040000 00000000 00000000 [................]
497000FA0 00000000 00031A55 00000000 0004D7DD [.......U........]
497000FB0 00000000 00071A55 00000000 00000000 [.......U........]
497000FC0 00000000 00000000 00000000 00000000 [................]
497000FD0 00000000 00000828 00000000 000000E0 [.......(........]
497000FE0 00000000 00000828 00000000 00000000 [.......(........]
497000FF0 00000000 00000000 00000000 00000000 [................]
        Repeat 4 times
497001040 00000002 00000000                    [........]
error 490 detected in background process
ORA-00490: PSP process terminated with error

Production Database Backup

I have a replicated production database to which I cannot perform a backup very often. We have got a one-off window to take a backup.
What I would like to know is whch particular backup to take...cold backup or user managed backup. I can take both, howver, in case of disaster reovery, I would only have this backup mand the archived redo logs and maybe access to one or two ionline redo log group files.
o which backup should I take which will allow me to recover the database using there archived and redo log files? Cold backups or user-managed backups?
Basically what I am asking is which backups allow redo logs to be applied to recover database to point in time when it crashed since it is a replicated database?
OS Win2K As Svr, Oracle DB 9.2.0.6,
Thanks in advance

What do you mean by replicated database?
I would go for RMAN backups with open database (database must be in archivelog).
I think this is the best env for performing backups, I would also suggest using
RMAN catalog if you have an option to use it.
Best Regards
Krystian Zieja / mob

Oracle 11g 64 bit on Linux - Restore failure in production database

Hi guru,
We used to take full hot backup with the help of BackupExec of Symantec in our production database.We have two different oracle database (not cluster).
We defined same policy for both .We defined schedule on Symantec to take full hot backup every night of database on tap drive.At any point of time we maintain only 2 full backup for each database on tap and then recycle it.
Yesterday suddenly storage of database failed for both.?It was complete failure so we did not have any option but to restore last night full backup.
It has done successfully for one database but when we tried to restore second from last night backup it thrown error :
channel ch0: ORA-19870: error while restoring backup piece BE_9kjsfol6_1_1
ORA-19507: failed to retrieve sequential file, handle="BE_9kjsfol6_1_1", parms=""
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text
then we tried to restore backup of last to last night and it gave again error :
channel ch0: ORA-19870: error while restoring backup piece BE_9djsaman_1_1
ORA-19507: failed to retrieve sequential file, handle="BE_9djsaman_1_1", parms=""
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text
But we have seen log of Symantec at the time of backup and it said that backup has successfully completed.
right now I am in big trouble I tried almost all possible combination of symantec to restore database but got no success.I used script generated by symantec and tried to run that on RMAN directly but it is throwing same error.
Please help me if possible an throw some light on exception (as I understand it says it is not able to find some piece on tap but we have not touched tap and tap media is completely safe.)
I am pasting complete text log generated by Symantec at the time of restore attempt:
Recovery Manager: Release 11.1.0.6.0 - Production on Sun Oct 12 01:26:45 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
# RMAN command section
RUN {
ALLOCATE CHANNEL ch0
TYPE 'SBT_TAPE';
SEND 'BSA_SERVICE_HOST=192.168.0.135,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE={E8E38B61-7C1B-41A2-A2D7-8BB38A516AD3},NBBSA_DB_DEVICE_NAME=Oracle-Linux::\\G1-1-BLD-DSA2\sniffer2';
RESTORE
DATABASE
UNTIL TIME "TO_DATE('10-08-2008:12:00:41', 'MM-DD-YYYY:HH24:MI:SS')";
RECOVER
DATABASE
UNTIL TIME "TO_DATE('10-08-2008:12:00:41', 'MM-DD-YYYY:HH24:MI:SS')";
RELEASE CHANNEL ch0;
connected to target database: SNIFFER2 (DBID=3949735487, not open)
using target database control file instead of recovery catalog
allocated channel: ch0
channel ch0: SID=316 device type=SBT_TAPE
channel ch0: Symantec/BackupExec/1.1.0
sent command to channel: ch0
Starting restore at 12-OCT-08
channel ch0: starting datafile backup set restore
channel ch0: specifying datafile(s) to restore from backup set
channel ch0: restoring datafile 00001 to /home/oracle/app/oracle/oradata/sniffer2/system01.dbf
channel ch0: restoring datafile 00002 to /home/oracle/app/oracle/oradata/sniffer2/sysaux01.dbf
channel ch0: restoring datafile 00003 to /home/oracle/app/oracle/oradata/sniffer2/undotbs01.dbf
channel ch0: restoring datafile 00004 to /home/oracle/app/oracle/oradata/sniffer2/users01.dbf
channel ch0: restoring datafile 00005 to /home/oracle/app/oracle/oradata/sniffer2/system02.dbf
channel ch0: restoring datafile 00006 to /home/oracle/app/oracle/oradata/sniffer2/sysaux02.dbf
channel ch0: restoring datafile 00007 to /Ora2Meta/metatab01.dbf
channel ch0: restoring datafile 00008 to /home/oracle/app/oracle/oradata/sniffer2/UNDOTBS103.dbf
channel ch0: restoring datafile 00009 to /Ora2Data/blobdata01.dbf
channel ch0: restoring datafile 00010 to /Ora2Data/blobdata02.dbf
channel ch0: restoring datafile 00013 to /Ora2BTreeIndex/bindtab02.dbf
channel ch0: restoring datafile 00014 to /Ora2DomainIndex/domaintab01.dbf
channel ch0: reading from backup piece BE_9kjsfol6_1_1
channel ch0: ORA-19870: error while restoring backup piece BE_9kjsfol6_1_1
ORA-19507: failed to retrieve sequential file, handle="BE_9kjsfol6_1_1", parms=""
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text
channel ch0: starting datafile backup set restore
channel ch0: specifying datafile(s) to restore from backup set
channel ch0: restoring datafile 00011 to /Ora2Data/blobdata03.dbf
channel ch0: restoring datafile 00015 to /Ora2DomainIndex/domaintab02.dbf
channel ch0: reading from backup piece BE_9ljsfqm6_1_1
channel ch0: piece handle=BE_9ljsfqm6_1_1 tag=TAG20081006T155830
channel ch0: restored backup piece 1
channel ch0: restore complete, elapsed time: 00:11:35
channel ch0: starting datafile backup set restore
channel ch0: specifying datafile(s) to restore from backup set
channel ch0: restoring datafile 00012 to /Ora2Data/blobdata04.dbf
channel ch0: reading from backup piece BE_9mjsfrcb_1_1
channel ch0: piece handle=BE_9mjsfrcb_1_1 tag=TAG20081006T155830
channel ch0: restored backup piece 1
channel ch0: restore complete, elapsed time: 00:02:55
failover to previous backup
skipping datafile 1; already restored to file /home/oracle/app/oracle/oradata/sniffer2/system01.dbf
channel ch0: starting datafile backup set restore
channel ch0: specifying datafile(s) to restore from backup set
channel ch0: restoring datafile 00002 to /home/oracle/app/oracle/oradata/sniffer2/sysaux01.dbf
channel ch0: restoring datafile 00003 to /home/oracle/app/oracle/oradata/sniffer2/undotbs01.dbf
channel ch0: restoring datafile 00004 to /home/oracle/app/oracle/oradata/sniffer2/users01.dbf
channel ch0: restoring datafile 00005 to /home/oracle/app/oracle/oradata/sniffer2/system02.dbf
channel ch0: restoring datafile 00006 to /home/oracle/app/oracle/oradata/sniffer2/sysaux02.dbf
channel ch0: restoring datafile 00007 to /Ora2Meta/metatab01.dbf
channel ch0: restoring datafile 00008 to /home/oracle/app/oracle/oradata/sniffer2/UNDOTBS103.dbf
channel ch0: restoring datafile 00009 to /Ora2Data/blobdata01.dbf
channel ch0: restoring datafile 00010 to /Ora2Data/blobdata02.dbf
channel ch0: restoring datafile 00013 to /Ora2BTreeIndex/bindtab02.dbf
channel ch0: restoring datafile 00014 to /Ora2DomainIndex/domaintab01.dbf
channel ch0: reading from backup piece BE_9djsaman_1_1
channel ch0: piece handle=BE_9djsaman_1_1 tag=TAG20081004T174806
channel ch0: restored backup piece 1
channel ch0: restore complete, elapsed time: 00:29:55
Finished restore at 12-OCT-08
Starting recover at 12-OCT-08
starting media recovery
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 2 needs more recovery to be consistent
ORA-01110: data file 2: '/home/oracle/app/oracle/oradata/sniffer2/sysaux01.dbf'
released channel: ch0
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 10/12/2008 02:12:48
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of archived log for thread 1 with sequence 34786 and starting SCN of 327309500 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34785 and starting SCN of 327301335 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34784 and starting SCN of 327293588 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34783 and starting SCN of 327283177 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34782 and starting SCN of 327276129 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34781 and starting SCN of 327270761 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34780 and starting SCN of 327259154 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34779 and starting SCN of 327247460 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34778 and starting SCN of 327238239 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34777 and starting SCN of 327230121 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34776 and starting SCN of 327221510 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34775 and starting SCN of 327215378 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34774 and starting SCN of 327212076 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34773 and starting SCN of 327211654 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34772 and starting SCN of 327211171 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34771 and starting SCN of 327202005 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34770 and starting SCN of 327194156 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34769 and starting SCN of 327183755 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34768 and starting SCN of 327182026 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34767 and starting SCN of 327179450 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34766 and starting SCN of 327172246 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34765 and starting SCN of 327161460 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34764 and starting SCN of 327157752 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34763 and starting SCN of 327149852 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34762 and starting SCN of 327142049 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34761 and starting SCN of 327134814 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34760 and starting SCN of 327128948 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34759 and starting SCN of 327029461 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34758 and starting SCN of 326986719 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34757 and starting SCN of 326981601 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34756 and starting SCN of 326978697 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34755 and starting SCN of 326978093 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34754 and starting SCN of 326977904 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34753 and starting SCN of 326976801 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34752 and starting SCN of 326973891 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34751 and starting SCN of 326970649 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34750 and starting SCN of 326962803 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34749 and starting SCN of 326958315 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34748 and starting SCN of 326955232 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34747 and starting SCN of 326951908 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34746 and starting SCN of 326943909 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34745 and starting SCN of 326935460 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34744 and starting SCN of 326922741 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34743 and starting SCN of 326910246 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34742 and starting SCN of 326905072 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34741 and starting SCN of 326901097 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34740 and starting SCN of 326900178 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34739 and starting SCN of 326899668 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34738 and starting SCN of 326899106 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34737 and starting SCN of 326891014 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34736 and starting SCN of 326875443 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34735 and starting SCN of 326863782 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34734 and starting SCN of 326842985 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34733 and starting SCN of 326838670 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34732 and starting SCN of 326823584 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34731 and starting SCN of 326821851 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34730 and starting SCN of 326820427 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34729 and starting SCN of 326816378 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34728 and starting SCN of 326812324 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34727 and starting SCN of 326802760 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34726 and starting SCN of 326790469 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34725 and starting SCN of 326779939 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34724 and starting SCN of 326771711 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34723 and starting SCN of 326757052 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34722 and starting SCN of 326739164 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34721 and starting SCN of 326730107 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34720 and starting SCN of 326721606 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34719 and starting SCN of 326718543 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34718 and starting SCN of 326715249 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34717 and starting SCN of 326709503 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34716 and starting SCN of 326693713 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34715 and starting SCN of 326680021 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34714 and starting SCN of 326674022 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34713 and starting SCN of 326664781 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34712 and starting SCN of 326648917 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34711 and starting SCN of 326637659 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34710 and starting SCN of 326633287 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34709 and starting SCN of 326632166 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34708 and starting SCN of 326621042 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34707 and starting SCN of 326617608 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34706 and starting SCN of 326613463 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34705 and starting SCN of 326611471 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34704 and starting SCN of 326610305 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34703 and starting SCN of 326602873 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34702 and starting SCN of 326601517 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34701 and starting SCN of 326593022 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34700 and starting SCN of 326577874 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34699 and starting SCN of 326567243 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34698 and starting SCN of 326553641 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34697 and starting SCN of 326544480 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34696 and starting SCN of 326531815 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34695 and starting SCN of 326528717 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34694 and starting SCN of 326522442 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34693 and starting SCN of 326515260 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34692 and starting SCN of 326504255 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34691 and starting SCN of 326494511 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34690 and starting SCN of 326484165 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34689 and starting SCN of 326475207 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34688 and starting SCN of 326470137 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34687 and starting SCN of 326463888 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34686 and starting SCN of 326456866 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34685 and starting SCN of 326415614 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34684 and starting SCN of 326398980 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34683 and starting SCN of 326385176 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34682 and starting SCN of 326373763 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34681 and starting SCN of 326365337 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34680 and starting SCN of 326352830 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34679 and starting SCN of 326351732 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34678 and starting SCN of 326351526 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34677 and starting SCN of 326351228 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34676 and starting SCN of 326350869 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34675 and starting SCN of 326350236 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34674 and starting SCN of 326344630 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34673 and starting SCN of 326336226 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34672 and starting SCN of 326334353 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34671 and starting SCN of 326332206 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34670 and starting SCN of 326325188 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34669 and starting SCN of 326323615 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34668 and starting SCN of 326317656 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34667 and starting SCN of 326304700 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34666 and starting SCN of 326296332 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34665 and starting SCN of 326283118 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34664 and starting SCN of 326270792 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34653 and starting SCN of 326183189 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34652 and starting SCN of 326175000 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34651 and starting SCN of 326159778 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34650 and starting SCN of 326154245 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34649 and starting SCN of 326148100 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34648 and starting SCN of 326142540 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34647 and starting SCN of 326136812 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34646 and starting SCN of 326124534 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34645 and starting SCN of 326118922 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34644 and starting SCN of 326111890 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34643 and starting SCN of 326108132 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 34642 and starting SCN of 326102908 found to restore
RMAN-00567: Recovery Manager could not print some error messages
Recovery Manager complete.

see metalink note 465558.1
https://metalink2.oracle.com/metalink/plsql/f?p=130:14:6831911279782618352::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,465558.1,1,1,1,helveticaKhurram

Creating standby database from ASM production database in standard edition

Hi,
I am using oracle 10g release 2 standard edition. I recently created a database instance and wanted to create a standby database instance. After sorting out how to achieve this without managed standby and data guard I finally got it working and the shipped archive logs are applied and working well on the standby database.
Now I am thinking of re-creating my production database and using ASM for storage managment. By doing this can a standby database still be created from a primary database using ASM? I want to be sure I can before I commit to using ASM for the production instance and manually creating a standby database from that instance.
Note: I am using standard edition not enterprise edition.

Hi
For Oracle SE standby, you can visit www.anbultechnologies.co.uk , they have a brilliant product name DRMC which is Automatic disaster recovery solution with automatic failover in case primary goes down due to any reason.
We are using this product for more than 2 years and it works like a dream using Oracle Standard Edition. We have depolyed more databases and Standby solution within the prices of 2 EE edition licenses.
You can give ma try as well.
website address is www.anbultechnologies.co.uk

SQL Server Reporting Services installed on a production database server used to support JD Edwards EnterpriseOne. What performance isses can arise

SQL Server Reporting Services installed on a production database server used to support JD Edwards EnterpriseOne. What performance isses can arise. Is it recommended. What are the pros and cons

Hi hazelannc,
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated. Thank you for your understanding and support.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Mount STANDBY with EE software created from SE production database

We mount (by error) our STANDBY databases with Enterprise Edition EE softare.
Our production database is Standard Edition SE.
We apply the logs without problem, but we have intention the mount the STANDBY database with SE software.
-> Could be possible mount the STANDBY database without need to recreate it? Remember the origin db are created from SE software and mount the STANDBY with EE software.
Thanks you!
Any help are welcome.
Diego.

Please read Note:139642.1 on metalink.

Changes are not reflected in Staging or Production Database - BCC

Hi,
I changed an asset from product catalog and able to see successful deployment in BCC. But, I am not able to see the changes in Staging or Production database.
I see only changes in Versioned Database.
Did the following things to see if thee is any error but there is no error during this operations.
1) Enabled all the logs for DeploymentManager, DeploymentServer.
2) Ran the CatalogMaintenanceService.
Please help me in resolving this issue.
Thanks,
DKAP

Adding to Desai, check for the repository mapping in agents, i.e in your production agent, you need to map the repositories to production repositories. For example ProductCatalog should be mapped to ProductCatalogproduction, similarly in Staging agent as well.
Cheers
R

Production database Alert log Message

Hi,
I am using oracle 10gR1 on windows.Recently i have created a physical standby database (sid=smtm) and production database (sid=mtm).My production alter log file dispaly some thing like please suggest my what it shows.
Mon Mar 02 00:18:31 2009
Private_strands 7 at log switch
Thread 1 advanced to log sequence 35722
Current log# 4 seq# 35722 mem# 0: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\REDO04.LOG
Current log# 4 seq# 35722 mem# 1: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\REDO04_A.LOG
Mon Mar 02 00:18:31 2009
ARC1: Evaluating archive   log 2 thread 1 sequence 35721
ARC1: Destination LOG_ARCHIVE_DEST_2 archival not expedited
Committing creation of archivelog 'E:\ORACLE\MTM\ARCHIVES\MTM_945F37AC_1_35721_500044525.ARC'
Invoking non-expedited destination LOG_ARCHIVE_DEST_2 thread 1 sequence 35721 host SMTM
*FAL[server, ARC1]: Begin FAL noexpedite archive (branch 500044525 thread 1 sequence 35721 dest SMTM)*
*FAL[server, ARC1]: Complete FAL noexpedite archive (thread 1 sequence 35721 destination SMTM)*Mon Mar 02 00:29:42 2009
Private_strands 7 at log switch
Thread 1 advanced to log sequence 35723
Current log# 3 seq# 35723 mem# 0: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\REDO03.LOG
Current log# 3 seq# 35723 mem# 1: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\REDO03_A.LOG
Mon Mar 02 00:29:42 2009
ARC1: Evaluating archive   log 4 thread 1 sequence 35722
ARC1: Destination LOG_ARCHIVE_DEST_2 archival not expedited
Committing creation of archivelog 'E:\ORACLE\MTM\ARCHIVES\MTM_945F37AC_1_35722_500044525.ARC'
Invoking non-expedited destination LOG_ARCHIVE_DEST_2 thread 1 sequence 35722 host SMTM
*FAL[server, ARC1]: Begin FAL noexpedite archive (branch 500044525 thread 1 sequence 35722 dest SMTM)*
*FAL[server, ARC1]: Complete FAL noexpedite archive (thread 1 sequence 35722 destination SMTM)*
Thanks

Sorry i have no metalink account.
On production database there is no any ORA error and on standby database Alert log shows.
Mon Mar 02 03:40:38 2009
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35728_500044525.ARC'
Committing creation of archivelog 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35728_500044525.ARC'
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35729_500044525.ARC'
Committing creation of archivelog 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35729_500044525.ARC'
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35730_500044525.ARC'
Committing creation of archivelog 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35730_500044525.ARC'Mon Mar 02 04:29:14 2009
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35731_500044525.ARC'
Committing creation of archivelog 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35731_500044525.ARC'
Media Recovery Log
ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...Mon Mar 02 11:01:57 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Mon Mar 02 11:01:57 2009
Media Recovery Log E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35553_500044525.ARC
ORA-279 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT ...Mon Mar 02 11:02:05 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35554_500044525.ARC
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Mon Mar 02 11:02:14 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35555_500044525.ARC
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Regards
Thanks for reply.

Production database version 10.1.0.3 to 10.2

We are planning to upgrade the production database version 10.1.0.3 to 10.2 version.
Please provide the link to download the any standard document related to upgrade the oracle version 10.1.0.3 to 10.2.

You can directly upgrade 10.1.0.3 to 10.2.0.2 by using 10.2.0.2 complete software distribution but not 10.2.0.2 patch set.
10.2.0.2 Patch set requires 10.2.0.1 base release first.
To proceed with the upgrade review instructions from Oracle Database upgrade guide 10.2 from OTN.
http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14238.pdf
Regards
Vignesh Bala

Adding new column to production database

I have to add a new timestamp column, that defaults to the current date/time, to an existing production database. The table is large - 150M records. I am trying to understand the ramifications of adding a new column to a table this large that gets hit often, mostly with inserts and reads. The column does allow null values and I am not going back and populating existing records with a value. Basically, I am looking for some best practice guidelines - how to prepare, what to expect, what other processes should be followed along with this schema update.

Radiators wrote:
Thanks, I have not found any %TYPE or %ROWTYPE dependencies on the table I am altering. But at the same time I do not understand how these types of dependencies would invalidate packages. I wouldn't be breaking any %TYPE dependency because I am not dropping columns, only adding a new one. And according to documentation for %ROWTYPE - "If columns are later added to or dropped from the table, your code can keep working without changes." Can you point me to Oracle documentation that describes your concern in detail? Thanks.you can test it yourself
SQL> CREATE TABLE abc (c1 NUMBER);
Table created.
SQL> INSERT INTO abc
2       VALUES (99);
1 row created.
SQL> CREATE OR REPLACE PROCEDURE test_proc
2 AS
3     v   abc%ROWTYPE;
4 BEGIN
5     SELECT c1
6       INTO v
7       FROM abc
8       WHERE ROWNUM = 1;
9 END;
10 /
Procedure created.
SQL> SELECT object_name, status
2    FROM user_objects
3   WHERE object_name = 'TEST_PROC';
OBJECT_NAME                STATUS
TEST_PROC                    VALID
SQL> ALTER TABLE abc ADD (c2 VARCHAR2(10));
Table altered.
SQL> SELECT object_name, status
2    FROM user_objects
3   WHERE object_name = 'TEST_PROC';
OBJECT_NAME                 STATUS
TEST_PROC                     INVALID
SQL> you should also consider the chance that some where if people are using "select * into" using this table, which will fail since you added new column. i don't see any unusual performance bottlenecks by adding a new column. in case of the backups, yes the earlier backups will not have the column. if you restore it, you will see earlier table structure itself. i have one specific question. why are you not attempting this in development/test environment first? even if it is a simple insert, it's always important to do it in test environments before attempting on production db. one thing for sure i know is, after adding column, you will have to recompile all the invalid dependencies. i think, it's better if you attempt it in test db and come up with any issues you see rather than asking a general question where problematic scenarios are plenty and rarely unknown before hand.

Daily export backup (via datapump) of a 600GB production database

Hi Guys,
I have a 600GB DB.
10G Database.
Currently I have daily rman backup to tape.
Based on your experience, should i bother to perform a daily export of production database of such size?
Do u think it's useful?
thanks

Fran wrote:
All depends, what do you want to do? Do you have enough space to save a backup and export daily?
In my opinion with one backup is enough to save your database. I'm sorry, I can't agree with that. I've been in situations where the first, second and THIRD backup sources have been unavailable in the event of a Production restore. I had to go to Plan D and cross my fingers (and sweat a lot). That might be overkill, but you should never rely on just one backup method/source for Production data.
Not only that, but, obviously, you can also use an export of the data and import into another database or a schema inside the database in case you need to address any logical corruption. We also use the exports to refresh test databases.
We have many similar sizes of databases and we take exports weekly, instead of daily. An export will be an incomplete backup, obviously, though you can ensure consistency by giving it an SCN to use as a datapoint. You can also run Data Pump in parallel which does speed things up.
If you use it as part of your backup strategy, I'd make sure I had regular backups of the parameter file and the controlfiles (both binary and trace). I'd also make sure I had regular txt files showing the necessary information for the tablespaces and the datafiles which you can use to recreate the files in case you needed to.
Mark

Production Database Crashed

Similar Messages

Maybe you are looking for