Tag Query - History 12.0.2

Has anyone run into a problem with using the History mode of a Tag Query?
I am connected to an IP21 data source. I can get HistoryEvent data and Current data back, but when I run in History mode, I get a blank HTML. Running in XML mode, I receive the following back:
<?xml version="1.0" encoding="UTF-8" ?>
<Rowsets DateCreated="2008-02-25T13:17:36" EndDate="2008-02-25T13:17:28" StartDate="2008-02-25T12:17:28" Version="12.0.2 Build(88)" />
I have an 11.5 instance and the same tag and data source does return the expected values, so the problem does not appear to be in the data source.
I am going to initiate a ticket for this.
Thanks,
Mike

Never mind. Turns out it was pointing to incorrectly configured local data server. Configuration fixed and then it works fine.

Similar Messages

Tag Query History mode returning too many rows of data

I am running a Tag Query from HQ to a plant site and want to limit the amount of data that returns to the minimum required to display trends on a chart. The minimum required is subjective, but will be somewhere between 22 and 169 data points for a weeks data. Testing and viewing the result is needed to determine what is an acceptable minimum.
I build a Tag Query with a single tag and set it to History Mode. I set a seven day period going midnight to midnight. And I set the row count to 22. When I execute the query it returns 22 data points. But when I go to visualization, I get 565 datapoints. So obviously that is not what I want as I want a very slim dataset coming back from the IP21 server (to minimize the load on the pipe).
Any suggestions?

Hi Michael,
it looks to me like you have enabled the "Use Screen Resolution" option in your display template or in the applet HTML. Setting this option makes the display template fetch as many rows as there are pixels in the chart area. Like setting a rowcount in the applet HTML as a param, this will override any rowcount limitations you have set at the Query Template level...
Hope this helps,
Sascha

Tag query - Rowcount Property

Hi,
We are using SAP MII 12.1.5 ( build 83).
We have been connecting to a PI historian to get data and performing some calculations.
Since the client gives more important on the accuracy of data, we are using the history event mode.
( With history event , we could not get the results as expected)
While querying a particular tag, the value is not as expected.
After doing all the testing, We found out the For the particular period PI has some where around 18000 rows. and we are only getting 9999 rows since we have specified this in the tag query row count.
In the transaction I tried to increase the rowcount to 20000. It is not working.
The maximum count is 10000. After that the query gives unknown error Java LH exception.
Is there a limitation on the rowcount property?
If we fix the row count for a certain limit and the query returns more than those number of rows, how to get all data?
I am sure handling these huge number of rows is not a very good thing to do. But the algorithm to calculate the end result requires each and every data as registered in PI.
Any input is appreciated.
Thanks in Advance,
Kishore kumar P S

Hi Mike,
We have initially told about the performance issues if we go with this approach.
But once we have shown the demo last week, they agreed with the modified approach.
Now we are using the Statistics with TOT. Still the totalizer value is not taking effect.
As I know from the help docs, the totalizer factor is used to change the from one unit to another unit.
the help Doc says
"The area under the curve (effectively a "totalizer" value) can be calculated by multiplying the time-weighted average by the width of the time interval in seconds. However, quite often, the instrument or measurement is in different units (perhaps gallons per minute versus per second), and the TotalizerFactor parameter can be used to perform the correction."
But there is no effect on the totalizer value. There is one more point in totalizer value is depend upon the connector. We are using the UDC connector. Currently I am not getting anything on this connector type.
Any inputs will be appreciated.
Thanks & Regards,
Kishore kumar P S

Modes and Methods in Tag Query and SQL Query

Hi,
Can someone explain me about the modes available in TAG Query and SQL Query.
TAG Query has modes such as Current, CurrentWrite, GroupList, History, HistoryEvent, ModeList, Statistics and TagList
SQL Query i still have doubt on FixedQuery with output , Modelist and TableList
I also need to know why methods are used?
Thanks in advance
Regards
Muzammil

