Hello,
What does the output of emcli status look like?
Can you see the session in the database?
Are there any clues in alert.log, sqlnet.log or listener.log?
My first attempt would be to eliminate the database or listener as a source
of your problem.
My understanding is that emcli logs into the database as MGMT_VIEW and it
would be best to eliminate that database login as a source of the problem
first.
The next line of attack is the network, any timeouts or anything like that.
The last line would be on your OMS is java running out of memory, that kind
of thing.
Does bug 10625373 in My Oracle Support apply?
Sorry its so vague.
Regards,
Frank
On Wed, Sep 15, 2021 at 2:58 PM Charlotte Hammond <
dmarc-noreply@xxxxxxxxxxxxx> wrote:
Hello All,
Please could somebody explain to me how emcli sessions work? Quite often
I will run emcli only to be prompted immediately on the next command:
Error: Session expired. Run emcli login to establish a session.
If I login again it mostly works but sometimes I have to do this several
times to get a session that allows me to do any work.
Our timeout is set to the default (45 minutes) but quite often we can't
run the next command even seconds after logging in.
This mostly (but not exclusively) seems to happen with scheduled scripts
rather than interactively.
Any suggestions?
Thanks!
Charlotte
