Summary of Subprograms

Table 50-1 DBMS_SPACE_ADMIN Package Subprograms

SEGMENT_VERIFY Procedure

SEGMENT_CORRUPT Procedure

SEGMENT_DROP_CORRUPT 
Procedure

SEGMENT_DUMP Procedure

TABLESPACE_VERIFY Procedure

TABLESPACE_FIX_BITMAPS 
Procedure

TABLESPACE_REBUILD_BITMAPS 
Procedure

TABLESPACE_REBUILD_QUOTAS 
Procedure

TABLESPACE_MIGRATE_FROM_LOCAL 
Procedure

TABLESPACE_MIGRATE_TO_LOCAL 
Procedure

TABLESPACE_RELOCATE_BITMAPS 
Procedure

TABLESPACE_FIX_SEGMENT_STATES 
Procedure 

SEGMENT_VERIFY Procedure

This procedure verifies that the extent map of the segment is consistent with the bitmap.

Syntax

DBMS_SPACE_ADMIN.SEGMENT_VERIFY (
   tablespace_name         IN    VARCHAR2,
   header_relative_file    IN    POSITIVE,
   header_block            IN    POSITIVE,
   verify_option           IN    POSITIVE  DEFAULT SEGMENT_VERIFY_EXTENTS);

Parameters

Table 50-2 SEGMENT_VERIFY Procedure Parameters

tablespace_name

header_relative_file

header_block

verify_option

Usage Notes

Anomalies are output as dba-range, bitmap-block, bitmap-block-range, anomaly-information, in the trace file for all dba-ranges found to have incorrect space representation. The kinds of problems which would be reported are free space not considered free, used space considered free, and the same space considered used by multiple segments.

Example

The following example verifies that the segment with segment header at relative file number 4, block number 33, has its extent maps and bitmaps in sync.

EXECUTE DBMS_SPACE_ADMIN.SEGMENT_VERIFY('USERS', 4, 33, 1); 

SEGMENT_CORRUPT Procedure

This procedure marks the segment corrupt or valid so that appropriate error recovery can be done.

Syntax

DBMS_SPACE_ADMIN.SEGMENT_CORRUPT (
   tablespace_name         IN    VARCHAR2,
   header_relative_file    IN    POSITIVE,
   header_block            IN    POSITIVE,
   corrupt_option          IN    POSITIVE  DEFAULT SEGMENT_MARK_CORRUPT);

Parameters

Table 50-3 SEGMENT_CORRUPT Procedure Parameters

tablespace_name

header_relative_file

header_block

corrupt_option

Example

The following example marks the segment as corrupt:

EXECUTE DBMS_SPACE_ADMIN.SEGMENT_CORRUPT('USERS', 4, 33, 3); 

Alternately, the next example marks a corrupt segment valid:

EXECUTE DBMS_SPACE_ADMIN.SEGMENT_CORRUPT('USERS', 4, 33, 4); 

SEGMENT_DROP_CORRUPT Procedure

This procedure drops a segment currently marked corrupt (without reclaiming space). For this to work, the segment should have been marked temporary. To mark a corrupt segment as temporary, issue a DROP command on the segment.

The space for the segment is not released, and it must be fixed by using the TABLESPACE_FIX_BITMAPS or TABLESPACE_REBUILD_BITMAPS procedure. These are described later in this chapter.

Syntax

DBMS_SPACE_ADMIN.SEGMENT_DROP_CORRUPT (
   tablespace_name         IN    VARCHAR2,
   header_relative_file    IN    POSITIVE,
   header_block            IN    POSITIVE);

Parameters

Table 50-4 SEGMENT_DROP_CORRUPT Procedure Parameters

tablespace_name

header_relative_file

header_block

Example

EXECUTE DBMS_SPACE_ADMIN.SEGMENT_DROP_CORRUPT('USERS', 4, 33); 

SEGMENT_DUMP Procedure

This procedure dumps the segment header and extent map blocks of the given segment.

Syntax

DBMS_SPACE_ADMIN.SEGMENT_DUMP (
   tablespace_name         IN    VARCHAR2,
   header_relative_file    IN    POSITIVE,
   header_block            IN    POSITIVE,
   dump_option             IN    POSITIVE  DEFAULT SEGMENT_DUMP_EXTENT_MAP);

Parameters

Table 50-5 SEGMENT_DUMP Procedure Parameters

tablespace_name

header_relative_file

header_block

dump_option

Example

EXECUTE DBMS_SPACE_ADMIN.SEGMENT_DUMP('USERS', 4, 33); 

TABLESPACE_VERIFY Procedure

This procedure verifies that the bitmaps and extent maps for the segments in the tablespace are in sync.

Syntax

DBMS_SPACE_ADMIN.TABLESPACE_VERIFY (
   tablespace_name         IN    VARCHAR2,
   verify_option           IN    POSITIVE DEFAULT TABLESPACE_VERIFY_BITMAP);

