Flushing the shared pool should do it, but Tom Kyte lists a couple reasons below why you may not get the result you are expecting in some cases: http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:6349391411093
Remove the TO_DATE in the WHERE clause TO_DATE (alarm_datetime,’DD.MM.YYYY HH24:MI:SS’) and change the code to alarm_datetime The error comes from to_date conversion of a date column. Added Explanation: Oracle converts your alarm_datetime into a string using its nls depended date format. After this it calls to_date with your provided date mask. This throws the exception.
The reason for this error is that SQL SELECT statements are logically * processed in the following order: FROM: selection of one table or many JOINed ones and all rows combinations that match the ON conditions. WHERE: conditions are evaluated and rows that do not match are removed. GROUP BY: rows are grouped (and every … Read more
This is a simple way to do it without any triggers or sequences: insert into WORKQUEUE (ID, facilitycode, workaction, description) values ((select max(ID)+1 from WORKQUEUE), ‘J’, ‘II’, ‘TESTVALUES’) It worked for me but would not work with an empty table, I guess.
Pressing ctrl+shift+N will open a new unshared worksheet that can run queries in parallel. In that case you have to paste a query in each tab and run them manually though, but it is handy when just testing a few queries.
ORA-00904-invalid identifier errors are frequently caused by case-sensitivity issues. Normally, Oracle tables and columns are not case sensitive and cannot contain punctuation marks and spaces. But if you use double quotes to create a quoted identifier, that identifier must always be referenced with double quotes and with the correct case. For example: create table bad_design(“goodLuckSelectingThisColumn … Read more
It means the connection was successfully established at some point, but when you tried to commit right there, the connection was no longer open. The parameters you mentioned sound like connection pool settings. If so, they’re unrelated to this problem. The most likely cause is a firewall between you and the database that is killing … Read more
Oracle’s security model is such that when executing dynamic SQL using Execute Immediate (inside the context of a PL/SQL block or procedure), the user does not have privileges to objects or commands that are granted via role membership. Your user likely has “DBA” role or something similar. You must explicitly grant “drop table” permissions to … Read more
Answer It’s most likely a firewall between SQL Developer and the database that breaks things. You can solve that from SQL Developer using the SQL Developer Keepalive plugin. You can also fix this from the Database Server by using the answers by Thomas and David Mann. Oracle Net can be configured with Dead Connection Detection … Read more
(as the previous answer) and here’s the code: ALTER TABLE atable ADD (tmpdetails CLOB); UPDATE atable SET tmpdetails=details; COMMIT; ALTER TABLE atable DROP COLUMN details; ALTER TABLE atable RENAME COLUMN tmpdetails TO details;