During the previous year we have seen 3 new editions of Oracle: 9i, 10g and 11g.There is an often requested and I do ask well which is the best or which are the best popular functions of Oracle.
Real Program Groups and Information Secure in 9i
Grid Management and Information Push in 10g
Automatic SQL Adjusting and Edition-Based Redefinition in 11g
There have been so many new, excellent and essential functions but let us say that they all are in the improvement of humanity and the latest growth of IT. Perhaps?
In 11gR2, Oracle chooses introducing Information Push Heritage Method to be able to offer in reverse interface for programs and parameter data files used for exclusive export/import programs. The certification temporarily says: “This function allows customers to proceed using exclusive Trade and Transfer programs with Information Push Trade and Transfer. Growth time is decreased as new programs do not have to be designed.”
If you examine AristaDBA’s Oracle Weblog and browse the first three sections you will probably see what it is about. I completely believe the fact with all published there.
And I don’t really get it, why do we have Information Push Heritage Mode? Oracle customers poorly need it? Exp/imp was so, so great that we must have it back? How about RAC Heritage Method if I want to use gc_files_to_lock or freeze_db_for_fast_instance_recovery parameters? There really was a parameter known as freeze_db_for_fast_instance_recovery, I am not creating this up. Run this one:
However, the Information Push Heritage Method function prevails and once you use any traditional export/import parameter you allow data pump in legacy mode. Just one parameter is enough. In Oracle language, Information Push goes into legacy mode once it chooses a parameter exclusive to exclusive Trade or Transfer is existing. Of course some factors like shield, make, pack, object_consistent, recordlength, resumable, research, gather, filesize, tts_owners, streams_configuration and streams_instantiation are merely ignored.
Now, here is a paradox or simple certification error: deferred_segment_creation is set to TRUE automatically in 11gR2. Have a look at the documentation:
But it is not true that you cannot export tables with no segments. Here is the proof:
But ignore about this Heritage Method. Do not use. Imagine it does not quit
Let us look now at some new popular functions of Information Push. Remember that in 11gR2 several of limitations have been already removed:
– The limitation that in TABLES mode all tables had to live in the same schema.
– The limitation that only one item (table or partition) could be specified if wildcards were used as aspect of the item name.
For RAC users: Information Push employee procedures can now be allocated across RAC circumstances, a aspect of Oracle RAC circumstances, or limited to the example where the Information Push job begins. It is also now possible to begin Information Push tasks and run them on different Oracle RAC circumstances at the same time.
For XMLType line users: there is a new DISABLE_APPEND_HINT value on the DATA_OPTIONS parameter which hinders the APPEND sign while running the information item.
For EBR users: particular versions can be released and brought in. Using the SOURCE_EDITION parameter upon trade and the transfer TARGET_EDITION parameter you can trade a certain version of the data source and transfer into a particular version of the data source.
Information Push is among the Oracle resources with least bugs! Although it challenging to say these days what is a bug, what is an element, what is a copy enhancement. There are about 100 kinds of insects.