Parameters

Table 50-6 TABLESPACE_VERIFY Procedure Parameters

tablespace_name

verify_option

Example

EXECUTE DBMS_SPACE_ADMIN.TABLESPACE_VERIFY('USERS'); 

TABLESPACE_FIX_BITMAPS Procedure

This procedure marks the appropriate DBA range (extent) as free or used in bitmap.

Syntax

DBMS_SPACE_ADMIN.TABLESPACE_FIX_BITMAPS (
   tablespace_name         IN    VARCHAR2,
   dbarange_relative_file  IN    POSITIVE,
   dbarange_begin_block    IN    POSITIVE,
   dbarange_end_block      IN    POSITIVE,
   fix_option              IN    POSITIVE);

Parameters

Table 50-7 TABLESPACE_FIX_BITMAPS Procedure Parameters

tablespace_name

dbarange_relative_file

dbarange_begin_block

dbarange_end_block

fix_option

Example

The following example marks bits for 50 blocks for relative file number 4, beginning at block number 33 and ending at 83, as USED in bitmaps.

EXECUTE DBMS_SPACE_ADMIN.TABLESPACE_FIX_BITMAPS('USERS', 4, 33, 83, 7); 

Alternately, specifying an option of 8 marks the bits FREE in bitmaps. The BEGIN and END blocks should be in extent boundary and should be extent multiple. Otherwise, an error is raised.

TABLESPACE_REBUILD_BITMAPS Procedure

This procedure rebuilds the appropriate bitmap(s). If no bitmap block DBA is specified, then it rebuilds all bitmaps for the given tablespace.

Syntax

DBMS_SPACE_ADMIN.TABLESPACE_REBUILD_BITMAPS (
   tablespace_name         IN    VARCHAR2,
   bitmap_relative_file    IN    POSITIVE   DEFAULT NULL,
   bitmap_block            IN    POSITIVE   DEFAULT NULL);

Parameters

Table 50-8 TABLESPACE_REBUILD_BITMAPS Procedure Parameters

tablespace_name

bitmap_relative_file

bitmap_block

Example

The following example rebuilds bitmaps for all the files in the USERS tablespace.

EXECUTE DBMS_SPACE_ADMIN.TABLESPACE_REBUILD_BITMAPS('USERS'); 

TABLESPACE_REBUILD_QUOTAS Procedure

This procedure rebuilds quotas for the given tablespace.

Syntax

DBMS_SPACE_ADMIN.TABLESPACE_REBUILD_QUOTAS (
   tablespace_name         IN    VARCHAR2);

Parameters

Table 50-9 TABLESPACE_REBUILD_QUOTAS Procedure Parameters

tablespace_name

Example

EXECUTE DBMS_SPACE_ADMIN.TABLESPACE_REBUILD_QUOTAS('USERS'); 

TABLESPACE_MIGRATE_FROM_LOCAL Procedure

This procedure migrates a locally-managed tablespace to a dictionary-managed tablespace.

Syntax

DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_FROM_LOCAL (
   tablespace_name         IN    VARCHAR2);

Parameter

Table 50-10 TABLESPACE_MIGRATE_FROM_LOCAL Procedure Parameter

tablespace_name

Usage Notes

The tablespace must be kept online and read write during migration. Migration of temporary tablespaces and migration of SYSTEM tablespaces are not supported.

Example

EXECUTE DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_FROM_LOCAL('USERS'); 

TABLESPACE_MIGRATE_TO_LOCAL Procedure

Use this procedure to migrate the tablespace from dictionary managed format to locally managed format. Tablespaces migrated to locally managed format are user-managed.

Syntax

TABLESPACE_MIGRATE_TO_LOCAL(tablespace_name, allocation_unit, relative_fno)

Parameters

Table 50-11 Parameters for TABLESPACE_MIGRATE_TO_LOCAL

Parameter Name	Purpose	Datatype	Parameter Type
Tablespace Name	Name of the tablespace to be migrated.	VARCHAR	IN
Allocation Unit	Unit size (which is the size of the smallest possible chunk of space that can be allocated) in the tablespace.	INTEGER	IN
Relative File Number	Relative File Number of the file where the bitmap blocks should be placed (optional)	INTEGER	IN

Note on Allocation Unit

Allocation Unit may be specified optionally. The default is calculated by the system based on the highest common divisor of all extents (used or free) for the tablespace. This number is further trimmed based on the MINIMUM EXTENT for the tablespace (5 if MINIMUM EXTENT is not specified). Thus, the calculated value will not be larger than the MINIMUM EXTENT for the tablespace. The last free extent in every file will be ignored for GCD calculation. If you specify the unit size, it has to be a factor of the UNIT size calculated by the system, otherwise an error message is returned.

Note on Relative File Number

