Why server file loads are quicker

Most of us know that if the data file exists on the server (especially in the database directory) and we do a data load it is faster than if the file is on the client. But what do EAS and MAxL actaully do when the file is on the client machine? If you look at an EAS data load,  when you start it, you see the box:

When the dialog hits 100%, in the message area of EAS, you will see a statement something like:
User selected data file ‘C:\temp\data.txt’ is uploaded to server for execution at location d:\Oracle\Middleware\user_projects\epmsystem1\tmp\tempfile9706446338807355961.txt
(your path will vary depending on what version of Essbase is installed)
EAS uploads (FTPs) the file onto the Essbase server then processes it. When the process is complete, it deletes the file.  What is the implication of this. Aside from being slower that having the file on the server, it is possible that aborted loads are leaving dead files in the temp directory. I had a system where the number of files and space consumed became significant.
Talking about slower, at a client I’m at, I tested the differences in load time. I’m connected over a VPN connection and have a data file that is 65 meg. For each test, I loaded into the same empty ASO database.  I’m running the web version of EAS so it is on my local machine.  Running the data load process with a client file took about 36 minutes.
Running the same file on the server in the database directory took less than 1 minute. 35 minutes of savings which is significant when you are waiting for processes to run.
To improve my time overall since the files were on my local machine, I would zip them up, copy them to the server, unzip them and then process them. In all I saved about 20 minutes off EAS’s client time. This showed me that the upload does not do any file compression when it copies the file.

Update note:
I've talked with a few people that have read this post and need to clearify. When I talk about a server file, I mean the file should be in the application/database directory on  the server. This way EAS recongnizes it as a server file. The easy way to check if the system thinks it is a server file is to open up the load utility in EAS and select find file. Click on the server tab. IF the file pops up, it is in the right place (It should be saved as a txt file to make life easier).


While this will not affect most people as they are doing their processing on the server or in house on fast networks, it does help to understand what EAS and MaxL do when you have a client file to load.
This is just a single tidbit of the type of information you can get at Kscope 11. I’ll be presenting a couple of sessions. One on Advanced Essbase Studio tips and another one on the exception to the rules on outline design. I think both are pretty good sessions. Come see for yourself and let me know. I’m sure I’m going to get sucked into some other sessions , like a panel or two on Hyperion.
If you want to save $100 off of registration,  enter the three character code IRC   (which stands for interRel consulting). I’m not sure how long the code is good for, so don’t wait too long.

Essbase Studio book released (Finally)

It took a bit longer than I expected, as the editors, especially Cameron Lackpour, found numerous little issues that needed to be fixed, but the Look Smarter Than you are with Essbase Studio book has finally be released to the general public. You can go to Lulu.com and just search for Essbase Studio books. It will be the only one or if you are smarter than I are, you can just click on the link Studio Book and go right to it. If you are at the Collaborate 11 conference, you can get it quicker as they have some copies in the bookstore. 

You can even preview the first chapter of it without buying it (I think it is the funniest chapter). 

Wolf, Wolf, Wolf 11.1.2.1 is HERE NOW

Like the little boy who cried wolf once too much, I doubt you will believe me, but EPM 11.1.2.1 is now available. What’s that you say, you just looked at edelivery.oracle.com and its not there. True, but if you go to download.oracle.com and select  Hyperion Performance Management and BI, you get to Here.

Notice it says 11.1.2.1.0  So I’m not crying wolf and it actually has been released. For those of you who were waiting till April 10th, wait no more. Go and upgrade my children.

11.1.2.1 We are getting close

I can not take credit for being the first to notice, I give that to Sebastian Roux on the Network 54 forum, but the documentation for 11.1.2.1 is now available at Documentation link. The actual release can’t be far off.

The first thing I see in the readme is the upgrade path (I’m concentrating on Essbase here).

 

Release Upgrade Path From	To
11.1.2.0.x	11.1.2.1 Note that when moving from Release 11.1.2.0.x to Release 11.1.2.1, you use the "Apply Maintenance Release" option in EPM System Installer, instead of following the documented upgrade procedures
11.1.1.3.x	11.1.2.1
9.3.3.x Note: If you were using Performance Management Architect Release 9.3.1, you can download the Performance Management Architect Release 9.3.3 from My Oracle Support.	11.1.2.1
9.2.1.x	11.1.2.1
A release earlier than Release 9.2.1.x	If you are upgrading from a release earlier than 9.2.1.x, you must first upgrade to a supported release and then upgrade to release 11.1.2.1. For upgrade procedures for the earlier release, see the product installation guides for the interim release that you are upgrading to.
An environment that includes multiple releases, which can include an environment with one instance of Hyperion Shared Services or an environment with two instances of Shared Services	See “Upgrading from an Environment with Multiple Releases” in the "Upgrading EPM System Products" chapter in the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.

Note: If you are starting from Release 9.2.0.3+, 9.3.0.x, 9.3.1.x (except for Essbase 9.3.1.4.1, 9.3.1.5, 9.3.1.6, and 9.3.1.7), or 11.1.1.x, Oracle recommends that you upgrade to Release 11.1.1.3 as your interim release. If you are starting from an earlier release, Oracle recommends that you upgrade to the highest level release that directly supports upgrade from your starting release.
Security Synchronization between Essbase and Shared Services was removed in Essbase Release 9.3, starting with Release 9.3.1.4.1. Essbase and Shared Services Release 11.1.1.3, however, still synchronize security information. For this reason, if you are using Essbase Release 9.3.1.4.1, 9.3.1.5, 9.3.1.6, or 9.3.1.7, you must first upgrade all products to Release 9.3.3, instead of Release 11.1.1.3.

As time permits, I’ll go though some of the interesting enhancements (don’t seem to be many) and the bug fixes.

Not an April fool’s joke. 11.1.2.1 release date

While I am writing this on April 1st, It is not intended to be an April fool’s joke. Edward Roske had blogged that the release of 11.1.2.1 was supposed to be sometime in March. Edward's Blog Post  March is now history and there is no release. So Mr. Roske, WHERE IS IT? (Of course I’ll blame my boss for something he has no control over). I think this might be a career limiting move. 

Is the release vaporware? No not really, it is just taking longer than expected.  I’ve heard from a few reliable sources (to be unnamed) that the Release is targeted to be April 10th. I’ll put the typical and necessary disclaimer here. This is just what I have heard and not official and of course subject to change.  So at 12:01 on April 10th, the thousands of people who read my blog (Ok Cameron and three others) will descend on edelivery.oracle.com to prove me wrong. We will see.