Essbase log location

how can i change the essbase log location and application log location in V 11
Edited by: Mink2 on Mar 10, 2010 1:39 PM

currently you can't that I know of. In version 11 it is in Hyperion\logs\essbase. I guess you could uninstall everything and reinstall Hyperion products on a different drive and that would change it :)

Similar Messages

Changes required in Essbase logs location:

Hello Masters,
I am trying to change Essbase log file location from default location to new location. this is our internal requriement.
Existing Log location:
../app/hyperion/Oracle/Middleware/user_projects/epmsystem1/diagnostics/logs
Desired New Log Location:
../app/essbase/logs
To do the change, We are modifying logging.xml file at ../app/essbase/EssbaseServer/essbaseserver1/bin
In the logging.xml file, changed the path parameter value from old location to new location. But, still the log files are creating in the old location.
Please share me your experiences if anyone already did it and let me know do I need to do any specific steps after modification.
Thanks,
Ganesh.

Did you recycle the services after you made the change?
Thank you,
Todd Rebner

Essbase Log

I am have issue connecting to admin Server
where are the Logs for the following
Foundations service
Intergration Services
Essbase Server
and
Essbase Admin Server
Please advise

which version?
Default Location of Log Files in Version 7.1.x
Essbase.log - //Hyperion/essbase
Application_Name.log - //Hyperion/essbase/app/application_name
Default Location of Log Files in Version 9.0.x - 9.3.x
Essbase.log - //Hyperion/AnalyticServices
Application_Name.log - //Hyperion/AnalyticServices/app/application_name
Default Location of Log Files in Version 11.1.1.x
Essbase.log - //Hyperion/logs/essbase
Application_Name.log - //Hyperion/logs/essbase/app/application_name
Default Location of Log Files in Version 11.1.2
//Oracle/Middleware/user_projects/epmsystem1/diagnostics/logs/essbase/essbase_0
Essbase.log
Essbase_ODL.log
//Oracle/Middleware/user_projects/epmsystem1/diagnostics/logs/essbase/essbase_0/app/application_name
Application_Name.log
Application_Name_ODL.log

Essbase Log to a Cube

I am looking for a download that was there on Hyperion forum download before Oracle buy out or some where. The download kit was to load Essbase Log to an Essbase Cube to help analyze the activity. Kit includes .rul file and base outline structure etc.
I will highly appreciate if anybody knows where to get it. Thanks in advance.
I know if I can spend some time I can development it but I would like use download kit rather than re-inventing the "wheel".

Hi Rajsheel,
I also required the above mentioned application code for essbase log analyse and purging activities.
Can you please let me know about some concepts to purge the Essbase logs.
my mail id is [email protected]
Thanks in advance!!
Deepak

E-mail alerts in planning & essbase log

Hi All,
1).How to get the e-mail alerts in planning .
2).where can we find in detail log file in Essbase.
Bunny

Hi,
To set up e-mail for workflow notification.
In planning - Administration > Application Settings
Under System Settings in the E-mail Server box - enter the smtp server information.
essbase.log will be in arborpath directory e.g. C:\hyperion\AnalyticServices\essbase.log
Also there is a log file for each application. e.g. C:\hyperion\AnalyticServices\app\Sample\Sample.log
Cheers
John
http://john-goodwin.blogspot.com/

Web Dynpro error log location

I'm pretty new to Web Dynpro and have a few questions regarding the location of the different error log.
1. Sometimes the web dynpro IDE prompt up saying "please check the error logs for details". Where is the error log located?
2. After i deployed and run the Web Dynpro application, there is a "Red Exclaimation" picture and the bottom of the web page. Where to find this error log?
3. Where is the error log for run time error, eg, NULL POINTER exception etc ?
Any help would be much appreciated. Thanks.

Hi julius,
1) Go to windows->preferences->workbench->workspace->current workspace. Open directory, go to ".metadata" folder and check ".log" file
2) 3) In my case it is C:\usr\sap\J2E\JC02\j2ee\cluster\server0\log\defaultTrace.trc (J2E - SID, JC02 - 2nd instance)
Best regards, Maksim Rashchynski.

Control the size of Essbase.log and application log

Understand that there are many message were written to the Essbase.log and application log. Is there any method to control what kind of message to be written to the log file so as to reduce the IO frequency of the server disk folders?
Thanks for your help!

CL wrote:
You might want to think about forcing your BSO/ASO PAG & IND/DAT files to go onto a separate drive volume from your base Essbase binaries. This can be tough to do in a SAN environment as it is difficult to know what is truly where.
Another option would be to use CLEARLOGFILE to reset the logs (this will delete them every time you stop/restart Essbase, so make sure you archive them if you need log history).
See: http://download.oracle.com/docs/cd/E10530_01/doc/epm.931/html_esb_techref/config/clearlogfile.htm
Yet another would be to set SSLOGUNKNWON to false to cut down on the log.
See: http://download.oracle.com/docs/cd/E10530_01/doc/epm.931/html_esb_techref/config/sslogunknown.htm
Regards,
Cameron LackpourThanks! We already separate the log files from the data files but they still in the same hardware server. Yes, in SAN environment we really don't know where it the physical drive.
Essbase do not have log rotate option like Apache and maybe we should archive the essbase log regularly and clear it up.
We don't have much unknown member case in our log. Anyway we will investigate the option SSLOGUNKNOWN
Thanks again!

How to change error log location

I have been trying to change the location of the SQL 2005 error log. It's logging to the default location at C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG
I want to move the log location to the E drive because it can get quite large.
I already changed the setting in the SQL Server Error and Usage config tool, but this did not seem to make a difference.
Can someone tell me please how to do this?
Thank You,
Ed

