This section assumes that your sybsystemprocs database exists, but is corrupt. If sybsystemprocs does not exist, skip this section; you must create it using create database.
To restore sybsystemprocs with installmaster:
Check to see which devices currently store sybsystemprocs. sp_helpdb probably will not work at this time, but the following query will:
select lstart,
size / (power(2,20)/@@maxpagesize) as 'MB',
d.name as 'device name',
case when segmap = 4 then 'log'
when segmap & 4 = 0 then 'data'
else 'log and data'
end as 'usage'
from sysusages u, sysdevices d
where d.vdevno = u.vdevno
and d.status & 2 = 2
and dbid = db_id('sybsystemprocs')
order by 1
The result probably shows sybsystemprocs all on one disk fragment, and
having log and data as
its usage, but you may have a more complex layout than that. Save
this query’s results for later use.
Drop the database.
drop database sybsystemprocs
If that succeeds and the device is undamaged, go to step 3.
If the drop database fails, perform either:
If sybsystemprocs is badly corrupted, the drop database may fail. In that case, you can remove the database by hand by deleting the information that identifies it:
sp_configure ‘allow updates’, 1
go
delete from sysusages
where dbid = db_id('sybsystemprocs')
delete from sysdatabases
where name = 'sybsystemprocs'
go
sp_configure 'allow updates', 0
go
If the physical disk is damaged, you must drop the device:
sp_dropdevice name_of_sybsystemprocs_device
If you removed sybsystemprocs by hand or recreated the sybsystemprocs device, shut down Adaptive Server using shutdown with nowait. If you dropped the sybsystemprocs device and it was not a raw partition, remove the physical file. Restart Adaptive Server.
Recreate the sybsystemprocs device. If you dropped the sybsystemprocs device, create a new one via disk init. Then recreate sybsystemprocs using one of the methods below using the results you wrote down in step 1.
If you plan to load a backup copy of sybsystemprocs,
you can include the for load option with the create
database or alter database commands.
However, you must use load database to load it
before it can be used for any other purpose.
If the displayed usage was
all log and data, create
a simple database using:
create database sybsystemprocs on device_name = N
where N is the total size from all its previous sections. You may find that you need to create it on multiple devices to get the size you need.
If the displayed usage contains any log or data entries,
recreate this same layout using create database and alter
database. You can group contiguous data or log sections
on a single device, but avoid mixing log with data. Recreate the
first group of data and log sections using create database:
create database sybsystemprocs on device_1 = M log on device_2 = N
where M is the sum of the first group of data sizes and N is the sum of the first group of log sizes. For each successive group, repeat this process using alter database instead of create database to enlarge the database.
Run the installmaster script to create the Sybase-supplied system procedures.
On Unix platforms:
isql -Usa -Ppassword -Sserver_name -i $SYBASE_/$SYBASE_ASE/scripts/installmaster
On Windows (from the %SYBASE%\%SYBASE_ASE%\scripts directory):
isql -Usa -Ppassword -S<server_name> -i instmstr
If your site added any procedures or made other changes in sybsystemprocs, you must make these changes.
