Maxl Error

I am trying to load data from RDBMS using maxl script. I am using this script
import database Rollout.Rollout data
connect as Suman identified by kolkata@1
using server rules_file 'Rul_DB.rul'
on error write to 'C:\Hyperion\AnalyticServices\app\Rollout\Rollout\ErrorLog_RDBMS.txt';
I am getting this error:
syntax error near ['@']
In password i have the '@' symbol. I am getting no other error. Please help me to fix this issue.
Regards,
Suman

I'd try ruling out the password first then. Have you tried putting it in quotes? Another thing you could try is changing the password temporarily if that is possible.

Similar Messages

MaxL error 1241114 - There were errors, look in...

I am running the following MaxL in a batch script on one of our Essbase cubes, which passes the MaxL to ESSMSH.
MaxL:
login admin identified by ******* on *******;
iferror "errorhandler";
spool stdout on to "\\*******\\*******\\Logs\\*******BefLoad.log";
iferror "errorhandler";
spool stderr on to "\\*******\\*******\\Logs\\*******BefLoad.err";
iferror "errorhandler";
set timestamp on;
execute calculation "'FIX(\"*******\",@ICHILDREN(\"*******\")) CLEARDATA \"*******\"; ENDFIX'" on *******.*******;
iferror "errorhandler";
import database *******.******* dimensions from data_file "\\\\*******\\FDMDATA\\*******\\Outbox\\*******.Dat" using server rules_file "L_Data" preserve input data on error append to "\\\\*******\\*******\\Logs\\*******BefLoad.err";
iferror "errorhandler";
logout;
exit 0;
define label "errorhandler";
exit 10;
However, every time the MaxL executes, I have the following single line generated in the "\\*******\*******\Logs\*******BefLoad.err" file:
WARNING - 1241114 - There were errors, look in \\*******\*******\Logs\*******BefLoad.err.
This error is actually pointing to itself (the .err file), however this is the only line with no further information, and is generated every time the batch script is run, even though the build appears to have worked fine. I have double-checked and there are no errors (or even warnings) in the Essbase application log to suggest anything has gone wrong!
Does anyone please have a suggestion as to why it is being generated? Can we just ignore this error? I have read the following, which points out that data load errors will not be trapped by the MaxL "iferror" statement. However, it would be useful to know why this error is occurring and specifically what is going wrong.
MaxL Error Codes

Hi James -
Your dataload errors are getting spooled to the same file as Essbase is trying to spool the message saying that there were dataload errors. I wouldn't count on that working the way you expect it to, and it's not an approach I have ever used - I'd think keeping the stderr spool separate (i.e. separate files) from the dataload errors makes sense.
My bet is that if you point the two error streams to different files you'll see that there are in fact load errors, they're just getting messed up by the fact that stderr and dataload errors are pointing at the same file.
BTW, I appreciate that you're anonymizing for client confidentiality (amazing how many folks post info that obviously identifies their company and give out server / user names...), but any chance you could use e.g. 'appname', 'dbname' etc rather than *******? Asterisks make my eyes hurt, but more importantly they make the different tokens impossible to distinguish. Cheers!

MAXL error handling

Can someone show me an example of MAXL error handling, especially in cases of copying or creating an app/db and it already exists?Thanks,Alex

Hi,Can someone explain what advantages enterprise has over reports?

MaxL error tracking II

I have a simpler question about tracking errors from a Maxl script. I run a Unix script that calls Maxl to back up the Essbase applications. I just want to trap the return code and send a email if there were any errors from the Maxl script. I'm using the follow code to trap any errors from the Unix commands. This is working for the Unix commands but does not reccognize errors from the Maxl script. Is there a way I can set the return code in the maxl script to non zero when an error occurs. Currently the return code is zero after returning from Maxl when an error occurs.
error_message()
mailx -s "Essbase backup error" email@... < /opt/BackupError.txt
trap 'error_message' ERR
set -e
cd /opt/hyperion/HYP_BACKUP/scripts
/opt/hyperion/AnalyticServices/bin/essmsh < /opt/staff/MaxlScript.msh > /opt/staff/Maxl.log 2>$1
exit
Thanks,
Tom