I'll try to explain to the best of my knowledge :
TagQuery
Current : Gives you the current value of the Tag you are reading.
CurrentWrite : Let you write a Value as the Current Value of the Tag.
GroupList : Generally Tags are grouped under different groups. Returns you the name of the Groups.
From the xMII Help Document :
History : History Mode returns interpolated data. Interpolation can be accomplished by specifying either the # of rows desired or the retrieval resolution. If the mode is "History" and a value is provided for the Resolution parameter (which is in seconds), the connector will retrieve evenly-spaced values starting at the beginning of the time interval, up to the maximum # of rows specified in the RowCount parameter. If no value is provided for the Resolution parameter, the connector will return an evenly-spaced number of values based on the value of the RowCount parameter.
For example, if the time interval is 1 hour, Resolution is 15, and RowCount is 240, the connector will return evenly spaced values each 15 seconds, up to 240 values (which would span the entire hour).
If the time interval is 1 hour, Resolution is not provided or is set to zero, and RowCount is 120, the connector would return 120 evenly spaced values, at an effective interval of 30 seconds.
HistoryEvent Mode : The connector can provide historical values "as they were stored" the database. This mode provides no interpolation of values.
Statistics Mode : When retrieving data for statistical calculations, the connector utilizes the same techniques as in the "HistoryEvent" mode. It is important to note that the first two returning columns in the HistoryEvent query must be the timestamp and the value, in that order. The SAP xMII Statistical processor expects that order, or errors will occur. This ensures precision of statistical measurements, particularly time-weighted average, by using the exact storage time and values from the historical database. The SAP xMII system provides the statistical calculations.
Modelist : Basically returns the modes of the Query Available. The Data returned is same as the data in the Modes list in the Quert Template Editor.
Taglist : Returns all the Tags in the Datasource.
SQL Query
Modelist : Same as above.
TableList : List of all the tables in the database to which the connector connects.
Again from SAP xMII Help Documentation :
FixedQueryWithOutput : This mode is used to execute an Oracle stored procedure or function that returns a REF CURSOR as output. The position of the REF CURSOR is marked by a "?" in the query. For example:
Create a table.
create table usage (id int, name varchar(50));
insert into usage (id, name) values (1, 'test1');
insert into usage (id, name) values (2, 'test2');
insert into usage (id, name) values (3, 'test3');
insert into usage (id, name) values (4, 'test4');
insert into usage (id, name) values (5, 'test5');
insert into usage (id, name) values (6, 'test6');
insert into usage (id, name) values (7, 'test7');
insert into usage (id, name) values (8, 'test8');
Define the stored procedure.
DROP PACKAGE foopkg;
CREATE PACKAGE foopkg IS
TYPE cursortype is ref cursor;
PROCEDURE test (mycursor in out cursortype);
END foopkg;
CREATE PACKAGE BODY foopkg IS
PROCEDURE test (mycursor in out cursortype) AS
BEGIN
open mycursor for select * from usage;
END;
END foopkg;

Define a query template for calling the stored procedure. Enter the following in the FixedQuery tab:
call foopkg.test(?)
This template returns all rows from the Usage table.

Current Tag Query

Newbie Tag query questions, two questions in one here -
1) We are able to pull multiple tags within a history query, but when we try a Current query it only pulls back one tag. Why doesnt it return the other tags within the Current?
2) We have been seeing odd error message occasionally, "SQLGetData: Conversion Character to Timestamp.". We thought it was the DateTime config but that is set up correctly.
Any thoughts?

Brian - glad to see you made it back from AT&T park in one piece...
1) Is this just any pair of tags, or just certain combinations?
2) Does your ODBC System DSN have any of the advanced settings checked besides Read-Only? (specifically the Timestamp sent as Character one).
1/2) Are any of your tag meta queries failing when it sends the initial request for description and scaling ranges, etc?
Regards,
Jeremy

SAP MII 14.0 Tag Query Findings

Hi Everyone,
We has just migrated from 12.2 to 14.0 MII, we did not got any issue in BLS or any Queries. The only issue we faced was the tag Query. So, after migrating from 12.2 to 14.0 we need to re load the Tag query and save it after migration to 14.0 otherwise it will not work as expected.
Am sharing as many of us may be working for Migration of MII 12.2 to 14.0, this may be useful.

Where are you querying the data from?
For example, if you're reading tags from an OSISOFT PI Historian, the "mask" attribute should be tag='AB*'
Note the single quotes!
The mask value in PCo queries is dependent on the "source" system masking procedure and format.

How to pass 100+ tags in a single sql/tag query

In my current application I have to pass 180+ tags in a single query to retrieve data from iHistorian.
I want to know how to pass more thatn 100 tags in a single SQL or TAG Query using OLEDB or UDC connectors.
If anybody has done it in the past ,please share with me and also let me know how to do it

