SAP Knowledge Base Article - Preview

2374339 - Database dump file size does not shrink after dropping all tables in database - ASE

Symptom

  • Dropped all user tables in a database in ASE
  • Database log has been truncated prior to dumping database
  • Issuing the following commands to dump the database:

exec sp_dumpoptimize 'archive_space = maximum'
go

DUMP DATABASE db_firmprod TO '/sybase/sybdump/SYBASE_DUMP/dump1of10.FULL.112414_2016'
STRIPE ON '/sybase/sybdump/SYBASE_DUMP/dump2of10.FULL.112414_2016'
STRIPE ON '/sybase/sybdump/SYBASE_DUMP/dump3of10.FULL.112414_2016'
.
.
.
STRIPE ON '/sybase/sybdump/SYBASE_DUMP/dump9of10.FULL.112414_2016'
STRIPE ON '/sybase/sybdump/SYBASE_DUMP/dump10of10.FULL.112414_2016'
with compression=4
go

exec sp_dumpoptimize 'archive_space = default'
go

  • Database dump file is still the same size prior to dropping all tables

Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 15.7
  • SAP Adaptive Server Enterprise (ASE) 16.0

Product

SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0

Keywords

KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem

About this page

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

Search for additional results

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