I'm no *nix jockey, so you're going to hear this from a Windows perspective.
In Windows, %ERRORLEVEL% will return the error code, sometimes. See my comments in this thread: MaxL error tracking
A more robust approach would be spool errors to STDERR, and then test to see if that file exists, and if so, what's inside.
^^^Probably not what you wanted to hear.
Regards,
Cameron Lackpour
Edited by: CL on Oct 1, 2009 2:10 PM
Just an add on that writing a routine that interrogated the file shouldn't really be that big of a deal. Once you code your own way on this you can pass whatever value you want on to the calling code.

Maxl - Error while building dimension

Hi,
I am using below syntax in Maxl for building dimension. I am getting error. Could someone help me with this. I am pulling the load rule using SQL
import database 'Application Name'.'Database Name' dimensions connect as 'User Name' identified by 'password' using rules_file 'Buildfilename' on error write to 'D:\Error.txt';
Thanks

Try this
import database 'Application Name'.'Database Name' dimensions connect as 'User Name' identified by 'password' using SERVER rules_file 'Buildfilename' on error write to 'D:\Error.txt';

MAXL error logging

Hi Guys,
I have a script to import a number of dimensions, this was previously done with an Esscmd script but is now in a MAXL script. Is it possible to write to an error log for each dimensionn I dont seem to be able to get the syntax correct;
import database Appname.DBname dimensions
connect as 'user' identified by 'password' using server rules_file 'Products' preserve all data on error append to '\\\server\\share\Products.err',
connect as 'user' identified by 'password' using server rules_file 'Customer' preserve all data on error append to '\\\server\\share\product.err',
and so on, this will error at the first comma at the end of line 3, if I replace the comma with semi colon the first statement is executed ok but not the second.
All help appreciated
Ed

What happened is that you used the error file after each transaction, you should add the error file after your last transaction or build. Or if you want to have separate error files you have to have separate statements for each dimension build that starts with 'importdatabase Appname.DBname dimensions'.
here's a sample of a single statement:
import database sample.basic dimensions
from server text data_file 'genref' using server rules_file 'genref' suppress verification,
from server text data_file 'level' using server rules_file 'level' suppress verification,
from server text data_file 'time' using server rules_file 'time'
preserve input data on error append to 'C:\Hyperion\EAS\eas\client\dataload.err';

MaxL Error Codes

Hi,
We have many MaxL scripts to load, calculate, export databases etc.... The client wants more precise error messages in the emails the scripts send out to help them decipher what the problem may be in case of a WARNING or ERROR. Is there a list of all possible error codes MaxL would create in the .log? Here's an example of one that is created by changing a member name in source file to make it fail.
WARNING - 1241114 - There were errors, look in C:\Automation\Dev\Logs\Revenue\revload.err.
I'm trying to avoid having to think of every possible type of failure and making it fail on purpose to capture these errors. Was hoping there is a list of all that I could reference?

