12-01-2017 8:12 AM - edited 02-04-2024 1:28 AM
Hi Guys,
My customer has a ASE 1254 for Windows and recently she found the database logsegment got full quickly but the user database has 9GB logsegment space,
only last 4GB logsegment space seemed used and dump tran can not free up more logsegment space.
I have sugggested her to use dbcc usedextents and dbcc tablealloc(syslogs,full,fix) to fix the problem, how the result is it is still showed 4GB logsegment on sp_helpdb.
Any idea, what is going on the user database.
Please help to advise, any comment is thankful.
Best Regards,
Robert
<< our fix steps >>
1. verify full backup is completed
2. change user database to 'single user mode' :
use master
go
sp_dboption fsdb,’single user’,true
go
use fsdb
go
checkpoint
go
/* confirm the user database in single user mode now */
sp_helpdb fsdb
go
3. issue dbcc command to fix the problem :
dbcc traceon(3604)
go
dbcc tablealloc(syslogs, full, fix)
go
4. change user database to 'multiple user mode' :
use master
go
sp_dboption fsdb,’single user’,false
go use fsdb
go
checkpoint
go
Hi Mark,
There is no long running transactions in this problem database,
and sp_helpsegment logsegment also did not show negative values.
I attached sysusages and sp_helpsegment results for your reference.
Thanks again for your advice.
Best Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rong,
Check if dbcc gam() can fix this issue ?
Below is the beautiful article by Mr Bret:
https://wiki.scn.sap.com/wiki/display/SYBASE/DBCC+gam
Regards
Kiran K Adharapuram
User | Count |
---|---|
94 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.