You mean that your database will charge you by the query? - YES, that's what we hear from vendor

Agreed…currently it's on prem and we are migrating to cloud now so in cloud everything is based on the queries hit by the app and based on that cost will calculate. so i'm thinking all open possibilities to cut down it.

Thanks Gianni…Let me see in cache perspective.

Thanks all… there is a cronjob running to clear the temp files when server is up so i have changed the time to during to server restart time and I have increased the JVM from 2 GB to 4 GB. it's been two weeks now since OBIPS1 server is down

I feel it's because of usage… when i see number of reports is being generated on sunday is more than the other days…

Also, wouldn't nodemanager restart the component on it's own soon after in your case. Please confirm. Ans : it's reaching maximum number of attempts

Yes Steve. Have logged an SR with oracle and they are suggesting to apply the latest patch to the OBIEE12c. But they didn't tell the root cause of this issue. Had a word with OS & network admin also…they didn't see abnormal behavior in the server and there are no scheduled jobs in the OBIEE

Thanks Steve for your reply… Have checked…there is no such suspicious message in that file except with process id 11337864 is no longer alive. Also i have observed that it happens only on Sunday's.

Thanks Sumanth for acknowledging….it's OBIEE12c- 12.2.1.4.0. Error : <Node Manager command 'INVOCATION' failed unexpectedly due to: [end of file]. Please check Node Manager log and/or server log for detailed information.> <INFO> <Domainbi12c> <obips1> <The server 'obips1' with process id 11337864 is no longer alive;…