SQL Drill-through Password Update

Hello! Is it possible to use a script to update the password defined for the SQL Drill-Through? Our security policy does not allow the use of graphical user inteface at the production environment (Integration Services Console)... And we have to change the passwords monthly... Thank you!

You can have a "drill thru" defined to give you a view of lower level data that is not stored in your essbase cube. For example you may store only employee numbers in your essase cube, but from time to time you may need to know all details of an employee. You would setup a drill-thru using employee number to hit an SQL database and find all details for that employee (using the emplyee number). Its basically just a method of showing very low level data which would not be stored in a cube. You can define the drill through's using EIS.

Similar Messages

SQL Drill through??

I am new to the Essbase world. We have a few business requirements that requires us to report on a flat measure (it does not make sense to be a part of the cube as it can not be aggregated across dimensions) along with other measures from the cube. We were thinking about doing a drill through to relational db.We do not have integration server installed. The server options on the Application manager indicate that we have SQL Drill through & SQL interface options. But what I am not sure is how to specify a measure as drill through & how would I be able to drill through a specific relational table. Could some one tell me if I can do this without HIS? Any ideas or suggestions would be greatly appreciated.Thanks,Nithya

with vba, you can easily issue a sql query on a relational data source base and have the results placed in it's own sheet. (for free)look under ado (access data objects) in programming references for vba or vb.If you have any vb programmers in house, they could set something up for you in minutes.This is an often overlooked method of retrieving relational information based on the multidimensional criteria from an Essbase report.howard314-406-4022

EIS Template SQL Drill through

Has anyone been able to successfully use the template SQL drill through option in EIS? It seems that any modification to the default code only results in the error message "No display columns defined for a selected report". Maybe I'm missing something fundamental but can't get anything from the limited documentation. Without the paramaterization clauses, the SQL executes fine in a native query tool.

Maybe I could state my issue another way.
The reason I wanted to pass a data value to the drill through report is to utilize the Filter security defined in Essbase. If the user has access to an intersection point that has data, then the drill through should execute.
The security hole is when a user doesn't have access to an intersection point, they can still execute a drill through report and get to the detail. This does require a sophisticated user. I know you can apply security to the SQL data source and require a log in with the drill through, but I was hoping to avoid that mess.
Thanks,
Scot

EIS drill through reports in Analyzer

I'm having trouble pulling SQL drill through reports defined in EIS when using Analyzer. I can pull the report when I'm in Excel, but when I go into Analyzer and double click, I get the related content box to open, but no links to the drill through report. I did some searching on the Hyperion support site and found an entry in the knowledge base that said the Grid API option had to be turned on for this functionality to work. Of course there was no mention of how to turn the Grid API on and I have not been successful in finding anything in the install guide or the admin guide. I'm using Essbase 7.1.5 with EIS 7.1.2 and Analyzer 7.2.5. Is anyone using Analyzer to successfully pull EIS drill through reports? Did you have to turn on the Grid API option? How is this feature turned on? Or, any other suggestions? TIA

Hi, I am also facing few issues related to AIS: I am unable to use Drill Through (1) Smart View: It is asking for Connections and i am unable toprovide Shared Services Provider Information. It throws an error.In case i use URL as add feature then it asks for credential butstill no luck (2) Then i tried to used Add-In Excel and (This is my 1st time):When i double click on the data figure based on Intersaction leveli defined, it is taking me LRO's and now i don't know hoe toproceed further Can anybody help me?

SQL Drill Error

We are in the process of upgrading from 5.0.2 p11 to 6.5.1. After uninstalling 5.0.2 p11 from user desktop and installing 6.5.1 I get the following message everytime I open the excel add-in: "Could not load SQL drill-through customadd-in". Tech support said to remove the entries in the Essbase.ini file. The problem with that is that is NOT a Essbase.ini file on the PC. Any help would be appreciated.ThanksMike