The Relative File Number parameter is used to place the bitmaps in a desired file. If space is not found in the file, an error is issued. The datafile specified should be part of the tablespace being migrated. If the datafile is not specified then the system will choose a datafile in which to place the initial bitmap blocks. If space is not found for the initial bitmaps, an error will be raised.

Usage Notes

The tablespace must be kept online and read write during migration. Note that temporary tablespaces cannot be migrated. Migration of SYSTEM tablespace is not permitted in this release.

Example

To migrate a tablespace 'TS1' with minimum extent size 1m, use

execute dbms_space_admin.tablespace_migrate_to_local('TS1', 512, 2);

The bitmaps will be placed in file with relative file number 2.

TABLESPACE_RELOCATE_BITMAPS Procedure

Use this procedure to relocate the bitmaps to the destination specified. Migration of a tablespace from dictionary managed to locally managed format could result in the creation of SPACE HEADER segment that contains the bitmap blocks. The SPACE HEADER segment is treated as user data. If the user wishes to explicitly resize a file at or below the space header segment, an error is issued. Use tablespace_relocate_bitmaps command to move the control information to a different destination and then resize the file.

Syntax

TABLESPACE_RELOCATE_BITMAPS (Tablespace_Name, Relative_fno, Block_Number)

Parameters

Table 50-12 Parameters for TABLESPACE_RELOCATE_BITMAPS

Parameter Name	Purpose	Datatype	Parameter Type
Tablespace_Name	Name of Tablespace.	VARCHAR	IN
RFNO	Relative File Number of the destination file.	NUMBER	IN
BLKNO	Block Number of the destination dba.	NUMBER	IN

Usage Notes

The tablespace must be kept online and read write during relocation of bitmaps. Can be done only on migrated locally managed tablespaces.

Example

execute  dbms_space_admin.tablespace_relocate_bitmaps('TS1', 3, 4);

Moves the bitmaps to file 3, block 4.

TABLESPACE_FIX_SEGMENT_STATES Procedure

Use this procedure to fix the state of the segments in a tablespace in which migration was aborted. During tablespace migration to or from local, the segments are put in a transient state. If migration is aborted, the segment states are corrected by SMON when event 10906 is set. Database with segments is such a transient state cannot be downgraded. The procedure can be used to fix the state of such segments.

Syntax

TABLESPACE_FIX_SEGMENT_STATES(Tablespace_Name);

Parameter

Table 50-13 Parameter for TABLESPACE_FIX_SEGMENT_STATES

Parameter Name	Purpose	Datatype	Parameter Type
Tablespace_Name	Name of the tablespace whose segments needs to be fixed.	VARCHAR	IN

Usage Notes

The tablespace must be kept online and read write when this procedure is called.

Example

execute dbms_space_admin.tablespace_fix_segment_states('TS1');

Further Examples

1. TABLESPACE_VERIFY has discovered that some segment has allocated blocks which are marked free in the bitmap, but no overlap between segments was reported. In this case, the following actions are recommended:
   • Call SEGMENT_EXTENT_MAP_DUMP procedure to dump the DBA ranges allocated to the segment.

   • For each range, call TABLESPACE_FIX_BITMAPS with the TABLESPACE_MAKE_USED option to mark the space as used.

   • Call TABLESPACE_REBUILD_QUOTAS to fix up quotas.

2. Segment could not be dropped because the bitmap has some of the segment blocks marked free. The system has automatically marked it corrupted. In this case, do the following:
   • Call SEGMENT_VERIFY procedure with the SEGMENT_CHECK_ALL options. If no overlaps were reported, then do the following:
     • Call SEGMENT_EXTENT_MAP_DUMP procedure to dump the DBA ranges allocated to the segment.

     • For each range, call TABLESPACE_FIX_BITMAPS with the TABLESPACE_MAKE_FREE option to mark the space as free.

     • Call SEGMENT_DROP_CORRUPT to drop the SEG$ entry.

     • Call TABLESPACE_REBUILD_QUOTAS to fix up quotas

3. TABLESPACE_VERIFY has reported some overlaps. In this case, some of the real data will need to be sacrificed, perhaps, based on the previous internal errors. After the victim object is chosen, table T1, do the following:
   • Make a list of all objects which T1 overlaps.

   • Drop T1 using SQL. If necessary, then follow up by SEGMENT_DROP_CORRUPT.

   • Call SEGMENT_VERIFY on all objects that T1 has overlapped. If necessary, then call TABLESPACE_FIX_BITMAPS to mark appropriate bitmap blocks as used.

   • Rerun TABLESPACE_VERIFY.

4. A set of bitmap blocks is media corrupt. Do the following:
   • Call TABLESPACE_REBUILD_BITMAPS, either on all bitmap blocks or on a single block, if only one block is corrupt.

   • Call TABLESPACE_REBUILD_QUOTAS to rebuild quotas.

   • Call TABLESPACE_VERIFY to check if the bitmaps are consistent.