Skip to Content
author's profile photo Former Member
Former Member

Checking dump sizes - data & log separately


Is there any way to check how much space is needed for data and log before loading dump file?

This information would be useful before creating database for load and don't need to alter it with more space after getting error.

Any answers would be appreciated 😊

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    Posted on Dec 14, 2015 at 06:58 PM

    load database

    The "with headeronly" option to load database will give you the size of the database you need to create (in pages) without actually loading the dump. (You can use any database name in the command as it won't actually be loaded).

    You can also work out the order and size of data vs log fragments from the sysusages information that is output by this command. Segmap of 3 is system (1)+default (2) [aka "data"], 4 is log, 7 is data and log.


    1> load database test from "/work/test.dmp" with headeronly

    2> go

    Backup Server session id is: 5. Use this value when executing the

    'sp_volchanged' system stored procedure after fulfilling any volume change

    request from the Backup Server.

    Backup Server: Dumpfile name 'test153090D1FE ' section number 1

    mounted on disk file '/work/test.dmp'


    This is a full database dump

    Name: test

    Id: 7

    Dump date: Nov 5 2015 2:55PM

    Database page size: 4096.

    Number of pages: 5120

    Checkpoint RID: (2625, 1)

    Next object id: 992003534

    Sort order id: 25

    Status: 128

    Charset id: 190

    Database durability: UNDEFINED

    Compression level: N/A

    Database encrypted: NO

    Database Encryption Key: N/A


    Adaptive Server version: Adaptive Server Enterprise/15.7/EBF 23814

    SMP SP134 /P/Sun_svr4/OS 5.10/asecarina/3924/64-bit/FBO/Sa

    Backup Server version: Backup Server/15.7 SP131/EBF 23462/P/Sun_svr4/OS

    5.10/ase157sp131x/4751/32-bit/OPT/Mon Nov 3 15:18

    Database log version: 7

    Database upgrade version: 35

    Dump timestamps:

    Full: 0x0000 00000000

    Cumulative: 0x0000 00000000

    Delta: 0x0000 00000000


    segmap: 0x00000003 lstart=0 vstart=[2, 18432] lsize=1536 unrsvd=630

    segmap: 0x00000003 lstart=1536 vstart=[2, 57344] lsize=1024 unrsvd=1020

    segmap: 0x00000004 lstart=2560 vstart=[2, 59392] lsize=512 unrsvd=494

    segmap: 0x00000004 lstart=3072 vstart=[2, 72704] lsize=2048 unrsvd=2040

    Number of logical pages: 5120 (20 MB)

    Number of physical pages: 5120 (20 MB)


    devtype=0, vdevno=2, devname=datadev1,


    devsize=754688, dbdevsize=5120, vstart=0,

    devstat=2, devstat2=1


    status=0x0005, crdate=Sep 23 2015 3:10PM,

    dumptrdate=Sep 23 2015 5:37PM, status2=0x0000,

    audflags=0x0000, deftabaud=0, defvwaud=0, defpraud=0,

    def_remote_type=0, status3=0x20000, status4=0x4000,

    durablility=1, lobcomp_lvl=0, inrowlen=0,

    dcompdefault=1 status5=0x0000


    flmode: 0x0004

    Features found in the database or transaction dump header:

    ID = 4 : : Database has system catalog changes made in 15.7 GA

    ID = 7 : : Database has system catalog changes made in 15.7


    ID = 11 : : Database has the Sysdams catalog

    The database you are attempting to LOAD was DUMPed under a different sort order

    ID (25) or character set ID (190) than the ones running on this server (SortOrd

    = 50, CharSet = 1). If the sort orders differ, at least one of them is


    If you have dump history configured, you can use the "with create_sql" option to actually generate the scripts to create the database.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 14, 2015 at 07:05 PM

    Although Bret's answer works.....a much much simpler solution is:

    load database <dbname> from <dumpdevices> with listonly=create_sql

    ...then you might want to try

    load database <dbname> with listonly=load_sql

    See examples on page 557 of ASE Commands Ref.

    Add a comment
    10|10000 characters needed characters exceeded

    • You'll need 15.7 ESD#2 (or higher) to use the 'create_sql' feature.

      I believe (but not 100% sure) you need 15.7 ESD#2 (or higher) for both a) the creation of the dump file (to add the necessary details to the dump file header) and b) the reading of the dump file (to read the details from the dump file header).

  • Posted on Dec 15, 2015 at 03:36 PM

    Hello Thomas,

    It doesn't look like this is about SAP ASE for Business Suite? I don't remember ESD #1 was certified for BS.

    Could you confirm? So I'll move the thread to SAP Adaptive Server Enterprise (SAP ASE) for Custom Applications to avoid confusion 😊

    Thank you!



    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.