Originally posted by: Backdoor
I have successfully replicated test data for this customer which includes an Oracle database. Was able to do takeover operations successfully also. They even agreed that everything looked good.
On the last test that was performed, the Oracle database was not able to be brought online due to an inconsistent size in one of its data files. See the error below.
The Sys admin for the Solaris host that the database resides on says he thinks that when he did an fsck on the filesystem that some of it got truncated which caused this problem with the database.
They are asking me if there is any way to avoid this or if there are any best practices for configuring Oracle with replication in a Solaris UFS environment.
Is anyone aware of anything basic that I should be looking at? Are there any whitepapers that you can share? Or any gotchas that I need to watch for?
Database refresh failed on server CUNIP05.
Connected to an idle instance.
ORACLE instance started.
Total System Global Area 264241152 bytes
Fixed Size 2039888 bytes
Variable Size 88088496 bytes
Database Buffers 171966464 bytes
Redo Buffers 2146304 bytes
ORA-01122: database file 4 failed verification check
ORA-01110: data file 4: '/db02/oradata/HITACHI/HITACHI_TEST_users01.dbf'
ORA-01200: actual file size of 31872 is smaller than correct size of 32128