SAPDBA Troubleshooting (SAP Library - Database Administration (Oracle) with SAPDBA)

SAPDBA Troubleshooting

Before an additional file is added, SAPDBA carries out the following checks (if file systems are used):

Block size: The following block sizes must be identical:

	Block size for
filesystem block size	the file system
filesystem fragment size	the file system fragments
ORACLE block size	the database system

SAPDBA verifies that the above values are identical. If not, it issues a warning message and suggests selecting a new file system. You can ignore the warning and continue, but this is not recommended, as system performance will be affected when the block sizes of the file system and database are different.

Please also note the following:

The ORACLE database block size is always 8 KB in the R/3 System.
SAPDBA does not perform the check under the AIX operating system, as the block sizes are always different:

ORACLE block size

4 KB

filesystem block size

8 KB

For OSF1, the value for filesystem fragment size is always 1 KB, and is therefore not checked by SAPDBA.

Disk storage space: SAPDBA checks that there is sufficient storage in the file system proposed for the new file. If not, SAPDBA does not add the file.

If these checks were successful, SAPDBA creates a directory or a symbolic link for the data file. The control file (old and new) is backed up under the directory (directory name: <timestamp> ) belonging to the log file ( <timestamp>.ext ). SAPDBA then creates the data file with ALTER TABLESPACE ADD DATAFILE. If any of these operations fails, SAPDBA is terminated immediately.