Tag Info

Hot answers tagged

3

This can be done with a partial index. A bit complicated in Oracle because it doesn't allow a where clause in the create index statement (as e.g. Postgres does). But you can still trick Oracle in only indexing a sub-set of the rows by exploiting the fact that entries where all index columns are null are not put into the index. So you create a a unique ...


3

You could just try it out. This is logged in locally sqlplus / as sysdba: SQL> alter user mat identified by COOLPASSWORD ; User altered. SQL> select substr(sql_text,0,40) from v$sqlarea where lower(sql_text) like '%alter%' ; SUBSTR(SQL_TEXT,0,40) ---------------------------------------- select substr(sql_text,0,40) from v$sqla SQL> select ...


3

Just keep one table. Then replace the other table with a view on the table. Now you should be able to insert/update/delete a row in either the view or the table. Normally this should work. If the insert/update/delete in the view cause a problem then you can always create triggers on the view that replace insert, delete, and update (create trigger t_x instead ...


2

Just set the "long" in the sql sheet window big enough to hold the desired ddl. Example: set long 1000 select dbms_metadata.get_ddl('TABLE', 'XP','OPS$RM74384') from dual; -- Then just hit Run Script button or press f5.


2

Just start the database normally and run DBMS_DST.UPGRADE_DATABASE Then you must see the messages "An upgrade window has been successfully ended." and "Failures:0" Double check that it succeeded by running: 1: SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value FROM DATABASE_PROPERTIES WHERE PROPERTY_NAME LIKE 'DST_%' ORDER BY ...


2

Option 3. Unplug the PDB: Unplugging a PDB ALTER PLUGGABLE DATABASE salespdb UNPLUG INTO '/oracle/data/salespdb.xml'; Copy the files (XML + database files), then perform the checks listed below: Plugging In an Unplugged PDB Finally plug in the PDB: Examples of Plugging In an Unplugged PDB CREATE PLUGGABLE DATABASE salespdb USING ...


1

--Build the test table IF OBJECT_ID('SALES','U') IS NULL BEGIN CREATE TABLE SALES ( PRODUCT VARCHAR(10) , [YEAR] INT , QTR INT , [MONTH] VARCHAR(19) , Sales DECIMAL(19,4) ); INSERT SALES VALUES ('P1', 2013, 1, 'JAN', 2000.00) ,('P2', 2013, 2, 'APR', 3000.00) ,('P3', 2013, 3, 'JUL', ...


1

The DML in Inmemory involves new features like Journal & Inmemory Transaction Manager. When there is an insert operation on a table enabled for Inmemory, these new features get updated to bring the consistency in Transaction. Sometimes, there are overheads involved in keeping Inmemory Column Unit (IMCU) transactionally consistent. Following are some of ...


1

It sounds like you just want a CREATE TABLE AS SELECT CREATE TABLE your_new_table_name AS SELECT * FROM your_materialized_view If there are indexes on your materialized view that you want to create on the table, you'd need to create those separately.


1

It may not be the most efficient method but I can't see a problem with your SQL. Recommend you check your data..


1

Each element of a name must be quoted individually: drop java source "SCHEMA"."JAVASOURCENAME"; The identifier "SCHEMA.JAVASOURCENAME" refers to a java source name SCHEMA.JAVASOURCENAME in the current schema, e.g. "VORIAND"."SCHEMA.JAVASOURCENAME"


1

The main difference compared to the architecture of Data Pump utility exp / imp and expdp / impdp are always run on the DB server and not on a client. Then the files will always on the server where and active an Oracle database. The advantages of the data pump is performance (eg. Parallel) and the presence of new features' (eg. Migration direct SQL * Net, ...


1

Plugins are deployed on the OMS and the agents as well. First you should upgrade the plugin on the OMS, then on the agents. You don't need to upgrade between versions sequentially, you can upgrade to the highest available. Yes, there are. Currently 12.1.0.5 is the latest version, and there are quarterly PSUs as well. Check the below MOS note: Oracle ...


1

Yes, it is. BACKUP ARCHIVELOG ALL DELETE ALL INPUT; See: Deleting Archived Redo Logs After Backups in non-CDBs Or you can use FRA and configure an archivelog deletion policy: CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO DEVICE TYPE DISK'; This way when the FRA is getting full, the database will automatically delete already backed up ...


1

You might look at trying out Luca Canali's PerfSheet4 tool, which helps extract and visualize data from AWR tables in Excel. It comes with a video and should help you get started with some of the necessary data gathering and analysis for troubleshooting. You probably want to start with Query: Top 3 wait events and CPU option from the sheet which according ...


1

NOAFFIRM means the redo transport will be acknowledged before writing the received redo to disk (standby redo logs). ASYNC noaffirm means the log transfer method is ARCH right? No, it does not. Without specifying LGWR or ARCH, LGWR is the default. You can check it on the primary database by: select archiver from v$archive_dest where dest_id = 5; ...


1

SQL> alter session set nls_Date_format = 'DD-MON-YY HH24:MI:SS'; Session altered. SQL> select trunc(sysdate, 'DD') + 13/24 from dual; TRUNC(SYSDATE,'DD' ------------------ 29-AUG-15 13:00:00



Only top voted, non community-wiki answers of a minimum length are eligible