Don't work with Essbase release 6.5.1 since the essbase.ini file is not used anymore (cf. registry)But, it is because of the "sqldrinl.dll" which is missing in the essbase\bin repertory.I've tried this by copying the "sqldrinl.dll" file from an old release 5 version of Essbase to the 6.5.1's and it's fixed the problem.Nevertheless, I can't trust in this kind of solution.

SQL Drill Thru (v502p13a) and Excel Client(V6.1.5): Formatting Sucks

Sorry about the last note, caffeine got me a little jumpy!I got the SQL Drill through working rather well. Fast, efficient, and the users like it. (I guess I keep my job for another week or so). Anyway, the format of the returned data is brutal. It is text, and nothing can be done in Excel to change the format. The field's datatype is decimal (15,2) and the data is number formatted from the high priced ERP system. So, of course, it makes no sense to me.Any workarounds out there? One thought. The SQL Drill Thru has a section where you can add a pre or post connection .dll. Maybe something there with formatting capabilities would resolve. We do NOT utilize Hyperion Intergration Server.Any suggestions would be appeciated. [email protected]

I don't recall if it was an option in the Essbase 5 client, but if you could create a VBA macro to invoke the SQL Drill through rather than using the Add-In menu, then you could build some macros to clean up the format a little.Other than that, I'm not sure what (easy) solution there would be.Regards,Jade------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

How to filter records in EIS drill through using template SQL

Hi,
I'm looking for an option to filter records in EIS drill through using Template SQL.
For eg: If we user runs drill through on 2011, it should restrict display of Jan & Feb and should display records for other months.
I tried using NOT IN clause, but got an error.
Can any one help me in understanding how this needs to be defined in template SQL
Thanks in advance

Hi Glenn,
I'm able to filter the records for specific periods.
However, I'm facing another problem now.
When I try to run drill through I get 'OLAP_error (1192025): Unknown Error: Not a valid Entry' error.
This is happening when I include condition as ((($$ab.ACCOUNT_CODE-COLUMN $$) IN ($$Account-VALUE$$)))
Here, ACCOUNT_CODE is field from Account dimension table and 'Account' is the name of the dimension.
If I remove this statement and run drill through, it runs but shows data for all accounts (irrespective of the Account selected)resulting in incorrect data.
Our RDBMS is Oracle. Can you please help me with this
Thanks

SQL statement in Drill-Through

Hi, when you make a drill-through in excel add-in, is some way to get sql statement in excel? without open the EIS console.
I need this because Drill-through don't work well in a metaoutline with filter IN, so the user can use the query to execute the sql statement directly in the database.

there is no functionality to get the SQL that is about to be executed in Excel. There is a way to edit the columns or add filtering, but you really don't get the SQL statement.
You would have to design it yourself. You could grab the sql statement that is generated in the metaoutline and bring it into excel and have a macro that does the replacements.

FDM drill-through to source data residing in SQL Server

Hi-
I am trying to create an FDM app allowing for drill through down to the source residing in SQL Server tables. Is it currently possible with a custom integration script which pulls data from the source and some out of the box functionality which traces back to the source data? The drill through stops at FDM work table but I need to be able to see live data in the source. What do I need to do or install to achieve that? Thank you in advance.

Well thats news to me. I know there are some custom solutions offered by partners which can drill back to any ODBC source but I've not seen a Oracle offering. Marketing literature is not always the most reliable source of information :)

EIS - Fact Tables, Drill Through Reports & User Defined SQL

I have built a model using two factables. (Virtually one table as the two are combined in the OLAP Model.) I then built my metaoutline and I have specified an ASO cube. I built the cube and the drill through reports and then tried to load the cube.
Intially the standard SQL generated no records. I tweeked it a bit and it then loaded. However, once I tweeked the SQL I could not get any drill through reports.
Does anyone know how the SQL for the drill through reports is populated? Does it run off the user defined SQL?

I've figured it out. FYI to those curious.
The SQL for the drill through reports are specified on how the model is set up. The User Defined SQL is only for the data load.

