Corruption of block

hi all ,
I need to do a block corruption of oracle .dbf files etc on Win and then recover it....
Can any one help me in corrupting the databloc of datafile ??
thanks
sunny

If you don't need to currupt a specific block, open a
Hexeditor and play a litte.
By the way:
http://forums.oracle.com/forums/thread.jspa?messageID=
1098087􌅧
DimMany Thanks !!! Dim

Similar Messages

Corrupting the block to continue recovery in physical standby

Hi,
Just like to inquire how I will be able to corrupt the block to be able to continue the recovery in the physical standby.
DB Version: 11.1.0.7
Database Type: Data Warehouse
The setup we have is primary database and standby database, we are not using dataguard, and our standby setup is another physical copy of production which act as standby and being sync using script that being run from time to time to apply the archive log came from production (its not configured to sync using ARCH or LGWR and its corresponding configurations).
Then, the standby database is not sync due to errors encountered while trying to apply the archive log, error is below:
Fri Feb 11 05:50:59 2011
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log /u01/archive/<sid>/1_50741_651679913.arch
Fri Feb 11 05:52:06 2011
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0, kdr9ir2rst0()+326]
Errors in file /u01/app/oracle/diag/rdbms/<sid>/<sid>/trace/<sid>pr0028085.trc (incident=631460):
ORA-07445: exception encountered: core dump [kdr9ir2rst0()+326] [SIGSEGV] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0] [Address not mapped to object] []
Incident details in: /u01/app/oracle/diag/rdbms/<sid>/<sid>/incident/incdir_631460/<sid>pr0028085_i631460.trc
Fri Feb 11 05:52:10 2011
Trace dumping is performing id=[cdmp_20110211055210]
Fri Feb 11 05:52:14 2011
Sweep Incident[631460]: completed
Fri Feb 11 05:52:17 2011
Slave exiting with ORA-10562 exception
Errors in file /u01/app/oracle/diag/rdbms/<sid>/<sid>/trace/<sid>pr0028085.trc:
ORA-10562: Error occurred while applying redo to data block (file# 36, block# 1576118)
ORA-10564: tablespace <tablespace name>
ORA-01110: data file 36: '/u02/oradata/<sid>/<datafile>.dbf'
ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 14877145
ORA-00607: Internal error occurred while making a change to a data block
ORA-00602: internal programming exception
ORA-07445: exception encountered: core dump [kdr9ir2rst0()+326] [SIGSEGV] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0] [Address not mapped to object] []
Based on the error log it seems we are hitting some bug from metalink (document id 460169.1 and 882851.1)
my question is, the datafile # is given, block# is known too and the data object is also identified. I just verified that object is not that important, is there a way to set the block# to corrupted to be able the recovery to continue? Then I will just drop the table from production so that will also happen in standby, and the block corrupted will be gone too. Is this feasible?
If its not, can you suggest what's next I can do so the the physical standby will be able to sync again to prod aside from rebuilding the standby?
Please take note that I also tried to dbv the file to confirm if there is marked as corrupted and the result for that datafile is also good:
dbv file=/u02/oradata/<sid>/<datafile>_19.dbf logfile=dbv_file_36.log blocksize=16384
oracle@<server>:[~] $ cat dbv_file_36.log
DBVERIFY: Release 11.1.0.7.0 - Production on Sun Feb 13 04:35:28 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
DBVERIFY - Verification starting : FILE = /u02/oradata/<sid>/<datafile>_19.dbf
DBVERIFY - Verification complete
Total Pages Examined : 3840000
Total Pages Processed (Data) : 700644
Total Pages Failing (Data) : 0
Total Pages Processed (Index): 417545
Total Pages Failing (Index): 0
Total Pages Processed (Other): 88910
Total Pages Processed (Seg) : 0
Total Pages Failing (Seg) : 0
Total Pages Empty : 2632901
Total Pages Marked Corrupt : 0
Total Pages Influx : 0
Total Pages Encrypted : 0
Highest block SCN : 3811184883 (1.3811184883)
Any help is really appreciated. I hope to hear feedback from you.
Thanks

damorgan, i understand the opinion.
just new with the organization and just inherit a data warehouse database without rman backup. I am still setting up the rman backup thats why i can't use rman to resolve the issue, the only i have is physical standby and its not a standby that automatically sync using dataguard or standard standby setup, i am just checking solution that is applicable in the current situation

Unable to drop materialized view with corrupted data blocks

