rittmanmead / scripts

Useful scripts for the admin of OBI and other tools

A collection of scripts and utilities to make the OBI admin's life easier

scripts's Issues

Use WLST to start servers, not direct script calls

Per Oracle documentation NodeManager should be used to start the Admin and Managed servers.

Therefore, update this init.d script to use WLST instead. Ref: http://docs.oracle.com/cd/E23943_01/web.1111/e13813/reference.htm#i1106406

OBIEE 12c bi_server1 failed_not_restartable

i'm trying to start bi_server1 but failed to start all other services is up

rc0 shutdown script does not run due to lock file naming issue

Hello and thanks for the obiee rc-script.

The shutdown script in /etc/rc0.d/K??obiee does not run on system
halt. The /etc/rc script expects an lock file named after the init.d
script, not the rc?.d link.

In my case SUBSYS=$(basename $0) results to S96obiee but should be
SUBSYS=$(basename $(readlink -f $0)) to use just the scriptname obiee.

Patch below tested on SampleApp_v406:

+BEGIN_SRC git

--- a/home/work/oracle/init.d/obiee
+++ b/home/work/oracle/init.d/obiee
@@ -82,7 +82,7 @@ OBIS_FINGERPRINT=$FMW_HOME'.*/bin/opmn'

---------------------------------

SUBSYS must match the script name (eg obiee), as it is used for the process lockfile

-SUBSYS=$(basename $0)
+SUBSYS=$(basename $(readlink -f $0))
LOCK_FILE='/var/lock/subsys/'$SUBSYS
START_LOG=$LOG_PATH/$SUBSYS-start.log
STOP_LOG=$LOG_PATH/$SUBSYS-stop.log

+END_SRC

The log files in /var/log will change their names after this patch
accordingly.

Kind regards,

Oliver

Update documentation to specify Enterprise install type

Hi,

i started to use your script and while customizing for my install, decided to update you as well, so that the script could be improved even further.
Documentation should be updated specifying that script is for Enterprise Install type. If any user, like me, installed Simple Install type, the script needs to be modified.

init.d script doesn't cope with multiple instances on single server

c.f. SampleApp v406 with both instances running. Get confused about ports etc. Needs to be more specific in grepping for paths associated with processes maybe?

Start components intelligently, based on what is running already

Per @stewartbryson's suggestion, instead of trying to start up all components of the stack whenever 'start' is invoked, instead check the status of each and only start up if it appears not to be running.
Would need a --force flag to override.

obiee startup script (init.d) - update for RHEL7-related distros to use systemd

init.d/obiee issue with IPv6 in check_process_ports

In check_process_ports there is a line to find the port a process is listening on.
PORT=$(pgrep -f $1|xargs -I'{}' $LSOF_PATH -nPp {}|grep LISTEN|awk -F ":" '{print $2}'|cut -d " " -f 1|sort -u|paste -s)
When using IPv6 this line match the second block of the IP instead of the port. In the picture below it return "120b" instead of "9000".

get a failed when running the obi script

OBIEE version: 11.1.1.9.0.150415.1247

Can you please advise me on where i am going wrong.

Checking WLS Admin Server: listening on port 7001 [ OK ]
Checking WLS Node Manager: listening on port 9556 [ OK ]
Checking WLS Managed Server: listening on port 8205 9704 [ OK ]

** OBIEE login page is not accessible ** [FAILED]
Login to the WLS Console and check :

• the Managed Server state is RUNNING
• the Application Deployment "analytics" is running
  Checking OPMN: listening on port 9500 9501 [ OK ]
  All OPMN-managed BI Components are running [ OK ]

RPD xml Patch Merge shall script

Hi I have developed one simple Batch Script for OBIEE RPD xml Patch Merge script.

Could you please do the same in automation using Shall script(For Linux Environment). In my case i gave you a specific one which can deal with 3 xml patch merges and it generates one Output RPD for each successful merge.

