I connect to my Oracle database using SQL developer. The current idle time is set to 15 minutes of inactivity. I have sys dba privileges.
In the database, I did the following:
Alter profile {the profile my account belongs to} limit IDLE_TIME 10;
COMMIT;
Then, I stopped and started the database for good measure. Verified the idle time was still set to 10. It was.
Back in SQL developer, I start a new database session, ran a query, got the intended results. Stayed idle for 11 minutes, ran the same query once more, and it let me do so. My session hadn't timed out.
Am I missing something here?
UPDATE
I found out that I had to completely shutdown SQL developer and start it up once more for the changes to stick.
Related
I have been trying to successfully configure oracle database 11g with dead connection detection keep alive settings without changing any tcp settings. I went into $ORACLE_HOME/network/admin/sqlnet.ora and set the oracle keep alive to 10 minutes (SQL_NET.EXPIRE_TIME = 10). I also went into tnsnames.ora file and added the ENABLE=BROKEN parameter to the net_service_name. In one terminal I find the Oracle session process ID and then open a second terminal where I use the Linux trace tool to verify there is a write after 10 minutes. Unfortunately there is no write after 10 minutes. The only time there is a write is when the original oracle session being traced is disconnected or there is activity being performed in this session. I am trying to figure out how to resolve the issue of not seeing a write every 10 minutes to verify the server process sent an empty packet to the client.
I ran a script in Oracle sql developer last night which is a quite simple command:
'update TABLE set column A=...'
The table is a large one maybe about 70GB.
The task kept running for the whole night and still running....
Could I just click on the stop button on the window? I'm afraid of locking the session or the rolling back procedure will take longer time.
So what will happen to the database after we click stop? Or is there a more efficient way to kill task...
I would recommend not to stop it from SQL Developer instead you can get the session id from V$SESSION of this connection and kill it
alter system kill session 'sid,serial#';
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.
I am using PL/SQL Developer 11.0.4.1774. In my work, I need to use database whole day. Sometimes, during 30-60 minutes, I do not use ide and when I need to use it again, it requires reconnection.
I do not want to reconnect, is there any way to keep the connection alive whole day?
Go to Tools --> Preferences and click "Check connection". It pings the database every 60 seconds, making the session active and avoids idle session disconnects caused by profiles.
NOTE: This question and answer are for Allround Automations PL/SQL Developer. See this question if you're looking for Oracle SQL Developer.
you need check 'IDLE_TIME' and 'CONNECT_TIME' setting for your user profile
select * from dba_profiles
where resource_name in ('IDLE_TIME','CONNECT_TIME')
http://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_6010.htm
If a user exceeds the CONNECT_TIME or IDLE_TIME session resource
limit, then the database rolls back the current transaction and ends
the session. When the user process next issues a call, the database
returns an error.
I have PL/SQL Developer opens for days and don't have the issue
my PL/SQL Dev Tools-Prefernces-connection settings are:
Session Mode = Multy Session
Check connection = unchecked
Logoff with open transaction = Commit
and TIME settings are:
PROFILE RESOURCE_NAME RESOURCE_TYPE LIMIT
1 DEFAULT IDLE_TIME KERNEL UNLIMITED
2 DEFAULT CONNECT_TIME KERNEL UNLIMITED
Install the Reconnect plug-in so at least reconnecting can be a simple button-press.
Possibly against the intention of the DBA (if the issue is due to profile/resource manager settings), but you might try setting a Sessions window (or other report/query etc) to auto-refresh every 25 minutes or so.
Edit: I see on the Bar Solutions website the developer has moved Reconnect from "Plugins" to "Old Plugins". At my current client site I can't install plugins, so I can't tell whether it still works at the moment.
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.