Block corrruption in production database

pl help me to detect and remove block corruption error
find alertlog
Archived Log entry 2717 added for thread 1 sequence 3027 ID 0x552bc791 dest 1:
Mon Jul 05 08:30:52 2010
kewastUnPackStats(): bad magic 1 (0x110aaa2ad, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa2ad, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa2ad, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa2ad, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa2bd, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa2bd, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa2ad, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa2ad, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa2a5, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa2a5, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa2b5, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa2b5, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa15d, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa15d, 0)
kewastUnPackStats(): bad magic 1 (0x110aa9edd, 0)
kewastUnPackStats(): bad magic 1 (0x110aa9edd, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa015, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa015, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa015, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa015, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa14d, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa14d, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa027, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa027, 0)
kewastUnPackStats(): bad magic 1 (0x110a6cec7, 0)
kewastUnPackStats(): bad magic 1 (0x110a6cec7, 0)
kewastUnPackStats(): bad magic 1 (0x110a6ceb7, 0)
kewastUnPackStats(): bad magic 1 (0x110a6ceb7, 0)
kewastUnPackStats(): bad magic 1 (0x110a6cebf, 0)
kewastUnPackStats(): bad magic 1 (0x110a6cebf, 0)
kewastUnPackStats(): bad magic 1 (0x110a6ceb7, 0)
kewastUnPackStats(): bad magic 1 (0x110a6ceb7, 0)
kewastUnPackStats(): bad magic 1 (0x110a6cebf, 0)
kewastUnPackStats(): bad magic 1 (0x110a6cebf, 0)
kewastUnPackStats(): bad magic 1 (0x110a6cd97, 0)
kewastUnPackStats(): bad magic 1 (0x110a6cd97, 0)
kewastUnPackStats(): bad magic 1 (0x110a6cec7, 0)
kewastUnPackStats(): bad magic 1 (0x110a6cec7, 0)
kewastUnPackStats(): bad magic 1 (0x110a6d15f, 0)
kewastUnPackStats(): bad magic 1 (0x110a6d15f, 0)
kewastUnPackStats(): bad magic 1 (0x110a6d157, 0)
kewastUnPackStats(): bad magic 1 (0x110a6d157, 0)
kewastUnPackStats(): bad magic 1 (0x110a6cfff, 0)
kewastUnPackStats(): bad magic 1 (0x110a6cfff, 0)
kewastUnPackStats(): bad magic 1 (0x110a6cfff, 0)
kewastUnPackStats(): bad magic 1 (0x110a6cfff, 0)
kewastUnPackStats(): bad magic 1 (0x110a6cfff, 0)
kewastUnPackStats(): bad magic 1 (0x110a6cfff, 0)
kewastUnPackStats(): bad magic 1 (0x110a6cebf, 0)
kewastUnPackStats(): bad magic 1 (0x110a6cebf, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa03f, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa03f, 0)
kewastUnPackStats(): bad magic 1 (0x110a6d017, 0)
kewastUnPackStats(): bad magic 1 (0x110a6d017, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa01f, 0)
kewastUnPackStats(): bad magic 1 (0x110aaa01f, 0)
kewastUnPackStats(): bad magic 1 (0x110a6d15f, 0)
kewastUnPackStats(): bad magic 1 (0x110a6d15f, 0)
kewastUnPackStats(): bad magic 1 (0x110aa998d, 0)
kewastUnPackStats(): bad magic 1 (0x110aa998d, 0)
kewastUnPackStats(): bad magic 1 (0x110aa999d, 0)
kewastUnPackStats(): bad magic 1 (0x110aa999d, 0)
Errors in file /Oracle_Logs/oracle/diag/rdbms/misdba2/MISDBA2/trace/MISDBA2_m000_786568.trc (incident=146569):
ORA-01578: ORACLE data block corrupted (file # 2, block # 4278)
ORA-01110: data file 2: '+DG_MISDBA21/misdba2/datafile/sysaux.262.718889115'
ORA-26040: Data block was loaded using the NOLOGGING option
Errors in file /Oracle_Logs/oracle/diag/rdbms/misdba2/MISDBA2/trace/MISDBA2_m000_786568.trc (incident=146570):
ORA-01578: ORACLE data block corrupted (file # ORA-01578: ORACLE data block corrupted (file # 2, block # 4278)
ORA-01110: data file 2: '+DG_MISDBA21/misdba2/datafile/sysaux.262.718889115'
ORA-26040: Data block was loaded using the NOLOGGING option
, block # )
Mon Jul 05 08:31:00 2010
Sweep [inc][146570]: completed
Sweep [inc][146569]: completed
Mon Jul 05 09:06:31 2010
Thread 1 cannot allocate new log, sequence 3029
Private strand flush not complete
Current log# 6 seq# 3028 mem# 0: +DG_MISDBA21/misdba2/onlinelog/group_6.544.719237719
Current log# 6 seq# 3028 mem# 1: +DG_MISDBA22/misdba2/onlinelog/group_6.272.719237735
Thread 1 advanced to log sequence 3029 (LGWR switch)
Current log# 7 seq# 3029 mem# 0: +DG_MISDBA21/misdba2/onlinelog/group_7.545.719238209
Current log# 7 seq# 3029 mem# 1: +DG_MISDBA22/misdba2/onlinelog/group_7.273.719238241
Mon Jul 05 09:07:12 2010
Archived Log entry 2718 added for thread 1 sequence 3028 ID 0x552bc791 dest 1:
Mon Jul 05 09:22:05 2010
Thread 1 cannot allocate new log, sequence 3030
Private strand flush not complete
Current log# 7 seq# 3029 mem# 0: +DG_MISDBA21/misdba2/onlinelog/group_7.545.719238209
Current log# 7 seq# 3029 mem# 1: +DG_MISDBA22/misdba2/onlinelog/group_7.273.719238241
Thread 1 advanced to log sequence 3030 (LGWR switch)
Current log# 8 seq# 3030 mem# 0: +DG_MISDBA21/misdba2/onlinelog/group_8.546.719238883
Current log# 8 seq# 3030 mem# 1: +DG_MISDBA22/misdba2/onlinelog/group_8.274.719238901
Mon Jul 05 09:22:46 2010

ORA-1578 is indication of physical block corruption. Oracle computes an internal checksum before fetching the block from disk, when it is about to fetch the block it reads the block header and compare the checksum stored in it. If the checksum mismatches we get ora-1578 error.
It indicates that a block is corrupted at hardware level i.e at OS.
This error will always come whenever the corrupted block is read by Oracle.
Reasons for ora-1578:
1. Bad sectors in the Storage Disk Drive.
2. Formatting of blocks At OS level.( Zeroed out disk blocks).
3. some corruption in underlying hardware which is making block unreadable.
How to collect information for ora-1578:
Error Text:
ORA-01578: ORACLE data block corrupted (file # 14, block # 38976)
The block # 38976 shows the corrupted block number and the file # 14 indicates
the reletive file number 14.
1. Get the absolute file number:
To get the absolute file # we will use the following query:
SQL > select file# from v$datafile where rfile#=14;
FILE#
14
here the absolute file# is also 14.
2. Get the segment name and segment type in which this corrupted block resides:
Use the following query:
SQL > SELECT tablespace_name, segment_type, owner, segment_name FROM
dba_extents WHERE file_id = 14 and 38976 between block_id AND block_id + blocks - 1;
-- It will give us the segment type (Table, Index, LOB etc.), name of the segment (Table name
Index name etc.), Owner of the segment and the tablespace name of the segment in which corrupted block resides.
SQL > select FILE#,TS#,STATUS,BLOCKS,NAME from v$datafile where FILE#=14;
-- From this we will get the tablespace number and the fine name of the datafile in which the corrupted block resides.
SQL> select TS#,NAME from v$tablespace where TS#=;
-- It will give us the Name of the tablespace.
Now we have all the information required to perform an action to overcome ora-1578.
Source: http://askoracledba.blogspot.com/2008/04/ora-1578-is-indication-of-physical.html
I could post only source link, but at this moment, the link is not working (for me at least), so i am posting its contents.
HTH
Girish Sharma

Similar Messages

  • How to set Blocking Indicator for product specific TransportationLanes?

    Hi All,
    I'm facing a problem while trying to set the blocking indicator for product specific Transportation Lanes-external procurement.
    How can i proceed on the same?
    I've figured out 2 methods for blocking the product specific TLanes.
    1. using /SAPAPO/TR_TL_TRANSFER_BAPI.
    2. using BAPI_TRLSRVAPS_SAVEMULTI.
    I tried using the BAPI - /SAPAPO/TR_TL_TRANSFER_BAPI, which comes inside the DELETE BAPI - BAPI_TRLSRVAPS_DELMULTI. Although I had passed the parameters reg. external procurement, nothing seemed to be happening in the system. There was no blocking indicator - D(locked and flagged for deletion) set against the subjected TLane. In fact, to my amazement, the BAPI didn't return even a single msg. BAPIRETURN internal table after execution was empty.
    Here, I'm passing:
    (IV_LOGQS) TYPE  /SAPAPO/LOGQS
    (IV_LOGSYS) TYPE  LOGSYS
    (IV_CALLER) TYPE  /SAPAPO/MD_CALLER
    (IT_TR) TYPE  /SAPAPO/TR_TTD_TR
    (IT_TR_X) TYPE  /SAPAPO/TR_TTX_TR
    (IT_TRPROD_SRC) TYPE  /SAPAPO/TR_TTD_TRPROD_SRC    and
    (IT_TRPROD_SRC_X) TYPE  /SAPAPO/TR_TTX_TRPROD_SRC
    I haven't tried on the second method yet. Is there any other programming alternative for setting the blocking indicator of a TLane / multiple Tlanes?
    Could anyone pls explain and guide me on a suitable method to be chosen and the process to be followed, parameters to be passed, etc.

    Hi Sanjay,
                    Use the standard BAPI:  BAPI_TRLSRVAPS_SAVEMULTI2 (according to SCM version you are using)
    to update the deletion flag for product specific T-lane, in this BAPI you have to pass the data to EXTERNAL_PROCUREMENT parameter table in which LOCKED_FLG field is there in which you can pass the "D" for deletion or block flag.
    Also you have to pass the same entries in EXTERNAL_PROCUREMENT_X parameter table of this BAPI.
    If any further help required, refer the documentation of BAPI or let me know.
    I hope this will help you to solve the issue.
    Regards,
    Saurabh

  • 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

  • Blocking creation of production order if standard cost estimate is not done

    Hi PP gurus,
    Can anyone help me in blocking the creation of production order if the standard cost estimate is not done for the particular posting period.

    Hi,
    I do not think there exist a standart check. You can use exit EXIT_SAPLCOZF_003 to block creation of production order by sending error messages based on any condition.
    Regards.

  • 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

  • Adding a Dialog instance to a live production database.

    We are adding a number of new App servers to a ECC6 7.0 Live production database but we don't have enough confidence in the in the information in InstGui and install guide that it will not over write the /sapmnt/SID/exe of the running CI.
    Has anyone done this and is just down to not selecting the unpack Kernel and oracle client check boxes in the Parameter Summary?
    Cheers
    Chris

    Hi,
    >If parameters are set correctly it shouldn't ask you to unpack exe files.
    >DI should get all exe files from CI and it will do the same copy again whenever it gets restarted.
    Well, yes if only, the DI use the same kernel as the CI...
    For example we run our ECC6 production system with a CI on Windows 2003 64 Itanium and the DI on Windows 2003 x86_64.
    Regards,
    Olivier

  • What is the Best way to extract a subset of data from a Production database

    Hi,
    One of our cleint want to to extract a subset of data from a Production databases in order to build a dev or test database. Since it is a banking sector they do not want to clone the db.
    Can anybdoy suggests any tool or any info
    Regards
    Manoj

    DataBee is one option. Depending on circumstances, you may also want their DataMasker utility in addition...
    Of course, depending on your particular system and your particular requirements, this sort of thing can rather quickly get quite complicated since you may need very particular types of subsets of data...
    Justin

  • Severe performance issues in production database

    Hi Experts,
    we have configured RMAN in our production database recently using some 3 party tool COMMVAULT.
    Problem is just 47 GB database taking around 6 hrs of time to complted the bakcup job. Please let me know what could be the reason.
    Further to this issues i found out some of few things, our application vendor commissioned this database server and it seems that they done some changes in TIMEZONE settings.
    when i query against some of few dictionary tables for example dba_schedular_jobs i am getting the following error.
    ORA-01882: timezone region %s not found
    when ever i connect the database , the connection itself is very slow and suffering severe performance issues in my production database.
    You help would be much appreciated.
    Regards,
    Salai

    Hi,
    also let us know if you use asm or local file system for datafiles.
    Your backup strategy will also be helpful:
    Do you make compressed backups?
    Full or incremental?
    To where do you backup the database? To the local filesystem, SAN Volume, Offsite Storage, Tape storage?
    Is there any other jobs running while the RMAN job is running?
    Please post the stats that you have gathered over the time period when the backup is running.
    Thanks.

Maybe you are looking for

  • How do I delete a MobileMe email account from iPad that has iCloud on it?

    I Have an iPhone 4s that I installed iCloud on during the setup process. My iPhone, iPad and PC sync properly. However, my iPad email settings display both the MobileMe and iCloud accounts (with identical settings to each other).  Sometimes, the iPad

  • Success!  Solution to .DV files unable to be opened in Premiere Pro

    I'm super excited to have finally figured out why my .DV files kept getting "file type not supported" messages when I tried to import them into Premiere Pro.  I had used them previously before I wiped the hard drive on my laptop.  After Effects also

  • LR2 How to select one person in a picture

    New to LR and I'm trying to select just one person in a picture and remove everything else.  What tool do I use or should I use Photoshop thanks Mike

  • A Lesson in Frustrating Customer Service

    I had a hell of a time with a locked account a month back. But it wasn't the locked account that bothered me. It was the continuous lack of solid action....except by one retailer who will undoubtedly not be rewarded for her efforts. https://docs.goog

  • Integrated Business Processes with ERP Systems Textbook

    This forum will move to the New SCN as part of our migration to a new platform. Once we make that move, on December 5, it will become a read-only discussion. It will be searchable but will not be part of the site navigation.  If you have questions, p