Choose a layout and drag widgets onto your Overview Page to customize it. Widgets placed on the page below can be configured by selecting the symbol.
Click here to view all ideas!
i think Oracle could be more if a datapump could be restartable after a database Shutdown while a datapump job is being execute, because datapump master table could contains all necessary information. Regards.
A review of a costum built materialized view implementation raised the idea to integrate such a refresh method into Oracles native materialized views. It has been achieved by MERGing differences only into the target table (MV) even for complex/non fast refreshable MVs as depicted in the example below. This might be useful for non fast refreshable MVs that do change rather rarely but should reflect changes quite promptly even so without generating large amounts of redo. As this MERGE can simpl …
There is quite often a need to purge old data from tables. I appreciate this is a very complex subject, and involves checking referential integrity etc, however I have seen a lot of examples of people setting up custom jobs to purge old partitions in their interval tables. I too have a similar requirement. Rather than having to do this manually, I think it would be very useful to include some form of retention clause on the partition key. Something like: partition by range (a) purge partitions …
Currently, if you use a constant in a SQL statement in PL/SQL (e.g. to avoid the use of "magic" values, as is good coding practice), it gets treated as a bind variable when it's parsed and run. E.g.: declare
k_constant_val varchar2(10) := 'X';
where dummy = k_constant_val;
returns the following when viewed in V$SQL: SELECT DUMMY FROM DUAL WHERE DUMMY = :B1
This could impact performance when runnin …
HI, Oracle have to make “better” relation between histogram and indexes, actually need some kind of new index, index that not include rows in index if values of rows have bad selectivity, just ignore that rows like what it is doing with NULL value. Index will be “smaller and faster”. We can do it with functional index, but this "feature of index" will be "built in feature". example: - Index on column status - Status possible has 2 values ('Y', 'N') - 95% of the row has status 'Y' D …
No user featured