12 ways to upgrade sybase11 If, however, the database upgrade to 12.0 sybase11 previous methods. In accordance with the following steps you can easily do. 1, the first to use sp_helpdevice order to show all the information kept. For example : Device_name physical_name Description Status cntrltype device_number Low High ------------------------------ ---------------------------------------------- ---------------------------------------------------------------------------------- ------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ------ --------- ------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- Staticdb /dev/rvol/dg2/vol03 Special, physical disk, 200.00 MB 2 0 2 33554432 33656831 Staticdb_log /dev/rvol/dg2/vol04 Special, physical disk, 50.00 MB 2 0 3 50331648 2, the use sp_helpdb order to preserve all the same information shows. Name db_size owner dbid Created Status ------------------------ ------------- ------------------------ ------ -------------- ------------------------------------------------------------------------------------------------------ Staticdb 250.0 MB sa 5 Nov. 16, 1999 No options set 3, use sp_helpdb db_name, where db_name is the use of the information displayed sp_helpdb. Preserve all information database inquiries. Prevent mishaps. ^_^ Sp_helpdb staticdb such as : Rev. sp_helpdb staticdb 2>; go Name db_size owner dbid Created Status ------------------------ ------------- ------------------------ ------ -------------- ------------------------------------------------------------------------------------------------------ Staticdb 250.0 MB sa 5 Nov. 16, 1999 No options set Device_fragments size usage free kbytes ------------------------------ ------------- -------------------- ----------- Staticdb MB data only 200,832 200.0 Staticdb_log log only 51,184 50.0 MB (Return status = 0) 4, dump database information. Dump database db_name to "device path." Here is a device path must be written authority of Sybase System users with a list. Contents of a new proposal. For example : "/usr/users/xxxxx." (What? Dump? Canal floor tiles can hit you, backup_server have not played together. ) If you did not do any further 1-4, and when your database upgrade failure (fatal failure) when you can say, "If God will give me a chance, I will. . . . . . . . . . . " I can hit you with floor tiles. At this point you basically only pray for a miracle occurred. ^_^ 5, dumps log : Dump tran db_name with no_log 6, bcp system table information. Select name form sysobjects where type= 'U' will be displayed to preserve. After bcp out all forms of information systems. Bcp master. . Db_name out bcp_db_name -Sserver_name -Usa -Ppasswd -tOnes 6, 12.0 demands master, model, and tempdb database size is 7,3,3m sizes. Therefore, the following should be done is to expand the database. Alter database master on master=xx units Katherine M.. Alter database model on dev_name=xx Alter database tempdb on dev_name=xx 7, 12.0 and the subsequent version of the database must have a sybsystemdb database. So to the existing database created such a database server. First, an initialization equipment. 1>;disk init 2>;name= 'dev_name' physname= '/dev/rvol/dg2/vol19' vdevno=18, size=512000 (ggjjddmm have to be able to read bar ??^_^) 3>;go 8, in just the new equipment and build new database initialization sybsystemdb. Rev. create database sybsystemdb 2>; on dev_name=5 3>; log on dev_name=15 WITH OVERRIDE 4>;go CREATE DATABASE : allocating 2,560 pages on disk 'dev_name' CREATE DATABASE : allocating 7,680 pages on disk 'dev_name' Msg 5018, Level 17, State 1 : Line 1 : Caution : You have set up this database to include space on disk for both 18 Data and the transaction log. This can make recovery impossible if that disk Fails. 9, in addition to the closure of tempdb database library "select. . . . "Every outside the database option. 1>;sp_dboption db_name "option name" false 2>;go 1>;use db_name 2>;go 1>;checkpoint 2>;go Of the database changes. 10, may be connected to the cessation of all database applications. 11, stop in the background may be connected to or installed in the crontab database applications. 12, sa landing to use sp_who to check for the number of users. A user must show only that their own. 13, sqlupgraderes use of the Script Editor document. In this document $SYBASE/ASE-12_0/init/sample_resource_files/upgrade.rs Best upgrade.rs document will make a copy and re-naming, for example : Upgrade_servername.rs, which set up the relevant documents related to the note, they should be able to understand. Sqlupgraderes order to use the database upgrade. Sqlupgraderes r $SYBASE/ASE-12_0/init/sample_resource_files/upgrade_servername.rs Now you had better pray that God will bless you. I wish you every success. If you see 10% of the words, then congratulate you that you have succeeded in upgrading the database. Of course, this In the process of upgrading more slowly, I probably spent 10 minutes in the process of upgrading around. Must not be interrupted because of petulance. So that you can face the fans themselves. ^_^ Oh. Before you forget that in these sybase12.0 the correct installation of a bar. There might have to say is that you should have to upgrade before installing the database places . Cshrc Document that will be installed as the new path to the Sybase database path, and adding a OLDSYBASE environment variables. Needless to say you know it The usefulness of environmental variables were doing! Well, not wordy, I wish you smooth sailing database upgrade. [ Closed window ]