Issue:
Concurrent Program was terminated by signal 25.
When attempting to run a concurrent program which is accessing file "reports.log" in directory $APPLCSF/$APPLLOG then following error occurs: emsg:was terminated by signal 25
Cause:
File size of "reports.log" has reached its maximum limit at operating system which is 2GB. If $APPLCSF/$APPLLOG/reports.log will be huge -- 2GB in size, then reports can not append anything else to it and hence concurrent program accessing reports.log for its execution will error out.
Solution:
1. Stop the concurrent manager.
2. Check the size of reports.log file and if file size is more than 2 GB then rename/truncate existing "reports.log" in directory $APPLCSF/$APPLLOG and create a empty "reports.log".One can do a find command as well.
$ find $INST_TOP -name reports.log
cd $APPLCSF/$APPLLOG
bash-3.2$ls -lrth reports.log
-rw-r–r– 1 applmgr dbamgr 2.1GB Mar 05 23:00 reports.log
bash-3.2$ cp -r reports.log reports.log_BKP
bash-3.2$ > reports.log
3. Start the concurrent manager.
4. Retest the issue.
Concurrent Program was terminated by signal 25.
When attempting to run a concurrent program which is accessing file "reports.log" in directory $APPLCSF/$APPLLOG then following error occurs: emsg:was terminated by signal 25
Cause:
File size of "reports.log" has reached its maximum limit at operating system which is 2GB. If $APPLCSF/$APPLLOG/reports.log will be huge -- 2GB in size, then reports can not append anything else to it and hence concurrent program accessing reports.log for its execution will error out.
Solution:
1. Stop the concurrent manager.
2. Check the size of reports.log file and if file size is more than 2 GB then rename/truncate existing "reports.log" in directory $APPLCSF/$APPLLOG and create a empty "reports.log".One can do a find command as well.
$ find $INST_TOP -name reports.log
cd $APPLCSF/$APPLLOG
bash-3.2$ls -lrth reports.log
-rw-r–r– 1 applmgr dbamgr 2.1GB Mar 05 23:00 reports.log
bash-3.2$ cp -r reports.log reports.log_BKP
bash-3.2$ > reports.log
3. Start the concurrent manager.
4. Retest the issue.
Comments
Post a Comment