The copy-pastes and explanations blog for SQL code, errors and daily cases! This blog is a 'list' of actions that always good to have available. The copy-paste concept here is short and clear explanations and descriptions (no long stories!) and - of course - the code to take (copy) and use (paste). The blog deals in the database (mostly) and software issues.
Labels
SQL Server - history of failed jobs
SQL Server - database stuck in restoring status
RESTORE DATABASE <DATABASE_NAME> FROM DISK = '<Fuul path>\MyDatabase.bak' WITH REPLACE,RECOVERY
SQL Server - ALTER DATABASE SET OFFLINE takes a long time
ALTER DATABASE SET OFFLINE takes a long time
Close active sessions of the database:
--find active sessions:
SELECT * FROM sys.sysprocesses WHERE dbid = DB_ID('MYDATABASE')
A connection was successfully established with the server, but then an error occurred during the login process
A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.)
SQL Server: fix Recovery Pending State of a Database
GO
ALTER DATABASE [DBName] set single_user
GO
DBCC CHECKDB ([DBName], REPAIR_ALLOW_DATA_LOSS) WITH ALL_ERRORMSGS;
GO
ALTER DATABASE [DBName] set multi_user
GO
SSMS: sql server Script failed for StoredProcedure 'PROCEDURENAME' (Microsoft.SqlServer.Smo) ... Invalid version: ...
Alter Stored Procedure in SSMS.
Error:
sql server Script failed for StoredProcedure 'PROCEDURENAME' (Microsoft.SqlServer.Smo) ... Invalid version: ...
Update SSMS to a newer release.
SAP RS - Sybase SSL error: Open Server error: Error: 16029, State: 0, Severity 20 -- 'Failed to start any network listeners'
SAP ASE - Sybase SSL error: kernel ninit: bind, Address already in use
00:0002:00000:00009:2020/07/21 13:10:26.85 kernel ninit: bind, Address already in use
00:0002:00000:00009:2020/07/21 13:10:26.85 kernel Cannot allocate resources for listener with protocol ssltcp, host asazrlnsap16, port 5000.
Solution:
Delete duplicate definitions for the server with the same port (edit the ini file).
SAP ASE - Sybase SSL error: Configuration parameter 'enable ssl' can not be enabled without license 'ASE_ASM'.
2. Click tile "License keys"
3. Click your current server id, i.e. L16
4. Right bottom click "Edit"
5. The info should already there, so "Continue"
6. In this page search "security"
From my side I see below, but you might have different license number, for an example:
Item Description
7011762 SAP Sybase ASE Enterprise Edition Security & Directo
-> If you can find such "security" license, then click the "Generate" and step by step fill out the system info, to download.
-> If you can NOT find such license, call SAP hotline(560499) for help, ask them to help involve the SAP sales for license purchase.
7. Put the downloaded license in folder:
/sybvol01/sap16/SYSAM-2_0/licenses/
8. Restart ASE server.
9. Check ASE error log see if SSL is enabled, if still license error raised please send me back the complete ASE error log.
SQL Server on GCP - You do not have permission to run the RECONFIGURE statement
Can not connect SQL Server instance on GCP from SSMS
Can not connect SQL Server instance on GCP from SSMS (SQL Server Management Studio).
Solution:
Create Authorized networks:
Go to Connections page, under Connectivity → Public IP:
MySQL - Can not connect to the database
Error message:
ERROR 2003 (HY000): Can't connect to MySQL server on '....' (111).
Solution:
- Check connection details:
- Verify that the IP is correct.
- Verify that the Port number is correct.
- Check username and password.
- Network issues:
- Check that connection to VPN or any other connection types.
- Check Firewall definition.
- For cloud instances: check that your IP is allowed.
- Check that MySQL is up:
- Check that the MySQL service is up:
- Windows: in the services.
- Linux: sudo systemctl start <SERVICENAME>
- MySQL configurations:
- Max connections - see here: http://copypastenet.blogspot.com/2021/02/mysql-see-orand-change-how-many.html
- cnf file configurations.
MySQL - MariaDB - error in your SQL syntax near ';
Error Code: 1064. You have an error in your SQL syntax;
check the manual that corresponds to your MariaDB server version for the right syntax to use near '; INSERT CITY (..... at line 1
INSERT CITY (CITY_CODE, CITY_DESCRIPTION) VALUES (N'TT1', N'test1');;
INSERT CITY (CITY_CODE, CITY_DESCRIPTION) VALUES (N'TT2', N'test2');
The ';' without a statement.
;; --> ;
MySQL - Operation ALTER USER failed for 'root'
Operation ALTER USER failed for 'root'
ERROR 1396 (HY000): Operation ALTER USER failed for 'root'@'%'
or
ERROR 1396 (HY000): Operation ALTER USER failed for 'root'@'localhost'
The case:
root password was damaged and login with root user is failed.
Solution:
- Connect to MySQL with another user
- Update root set authentication_string=null
- FLUSH PRIVILEGES;
- Logout (quit)
- Connect to MySQL using "mysql -u root"
- Set root password
- Logout (quit)
C:\Program Files\MySQL\MySQL Server 8.0\bin> mysql -uusername -ppasswordmysql> UPDATE mysql.user SET authentication_string=null WHERE User='root';Query OK, 1 row affected (0.01 sec)Rows matched: 1 Changed: 1 Warnings: 0mysql> FLUSH PRIVILEGES;Query OK, 0 rows affected (0.31 sec)mysql> quitByeC:\Program Files\MySQL\MySQL Server 8.0\bin>mysql -u rootmysql> ALTER USER 'root'@'%' IDENTIFIED BY 'newrootpassword';Query OK, 0 rows affected (0.26 sec)mysql> quitBye
Can't connect to MySQL 8.0 because a plugin error
Can't connect to MySQL 8.0 because a plugin error
FATAL: error 2059: Authentication plugin 'caching_sha2_password' cannot be loaded: /usr/lib64/mysql/plugin/caching_sha2_password.so: cannot open shared object file: No such file or directory
FATAL: 'sysbench.cmdline.call_command' function failed: /usr/share/sysbench/oltp_common.lua:83: connection creation failed
The main cause is that the user has password plugin as "mysql_native_password" but authentication_string contains different hash in mysql.user table.
FLUSH PRIVILEGES;
UPDATE mysql.user
SET authentication_string=concat('*',upper(sha1(unhex(sha1('USERNAME')))))
WHERE user='USERNAME';
FLUSH PRIVILEGES;
MySQL service is in the status “starting” on windows but the service doesn't work
SAP RS - The transaction log in database RSSD is almost full
Error when trying to start SAP Replication Server.
E. 2020/12/14 21:39:52. ERROR #11061 GLOBAL RS(GLOBAL RS) - generic\sts\stscol.c(2631)
I. 2020/12/14 21:39:52. Message from server: Message: 7415, State 1, Severity 10 -- 'The transaction log in database RS1_RSSD is almost full. Your transaction is being suspended until space is made available in the log.
Reason:
Cause of the error: The transaction lof of the RSSD database is (almost) full.
MySQL troubleshooting - Can’t login remotely
The problem:
Can’t login remotely, can login only from the server itself.
The reason:
Permissions for remote login are missing.
Solution – Linux:
GRANT ALL PRIVILEGES ON *.* TO 'root'@'%' IDENTIFIED BY 'second_server’;
Check with:
SELECT host, user, authentication_string FROM user ;
Solution – Windows:
From MySQL Workbench, on the instance connection, Users and Privilages, choose the user (root) and change “Limit to host matching” to “%”.
MySQL Shell - Dba.deploySandboxInstance: ERROR: Error creating sandbox: Could not find mysqld executable. Make sure it is on the %PATH% environment variable.
Error message:
MySQL JS > dba.deploySandboxInstance(3310)
A new MySQL sandbox instance will be created on this host in
C:\Users\IGittler\MySQL\mysql-sandboxes\3310
Warning: Sandbox instances are only suitable for deploying and running on your local machine for testing purposes and are not accessible from external networks.
Please enter a MySQL root password for the new instance: ******
Deploying new MySQL instance...
Dba.deploySandboxInstance: ERROR: Error creating sandbox: Could not find mysqld executable. Make sure it is on the %PATH% environment variable. (RuntimeError)
Solutions:
- Check path definitions.
- MySQL Server should be installed on the machine.
MySQL: You are using safe update mode and you tried to update a table without a WHERE that uses a KEY column
Error message:
You are using safe update mode and you tried to update a table without a WHERE that uses a KEY column.
Solution:
add before the update (/delete) statement:
SET SQL_SAFE_UPDATES=0;