Currently you can only query a maximum of 128 tags, this is a hard limit and may be changed in future releases of xMII, but < 11.5 (im fairly sure 12 also) all have the limit of 128.
As for iHistorian with the OLEDB UDS, you can write a query that would return over 128 queries becasue this is an input limitation on the UDSs. (PLEASE DON"T ASK US HOW TO WRITE iHistorian QUERIES... we aren't experts in iHistorian).
Please note that though you can query over 128 tags, the performance may not be what you expect... This may take a very long time to return.
Martin

Tag Query error when assigning mode in Link Editor

Hi,
I am receiving the following error when I run a transaction that contains a Tag query. In my transaction I have set the tag query mode to be defined by a local property via the link editor. Then when I execute the transaction I get the following error:
"[ERROR] [TAG_QUERY_WRITE_TAG]com.sap.xmii.Illuminator.logging.LHException: Mode parameter was not found or is malformed"
I am on version 12.1.8 Build(43).
I import the project into MII 12.1.4 Build(53) and the transaction works as expected.
In the new verson of MII is there a bug utilizing the link editor to set mode? Or is there a specific way it wants the mode linked. (e.g. specific case)
Additional details:
I am trying to use the CurrentWrite mode. I have tried setting Current mode via the link editor and that isn't working either.
Any suggestions?
Thanks,
Justin

Hi Mike,
Please correct me if I understand the logic incorrectly. But here is what I am thinking....
I have configured my transaction to have this flow:
String_List_To_XML_Sequence --> Repeater_TagValues --> TAG_QUERY_WRITE_TAG
The String_List_To_XML_Sequence would contain String_List_To_XML_Parser_TagValues & String_List_To_XML_Parser_TagNames.
With this flow the logic would say that I will be running a seperate tag query for each tag value. So if I have 100 tag values that I want to send, I will run 100 tag queries. This doesn't seem the most efficient. Also if this is how you were thinking I would configure the transaction then I could use the following links:
Target Xpath: TAG_QUERY_WRITE_TAG.TagValue.1
Expression: String_List_To_XML_Parser_TagValues.Output{/Rowsets/Rowset/Row[#Repeater_TagInput.CurrentItem#]/Item}
Target Xpath: TAG_QUERY_WRITE_TAG.TagName.1
Expression: String_List_To_XML_Parser_TagNames.Output{/Rowsets/Rowset/Row[#Repeater_TagInput.CurrentItem#]/Item}
With this configuration updating 10 tags takes 2 seconds:
[INFO] Statistics [Load = 35 ms msec, Parse = 35 ms, Execution = 2015 ms, Total = 2067 ms]
With my old configuration updating 10 tags took 700 ms. (original transaction on 12.1.4 Build (53)
[INFO] Statistics [Load = 11.137 msec, Parse = 224.113 msec, Execution = 451.78 msec, Total = 736.62 msec]
Please let me know if I interpreted your thoughts incorrectly.
If there is a way to utilize only 1 Tag Query, then I am not sure how the transaction flow should be configured.
Thanks for your time,
Justin
Edited by: Justin M Brown on Jul 14, 2011 7:29 PM
Edited by: Justin M Brown on Jul 14, 2011 7:33 PM

Dynamic Tag Query with dynamic tag name.

Hi,
In our implementation we have 10+ users. Each one want to monitor only one production line ( eg. one tag value ) in the dashboard by default when they login.
I was able to design this requirement CONCEPTUALLY but facing some trouble technically.
Here is my issue.
Tagname will be coming from one of the BLS Transaction input parameters (Transaction.Tagname). I am able to build tag query using xMII Tag Query block, able to configure repeater. Here is the spot where I was struck. While assigning tag value to XML Row
i.e IlluminatorRow_0.Tagvalue = Repeater_0.Output{/Row/AssetUtil1}.
In the above assignment link it requires a hardcoded tagname. In my case it will be dynamic. I tried different ways like
1. IlluminatorRow_0.Tagvalue = Repeater_0.Output{/Row/@Transaction.Tagname}.
2.IlluminatorRow_0.Tagvalue = Repeater_0.Output{/@Transaction.Tagname}.
But no luck.
Can someone help in how to do this dynamic tagname assignment.
Thanks,
Srinivasa.

Hi Srinivas,
another option is to use "Dynamic Links" which from your sample code is what you were trying to do. For this, the proper syntax is:
Repeater_0.Output{/Row/#Transaction.Tagname#}
Make sure that the tag name you pass to the historian is the same as the tag name returned by the historian as part of the data set, and make adjustments for that. For example, some historians escape non-alphanumeric characters when they process your request (e.g. passing "abc.def 12-rt" as the tag name can be returned from the historian as "ABC.DEF_12_RT", etc.).
Hope this helps,
Sascha

Tag Query Error

Hi,
I am executing a tag query and I keep getting the following error -
OperationList [ERROR] - Error Message: Pending requests found, current request will be retried at a later date
OperationList [ERROR] - Error updating
com.sap.xmii.applet.common.ResultModelException: Error Message: Pending requests found, current request will be retried at a later date
 at com.sap.xmii.applet.common.BaseApplet.getResultModel(BaseApplet.java:1089)
Can somebody explain what would be the cause of such an error and how to fix it?
Regards,
Chanti.

Actually, they have to be run in isolation because I can't load both projects in the OPC server at the same time. So, I can run the related MII applications only one at a time. But heres something I found in the UDS logs -
[P:4192, T:5000, UDS, ] 0x0 HRESULT: 0x80070057 [Invalid at the top level of the document.
] [Connection.cpp @ 1024, CLHOpcDaConnection::FinalGetMetadata]
[P:4192, T:5000, UDS, RETHROW] 0x0 Rethrowing exception. [Connection.cpp @ 1130, CLHOpcDaConnection::FinalGetMetadata]
[P:4192, T:5000, UDS, RETHROW] 0x0 Rethrowing exception over COM. [tagUtil/lhds2Connection.h @ 1427, lhds::LHDSConnectionImpl<class CLHOpcDaConnection>::GetMetadata]
[P:4192, T:5000, UDS, ] 0x0 Caught exception over a COM boundry. [tagUtil/lhds2NamespaceMode.h @ 174, lhds::LHDSTagListModeImpl<class CLHOpcDaDSTagList>::LookUpDescription]
[P:4192, T:5000, UDS, HANDLED] 0x0 Handled exception. [tagUtil/lhds2NamespaceMode.h @ 177, lhds::LHDSTagListModeImpl<class CLHOpcDaDSTagList>::LookUpDescription]
Does it make sense?

Error using a tag query

We have a tag query that works in our sandbox environment, but not in dev. I loaded the same JDBC drivers on both systems.
The project was exported from the sandbox, and imported into dev.
I have verified the Data Server set up is identical in both environments. Connection status in both environments is identical - running, same number of connections, etc.
When I try to run the query on sandbox in workbench, the query returns data. I get this error on the dev system -
SQL error has occurred on query java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Invalid object name 'tag'.
Detailed error -
java.lang.Exception: SQL error has occurred on query [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Invalid object name 'publicgrouptag'.
     at com.sap.xmii.Illuminator.gui.workbench.populators.IlluminatorPopulator.get(IlluminatorPopulator.java:114)
     at com.sap.xmii.Illuminator.gui.workbench.populators.TagListPopulator.get(TagListPopulator.java:47)
     at com.sap.xmii.Illuminator.gui.workbench.components.desktop.custom.TagQueryBuilderPanel$6.construct(TagQueryBuilderPanel.java:723)
     at com.sap.lhcommon.gui.ThreadCreator$2.run(ThreadCreator.java:94)
     at java.lang.Thread.run(Unknown Source)
Any suggestions??

One of your included JDBC driver archives has a class that matches the path provided by the JDBCDriver setting for the data server (likely the sqljdbc.jar file).
If you take the JDBCDriver setting:
com.microsoft.sqlserver.jdbc.SQLServerDriver
and replace the periods for sub directories and add a .class on the end you'll have:
com\microsoft\sqlserver\jdbc\SQLServerDriver.class
So if you unpacked the jar file you'd find this java class (and the other ones included with the driver).
Do you get the same error about 'publicgrouptag' and 'tag' objects when you test a tag query request for GroupList mode? These tables/views would be used by the underlying queries used to populate the tag details tab in the WB. Do you see these tables or view within the SQL Server? Does the sa user have appropriate permissions?

MII 11.5 and PCo 2.1 and Tag Query Error

Hi,
I have KEPWare OPC server configured with a single tag, and with the OPC Client open. I have PCo 2.1 configured with a single agent, and 'legacy' ticked with port 9001. I have a UDS connector pointing to port 9001, and a tag query in 'currentwrite' mode, and can successfully write a value from the query editor (within MII 11.5) to KEPWare, when tested directly within the MII query editor.
However, when I call the same tag query from within an MII transaction, and set 'TagName.1' and 'TagValue.1' to the values I want, I get the following error:
"An item with the same key has already been added. at SAP.Manufacturing.Connectivity.Protocol.Custom.PCoQueryRequestHandler.ProcessRequest(Object handler)"
I see this error in the PCo log.
Interesting thing is, that within the transaction editor, when I select the underlying tag query, and the editor asks to generate the XML, and I say Yes, the underlying tag query runs fine (I can see the value getting updated within KEPWare).
I've also tried with/without subscription items in PCo, plus different settings for 'Cache Mode' in PCo, plus using fully qualified tag name (ie: channel.device.tag as KEPWare sees it), etc, but in all cases I get the above error.
Any ideas?

Hi Diana,
I upgraded to PCo V2.1.4.2, still same issue. And yes, the data server (UDC) is checked as "Writable"!!
As mentioned, the tag query runs fine in both "Current" mode and "CurrentWrite" mode. Only when I call the same query from a transaction do I see this error. Excerpt from Runner Log below;
2011-02-23 15:20:32,390 [ServletExec: request: time=1298434832343, uri=/Lighthammer/Runner]
ERROR Runner - [9FA68944-67CE-824D-3FA6-D96023119ECE][ERROR]:
IlluminatorQuery: An item with the same key has already been added. TMP0794C967-0F69-8F04-568C-CD037815D1D0
2011-02-23 15:20:32,453 [ServletExec: request: time=1298434832343, uri=/Lighthammer/Runner]
ERROR Runner - [9FA68944-67CE-824D-3FA6-D96023119ECE][ERROR]:
ACTION FAILED: End Action IllumTagQuery_0 : () TMP0794C967-0F69-8F04-568C-CD037815D1D0
If I leave the transaction Tag Query action (that calls the underlying tag query) without any assignment to TagValue.1, then there is no error, and the error as set in the aunderlying tag query is used. But as soon as I assign values to TagValue.1 inside the transaction, I get the error. I've tried passing a value via a local paramater etc, same issue.
Regards
Kevin.

Link Tag Query to SQL Query

I have tag values that are steps or alarm codes in a process and I want to create a cross reference SQL table for these values. Using BLS, how do you link these tables to have an Xacute query that will return the cross referenced values from the tag?
I appreciate any help that can be provided.
Thanks
Larry

Rick,
One other note I missed in my last e-mail, the Tag Query does not return the TagName as a value in a column but as the column header for the value of the tag. How is it possible to get this as the value of its own column to be used as a link in the Joiner action.
Current query returns
DateTime                              XV43003     -
(header row)
03/22/2007 03:30:00                     0
03/22/2007 03:31:00                     2
03/22/2007 03:32:00                     8
Preferred method
DateTime                              TagName         Value     -
(header row)
03/22/2007 03:30:00              XV43003              0
03/22/2007 03:31:00              XV43003              2
03/22/2007 03:32:00              XV43003              8
This would give me both the tagname and value to join to the sql table.
Thanks for your help!
Larry

String Tag Types + History Mode - xMII 12.0.1

Hi all,
I'm really newbie in Tags but i'm with the following problem:
I'm trying to access value from a specified data range in a Tag that returns just string to me, but I can't use the HistoryEvent Mode like I was doing for Tag Queries that return me number, I would like to know how to retrieve "non-current" string data from a Tag Query.
Thanks in advance.
Pedro Sena
www.neoris.com

Sam, is this that you are looking for? :
Connector InSQL
ConnectorID
ConnectorType TAG
DatePrefix '
DateSuffix '
DaysRetention 7
Description ---
Enabled T
InternalDateFormat MM-dd-yyyy HH:mm:ss
JDBCDriver com.inet.tds.TdsDriver
MaxRetryCount 5
Name Alicorp_InSQL
PoolMax 100
PoolSize 1
RetryInterval 60000
ServerPackage com.sap.xmii.Illuminator.connectors.InSQL
ServerURL jdbc:inetdae:aliargsql1:1433?database=Runtime&sql7=true
Timeout 15
UseCount 256
UseOLEDB true
UserName wwAdmin
ValidationQuery SELECT GETDATE()
WaitTime 30
Tnx

Writing a Tag query

Hi all,
I need to write complex select statements on Tag database.
Can anyone please let me know how and where in query template to write.
Thanks
Ravi Kumar.

Once setting up the UDS connection as above, you'll need to connect your datasource to the exposed port of the UDS using a "OLEDB Connector", port must match that of the SAP UDS.
from there you can simply drop a PI tag query into the query template to extract data.
SELECT "tag", "time", "_index", "value", "status", "questionable", "substituted", "annotated", "annotations" FROM "piarchive".."picomp2" WHERE tag = 'sinusoid' AND time BETWEEN '-1h' AND ''

Tag Query - History 12.0.2

Similar Messages

Maybe you are looking for