Log configuration

Hello every one
We delete two objects from conrol structure and recreate them(FRIQ205,FIRQ0001).after that insert new log configuration aspect in aspect area , but not activate.in addition all of log configuration stored in IM historian.photos related to problem attached;Pls recommend solution for this problem.
Thanks

Comments (0) New comment

mohsennazari6453 Rank: 656

Asked 28 days ago

Answer this question Follow

Voted best answer

There are a few things you should check here:

1. Make sure disk quota permit adding more logs (use IM Database Instance Wizard).
2. Make sure Oracle disk space is not 100% filled for any tablespace (use same tool as above).
3. Make sure no corrupted entries remain in log database (use "hsdbmaint -checkDB" and "hsdbmaint -clean" as necessary, both are outlined in the IM Configuration User's Guide).
4. Make sure there are no consistency errors in any Log Template aspect (use the Plant Explorer's Find Tool, search for Aspect Category = Log Template, drop result in Consistency Checker, fix or delete errors).
5. Make sure there are no consistency errors in any Log Configuration aspect (use the Plant Explorer's Find Tool, search for Aspect Category = Log Configuration, drop result in Consistency Checker, fix or delete errors).
6. Make sure all IM services are running OK w/o warning in PASGUI.exe (tool) or IM History Manager (via icon in system tray).

Consider filing a support case with your regional ABB Support Center to obtain professional support.

Comments (2) New comment

Stefan Stromqvist AKS expert

Rank: 1

Answered 27 days ago

Answers

above items are checked and the results are as follow photos.

Comments (2) New comment

mohsennazari6453 Rank: 656

Answered 27 days ago

I performed hsdbmaint -checkDB ,the result is as follow photos.in addition do not see any inconsistency.

Comments (19) New comment

by Stefan Stromqvist AKS expert

Rank: 1 on 12/23/2020 2:31:07 AM | Like (1) | Report

On the contrary, in the second image I see 5 + 28 logs in inconsistent state.
You should stop IM services and run a "hsdbmaint -clean" to have them purged.
Then startup, wait a few minutes and perform a new "hsdbmaint -checkDB" and expect "0 logs to delete".

If this does not work, I believe you should file a support case with your regional ABB support center (hand over a ZIP of all files below %HS_LOG% when filing the case).

by Stefan Stromqvist AKS expert

Rank: 1 on 12/23/2020 2:33:25 AM | Like (1) | Report

What were the results of consistency check? You said OK but you did not provide any images, etc. of what was checked.

A standard error to see "no new logs in IM" is if there is inconsistent log configurations in the system.

How many Log Templates and Log Configurations did you find & check with the Consistency Checker Tool?

by mohsennazari6453 Rank: 656 on 12/23/2020 3:16:38 AM | Like (0) | Report

When I performed hsdbmaint-checkDB ,new page open and start check data base after that this page automatically closed,nothing text or message in main cmd page do not shown so i concluded that is not any inconsistency.

by mohsennazari6453 Rank: 656 on 12/23/2020 3:21:12 AM | Like (0) | Report

Also i performed consistency check for log template ,log configuration aspect and inform it log set in node admin structure,then shown No error found for all of them.

by mohsennazari6453 Rank: 656 on 12/23/2020 3:25:17 AM | Like (0) | Report

I have a question, that is i try to use history utility in IM server by admin users but credential error shown.how do i can change or find password? And can this at all contribute to the recent problem?

by Stefan Stromqvist AKS expert

Rank: 1 on 12/23/2020 3:59:36 AM | Like (1) | Report

Your comment regarding consistency check makes me suspect you did not check ALL Log Template and Log Configuration aspects in the entire system (the Node Administration Structure usually have none of them...)

Please do as I did describe in my first comment (use the Find Tool to search for Aspects with Category = Log Template, then Log Configuration). Drag the results to the Consistency Checker Tool. There must be 0 errors/warnings when your have completed this important step.

The hsdbmaint.exe should be called from an elevated CMD.EXE (i.e. started using "Run as administrator").

I don't understand your last comment. History Utility? What is that?

I recommend to use the 800xA Installer or 800xA Service accounts, they both should have full access to the IM platform.

Consider asking your regional ABB Support Center to assist you.

by mohsennazari6453 Rank: 656 on 12/23/2020 6:18:28 AM | Like (0) | Report

For 800xA History Configuration Utility Navigate to the path: “C:\Program Files (x86)\ABB Industrial IT\Inform
IT\ABB 800xA History Connectivity\bin” on the 800xA History Data Collector
Nodes and double click on the tool to launch.

by mohsennazari6453 Rank: 656 on 12/23/2020 6:21:07 AM | Like (0) | Report

What is path of find Consistency checker tool ?

by Stefan Stromqvist AKS expert

Rank: 1 on 12/23/2020 6:33:58 AM | Like (1) | Report

Why are you mentioning "800xA History"? The images you posted come from Information Manager, another of the 4-5 historians part of the 800xA suite of products. IM and 800xA are seldomly mixed in the same system!

The Consistency Checker Tool is launched from the Plant Explorer, top right corner (the icon with the question mark and a small figure "1" inside a square).

Consisterncy Checker is described in chapter 7 of Reference Tools 2PAA101888-610 A (page 94 and forward)

I am beginning to loose patience - you have skipped actions I asked you to perform; this wastes time (something I have very little to offer you here on this public forum).

There is an official support channel you can access via your regional ABB Support Center. Use it to obtain professional support.

by mohsennazari6453 Rank: 656 on 12/23/2020 6:53:10 AM | Like (0) | Report

Dear Master, you got it wrong.i checked consistency check but from instance defenition aspect and object type definition aspect.so i deffenitely check by consistency checker tool,send you the respective result.

by Stefan Stromqvist AKS expert

Rank: 1 on 12/23/2020 7:44:08 AM | Like (1) | Report

The best you can hope for is that you do find errors in your LC and/or LTs. They often halt the IM sync of new logs.

A typical error is that you export some objects from system A including some Log Configurations (LCs).
Later you import those objects into system B.
If the Log Templates (LTs) used by the exported LCs is not existing in system B you get a consistency error like "No Log Template Found". To solve this, either export the LTs from A and import to B, or erase the "orphaned" LCs from B and create new.

The Bulk Data Manager and the LogConfig.xlsx bulk sheet is a good friend here; very quickly you can find the LCs and change the LTs they are referencing,

Needless to say, BDM is detailed in the Engineering Studio suite of user's guides.

by mohsennazari6453 Rank: 656 on 12/23/2020 9:03:48 AM | Like (0) | Report

Thanks
Once i created new log config or the respective objects that not have proper result.later delete that and create LC with copy from LC related to the object thats ok but not have proper result again.all of work done in same system.

by mohsennazari6453 Rank: 656 on 12/23/2020 9:08:50 AM | Like (0) | Report

I checked consistency checked on saturday because i am in rest.🙏

by Stefan Stromqvist AKS expert

Rank: 1 on 12/23/2020 9:10:02 AM | Like (1) | Report

OK
If all my advises turn up without any finding it is indeed time for you to file an official support case with your regional ABB support center. Don't forget to attach the %HS_LOG% folder content, zipped, to the case.

by mohsennazari6453 Rank: 656 on 12/23/2020 10:03:48 AM | Like (0) | Report

If i stop IM service and perform cleaning ,is not problem for process thats running and another data log.
What do you meant %HS_LOG%?

by Stefan Stromqvist AKS expert

Rank: 1 on 12/23/2020 10:42:55 AM | Like (1) | Report

Stopping IM will arrest its duties - the HMI and PLC will continue to perform theirs.

%HS_LOG% is a folder on disk. Type the variable name in the Address Bar of Windows Explorer.

by mohsennazari6453 Rank: 656 on 12/23/2020 1:01:57 PM | Like (0) | Report

Thanks.🙏

by mohsennazari6453 Rank: 656 on 12/25/2020 10:28:32 PM | Like (0) | Report

If i perfomed cleaning ,notice that operation need to some log that work correctly at this time hence Dont these logs become difficult or erased?

by Stefan Stromqvist AKS expert

Rank: 1 on 12/26/2020 3:01:49 AM | Like (1) | Report

"hsdbmaint -clean" should only remove inconsistencies, but always maintain fresh IM History Backups in case something should go wrong.

Repeat until there are 0 inconsistencies reported.

Please contact your regional ABB Support Center for assistance. IM is a complex product hard to "auto didact".

Add new comment

mohsennazari6453 Rank: 656

Answered 27 days ago

I performed consistency check for LC and LT by consistency checker tool and the respective results are as follow photo.so check the errors and warning ,found these are wrong configuration.so delete them.and performed consistency check again and send result photo.

Comments (4) New comment

by Stefan Stromqvist AKS expert

Rank: 1 on 12/26/2020 2:58:20 AM | Like (1) | Report

The "No History Source" should be obvious; the Log Configuration is in a location where it has no History Source on any ascendant object. This is OK in Object Type Structure, etc. when the library creator has supplied a template aspect. On the other hand, if the inconsistent Log Configuration is located on an object where you expect logging to take place, e.g. in the Control Structure, you must figure out the best solution to add a History Source aspect somewhere. Typically, the History Source is put at the highest located common denominator for a group of objects that should be attended by a specific service group of Basic History.

The remainder of of consistency errors need to be further examined - has the Log Configuration been created by copying it from an incompatible object?

E.g Control Module X has property Y logged by Log Configuration Z referencing Log Template W.

If that Log Configuration Z is copied to Function Block A where there is no property Y you will get a similar error as your examination has shown.

Make sure all log configurations are "sane" and properly pointing out a suitable template.

by mohsennazari6453 Rank: 656 on 12/26/2020 3:12:14 AM | Like (0) | Report

If exist tool to check allo of log configuration in terms of sane.

by Stefan Stromqvist AKS expert

Rank: 1 on 12/26/2020 9:48:45 AM | Like (1) | Report

Yeah, the consistency checker. Sane = nothing unexpected reported. A missing History Source may be expected outside where logging is expected.

by mohsennazari6453 Rank: 656 on 12/26/2020 10:07:06 AM | Like (0) | Report

Please more explaine.it is meant that it doesnt need to more work and it is fine to clear errors from consistency checker tool is sufficient.

Add new comment

mohsennazari6453 Rank: 656

Answered 24 days ago

The respective result about hsdbmaint -checkDB are as follow.How do I delete those 28 items?

Comments (4) New comment

mohsennazari6453 Rank: 656

Answered 24 days ago

Question details

Log configuration

Voted best answer

Answers

Other questions needing answers

Related topics

AKS experts