Sybase's Master Library log Management

How should the Sybase Master log be cleared when it is full?

You can manage the master library in the following ways, and if you do not have enough space, consider expanding the master library.

1, simple case of the dump trans with no_log on it, Master Library will not be full.

1> Use Master

2> Go

1> checkpoint

2> Go

1> dump Tran Master with NO_LOG

2> Go

00:00000:00011:2006/02/22 14:53:38.06 Server WARNING: *************************

**

00:00000:00011:2006/02/22 14:53:38.06 Server attempt by user 1 to dump XACT on

DB Master with No_log

00:00000:00011:2006/02/22 14:53:38.06 Server attempt by user 1 to dump XACT on

DB Master with NO_LOG is successful

00:00000:00011:2006/02/22 14:53:38.06 Server WARNING: *************************

**

2, if it is a Windows platform, then find Run_your_server_name.bat

If it is a UNIX platform, locate the Run_your_server_name file

Edit the boot file above, add-t3067 at end of line

Then use the startup file to start the database, and then start

Dump Tran Master with Truncate_onlyu

Go

1) Backup master database

Dump DATABASE Master to ' backup path and filename '

2) Stop Sybase Service

Shutdown

3 Edit the Sybase service startup file (typically the "Run_ service name" file under UNIX, which is typically a batch file under Windows "Run_ Service name. bat"). At the end of the command line of the startup file, add-t3607)

4 after starting the service with the boot file, then dump Tran Master with TRUNCATE_ONLY

5 at this time the dump cleanup log will generally be more successful. Then stop the shutdown service, remove the-t3607, and start the service in the normal way

3, if not, you need to establish a device for expansion or reconstruction as follows:

1) Backup master database

Start Backup server and enter ISQL environment execution:

1>dump database Master to '/sybase/master.dump '

2>go

(Dump log with no log if not possible)

Hut down Sql/ase Server

1>shutdown

2>go

2 Create a new master device that is large enough

$buildmaster-D-ssize (size is 2K)

Example: $buildmaster-d/sybase/database/master.dat-s102400

3) Modify Run_servername file

Edit the Run_server_name file, and the-D argument points to the newly created device name.

4 Single user mode restart server

$startserver-F Run_servername-m

5) Execute Installmaster script

6 load master database from backup file

1>load database Master from '/sybase/master.dump '

2>go

7) Modify sysdevices information

sp_configure ' allow updates ', 1

Go

BEGIN Tran

Go

Update sysdevices Set high = 102399, phyname = ' E:\sybase\data\master_test.dat ' WHERE name = ' master '

Go

(102399=200*512-1 master device size is 200M)

Commit Tran

Go

8) Extend master database

1>alter database master on master device name =size (this value is in m)

2>go

Example: Alter DATABASE master on MASTER=10

Extend the master database on a master device 10M

This operation is more dangerous, pay attention to the first backup (such as GHOST)