I'm running Oracle 19c with the cx_Oracle Python connector and I'm getting this error.
DPI-1067: call timeout of 15000 ms exceeded with ORA-3156
The problem is that I'm getting this error when attempting to commit.
Because this is so hard to reproduce in a development environment I have no idea if this is safe. If a call timeout happens in Oracle when committing, will the commit be rolled back?
Related
I am connecting to oracle 12 in Oracle cloud, from PowerBI Desktop windows server 2016.
Oracle client is installed and TNS file configured.
Oracle is hosted by a vendor so my only access is to directly query the database.
In powerBI, when using an oracle connection, i get ORA-03113 errors about 50% of the time when refreshing data. There is no discernible pattern to the appearance of the error.
If i connect via a System ODBC connection set up in windows, I dont get any issues or errors, although the data load is a bit slower.
I would appreciate ideas on what may be causing this issue or what to check to help get more information.
I'm afraid your issue needs some deeper analysis as ORA-03113 might have various reasons, but typically it means that the 'oracle' executable has terminated unexpectedly once there was an existing connection. You should try to isolate the SQL command that is executing when the error occurs. It can be done either by checking the trace files on the server or by using SQL*Net trace if you don't have access to the server. If a statement can be isolated which consistently raises the ORA-3113 error, then it can be further analysed (like execution plan, triggers, etc), or maybe the best to raise an SR so Oracle Support can work on the issue. If you have access to Oracle Support you can find more information about ORA-03113 troubleshooting in MOS Doc ID 1506805.1. Let me know if I can help you any further.
I have installed Oracle xe 18 with apex and ORDS successfully on Centos 7, every thing runs fine but after certain inactivity on database like 6/8 hours later Oracle stopped and ORDS throws 503 error code.
Once I start the database up, all are normal then.
Can you please suggest me how to keep Oracle up all time/ unless manually shutdown VPS or the like?
Thanks
After your database is restarted, connect with an ADMIN level user, and use SQL Developer to inspect the Alert Log - you'll find this as one of the standard reports we ship in the Database Administration section.
Look for things like 'fatal' 'ora-600' 'abort' - this should clue you in as to what is happening.
We'll assume you don't have a job scheduled on Centos that shuts down the database.
Is there an option in Oracle SQL Developer (I use version 4.1.5) to make it reconnect to the DB when needed?
For example, if I start an SQL script but the DB was disconnected, then it should reconnect with minimum hassle and execute the script instead of giving a SQL Error: Closed Connection message.
Note: I'm not interested in keep-alive (what most related questions discuss). If I don't use it today, then it is OK to disconnect. I just want it to reconnect next time I use it.
No.
Auto-connecting dropped connections sounds good in theory, but the 'auto' part is where the trouble begins.
I have a standing ER to add the reconnect button to the dropped connection ERROR message.
In at least SQL Developer version 20.2 this is implemented:
when running an SQL operation when the DB was disconnected after a while, the connection is restored and the operation is executed (there is also a dialog shown telling about the fact).
I often get below error while running some sessions in Informatica Powercenter. The session is supposed to insert/update some records in oracle tables.
Username USER123 DB Error -1
Database driver Error...
Function Name: Logon
ORA-12537: TNS-connection closed
Database Error: Failed to connect to database using user [USER123] and connection string [ORCL123]
This is totally random. I have ran the same sessions sometimes smoothly without a singe hitch. But sometimes the error comes back again and again. Whenever it occurs, stays for 5 mins max, means if I restart the session immediately after failure, it will fail again. But if I wait for 5 mins and restart them again, it runs successfully. But the only problem is it comes back again in another half an hour or so.
Can somebody enlighten me to get a probable resolution for the error?
Do check the number of connections allowed on the Oracle instance if they are exceeding intermittently by other users and refusing your user connection from Informatica.
Im having some trouble with an oracle database. Every time i try to connect, i get this message.
ORA-01033: ORACLE initialization or
shutdown in progress
I searched the web, and found that the solution is to execute an alter database open command, but what I dont understand is where should i execute if, since I cant connect to the database.
Am I missing something?
Thanks in advance
You should connect AS SYSDBA:
sqlplus "sys/pwd AS SYSDBA"
An ORA-01033 would also be thrown if the connection attempt were made against a mounted standby database (Oracle Data Guard environment) by a non-sysdba user. Maybe a database role change (switchover or failover) has occurred since your last connection attempt.
Which OS are you using? The database is still shutting down - check the alert log as to the status of where it is at. Sometimes there are sessions hanging around that need to manually be killed off, there should be an indication of this in the alert log. It also depends how the database was shutdown, NORMAL, TRANSACTIONAL, IMMEDIATE. Even with a SHUTDOWN IMMEDIATE the sessions hanging around may still happen. To find the sessions on UNIX use the 'ps' to list all processes on the server ('ps -eaf' on Solaris) command and 'grep' for the ORACLE_SID name.