Export and Import Planning Security Through Utility

When I am working with Planning and mainly during the forecast cycle, The security backups, export and imports are regular activities and also critical ones.

Below is a brief description of what I use for Import and Export of Security in Hyperion Planning.

- For Exporting the security

The utility used is ExportSecurity.cmd
Ideally it is installed in the path E:\Oracle\Middleware\user_projects\epmsystem7\Planning\planning1

We can use this utility to export the Planning security for a complete application or a single user or even a group.

For a complete application, one can use :-

ExportSecurity /A=AppName, /U=UserName

Note that the user should have admin prvileges

Similarly we can use ExportSecurity /A=AppName, /U=UserName,/S=User or ExportSecurity /A=AppName, /U=UserName,/S=Group for exporting user or group security respectively.

One needs to go to the specified path through command prompt and execute this command and the security file is created with the name secFile.txt in the same path.

At the end of the Export, we will recieve the completion note

- For Importing the Security

In the same path as the ExportSecurity utility, we will have another utility ImportSecurity.cmd

Firstly, we need to place the secFile.txt file in this path because the utility will look for this name to import the security.

Go to the same path at command prompt and the command would be:-

ImportSecurity.cmd "AppName,UserName,SL_COMMA,,,"

This is because the secFile will ideally be Comma delimited.
Note: Ensure you type the double quotes manually because Copy and paste from a website or other source might sometimes give other format which may not work.

Once you run this command, it will ask for the password for the given UserName.

We can find the logs for both Import and Export Security in the path : E:\Oracle\Middleware\user_projects\epmsystem7\diagnostics\logs\planning

Essbase/MaxL error: Error (1013204) Client Commands are currently not being accepted.

We were trying to execute a shell script which in turn runs a MaxL script to load data to our ASO cube.
As soon as we run the script, we face an error:

Error: 1013204 Client commands are currently not being accepted.

The clear script which was run before executing this Maxl script was at the end of completion/the session was still in process.
Restarting the application and then executing the script cleared the error.

Waiting for the other process to complete, and then going ahead with the next script should be helping in avoiding such error. Sometimes there is some erroneous lock on the application.
So restarting the application should sort this one out.

Database clear unsuccessful error in EAS

When trying to clear the data (mostly as a part of Defragmentation), we encounter an error prompting that the database clear was unsuccessful.

The clearing of data from the EAS sometimes throws an error as above.
Sometimes, we are also not able to see the Runtime parameters in the statistics tab for the cube.

Check if any changes are being made at that time by any other person.
Need to be aware in case any cache parameters settings are being changed.

A simple restart of the application and then trying to clear the data would be successful in this case.

Unable to validate Partition in EAS

Sometimes when trying to validate the Partition, it errors out saying:  Partition definition is not valid: []

And the typical error message can be:

Typically this happens when there any data movements scripts running in the background or their sessions are still in progress.
Verify that no Data movement scripts are being executed and then try to validate the partition.

We have encountered this mostly for Replicated Partitions and the solution helped every time.

#6 ODI session failed due to config xml file issue

One of our scheduled daily Load plan did not run as expected and when we drilled down the session, found an error as:







When I checked the Message Log, it said:

oracle.odi.agent.logging.AgentLogger initLogEnvironment
INFO: exception reading config file called ODI-logging-config.xml
Also mentioned are other errors ODL-52053 and ODL-52035

The detailed log had another info:
Caused By: java.sql.SQLException: ODI-40844: Could not generate the DTD because the file could not be created. Verify that you have write permission in the directory.


So going by the logs and errors, It is a bit clear that something was wrong with the config file and also related to java settings.

Opened the Connection details for the Physical Server and checked the JDBC url:

The JDBC url is as:  jdbc:snps:xml?f=http://Hostname:port/data/data/data/***_config.xml&ro=true


The day before we had a new release where additional data servers were added and the config files were changed.


What worked for me:
Appending nobu=false&ro=false in the JDBC url succeeded in testing the connection.


In the old url, ro=true made the XML file to be opened only in read only mode and sometimes the java.sql.SQLException says that while executing the scenario, the statement is not in batch mode.


As per Oracle docs:

ro or read_only :      Open the XML file in read only mode.

nobu or no_batch_update : Batch update is not used for this connection. The command to set the batch update is not sent. This prevents errors to occur for external databases that do not support this JDBC feature, or allows to debug errors related to batch update usage.

#5 Disabling ODI Schedule

This one is just to summarize the steps in doing one of the regular activities :- Disabling a Schedule in ODI

Login to the ODI Console -> Click on the Operator tab

We can find the Load plans and the schedules under Scheduling -> All Schedules

Right Click and Open the Schedule:

When the Schedule is Active, the Status will be as Active.

To Disable the schedule, Unmark Active status and set it as Inactive and then Save.

Once the change in Status is done, we need to Update the Schedule.

Click on the Topology tab and under Physical Architecture -> Agents, Right click on the OracleDIAgent and click on Update Schedule

Similarly, to get back the schedule to enabled status, mark the Status to Active and Update the schedule as above.

 

#4 Unable to launch EAS console. (easconsole.jnlp file issue)

When trying to open the EAS Console in my pc, i get the popup as to Save or Open the file 'easconsole.jnlp'
Though I save/Open it, it does no good and repeatedly asks the same thing.

Solution: Just right click on the easconsole.jnlp file and open with -> Go to the java path where you have the file javaws.exe (In my case the path is : C:\Program Files\Java\jre6\bin)

This will open the file as below:

Explanation:
The JNLP(Java Network Launching Protocol) file format is used by Java to launch and manage various Java applications over a network or on the Internet.  The files are actually comprised of a group of protocols that define the specific requirements of a JAVA launching mechanism.

Unlike typical web applets, JNLP files are not run within a user's Web browser. These files are actually downloaded onto a user's computer and are then run as normal Java applications. The files are used only for stand-alone applications.  (Source: file.org)

Javaws.exe is a web start utility. It is used to launch a java application that is distributed through web.
It is a process file from company Oracle Corporation belonging to product Java(TM) Platform SE which starts Java(TM) Web Start Launcher. The file is digitally signed from Sun Microsystems, Inc.