There are two kinds of errors in MaxL -- command errors and errors that Essbase passes back.
The Essbase data load error you've identified is of the latter type and is not going to get trapped by MaxL's iferror. Unfortunately.
For errors that MaxL can trap (I bet you know the below, but there is something new in 11.1.2.x that's worth reviewing) there are now unique error codes which, I suppose, is what you don't want to do, but it's still an interesting function.
Check out this for a general overview of branching on error:
http://download.oracle.com/docs/cd/E17236_01/epm.1112/esb_tech_ref/maxl_commands_errs.html
And of course there's the new Exit function that allows you to pass an error code:
http://download.oracle.com/docs/cd/E17236_01/epm.1112/esb_tech_ref/frameset.htm?maxl_commands_exit.html
^^^That's pretty cool and I need to write up a blog post on it, to teach myself to use it if nothing else.
Regards,
Cameron Lackpour

MAXL Errors in a Working Script

Hi All,Making the transistion to MAXL from ESSCMD under Essbase 6.2. I have a script that successfully builds two of my dimensions using the SQL interface from Oracle. What's strange is, even though the script works, mid-way through MAXL log file, the following error appears:9 - Essbase error encountered: [BuildDimFile:'test'] [1030001].Then at the end of the file, it states:51 - MaxL execution failed.Anyone have any idea why MAXL is reporting failure, when the script is actually working?

Is that this error?:##1003001 Duplicate Members From Same Dimension On Data Record, [%s] Records CompletedIf so, could it be that this error is not fatal and that maxl just doesn't know the difference between a fatal and non-fatal error?-z

MAXL ERROR - 1013145 - Invalid agent login id

All,
We are trying to automate the process of data load and Calculations using Maxl. Unfortunately we see the below mentioned error while performing the calculation in MAXL.
MaxL command:
execute calculation app.dbname.test;
ERROR - 1013145 - Invalid agent login id
But while executing the same command in Maxl editor, it works fine.
Regards,
Nainitha.

Are you doing a stop and/or start app command(or disconnect users) anywhere near while executing the mentioned calc scripts/data loads? I have seen on some occasions that these errors also come up due to stale ESSSVR processes in the background (rare, although possible)
As an example, you might be logged in as admin ID but however, if anywhere there might be a MAXL command and or activity that is causing the app to disconnect users/sessions (idle of course) before running the calcs. This error might be the result of that?
All this is assuming that the security set up for the admin ID is correct, right?
Also, since you mentioned that this error is coming only on Data exports/calc scripts. I am assuming this error comes up only when Essbase is trying to output a file to the drive/path. Does the OS environment login/ID credentials have that authority?
From whatever i could deduce of this, this might be happening because of either one of two reasons :
1.) Security is not setup correctly for that operation to complete (export to that path might not be authorized?)
2.) The user ID is being logged off/disconnected before that operation kicks off.
Thanks and regards,
Harsh Warikoo

MaxL error tracking

Hi, could you advise me if there is a way to execute a oracle package from a Maxl.
We have a oracle procedure mxl_status(process_name, status, error_message). our theme is to embed this procedure in the batch/maxl script so that if the Essbase dimension build/data load process fails, the essbase error code with description will be stored in the table used by the procedure. Any way to capture the error message only to variables and pass this to the oracle procedures is appreciated.
Thanks
Subbu

RS,
When I say, you cannot capture error message in MAXL, it does not mean that you have no means of doing it. You can prestore the error codes and messages in a 2 column table and refer it while running the stored procedure.. Check for Message.txt file in $ARBORPATH/api/include, if you installed API with Essbase..The error code that MaxL returns is going to get reset by the next process. So you're probably going to need an iferror statement to branch to exit to trap the error code externally.
Also, there are different kinds of errors as far as OS trapping is concerned. A bad password on login will throw a 1051293 (which is the actual Essbase error code) to %ERRORLEVEL%, but bad data in a data load that results in rejected records -- not an error, and a 0 to %ERRORLEVEL%.
Personally, I would trap the existence of STDERR. That will capture all errors -- the big ones that show up in %ERRORLEVEL% and the minor but still important ones like data got rejected. You will get both the error code and the description from that.
Here's an example of myprocess.err:
ERROR - 103 - Unexpected Essbase error 1051293.
ERROR - 1051293 - Login fails due to invalid login credentials.
To your point -- execute the MaxL script in DOS/Bourne/Korn/VBScript/whatever, check for the existance of the error file and it's contents, have another non-MaxL process pick it up and write its contents to a table. And then of course do whatever you want based on the error.
I always enjoy this stuff -- I don't know why. Maybe because it's because I think once, do it, and never worry about it again.
Regards,
Cameron Lackpour
P.S. As I'm on the ODI bandwagon -- you could do all of the above in an ODI package and it would likely (once you got over the ODI learning curve) be far faster than coding it in a scripting language.

MaxL error translation

I'm trying to get MaxL to skip certain parts of a script on error like ESSCMD used to do without splitting up the scripts into multiple separate parts. I've heard that the PERL module can take care of errors, but I can't find a way to use perl to handle errors without splitting up the scripts. Anyone have experience doing this? Thanks in advance!

Hi,Can someone explain what advantages enterprise has over reports?

Maxl Error during data load - file size limit?

