I am trying to use echart widget for wirecloud display. The logic of the wiring is:
quantumleapsource -->quantumleap 2 echart --> echart.
I keeping the two errors below:
1. Error getting Historical Data (422): {"description":"The parameter value '1637496000000' for parameter **fromDate** or **toDate** is not valid.","error":"<class 'exceptions.exceptions.InvalidParameterValue'>"}
2. Error creating subscription in the context broker server: Connection Error
I have tried different date formats like: 2021-11-21T12:00:00Z , 2021-11-21T16:00:44.600+00:00 , 2021-11-16T16:00:44.600. But the error persists.
What could be wrong? Or How can use echart in wirecloud?
The issue with the historical data(422) has already been dealt with in https://github.com/Ficodes/quantumleap-source-operator/pull/19
The subscription error is solved by ensuring the context broker and NGSI proxy is up and running. Also key in the correct IP addresses.
Related
I am developing a PDI transformation, which takes data from a MySql database, and output the data into an MSSQL table. But before output, I add a deletion step to delete records in dest. table with same key field values. But I do not know why that by this setting the transformation always fails casting exception of connection timeout of data source.
But, after I added a "Block" step between "table input" and "Delete", the issue got gone, and the transformation got successfully finished.
My configuration and exception message are as blow:
Transformation setting and system exception message
Data Input SQL, and Delete condition
Error what I see from the screen-shot you attached and also recommendation in the 4th error line from top "consider raising value of 'net_write_timeout' on the server"
Default value will be 60, Kindly increase the value for the same.
Follow below document for more reference.
https://wiki.pentaho.com/display/EAI/MySQL
We are performing HA InnoDb in Mysql. For that we need 3 instance to perform failover.
While running this query in msql-js we got an error of invalid object member.
Query - dba.deploySandboxInstance(3310);
Error - Invalid object member deploySanboxInstance (AttributeError)
The error message is clear: Invalid object member deploySanboxInstance (AttributeError)
The function is named "deploySandboxInstance".
Note that sandboxes are not suitable for production environments and should be used for testing purposes only.
Please read the user guide as it contains all the information you're looking for:
https://dev.mysql.com/doc/refman/8.0/en/mysql-innodb-cluster-userguide.html
I have an ssis package which uses SQL command to get data from Progress database. Every time I execute the query, it throws this specific error:
ERROR [HY000] [DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEDGE]Internal error -1 (buffer too small for generated record) in SQL from subsystem RECORD SERVICES function recPutLONG called from sts_srtt_t:::add_row on (ttbl# 4, len/maxlen/reqlen = 33/32/33) for . Save log for Progress technical support.
I am running the following query:
Select max(ROWID) as maxRowID from TableA
GROUP BY ColumnA,ColumnB,ColumnC,ColumnD
I've had the same error.
After change startup-parameter -SQLTempStorePageSize and -SQLTempStoreBuff to 24 and 3000 respectively the problem was solved.
I think, for you the values must be changed to 40 and 20000.
You can find more information here. The name of the parameter in that article was a bit different than in my Database, it depends on the Progress-version witch is used.
I'm trying get logs created by DMS.
I read DMS documents, and successfully captured DMS's SQL logging like following:
2017-02-17T00:58:29 [TARGET_APPLY ]D: Construct statement execute internal: 'UPDATE `some_schema`.`typical_usr_master` SET `id`=? WHERE `id`=? AND `start_dt`=? ''(ar_odbc_stmt.c:3323)
However this log doesn't have original binding values, for example id or start_dt.
If they are revealed, values would be like id = "00000001", start_dt = "2017-02-17".
Do we have any chance to see such bind values on DMS logging ?
Currently, I changed all logging level to DEBUG, but only ERROR logging shows such binding values.
I received an answer from AWS support.
How to reveal DMS SQL query logging with binding values ?
Unfortunately, we do not expose bind values in logs because of security concerns.
Normally, we recommend customers to look at their target to get the actual data
values we migrated.
I'm happy if there was a way to check data integrity.
I am using Hibernate3 with spring application.
I introduced a column in my existing table with many to one relationship with the addition in the .hbm file as mentioned below:
<many-to-one name="qualityStatus" column="quality_status"
class="model.PurchaseStatus" lazy="false" fetch="join"/>
The corresponding object to this hbm has a property of type 'PurchaseStatus' and field name as 'qualityStatus'.
Now when i try fetching the data from the table representing the above object with the query:
List<Long> dnIds = session.createQuery("select dnItem.dnId from DeliveryNoteItem dnItem where dnItem.qualityStatus!=? and dnItem.qualityStatus!=? and dnItem.qualityStatus!=?")
.setInteger(0,1)
.setInteger(1,5)
.setInteger(2,7)
.list();
i get an error saying as 'java.sql.Exception: Unknown column 'deliveryno0_.quality_status' in 'where clause'
I get this error when deployed on test server but when i check the same thing on my local server i works fine as well when i just run this query directly on the database on the test server it returns me result. So it confirms that the database on the test server is alright. It is only when it executes through the application on the test server i am getting this error.
Can anybody let me know what can be the reason or how do i debug this out.
Thanks in advance. Looking forward for replies.
If you really have a quality_status column in your database, then you should make sure you have the most recent version of your application deployed on the test server, and make sure that the connection url of hibernate really points to the test database.
This is not a hibernate problem, not a programming one. It is environmental - check your configurations and redeploy.