OAM [Object Allocation Mapping]

OAM [Object Allocation Mapping]

With this for load option db will be offline until a load has been done and then become online.

• When we use this option the database will be created and it will be in offline mode.
• Only the OAM pages will be initialized during the creation of this db and the actual page allocation will be done at the time of load
• with this option db creation is faster
• whenever we create a database with this option it will be in don't recover option and even when ever there is a termination of dump db transaction
• whenever creating a dbcheck whether the given size and size of the disk after creating are equal or not this may create the problem
• whenever you forget the compression option of dump db during loading db it takes the option if dumpdb .

Syntax

dumpdb <database name> “ compress::2::/physical path ” → option given here

dumpdb <database name> “ compress::/physical path ” → option not given here

WITHOVERRIDE

option is used if we want to “create a database” or “alter a database” whose data and log is on same device .

Example:

Create database dbname on d001=40 log on d001=5 WITHOVERRIDE

!! Warning !!

• This can make recovery impossible if that disk fails and database is online
• When database is critical I.e mostly 95% of the space is used then the threshold action is fired .