What is the cause of this error when data is written into the TDengine database?
TDengine ERROR (80000014): Database not ready
The error message "TDengine ERROR (80000014): Database not ready" indicates that the TDengine database is not yet ready to accept incoming data. This error typically occurs when the database is starting up, initializing data structures, or recovering from a crash.
There could be several reasons for the database not being ready:
1.The TDengine server is still starting up: In this case, the error message should go away once the server has fully started and is ready to accept incoming data.
2.The TDengine server is undergoing maintenance or is in the process of a software upgrade: In this case, you may need to wait until the maintenance or upgrade has completed before trying to write data to the database again.
3.The TDengine server has encountered an error: In this case, you may need to investigate the error log or reach out to the TDengine support team for assistance.
4.The TDengine client is not configured correctly: In this case, you may need to check the client configuration and ensure that the correct hostname, port number, and database name are specified.
If the error persists, it is recommended to check the TDengine log files and consult the TDengine documentation or support team for further guidance.
Related
In our production environment there are sometimes peaks of ORA-12599 errors the connection works otherwise.
The description is not quite clear to me.
Cause: The data received is not the same as the data sent.
Action:
Attempt the transaction again. If error persists, check (and correct)
the integrity of your physical connection.
https://www.oraexcel.com/database-oracle-11gR2-ORA-12599
Does that mean there is a problem with my network cable? Or any other Hardware?
Because our DBA said the error can be caused by a configuration issue on the client side.
Edit:
It started without any changes on the client or server side. And there are spikes. 80 errors in an hour and then no errors for 4 hours while the load is more or less constant
It can mean a mismatch in how the client and the server are wishing to communicate (in encrypted fashion). For example, trying to connect to an 11g database with 10g JDBC drivers will get this because the encryption implementation changed between these versions.
Check your local (ie, client) sqlnet.ora file - you may need to opt for a different method or change the order of them.
The error can be typically be ignored (its informational) but using the latest drivers will normally resolve the issue.
We had sporadic ORA-12599 errors and also ORA-24300 ("bad value for mode") in a Python web app using Flask and uwsgi. It turned out to be caused by multiple worker processes writing and reading to/from the same TCP connection to the DB, giving chaotic communications on the socket.
In our setup this was caused by creating the TCP connections to the DB before uwsgi forked the workers, and the file descriptors being inherited. We fixed this by using uwgsi's lazy-apps mode.
See also this question.
The POSTGRE SQL database associated with our AppEngine project does not start giving "An unknown error occurred". The first error of this kind is reported this morning, 22.05.2019 at 7:31 Spain time, and later trials on Starting the database have equally failed with the same "unknown error" message.
Is it possible that this is related to issue 19002 reported yesterday?
https://status.cloud.google.com/incident/cloud-sql/19002
We need your help to see what is happening and start the database as soon as possible. Thanks
It is possible that this Google Cloud SQL Incident #19002, cause a lot errors between this stage.
Cloud SQL provides the ability to replicate a master instance to one or more read replicas:
https://cloud.google.com/sql/docs/postgres/replication/create-replica
I have couple of database on SQL server which were working fine. Now I am no longer able to explore those. What can be the reason?
Also i am getting below error while trying to turn database on
"File activation failure. The physical file name "D:\Microsoft SQL Server\MSSQL10_50.MSSQLSER\DATA\DB_NAME_log.ldf" may be incorrect.
The log cannot be rebuilt because there were open transactions/users when the database was shutdown, no checkpoint occurred to the database, or the database was read-only. This error could occur if the transaction log file was manually deleted or lost due to a hardware or environment failure."
Can jdbc connections which are closed due to database un-availability be recovered.
To give back ground I get following errors in sequence. It doesn't look to be manual re-start. The reason for my question is that I am told that the app behaved correctly without
the re-start. So if the connection was lost, can it be recovered, after a DB re-start.
java.sql.SQLException: ORA-12537: TNS:connection closed
java.sql.SQLRecoverableException: ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
IBM AIX RISC System/6000 Error: 2: No such file or directory
java.sql.SQLRecoverableException: ORA-01033: ORACLE initialization or shutdown in progress
No. The connection is "dead". Create a new connection.
A good approach is to use a connection pool, which will test if the connection is still OK before giving it to you, and automatically create a new connection if needed.
There are several open source connection pools to use. I've used Apache's JDCP, and it worked for me.
Edited:
Given that you want to wait until the database comes back up if it's down (interesting idea), you could implement a custom version of getConnection() that "waits a while and tries again" if the database doesn't respond.
p.s. I like this idea!
The connection cannot be recovered. What can be done is to failover the connection to another database instance. RAC and data guard installations support this configuration.
This is no problem for read-only transactions. However for transactions that execute DML this can be a problem, especially if the last call to the DB was a commit. In case of a commit the client cannot tell if the commit call completed or not. When did the DB fail; before executing the commit, or after executing the commit (but not sending back the acknowledgment to the client). Only the application has this logic and can do the right thing. If the application after failing over does not verify the state of the last transaction, duplicate transactions are possible. This is a known problem and most of us experienced it buying tickets or similar web transactions.
Today we had a lot more activity than normal between our Ruby on Rails application and our remote legacy SQL Server 2005 database, and we started getting the error below intermittently. What is is? How can I prevent it (besides avoiding the situation, which we're working on)?
Error Message:
ActiveRecord::StatementInvalid: DBI::DatabaseError: 08S01 (20020) [unixODBC][FreeTDS][SQL Server]
Bad token from the server: Datastream processing out of sync: SELECT * FROM [marketing] WHERE ([marketing].[contact_id] = 832085)
You need to use some sort of connection pooling.
Windows itself (including Windows Server X) will only allow a certain number of socket connections to be created in a given time frame, even if you close them. All others will fail after that.
A connection pool will keep the same sockets open, avoiding the problem. Also, new connections are real slow.
This Microsoft article says:
Often caused by an abruptly terminated network connection, which causes a damaged Tabular Data Stream token to be read by the client.
Was the server network bound? I have no experience with SQLÂ Server, but does it have a limit on the number of connections you can make?
Add the following to your script; the first statement you run:
SET NO_BROWSETABLE OFF