Learn about known issues and workarounds for Replication Agent that are not specific to a particular environment or data server type.
| CR# | Description |
|---|---|
| 701683 |
Migration may not complete although ra_migrate returns a success status if pdb_auto_run_scripts is not set to true. Workaround: Make sure pdb_auto_run_scripts is set to true before starting migration. To check:
ra_config pdb_auto_run_scripts go To change
value:
ra_config pdb_auto_run_scripts, true go |
| 642804 |
Incorrect pdb_auto_create_repdefs command description in the output display. The ra_config displays an incorrect description for pdb_auto_create_repdefs. Workaround: See the Replication Agent Reference Manual for the correct description of the pdb_auto_create_repdefs command. |
| 628568 | Replication Agent initialization may fail when tables are automatically marked for replication. The pdb_xlog init command may fail when pdb_automark_tables is set to true. Workaround: Set the pdb_automark_tables to false before you issue pdb_xlog init. You can set pdb_automark_tables to true after Replication Agent has been initialized. |
| 624714 | Limitation of running Replication Agent as a Windows service on a Microsoft Windows 64-bit platform. Currently, you cannot use the Microsoft Windows Services utility to start, stop, remove, or install a Microsoft Windows service instance of Replication Agent. Workaround: Use agt_service.bat to start, stop, remove, or install a Replication Agent instance. |
| 611175 |
Java Virtual Machine stops responding due to thread stack overflow. When Replication Agent for Oracle or UDB, running on an HP-UX 64-bit machine, processes high volume of data with an insufficient thread stack size memory setting, the Java Virtual Machine (JVM) may crash due to a thread stack overflow: Pid xxxx was killed due to failure in writing to user register stack - possible stack overflow.
Workaround: Adjust the HP-UX PTHREAD_DEFAULT_STACK_SIZE
environment variable to increase the default thread stack size to accommodate
Replication Agent. To do this for all instances of Replication Agent, add the
following two lines to the $SYBASE/RAX-15_5/bin/ra.sh file and set a proper
stack size before running Replication Agent:
PTHREAD_DEFAULT_STACK_SIZE=2048000 export PTHREAD_DEFAULT_STACK_SIZE |
|
Changes to the table replication definition in Replication Server 15.2 or earlier are not recognized by Replication Agent. Replication Agent caches a copy of the table replication definition that it reads from Replication Server. Because Replication Server 15.2 or earlier does not automatically update Replication Agent of changes to the table replication definition, Replication Agent does not know when changes have been made to the table replication definition. Workaround: Before changing the table replication definition in Replication Server 15.2 or earlier, quiesce Replication Agent and wait for it to reach ADMIN state. Replication Agent will use the new table replication definition when you resume replication. |
|
|
Error while loading shared libraries when running on Red Hat Linux 5.0. You may be unable to start Replication Agent due to this error message: Error while loading shared libraries. Workaround: Check the system configuration and change the firewall configuration from enforcing to permissive. You must have root or sudo permission to make this change. |