Quantcast
Channel: SCN : All Content - SAP Applications on SAP Adaptive Server Enterprise (SAP ASE)
Viewing all articles
Browse latest Browse all 956

Can't truncate log although it looks empty

$
0
0

Hello Sybase gurus,

 

I have an ASE 15.02, running on windows server 2008. A replica database "mcall" acts as if it has log full. Transactions / replication stopped.

 

I try:

dump tran mcall with truncate_only

and

dump tran mcall with no_log

 

They both report:

DUMP TRANSACTION for database 'mcall' could not truncate the log. Either extend the log using ALTER DATABASE ... LOG ON command or eliminate the oldest active transaction in database 'mcall' shown in syslogshold table.

 

I tried to extend the log, to no avail.

In fact, the log seems to be empty. I try:

 

dbcc checktable ('syslogs')

 

It reports the following:

 

Checking table 'syslogs' (object ID 8): Logical page size is 2048 bytes.

 

Checking partition 'syslogs_8' (partition ID 8) of table 'syslogs'. The logical page size of this table is 2048 bytes.

The total number of data pages in partition 'syslogs_8' (partition ID 8) is 1.

Partition 'syslogs_8' (partition ID 8) has 15 data rows.

 

 

The total number of data pages in this table is 1.

*** NOTICE: Space used on the log segment is 17201 pages (33.60 MB), 0.39%.

*** NOTICE: Space reserved on the log segment is 0 pages (0.00 MB), 0.00%.

*** NOTICE: Space free on the log segment is 4385999 pages (8566.40 MB), 99.61%.

Table has 15 data rows.

Msg 1105, Level 17, State 4:

Server 'WDBASE10', Line 3:

Can't allocate space for object 'syslogs' in database 'mcall' because 'logsegment' 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 the segment.

DBCC execution completed. If DBCC printed error messages, contact a user with System Administrator (SA) role.

 

 

I try:

select * from syslogshold

 

 

It shows 0 rows.

 

 

Per Sybase troubleshooting guide, I checked sysusages; unreservedpgs column for this database does not have any NULL value.

 

 

Also ran (just in case):

dbcc settrunc (ltm, ignore)

 

 

it shows:

secondary trunc page secondary trunc state dbrepstat generation id database id database name                  ltl version

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

             10580254                     0       166             1           5 mcall                                  720

 

 

Has anyone encountered such a situation, or has any other thoughts?

 

 

Thanks much!


Viewing all articles
Browse latest Browse all 956

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>