Hyperion Essbase (MOSC)

MOSC Banner

Essbase unable to connect to lease manager database

edited Jan 11, 2016 9:12AM in Hyperion Essbase (MOSC) 12 commentsAnswered

We recently updated the shared services and registry database connections using the configtool.bat/sh. It looks like those references are working ok as shared services console works ok and Essbase starts.

We are getting the lease manager error log messages below. It is trying to use the alias for the new Oracle server.   I didn't see anywhere in the configtools to update a lease manager database reference.

I updated all of the screens with the new server name of z1uayora.corp.cat.com.   Is there something else to update for the lease manager?  How do I correct the error?  Why would it use the alias?  

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center