Hot answers tagged oracle-11g-r2
The correct answer for licensing questions is: contact your oracle sales representative. With Oracle you license cpu's. If your test and prod run on the same cpu's, they don't need a new license. As long as it all runs on the same cpu's, it does not matter if you have multiple databases (and instances) or run it all in one single database. Normally we don't ...
Use this on Windows (three nested double quotes): exp system/password_for_system@dev file=c:\fooadmin.dmp full=yes imp """sys/password12345@dev as sysdba""" FROMUSER=FOOADMIN TOUSER=FOOADMIN file=c:\fooadmin.dmp In general imp would work as intended with sys account, it is just not recommended. But exp with sys account could possibly produce inconsistent ...
First you need to convert it to TIMESTAMP datatype (because DATE type does not handle fractions of second). Then you can truncate it to date for example: alter session set nls_date_format='YYYY-MM-DD HH24:MI:SS'; with data as (select '2012/09/06-21:17:30:019' as lastupdate from dual) select trunc(to_timestamp(lastupdate, 'YYYY/MM/DD-HH24:MI:SS:FF3')) ...
DBCA relies on /etc/oratab. If that file is empty, or the entry for the database you want to delete is missing, the option(s) will be disabled.
In Oracle BEGIN starts a PL/SQL block. In other words, after BEGIN you ought to provide a text of a program that is written in a procedural language that is somewhat different than SQL (although it bears some similarities). Your sqlplus had read everything but it was not yet parsing or executing anything, it was waiting for an END and a line containing only ...
Oracle's transactions are implicit in sqlplus you're already in one and don't have to start it. This means you can just do select ... update .. rollback ... select... if you do an exit without doing exit rollback it will commit on exit. begin is not necessary here.
This was a problem with the hostname not getting set consistently on boot, and was not correctly available at that time but was later.
Views starting with VW_DTP showing up in the execution plan is the result of one of the cost-based query transformations available since 11.2, called distinct placement. It happens with statements using the DISTINCT clause, just like yours. It is an absolutely acceptable an quite obvious execution plan to join the tables and filter the rows, and after that, ...
Only top voted, non community-wiki answers of a minimum length are eligible