Replication Source Server startup errors always appear in the Source Server log file. In previous versions of YottaDB, if the Source Server was started from the terminal, and the Source Server startup command failed or the Source Server successfully started but later failed (e.g. with errors like NULLCOLLDIFF, REPLOFFJNLON, REPLINSTNOHIST, SECNOTSUPPLEMENTARY etc.) this error message did not show up in the Source Server log file or on the terminal where it was started (assuming that terminal still exists at the time of the error). The release notes of GT.M V6.3-004 mention that this issue has been fixed by GTM-8576 but we found the issue exists even in GT.M V6.3-004. (#210)
Description
Set up a 2-region database with one region having standard null collation turned on and the other having it turned off. Enable replication on the two regions. And start the source server. The source server startup will fail. In prior versions of YottaDB, one used to get a NULLCOLLDIFF error in the terminal where one attempts the source server startup. But in the current mainline of YottaDB (which has inherited the GT.M V6.3-004 changes), no such error shows up either in the terminal or in the source server log. Without a debugger to step through the code, one would have no clue on why the startup failed. This is an issue in GT.M V6.3-004 most likely due to GTM-8576 which has the following release note.
The Source Server directs errors to the Source Server log file. Operators should be sure to check the Source Server log; previously it directed errors to stderr, which meant that if it was started from a terminal and the terminal session closed, a subsequent error logged an inappropriate NOPRINCIO error and terminated the Server. (GTM-8576) [!Alert!] [!New Feature!]
The NULLCOLLDIFF error was previously issued to stderr but was not changed to go to the source server log file as part of GTM-8576.
Draft Release Note
The replication source server issues startup errors in the source server log file in all cases. Note that this is not an issue in any YottaDB release but was discovered after integrating GT.M V6.3-004 into the YottaDB codebase after r1.20. In GT.M V6.3-004, if the source server was started from the terminal, and the source server startup command failed or the source server was successfully started but later failed, it was possible in case of some errors that the actual error message never showed up either on the terminal or the source server log (e.g. NULLCOLLDIFF, REPLOFFJNLON, REPLINSTNOHIST etc.).
Final Release Note
Replication Source Server startup errors always appear in the Source Server log file. In previous versions of YottaDB, if the Source Server was started from the terminal, and the Source Server startup command failed or the Source Server successfully started but later failed (e.g. with errors like NULLCOLLDIFF, REPLOFFJNLON, REPLINSTNOHIST, SECNOTSUPPLEMENTARY etc.) this error message did not show up in the Source Server log file or on the terminal where it was started (assuming that terminal still exists at the time of the error). The release notes of GT.M V6.3-004 mention that this issue has been fixed by GTM-8576 but we found the issue exists even in GT.M V6.3-004. (#210)
Description
Set up a 2-region database with one region having standard null collation turned on and the other having it turned off. Enable replication on the two regions. And start the source server. The source server startup will fail. In prior versions of YottaDB, one used to get a NULLCOLLDIFF error in the terminal where one attempts the source server startup. But in the current mainline of YottaDB (which has inherited the GT.M V6.3-004 changes), no such error shows up either in the terminal or in the source server log. Without a debugger to step through the code, one would have no clue on why the startup failed. This is an issue in GT.M V6.3-004 most likely due to GTM-8576 which has the following release note.
The NULLCOLLDIFF error was previously issued to stderr but was not changed to go to the source server log file as part of GTM-8576.
Draft Release Note
The replication source server issues startup errors in the source server log file in all cases. Note that this is not an issue in any YottaDB release but was discovered after integrating GT.M V6.3-004 into the YottaDB codebase after r1.20. In GT.M V6.3-004, if the source server was started from the terminal, and the source server startup command failed or the source server was successfully started but later failed, it was possible in case of some errors that the actual error message never showed up either on the terminal or the source server log (e.g. NULLCOLLDIFF, REPLOFFJNLON, REPLINSTNOHIST etc.).