New answers tagged oracle-11g-r2
The documentation clearly describes the precedence for NLS settings: http://docs.oracle.com/cd/E11882_01/server.112/e10729/ch3globenv.htm#NLSPG188 1 (highest) Explicitly set in SQL functions 2 Set by an ALTER SESSION statement 3 Set as an environment variable 4 Specified in the initialization parameter file 5 Default ...
On Win7 you also must be running this as admin, or it will fail to be able to read the path variable, and install halts.
So you are trying to say that now my new user on server is using USER tablespace untill there is a enough space and after will continue to use DATATAB tablespace or not? Could I have problems in future? I dont understand why if new user on server is related to DATATAB tablespace and dmp is imported to that user, does use old tablespace from old user from ...
TRUNCATE TABLE_NAME; does the magic for you.
You should use TRUNCATE instead of DELETE if you is using SQL Server. Because it will reduce log records in log file. USE <your database>; GO DECLARE @table_name varchar(100); DECLARE c CURSOR FOR SELECT name FROM sys.tables WHERE type='U' OPEN c FETCH NEXT FROM c INTO @table_name WHILE @@FETCH_STATUS =0 BEGIN EXEC (N'TRUNCATE TABLE ...
Generate the statements you need select 'DELETE FROM '||table_name||' ;' from user_tables;
Why using original Export and Import utilities (imp and exp respectively), which are deprecated, while since 10g Oracle provides a new, more efficient facility called Data Pump? You can use Data Pump Import with REMAP_TABLESPACE parameter to specify the new tablespace name for the objects being imported: $ impdp hr REMAP_TABLESPACE=tbs_1:tbs_6 ...
It means that possibly some other DBA issued the command below (alter system with optional comment clause). Then the comment is put into spfile this way. But as I read metalink note: 257643.1 it might some outcome of some changes in automatic memory management. See alter system command: alter system set sga_max_size=2G scope=spfile sid=* ...
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')) ...
I think you need to either qualify type with schema when using client account (CO_ADMIN.DOCPARAMETERTYPE_TABLE, not just DOCPARAMETERTYPE_TABLE ) or create a public synonym for the type.
The only reason that I can think of is that the system was on the limit of physical memory and using a little bit of virtual memory (on Windows, paging file). Once you add more memory to Oracle, you push a lot of that buffer out of physical memory, which causes a huge increase in response time due to paging. Having a lot of paging taking place on an Oracle ...
configure the listener using Net Configuration Assistant or delete and recreate the listener with the same name and port
You just need to use NOT IN SELECT * FROM table1 WHERE col1 NOT IN (SELECT colA FROM table_2)
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, ...
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 ...
Top 50 recent answers are included