- Monitor the storage load
- Change the storage parameters
- Restore individual files
- Improve the safety concept
The checking and analysis features in the reorganization menu of SAPDBA
were extended. You can now call a large selection of the ORACLE analysis
commands ANALYZE <TABLE/INDEX> <Name> COMPUTE|ESTIMATE STATISTICS
or VALIDATE STRUCTURE directly using the corresponding SAPDBA menu.
These operations are logged in a log <time stamp>.rch. You can access
statistics which were already generated if these are current enough.
A similar selection of analysis tools is possible with the command
option sapdba -analyze if the corresponding options (option, time)
are specified. You can also call both sapdba -analyze and sapdba -next
now specifying a list of tablespaces.
Example of the call: sapdba -analyze PSAPTESTD,PSAPTESTI
These operations are logged in a log <time stamp>.aly or
<time stamp>.nxt.
During a reorganization, you can influence the storage parameters of
the objects affected by the reorganization using the menu option
'Reduce object size'. SAPDBA determines the space actually used by
the tables and indexes and stores the new object with a size adjusted
to these values. In this way you can for example ensure that tables
with large storage areas which are never used are created with smaller
values for the INITIAL-Extent after a reorganization.
With the SAPDBA menu option 'Restore/Recovery->Restore individual
file(s)', it is possible to restore individual files. The menu option
'File type' defines the type of the files to be restored.
The following files can be restored:
Non-database files, database data files, control files
Online-redo-log files, offline-redo-log files, ORACLE profile,
BRBACKUP/BRARCHIVE profile, central SAPDBA log,
summed/detailed BRBACKUP/BRARCHIVE logs.
With the menu option 'BRBACKUP run', you can specify safety measures
to be used for loading back the files.
SAPDBA can also be started if a user is logged on as <sid>adm.
This is only possible if the corresponding authorization was granted for SAPDBA (for UNIX, for example, the s-bit must be set).
In this way you can distinguish the authorization for using SAPDBA
from the authorizations of user ora<sid> (e.g. calling SQLDBA).
BC SAP database management: ORACLE