Kbase P130126: FathomTrending Unavailable error persists when Trending user ID does not exist in _user table.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
02/04/2008 |
|
Status: Unverified
FACT(s) (Environment):
OpenEdge 10.1x
OpenEdge Management 3.1x
SYMPTOM(s):
FathomTrending Unavailable
Fathom trend database log file shows trending user logging in and out every few seconds.
No errors in the admserv.log file
Running dbtool to increase sqlwidth with extra padding shows not change
Able to connect to the trend db via sqlexp using trending user
CAUSE:
The trending userid does not exist in the _user table, nor does it have DBA access granted.
FIX:
The trending user must be able to update the pub tables. In a default OE Management Install, the following should be returned when querying select * from sysprogress.sysdbauth:
GRANTEE DBA_ACC RES_ACC
-------------------------------- ------- -------
fathmbld y y
SYSPROGRESS y y
TRENDING y
Also, the _user table of the FathomTrendDatabase should have two users listed: trending and guest.
If the trending user does not appear in this list, trending must be added to the _user table. You must also add the sysprogress user to the _user table. Once this is done, connect to the FathomTrendDatabase as sysprogress and grant DBA Access to trending:
grant dba to "trending";
commit;