MemSQL select query 1705 error - singlestore

I am using memsql community version and I am able to execute some queries but getting error for few queries like
select * from policy;
Error code:
ERROR 1705 (HY000): The query cannot be executed.
MemSQL code generation has failed: Failed to delete .fin file.

This likely indicates a permissions problem or some other issue with your installation ([install dir]/plancache may not be writable by memsqld for example). Did you install and start MemSQL via Ops?
There will probably be a more detailed error message inside of
[install dir]/tracelogs/memsql.log

Related

npm oracledb logging and tracing

My goal is to enable logging and tracing for the oracle database using the oracle client and npm package oracledb so that I can check when the query was started and when results were returned or if the query was timed out.
More precisely I want to check if it's the oracle client which is taking the time or if there is something wrong with the oracledb package.
I want to check logs for any errors and want to trace slow queries or queries for which a timeout error has occurred or any deadlock that occurs.
So far I'm successfully able to enable logging and tracing for the oracle database client and it's working only when I use sqlplus CLI but when it comes to the oracledb npm package it's not working.
I have created sqlnet.ora in $ORACLE_HOME/network/admin directory, and then pasted this content to enable logging and tracing for oracle-client.
LOG_DIRECTORY_CLIENT=C:\Oracle\instantclient_21_3\network\admin\cl-log
LOG_DIRECTORY_SERVER=C:\Oracle\instantclient_21_3\network\admin\srv-log
LOG_FILE_CLIENT=client
LOG_FILE_SERVER=svr.log
TRACE_LEVEL_CLIENT=ADMIN
DIAG_ADR_ENABLED=ON
ADR_BASE=C:\Oracle\instantclient_21_3\network\admin\log-adr
And as far as the implementation of oracledb with NodeJs is concerned I create connection pools using oracledb.createPool({...config}) and then when I need to query into DB I use oracledb.getPool('poolName').execute(query).
To me, the error is that it creates random .trc files and does not put logs to the sqlnet.log file only when using the oraceldb npm package.

frequent restart of Solr required. Otherwise user gets 500 error - no available shards for solr query?

Using Solr 6 with Alfresco 6.2.2. Solr needs to be restarted otherwise an error is generated. The User gets a message like: framework.exception.ApiDefault, statusCode: 500 checking into the Alfresco logs, I find a corresponding error message:
ERROR: org.alfresco.rest.api.search.SearchApiWebscript : org.alfresco.repo.search.impl.solr.SolrQueryHttpClient.executeQuery(...)
on the next line also see this error with the same timestamp:
ERROR: org.alfresco.repo.search.impl.solr.SolrClientUtil: No available shards for solr query of store workspace://SpacesStore - trying non-dynamic configuration
Our solr index is not sharded. Does anyone know what this means? Any ideas how to fix the error? A restart of Solr is a short term solution.
****** additional comments ******
not finding a directly correlated error message in the solr log, like with corresponding timestamp and logid. What I do find is the following error message:
WARN (SolrTrackingPool-archive-SpacesStore-0-ContentTracker-6) [ ] o.a.s.t.AbstractWorkerRunnable Index tracking batch hit an unrecoverable error
org.alfresco.error.AlfrescoRuntimeException: 11148343 GetTextContentResponse return status is 500
at org.alfresco.solr.client.SOLRAPIClient.getTextContent(SOLRAPIClient.java:1119)
at org.alfresco.solr.SolrInformationServer.addContentPropertyToDocUsingAlfrescoRepository(SolrInformationServer.java:3387)
at org.alfresco.solr.SolrInformationServer.addContentToDoc(SolrInformationServer.java:3374)
at org.alfresco.solr.SolrInformationServer.updateContentToIndexAndCache(SolrInformationServer.java:3306)
at org.alfresco.solr.tracker.ContentTracker$ContentIndexWorkerRunnable.doWork(ContentTracker.java:154)
at org.alfresco.solr.tracker.AbstractWorkerRunnable.run(AbstractWorkerRunnable.java:45)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Does this error message mean anything?
using ACS 6.2.2, Solr 6, Search Services 1.4.3, solr spec 6.6.5. Solr has its own two node cluster. ACS also has it's own two node cluster.
The issue seems to happen everyday. When the issue happens, the user gets an error message when they try to search. The error message says it's a 500 error, framework.exception.ApiDefault.

SQL Server Agent fails when using sp_send_dbmail to execute a stored procedure containing a linked server

