FDM Error "Invalid object name 'tWebUserPreference'." Running FDM Schema Update For A 9.2 Application To 11.1.1.3
Information in this document applies to any platform.
When showing the 9.3.0 upgrade level.
The update.log file has the following entry-
** Begin Schema Update Entry [11/18/2010 3:11:42 PM] **
-------------------------------------------------------------
Step 12: Update English Language Code to Standard Locale Value
Description...................................... Invalid object name 'tWebUserPreference'.
When the MSSQL restore was done in the upgraded environment, a number of tables were owned by the old SQL login in the 9.2 environment that is no longer valid.
All objects within the FDM application database need to be owned by DBO.
A) Have the DBA Restore the FDM application database
B) Grant DBO as owner of all objects in the database
C) Re-run the schema update utility.
|
|||||
Modified 02-DEC-2010 Type PROBLEM |
Applies to:
Hyperion Financial Data Quality Management - Version: 11.1.1.3.00<max_ver> and later [Release: 11.1 and later ]Information in this document applies to any platform.
Symptoms
When running the Schema Update Utility on a 9.2 application for an 11.1.1.3 upgrade, A "Failed, check log" message is encountered.When showing the 9.3.0 upgrade level.
The update.log file has the following entry-
** Begin Schema Update Entry [11/18/2010 3:11:42 PM] **
-------------------------------------------------------------
Step 12: Update English Language Code to Standard Locale Value
Description...................................... Invalid object name 'tWebUserPreference'.
Cause
The SQL DBA did not restore application database with the proper owner for all tablesWhen the MSSQL restore was done in the upgraded environment, a number of tables were owned by the old SQL login in the 9.2 environment that is no longer valid.
All objects within the FDM application database need to be owned by DBO.
Solution
To resolve this try the follow:A) Have the DBA Restore the FDM application database
B) Grant DBO as owner of all objects in the database
C) Re-run the schema update utility.
GKontos
Comments