I am trying to connect to a sybase ASE 15 enterprise edition database. Initially the connection is working fine but suddenly the page becomes unresponsive. There are no exceptions in the log nor is there any error displayed on the page. Also I have noticed that only the connection related to a particular database is unresponsive and remaining all are working just fine. However, if I restart the server, everything's working fine.
I have tried to increase the number of user connections and modified sytem configurations. But the result is all the same. Please help me out
I recommend you trace the session to get more log information:
1- initiate a connection to the database
2- use the stored procedure'sp_who' to identify the spid of the process of your connection on the server side
3- set up the trace file for this spid:
set tracefile 'log_file' for spid
(follow doc: http://www.sybase.com/files/White_Papers/ASE15-apptrace-070507-wp.pdf
OR
http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc00743.1502/html/queryprocessing/BABJDBHJ.htm )
4- analyze your log file
let us know if it helped.
Related
I have a WebLogic server and oracle db. At some point WebLogic server returns with ORA-1422 error but while executing the same procedure from backend it works. Also this will work when I restart the WebLogic server.
Any idea why its happening like this and any resolutions?
If you have uncommitted data then it is only visible to the session in which the data was inserted/updated and each connection will be a different session even if you are connecting as the same user.
Therefore, if you insert/update some data and end up with duplicate data but forget to COMMIT it in the WebLogic server then you will only see the issue in the WebLogic server (particularly if you are using a connection pool and you are reusing the same connection and session over-and-over) because that session is the only one that can see the uncommitted data.
You will not see the issue from other connections (i.e. if you connect to the backend or if you close and reopen the WebLogic server's connections).
You need to check that you are always committing your data.
Currently using version 7.13.2 with MySQL database.
When the usage in production server is high (with alot of concurrent user), Umbraco tend to create alot of database connection to handle those job. Those connection is not close after used but sleep.
Umbraco would continue to create more database connection when necessary until it reach the database max pool size.
Is this the intention behaviour by Umbraco? Else, how could we configure this issue?
After hundred hours of debugging, I finally found out the cause and the solution is easy.
This bug has nothing to do with Umbraco, it handles the connection perfectly. Umbraco using MySql Connector when connecting to MySql database. When the connection close, it is actually not close but instead, added to connection pool. Please refer to link below for more information.
MySql Connection not closing using .net MySql Connector
The solution as suggested from the link, just adding "Pooling=false" as a string parameter into connection string. The connection string locate inside the web config.
enter image description here
After rebooting my Windows Server 2016 Standard (SQL Server 2016) my SSIS process that runs this query:
select * from openquery(HRMPROD, 'SELECT QUERY HERE' )
started failing with this error:
I get the same error if I try to run the query in SSMS. I have the same linked server set up on my test instance and the query is successful when I run it there. I have compared the linked server create script on both instances and it is the same.
Any idea where I should look for what is causing the connection issue on the one server but not the other?
Thank you.
Saying the answer is on the Oracle side is just like pointing fingers across the way. Let's just fix the issue here.
There is a connection string that is used from SSIS, (which you also used in SSMS) The connection string contains three main components to connect and would result in the 12154 error if any of them were incorrect:
Host
Instance name (different than Instance on Sql Server, think database name)
port
The port most likely hasn't change, neither has the database name, but the host...No, hasn't changed, but the DNS server used to connect most likely has! I would ping the host and see what returns from the SSIS and your SSMS host that you're using. I would expect it to fail. Find out what IP address the host is using and ping that - see if it returns. I'm guessing that's the change that needs to be updated or your Network folks need to fix a DNS configuration/server issue.
Hope this helps!
Kellyn
Since you are getting a response from the TNS Listener, the problem lies on the Oracle side. See Architecture of Oracle Network Services for an overview of how the Oracle networking handles things. Keep in mind that based on the error message you've reached the TNS Listener, so you only need to check things between TNS and the Oracle database... In other words, your networking and SQL Server settings are fine or you wouldn't be able to get this error message.
I would agree with above that the issue might have to do with the network. I have come across that a few times, where we can set everything up, but a firewall is blocking communication between the two servers.
Open up powershell on the new server and run a tracert to the target to see the hops and identify if is connecting across the network.
If it is, then run a test-netconnect on the specific port, to see if the port is open from the firewalls.
Cheers!
I have a Tableau (reporting) server on Windows 10 that internally uses PostgresDB. Besides I have a PostgresDB, where my data is located, so reports are aggregated using this data.
What should our end-user experience? - He or she opens in a web browser a report by url and see the data.
For some reason from time to time our end-users face with the problem:
could not receive data from server: Software caused connection abort
(0x00002745/10053) Unable to connect to the server "server_name".
Check that the server is running and that you have access privileges
to the requested database.
This problem arises with different reports and in different time. Moreover, when I do not fix it for a long time, this report may start to work again.
There is no firewall or antivirus on Windows where Tableau server is, but there is a VPN.
What has helped?
Pgbouncer has solved it problem partially. By partially I mean that during 2 weeks of exploitation this error has only once occurred instead of 3 times per day by using pure Postgres.
Restart of Tableau server solves this problem as well.
Accidental loose of Internet connection on Tableau server also may help with this problem.
What have I also checked?
1) When everything is fine, in Pgbouncer logs I can see that queries are loading when I interact with a report, otherwise (when there is this error) no logs are recorded. So Tableau Postgres can't connect to Postgres with data for some reasons.
2) When I connect manually to PostgresDB from the Tableau Postgres, then everything is fine and all queries were executed, while end-clients face with the problem interacting via web browser.
3) When I type in CMD in Tableau Server (windows): netstat -nao | find PostgresDB:5432, in normal case I see many TCP connections with different PIDs except one PID which is executed from 2 different ports on Tableau Server, however all of them are tabprotosrv.exe; in case when it fails I see only one PID which is executed from 2 different ports on Tableau Server.
So I have 2 main questions
1. How to solve it normally?
2. Or what should I check else?
I'm currently attempting to debug a solution that I've picked up as a side project but I'm not having much luck. The solution depends on data (user IDs, page content, etc) stored on an MSSQL server on my local network, but when I execute the solution in VS2012 debug mode the connection fails. The error I'm getting says that the connection failed, and that the user was rejected.
When I log into the SQL server and check the event logs I can see where the login ID was rejected, but it was rejected because it wasn't the login ID that I specified in the connection string. It seems to be trying to use my windows authentication instead (which in windows 8 is a live ID) which won't work because my windows ID doesn't (and shouldn't) have access to the server.
Some basic connection string info (all data changed to protect the innocent... aka my poor server)
Data Source=myServer; Initial Catalog=myDB; User ID=myUsername; Password=myPassword; Integrated Security=false;
Has anyone run into this issue?
Do a search in the entire solution for myServer. This should shed light on the issue, given the connection string is defined somewhere else and it connects to the same server.