Enabling / Disabling Connects in Essbase During Separate App Copy (v11.1.1.3)

---

I found something interesting recently in our EPM 11.1.1.3 environment regarding app copies affecting unrelated processes on the same Essbase server.  For this example lets assume I have an Essbase server with 3 applications on it; App1, App2, and App3.

When running an app copy from App1 to App2 using the syntax below, you cannot enable or disable connects in App3.

create or replace application App2 as App1;

When executing the following MaxL to disable connects, the system will allow me to log into the Server and log out any active users in the App, but will stall on the line that disables the connects until the app copy has completed.  This is very strange behavior since App3s commands should have nothing to do with the app copy going on between App1 and App2.

login Scott MyPassword on MyServer;

/* Logout current users */
alter system logout session on application App3 force;

alter application App3 disable connects;
alter application App3 disable commands;

logout;
exit;

This is also the same for enabling connections as well.  I have not yet came across another MaxL function that is affected by this app copy other than the 2 mentioned above.  In Essbase v6.5, there was an issue with app copies that froze up all users on the server.  I am wondering if this is a leftover bug from back in those days.

Currently, I have an Oracle SR open that will hopefully shine some light on the subject.  So far, the response I am getting is that I should time my batch scripts differently...   I will keep this post updated as I find out more information about this and whether or not it affects the latest version of the EPM suite.

Thanks for reading!