| Error code | Error Text | Resolution |
|---|---|---|
| FATAL-7002: | Internal error: Redo block checksum failed | This happens when the mine restarts and the generated plog is different from the one it created previously (or usually started to create). The solution is to restart the both mine and apply processes. |
Could not connect to APPLY process. Resource temporarily unavailable. Could not connect to MINE process. Resource temporarily unavailable. | This is a network issue. Please check that the hostname used in the configuration resolves to the correct IP address and that no firewall blocks the connection on the specified ports. Use the command "SHOW INTERFACE" to see the host:port used by Dbvisit Replicate. | |
| ORA-00955 | Conflict | The ORA-00955 indicates a conflict due to DDL replication. If doing 2-way replication, consider whether you really need to replicate DDL changes as getting this correct not trivial (to prevent the DDL change to be applied to second database and getting replicated back to source). The proper steps for a conflict resolution is: 1. choose the correct process. Example "choose process apply1" (so console knows we want the second direction) 2. list conflict (to see the actual conflicting statement) 3. resolve conflict |
| -1: Operation now in progress | This can be with issuing any command such as "RESOLVE CONFLICT" | This is a network timeout issues. Please try again. |
ORA-01017: invalid username/password | ERR-11: Could not connect as dbvrep to database, error is ORA-01017: invalid username/password; logon denied (DBD ERROR: OCISessionBegin) FATAL-9043: Error detected and ON_ERROR set to EXIT. | The Dbvisit Replicate login is not correct. Please ensure the password is correct. To change the password please see "How do we change the Dbvisit Replicate schema user password (default: dbvrep)?" under FAQ and other troubleshooting questions and tips |
libnnz11.so: | Cannot restore segment prot after reloc: Permission denied | Currently Dbvisit Replicate does not work with Security-Enhanced Linux. To check if SELinux is enabled, run command "/usr/sbin/getenforce". If the output is "Enforcing" then SELinux is enabled. To disable SELinux, please see http://www.crypt.gen.nz/selinux/disable_selinux.html |
| ORA-01110 | data file x: filename.dbf (DBD ERROR: error possibly near indicator at char 337 in ' select ID, SCHEMA_NAME, | This is not an actual conflict, but failing SQL that tries to read the conflict information - the base error is ORA-01187: cannot read from file because it failed verification tests. The file is most likely a tempfile. Please check whether the mentioned tempfile exists. Check the steps to create the target database. In 11g, rman restore/duplicate usually creates necessary tempfiles automatically. |
General
Content
Integrations