 RMAN error ORA 27603 [message #175493] |
Fri, 02 June 2006 08:58  |
sinistral
Messages: 7
Registered: November 2005
|
Junior Member |
|
|
I am getting this consistent error stack message from my backups on one of the two databases we have on this server.
Server OS: Solaris 5.9
DB: Oracle 10gR2 (no patches)
RMAN: Recovery Manager: Release 10.2.0.1.0 - Production
the error stack is as follows:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 06/02/2006 02:05:25
ORA-19501: read error on file "[filename]", blockno 320705 (blocksize=8192)
ORA-27063: number of bytes read/written is incorrect
Additional information: 221184
Additional information: 524288
What I read from the Oracle Error definitions is that this appears to be twice as large as it should be? How do I fix those tags on the dbf? Would a COALESCE fix this, or some other tablespace command? It seems to be able to be read from normally. This is a development database, so no HUGE issue that I know of, but I do not have a good backup of this database to recover the tablespace file from. We are currently running one datafile per tablespace.
Thanks for any help
S L Niemann
|
|
|
|
| Re: RMAN error ORA 27603 [message #175519 is a reply to message #175493] |
Fri, 02 June 2006 10:27  |
aciolac
Messages: 242
Registered: February 2006
|
Senior Member |
|
|
The only sense of this error - that Oracle cannot read some files of database. Possible that file are not on the disk(deleted, moved), but in controlfile definition of file exist. If You are changed physical structure of database, he are not automatically reflects in catalog database. For rman to be inline about new changes in database, you must to connect to your target(and catalog of course ) and execute command
RMAN>resync catalog;
|
|
|
|
 Re: RMAN error ORA 27603 [message #175520 is a reply to message #175519] |
Fri, 02 June 2006 10:40 |
sinistral
Messages: 7
Registered: November 2005
|
Junior Member |
|
|
|
It looks like actually Bad Disk sector. Our SAs are working on that aspect; we just need to move our tables out of that tablespace into a new one hopefully not created on a damaged sector. I hope this is all it is, so we can backup and then put in a new disk.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
