Skip to Content

Sybase Ase, Log Database Extend "DBIF_RSQL_SQL_ERROR dump"

Dear Ase Gurus,

We are taking dump like DBIF_RSQL_SQL_ERROR,

Short Text

    SQL error 1105 occurred while accessing table "ALCLASTOOL".

What happened?

    Database error text: "[ASE Error SQL1105]Can't allocate space for object

     'ALCLASTOOL' in database 'HCP' because 'default' segment is full/has no free

     extents. If you ran out of space in syslogs, dump the transaction log.

     Otherwise, use ALTER DATABASE to increase the size of th".

When i check space on db,

sp_helpdb HCP

go

Returns screen shot

Not appliable mean : Not enough space for log database sure ?

Should increase log.database with this command ? And should i restart Sybase Ase and SAP ?

disk resize name ="HCP_log_002" , size="15G"

Best Regards

db.png (12.5 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Dec 30, 2014 at 04:10 PM
    16

    This particular issue doesn't appear to be related to the log.

    The error message states the 'default' segment is full.  This is the *data* portion of your database.

    Your sp_helpdb output shows all of the 'data only' fragments have 0/zero free space available, ie, this confirms the error message that you're run out of space for new *data*.

    You need to add some more *data* space to your database via the 'alter database' command. (The alternative is to find some data to delete and/or drop unwanted tables/indexes.)

    --------------

    You can check your log space usage by running: exec HCP..sp_helpsegment logsegment

    --------------

    There is no need to restart ASE ... at least not for this particular issue.

    Add comment
    10|10000 characters needed characters exceeded

    • Well, if that last image is a snapshot of the output from running 'sp_helpdb HCP' ... then it's showing that you keep adding the saptools* devices to the HCP database, ie, you're *NOT* adding the saptools* devices to the saptools database.

      My guess is that you keep issuing "alter database HCP ..." while trying to increase the the size of the saptools databases.

      When you should have been issuing "alter database saptools ..." in order to increase the size of the saptools database.

      NOTICE the name of the database in included in the command 'alter database <dbname>' ... where <dbname> = HCP if you want to increase the size of the HCP database ... where <dbname> = saptools if you want to increase the size of the saptools database.

      --------------------

      From your latest sp_helpdb output it would appear that you've added the following to the HCP database today:

      HCP_data_001             = 10GB (as data)

      HCP_data_002             = 10GB (as data)

      saptools_log_001         =  1GB (as data)

      saptools_data_001        =  1GB (as data)

      saptools_tempdb_data_001 =  1GB (as data)

      HCP_log_001              = 10GB (as log)

      HCP_log_002              = 10GB (as log)

      saptools_data_001        =  1GB (as data)

      That's a total of 24GB added as data, plus 20GB added as log ... to the HCP database.

      This would seem to match up with your DBA Cockpit output that shows ... for the HCP database:

      - 23GB free in the data segment (ie, you've already used up 1GB of the 24GB you allocated today)

      - 40GB free in the logsegment (ie, you increased the log size from 20GB to 40GB even though you likely did not have a problem with the log being filled up)

      And because you haven't been using the correct command (ie, "alter database saptools ...."), the size of your saptools database has not been increased (ie, the saptools database is still full as per DBA Cockpit).

      To verify what I just said, try running the following at the isql prompt ...

      =====================

      use master

      go


      -- to get device allocations for the HCP database:

      exec sp_helpdb HCP

      go


      -- to get device allocations for the saptools database:

      exec sp_help saptools

      go

      =====================

      ... and see what shows up in the output for each of the databases (HCP vs saptools).

  • Jan 05, 2015 at 01:12 PM

    Hi Kemal,
    This has already a lot of replies, let just summarize.

    1) the "not applicable" you see on a sp_helpdb for log segment doesn't means "Not enough space for log". It is always returned for any log segment (let say that free space of transaction log cannot be estimated while transactions are running).

    2) The error : "

    Database error text: "[ASE Error SQL1105]Can't allocate space for object

         'ALCLASTOOL' in database 'HCP' because 'default' segment is full/has no free

         extents. If you ran out of space in syslogs, dump the transaction log.

         Otherwise, use ALTER DATABASE to increase the size of th".

    "

    indicated that your "data" segment (not the log segment) was fullfiled. You have been instructed about how to increase the data segment.

    3) for the data segment fullfiled on database "saptools", your DBACockpit screenshot is showing that the data segment of "saptools" is full, and the output you sent from command line is about the available space on device saptools_data_001 (1gb) but the other 1Gb marked red has been added to saptempdb_data_001 that is a saptempdb database device.

    As mentioned Mark an sp_helpdb would help to understand which devices are used for each databases, or a snapshot from your DBA Cockpit ( go to Database HCP -> Space -> Databases -> click on HCP (or saptools) -> tab "Devices" )

    For information about free spaces on "saptools" database, you may check Note 1836607 - SYB: How to solve error 1105 in database "saptools".


    Just for the record:  you can avoid such error 1105, to use the Automatic Database Extension feature.

    HTH,
    Best regards,

    Victoria.


    Add comment
    10|10000 characters needed characters exceeded