Does anyone know if there is a file size limit while importingdata into an ASO cube via Maxl. I have tried to execute: Import Database TST_ASO.J_ASO_DB datausing server test data file '/XX/xXX/XXX.txt'using server rules_file '/XXX/XXX/XXX.rul'to load_buffer with buffer_id 1on error write to '/XXX.log'; It errors out after about 10 minutes and gives "unexpectedEssbase error 1130610' The file is about 1.5 gigs of data. The filelocation is right. I have tried the same code with a smaller fileand it works. Do I need to increase my cache or anything? I alsogot "DATAERRORLIMIT' reached and I can not find the log filefor this...? Thanks!

Have you looked in the data error log to see what kind of errors you are getting. The odds are high that you are trying to load data into calculated memebers (or upper level memebers) resulting in errors. It is most likely the former. you specify the error file with the on error write to '/XXX.log'; statement. Have you looked for this file to find why you are getting errors? Do yourself a favor, load the smaller file and look for the error file to see what kind of an error you are getting. It is possible that you error file is larger than your load file, since multiple errors on a single load item may result in a restatement of the entire load line for each error. This is a starting point for your exploration into the problem. DATAERRORLIMIT is set at the config file, default at 1000, max at 65000. NOMSGLOGGINGONDATAERRORLIMIT if set to true, just stops logging and continues the load when the data error limit is reached. I'd advise using this only in atest environement since it doesn't solve the initial problem of data errors. Probably what you'll have to do is ignore some of the columns in the data load that load into calculated fields. If you have some upper level memebers, you could put them in skip loading condition. let us know what works for you.

Maxl Error Detection

Hi All,
I am trying to find some info/suggestions how to detect maxl run time error in a shell script (unix environ) that calls multiple maxl statements. It is to be interfaced with sending email messages to dba group in the scenario. I am not aware how to parse info from maxl shell in case it fails and then how to integrate it with email msgs. Any recommendations/advise would be welcomed.
Thanks,
munish

While this is not what you are looking for, it may give you a path to follow: Re: Weird problem using "Login" in MaxL script
The core concepts:
1) Use of a shell script to manage the overall task
2) Redirection of both normal output and errors via OS pipes rather than scripted logging
3) Scanning of the output file for lines containing an "Error" token
4) Filtering of some errors by error code
5) Responding to remaining errors by email
The FOR command is used heavily because this batch script was written for Windows, in Unix you have much more flexibility and power with grep and such. It should be easier for you, although I am too rusty to convert the script in the absence of a dire need.

ASO Allocation Maxl error

Syntax error in input mdx query on line 1 token ","
Allocation terminated with essbase error 1260052 in POV
execute allocation process on database ASOALLOC.ALLOCAT with
pov "crossjoin([Year].[FY10],
crossjoin([period].[Jan],
crossjoin([account].[a111],
([Entity],[Entity].levels(0)))))"
amount "([account].[a111]"
target ""
range "{[Entity].[e222]}"
spread;
Edited by: mb021059 on Oct 13, 2010 5:13 AM
Edited by: mb021059 on Oct 13, 2010 6:53 AM
Edited by: mb021059 on Oct 13, 2010 7:00 AM

I really don't understand what you are trying to do (may be because you are in 11 version{allocation in ASO cube sounds kool).
but I can tell you the syntax error you are getting at first line.
change it to:
"crossjoin([Year].[FY10],crossjoin([period].[Jan],crossjoin([account].[a111],[Entity].levels(0))))"
Thanks,
Jeeth
Edited by: Jithendra on Oct 14, 2010 5:20 PM

Problem while copying outlines with MaxL (error 1241167)

Dear all,
I'm trying to copy outline to database1 on server1 from database2 on server2.
When I run my script, I get the following error message : "ERROR - 1241167 - Database xxx.yyy is not on a block storage application."
Isn't it possible to copy outline from an aggregate storage application to another aggregate storage application ?
Thanks in advance,
Lionel.

>
When I run my script, I get the following error message : "ERROR - 1241167 - Database xxx.yyy is not on a block storage application."
From the error message I understand that you might be trying to copy a block storage outline to an aggregate storage outline. Check the source outline you are migrating is an ASO outline or not.
Hope this helps!

Maxl Error

Similar Messages

Maybe you are looking for