Sometimes it is very useful to get the DDL of an object of particular database.
We can recreate such a user from one environment to another without even knowing the password.
DDL statements can be obtained by calling the function:
object_type IN VARCHAR2,
name IN VARCHAR2,
schema IN VARCHAR2 DEFAULT NULL,
version IN VARCHAR2 DEFAULT 'COMPATIBLE',
model IN VARCHAR2 DEFAULT 'ORACLE',
transform IN VARCHAR2 DEFAULT 'DDL')
In 10g and 11g versions of Oracle Database, it has been simplified configuration memory structures for both the SGA and the PGA significantly.
Oracle version >=10g
From 10g, 2 new memory management parameters that enormously simplify this task are introduced.
SGA_TARGET, simply set a value and resizes demand values (if they are = 0):
- Buffer cache (DB_CACHE_SIZE)
- Shared pool (SHARED_POOL_SIZE)
- Large pool (LARGE_POOL_SIZE)
- Java pool (JAVA_POOL_SIZE)
- Streams pool (STREAMS_POOL_SIZE)
When we make a list of the backups made with:
RMAN> list backup summary;
For example, we may have problems locating a backupset. The result is quite confusing and certainly inelegant labels are created by default.
Since the release of Oracle Database 11g, it has reinforced security by default. This should in principle be positive, but there are some situations where some behaviors may be unpleasant.
The most obvious example can be found in the modification of the profile (PROFILE) DEFAULT, which is applied to any user created by default.