01-22-2014 12:49 AM
Hi
has anyone an idea what that message means? All processes are running fine and I can't find that error message in any log or documentation.
01-22-2014 12:51 AM
May be temporary. Did you tried daemon manager restart?
Please share screenshot and details on what exactly you're trying to do, when you get this error.
-Thanks
01-22-2014 01:09 AM
To restart the daemon manager, I have to wait for the next maintenance window.
Any idea to investigate the error to avoid its return?
01-22-2014 01:25 AM
Reasons are unknown on almost all SRs I have seen with this issue. As performace portion doesnt have much data, reinitialize is the easiest option, done in seconds.
But that would too, require daemon restart. you can Share upm_ui.log, upmprocess.log, upmdbmonitor.log from NMSROOT/log and NMSROOTdatabases\upm\upm.log.
-Thanks
Vinod
**Rating Encourages contributors, and its really free. **
01-22-2014 02:30 AM
Would not reinitializing the db clear all data?
01-22-2014 02:32 AM
Yes it does, but for the specific module, just performence, which means loosing custom templates, but you can export important one's.
Not any other details from LMS.
-Thanks
Vinod
01-22-2014 12:54 AM
I have seens some of the older issues in LMS 4.2.2 as well as 4.2.3, and the issue came out to be corrupt DB for Performance Management portion of LMS. Was fixed with the DB reinitialization.
You may have to follow the same path if restart doesnt help.
-Thanks
01-22-2014 03:41 AM
Daemon manager restart did not help, but UPM DB process is running fine:
pdshow UPMDbEngine
Process= UPMDbEngine
State = Program started - No mgt msgs received
Pid = 34732
RC = 0
Signo = 0
Start = 1/22/2014 12:37:57 AM
Stop = Not applicable
Core = Not applicable
Info = Application started by administrator request.
Next step is to validate the upm database or to clear the upm db transaction log?
01-22-2014 03:53 AM
Though it is time consuming to stop daemon --> do a transaction log receovery --> and restart daemon to check effectiveness, it will be much better to try it once, which has a fair probability of fixing the issue.
Please try following procedure for Transaction log receovery :
Do a trasaction log recovery for all Db's :
* Goto NMSROOT/databases/upm and remove upm.log file.
* on command prompt run following command :
dbsrv10 -f upm.db
Example:
C:\Program Files (x86)\CSCOpx\databases\upm>dir *.log
Volume in drive C has no label.
Volume Serial Number is E492-A3AB
Directory of C:\Program Files (x86)\CSCOpx\databases\upm
03/27/2012 07:01 AM 196,608 upm.log
1 File(s) 196,608 bytes
0 Dir(s) 27,119,108,096 bytes free
C:\Program Files (x86)\CSCOpx\databases\rmeng>del upm.log (you have to delete if from GUI, cli mostly doesnt work)
C:\Program Files (x86)\CSCOpx\databases\rmeng>dbsrv10 -f upm.db
On Solaris, try :
env LD_LIBRARY_PATH=/opt/CSCOpx/objects/db/lib64 /opt/CSCOpx/objects/db/bin64/dbsrv10 -f /opt/CSCOpx/databases/upm/upm.db
Else for reinitialize, following is the command :
Solaris : /opt/CSCOpx/bin/dbRestoreOrig.pl dsn=upm dmprefix=UPM
Windows : NMSROOT\bin\perl.exe NMSROOT\bin\dbRestoreOrig.pl dsn=upm dmprefix=UPM
-Thanks
Vinod
**Rating Encourages contributors, and its really free. **
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide