ESSBASE DATABASE Backups scripts in Unix

#!/bin/ksh
####################################################################
#                                                                  #
#  Who          When            What                               #
#  ----------------------------------------------------------------#
#  shaiks       24-JUL-17       Created
#                                                                  #
#                                                                  #
####################################################################
#

date1=`date +'%d%b%y'`
date2=`date +'%d%b%Y%H%M%S'`

#Set Parameters
if [ ${#} -ne "1" ];then
        echo " Please pass the environment name"
exit 0
else
        ENV=$(echo $1 |tr '[:lower:][:upper:]' '[:upper:][:lower:]')
fi

. /home/hypuser/EPM$ENV.env
if [ $ENV == "DEV" ] || [ $ENV == "TST" ];then
SCRIPTS_DIR=/PATH/scripts
else
SCRIPTS_DIR=/PATH$1/scripts
fi
DATA_BACKUP_DIR=/HYP/$ENV/DATA_BKP
BACKUP_DIR=$DATA_BACKUP_DIR/$date2
LOG_FILE=$BACKUP_DIR/$(basename "$0" | cut -d \. -f1)_$ENV_$date2.log

mkdir -p $BACKUP_DIR
#echo $ENV $date2 $DATA_BACKUP_DIR/$date2/ $SCRIPTS_DIR $LOG_FILE

. /home/hypadm/EPM$ENV.env

startMaxl.sh -D ${SCRIPTS_DIR}/essbase_data_backup_all.mxls ${MAXLPVTKEY} ${MAXLENCRID} ${MAXLENCRPWD}
${ESBSERVER} ${BACKUP_DIR} ${LOG_FILE} ${date2}

#Verify Success or Failure
status=$(grep -i error $LOG_FILE | awk '{print $1}'| uniq)
if [[ $status != "ERROR" ]];then
echo "Success"  | mailx -s "ESSBASE $ENV Backup completed Successfully" shaiksameer@shaiksameer.com
else
uuencode $LOG_FILE $LOG_FILE | mailx -s "ESSBASE $ENV Backup failed - verify the attached log" shaiksameer@shaiksameer.com
fi


#Delete Data backups older than 45 days.
find $DATA_BACKUP_DIR -prune -type d -mtime +45 -exec rm -rf {} \;

cat essbase_data_backup_all.mxls

/*Purpose: Data Back-up of all Essbase Databases */

/*    Log in to Essbase    */

login $key $1 $key $2 on $3;

spool on to "$5";

/*    Disable connection to RPT database */

alter application RPT disable connects;

/*    Back-up Reporting Data   */

export database RPT.RPT data to data_file "$4/RPT_RPT_data_export_$6.txt";

/*    Enable connection to RPT database */

alter application RPT enable connects;

spool off;

logout;

exit;

Smartview Ad hoc grid cannot be opened as there are no valid rows of data

In smarview when trying to do the ad-hoc analysis you may see the below error message:

Ad hoc grid cannot be opened as there are no valid rows of data

Fix:

Under Data Options:
you should clear the suppress options in the Data Options tab of the Options dialog box. Ensure that all Suppress Rows and Suppress Columns options are cleared, and that the Suppress missing blocks option is cleared

EPMLCM-13000: Service currently not available.

While importing artifacts using LCM you may run into the below error:

Error:
EPMLCM-13000: Service currently not available.


Issue:
This issue is caused by unpublished Bug 18327819 - LCM IMPORT FAILS WITH "MAX ERRORS THRESHOLD" SET AS "<=100" IN MIGRATION OPTIONS



SOLUTION:

1. Login to Shared Services Console with administrator user.

2. Change the value of "Shared Services - Max Errors Threshold" under Administration->Migration Options to "5000".

3. Attempt to Import or Export artifacts again.

Cannot open file: [\Middleware\user_projects\epmsystem1\tmp\tempfile46694208.txt] Unexpected Essbase error 1030100

Issue:

Cannot Open/load data when Importing Data Using the Essbase Administration Services Console (EAS)

 Unexpected Essbase Error 1030100

Fix:
Rename the data file to .txt extension and then try again

An Unpublished Enhancement Request has been filed to support files with any extension: Bug 23537231

EPMLCM-14000:Error reported from FDM Enterprise Edition. EPMFDM-140291:Export of scripts has failed since system directory could not be found

Error:
EPMLCM-14000:Error reported from FDM Enterprise Edition.  EPMFDM-140291:Export of scripts has failed since system directory could not be found

While cloning using the epm_clone*.sh utility/LCM exports of the FDMEE ,  you may encounter the above error:

root cause:

FDMEE Application root folder was not set correctly. The error "EPMFDM-140291:Export of scripts has failed since system directory could not be found" can occur only when the application root folder is not being set. 

The code where the failure occurred, will execute only when exporting a custom, event, drill script.

Fix:

Set  Application Root folder in the application settings. Under Workflow tab > System Settings > Application Root Folder.

Check if the Application Root Folder is also set in the Application Settings page, for all the applications that are being exported. (Setup Tab > Application Settings > Select the target application in the drop down > Check Application Root Folder entry).

If its a full LCM export, all the Applications in the drop down need to have the App root folder set. It can be set with the same value as in System Settings page.