Type commit now to commit these updates, or rollback to cancel.
SP2-0042: unknown command "Disclaimer" - rest of line ignored.
SP2-0734: unknown command beginning "EXCEPT WHE..." - rest of line ignored.
SP2-0734: unknown command beginning "PROVIDED O..." - rest of line ignored.
SP2-0734: unknown command beginning "ALL WARRAN..." - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
SP2-0734: unknown command beginning "LIMITED TO..." - rest of line ignored.
Please make sure not to copy/include the lines after "REM <= Last REM statment -----------------------------------------------------" from cmclean.sql script which is on MOS website. Once you remove those entries from the script, run it again and check the CM.
Ok akhi Hussein I deleted the lines and re-executed the script and it was executed without errors but concurrent manager was still not working. I even executed autoconfig it was succeeded too but issue was still remain.
I took help from another friend he found that the nodes were not mentioned on concurrent managers and tried some methods, at last he stopped and re-executed adcmctl.sh through root and concurrent managers start working.
What would be the main issue?
We tried to bring up the CM through applmgr user and it was showing internal CM status up too but Concurrent -> Administer application node name was not showing. Then we tried to assign node names through Concurrent -> Define but nothing was working. In last we brought it down through applmgr and brought up again through root and everything started working fine even after machine restart. We are not using that trick anymore as now it's working fine through applmgr. My friend told me that some services were stucked up, that's why managers were not working.
Here is old log file, while we were facing the issue:
I've granted the permissions on the same directory and I can't see errors anymore in logs, the managers are working fine.
Please help me to delete the log files includes .req, .mgr, .txt formats. I've logs starting from July 2012.
[oracle@OAConsultants log]$ ls | wc -l
[oracle@OAConsultants out]$ ls | wc -l
Thanks and regards
The files you are refering are the concurrent request log and output files, and the effective way is to delete them is from the front end by running the following request ( from Sysadmin responsibility):
Purge Concurrent Request and/or Manager Data
As you wish to delete both log and output files, have the following paramete:
Mode=Count ( how many days of log and output files you wish to have)
=Age ( how many number of files you wish to have)
Mode Vaue = your input value for the selected mode
Please also refer note:
Concurrent Processing - Purge Concurrent Request and/or Manager Data Program (FNDCPPUR) [ID 104282.1]
Hope this helps!
Thanks Asif Bhai
I ran the request for purging logs older than 14 days, the output is :
Purged 1870 entrie(s) from FND_CONCURRENT_REQUESTS :-19-JUN-2013 12:42:35
Purged 0 entrie(s) from FND_FILE_TEMP :-19-JUN-2013 12:42:35
Purged 4182 entrie(s) from FND_CRM_HISTORY :-19-JUN-2013 12:42:35
Purged 0 entrie(s) from FND_TM_EVENTS :-19-JUN-2013 12:42:36
Purged 0 entrie(s) from FND_TEMP_FILES :-19-JUN-2013 12:42:36
Purged 0 entrie(s) from FND_ENV_CONTEXT :-19-JUN-2013 12:43:28
Purged 0 entrie(s) from FND_DUAL :-19-JUN-2013 12:43:28
Purged 1 entrie(s) from FND_CONFLICTS_DOMAIN :-19-JUN-2013 12:43:28
But I still have so many .mgr, .log, .txt files and date still goes upto July 2012.
$ ls *.mgr | less | wc -l
$ ls *.log | less | wc -l
$ ls *.txt | less | wc -l
Thanks and regards