![]() ![]() Restart SAP ASE in normal (multiuser) mode.Ĭheck your hard copy of syslogins and your restored syslogins table.Ĭompare your hard copy versions of system tables with the versions of the system tables you brought online in the restored databases. If you have backed up the master database since issuing the most recent disk init, create database, or alter database command, then the contents of sysusages, sysdatabases, and sysdevices match your hard copy. Checking System Tables to Verify Current Backup of master.Use startserver to restart SAP ASE in master-recover mode. ![]() Restarting SAP ASE in Master-Recover Mode.You must update the number of devices configuration parameter if you use more than the default number of database devices. Updating the number of devices Configuration Parameter.Load the most recent backup of the master database. On UNIX platforms, use the showserver command to verify that Backup Server is running restart the server if necessary. Verifying That Your Backup Server Is Running.You must verify that sysservers includes the correct information. Checking Your Backup Server sysservers Information.If you re-created your master device according to the process described in Rebuilding a New Master Device, your master database may be too small. Re-creating Device Allocations for master.Start SAP ASE in master-recover mode with the dataserver -m (UNIX and Windows) option. Starting SAP ASE in Master-Recover Mode.Otherwise, you can re-create the master and model databases on your existing master device. ![]() To restore a damaged master device, follow the recovery steps below, or use the sybrestore utility.įind copies of the system tables that you have saved to a file: sysdatabases, sysdevices, sysusages, sysloginroles, and syslogins.īuild a new master device only if your old master device is damaged beyond repair. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |