After server migration, receiving errors "Invalid object name "dbo.ConvertSTTimestamp".

0 Likes

Problem:

After server migration, receiving errors "Invalid object name "dbo.ConvertSTTimestamp".

Resolution:

  • Product Name: StarTeam
  • Product Version: 2006, 2006 R2
  • Product Component: Server Migration
  • Platform/OS Version: All platforms & databases

Description:
Sometimes, when performing a StarTeam database migration using the Migrate function in starTeam Server, the newly migrated server will not start correctly. The error below is thrown and the startup fails.

Exception thrown from Unknown: Class = CDBException, Code = 4294967295(0xffffffff)
Msg = Invalid object name "dbo.ConvertSTTimestamp".
Invalid object name "dbo.ConvertSTTimestamp".
Invalid object name "dbo.ConvertSTTimestamp".
Invalid object name "dbo.ConvertSTTimestamp".
Invalid object name "dbo.ConvertSTTimestamp".
Invalid object name "dbo.ConvertSTTimestamp".
Invalid object name "dbo.ConvertSTTimestamp".

[Function Name] = CStDatabase::InstallStoredProc
[Stored procedure path] = C:\Program Files\Borland\StarTeam Server
2006\DBScripts\SqlServer_Scripts\DW\Install\starteam_sqlserver_create_dw_changeobject.sql
[ODBC Error] = State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server]
State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server]
State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server]
State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server]
State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server]
State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server]
State:S0002,Native:208,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server]




Answer/Solution:

This error normally indicates a security or ownership issue in the new database. Most likely, the new tables created by the migration are not owned by the username associated with the server instance. For example, look in the database and view the table owners. Some of the tables will be owned by DBO and others are owned by another user.

The recommended solution for this issue is to change the user in the StarTeam Server admin tool to your SQL Server SA account. To do this, open the StarTeam Server Administration tool and select the server configuration. From the menu bar, click on Server --> Configuration Properties. Now select the Database Connection Information tab. Change the username to sa. Enter the password (if the SA password is unknown, please check with the database administrator) and click Verify Connection to make sure it works. Click OK then start the server configuration.

If the StarTeam Server configuration is already using the sa username for the server config, then the solution needs to involve the database administrator directly. The DBA will need to access the database using the software tools that come with the database or a third party tool, such as Toad. The actual ownership of the tables in the database needs to be reviewed for discrepencies. All of the tables need to owned by "dbo". The database administrator can run a script on the database tables to change ownership to "dbo" for all that are not owned by "dbo". After the ownership has been changed, restart your StarTeam Server configuration and it should start up. If it fails again, please contact technical support.




Old KB# 28714
Comment List
Related
Recommended