Kbase 17540: Journaling Not Started For P__SEQ file. *ALLOBJ Needed
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/15/2008 |
|
Status: Verified
FACT(s) (Environment):
Progress/400 DataServer
SYMPTOM(s):
The following errors are encountered when switching to "Modify Schema" in the Progress/400 Data Dictionary
ERROR:
The following DBA command error message was received:
Invalid User Authority for Maintenance
The following DBA command error message was received:
Journaling receiver not started
Within the AS/400 job log, the following error is seen:
PRO9706 - Journaling not started for P__SEQ file
CAUSE:
The user profile used for connecting the AS/400 database does not have enough authority to modify schema files. In order to modify the schema, Progress needs some authority to; start and stop journaling, create and delete objects, and compile source files and so on.
FIX:
Basically, Progress needs the same authority as any user would need to maintain the schema of an standard DB2/400 database from the OS/400 point of view, plus the journal handling. Setting *ALLOBJ is recommended because it is the easiest way to allow Progress to handle that.