IM database, message log not added during configuration - how to add after database created?
The IM database appears to have been created with no message log
In the Node Admin Structure the Message log is ACTIVE, on the IM itself the event browser connects to the log but returns no values
Also, using data direct 'message log' returns 'No Data'
Is there a 'simple' way to add the Message Log into the database?
In the Node Admin Structure the Message log is ACTIVE, on the IM itself the event browser connects to the log but returns no values
Also, using data direct 'message log' returns 'No Data'
Is there a 'simple' way to add the Message Log into the database?
Asked 3 months ago
Answers
0
Hi. The Message Log does not get created when you create an IM Oracle database, it has to be added in the Node Administration structure. Can you provide a screen shot of what is there now? I don't know the 800xA version you are using, but the "System 800xA Information Management Configuration" has a section about how to configure a Message Log in section 7 "Alarm/Event Message Logging". Please note that sufficient disk space has to be allocated for the Oracle tablespaces used to store the event data. How many events do you intend to store?
Answered 3 months ago
0
Message log and IM event browser screenshots attached
Answered 3 months ago
0
Hi again. If you had answered "yes' to the question on whether Message Log was to be used the follow up question would be the size. This would then be used for size information when creating two files holding Oracle tablespaces. If you open the Oracle Instance Wizard (Should be in the taskbar of the IM) you will see all the sizes of the different Oracle tablespaces. The ones of interest because they are used to store data for Message Log(s) are INFORM_HS_RUNTIME and HS_INDEXES. These are most likely too small in your case which will stop the storage of event in the Message Log. However, the Oracle Instance Wizard is one place where you can increase the size of the respective tablespaces. I think your size of 500,000 events would require about 300 Mbyte size of INFORM_HS_RUNTIME and 200 - 300 Mbyte for HS_INDEXES.
Answered 3 months ago
0
Please check if the message log have been created by having a look at the output of "hsdbmaint -space" executed in a previously elevated (Run as admin) Command Prompt (cmd.exe). The command output contains "number of history logs" and "number of message logs" in a table like printout after the database size section. Expect 1 message log at design capacity (500000 ?).
If the count is 0, the message log has not been created. This can depend on a few things, free space in Oracle tablespace or consistency errors to mention a few. A full database (one or more tablespaces at or near 100%) is indicated in the output of "hsdbmaint -space". If needed, add more space by enabling and increasing the Auto-Extend feature on struck tablespaces using the IM Oracle Configuration Assistant (which you can call from the Start menu or the IM icon in the system tray). A fully fledged message log (12 million messages) may need several tens of GB of tablespace and disk.
The most common IM message log support case of all categories since epoch is: "a message log has been created with a larger capacity than what the allocated Oracle tablespace permits". This is simple to prevent/correct with Auto-Extend (and tens of GB of disk...). Auto-sizing need to be enabled manually by the system admin.
A synchronization issue is more troublesome to find & correct. First check the Synchronization State on the IM History Manager (call it from the IM system tray icon). It shall not say "Disabled".
A synchronization issue may yield periodic system messages into the [Workplace Structure]Web System Workplace:System Event List. Expect none. You may have to call "hsdbmaint -checkDB" and possibly also "hsdbmaint -clean" (having IM services stopped from PASGUI.exe) from an elevated command prompt to get rid of inconsistencies in Oracle. Refer to the IM Configuration User's Guide for more help with these tools.
Last resort is checking the log files of IM, they are located in the folder %HS_LOG% (just type the variable name in a File Explorer). The file of interest for sync is named "hsHistoryServiceXXX.log". Look for failure messages near the end.
A common issue halting IM log synchronzation is inconsistent configurations in the Aspect Directory, e.g. a Log Configuration aspect has been imported from outside but without the Log Template it is referencing. The IM is unable to synchronize when this have taken place. A "No Log Template" error code/message is typically found in the above log file then. You can translate error codes with "afwerrorlookup.exe".
To find offending configurations, launch the Find Tool of Plant Explorer, set to search for Aspects and add the filter Aspect Category = Log Template, then search. Drag & drop the result into the Consistency Checker Tool (the icon with a small question mark in the upper right corner of Plant Explorer). Correct/Delete any errors found. Next change filter to Aspect Category = Log Configuration and repeat the exercise. Correct/Delete any errors.
On the contrary, if the count of message logs is = 1, a message log has been created in Oracle. Then check its content with respect to number of logged messages and within what timeframe they exist in the database with this SQL statement:
The above login will work from the account used to create the system, or the 800xA service account. If you know the OPS$ocshis account's password (set during installation) you can use it as well (sqlplus ops$ocshis/secret@localhost).
If message logging has once worked but since stopped at some time time while Oracle tablespace is still available, the problem can be an altered event attribute type, e.g. a custom added event attribute has changed from one datatype to another. This is not accepted by IM. This problem can be solved by reverting on the change or force IM to adopt the new datatype. See attached document.
Ultimately, file a support case with your regional ABB support center to obtain professional support.
If the count is 0, the message log has not been created. This can depend on a few things, free space in Oracle tablespace or consistency errors to mention a few. A full database (one or more tablespaces at or near 100%) is indicated in the output of "hsdbmaint -space". If needed, add more space by enabling and increasing the Auto-Extend feature on struck tablespaces using the IM Oracle Configuration Assistant (which you can call from the Start menu or the IM icon in the system tray). A fully fledged message log (12 million messages) may need several tens of GB of tablespace and disk.
The most common IM message log support case of all categories since epoch is: "a message log has been created with a larger capacity than what the allocated Oracle tablespace permits". This is simple to prevent/correct with Auto-Extend (and tens of GB of disk...). Auto-sizing need to be enabled manually by the system admin.
A synchronization issue is more troublesome to find & correct. First check the Synchronization State on the IM History Manager (call it from the IM system tray icon). It shall not say "Disabled".
A synchronization issue may yield periodic system messages into the [Workplace Structure]Web System Workplace:System Event List. Expect none. You may have to call "hsdbmaint -checkDB" and possibly also "hsdbmaint -clean" (having IM services stopped from PASGUI.exe) from an elevated command prompt to get rid of inconsistencies in Oracle. Refer to the IM Configuration User's Guide for more help with these tools.
Last resort is checking the log files of IM, they are located in the folder %HS_LOG% (just type the variable name in a File Explorer). The file of interest for sync is named "hsHistoryServiceXXX.log". Look for failure messages near the end.
A common issue halting IM log synchronzation is inconsistent configurations in the Aspect Directory, e.g. a Log Configuration aspect has been imported from outside but without the Log Template it is referencing. The IM is unable to synchronize when this have taken place. A "No Log Template" error code/message is typically found in the above log file then. You can translate error codes with "afwerrorlookup.exe".
To find offending configurations, launch the Find Tool of Plant Explorer, set to search for Aspects and add the filter Aspect Category = Log Template, then search. Drag & drop the result into the Consistency Checker Tool (the icon with a small question mark in the upper right corner of Plant Explorer). Correct/Delete any errors found. Next change filter to Aspect Category = Log Configuration and repeat the exercise. Correct/Delete any errors.
On the contrary, if the count of message logs is = 1, a message log has been created in Oracle. Then check its content with respect to number of logged messages and within what timeframe they exist in the database with this SQL statement:
C:\> sqlplus /@localhost
SQL> select count(*), min(localtime), max(localtime) from immsglog_ip;The above login will work from the account used to create the system, or the 800xA service account. If you know the OPS$ocshis account's password (set during installation) you can use it as well (sqlplus ops$ocshis/secret@localhost).
If message logging has once worked but since stopped at some time time while Oracle tablespace is still available, the problem can be an altered event attribute type, e.g. a custom added event attribute has changed from one datatype to another. This is not accepted by IM. This problem can be solved by reverting on the change or force IM to adopt the new datatype. See attached document.
Ultimately, file a support case with your regional ABB support center to obtain professional support.
0
Hi. Is your problem solved yet? If not, and you can start again I suggest you drop the IM database and then re-create it with the appropriate answer to the Message Log question from the Wizard.
Answered 3 months ago
Add new comment