The errorlog location is controlled by the -e startup parameter, which is read from the registry at startup.
You can change the default location from the SQL Server Configuration Manager. Open the properties for the SQL Server Service and find the Startup Parameters entry on the Advanced page.
By default the entry looks something like this:
-dD:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf;-eD:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG;-lD:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
Change the path after -e to be anything you'd like.

How to import this package com.sap.tc.logging.location?

Hi, all,
I can't import this package into programming area since i'm using com.sap.tc.logging.location. I think my developer studio does not have such package. Do you know how do find such package and import it in the studio?
Logging location.
private static final com.sap.tc.logging.Location logger =
com.sap.tc.logging.Location.getLocation(Exc_EJB_Component.class);

hi
try to see your package is avalible into Navigator prosective. if it has then import it from here itself
thanks

Essbase log files

Does anyone know what the info codes are at the end of the various lines in the Essbase log files. eg: [Wed Oct 22 08:18:17 2003]Local/ESSBASE0///Info(1051164)- id like to understand what "info (1051164)" is

If you have licensed the Essbase API, on your essbase server there should be an essbase\api\include folder. In that folder there should be a file called message.txt that has a list of all the codes and messages associated with them.If you have a newer version of Essbase, some of the messages are documented in greater detail in an html document in the docs folder of the Essbase server. Look for /essbase/docs/errmsgs/erhelp.htm (or something like that).Good luck,Bruce

Installer Logs Location for Troubleshooting Failed Installs.

I'm attempting to troubleshoot failed installations on packages built with the Mac version of AAMEE 3.0. Where are the installer logs located that give relevant failure information? The system log only passes along the generic "The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance." message when the install fails. Thanks.

The detail logs can be found at PDApp.log file present in user specific temp folder. You can find this folder using %temp%\PDApp.log (if msi is run from logged-in user account) OR [BootDrive]:\windows\Temp\PDAp.log. (No user logged in)
Thanks
Saransh Katariya | Member of technical staff | Adobe Systems

Logging location

What is logging location in web dynpro java application.
why it is used?
what is the meaning of the following statemant:::::::::::---->>>>
private static final com.sap.tc.logging.Location logger =
com.sap.tc.logging.Location.getLocation(Sarb_1View.class);

Hi,
Add -Dweblogic.Stdout -Dweblogic.Stderr flag while starting the managed server .
For setting the flag follow the below steps
If your using Linux box and not using node manager to start the managed server,add the below line startManagedWebLogic.sh file
JAVA_OPTIONS="-Dweblogic.Stdout=/var/log/weblogic/mfgeodev1.log -Dweblogic.Stderr=/var/log/weblogic/mfgeodev1.log ${JAVA_OPTIONS}"
echo "JAVA_OPTIONS=${JAVA_OPTIONS}"
If you are starting the Managed server through the node manager then use these flags From Admin console : servers >>>mfgeodev1 >>>> server start >>>> Arguments--> -Dweblogic.Stdout=/var/log/weblogic/mfgeodev1.log
-Dweblogic.Stderr=/var/log/weblogic/mfgeodev1.log
Please rotate these logs on hourly or daily basis
Regards,
Fabian

Print Service -- Queue Log location

Hi,
I'm sure this is just a minor thing I should know, but I'm trying to find the individual Queue logs. In reading the OS X Server -Print Server Admin document, it mentions:
A print queue log records information such as the name of users who submitted
jobs, the size of each job, and errors associated with a job.
It then tells me how to view a Print Service log which only contains info on the Print service itself, but not how to view the individual Queue logs. I've dug around for the past 2 hours but cannot locate it. I'd really like to have a log of that info-- any help would be much appreciated.

I appears the nature of this question has changed a bit. I can't the queue logs because it appears my jobs are not being processed by the server.
Here's the deal. I have a 10.6 lab set up pointing to an 10.6 server. All of the lab computers are set up to printing, using the printers provided by my MCX prefs. When you print a document from the workstation, it processes and prints as expected-- however at no point does the server have this job appear in the queue.
I just want to see if there is something I've missed. I set up the server with the printers I want in my queue. I then added said printers to the list via workgroup manager. The workstations see AND print to only the printers supplied in workgroup manager. But it appears that jobs do not actually go through the queue-- it's almost as though they bypass the server and print directly to the printer. Is there a step I left out?

Where is system.log located? (In the filesystem, outside of Console.app)

Where is the system.log file actually located? I know of course that I can view its contents in Console.app, but I just want to know where this text file is actually located. Or is it an almagamation of multiple files merged together or something, so that's why there's no actual location for it?

Macintosh HD > private > var > log
Found by using Reveal in Finder onthe menu in Console

Configuring log location for Adobe Document Services specific log

Hi All,
Interesting one for you. I am currently helping to resolve a PDF rendering issue which is intermittent. I have sent the default trace logs to SAP, however, there is an additional adobe specific log which should be written to /usr/sap/<SID>/SYS/global/AdobeDocumentServices/renderErrorLog/errorFiles. However, my default trace is saying that they are written to the the wrong SID and also puts a double // between gloab and AdobeDocumentServices, which of course is never going to work.
The system in question is a fully supported system copy of our Production environment, created using SAP sapinst tools.
If anyone can point me in the right direction to edit/configure the renderErrorLog location I would be most relieved as there does not appear to be anything in the Visual Administrator or Config tool.
many thanks

Hi,
All the form-related services have to be started first: the IIOP on dispatcher and server, all the Document Services *, PDF manupulation and XML form module.
Then you should be able to register your credential.
Francois

Essbase log location

Similar Messages

Maybe you are looking for