Hi,
The alert log of our database is giving this message
Wed Jan 31 05:23:13 2007
ORACLE Instance mesh (pid = 9) - Error 1578 encountered while recovering transaction (6, 15) on object 13355.
Wed Jan 31 05:23:13 2007
Errors in file /u01/app/oracle/admin/mesh/bdump/mesh_smon_4369.trc:
ORA-01578: ORACLE data block corrupted (file # 5, block # 388260)
ORA-01110: data file 5: '/u03/oradata/mesh/mview.dbf'
No one is using this mview still oracle is trying to recover this transaction (6, 15).
when i tried to drop this mview it gives me this error
ERROR at line 1:
ORA-01578: ORACLE data block corrupted (file # 5, block # 388260)
ORA-01110: data file 5: '/u03/oradata/mesh/mview.dbf'
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2255
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2461
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2430
ORA-06512: at line 1
I have tried to fix the corrupted data blocks by using dbms_repair package, but of no use.
I have marked this block to be skipped by using dbms_repair.skip_block but still unable to drop it.
Please suggest what should I do?
Thanks in advance
Anuj

You are lucky if only your undesirable MV is affected by theese corrupted blocks. This is an advice to do a complete-super-full-hot-cold-middle backup of ypur database and search for any disk for a "possible replace".
God save us!

Log corruption near block 1737

hi,
i am getting an error while open the db
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 1737 change 16680088 time 12/22/2008
10:40:13
ORA-00312: online log 2 thread 1: 'G:\ORACLE\ORADATA\HOTEST\REDO02.LOG'while doing an incomplete recovery it is asking for an archived file which i am not having i.e ARC_801_1.ARC.........
SQL> recover database until cancel;
ORA-00279: change 16679127 generated at 12/22/2008 10:37:11 needed for thread 1
ORA-00289: suggestion : G:\ORACLE\ARCH\ARC_801_1.ARC
ORA-00280: change 16679127 for thread 1 is in sequence #801
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'G:\ORACLE\ORADATA\HOTEST\SYSTEM01.DBF'
ORA-01112: media recovery not startedpls suggest me for the same....

I am not having a archived log of sequence no. 801 neither i am having backup, is there any other way to up the db....
SMON: enabling tx recovery
Mon Dec 22 10:37:16 2008
Database Characterset is WE8MSWIN1252
replication_dependency_tracking turned off (no async multimaster replication found)
Completed: alter database open
Corrupt block relative dba: 0x0300cc4b (file 12, block 52299)
Bad check value found during buffer read
Data in bad block -
type: 6 format: 2 rdba: 0x0300cc4b
last change scn: 0x0000.000fa127 seq: 0x1 flg: 0x06
consistency value in tail: 0xa1270601
check value in block header: 0x8f85, computed block checksum: 0xcf00
spare1: 0x0, spare2: 0x0, spare3: 0x0
Reread of rdba: 0x0300cc4b (file 12, block 52299) found valid data
Corrupt block relative dba: 0x0300cdfb (file 12, block 52731)
Bad check value found during buffer read
Data in bad block -
type: 6 format: 2 rdba: 0x0300cdfb
last change scn: 0x0000.000fa128 seq: 0x1 flg: 0x04
consistency value in tail: 0xa1280601
check value in block header: 0x446b, computed block checksum: 0x3200
spare1: 0x0, spare2: 0x0, spare3: 0x0
Reread of rdba: 0x0300cdfb (file 12, block 52731) found valid data
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     Dump file g:\oracle\admin\hotest\bdump\alert_hotest.log
Mon Dec 22 10:41:29 2008
ORACLE V9.2.0.4.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.1 Service Pack 2, CPU type 586
Mon Dec 22 10:41:29 2008
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
Using log_archive_dest parameter default value
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.4.0.
System parameters with non-default values:
processes                = 150
timed_statistics         = TRUE
shared_pool_size         = 50331648
large_pool_size          = 8388608
java_pool_size           = 33554432
control_files            = G:\oracle\oradata\hotest\CONTROL01.CTL, G:\oracle\oradata\hotest\CONTROL02.CTL, G:\oracle\oradata\hotest\CONTROL03.CTL
db_block_size            = 8192
db_cache_size            = 25165824
compatible               = 9.2.0.0.0
log_archive_start        = TRUE
log_archive_dest_1       = location=G:\oracle\arch
log_archive_dest_2       = SERVICE=stand LGWR ASYNC
log_archive_dest_state_1 = ENABLE
log_archive_dest_state_2 = ENABLE
fal_server               = STAND
fal_client               = HOTEST
log_archive_format       = arc_%s_%t.arc
db_file_multiblock_read_count= 16
fast_start_mttr_target   = 300
undo_management          = AUTO
undo_tablespace          = UNDOTBS1
undo_retention           = 10800
remote_login_passwordfile= EXCLUSIVE
db_domain                =
instance_name            = hotest
dispatchers              = (PROTOCOL=TCP) (SERVICE=hotestXDB)
job_queue_processes      = 10
hash_join_enabled        = TRUE
background_dump_dest     = G:\oracle\admin\hotest\bdump
user_dump_dest           = G:\oracle\admin\hotest\udump
core_dump_dest           = G:\oracle\admin\hotest\cdump
sort_area_size           = 524288
db_name                  = hotest
open_cursors             = 300
star_transformation_enabled= FALSE
query_rewrite_enabled    = FALSE
pga_aggregate_target     = 25165824
aq_tm_processes          = 1
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
CJQ0 started with pid=8
QMN0 started with pid=9
Mon Dec 22 10:41:36 2008
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=12
ARC0: Archival started
ARC1 started with pid=13
Mon Dec 22 10:41:37 2008
ARCH: STARTING ARCH PROCESSES COMPLETE
Mon Dec 22 10:41:37 2008
ARC0: Thread not mounted
Mon Dec 22 10:41:38 2008
ARC1: Archival started
Mon Dec 22 10:41:38 2008
ARC1: Thread not mounted
Mon Dec 22 10:41:38 2008
alter database mount exclusive
Mon Dec 22 10:41:43 2008
Successful mount of redo thread 1, with mount id 1003521250.
Mon Dec 22 10:41:43 2008
Database mounted in Exclusive Mode.
Completed: alter database mount exclusive
Mon Dec 22 10:41:43 2008
alter database open
Mon Dec 22 10:41:44 2008
Beginning crash recovery of 1 threads
Mon Dec 22 10:41:44 2008
Started first pass scan
ORA-368 signalled during: alter database open...
Mon Dec 22 10:42:35 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Dump file g:\oracle\admin\hotest\bdump\alert_hotest.log
Mon Dec 29 10:14:22 2008
ORACLE V9.2.0.4.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.1 Service Pack 2, CPU type 586
Mon Dec 29 10:14:22 2008
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
Using log_archive_dest parameter default value
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.4.0.
System parameters with non-default values:
processes                = 150
timed_statistics         = TRUE
shared_pool_size         = 50331648
large_pool_size          = 8388608
java_pool_size           = 33554432
control_files            = G:\oracle\oradata\hotest\CONTROL01.CTL, G:\oracle\oradata\hotest\CONTROL02.CTL, G:\oracle\oradata\hotest\CONTROL03.CTL
db_block_size            = 8192
db_cache_size            = 25165824
compatible               = 9.2.0.0.0
log_archive_start        = TRUE
log_archive_dest_1       = location=G:\oracle\arch
log_archive_dest_2       = SERVICE=stand LGWR ASYNC
log_archive_dest_state_1 = ENABLE
log_archive_dest_state_2 = ENABLE
fal_server               = STAND
fal_client               = HOTEST
log_archive_format       = arc_%s_%t.arc
db_file_multiblock_read_count= 16
fast_start_mttr_target   = 300
undo_management          = AUTO
undo_tablespace          = UNDOTBS1
undo_retention           = 10800
remote_login_passwordfile= EXCLUSIVE
db_domain                =
instance_name            = hotest
dispatchers              = (PROTOCOL=TCP) (SERVICE=hotestXDB)
job_queue_processes      = 10
hash_join_enabled        = TRUE
background_dump_dest     = G:\oracle\admin\hotest\bdump
user_dump_dest           = G:\oracle\admin\hotest\udump
core_dump_dest           = G:\oracle\admin\hotest\cdump
sort_area_size           = 524288
db_name                  = hotest
open_cursors             = 300
star_transformation_enabled= FALSE
query_rewrite_enabled    = FALSE
pga_aggregate_target     = 25165824
aq_tm_processes          = 1
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
CJQ0 started with pid=8
QMN0 started with pid=9
Mon Dec 29 10:14:28 2008
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=12
ARC0: Archival started
ARC1 started with pid=13
ARC1: Archival started
Mon Dec 29 10:14:30 2008
ARCH: STARTING ARCH PROCESSES COMPLETE
Mon Dec 29 10:14:30 2008
ARC1: Thread not mounted
Mon Dec 29 10:14:31 2008
ARC0: Thread not mounted
Mon Dec 29 10:14:32 2008
alter database mount exclusive
Mon Dec 29 10:14:37 2008
Successful mount of redo thread 1, with mount id 1004122632.
Mon Dec 29 10:14:37 2008
Database mounted in Exclusive Mode.
Completed: alter database mount exclusive
Mon Dec 29 10:14:37 2008
alter database open
Mon Dec 29 10:14:37 2008
Beginning crash recovery of 1 threads
Mon Dec 29 10:14:38 2008
Started first pass scan
ORA-368 signalled during: alter database open...
Mon Dec 29 10:15:29 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 10:20:44 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 10:25:54 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 10:31:09 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 10:36:24 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 10:41:40 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 10:46:55 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 10:52:10 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 10:57:26 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:02:41 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:07:56 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:13:05 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:18:15 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:23:30 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:28:39 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:33:49 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:39:04 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:44:19 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:49:35 2008
Restarting dead background process QMN0
QMN0 started with pid=9
Mon Dec 29 11:54:44 2008
Restarting dead background process QMN0
QMN0 started with pid=15
Mon Dec 29 11:59:59 2008
Restarting dead background process QMN0
QMN0 started with pid=14
Mon Dec 29 12:03:06 2008
alter database open
Mon Dec 29 12:03:06 2008
Beginning crash recovery of 1 threads
Mon Dec 29 12:03:07 2008
Started first pass scan
ORA-368 signalled during: alter database open...
Mon Dec 29 12:05:09 2008
Restarting dead background process QMN0
QMN0 started with pid=15
Mon Dec 29 12:05:14 2008
ALTER DATABASE RECOVER database until cancel
Mon Dec 29 12:05:14 2008
Media Recovery Start
Starting datafile 1 recovery in thread 1 sequence 801
Datafile 1: 'G:\ORACLE\ORADATA\HOTEST\SYSTEM01.DBF'
Starting datafile 2 recovery in thread 1 sequence 801
Datafile 2: 'G:\ORACLE\ORADATA\HOTEST\UNDOTBS01.DBF'
Starting datafile 3 recovery in thread 1 sequence 801
Datafile 3: 'G:\ORACLE\ORADATA\HOTEST\CWMLITE01.DBF'
Starting datafile 4 recovery in thread 1 sequence 801
Datafile 4: 'G:\ORACLE\ORADATA\HOTEST\DRSYS01.DBF'
Starting datafile 5 recovery in thread 1 sequence 801
Datafile 5: 'G:\ORACLE\ORADATA\HOTEST\EXAMPLE01.DBF'
Starting datafile 6 recovery in thread 1 sequence 801
Datafile 6: 'G:\ORACLE\ORADATA\HOTEST\INDX01.DBF'
Starting datafile 7 recovery in thread 1 sequence 801
Datafile 7: 'G:\ORACLE\ORADATA\HOTEST\ODM01.DBF'
Starting datafile 8 recovery in thread 1 sequence 801
Datafile 8: 'G:\ORACLE\ORADATA\HOTEST\TOOLS01.DBF'
Starting datafile 9 recovery in thread 1 sequence 801
Datafile 9: 'G:\ORACLE\ORADATA\HOTEST\USERS01.DBF'
Starting datafile 10 recovery in thread 1 sequence 801
Datafile 10: 'G:\ORACLE\ORADATA\HOTEST\XDB01.DBF'
Starting datafile 11 recovery in thread 1 sequence 801
Datafile 11: 'G:\ORACLE\ORADATA\HOTEST\CADATA3.ORA'
Starting datafile 12 recovery in thread 1 sequence 801
Datafile 12: 'G:\ORACLE\ORADATA\HOTEST\CADATA.ORA'
Starting datafile 13 recovery in thread 1 sequence 801
Datafile 13: 'G:\ORACLE\ORADATA\HOTEST\CADATAWRO.ORA'
Starting datafile 14 recovery in thread 1 sequence 801
Datafile 14: 'G:\ORACLE\ORADATA\HOTEST\CADATANRO.ORA'
Starting datafile 15 recovery in thread 1 sequence 801
Datafile 15: 'G:\ORACLE\ORADATA\HOTEST\CADATACRO.ORA'
Starting datafile 16 recovery in thread 1 sequence 801
Datafile 16: 'G:\ORACLE\ORADATA\HOTEST\CADATAOTH.ORA'
Starting datafile 17 recovery in thread 1 sequence 801
Datafile 17: 'G:\ORACLE\ORADATA\HOTEST\CADATAERO.ORA'
Starting datafile 18 recovery in thread 1 sequence 801
Datafile 18: 'G:\ORACLE\ORADATA\HOTEST\CADATAHO.ORA'
Starting datafile 19 recovery in thread 1 sequence 801
Datafile 19: 'G:\ORACLE\ORADATA\HOTEST\CADATASRO.ORA'
Starting datafile 20 recovery in thread 1 sequence 801
Datafile 20: 'G:\ORACLE\ORADATA\HOTEST\PAYROLL.ORA'
Starting datafile 21 recovery in thread 1 sequence 801
Datafile 21: 'G:\ORACLE\ORADATA\HOTEST\ORION.ORA'
Starting datafile 22 recovery in thread 1 sequence 801
Datafile 22: 'G:\ORACLE\ORADATA\HOTEST\ATHENA.ORA'
Starting datafile 23 recovery in thread 1 sequence 801
Datafile 23: 'G:\ORACLE\ORADATA\HOTEST\CAL_YEAR_2004.ORA'
Starting datafile 24 recovery in thread 1 sequence 801
Datafile 24: 'G:\ORACLE\ORADATA\HOTEST\CAL_YEAR_2005.ORA'
Starting datafile 25 recovery in thread 1 sequence 801
Datafile 25: 'G:\ORACLE\ORADATA\HOTEST\CAL_YEAR_2006.ORA'
Starting datafile 26 recovery in thread 1 sequence 801
Datafile 26: 'G:\ORACLE\ORADATA\HOTEST\CAL_YEAR_2007.ORA'
Starting datafile 27 recovery in thread 1 sequence 801
Datafile 27: 'G:\ORACLE\ORADATA\HOTEST\CAL_YEAR_2008.ORA'
Starting datafile 28 recovery in thread 1 sequence 801
Datafile 28: 'G:\ORACLE\ORADATA\HOTEST\CAL_YEAR_2009.ORA'
Starting datafile 29 recovery in thread 1 sequence 801
Datafile 29: 'G:\ORACLE\ORADATA\HOTEST\EXAMPLE02.DBF'
Starting datafile 30 recovery in thread 1 sequence 801
Datafile 30: 'G:\ORACLE\ORADATA\HOTEST\EXAMPLE02.RAW'
Media Recovery Log
ORA-279 signalled during: ALTER DATABASE RECOVER database until cancel ...
Mon Dec 29 12:06:24 2008
ALTER DATABASE RECOVER    CANCEL
Mon Dec 29 12:06:24 2008
ORA-1547 signalled during: ALTER DATABASE RECOVER    CANCEL ...
Mon Dec 29 12:06:24 2008
ALTER DATABASE RECOVER CANCEL
ORA-1112 signalled during: ALTER DATABASE RECOVER CANCEL ...
Mon Dec 29 12:06:40 2008
alter database open resetlogs
Mon Dec 29 12:06:41 2008
ORA-1194 signalled during: alter database open resetlogs...
Mon Dec 29 12:06:47 2008
alter database open noresetlogs
Mon Dec 29 12:06:48 2008
Beginning crash recovery of 1 threads
Mon Dec 29 12:06:48 2008
Started first pass scan
ORA-368 signalled during: alter database open noresetlogs...
Mon Dec 29 12:10:24 2008
Restarting dead background process QMN0
QMN0 started with pid=15
Mon Dec 29 12:15:39 2008
Restarting dead background process QMN0
QMN0 started with pid=15
Mon Dec 29 12:20:55 2008
Restarting dead background process QMN0
QMN0 started with pid=15
Mon Dec 29 12:26:10 2008

Block corruption에서 physial block corruption과 soft block corruption 의 차이점

어느 분께서 저에게 block corruption에 대한 질문을 하셨는데
그래서 솔루션을 제시해주었고 block dump를 보니 아래와 같았습니다.
(1번덤프) 제가 잘못 진단한 block dump(soft corrupt로 판단했는데 raid5의
디스크가 나간 physical corrupt이네요)
*** 2007-03-06 09:54:33.103
Start dump data blocks tsn: 6 file#: 6 minblk 102032 maxblk 102032
buffer tsn: 6 rdba: 0x01818e90 (6/102032)
scn: 0x056c.f689329c seq: 0x01 flg: 0x06 tail: 0xa0cf0000
frmt: 0x02 chkval: 0x7675 type: 0x06=trans data
Hex dump of corrupt header 2 = BROKEN
이었습니다.
그런데 저는 이미 이전에 physical block corruption을 경험 한 후
아래와 같이 dump를 떠서 확인한 결과 여러문서를 찾아본 후
이와같이 판단하였습니다.
(2번 덤프) physical corrupt로 확인된 덤프
- 아래의 scn: 0x0000.00000000 seq: 0xff flg: 0x00 tail: 0x000006ff
에서 SCN이 0x0000 이고 seq값이 UB1MAXVAL-1 이 아니므로
physical block corruption 임을 확인
*** SESSION ID:(25.59041) 2005-12-12 11:41:13.132
Start dump data blocks tsn: 7 file#: 8 minblk 169994 maxblk 169994
buffer tsn: 7 rdba: 0x0202980a (8/169994)
scn: 0x0000.00000000 seq: 0xff flg: 0x00 tail: 0x000006ff
frmt: 0x02 chkval: 0x0000 type: 0x06=trans data
Block header dump: 0x0202980a
Object id on Block? Y
seg/obj: 0xef9 csc: 0x00.8c13d2b itc: 2 flg: O typ: 2 - INDEX
fsl: 2 fnx: 0x2024b0f ver: 0x01
Itl Xid Uba Flag Lck Scn/Fsc
0x01 xid: 0x0001.052.0001888b uba: 0x00c07725.2482.02 C--- 0 scn 0x0000.083a0f80
0x02 xid: 0x0007.038.0001a196 uba: 0x00c07574.1f28.0b ---- 232 fsc 0x0f57.00000000
질문..
physial block corruption과 soft block corruption 인지의 여부를 block dump를
통해서 알고 싶은데요. 기존에 제가 잘못 알고 있는 것 같습니다.

좀 이상한 부분이 있어서 직접 login 하여서 조사해보았습니다.
alert 에러 코드는
Errors in file /app/oracle/product/10.2.0/admin/TEST_T_ktrp4vpe/bdump/test_t_smon_12714.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-01578: ORACLE data block corrupted (file # 2, block # 2714)
ORA-01110: data file 2: '/test_tdata/SYSTEM04.dbf'
상기로 메타 링크를 찾아보면...
제목: FAQ: Physical Corruption
문서 ID: 공지:403747.1 유형: FAQ
(a) ORA-01578 - This error explains physical structural damage with a particular block.
(b) ORA-08103 - This error is a logical corruption error for a particular data block.
(c) ORA-00600 [2662] - This error is related to block corruption , and occurs due to a higher SCN than of database SCN.
-- 좀 이상한게 physical corruption 이란 문서내에
physical corrupt 와 logical corrupt 를 분류하는게 좀 이상한데 ㅡ_ㅡ;
a 항목이라, physical structual damage ... 자연스럽게 physcial corrupt 로 보입니다. dump 내용으로 제가 판독이 안되고, alert 의 error code 로는
physical corrupt 로 보이는데..
alert 의 error code 와 dump 의 내용이 상이 할수 있는건가요 ?
글 수정:
darkturtle

RMAN-05501: RMAN-11003 ORA-00353: log corruption near block 2048 change

Hi Gurus,
I've posted few days ago an issue I got while recreating my Dataguard.
The Main issue was while duplicating target from active database I got this errors during the recovery process.
The Restore Process Went fine, RMAN Copied the Datafiles very well, but stop when at the moment to start the recovery process from the auxiliary db
Yesterday I took one last try,
I follow same procedure, the one described in all Oracle Docs, Google and so on ... it's not a secret I guess.
The I got the same issue, same errors.
I read soemthing about archivelogs, and the Block corruption and so on, I've tried so many things (register the log... etc etc ), and than I read something about "catalog the logfile)
and that's waht I did.
But I was just connect to the target db.
contents of Memory Script:
set until scn 1638816629;
recover
standby
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 14-MAY-13
starting media recovery
archived log for thread 1 with sequence 32196 is already on disk as file /archives/CMOVP/stby/1_32196_810397891.arc
archived log for thread 1 with sequence 32197 is already on disk as file /archives/CMOVP/stby/1_32197_810397891.arc
archived log for thread 1 with sequence 32198 is already on disk as file /archives/CMOVP/stby/1_32198_810397891.arc
archived log for thread 1 with sequence 32199 is already on disk as file /archives/CMOVP/stby/1_32199_810397891.arc
archived log for thread 1 with sequence 32200 is already on disk as file /archives/CMOVP/stby/1_32200_810397891.arc
archived log for thread 1 with sequence 32201 is already on disk as file /archives/CMOVP/stby/1_32201_810397891.arc
archived log for thread 1 with sequence 32202 is already on disk as file /archives/CMOVP/stby/1_32202_810397891.arc
archived log for thread 1 with sequence 32203 is already on disk as file /archives/CMOVP/stby/1_32203_810397891.arc
archived log for thread 1 with sequence 32204 is already on disk as file /archives/CMOVP/stby/1_32204_810397891.arc
archived log for thread 1 with sequence 32205 is already on disk as file /archives/CMOVP/stby/1_32205_810397891.arc
archived log for thread 1 with sequence 32206 is already on disk as file /archives/CMOVP/stby/1_32206_810397891.arc
archived log for thread 1 with sequence 32207 is already on disk as file /archives/CMOVP/stby/1_32207_810397891.arc
archived log for thread 1 with sequence 32208 is already on disk as file /archives/CMOVP/stby/1_32208_810397891.arc
archived log for thread 1 with sequence 32209 is already on disk as file /archives/CMOVP/stby/1_32209_810397891.arc
archived log for thread 1 with sequence 32210 is already on disk as file /archives/CMOVP/stby/1_32210_810397891.arc
archived log for thread 1 with sequence 32211 is already on disk as file /archives/CMOVP/stby/1_32211_810397891.arc
archived log for thread 1 with sequence 32212 is already on disk as file /archives/CMOVP/stby/1_32212_810397891.arc
archived log for thread 1 with sequence 32213 is already on disk as file /archives/CMOVP/stby/1_32213_810397891.arc
archived log for thread 1 with sequence 32214 is already on disk as file /archives/CMOVP/stby/1_32214_810397891.arc
archived log for thread 1 with sequence 32215 is already on disk as file /archives/CMOVP/stby/1_32215_810397891.arc
archived log for thread 1 with sequence 32216 is already on disk as file /archives/CMOVP/stby/1_32216_810397891.arc
archived log for thread 1 with sequence 32217 is already on disk as file /archives/CMOVP/stby/1_32217_810397891.arc
archived log for thread 1 with sequence 32218 is already on disk as file /archives/CMOVP/stby/1_32218_810397891.arc
archived log for thread 1 with sequence 32219 is already on disk as file /archives/CMOVP/stby/1_32219_810397891.arc
archived log for thread 1 with sequence 32220 is already on disk as file /archives/CMOVP/stby/1_32220_810397891.arc
archived log for thread 1 with sequence 32221 is already on disk as file /archives/CMOVP/stby/1_32221_810397891.arc
archived log for thread 1 with sequence 32222 is already on disk as file /archives/CMOVP/stby/1_32222_810397891.arc
archived log for thread 1 with sequence 32223 is already on disk as file /archives/CMOVP/stby/1_32223_810397891.arc
archived log file name=/archives/CMOVP/stby/1_32196_810397891.arc thread=1 sequence=32196
released channel: prm1
released channel: stby1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/14/2013 01:11:33
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/archives/CMOVP/stby/1_32196_810397891.arc'
ORA-00283: recovery session canceled due to errors
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 2048 change 1638686297 time 05/13/2013 22:42:03
ORA-00334: archived log: '/archives/CMOVP/stby/1_32196_810397891.arc'
################# What I did: ################################
Rma target /
RMAN>catalog archivelog '/archives/CMOVP/stby/1_32196_810397891.arc';
The I connect to target and Auxiliary again :Rman target / catalog rman/rman@rman auxiliary
and I run the last content of the failing memory script:RMAN> run
set until scn 1638816629;
recover
standby
clone database
delete archivelog
And The DB start the recovery Process and my Standby complete the recovery very weel with message "Recovery Finnish or Termintaed or Completed"
The I could configure Datagurd
And I check the process and the Log Apply was on and running fine, no gaps, perfect!!!!!
How !!! Just Cataloging an "Supposed Corrupted"archive log !!!!!!
If Any ideas, that ould be great to understand this.
Rgds
Carlos

okKarol wrote:
Hi Gurus,
I've posted few days ago an issue I got while recreating my Dataguard.
The Main issue was while duplicating target from active database I got this errors during the recovery process.
The Restore Process Went fine, RMAN Copied the Datafiles very well, but stop when at the moment to start the recovery process from the auxiliary db
Yesterday I took one last try,
I follow same procedure, the one described in all Oracle Docs, Google and so on ... it's not a secret I guess.
The I got the same issue, same errors.
I read soemthing about archivelogs, and the Block corruption and so on, I've tried so many things (register the log... etc etc ), and than I read something about "catalog the logfile)
and that's waht I did.
But I was just connect to the target db.
contents of Memory Script:
set until scn 1638816629;
recover
standby
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 14-MAY-13
starting media recovery
archived log for thread 1 with sequence 32196 is already on disk as file /archives/CMOVP/stby/1_32196_810397891.arc
archived log for thread 1 with sequence 32197 is already on disk as file /archives/CMOVP/stby/1_32197_810397891.arc
archived log for thread 1 with sequence 32198 is already on disk as file /archives/CMOVP/stby/1_32198_810397891.arc
archived log for thread 1 with sequence 32199 is already on disk as file /archives/CMOVP/stby/1_32199_810397891.arc
archived log for thread 1 with sequence 32200 is already on disk as file /archives/CMOVP/stby/1_32200_810397891.arc
archived log for thread 1 with sequence 32201 is already on disk as file /archives/CMOVP/stby/1_32201_810397891.arc
archived log for thread 1 with sequence 32202 is already on disk as file /archives/CMOVP/stby/1_32202_810397891.arc
archived log for thread 1 with sequence 32203 is already on disk as file /archives/CMOVP/stby/1_32203_810397891.arc
archived log for thread 1 with sequence 32204 is already on disk as file /archives/CMOVP/stby/1_32204_810397891.arc
archived log for thread 1 with sequence 32205 is already on disk as file /archives/CMOVP/stby/1_32205_810397891.arc
archived log for thread 1 with sequence 32206 is already on disk as file /archives/CMOVP/stby/1_32206_810397891.arc
archived log for thread 1 with sequence 32207 is already on disk as file /archives/CMOVP/stby/1_32207_810397891.arc
archived log for thread 1 with sequence 32208 is already on disk as file /archives/CMOVP/stby/1_32208_810397891.arc
archived log for thread 1 with sequence 32209 is already on disk as file /archives/CMOVP/stby/1_32209_810397891.arc
archived log for thread 1 with sequence 32210 is already on disk as file /archives/CMOVP/stby/1_32210_810397891.arc
archived log for thread 1 with sequence 32211 is already on disk as file /archives/CMOVP/stby/1_32211_810397891.arc
archived log for thread 1 with sequence 32212 is already on disk as file /archives/CMOVP/stby/1_32212_810397891.arc
archived log for thread 1 with sequence 32213 is already on disk as file /archives/CMOVP/stby/1_32213_810397891.arc
archived log for thread 1 with sequence 32214 is already on disk as file /archives/CMOVP/stby/1_32214_810397891.arc
archived log for thread 1 with sequence 32215 is already on disk as file /archives/CMOVP/stby/1_32215_810397891.arc
archived log for thread 1 with sequence 32216 is already on disk as file /archives/CMOVP/stby/1_32216_810397891.arc
archived log for thread 1 with sequence 32217 is already on disk as file /archives/CMOVP/stby/1_32217_810397891.arc
archived log for thread 1 with sequence 32218 is already on disk as file /archives/CMOVP/stby/1_32218_810397891.arc
archived log for thread 1 with sequence 32219 is already on disk as file /archives/CMOVP/stby/1_32219_810397891.arc
archived log for thread 1 with sequence 32220 is already on disk as file /archives/CMOVP/stby/1_32220_810397891.arc
archived log for thread 1 with sequence 32221 is already on disk as file /archives/CMOVP/stby/1_32221_810397891.arc
archived log for thread 1 with sequence 32222 is already on disk as file /archives/CMOVP/stby/1_32222_810397891.arc
archived log for thread 1 with sequence 32223 is already on disk as file /archives/CMOVP/stby/1_32223_810397891.arc
archived log file name=/archives/CMOVP/stby/1_32196_810397891.arc thread=1 sequence=32196
released channel: prm1
released channel: stby1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/14/2013 01:11:33
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/archives/CMOVP/stby/1_32196_810397891.arc'
ORA-00283: recovery session canceled due to errors
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 2048 change 1638686297 time 05/13/2013 22:42:03
ORA-00334: archived log: '/archives/CMOVP/stby/1_32196_810397891.arc'
################# What I did: ################################
Rma target /
RMAN>catalog archivelog '/archives/CMOVP/stby/1_32196_810397891.arc';
The I connect to target and Auxiliary again :Rman target / catalog rman/rman@rman auxiliary
and I run the last content of the failing memory script:RMAN> run
set until scn 1638816629;
recover
standby
clone database
delete archivelog
And The DB start the recovery Process and my Standby complete the recovery very weel with message "Recovery Finnish or Termintaed or Completed"
The I could configure Datagurd
And I check the process and the Log Apply was on and running fine, no gaps, perfect!!!!!
How !!! Just Cataloging an "Supposed Corrupted"archive log !!!!!!
If Any ideas, that ould be great to understand this.
Rgds
CarlosHi,
Can you change standby database archive destination from /archives/CMOVP/stby/ other disk?
I think this problem on your disk.
Mahir
p.s. I remember you before thread, too

Corrupt logical block

I want to check logical block corruption and repair it with dbms_repair package.
For that first i need to corrupt block logically.
How to corrupt oracle database table block logically? Is there any procedure to do that?
Thanks,

Hello,
Thanks for you resposes.
I tried to corrupt datablock by editing datafile and remove some data and add some data.
1. Execurted below rman commad
RMAN> backup validate check logical database;
Output show block is corrupted.
Below query is also listing corrupted blocks.
SQL> select * from v$database_block_corruption;
But when i am checking corruption with dbms_repair packges it doesn't list any corruption.
SET SERVEROUTPUT ON
DECLARE num_corrupt INT;
BEGIN
num_corrupt := 0;
DBMS_REPAIR.CHECK_OBJECT (
SCHEMA_NAME => 'TEST',
OBJECT_NAME => 'TEST1',
REPAIR_TABLE_NAME => 'REPAIR_TABLE',
CORRUPT_COUNT => num_corrupt);
DBMS_OUTPUT.PUT_LINE('number corrupt: ' || TO_CHAR (num_corrupt));
END;
Please let me know any other scenarios to corrupt LOGICAL block.
Thanks,

Unable to Drop table from a corrupted Data Block

while exporting tables i got message data block corrupted 7481. and while i was trying to drop the table, found SQL Recursive Error.
Pls Help me. i am on the way to recreate my database..
Thanks
Rinson

Is 7481 the block number?. Block corruption can be diagnosed using the CLI (Command Line Interface) dbv (database verify). You can also diagnose it by looking for the corresponding error message in the alert.log.
Trying to recover data from a corrupt block is only possible using rman. Otherwise, the only thing you can do is to mark the block as corrupt using DBMS_REPAIR, rebuild the table and try to rescue data by recapturing it.

Logical corruption of block

Dear Experts
Can you pls help in understanding of logical block corruption in detail.
Thanks
Asif Husain Khan

I wrote a small piece of note about it over my blog, you may want to read that,
http://blog.aristadba.com/?p=109
HTH
Aman....

Corrupted Data Block

While doing a routine maintenance, I realized that my production database has two bad data block.
select count(*) from v$database_block_corruption;
COUNT(*)
2I tried using blockrecover command in RMAN and quickly realized that we have already deleted the backup set that could have help us restored the corrupted blocks.
Is there a way I could fix the corrupted block without the backup?
Thank you,

Pl see MOS Doc 28814.1 (Handling Oracle Block Corruptions in Oracle7/8/8i/9i/10g/11g)schavali
Thank you, I will look at this document sometime today.

SYSTEM TS Corruption - Zero Blocks

One of our production instances use operating system level COPY as backup method. When we tried to implement rman backups, we came to know there are some zero blocks in system tablespace. after doing a DBV on the datafile noted by rman, we found there are 12 corrupt/zero pages in system03.dbf.
We cannot go to a backup and roll forward, because we dont know since when this system03 is corrupt. The only option that comes to mind is a full export and rebuild of the database. This is an oracle applications db and pretty critical. The size is around 300GB. We cant afford that much downtime on production.
Any ideas ? so far we didnt have any reported issues due to this corruption. The corrupted object in SYS.IDL_UB1$.
++DBV LOG :-++
DBVERIFY: Release 10.2.0.3.0 - Production on Thu Dec 11 11:00:26 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
DBVERIFY - Verification starting : FILE = system03.dbf
Page 191938 is influx - most likely media corrupt
Corrupt block relative dba: 0x00c2edc2 (file 3, block 191938)
Fractured block found during dbv:
Data in bad block:
type: 0 format: 2 rdba: 0x00c2edc2
last change scn: 0x0000.00000000 seq: 0x1 flg: 0x05
spare1: 0x0 spare2: 0x0 spare3: 0x0
consistency value in tail: 0x00000000
check value in block header: 0xea00
computed block checksum: 0x1
Page 191939 is marked corrupt
Corrupt block relative dba: 0x00c2edc3 (file 3, block 191939)
Completely zero block found during dbv:
Page 191940 is marked corrupt
Corrupt block relative dba: 0x00c2edc4 (file 3, block 191940)
Completely zero block found during dbv:
Page 191941 is marked corrupt
Corrupt block relative dba: 0x00c2edc5 (file 3, block 191941)
Completely zero block found during dbv:
Page 191942 is marked corrupt
Corrupt block relative dba: 0x00c2edc6 (file 3, block 191942)
Completely zero block found during dbv:
Page 191943 is marked corrupt
Corrupt block relative dba: 0x00c2edc7 (file 3, block 191943)
Completely zero block found during dbv:
Page 191944 is marked corrupt
Corrupt block relative dba: 0x00c2edc8 (file 3, block 191944)
Completely zero block found during dbv:
Page 191945 is marked corrupt
Corrupt block relative dba: 0x00c2edc9 (file 3, block 191945)
Completely zero block found during dbv:
Page 191946 is marked corrupt
Corrupt block relative dba: 0x00c2edca (file 3, block 191946)
Completely zero block found during dbv:
Page 191947 is marked corrupt
Corrupt block relative dba: 0x00c2edcb (file 3, block 191947)
Completely zero block found during dbv:
Page 191948 is marked corrupt
Corrupt block relative dba: 0x00c2edcc (file 3, block 191948)
Completely zero block found during dbv:
Page 191949 is influx - most likely media corrupt
Corrupt block relative dba: 0x00c2edcd (file 3, block 191949)
Fractured block found during dbv:
Data in bad block:
type: 0 format: 0 rdba: 0x00000000
last change scn: 0x0000.00000000 seq: 0x0 flg: 0x00
spare1: 0x0 spare2: 0x0 spare3: 0x0
consistency value in tail: 0x00000001
check value in block header: 0x0
block checksum disabled
DBVERIFY - Verification complete
Total Pages Examined : 256000
Total Pages Processed (Data) : 128521
Total Pages Failing (Data) : 0
Total Pages Processed (Index): 52973
Total Pages Failing (Index): 0
Total Pages Processed (Other): 493
Total Pages Processed (Seg) : 0
Total Pages Failing (Seg) : 0
Total Pages Empty : 74001
Total Pages Marked Corrupt : 12
Total Pages Influx : 2
Highest block SCN : 1191398275 (1.1191398275)
Edited by: Lakshmi Pavuluri on Dec 11, 2008 11:30 AM

I think Oracle support is playing it safe. With damaged system tablespace without backup, that's logical conclusion.
Did you try run hcheck.sql to get a report?
"hcheck.sql" script to check for known problems in Oracle8i,Oracle9i, Oracle10g and Oracle 11g
Doc ID: Note:136697.1
Do some DML on table SYS.IDL_UB1$ see you get any error.
This metalink doc has some info on fixing damaged database dictionary.
ORA-8103 Diagnostics and Solution
Doc ID: Note:268302.1
The error just mean the block has been zeroed out a common type of corruption.

How to logically corrupt a block

sir
i know different ways to check whether the block is corrupted.
But i can test it only if any block is corrupted .
how will u make a block corrupt . i will bw very much grateful if u can give an
example for the block corruption .

Hi Sheila M
I need to find a way to extract lists of emails from Junk mail folder and add them en masse to blocked senders, without having to add them to my blocked senders one by one.
I have had the same email address for too long to change it, but I receive huge amounts of junk mail. I have so far barred nearly 2000 senders and have 1100 sitting in my junk folder form the last week. I barred them one by one, using RULES function...I simply cannot keep doing this.
I have MacBook Pro running Mavericks, plus iPad plus iPhone 5.
The problem is aggravated by the fact that Apple has a weakness in Mail: I may bar thousands of senders on my Mac, but the filter does not sync the barred addresses to my iPad or iPhone, so if I use Mail on either, I get many thousands of emails at once and have to mark them one by one to delete. It's ridiculous.
To solve this problem, I have decided to do is block all the senders in webmail.
However I still have the same problem with extracting multiple addresses from my junk mail folder in order to copy them into blocked senders list.
Genius Bar said it can't be done. I think they're wrong. There simply as to be (a) a location on my Mac where I can find a list of all those I have already barred; (b) a way to extract email addresses from groups of received mail.
I'd be grateful for some advice, please.

Pre: corrupt contact blocks send/receive of SMS?

Hi all. Here's my issue - I had just had my wife add her Yahoo messenger info to the Messaging accounts on her Pre. She already had a contact for me for receiving text messages, so I tried to link the (newly appeared) Yahoo account to my full contact. Two unfortunate things happened:
1: I realized I was making the contact link the wrong way around (from Yahoo messenger profile to the full contact), so I removed the link (I thought) and re-made it from the full contact, opening the links screen there, then adding a link from the full contact to the Y! messenger profile.
2: I was doing this in a low-signal area.
What appears to have happened due to the combination of the two is that I can no longer send or receive a text message to the mobile number in my main, full contact! I am not sure what to do about this - I tried deleting the full contact and remaking it, along with quite a few soft resents, but still no texts are able to go out to, or come in from, this number in particular. Also, even after removing the Yahoo messenger profile, there is still a contact for my Yahoo identity, which apparently cannot be deleted (trying to use Menu > Delete Contact just causes the menu to hang with the Delete Contact choice highlighted).
I also tried sending an SMS from a different number and it worked fine.
I'm thinking that I might have created a corrupt contact when I did that rapid link, unlink, link again thing in a low-signal area, but I don't know.
Please help, anyone who can suggest anything! I'm happy to send my contacts (if I can still do that) to anyone who could provide analysis and a corrective method. Thanks!
Post relates to: Pre p100eww (Sprint)

I was able to reproduce the error. Here are the steps:
1. I called a number and quickly hung up, just as you would do to log a number for saving later.
2. From the call log, I clicked on the SMS button to send a text message.
3. I sent a text message.
4. From the text message log, I clicked on the number at the top to save it to contacts.
5. I saved a new contact with the number.
6. I went back to the text message log card. The text message log still had the number at the top, not the contact's name. I think this is important.
7. I went to the summary view of the text message log (where it shows the message logs for all your contacts). Again, the text message log for the test contact still showed a number and not the contact's name.
8. I deleted the complete message log for the test contact.
9. Finally, I went to the test contact and pressed the SMS button and nothing happens.
Please try this out on a test number and tell me if anyone else can reproduce the result. Try to delete the message log while it is still showing a number instead of the contact's name. I will try it again and will wait for the message log to update with the contacts name.

Corrupted Files Blocking Transfer of Purchases

I recently purchased a 160GB iPod Classic with the intention of being able to store all of my music on a single device. Due to a hard drive crash on my old computer, the only place aside from assorted burned CDs that I have all of my previously purchased iTunes music is on my old iPods. I have tried transferring the purchases; however, due to some corrupted song files (I assume), I cannot get all of the songs to transfer. It stops when it gets to a corrupted file and won't go any further.
I contacted Apple when I first learned that there was something wrong with some of my downloaded music because the songs won't play on any of my devices. Of course, they have my money already and cannot be bothered with customer service, so they said there was nothing I could do except delete and re-purchase the songs for my library, which I had no intention of doing.
Does anybody have any idea how I get the iPod to skip over certain files when transferring purchases? I would really like to be able to transfer them just by logging into my my iTunes account on my new computer, but I don't see an option for that anywhere. Please help!

*Recover media from iPod*
See this post from Zevoneer for options on moving your iPod data back to your computer.
http://discussions.apple.com/message.jspa?messageID=11657508#11657508
Some of the tools linked to will only work if the iPod has a valid library. Others can scan the drive independently and some may even be able to rebuild a damaged library. The manual method towards the end should be able to recover your media regardless of the state of the library.
In your case the iPod's library might be readable but it sounds as if some of the files are not. You could try the manual method pulling one folder at a time out of the iPod.
tt2

Why is diagram clean up corrupting my block diagrams?

A couple of times now (you'd think I would learn my lesson...) I've used the Clean Up Diagram option only for it to render my block diagrams completely unreadable. It's happened on two different systems now..
In this latest incident the flat sequence structure and the labels render as normal but the controls and constants are "smeared out" - for example, instead of being the usual small blue boxes the integer constants are rendered as very tall, thin rectangles. The data flow is completely impossible to discern. It's fascinating.
Anyone seen this before and know how to fix it?
Attachments:
reset_clock_frequency.vi ‏16 KB

I've seen something similar before and I believe this occurs when cleanup results in a block diagram that is larger than the maximum space allowed in the block diagram. The VI you provided appears to go from ~-30000 pixels to ~+28000 pixels in the Y-direction, which is dangerously close to that limit. I'm not aware of any way to recover a VI once it's been saved in this state.
This KnowledgeBase article includes additional information on the maximum allowed size of the front panel and block diagram:
KnowledgeBase 3JEEP1ZH: Maximum Size for Front Panel and Block Diagram
http://digital.ni.com/public.nsf/allkb/62D66358BBF8A87186256FC50077FA17
Tom L.

Corruption of block

Similar Messages

Maybe you are looking for