During a recent upgrade we had to rename one of the financial databases from 'Navigator' to 'NavLive'.

I changed the ODBC and the test runs succesfully.

I changed the database name in the metadata/synonym and the test runs succesfully.

But when I run any of the reports I get an error that it is still trying to find a database called 'Navigator'.

-

 (FOC1400) SQLCODE IS 916 (HEX: 00000394) XOPEN: 08004
 : Microsoft OLE DB Provider for SQL Server: [08004] The server principal "
 : WebFocus1" is not able to access the database "Navigator" under the curr
 : ent security context. [] Deferred prepare could not be completed.
 L    (FOC1406) SQL OPEN CURSOR ERROR.  : NAV_COMPTROLLER$CHECK_LEDGER_ENTRY
 

Is there some place else I need to change the database name besides ths ODBC connection and the Metadata?

This message has been edited. Last edited by: Greg,

Remember that there is connection information in both the MAS and the ACX files that need to be changed. If all that is correct, you might try removing the data connection in the WF server and adding it back again. You mention ODBC but there is a reference to SQL Server. They're similar, but not the same. Make sure you're using the correct driver.

A number of other things could also be the issue, such as proper privileges on the renamed database. Try using a separate SQL tool such as MS Query, Excel, or an SQL Server tool to see if you can retrieve the data that way. If so, the problem lies in the WF server configuration or metadata. If not, it's in the SQL server itself.

The test in the metadata set-up runs and pulls data so I dont think it is a permission error.

I also can retrieve data using the mssql studio.

Webfocus stillthink the database is called Navigator some where.

I will have alook at the mas files.

The acx file is still looking for 'Navigator'

  SEGNAME='NAV_COMPTROLLER$CHECK_LEDGER_ENTRY', 
   TABLENAME='Navigator.dbo."Comptroller$Check Ledger Entry"', 
   CONNECTION=Navigator, KEYS=1, $
 

There are hundreds of these. I should not have to go and change them all by hand. I thought changing the metadata would change them all.

Well, technically this is part of the metadata. I would just use a search-and-replace utility to replace all of them. There's no way around it. The connection will be what that connection is named within the WF server, and the tablename must reflect your changed db name.

I conviced the DBA to give teh new database the old name and now everyitng it working again.