ESSBASE allows only one user at a time to do any modification in the Outline.
If any active connections are there while starting dimension build then the process will get fail,
during the dimension build if any user tries to access the outline then also dimension build process will get fail.
To avoid this ambiguity before starting the dimension build process just unlock the object from all connection and then start the process.
Here is the simple process how to do the unlock, the code is in maxl statements.
#!/bin/ksh
#########################################################################
# Script designed to make sure there are no more connections to a cube
# after a set waiting period
#
#
# 1. Disables logins
# 2. Wait for # seconds
# 3. Force logout/kill of all sessions to a cube
#
########################################################################## Validate command line arguments
if [ $# != 4 ]
then
echo "Insufficient arguments.."
echo "Usage: waitAndClearSessions.cmd env app_name profile secondsToWait"
exit -1
fi
FRENV=$1
APP=$2
PROFILE=$3
SEC=$4
. /clocal/fme/${FRENV}/forecast/${APP}/init/${PROFILE}.profile
# First login and disable additional connections then kill any connections
# not running a calcessmsh << end_mshcmd1
login $USER_ID $USER_PWD on $SERVER;
alter application '$APP_NAME' disable connects;
alter system logout session on application '$APP_NAME';
quit;
end_mshcmd1
# Now wait a given number of secondssleep $SEC
# Now force a logout of any remaining sessionsessmsh << end_mshcmd2
login $USER_ID $USER_PWD on $SERVER;
alter system logout session on application '$APP_NAME' force;
quit;
end_mshcmd2
Happy Learning
If any active connections are there while starting dimension build then the process will get fail,
during the dimension build if any user tries to access the outline then also dimension build process will get fail.
To avoid this ambiguity before starting the dimension build process just unlock the object from all connection and then start the process.
Here is the simple process how to do the unlock, the code is in maxl statements.
#!/bin/ksh
#########################################################################
# Script designed to make sure there are no more connections to a cube
# after a set waiting period
#
#
# 1. Disables logins
# 2. Wait for # seconds
# 3. Force logout/kill of all sessions to a cube
#
########################################################################## Validate command line arguments
if [ $# != 4 ]
then
echo "Insufficient arguments.."
echo "Usage: waitAndClearSessions.cmd env app_name profile secondsToWait"
exit -1
fi
FRENV=$1
APP=$2
PROFILE=$3
SEC=$4
. /clocal/fme/${FRENV}/forecast/${APP}/init/${PROFILE}.profile
# First login and disable additional connections then kill any connections
# not running a calcessmsh << end_mshcmd1
login $USER_ID $USER_PWD on $SERVER;
alter application '$APP_NAME' disable connects;
alter system logout session on application '$APP_NAME';
quit;
end_mshcmd1
# Now wait a given number of secondssleep $SEC
# Now force a logout of any remaining sessionsessmsh << end_mshcmd2
login $USER_ID $USER_PWD on $SERVER;
alter system logout session on application '$APP_NAME' force;
quit;
end_mshcmd2
Happy Learning
No comments:
Post a Comment