Error and Warning Codes

Could not connect to APPLY process. Resource temporarily unavailable.

Could not connect to MINE process. Resource temporarily unavailable.

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 replication process. Example "choose replication apply1" (so console knows we want the second direction)
2. list conflict (to see the actual conflicting statement)
3. resolve conflict

For more information please see Conflicts and Conflict Resolution

ORA-01017: invalid username/password

libnnz11.so:

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

This can result if the parameter _MINE_FIX_INVALID_DATE_NEW_VALUE is changed. This is because this shifts the offset of data in the PLOG file because 8 bytes are added (7 bytes, rounded up) every time a replacement is done. When MINE is restarted it will send the new PLOG to APPLY, which was still waiting on the old PLOG to finish. So it now has mix of old and new PLOG file, reading data at invalid place, and causing a memory error. An restart of APPLY will fix the issue. 

This usually happens when the Fetcher is configured incorrectly.

To fix, show the network interfaces to highlight where it is incorrectly configured.

Example:

dbvrep> show interface                                                                                                                         
*.APPLY_LISTEN_INTERFACE = undefined:1
APPLY.APPLY_LISTEN_INTERFACE = 0.0.0.0:7902
*.APPLY_REMOTE_INTERFACE = undefined:1
APPLY.APPLY_REMOTE_INTERFACE = target:7902
*.FETCHER_LISTEN_INTERFACE = undefined:1
FETCHER.FETCHER_LISTEN_INTERFACE = 0.0.0.0:7901
*.FETCHER_REMOTE_INTERFACE = undefined:1
FETCHER.FETCHER_REMOTE_INTERFACE = source:7901
*.MINE_LISTEN_INTERFACE = undefined:1
MINE.MINE_LISTEN_INTERFACE = 0.0.0.0:7901
*.MINE_REMOTE_INTERFACE = undefined:1
MINE.MINE_REMOTE_INTERFACE = source:7901

In this case, then MINE.MINE_REMOTE_INTERFACE is configured incorrectly. This should be running on server called "target".

Change the setting:

dbvrep> set MINE.MINE_REMOTE_INTERFACE = target:7901                                                                                           
Variable MINE_REMOTE_INTERFACE set to target:7901 for process MINE.

Restart all processes and the issue has been resolved.

Timeout waiting for incoming data (timeout 60s) - get command

Network timeout. Increase the timeout setting on the following variables:

set MINE.NETWORK_QUALITY WAN
set NETWORK_QUALITY WAN
set _TCP_CONNECT_TIMEOUT 300
set _TCP_RECEIVE_TIMEOUT 300
set _TCP_SEND_TIMEOUT 300

The steps to updating these settings are

1. Shutdown MINE and APPLY and Console
2. Add the above settings to the end of the *MINE.ddc.
3. Restart the MINE process
4. Restart the APPLY process once MINE has been restarted
5. Start console and verify that the settings have been updated with the "show variable_name" command

ERR-4213

Timeout (or dropped connection) trying to send data for command engine fileinfo plog x

The ERR-4213 messages may point to some 'issue' at the network level, although the details of this are not specified, and so you should review the connection with your network admin team. The key, however, is that Dbvisit Replicate will pick up and try again after hitting one of these points - and if the processing continues past this point then all is good. Messages to be particularly aware of, and which would indicate an issue (rather than a temporary glitch), would be in the APPLY log where you can see the application waiting for extended periods of time to receive plog information, when you know that there is activity happening on the primary which ought to be replicated.

Another possible reason is that Apply is very busy with the number of Inserts (etc) and so a timeout is happening on the networking thread. If this is the case then a workaround is to increase the timeout setting on the following variables:

set MINE.NETWORK_QUALITY WAN 
set NETWORK_QUALITY WAN 
set _TCP_CONNECT_TIMEOUT 300 
set _TCP_RECEIVE_TIMEOUT 300 
set _TCP_SEND_TIMEOUT 300 

The steps to updating these settings are:

1. Shutdown Mine and Apply and Console 
2. Add the above settings to the end of the *MINE.ddc. 
3. Restart the Mine process 
4. Restart the Apply process once Mine has been restarted 
5. Start console and verify that the settings have been updated with the "show variable_name" command

No changes are required for APPLY. The changes made in the MINE.ddc take affect in the DDC DB (database) so that applies to both Mine and Apply.

The TNS_ADMIN directory set in the .ddc file does not exist on this server. Please update the .ddc file and point to the correct location and start the process again.

Example:

memory_set TNS_ADMIN /u03/app/oracle/product/11.2.0.03/dbhome_5/network/admin

need explicit attach before authenticating a user.
Check database and listener are running. Check your TNS settings. Please check and/or update TNS_ADMIN in the DDC file to point to correct
tnsnames.ora location.

Check to ensure that the correct TNS_ADMIN is specified. To verify use tnsping to see if a connection to the database can be made.

This error is sometimes in combination with error:

ERR-11: Could not connect as xxx to database xxx, error is ORA-24327: need explicit attach before authenticating a user
(DBD ERROR: OCISessionBegin)

ORA-04031: unable to allocate 104 bytes of shared memory. More error messages may follow such as:

BEGIN dbms_streams_auth.grant_admin_privilege('dbvrep'); END;
*
ERROR at line 1:
ORA-04031: unable to allocate 104 bytes of shared memory ("shared pool","select
/*+ rule */ bucket, e...","SQLA^bbcee4f7","opiprwd : opitca")
ORA-06512: at "SYS.DBMS_STREAMS_AUTH", line 1606
ORA-06512: at line 1
Error encountered, not starting Dbvisit Replicate.

ORA-12705

KERNELBASE.dll

It could happen during start -all.sh/-all.bat script.

Solution: Kill all connections to database from user which was set up in configuration, Step-1. (Usually it is dbvrep)