SAP Knowledge Base Article - Preview

1899592 - dbcc extentzap and dbcc extentcheck report "open failed" error- SAP ASE

Symptom

dbcc extentzap and dbcc extentcheck may run into following error  if the target object has been removed from sysobjects.

dbid <dbid> objid <objid> open failed

Example:

dbid '4' objid '576002052' open failed


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 15.7

Product

SAP Adaptive Server Enterprise 15.7

Keywords

orphaned allocation pages, orphaned extents, extent deallocation, metadata inconsistency, invalid object identifier, missing system catalog entry, index catalog cleanup, allocation map, extent map cleanup, catalog corruption prevention, space management, orphan page cleanup, extent metadata repair, storage allocation anomaly, partition maintenance, dbcc, extentzap, extentcheck, open failed, checkalloc, 618451 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.