But my script will not handles any ERRORS at run time.
OBIEE RPD xml Patch Merge Command:
biserverxmlexec -P RANSBI#2014 -I D:\RPD'S\09032014\DEV\XML1.xml -B D:\RPD'S\09032014\DEV\RPD1.rpd -O D:\RPD'S\09032014\DEV\RPD2.rpd

Algorithm Flow:

All Inputs will in Present folder Named as Patch_Inputs
Inputs: N-number of XML patches(example:10- abc1.xml, abc2.xml,abc3.xml,...abc10.xml,), Main RPD (MASTER.rpd)

Step 1: Under present Directory Check and assign to XMl's to one Array varible xml{i}, and Master. RPD to rpd{j}

Step2: Based on xml file count begin a loop and start the merge process using below command:
biserverxmlexec -P RANSBI#2014 -I D:\RPD'S\09032014\DEV\XML1.xml -B D:\RPD'S\09032014\DEV\RPD1.rpd -O D:\RPD'S\09032014\DEV\RPD2.rpd
for each iteration output RPD will be input to next merge. If merge fails the handle the error and change the xml file without changing the RPD. If possible send a mail to group regarding xml patch error so that corresponding Dev team can know about the error.

Step 3: For each successful merge Output RPD need to be Validate using Validate command.
Under validation if something wrong need to be intimated with ERROR.
validaterpd -R repository.rpd -O results.txt -S

Step 4: For this total process log creation is required.

Regards,
Kishore
[email protected]

Batch Script for OBIEE RPD xml Patch Merge script.
@echo OFF
PAUSE
:: REm The format of %TIME% is HH:MM:SS,CS for example 23:59:59,99
set STARTTIME=%TIME%
CD C:\Middleware\Oracle_BI1\bifoundation\server\bin
set PWD=%CD%
echo **************************************************************************
echo.
echo OBIEE Patch Mearge Process Got Initiated on [%time% - %date%]
echo.
echo **************************************************************************
echo.
echo "Please Check Below parameters are Ok[Y]/Not[N]"
echo.
:: REM Patch Script Parameters Initiallization Start Point.
echo **************************************************************************
echo Number of Patch Merges: 3
echo Script Home path: C:\Middleware\Oracle_BI1\bifoundation\server\bin
echo Current Directory: %PWD%
echo Original Repository: RPD1.rpd
echo XML Patch File Name: XML1.xml
echo Modified Repository: RPD2.rpd
echo **************************************************************************
CHOICE /C YN
IF ERRORLEVEL 1 SET CHOICE=Y
IF ERRORLEVEL 2 SET CHOICE=N

::REM Conditional Check

IF %CHOICE% EQU N (
echo User Terminated the Patch Merge Initialization Process, Exiting now.
TIMEOUT 2
Exit /b
) ELSE (
echo Merge Script is Going to Start NOW:[%time%]
echo.
echo The Team Wise XMl's are Going to mearge by biserverxmlexec Command line Utility...
echo.
CALL biserverxmlexec -P RANSBI#2014 -I D:\RPD'S\09032014\DEV\XML1.xml -B D:\RPD'S\09032014\DEV\RPD1.rpd -O D:\RPD'S\09032014\DEV\RPD2.rpd
CALL biserverxmlexec -P RANSBI#2014 -I D:\RPD'S\09032014\DEV\XML2.xml -B D:\RPD'S\09032014\DEV\RPD2.rpd -O D:\RPD'S\09032014\DEV\RPD3.rpd
CALL biserverxmlexec -P RANSBI#2014 -I D:\RPD'S\09032014\DEV\XML3.xml -B D:\RPD'S\09032014\DEV\RPD3.rpd -O D:\RPD'S\09032014\DEV\RPD4.rpd
echo.
echo Merge Script is Going to End NOW:[%time%]
)
set ENDTIME=%TIME%
:: REM Total Time taken to Merge
set /A DURATION=%ENDTIME%-%STARTTIME%
echo Total Merge Time : %DURATION%
PAUSE 10

Handle AdminServer on separate host

Cater for scaled-out deployments

Modify/branch script for Simple Install type

The script doesn't work well for simple install type. I started modifying it - would you like to have perfect script, for both versions of OBIEE installation type?