Adapting Next Extents with BR*Tools

Prerequisites

Make sure you have set the necessary BRCONNECT parameters in the initialization profile init<DBSID>.sap, because BRTOOLS uses these when it calls BRCONNECT.
The database must be open.
It only makes sense to adapt next extents for tablespaces that are dictionary-managed. If all tablespaces are locally managed, do not use this function.

Context

You can adapt the next extents for tables in your Oracle database with BR*Tools. The aim is to avoid extent overflow, which causes transactions to abort.

For more information, see:

Procedure

Start BRGUI or BRTOOLS.
Choose Additional functions Adapt next extents .

Set the required options:

Menu Entry	Equivalent BRCONNECT Command Option
BRCONNECT profile (profile)	-p\|-profile
Database user/password (user)	-u\|-user
Database owner for adapt (owner)	-f next -o\|-owner
Maximum extent size in KB (max)	-f next -m\|-max
Maximum extent count (limit)	-f next -l\|-limit
Special NEXT extents (special)	-f next -s\|-special
Exclude from adapt (exclude)	-f next -e\|-exclude
Tables for adapt (table)	-f next -t\|-table
Confirmation mode (confirm)	-c\|-confirm
Query mode (query)	-q\|-query
Force options (force)	-f next -f\|-force
Additional output (output)	-o\|-output
Message language (language)	-l\|-language
BRCONNECT command line (command)	This shows you the BRCONNECT -f next command that is to be executed using the current settings.

To start processing with the selected options, choose Continue.
Check the results in the BRCONNECT logs.
- The summary log conn<DBSID>.log displays the return code.
- The detail log c<encoded timestamp>.nxt displays the progress.
For more information about how to view the logs with BR*Tools, see Showing Profiles and Logs with BR*Tools.