Thursday, December 29, 2016

Financial Reporting Studio : Services : Status: 503 - Service Temporarily Unavailable

ISSUE :

A 'Service Temporarily Unavailable' error occurred communicating with the server.
URI: http://server:19000/hr/xml/HRConfig.jsp

Status: 503 - Service Temporarily Unavailable

Content: text/html
<HTML><HEAD><TITLE>Weblogic Bridge Message</TITLE></HEAD> <BODY><H2>Failure of server APACHE bridge:</H2>

<P><hr>No backend server available for connection: timed out after 10 seconds or idempotent set to OFF or method not idempotent.<hr>
</BODY></HTML>


DEBUGGING STEPS:

This issue is more on the web-logic server side .

Error 503—Service Unavailable

Indicates that WebLogic Server cannot find the compiler it requires to compile your JSPs. 

more about the complier

WEBLOGIC SERVER SESSION ISSUES:
WLS Session Issues

The WebLogic Proxy Plug-In routes the requests to backend WLS server/cluster. WLS maintains sessions so that subsequent requests from the same client are routed to the same WLS server. However, due to various reasons, if the WebLogic Proxy Plug-In is unable to communicate with the WLS server:
  • If the request is routed to a single WebLogic Server instance, the WebLogic Proxy Plug-In continues trying to connect to that same WebLogic Server instance for the maximum number of retries as specified by the ratio of ConnectTimeoutSecs and ConnectRetrySecs. If all attempts fail, an HTTP 503 error message is returned back to the client.
  • If the request is routed to WebLogic Cluster, then the current WLS server is marked as bad, and the request is routed to the next available WLS server. If all attempts fail, an HTTP 503 error message is returned back to the client.
In addition to sending a HTTP 503 error message, the following is displayed as a response in the HTTP client:
Failure of Web Server bridge:
No backend server available for connection: timed out after xx seconds or idempotent set to OFF or method not idempotent.

Thursday, September 1, 2016

ODI Automation - Scenario

Navigate to the startscen.bat location , add the package name, add context, -v=5 picks the latest version , log location.

SCENARIONAME.BAT
D:
CD D:\OracleMiddleware\Oracle_ODI_117\oracledi\agent\bin
startscen.bat (NAME OF THE PACKAGE)PKG_00_UPD_PR_STG -1 
(NAME OF THE CONTEXT) Main_CONTEXT "-V=5">>F:\ODI\LOGS\logNAME.log
exit

/* Ignore bracketed comments in the above Code */

Saturday, May 25, 2013

About Jay R

Jay Raghupathruni, Hyperion Professional from past (13 Years) , Currently working as Lead or Facilitator in Implementations that require a Senior resource knowledgeable in parallel Business Intelligence toolsets from the competitors, I have worked with SAP BPC, Cognos, OBIEE, BIG Data, SAP HANA, Initial part of IT Experiences were in ASP Programming & Visual Basic, Later moved on to Datastage and transitioned into Hyperion version 6.5 up until now 11.1.2.x, Primarirly in supporting FP&A teams in all the clients I worked for,
My clients in past were
Marsh & Mclennan (Insurance) - Maintenance/Project support
Aetna (Insurance)- Hyperion planning support
Amazon - Retail - Infrastructure consultant
UNIVAR - Retail - Budget and Forecasting support
Sprint - Wireless (Planning support)
Hanger Orthopedic Group - (Health care)
Mid-States Petroleum (Oil & Natural gas)
Fred Hutchinson ( Non Profit, Cancer research)





Saturday, April 28, 2012

When Writting Fix Statement is there a Order of using Dimensions ?

Dear All,

In this Article we will be focusing on writing an article in which every Hyperion Calculation Scripts specialist once in the early stages of his career might have a doubt about it, I encountered myself this question couple of times.


To answer the question., 
Question : Is there an order of using dimensions in a Fix statement ?

Answer :  No the order of dimensions in a Fix statement don't make any difference






For example :: 

There should be no differene between a
Fix(Sparse)
Fix (Dense) 

and 
FIX(Sparse, Dense) 

as the fixes would be unioned together internally


Friday, February 24, 2012

Maintenance scripts - Calculations

//ESS_LOCALE English_UnitedStates.Latin1@Binary
/* Author: Jay Raghupathruni, Script is part of the yearly maintenance */
Yearly maintenance calc script ---As a Hyperion Administrator, you get Monthly, Quarterly, Yearly tasks to maintain Planning/Essbase applications...
Scenarios that a request can be -

  1. We want to clear whole year : wow that’s simple1



     



  1. Clear Budget data for year FY10, remove data for Descendants of Entity dimension, excluding Descendants(Parent1)
similarly there might be a request for writting a script from scenario dimension, asking to eliminate few selected from say 50+ members...