Template SQL for EIS Drill-Through

I am trying to figure out the command that I need to add to my template SQL in an EIS drill-through report that will exclude all rows that have a 0 value in my data column when the report is executed. Does anyone have an example of how this can be done?

The $$dimension-COLUMN$$ represents the column that contains your member name in your table and the $$dimension-MEMBERCOLUMN$$ represents the member.
When you run the drill-through report the $$dimension-MEMBERCOLUMN$$ will be replaced by the member referenced in the cross-section.
e.g. if you launch your drill-though on a cell where the product ID is 100-10 then the drill-though will only pull out data for product 100-10
SELECT......WHERE SKU IN (100-10)
Gee

SAP target provisioning - 'Password Update' Rejected causes a Valid Through Update on target

Hello Experts,
we have recently noticed a strange behaviour.
Some users had a strange Valid Through value on target SAP ECC system, after some researches we found that their SAP ECC resource had different task "Password Update" in status Rejected.
The date of task rejection match with the valid through update on SAP system, but we cannot understand how the 2 things are linked..
Could you help us?
The Log says:
[2013-02-27T11:14:13.576+01:00] [oim_server1] [ERROR] [] [OIMCP.SAPU] [tid: [ACTIVE].ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: oiminternal] [ecid: 0000JoR9HvTEwGp5kRDCiZ1H1zIc000f74,0] [APP: oim#11.1.1.3.0] [dcid: f8874950d78348e2:39e64793:13c8715021b:-7ffd-0000000000013e96] oracle.iam.connectors.sap.usermgmt.integration.SAPUMProxyUserProvisionManager : modifyUser() : User update Failed
[2013-02-27T11:14:13.577+01:00] [oim_server1] [ERROR] [] [OIMCP.SAPU] [tid: [ACTIVE].ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: oiminternal] [ecid: 0000JoR9HvTEwGp5kRDCiZ1H1zIc000f74,0] [APP: oim#11.1.1.3.0] [dcid: f8874950d78348e2:39e64793:13c8715021b:-7ffd-0000000000013e96] oracle.iam.connectors.sap.usermgmt.integration.SAPUMProxyUserProvisionManager : modifyUser() : The validity date is being set to the last logon date
Best Regards,
AT

Potomac wrote:
check these bugreports :
https://bugs.archlinux.org/task/42505
https://bugs.archlinux.org/task/42353
it seems that this bug related to i915 chip ( or intel graphic card ) is fixed in kernel 3.18rc3 mainline ( we can find this kernel package in AUR )
there is also another and complete different bug when we use a kernel 3.17 and even 3.18 ( it's a random bug ) but with a similar effect : boot can hang ( the boot process suddenly stops ) :
https://bbs.archlinux.org/viewtopic.php?id=189622
https://bbs.archlinux.org/viewtopic.php?id=189324
downgrading to kernel 3.16.x is the workaround
I assume my computer is affected by one of these bugs. While I can get to the point where my window manager is loaded, everything almost immediately hangs (but doesn't freeze). Terminal windows become non-responsive and Chromium will refuse input. It's very weird. This happens with both of the 3.17 kernel updates but not in any of the 3.16 releases (including 3.16.7).
This is on an AMD system (cpu/gpu w/ open source driver). Overall 3.17 seems rather buggy.

SQL generated by EIS for Drill Through

Hello, We are currently using EIS 7.1 on AIX. When we run a drill through report on a large flat dimensional member there are two separate SQLs generated. The first SQL has a where condition with appx. half of the child members and the second one with second half. Is this due to any kind of limitation on he length of the SQL generated? If so is there any way to work around with this? THanks a lot in advance Kris

Hi Michael,
I have got the following inputs from the OLAP forum on this query:
P_S
Posts: 40
Registered: 5/29/07
How to see the SQL (OLAP DML) generated by Discoverer for OLAP
Posted: Aug 30, 2007 9:30 AM Reply
Hi,
I originally posted this query on the Discoverer forum, but it was then suggested to post it here in the OLAP forum. Please help.........
Is there a way to see the SQL (OLAP DML) generated by Discoverer for OLAP (the way we have "View SQL" in Discoverer Relational). The version in use is 10.1.2.48.18.
Thanks,
Piyush
KLaker
Posts: 1,341
From: Manchester, UK
Registered: 1/10/01
Re: How to see the SQL (OLAP DML) generated by Discoverer for OLAP
Posted: Sep 5, 2007 7:34 AM in response to: P_S Reply
Directly within Discoverer for OLAP (or Viewer)? No - because there is no way to change the behaviour of the generated SQL, you cannot add hints or create any MVs to change the SQL generated. You can trace the SQL generated during a Disco for OLAP query though by switching on some of the OLAP tuning and diagnostic features. There is more information contained in the Discoverer for OLAP Best Practices Guide:
http://www.oracle.com/technology/products/discoverer/pdf/discoverer_plus_olap_best_practices.pdf
Keith Laker
Oracle EMEA Consulting
BI Blog: http://oraclebi.blogspot.com/
DM Blog: http://oracledmt.blogspot.com/
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
BI Samples: http://www.oracle.com/technology/products/bi/samples/
Regards,
Piyush

HT201412 My phone went through an update now won't let me in. Reset on my computer and phone doesn't accept new password.

My phone went through an update now won't let me in. Reset on my computer and phone doesn't accept new password. I went on line and changed password & confirmed ID and it still wont let me in. Refuses to go to main screen! WHY?

I am having the same problem.

Error on the reports with drill-through links on SSRS 2012 SP2 -- Invalid URI: The Uri string is too long

Hi, We are migrating SSRS 2008 R2 reports to SSRS 2012 SP2. (PS. SSRS 2012 SP2 has been applied.) Everything went smooth expect some reports which were using reporting services. These reports have some drilin-through actions and was passing in a huge
xml parameter. I referred to some other posts in which there were also some similar issues like "The Uri string is too long." but they're different. My reports can be opened and the error only occurred when accessing the drill-through actions.
As I know, Microsoft has provided the fix for the known issue "The Uri string is too long." in sp1 but it looks it can't cover this kind of situation since I have installed the SSRS SP 2. Is there any solution? In addition, there's no such
issue on SSRS 2008 R2.
Thanks,
onizga

Hi onizga,
According to your description that you are migrating SSRS 2008 R2 reports to SSRS 2012 SP2, after migration you got some error like “The Uri string is too long” which only occurred when accessing the drill-through actions, right?
Usually, the issue can be caused when you try to pass some parameters that cause the URL length to exceed 65,520 characters for a Microsoft SQL Server 2012 Reporting Services (SSRS 2012), you cannot render the report, and you may receive the following error
message:
The value of parameter 'param' is not valid. (rsInvalidParameter).Invalid URI: The Uri string is too long.
This is an known issue and already have the hotfix SQL Server 2012 Service Pack1 Cumulative Update 9 (CU9) as you know, you can try to reinstall this hotfix to fixed this issue:
http://support.microsoft.com/kb/2916827 .Any issue after applying the update, please post it on the following thread or you can submit an feedback:
http://connect.microsoft.com/SQLServer/feedback/details/788964/ssrs-2012-invalid-uri-the-uri-string-is-too-long
Similar threads for your reference:
SSRS - The value of parameter 'param' is
not valid. ---> System.UriFormatException: Invalid URI: The Uri string is too long.
Microsoft.ReportingServices.Diagnostics.Utilities.InvalidParameterException:
The value of parameter 'pSetOfScopes' is not valid. ---> System.UriFormatException: Invalid URI: The Uri string is too long
If you still have any question, please feel free to ask
Regards
Vicky Liu
If you have any feedback on our support, please click here

SQL Drill-through Password Update

Similar Messages

Maybe you are looking for