Hi,
My primary db (10g R2 Soalris) has a tablespace created by transported
it from other database (using oracle transportable tablespace ). it
has two datafiles (aa01 and bb02.dbf). The tablespace is read
writeable.
I then tred to create a logical standby db for the primary db using
RMAN. During creation, Oracle report such error:
Part one:
ORA-19502: write error on file "/oracle/oradata/**/aa01.dbf"
ORA-27063: number of bytes read/written is incorrect
SVR4 Error: 28: No space left on device
This is weird since there are plenty space left on disk
Part two:
creating datafile fno=7 name=/oracle/oradata/**/bb02.dbf
RMAN-06136: ORACLE error from auxiliary database: ORA-19723: Cannot
recreate plugged in read-only datafile 7
The message is misleading. bb02.dbf belongs to a read write tablespace.
did anyone know anything about that? is it a bug either in
transportable db or logical standby?
thanks in advance.
frank.van.bortel@gmail.com - 31 Mar 2006 11:54 GMT
You can only use RMAN to create a physical standby database, not a
logical.
And about your SVR4 error 28: could it be quota?
hongfeng.sun@gmail.com - 31 Mar 2006 11:57 GMT
>You caan only use RMAN to create a physical standby database, not a
logical
Yes, I know. I created physical one first, then convert to logical
ones. The errors I came across occured during phyical standby db
creation.
Frank van Bortel - 31 Mar 2006 15:49 GMT
> Part two:
> creating datafile fno=7 name=/oracle/oradata/**/bb02.dbf
> RMAN-06136: ORACLE error from auxiliary database: ORA-19723: Cannot
> recreate plugged in read-only datafile 7
>
> The message is misleading. bb02.dbf belongs to a read write tablespace.
RMAN restoring a backup, created when the datafile actually still
was read-only?

Signature
Regards,
Frank van Bortel
Top-posting is one way to shut me up...