Unified Reporting DB status

[joeharb]

I am preparing to apply the dst patch and have ran into an issue with the DB replication...when I go into unified reporting it states it can't reach the subscriber:

hows if replication is good or bad.

RTMT Counter Information

Error The bk0074ccm2 server cannot be reached.

Checking in RTMT both database states are @ 2. Is this a bug within the reporting..we are running version 6.1.2.1001-4. Everything seems to be working fine...phones are registered to Sub.

Thanks,

Joe

[joeharb]

Update:

I tried to do a utils dereplication stop on all nodes then a reset all on the pub. I now get a command failed -- Enterprise Replication not active (62) error and it appears the sub has a state of 0 and the pub is @ 2.

Any ideas..

Joe

[joeharb]

Update 2:

From RTMT both pub and sub have a status db replication state of 2. Still get the bk0072ccm2 cannot be reached error in Unified Reporting.

Joe

[kelvin.blair]

Joe,

I'm experiencing the same issue and it didn't occur until after the DST patch. I'm on the phone with TAC right now.

[joeharb]

Thanks for the reply...my issue is that I am not going to apply the patch until I get a good response from Unfied Reporting. Are you receiving the same error that the server cannot be reached? or the Enterprise error?

[kelvin.blair]

Same issue as you to the "T".

[kelvin.blair]

I'm still waiting to hear back from TAC, but found this bug CSCso82088.

[joeharb]

Please keep me updated on the status...have you ran the command...RTMT shows that the databases are in a good state...I still can't figure out why when I run the Unified reporting I get the server can't be found...I can ping it by name both ways...well I guess I will wait for further word.

Thanks,

Joe

[joeharb]

Any updates from TAC?

[kelvin.blair]

no updates at this time. Still waiting for them to get back to me. It has been pushed to the developers.

[joeharb]

Kelvin,

Took a shot @ rebooting both servers. Still no go, I have successfully done the upgrade on a 5.1.3 server with no issues, have they let you know if this a cosmetic issue...the fact the rtmt shows the database is in a good state is a good thing I would assume. The only thing this is affecting for the customer is TOD..which is a pretty big thing. Please keep me in the loop of any information that I may be able to give the customer.

Thanks,

Joe

[joeharb]

Do you know if this will affect a one server cluster...we have another customer that has one server running the same version that has one server in the cluster and I get a similar result:

RTMT Counter Information

Error All servers do not have a replication count of 393.

Error Not all servers have a good replication status. See the details.

Is the expected for a one server enviroment?

Thanks again for all your help.

Joe

[kraghavansag]

If the phones are registered to the subscriber, can you check the status if the phones in the pub? are they showing registered or unknown?

[joeharb]

The phones register to the sub during normal operating conditions...I have restarted both servers and the phone will register to the pub when the sub is down. Everyting seems to be working fine as far as phones registering to either CCM. I have set all TOD timezones back to their respective zone. All appears to be working for now but I would assume I would need to apply the patch prior to the Nov. switch. I also would like to be able to apply any patches that may be released in the interm.

Joe

[mcibanez]

Hi Joe and Kelvin,

I'm experiencing the same issue.

I've got a CM cluster of 6 servers, running 6.1.3.3101-1

Although all of them show a replication status of 2, in the Unified Reporting DB status of 3 of them I get the message 'The x.x.x.x server cannot be reached' (all of the 3 pointing to the same server)

Did you ever find out the solution?

Thanks in advance.

Best regards,

Carmen