Starting July 1st, 2021, SQL Server Agent fails when using sp_send_dbmail to execute a stored procedure containing a linked server. If I remove the linked server portion of the code from the stored procedure the job runs successfully.
The job simply executes the following SQL statement:
EXECUTE msdb.dbo.sp_send_dbmail
#recipients = 'My.Name#MyEmailAddress',
#subject = 'Daily Security Check',
#query = 'EXECUTE MyDatabase.sec.pr_LinkedServerQuery',
#attach_query_result_as_file = 1
I can successfully run this code manually from a query window while logged on as the Agent. But if I R-click the job and select “Start job at step…” the agent job fails. Also, if I edit the job by removing the dbmail procedure and simply run EXECUTE MyDatabase.sec.pr_LinkedServerQuery the agent job is successful. It is only when nested inside the dbmail procedure that it fails. This job has previously run successfully for over a year.
I am using SQL Server 2017.
The logs show an error about sp_send_dbmail but searches on this error don’t seem to reflect the issue I am having.
Executed as user: HCI\AgentName. Microsoft (R) SQL Server Execute Package Utility Version 14.0.3381.3 for 64-bit Copyright (C) 2017 Microsoft. All rights reserved. Started: 2:19:52 PM Progress: 2021-07-06 14:19:52.96 Source: {457716A2-22BF-47F5-A08E-8A48A218911F} Executing query "DECLARE #Guid UNIQUEIDENTIFIER EXECUTE msdb..sp...".: 100% complete End Progress Error: 2021-07-06 14:19:53.11 Code: 0xC002F210 Source: Execute T-SQL Statement Task Execute SQL Task Description: Executing the query "EXECUTE msdb.dbo.sp_send_dbmail #recipients = '..." failed with the following error: "Failed to initialize sqlcmd library with error number -2147467259.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. End Error Warning: 2021-07-06 14:19:53.11 Code: 0x80019002 Source: Subplan_1 Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning Progress: 2021-07-06 14:19:53.16 Source: Notify Operator Task Executing query "EXECUTE msdb.dbo.sp_notify_operator #name=N'Andy H...".: 100% complete End Progress DTExec: The package execution returned DTSER_FAILURE (1). Started: 2:19:52 PM Finished: 2:19:54 PM Elapsed: 1.719 seconds. The package execution failed. The step failed
This issue has bested me so far. Thank you for any insight into slaying this beast!
Thank you Ramya Makam for your article.
After I ran the profiler I got a real error:
Linked servers cannot be used under impersonation without a mapping for the impersonated login.
With that it was easy to edit Linked Servers and I am back up and running!

'MSSQL' encountered unexpected exception of type 'InvalidOperationException' with HResult 'x80131509' while opening connection

When I am trying to load a query into a tabular dateset (from a devops docker image) I will get the following error:
raise DatasetValidationError(error_message + '\n' + str(e), e)
azureml.data.dataset_error_handling.DatasetValidationError: Cannot load any data from the datastore using the SQL query "<azureml.data.datapath.DataPath object at 0x>". Please make sure the datastore and query is correct.
Error Code: ScriptExecution.DatabaseConnection.Unexpected
Failed Step: 9ad57100-4870-49d2-a32f-1c9c15c244e0
Error Message: ScriptExecutionException was caused by DatabaseConnectionException.
DatabaseConnectionException was caused by UnexpectedException.
'MSSQL' encountered unexpected exception of type 'InvalidOperationException' with HResult 'x80131509' while opening connection.
Internal connection fatal error.
I believe that I have allowed the connection in firewall (I might not have done it quite right).
I don't get the error when I am running it from the notebook (on the compute instance).
Is the code that is running on the compute instance the exact same as the docker image? If so, it's likely that the firewall is causing connectivity issues. One way of checking this is to (be cautious) disable the firewall and see if the connectivity issue is gone.
If you're comfortable sharing the firewall/network configurations, that will also help troubleshoot this.

Database Operation Failed: Azure SQL and Azure Data Factory

Database operation failed on server 'worker.database.windows.net,11146' with SQL Error Number '40197'. Error message from database execution : The service has encountered an error processing your request. Please try again. Error code 4815.
A severe error occurred on the current command. The results, if any, should be discarded..
I'm getting the following error. What does error code 4815 mean? Couldn't find any documentation regarding that error code.
The error 4815 means that the SQL Server engine received an invalid column length from the bcp client for colid. You might want to check the parameters again and try this task again.
Here is some documentation on the error codes. Hope this helps.
https://technet.microsoft.com/en-us/library/cc645613(v=sql.105).aspx

Resources