How can I find if the Oracle database is sending the proper batch event information?
On 05-09-14 at about 3:40PM our batch events stopped updating in PI. I have since restarted the RDBMS PI Batch Data services as well as the PI server, Oracle database server, and the PI configuration server. The RDBMS log file does not have any errors in it. I have spoken to OSI support and we found that the RDBMS interface was operating normally and was able to write to most tags. However, the distributor tag NE_BatchEventDistributor did not distribute values to any tags since 5/9/2014 around 3:40 pm. The distributor tag is running the stored procedure “PI_Interface_GetBatchEvents” to populate the tags and we suspect that the source database table did not receive any updated values since 5/9/2014 afternoon. OSI support stated that the next step would be to look in the Oracle SQLPlus database to determine if there are any new operationstate values (possible from //PIBATCHLOG/OPERATIONSTATE/@Value); if not, the troubleshooting focus should be the link between the batch system and the oracle database.
Please help if you have any valuable knowledge on this issue.
Your PI interface to the batch events on your site is entirely non standard and relies on SQL stored procedures and tables added to the IM by NNE. Your site is quite unique.
Essentially, you need to verify if events are being recorded into the IM. There is a simple web page on your site to veryfy this. The IM does not "distribute" anything to PI - the PI RDBMS interface simply tries to read the event tag aftert he stored procedure has executed.
There should not be any "new operation state variables" but again these are created using the web pages used to check the event log. Its more likely that something is triggering a bug in the stored procedures because a limit is exceeded somewhere.
This probably is not the best place to solve the problem. Send me a mail.
Check that the IM PDL log is updated (refer to IM Data Access & Reports Users Guide for details on how to query Oracle for PDL data). There may even exist a PDL Event Viewer in the standard delivery just as there is one for OPC Message Logs, but I can't verify that right now.
If the IM PDL logs updates as expected and Rob Lyon is correct about your custom made IM->PI interface its probably time to contact the organisation that delivered it to you - the IM has no "delivery mechanism", it must hence have been added as a custom application by someone with programming skills in Oracle, etc.
Adding custom config to the IM database is not covered by ABB's runtime license with Oracle. The delivering organisation must hence have a valid Oracle developer license to not violate the runtime license ABB has with Oracle.
Its also possible that custom stored procedures prevents IM to log PDL events, eg if they are driven by database triggers - triggers execute on behalf of the inserting process and if the trigger throw a bad result it may prevent insertion to the PDL log. If the IM PDL log does not receive any new events I would drop or deactivate any custom added trigger(s) to rule out it being involves/responsible.
If the IM PDL log remains frozen even after removing custom code and reboot I believe its time to ask your regional ABB support center for help.
The most common root cause for an IM to stop logging events is depletion of some Oracle tablespace (eg due to a too small or non-existent Auto-Extend setting or a too large storage setting with respect to the tablespace made available during database configuration).