Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

master log segment full URGENT!

1,516 views
Skip to first unread message

masood....@citicorp.com

unread,
Feb 18, 2000, 3:00:00 AM2/18/00
to
Hi,
I got the following message in the Sybase SQL Server errorlog:
Space available in the log segment has fallen critically low in database
'master'. All future modifications to this database will be suspended
until the log is successfully dumped and space becomes available.

"dump database" does not free any space in the logsegment.
I guess the problem is with master database being different from user
databases.
I created a new device "temp_log" and I started the server in single
user mode with transaction logging off. But then how can I extend the
master database (to another device, say)?
"alter database master on temp_log"
fails with
"Cannot extend the MASTER database onto any device other than 'master'.
The ALTER DATABASE was aborted."

This means that I cannot try either of these -
"sp_extendsegment logsegment , master , temp_log"
nor
"sp_logdevice master, temp_log"

What can I do? Will greatly appreciate help!

Regards
Masood Faruqui

masood....@citicorp.com


Sent via Deja.com http://www.deja.com/
Before you buy.

kohi...@my-deja.com

unread,
Feb 21, 2000, 3:00:00 AM2/21/00
to masood....@citicorp.com
Hi Masood,

I guess there is a way out. But I assume that you are very sure that
the log of master database is full and not any user database.

Here's what you should do :

1) Log off all users
2) Shutdown the server
3) Start the server in single user mode
4) extend the master database by 2MB's with the following command :
alter database master on master = 2
5) shutdown the server
6) restart the server
7) do a dump tran in the master database
8) release to users

And now the important thing. Normally there are'nt many logged
operations that take place on the master database. So how did your
master database fill up ? Please look up if some user objects exists in
the master and if they exist then remove them immediately and striclty
ensure that this does not happen in the future. This can be a
case of security violation also because somebody with 'sa' role can only
fiddle with the master.

Please remember that master database cannot be extended on any device.
It has to be the master device only. This master device is created only
during the time of installation and can be from 16MB - 30MB depending
on the version of Sybase SQL Server. However the master database
generally does not occupy the full device. Other databases created on
the master device include model and tempdb. Since some space is usually
left extending the master database is possible. BUT USUALLY THERE IS NO
SUCH REQUIREMENT. So if the log in master is full, I suggest you do a
thorough analysis for its cause.

Best wishes

Ejaz Ahmed
ej...@hotmail.com

In article <88jfo4$sfv$1...@nnrp1.deja.com>,

Babu

unread,
Feb 21, 2000, 3:00:00 AM2/21/00
to

I think your master transaction logs are accumulating either you are
not clearing it using dump tran or setting dboption 'trunc log on chkpt'
dump database never clears transaction log for any database. so you
need to run 'dump tran' to clear log.
so first try clearing master tran log using dump tran and see whether
it helps to solve your problem

Babu

0 new messages