I hope you are using LOAD DATA INFILE.
Try to use LOAD DATA LOCAL INFILE instead of LOAD DATA INFILE.
Other issue might be this, please visit the following links : MySQL LOAD DATA.
When you login in MySQL do like below,
abdul@xmpp3:~/Desktop/Jiva$ mysql -uroot -p --local-infile
Welcome to the MySQL monitor. Commands end with ; or \g.
No. This hard-coded restriction exists for good reasons related to possible excessive query plan compilation time. You can workaround it by listing the VALUES clauses in a CTE, then INSERTing from the CTE, but I do not recommend it.
Break the INSERT statement up into VALUES clauses of <= 1,000 lines each as a workaround, or use an alternative data ...
State codes and their meaning.
1 'Account is locked out'
2 'User id is not valid'
5 'User id is not valid'
7 'The login being used is disabled'
8 'Incorrect password'
9 'Invalid password'
10 'Related to a SQL login being bound to Windows domain password policy enforcement.
You can cycle the error log by calling sp_cycle_errorlog and then that will close the current error log and cycle the log extensions. Basically, it'll create a new error log file that SQL Server will be hitting. Then the archived error log(s) can be treated accordingly (delete/move with caution). This will not technically "truncate" the log, it'll just ...
I have been banging my head against this error today on OSX Yosemite with MySQL 5.7 recently updated with Homebrew. Following suggestions on StackOverflow and elsewhere, I hunted around after my.cnf files all of which specified bind-address=0.0.0.0. I even removed and reinstalled MySQL following these instructions and then reinstalled using brew install ...
Simply run mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root mysql -p
$ mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root mysql -p
Warning: Unable to load '/usr/share/zoneinfo/iso3166.tab' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.
Warning: Unable to load ...
You created the table in the SYS schema (which you should never, ever do. Really, never).
When you log in as teacher1 any statement looks for objects in that schema. But there is no TEACHER1.INSTRUCTORS table, because the real name is SYS.INSTRUCTORS (did I mention what a bad idea it is to create objects in the SYS schema?).
You need to run select * from ...
There are 3 methods that MySQL can use to write to the binary logs:
This means that every SQL statement on the master is recorded in the log, and executed on the slave. This can cause problems if the SQL statement contains statements such as "NOW()", "RAND()" and anything non-deterministic. This also requires support from the storage engine in ...
Following can be reason for this error
The account which user selected on Server Configuration page window ( during installation) is somehow not able to bring SQL Server database engine services online. Either is lacks privilege or it is corrupted. During installation of database engine services SQL Server tries to bring online database services as a ...
There are 3 different items in this question:
Incomplete startup packet occuring at server start is inconsequential, you may ignore it. Read Incomplete startup packet help needed (in pgsql-general mailing-list) for more.
syntax error at or near "exit" at character 1 means that a client issued exit as if it was an SQL statement.
The could not exec error when ...
Msg 8631, Level 17, State 1, Line xxx
Internal error: Server stack limit has been reached.
Please look for potentially deep nesting in your query, and try to simplify it.
This error occurs with long SET or SELECT variable assignment concatenation lists due to the way SQL Server parses and binds this type of statement - as a nested list of two-input ...
Every time I reboot windows, for some databases comes out this error. (OS Error 21 - Device not ready)
This is due to a disk being offline or not being online either at the time SQL Server started, or had transitioned states after SQL Server has been online.
3.If I restart SQL Server the errors disappears
Yes, because the databases have been remounted ...
This ended up as a case of not being careful when working as root.
I had been researching if SQLCLR on Linux would have access to the app.Config file like it does in Windows (sadly, it does not: SQL Server 2017 on Linux ignores app config file if it exists, or sometimes locks-up if it doesn't (SQLCLR) ) and under certain circumstances SQL Server would ...
'Cannot generate SSPI context' is a generic error. It can be caused by many issues, like an outaded password, clock drift, Active Directory access permissions, failure to register an SPN and so on and so forth.
There is no solution to this problem. The only 'solution' is to investigate the cause, as per KB811889 and/or Troubleshooting Kerberos Errors. ...
You can do this with a function that runs in the security context of its owner.
Function that refreshes the view (create it with the user that owns the MV/table):
CREATE OR REPLACE FUNCTION refresh_mvw1()
REFRESH MATERIALIZED VIEW mvw1 with data;
$$ LANGUAGE plpgsql;
Grant execute on the function to ...
I'd guess the problem is your SQL Server login does not have it's "default database" properly set.
This will show you what your "default database" is set to:
FROM sys.server_principals sp
WHERE sp.name = SUSER_SNAME();
You can either change the default database of your login, or you can specify the database in ...
Check the folowing
First check if another instance is runnig in the same machine
ps ax | grep mysql
Then, check if your file my.cnf (probably in /etc/mysql/ folder) is correctly configured with
datadir = /var/lib/mysql/
socket = /var/lib/mysql/mysql.sock
Next, you have changed the default data directory, did you gave the right permissions to ...
According to Infinite recompile message in the errorlog on the SQL Programmability & API Development Team Blog, this message is triggered when a statement in a batch recompiles 100 times in a row.
This message does not necessarily mean there is a problem; it exists to help troubleshoot statements that might legitimately be recompiling that often (for ...
The rules that SQL Server uses to derive the type of literals are complex, with some odd behaviours that are maintained these days for backward compatibility. For example, the derived type may depend on whether simple parameterization is applied. There are other (undocumented) considerations as well.
With those caveats out of the way, the situation you face ...
Retrieve column from a table with multiple rows in the else part
select case when foo = "bar" then 1 else (select table_name from information_schema.tables) end;
As an example, let's use @foo instead of foo
mysql> select case when @foo = "bar" then 1 else (select table_name from information_schema.tables) end;
ERROR 1242 (21000): Subquery returns more ...
Your problem has to do with mysql.user and the way you upgraded to MySQL 5.6
If you look my answer to Cannot GRANT privileges as root, I show you the description of mysql.user from MySQL 4.1 to MySQL 5.6.
The column plugin is column #41 in mysql.user in MySQL 5.5/5.6
mysql> SELECT column_name,ordinal_position FROM information_schema.columns
You can not select aggregates across a field if you don't include the field in the group by list.
If you want the totals per year you should write
GROUP BY year
If you want the totals per parameterno it should be
GROUP BY parameterno
From the error ...
It is not clear to me what you are asking but I believe that GROUP BY is one of the most misunderstood concepts in SQL, so I'll add this answer anyhow. It may or may not help with the understanding of the concept GROUP BY. Assume we have a table like:
CREATE TABLE T
( YEAR INT NOT NULL
, PARAMETERNO INT NOT NULL
, MARK INT NOT NULL
, PRIMARY KEY (YEAR, ...
There's nothing to fix, really.
The message refers to this computed column in the Sales.SalesOrderHeader table:
[SalesOrderNumber] AS (isnull(N'SO'+CONVERT([nvarchar](23),[SalesOrderID]),N'*** ERROR ***')),
The warning is informational in this case, to be sure you're aware in case it was a problem, as discussed in this Q&A: Type conversion in ...
Based on a_horse_with_no_name's comment, I started searching around psql and found the solution:
\set VERBOSITY verbose
SELECT * FROM tgvbn();
ERROR: 42883: function vfjkb() does not exist
Now that goes into .psqlrc. Details and further options can be found in the psql documentation.
The error message is quite clear. The table krneki_2 does not have a column named id_naslov. Unless there is some corruption in system tables or a bug, there is no question about that.
So we have to eliminate several possibilities why this appears:
There are mismatches between the CREATE TABLE statements and the UPDATE:
CREATE TABLE ` krneki_1` ...
I think I've found the cause.
Most likely the problem is due to "Fast startup" power options.
It'a a Windows technique to reduce the boot time; Fast Startup combines elements of a cold shutdown and the hibernate feature.
Here you can find another article about pros and cons
I have disabled it and the problem seems to be resolved.
Maybe this information is useful.
This release includes a change to the innodb_index_stats and innodb_table_stats system tables. When upgrading to this release, be sure to run mysql_upgrade in order to include these changes.