Kbase 15640: AS/400 DBA command error 100 start
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Unverified
SYMPTOM(s):
Problem changing the Progress/400 Data Dictionary
Error "A DBA COMMAND ERROR HAS OCCURED CONTACT PROGRESS SOFTWARE WITH THE
FOLLOWING ERROR CODE 100 START."
FACT(s) (Environment):
AS/400
Progress 9.1C
CAUSE:
One reason may be that the P__SEQ file is being journaled on the AS/400.
FIX:
Check:
Make sure another PROSERVER job is not hung up out there due to an earlier crash. Use the AS/400 command WRKACTJOB. If you find such a PROSERVER job and nobody is connected to the database, end it with option 4.
Look if the P__SEQ is being journaled. This file is only journaled when a user is modifying the PROGRESS/400 Data Dictionary. A customer must never journal manually this file. To check if this file is being journaled use the WRKJRNA command. The journal is PRODBAJRN and the library the same which contains the database files. In the screen where the journal attributes are shown, press F13 to see the journaled files. You must look if the P__SEQ is in the list.
Make sure another program (or job) is not trying to journal de P__SEQ file.
This problem usually has something to do with the P__SEQ file not being available.
RECOVERY
========
Once you are sure there are no users connected to the database, no PROSERVER jobs running, no other jobs running which might lock the P__SEQ file, and that the P__SEQ file is being journaled, what you should do is ending manually the journaling of the P__SEQ file. To do it, execute the following command:
ENDJRNPF FILE(library/P__SEQ) JRN(library/PRODBAJRN)
where library is your database name.