cancel
Showing results for 
Search instead for 
Did you mean: 

Can we use 'x_server stop' to stop livecache as well

Former Member
0 Kudos

I am used to the following procedure to stop MaxDB and APO

1) stop livecache

2) stop APO

3) stop services related to SQL server

4) 'x_server stop'

May I simplify above to:

1) 'x_server stop'

2) stop APO

3) stop services related to SQL server

i.e. I want to use 'x_server stop" to stop both livecahe and MaxDB.

Is this OK?

Thanks!

Accepted Solutions (1)

Accepted Solutions (1)

lbreddemann
Active Contributor
0 Kudos

> I am used to the following procedure to stop MaxDB and APO

> 1) stop livecache

> 2) stop APO

> 3) stop services related to SQL server

> 4) 'x_server stop'

>

>

> May I simplify above to:

>

> 1) 'x_server stop'

> 2) stop APO

> 3) stop services related to SQL server

>

>

> i.e. I want to use 'x_server stop" to stop both livecahe and MaxDB.

>

> Is this OK?

No, it isn't.

First of all: the command does not stop any liveCache or MaxDB instance.

All it does is to stop the network communication between the APO workprocesses and the liveCache instance.

And it does this quite forcefully.

Open transactions? Just cancelled/rolled back!

That will generate a ton of 'connection lost' errors in the APO system log.

regards,

Lars

Former Member
0 Kudos

Dear All,

What will happen if I execute x_server stop before stop database and later execute x_server start?

Answers (0)