Quantcast
Channel: SCN: Message List - SAP Adaptive Server Enterprise (SAP ASE) for Custom Applications
Viewing all articles
Browse latest Browse all 3587

Re: user databse log segemnt filling up when no active transaction present

$
0
0

OK, so you're only seeing this 'log full' issue in your PDB, right?

 

How many PDBs are showing this 'log full' issue?

 

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

 

Pick a PDB that is having the 'log full' issue.

 

Place the following in a file (eg, get_data.sql), making sure to replace all occurrences of 'DBNAME' with the name of the PDB, and provide a complete path for the 'dump tran /to_file' command:

 

============================= get_data.sql

use DBNAME

go

 

exec master..sp_helpdb DBNAME

go

 

select 'TimeStamp1' = convert(varchar,getdate(),109)

select * from master..syslogshold where dbid = db_id()

exec sp_help_rep_agent DBNAME

exec sp_helpsegment logsegment

go

 

dump tran DBNAME to ".... enter dump file path here ...."

go

 

select 'TimeStamp2' = convert(varchar,getdate(),109)

select * from master..syslogshold where dbid = db_id()

exec sp_help_rep_agent DBNAME

exec sp_helpsegment logsegment

go

 

dump tran DBNAME with no_log

go

 

select 'TimeStamp3' = convert(varchar,getdate(),109)

select * from master..syslogshold where dbid = db_id()

exec sp_help_rep_agent DBNAME

exec sp_helpsegment logsegment

go

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

 

The next time the log gets up to 80%, submit the above script via isql:

 

     isql -S... -U... -P... -i get_data.sql -o get_data.txt -e

 

NOTE: Obviously (?) you'll need to have performed a full db dump before you can issue the 'dump tran /to_file' command.

 

Then reply to this forum thread with the entire contents of the output file (get_data.txt) as an attachment.


Viewing all articles
Browse latest Browse all 3587

Trending Articles



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