For how many years have you been working
with physical servers that are starving your database of the memory
necessary to deploy important new performance features such as the Result
Cache, Memoptimize Pool, In-Memory Aggregation, In-Memory Column Store, and
Full Database Caching? Too long? Contact me to learn how to improve all
queries ... not just some queries.
Repairs various things that get lost across transport due to no relevant syntax (i.e. options/versions based on compatibility rather than explicit syntax). This is called during TTS import.
str1 IN VARCHAR2, -- schema name
str2 IN VARCHAR2,
str3 IN VARCHAR2,
str4 IN VARCHAR2,
str5 IN VARCHAR2,
str6 IN VARCHAR2,
str7 IN VARCHAR2,
bin1 IN BINARY_INTEGER); -- bitmap, etc.
This procedure will finish things up after objects have been created. Patchup table metadata after table has been created at the import site. This procedure is called by DataPump Import.
schemaName IN VARCHAR2, -- schema name
tableName IN VARCHAR2, -- table name
mdClob IN CLOB, -- data pump's metadata
expSrvrEndian IN BINARY_INTEGER, -- export endian
impSrvrEndian IN BINARY_INTEGER); -- import endian