DBVerify Called with a Segment_id Fails with Segmentation Fault (Doc ID 1323405.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Server - Enterprise Edition - Version: 9.2.0.1 to 11.2.0.2 - Release: 9.2 to 11.2
Information in this document applies to any platform.

Symptoms

In order to check an object like SYS.I_OBJ1, you are using DBV with an additional parameter SEGMENT_ID and this fails like in the following example:

% sqlplus / as sysdba
SQL> select t.ts#, s.header_file, s.header_block, t.name ,s.owner, s.segment_name
  from v$tablespace t, dba_segments s
  where t.name='SYSTEM'
  and s.owner='SYS'
  and s.segment_name='I_OBJ1'
  and t.name = s.tablespace_name;

      TS# HEADER_FILE HEADER_BLOCK       NAME         OWNER  SEGMENT_NAME
---------- ----------- ------------ -------------------------- -------------- ---------- --------------------------------------------------------------------
        0           1          336                                          SYSTEM     SYS         I_OBJ1


% dbv USERID=user/password SEGMENT_ID=0.1.336

DBVERIFY: Release 11.2.0.2.0 - Production on Wed May 11 07:11:48 2011

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

DBVERIFY - Verification starting : SEGMENT_ID = 0.1.336
Memory fault

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms