Hello,
About 4 (May) months ago we upgraded our DeltaV Software.
For some reason, I cannot get all (the past 7 years) of the Event Chronicle data before the the updragde. I can only view Event Chronicle data since April 2014.
Is there anyway I see this data?
Thanks
You can only view event chronicle data from one archive at a time. In order to view another archive, you must select from the top menu in Process History View:
Events-->Configure Events...
Then select the Events Data host and Event Chronicle Archive you are interested in from the drop down. The event chronicle time spans are listed so you can narrow down which one you are interested in by time range.
For this reason, it is important to assess a proper sizing/duration of your active chronicle so that data from within the last year (for example) can be easily accessed. Having a lot of data in the active may reduce performance.
In reply to Youssef.El-Bahtimy:
Youssef.El-Bahtimy said: Events-->Configure Events... Then select the Events Data host and Event Chronicle Archive you are interested in from the drop down. The event chronicle time spans are listed so you can narrow down which one you are interested in by time range. For this reason, it is important to assess a proper sizing/duration of your active chronicle so that data from within the last year (for example) can be easily accessed. Having a lot of data in the active may reduce performance.
Thank you Youssef
When I follow the steps above, the latest Event Chronicle Archive I can view is from April 2014 to Today. I do not see an archive from before April.
In reply to DCS Newbie:
HI,
did you "upgrade" the old event chronicle from the old files -> mbd to sql ?
and import it to the new project..
There are the instructions in the upgrade files
Niklas Flykt
Klinkmann Oy
Key Account Manager safety products
nikfly@gmail.com
In reply to Niklas Flykt:
here is a instrustion from kba:s
Here is the procedure in migrating the ejournal.mdb to v11.3.1.
1. Run the EJMigration.exe utility located under C:\DeltaV\bin of a v11.3.1 machine.
2. Browse for the Ejournal.mdb file.
3. The name of the node in which the database originally resided must be entered for migration to take place.
4. Migrated files will be located under D:\DeltaV\DVData\CHRONICLE\MigratedDatabases.
5. From Event Chronicle Administration, the migrated EJournal will be shown as an extended dataset and may be viewed via Process History View by configuring the events to point to that extended dataset created.
If the migration is performed on the Alarms and Events server node, the migrated EJournal will automatically be added on the Event Chronicle database as extended dataset. This can be checked from the Event Chronicle Administration tool. If the procedure is performed on another node and you would like to add the migrated database to the Event Chronicle database of the Alarms and Events server, select ‘Create Extended Dataset’ from the Event Chronicle Administration tool and browse on the directory where the migrated database is located.
After the dataset is available in the Event Chronicle Administration tool, the events can be viewed in Process History View by opening a new event and then selecting Events menu and then ‘Configure Events’. From the Configure Events window, select the migrated EJournal dataset which is now an extended dataset.
Thank you Niklas for the help,
There is one computer (logins via RTS) on our network that can access the past Event Chronicle archives before the upgrade. All other stations including Ops stations and Proplus can not view pass history. This person has admin rights.
Are all users and terminals connecting to the same event chronicle node? check this through the menu I mentioned in my first response.
By default, process history view attempts to connect to the localhost. Additionally, the default node is a user profile based setting and has to be set for each user on each terminal they might use. I wrote an article on streamlining this a few years back.
The statement, 'All other.... can not view...' ; do you mean the enumeration of all available chronicle database archives are not visible or when you try to select one it throws an access denied error?
Hi,
Youssef makes a good point there, maybe the problem is that simple ?
Usually if you have event server and you havve choosen the wrong input you will get the message cannot connect ot server...
Thank you Youssef,
I mean that everyone except the one user (with admin rights) can not see the archives past April 2014. For instance, I can only see from April 2014 til today.
Thanks, I will try what you mentioned above when return from lunch.
I have seen in the past where batch historian archives are created such that non-administrators are not assigned read access in SQL, but I would imagine that if a similar thing happened during migration to the event chronicle archives, an error would have been generated.
It is possible they have multiple event chronicles, and that each terminal is routing to a different one at present (perhaps because users independently selected one or another when facing the error that the client couldn't connect).
Worst case, you may need to use SQL Server Management Studio to see if there are security differences between the different archive databases. I'll go into this furher if need be.
Then it´s time or the swap_user_roles script :p
Youssef.El-Bahtimy said: Are all users and terminals connecting to the same event chronicle node? check this through the menu I mentioned in my first response. By default, process history view attempts to connect to the localhost. Additionally, the default node is a user profile based setting and has to be set for each user on each terminal they might use. I wrote an article on streamlining this a few years back.
Thanks for the help.
In Configure Event Chronicle---->Events Data, I see defaulthost, local host, and Pro+.
If I select defaulthost, I see EJourmal from april 2014 to today.
If I select localhost, I get error message saying Data Server does not exist or Dataset name does not match any names from current Data Server.
Where is your event chronicle located? Based on your description it sounds like the Pro+, because PHV can enumerate all known event chronicles. If you look in DeltaV explorer under the Alarms and Events field of each workstation or application station node, you can see which are enabled as event chronicles. If there are more enabled than you can see in the PHV list, then the chronicles may not have been downloaded and are not working.
Obviously, localhost will only work if the workstation where you launch PHV is also a chronicle.
Defaulthost is tricky. It represents what you as a user has selected for the client workstation as your default chronicle. The default chronicle is used for event charts by default. It is user-profile based, and could potentially vary for each user on each workstation. The "default" default chronicle is localhost, I believe.
Now for testing, lets do the following:
1. **Non-Admin** user should log in to Windows and DeltaV on a workstation.
2. Open PHV and select File-->Set Default Data Servers
3. Under Event Chronicle, Select Pro+ for the Events Data Server. Ensure 'save as my Application Startup Data Server' is checked.
4. Open a new Event file, File-->New-->Event.
5. Select Events-->Configure Events.
6. In the Configure Event Chronicle dialog, see if the Events drop down contains any current datasets.
If you don't see current data sets, repeat this process for the admin user. If he DOES see extra chronicles, then as I said, it would seem to be a permissions issue on the current data sets in SQL.