I have configured the testlink on my local machine. Everything is working fine expect while selecting "Requirements based Report" from "Result" menu it showing the following DB Access Error.
DB Access Error - debug_print_backtrace() OUTPUT START
==============================================================================
#0 database->exec_query(SELECT id FROM xp_executions WHERE tcversion_id=(SELECT id FROM xp_nodes_hierarchy WHERE parent_id='0') ORDER BY id DESC LIMIT 0,1, -1) called at [D:\wamp\www\testlink\lib\functions\database.class.php:535]
#1 database->fetchRowsIntoMap(SELECT id FROM xp_executions WHERE tcversion_id=(SELECT id FROM xp_nodes_hierarchy WHERE parent_id='0') ORDER BY id DESC LIMIT 0,1, id, 1) called at [D:\wamp\www\testlink\lib\results\resultsReqs.php:103]
==============================================================================
I have searched on google regarding DB Access Error - debug_print_backtrace() OUTPUT START error but didn't found any solution on it.
My primary question is what is debug_print_backtrace() error and why its coming? and second is how can I remove it?
Related
I was able to implement a connection from R through RMariaDB and DBI to a remote MariaDB-database. However, I am currently encountering a strange change of numbers when querying the database through R. I'll explain the differences:
I inserted one simple entry in my database with the following command:
INSERT INTO respondent ( id, name ) VALUES ( 2388793051, 'testuser' )
When I connect to this database directly on the remote server and execute a statement like this:
SELECT * FROM respondent;
it delivers these value
id: 2388793051, name: testuser
So I should also be able to connect to the database via R and receive the same results. So when I execute the following code in R, I expect to receive this inserted and saved information displayed above:
library(DBI)
library(RMariaDB)
conn <- DBI::dbConnect(drv=RMariaDB::MariaDB(), user="myusername", password="mypassword", host="127.0.0.1", port="1111", dbname="mydbname")
res <- dbGetQuery(conn, "SELECT * FROM respondent")
print(res)
However, the result of this query is the following
id name
-1906174245 testuser
As you can see, the id is now -1906174245 instead of the saved 2388793051 in the database. I don't understand this weird conversion of integers in the id-field. Can someone explain how this problem emerges and how I might solve it?
EDIT: I don't expect this to be a problem, but just to inform you: I am using an SSH tunnel to enable a connection via these specified ports from my local to my remote machine.
SOLUTION: What made the difference was to specify the id of a respondent in the database specification already as BIGINT instead of INT. Thanks to #JonnyCrunch
running apache-drill-1.14.0
tested this query on mysql and got result in 0.02 sec
running the query in drill cli fails with AssertionError
Query:
product_id is BIGINT
SELECT test50.customername, test50.color, test50.age, test50.city,
test50.product_id, test50.price FROM myplugin.sampler.test50 JOIN
myplugin.sampler.test52 ON test50.product_id = test52.product_id WHERE
test50.product_id = 759216 GROUP BY test50.customername, test50.color,
test50.age, test50.city, test50.product_id, test50.price ORDER BY
test50.customername;
Error:
Error: SYSTEM ERROR: AssertionError: Relational expression
rel#873:DrillFilterRel.JDBC.myplugin.ANY([]).
[](input=rel#83:JdbcTableScan.JDBC.myplugin.ANY([]).[](table=[myplugin,
sampler, test50]),condition=OR(=($18, 759216), =($18, 494636))) has
calling-convention JDBC.myplugin but does not implement the required interface
'interface org.apache.calcite.adapter.jdbc.JdbcRel' of that convention
need help if I need some extra configuration ?
Thanks
Could you please check on current master? Looks like it was fixed in DRILL-6850.
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.
The issue is,
a:5:{i:0;s:391:"SQLSTATE[42S02]: Base table or view not found: 1146
Table 'mohchaii_mage828.mgmu_tag_summary' doesn't exist, query was:
SELECT
tag_summary.popularity, tag.* FROM mgmu_tag_summary AS tag_summary
INNER JOIN mgmu_tag AS tag ON tag.tag_id = tag_summary.tag_id AND
tag.status = 1 WHERE (tag_summary.store_id = '1') AND (tag_summary.products
> 0) ORDER BY popularity DESC LIMIT 20";i:1;s:4257:"#0
/home/mohchaiinfusion/public_html/lib/Varien/Db/Statement/Pdo/Mysql.php(110): Zend_Db_Statement_Pdo->_execute(Array)
Any help is appreciated.
Log in to the Magento Admin.
Click System > Index Management.
Select the check box next to each type of indexer to change.
From the Actions list, click the indexing mode.
Click Submit. than working because this error is index management
This type of error basically arises when you are trying to run a query on a table that doesn't exists. So first you need to see whether the particular table is there in the database or not. If it is present flush all the cache and try running all the reindexing.
I have been trying to write an R script to query Impala database. Here is the query to the database:
select columnA, max(columnB) from databaseA.tableA where columnC in (select distinct(columnC) from databaseB.tableB ) group by columnA order by columnA
When I run this query manually (read: outside the Rscript via impala-shell), I am able to get the table contents. However, when the same is tried via the R script, I get the following error:
[1] "HY000 140 [Cloudera][ImpalaODBC] (140) Unsupported query."
[2] "[RODBC] ERROR: Could not SQLExecDirect 'select columnA, max(columnB) from databaseA.tableA where columnC in (select distinct(columnC) from databaseB.tableB ) group by columnA order by columnA'
closing unused RODBC handle 1
Why does the query fail when tried via R? and how do I fix this? Thanks in advance :)
Edit 1:
The connection script looks as below:
library("RODBC");
connection <- odbcConnect("Impala");
query <- "select columnA, max(columnB) from databaseA.tableA where columnC in (select distinct(columnC) from databaseB.tableB ) group by columnA order by columnA";
data <- sqlQuery(connection,query);
You need to install the relevant drivers, please look at the following link
I had the same issue, all i had to do was update the ODBC drivers.
Also if you can update your odbcConnect with the username and password
connection <- odbcConnect("Impala");
to
connection <- odbcConnect("Impala", uid="root", pwd="password")
The RODBC package is quirky: if there's no row updated/deleted in the query execution it will throw an error.
So before using sqlDelete to delete rows, or using sqlUpdate to update values, first check if there's at least one row that will be deleted/updated by querying COUNT(*).
I've had no problem after implementing the check, for Oracle SQL 12g.
An alternative would be to use a staging table for the new batch of data, and use sqlQuery to execute a MERGE command. RODBC won't complaint if there's zero row merged.
This might also be due to an error in your sql query itself. For example, I got this error when I missed an 'in' in the following generalized statement. Example:
stringstuff <- someDT$columnyouwanttouse
somestring <- toString(sprintf("'%s'", stringstuff))
RESULTS <- sqlQuery(con, paste0("select
fling as flam
and toot **in** (",somestring,")
limit 30
;"))
I got the error you did when I left out the 'in', so double check your syntax.
This error message can arise if the table doesn't exist in the database.
A few sensible checks:
Check for typos in the table name in your query
See if you can run the same query on the same database via another sql client
Talk to your data base administrator to confirm that the table does exist
Re-installing the RODBC package did the trick for me!
I had a similar problem. After unnisntalling the R version 4.2.1 and install the R version 4.1.3 the problem was solved.