The same space-dropping command (onspaces –d) may be used to drop this new type of space,
Only if the space is empty (53 pages, oncheck –pe to verify)
General Syntax:
onspaces -d
[-y]
Example:
onspaces -d plogdbs -y
Dropping a PLOGspace with SQL Admin
Dropping a PLOGspace with SQL Admin
One must use a new “drop plogspace” command with SQL Admin API.
“drop dbspace” will return an error.
“drop plogspace” takes no arguments, since there can be at most one PLOGspace in the instance.
The PLOGspace must be empty to be dropped.
General Syntax:
drop plogspace
Example:
execute function task(“drop plogspace”);
In the message log file:
In the message log file:
Thru the onstat –m command line utility:
You will see a message saying “Physical Log too small ……”
Thru onstat –g ckp utility:
Look for a warning at the top about the physical log being too small or a “Trigger” of “Plog” with “Block Time” > 0.0
The presence of long transaction rollbacks. A “Trigger” of “LongTX” with “Block Time” > 0.0 can be a too small physical log or too little Logical Log space.
