The problem description is that the stop post was issued on the target database and it showed that the post process is stopped by user.Then recycled SharePlex (shutdown and re-run sp_cop). The expectation is that post process suppose to continue to stay as stopped by user status. Yet post shows running.In the past the system honor the user action and keep the post process stopped until manually start it again.
Event_log shows 0x00000000000000000000000000000001 for hostname instead of actual hostname:
Notice 2018-03-01 10:44:59.871687 10041 3830384512 User command: oracle stop post (from 0x00000000000000000000000000000001)
Workaround:
1. Remove the hostname from the /etc/hosts file and save the file, as the root user
Example with hostname added to loopback:
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 alvsupl19
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 alvsupl19
10.1.23.156 alvsupl19.prod.quest.corp alvsupl19
Example with hostname removed from loopback:
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
10.1.23.156 alvsupl19.prod.quest.corp alvsupl19
2. bounce SharePlex
On version 9.0.1, there is not "Your tcp port is not set properly or 'sp_cop' is not running" notice when attempting to get into sp_ctrl whether SP_SYS_HOST_NAME is exported of not with the hostname in the loopback. The user is able to start sp_cop and get into sp_ctrl and the event_log does not log any notice related to getaddrinfo. The post is automatically launched after restarting SharePlex even though it was stopped by user prior to issuing a SharePlex shutdonw.
On version 9.0.2, there is a "Your tcp port is not set properly or 'sp_cop' is not running" notice when attempting to get into sp_ctrl with SP_SYS_HOST_NAME is exported of not with the hostname in the loopback. The user is able to start sp_cop but not get into sp_ctrl and the event_log says “Notice 2018-03-01 13:41:54.817976 13470 3297785696 Process: rmp_param: getaddrinfo( ) failed (rmp) [module rmp]”. Unsetting the SP_SYS_HOST_NAME, user is able to start cop and get into sp_ctrl and stop post and shutdown, restart cop and the post remains stopped by user as designed.
On version 9.1 WITH SP_SYS_HOST_NAME exported, user is able to start SharePlex but when attempting to get into sp_ctrl notice "Your tcp port is not set properly or 'sp_cop' is not running" is returned and is unable to get into sp_ctrl with the hostname in the loopback. WITHOUT SP_SYS_HOST_NAME exported everything works fine with the hostname in the loopback.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center