How to Copy a 5.1 or 5.2 StarTeam Repository with an Oracle Database Backend
Information in this Brief applies to:
Sometimes it may be important to move or copy a StarTeam Repository or its parts to a new Physical Server machine. To successfully achieve this goal you will need to copy all the essential StarTeam Repository and Database files to the target destination recreating the same configuration on a new machine. It is recommended that the Repository be copied as opposed to moved, to minimize the down time and assure that the target destination is fully functional before deleting the original repository files.
Please carefully test your modified repository configuration before disabling or deleting the old repository and configuration.
The steps for moving a 5.1 or 5.2 repository are slightly different than moving 3.x and 4.x repositories.
It is best, to move all of the repository to the same relative location. For example, on a Windows platform, you would want to copy the entire repository from its old location C:\Starteam_Repository on the original server machine to the new Starteam server at the same relative location C:\Starteam_Repository. The StarTeam Repository is the startup path location for the Starbase Server configuration, it is where the Server.Log will be created and all of the Vault Archive Files, Attachments and Vault Cache files are kept.
1. Before you move a Repository, make certain all the appropriate Repository items are backed up. The back up of the Database on Oracle Server and the File System (Attachments, Logs and Vault files) should all be created at the same time. It is important that this back up occurs while StarTeam is either locked or ideally, not running so no one is using the Starbase server.
1a. Make sure that you are backing up the database at the same time you are copying the Repository, it is imperative that these two separate parts remain in completely synchronized.
2. Verify and note the Repository path and the relative location of all the folders and child folders. Once you change this information in StarTeam it may be difficult to locate the files and folders you need to move.
To verify the startup path and folder locations:
2a. Display the Server Administration dialog by doing one of the following:
2a i. From the StarTeam Client, select Tools\Server Administration from the menu.
2a ii. On the computer where Starbase Server is installed, start the Server Administration tool.
2b. From the Server Administration dialog?s left pane, select the server configuration you anticipate moving.
2c. Click the Configure Server button. The Starbase Server Configuration dialog opens.
2d. Make a note of the path information in the following text boxes:
2d i. General Tab: Server Startup Log Path and Attachments Path
2d ii. Vault tab: Vault Path, Disk Cache Path, and Archive Path
2e. At this time it is important to also open the "Server Tools" application, by going to the Starteam Server machine, go to the Windows, Start -> Programs -> Starteam Server -> Starteam Server option, make a note of the information from the Properties button under the Database tab: Database server/DSN, this will be the Service Name (name listed in the TNSnames.ORA file) of the Oracle Server Machine.
3. Make certain that Starbase server is installed on the target system. Ensure the Starbase server is not running.
4. Copy all the important files and folders to the target destinations. These files/folders should include:
4a. StarbaseServer.ini (by default located in the installation folder of Starbase Server). You will need this file moved to the different server computer at the same time as the copy of the Repository.
4b. The StarTeam Vault folder and all its folder/file contents (Archive and Cache folders and contents)
4c. The StarTeam Attachments folder and all its file contents
4d. With Oracle 8i or 9i, (MS SQL or DB2 included), you will need to make sure that the Database Server is backed up and restored to the new Oracle Server if you are also changing the Oracle Server at this time.
5. When setting up your Oracle Server to restore this Starteam Server to there are a few things that you"ll need to take into account. Borland recommends installing StarTeam Server on a dedicated application server and the database on a separate server as you are well aware.
- Please follow the recommendations outlined by Oracle for the hardware specification for the Oracle Server version you decide to implement, modified by the number of expected Starteam users. If you plan to run Starteam Server and Oracle on the same machine, please remember that the system requirements demanded by this machine are going to literally a combination of the requirements of these 2 systems. You can install Oracle with default settings of your Starteam or Dedicated Oracle Server.
- Borland currently recommends Windows 2000 Service Pack 3 for both Windows 2000 and Professional, and we highly recommend Oracle 8.1.7 (8i) or 18.104.22.168.0 (9i).
Note** When you copy the database it was most likely backed up into 1 file that contains the files the database was set up with. Oracle Server as well as many other systems was likely set up with a Log file and a Data file, but quite often they can be set up with multiple files. The first step you need to do when restoring this database is to create the database with the same number of files.
- Open the "Oracle Enterprise Manager Console" and drill down to the "Database" folder. Under that you should see a list of Icons, the one that needs to be addressed first is the one named "Storage". Expand the Icon for "Storage", it will display many folders.
- Expand the folder for Tablespaces. Right click the Tablespaces folder and "Create...". Create a new Tablespace with the name the same as it was on the old Server (this isn"t completely necessary but will keep things easier to follow later).
- Give this Tablespace a size that matches or exceeds the space used by the original Tablespace on the original Oracle Server.
Note You may place the Tablespace in any custom location that is local to the server machine, the folder structure you choose must exist.
Note When you enter a name for the Database, you must avoid strange characters such as full stops, tildes etc. and spaces, they will not be acceptable to connection protocol.
- Now create the Tablespace. Once the Tablespace is created, you must drill down through the New Tablespace Icon for your Tablespace and open the Folder for the Datafiles and click on the Datafile Icon.
- This will display a "General" and a "Storage" tab. Open the Storage tab, there you need to set the option to "automatically extend file when full", this should be set with no limit.
- Next you must go back to the "Security" Icon. Expand the Security Icon and select the Users folder. Right Click the Users folder and create the user that "owned" the Tablespace on the previous Oracle Server.
- Assign the new user to the Tablespace you just created in the previous step.
- Create the user with the Roles "Connect" and "Resource" specifically as well as any others you may desire, also specifically give the user the System Privileges "Create Table" and "Create View" as well as any others you prefer.
You are now ready to import you Oracle Backup file (dump). Please see a qualified Oracle DBA to perform these steps, if you have none available, these steps are included as a rough guideline to go by.
- Open a command prompt and type in the word "Imp". This will bring up a Username: prompt, sign in as the System Manager for Oracle at this time.
- Type in the directory and the name of the *.dmp file that was created during your backup.
- The recommended buffer size is 64000
- You may enter "no" to "List contents of import file only"
- You may enter "no" to "Ignore create error due to object existence"
- You may enter "no" to "Import grants"
- You need to enter "yes" to "Import table data"
- You may enter "no" or "yes" to "Import entire export file", if you know the previous owner of the Starteam Tablespace on your Oracle Server (schema owner) then you should enter "no" here, the reason is that the next question will prompt you for that user ID.
After this is done the database should be restored with no errors.
6. At this time, because you have copied the StarbaseServer.ini from the original Server Machine, the configuration will show up in Server Tools as it did on the original machine. Select the Configuration for which you have relocated. You may need to edit some of the fields in the INI file, all the relevant fields can be edited through the Server Tools Application via the "Properties" button and the "Start with override" button.
Do not create a "new configuration", please do not attempt to create a new configuration of the same name, if the Starteam Configuration does not appear in the list of configurations, please re-copy the StarbaseServer.ini to the new machine.
Take these steps before starting StarTeam.
6a. Click on the Configuration Properties button.
6b. With the General tab selected, click on the Verify. You generally need to know the Cipher Phrase to successfully complete this step.
Contact StarTeam Support if you do not know your Cipher Phrase. Just login to to http://support.borland.com and create a case with the subject line "Cipher Name Decryption Requested" and just enclose the StarbaseServer.ini file with an official request for Starbase to decrypt the Cipher Phrase from the file enlcosed and send it back.
6c. After a successful verification of the Cipher Phrase, select the Database tab and click on the Verify Connection. If you have problems with this check your connectivity with the Database either through the NET8 Configuration or with TNS "ping". If you still have problems contact StarTeam Support at (714) 445-4460.
6e. You can now start the Starbase Server.
7. If you have moved one or more of the repository folders to different relative locations you will need to redefine those locations before the server is started.
7a. From Server Tools, click on the "Start with Override..." button.
7b. Browse to or type the new path information for the repository items.
7c. Click on OK.
7d. Test to make certain that your move is totally successful. Consider adding a test file to a project and check the archive directory for a new file entry matching the appropriate date/timestamp.
While it is usual to move the entire repository, you can move
The Attachments Path. StarTeam allows you to attach files to change requests, tasks, or topics. These files are stored in a separate folder on the server. By default this folder is the Attachments folder and is a child of the folder specified for the repository. It has three child folders whose names should not be changed: Changes_Attachments (for change requests), StTasks_Attachments (for tasks), and Topics_Attachments (for topics). If you move this folder, you must also move the currently attached files to that new location. Do so while the server configuration is shut down.
The Vault Path. By default this folder is the Vault folder and is a child of the folder specified for the repository. The Vault folder initially has two child folders: one for the disk cache and the other for the archive. Changing the Vault path does not change the path to either the disk cache or the archive. You do not have to move the Cache and Archive folders unless you change their paths, too.
The Disk Cache Path. The disk cache folder contains copies of
the most recently checked-out file revisions. If a user checks out
a revision that is already in the cache, the file is copied from
the cache rather than from the archive. This speeds up the check
out process. The maximum cache size determines how many files can
be stored. By default this folder is the Cache folder and is a
child of the folder specified for the vault. If you move this
folder, you can (but you don?t have to) move the cached files to
the new location. If you move these files, do so while the Starbase
Server is down. You may want to resize the cache and reset its
refresh interval at this time as well.
The Archive Path. The archive folder stores file revisions. By default this folder is the Archive folder and is a child of the folder specified for the vault. If you move this folder, you must also move the archived files to that new location. Do so while the server configuration is shut down.
If you change any of these folder locations, you must restart the server configuration. If you move the entire repository, you usually change all of these folder locations and the startup location.