Synchronization state showing "Intializing..." in informIT history manger window 800xA6.0.3.2
Hi,
We are using one number information management server to store long term history along with 800xA.
800xA and IMS all services and PAS showing healthy in service connection viewer but when we open InformIT history manger we observed the following
Historian state: Active
Synchronization state: Initializing.......
All numerical logs showing "Inactive"
Actions taken but no success:
Please let us know any work around to fix the issue
We are using one number information management server to store long term history along with 800xA.
800xA and IMS all services and PAS showing healthy in service connection viewer but when we open InformIT history manger we observed the following
Historian state: Active
Synchronization state: Initializing.......
All numerical logs showing "Inactive"
Actions taken but no success:
- Restarted PAs is running
- Restarted Server
- dropped and re-created oracle instance
- checked the time sync Ok
- clean hsbdbmaint
- checked the Db
- checked the roles of oraDBA and hsDB
Please let us know any work around to fix the issue
Answers
0
To answer this question, a few more details will be required.
Since you are at 6.0.3-2, is this a new issue or has it been happening for some time?
What preceded this issue, ie. power outage, upgrade, etc. ?
Did you run "hsDBMaint -report" to check to see if there are any errors?
Did you check the Oracle Table Space sizes?
If this was an upgrade, was there a History Backup/Restore done from an older IM node?
I would suggest that you gather this information, along with the IM Log files & alert_adva log file and open a Support case with your local RAC.
IM Log Files: C:\ProgramData\ABB\IM\History\log
alert_adva.log: C:\oracle\diag\rdbms\adva\adva\trace
Regards,
Geof Ledin
Since you are at 6.0.3-2, is this a new issue or has it been happening for some time?
What preceded this issue, ie. power outage, upgrade, etc. ?
Did you run "hsDBMaint -report" to check to see if there are any errors?
Did you check the Oracle Table Space sizes?
If this was an upgrade, was there a History Backup/Restore done from an older IM node?
I would suggest that you gather this information, along with the IM Log files & alert_adva log file and open a Support case with your local RAC.
IM Log Files: C:\ProgramData\ABB\IM\History\log
alert_adva.log: C:\oracle\diag\rdbms\adva\adva\trace
Regards,
Geof Ledin
0
What is seen in the various %HS_LOG% files? Especially the hsHistoryService0.log file.
Have you checked the Log Templates, LT and Log Configurations, LC using the Consistency Checker tool?
IM has been (might still be?) sensitive to if a LC is referencing a non-existent LT. Normally, you cannot delete a LT as long as at least one LC references it. However, you can still get into this situation of "orphaned" LC by importing objects created in another system.
The Consistency Checker will spot this and other problems.
Hint: To have only LTs or LCs checked, use the Find Tool to search for aspects with Aspect Category=LT (or LC). Drag the result to Consistency Checker tool and have them checked.
Do not use/trust the Log Summary aspect's "consistency" column.
Have you checked the Log Templates, LT and Log Configurations, LC using the Consistency Checker tool?
IM has been (might still be?) sensitive to if a LC is referencing a non-existent LT. Normally, you cannot delete a LT as long as at least one LC references it. However, you can still get into this situation of "orphaned" LC by importing objects created in another system.
The Consistency Checker will spot this and other problems.
Hint: To have only LTs or LCs checked, use the Find Tool to search for aspects with Aspect Category=LT (or LC). Drag the result to Consistency Checker tool and have them checked.
Do not use/trust the Log Summary aspect's "consistency" column.
Add new comment