Constrain on Parameters

Hi All,
I want to constrain parameters on another parameter based on the selection of first parameter like we do constrain on prompts in OBIEE.Is the Refresh Other Parameter on change is the check box?
Really appreciate your thoughts
Thanks

when you create the parameters there is an option to refresh other parameters on change.
then all you need to do is reference that parameter in the WHERE clause of the SQL that you have for populating the List of Values.
-w

Similar Messages

"PDF Open Options" in Applescript

So I am trying to batch convert a bunch of PDFs to JPEG files as part of a larger Applescript, and I'm finding that some of the parameters in "PDF Open Options" are ignored. Namely, the "height", "width" and "constrain proportions" parameters.
This code is lifted directly from the Photoshop CS3 Scripting Guide (with filename changed, of course):
tell application "Adobe Photoshop CS3"
set myFilePath to alias "WABEL0457937:Users:Charles:Desktop:8925.pdf"
with timeout of 10000 seconds
open myFilePath as PDF with options {class:PDF open options, height:pixels 100, width:pixels 200, mode:RGB, resolution:72, use antialias:true, page:1, constrain proportions:false}
end timeout
end tell
In the resulting file, the "resolution" is correct, but the height and width are calculated using the PDF's original height and width multiplied by the resolution, and the image is constrained to the original proportions.
I thought it might be a collision with specifying the resolution and the height/width in pixels, so I tried omitting the resolution, but then it just defaults to 300.
Anyone else create a script that opens PDFs and run into this?

Thanks for that!
(If those parameters are deprecated since CS2, it's probably bad form for Adobe to use them in their documentation for CS3. Just sayin'!)
Anyway, it looks like the shell script you quoted gives the page height in points with an assumed resolution of 72 DPI. I can use that with my target dimension to calculate what to set the resolution to.
In case it helps anyone else, here's the working code I came up with:
-- ("str_replace" is a custom function to find and replace text in a string, it's not built-in to Applescript)
set pageHeight to do shell script "/usr/bin/mdls -name kMDItemPageHeight " & quoted form of (POSIX path of this_item as string)
set pageHeight to my str_replace("kMDItemPageHeight = ", "", pageHeight)
set pageWidth to do shell script "/usr/bin/mdls -name kMDItemPageWidth " & quoted form of (POSIX path of this_item as string)
set pageWidth to my str_replace("kMDItemPageWidth = ", "", pageWidth)
if (pageHeight as number) is greater than (pageWidth as number) then
set pdf_resolution to round (1000 / (pageHeight as number) * 72) rounding up
else
set pdf_resolution to round (1000 / (pageWidth as number) * 72) rounding up
end if
try
with timeout of 5 seconds
open alias ("WABEL0457937:Users:Charles:Desktop:Test:image_prep:" & image_id & ".pdf") as PDF with options {class:PDF open options, resolution:pdf_resolution, mode:RGB, use antialias:true, suppress warnings:false, use page number:true, page:1, crop page:media box}
end timeout
on error
-- I have some sections here that check for and handle progress windows, password prompts, and such
-- so the script can either continue or fail gracefully
end try
All of the images coming out of this script are just over 1000 pixels at their widest dimension. Since it's not critical that they be exactly 1000 (just very close), I was able to completely eliminate the resizing portion of the script to save even more processing time.
Thanks for the pointers, everyone!

Using Constraints on my optimization problem (currently implemented in Unconstrained Nonlinear Opt.VI)

I have an function f(x) that I minimize to find parameters for an algorithm. The algorithm consists of a coordinate transformation matrix. The transformation matrix parameters are currently found using the Unconstrained Optimization VI (simplex). I have had quite a bit of success using this VI and defining my algorithm as an objective function. I previously used Excel Solver for this application. The data set changes over time and certain parameters are tracked.
Whenever I perform an optimization, I move the minimum parameters found to the initial guess parameters. I am finding that my initial guess parameters will remain stable for a while but at times will guess incorrectly. This can happen if I feed the algorithm bad data. It is difficult to determine that the data is bad initially, but it causes the minimization to trail off in some crazy direction that is inconsistent with the real world. This happens after repetitive minimizations and is a result of using my found results for the next iteration. However, in an ideal world, my last found results would be the best initial guess for the next optimization I perform.
One major improvement would be to constrain my initial guess parameters. In particular, I would like to constrain the parameters I use in finding the transformation matrix (in my objective function) with lower and upper limits: 9 < R < 12, for example. Can anyone with experience using the optimization VIs, knowing the information above, help point me in the right direction? I came across the Constrained Nonlinear Optimization VI but it appears to work much different than the Simplex method; so I am not sure if this would work. I will try this next. Any thoughts?
Chris Walker
Certified Labview Developer

I tried using the Constrained Nonlinear Optimization VI. I first tried it without any constraints (min or max constraints) on my parameters and it appeared to work. I could change the initial guess parameters and they would eventually end up the same minimization each time (with the same set of data). Once I add the parameter constraints, however, the VI freezes on the first iteration and I have to abort. I am not sure why and I do not get any errors.
After some testing, it appears that the cno_isisubopt.vi subvi inside the Constrained Nonlinear Optmiziation VI is locking up. The code is attached. If I had to guess, this probably has to do with the input L advancing to Infinity and never allowing the while loop to stop. I am not sure what the internal workings of this VI are so this appears rather difficult to debug!
This is an error that is not tracked or handled by the Constrained Nonlinear Opt Labview VI; thus freezing my program.
Chris Walker
Certified Labview Developer
Attachments:
4-4-2012 9-36-53 PM.jpg ‏158 KB

Dealing with functions not in class Object

Hi,
while i was working on GJ i faced the following problem, when i write a generic class i have to take into my consideration those functions that i want to define for the row type class and not included in class Object (toSting() is in class Object but print() is not). of course every time i want to call print() from the generic class the compiler gives me an error becuz it is not in class Object.. is there anyway to get rid of this problem in a simple way without having to deal with more than one row type ?
thanks everyone

I think I see what you're getting at...the GJ compiler substitues Object for all unconstrained type parameters, and therefore tries to call methods on parametized type objects as if they were simply of type Object.
A solution would be to create a base class (or interface) AbstractRow that declares all the methods you need. Then constrain your parameters against AbstractRow. Eg:
public interface AbstractRow
public AbstractRow rowMethod();
public class MyClass<RowType extends AbstractRow>
public RowType doSomething(RowType rt) {
rt.rowMethod();
I think that should work. I'm not sure what you meant by "without having to deal with more than one row type." If you meant "without having to introduce an inheritance hierarchy," then no, this is not possible in GJ (as far as I can tell). If you meant "without having to write adapters for every single row type," then yes.
shaun

How to constrain parameters in Lev-Mar?

It's a common case for non-linear fitting.
How can it be done in LabView's Lev-Mar?
Thanks.

The provided LabVIEW implementation does not contain options for parameter bounds.
One solution would be to re-parametrize your code in terms of unconstrained variables that cause a constraint on your original parameters.
Some transformations for one-sided or two-sided parameter bounds are given here:
http://www.id.unizh.ch/software/unix/statmath/sas/sasdoc/stat/chap19/sect41.htm
The link also lists references with more details.
LabVIEW Champion . Do more with less code and in less time .

How to manage different supply parameters for the same item based on demand quantity?

We are using unconstrained ASCP. We have some products that can be produced in a 'small' machine or can be produced in a large tank. If ASCP has created a planned order for a quantity less than 1000 it will be made on the small machine with the supply quantity = demand quantity. For example, we have a demand of 250, we will make exactly 250 on the small machine. But if the demand quantity is greater than 1000 we will make the supply in the tank with a fixed order quantity of 1590. Financially it will cost us less to do this and scrap the difference because the small machine is very expensive to run compared to the tank.
The challenge is, say we need 1200. ASCP generates a planned order for 1200 and all the dependent demands support 1200. Now we want to make 1590 and we are short of materials. This assumes we have set the item with no supply parameters. On the other hand, if we set a fixed order quantity of 1590 but only need 100 then we we have to scrap the materials for the balance due to a short shelf life.
Any ideas how to set a supply quantity using different parameters based on the demand quantity?
Mark Madal

Hi Mark,
I personally don’t see any standard solution for this requirement especially with an unconstrained plan.
However, if it is feasible, you can try below solution with a 'constrained plan with decision rules enabled' and check if it works,
1.   1. Define two different items – Item A and Item B
2.   2. Item A uses small machine in its routing and can have any demand that is below 999. So, Max order quantity = 999.
3.   3. Item B uses Large Tank in its routing and is a substitute of item A. Also, fixed order quantity = 1590.
4.   4. Define component substitution relationship between A and B. A and B will have identical BOM.
In a constrained plan with decision rules enabled, optimization logic will ensure that planned orders are generated for Item A whenever there is demand below 999. And for Item A, supply will always be equal to demand quantity. When the demand is more than 999, optimization engine will select substitute item B and will generated fixed supply of 1590 for it.
Check if this satisfies your requirement.
Regards,
Durgesh P
(Please mark this post helpful or correct, if answered)

Cardinality explosion with several XMLTable calls in one query - how to constrain ?

Hi,
when I engage several (say, four) XMLTable calls using comma (= cartesian join) in a single query, the plan shows me insane cost of 15 digits. Though execution time is reasonable because XML document is very small, I would like the plan appear with more realistic values to correctly predict query time when XML document becomes larger. How can I make CBO be aware of actual size of XML text?
Should I use XML indexing to constrain search space? What are the 'best practices' in indexing XML text for efficient parsing by XMLTable?
SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE    11.2.0.3.0      Production
TNS for Linux: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
Thanks for your answers!

Hi,
Thanks, odie_63. I used index to give CBA an idea of cardinality.
So, the original plan is (P=Peta, T=Tera, etc...):
Plan hash value: 954188411
| Id | Operation             | Name        | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT      |             | 4451T| 5099P|    14T (1)|999:59:59 |
|   1 | NESTED LOOPS         |             | 4451T| 5099P|    14T (1)|999:59:59 |
|   2 |   NESTED LOOPS        |             |   544G|   638T| 1816M (1)|999:59:59 |
|   3 |    NESTED LOOPS       |             |    66M|    79G|   222K (1)| 00:44:34 |
|   4 |     NESTED LOOPS      |             | 8168 |     9M|    32   (0)| 00:00:01 |
|   5 |      TABLE ACCESS FULL| XML_DROPBOX |     1 | 1252 |     3   (0)| 00:00:01 |
|   6 |      XPATH EVALUATION |             |       |       |            |          |
|   7 |     XPATH EVALUATION |             |       |       |            |          |
|   8 |    XPATH EVALUATION   |             |       |       |            |          |
|   9 |   XPATH EVALUATION    |             |       |       |            |          |
Note
   - Unoptimized XML construct detected (enable XMLOptimizationCheck for more information)
After creating an index, like:
CREATE INDEX XML_DROPBOX_IDX ON XML_DROPBOX (SYS_NC_ROWINFO$)
INDEXTYPE IS XDB.XMLINDEX PARAMETERS (
'PATH TABLE XML_DROPBOX_PATH_IDX (NOLOGGING ENABLE ROW MOVEMENT)
   PATH ID INDEX XML_DROPBOX_PATH_ID_IDX (NOLOGGING)'
the plan become more voluminous, but shows realistic cost:
Plan hash value: 1726871192
| Id | Operation                          | Name                    | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                   |                         |     1 | 10666 |     9   (0)| 00:00:01 |
|* 1 | FILTER                            |                         |       |       |            |          |
|* 2 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 3 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 4 | FILTER                            |                         |       |       |            |          |
|* 5 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 6 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 7 | FILTER                            |                         |       |       |            |          |
|* 8 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 9 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 10 | FILTER                            |                         |       |       |            |          |
|* 11 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 12 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 13 | FILTER                            |                         |       |       |            |          |
|* 14 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 15 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 16 | FILTER                            |                         |       |       |            |          |
|* 17 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 18 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 19 | FILTER                            |                         |       |       |            |          |
|* 20 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 21 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 22 | FILTER                            |                         |       |       |            |          |
|* 23 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 24 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 25 | FILTER                            |                         |       |       |            |          |
|* 26 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 27 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 28 | FILTER                            |                         |       |       |            |          |
|* 29 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 30 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 31 | FILTER                            |                         |       |       |            |          |
|* 32 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 33 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 34 | FILTER                            |                         |       |       |            |          |
|* 35 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 36 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 37 | FILTER                            |                         |       |       |            |          |
|* 38 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 39 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 40 | FILTER                            |                         |       |       |            |          |
|* 41 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 42 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 43 | FILTER                            |                         |       |       |            |          |
|* 44 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 45 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 46 | FILTER                            |                         |       |       |            |          |
|* 47 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 48 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 49 | FILTER                            |                         |       |       |            |          |
|* 50 |   TABLE ACCESS BY INDEX ROWID      | XML_DROPBOX_PATH_IDX    |     1 | 3524 |     2   (0)| 00:00:01 |
|* 51 |    INDEX RANGE SCAN                | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
| 52 | NESTED LOOPS                      |                         |     1 | 10666 |     9   (0)| 00:00:01 |
| 53 |   NESTED LOOPS                     |                         |     1 | 10654 |     8   (0)| 00:00:01 |
| 54 |    NESTED LOOPS                    |                         |     1 | 9132 |     7   (0)| 00:00:01 |
| 55 |     NESTED LOOPS                   |                         |     1 | 7610 |     6   (0)| 00:00:01 |
| 56 |      NESTED LOOPS                  |                         |     1 | 6088 |     5   (0)| 00:00:01 |
| 57 |       NESTED LOOPS                 |                         |     1 | 4566 |     4   (0)| 00:00:01 |
| 58 |        NESTED LOOPS                |                         |     1 | 3044 |     3   (0)| 00:00:01 |
|* 59 |         TABLE ACCESS BY INDEX ROWID| XML_DROPBOX_PATH_IDX    |     1 | 1522 |     2   (0)| 00:00:01 |
|* 60 |          INDEX RANGE SCAN          | XML_DROPBOX_PATH_ID_IDX |     1 |       |     1   (0)| 00:00:01 |
|* 61 |         TABLE ACCESS BY INDEX ROWID| XML_DROPBOX_PATH_IDX    |     1 | 1522 |     1   (0)| 00:00:01 |
|* 62 |          INDEX RANGE SCAN          | XML_DROPBOX_PATH_ID_IDX |     1 |       |     0   (0)| 00:00:01 |
|* 63 |        TABLE ACCESS BY INDEX ROWID | XML_DROPBOX_PATH_IDX    |     1 | 1522 |     1   (0)| 00:00:01 |
|* 64 |         INDEX RANGE SCAN           | XML_DROPBOX_PATH_ID_IDX |     1 |       |     0   (0)| 00:00:01 |
|* 65 |       TABLE ACCESS BY INDEX ROWID | XML_DROPBOX_PATH_IDX    |     1 | 1522 |     1   (0)| 00:00:01 |
|* 66 |        INDEX RANGE SCAN            | XML_DROPBOX_PATH_ID_IDX |     1 |       |     0   (0)| 00:00:01 |
|* 67 |      TABLE ACCESS BY INDEX ROWID   | XML_DROPBOX_PATH_IDX    |     1 | 1522 |     1   (0)| 00:00:01 |
|* 68 |       INDEX RANGE SCAN             | XML_DROPBOX_PATH_ID_IDX |     1 |       |     0   (0)| 00:00:01 |
|* 69 |     TABLE ACCESS BY INDEX ROWID    | XML_DROPBOX_PATH_IDX    |     1 | 1522 |     1   (0)| 00:00:01 |
|* 70 |      INDEX RANGE SCAN              | XML_DROPBOX_PATH_ID_IDX |     1 |       |     0   (0)| 00:00:01 |
|* 71 |    TABLE ACCESS BY INDEX ROWID     | XML_DROPBOX_PATH_IDX    |     1 | 1522 |     1   (0)| 00:00:01 |
|* 72 |     INDEX RANGE SCAN               | XML_DROPBOX_PATH_ID_IDX |     1 |       |     0   (0)| 00:00:01 |
| 73 |   TABLE ACCESS BY USER ROWID       | XML_DROPBOX             |     1 |    12 |     1   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   1 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
   2 - filter("SYS_P6"."ORDER_KEY">:B1 AND "SYS_P6"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P6"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P6"."LOCATOR")=1)
   3 - access("SYS_P6"."PATHID"=HEXTORAW('6043') AND "SYS_P6"."RID"=:B1)
   4 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
   5 - filter("SYS_P9"."ORDER_KEY">:B1 AND "SYS_P9"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P9"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P9"."LOCATOR")=1)
   6 - access("SYS_P9"."PATHID"=HEXTORAW('66A6') AND "SYS_P9"."RID"=:B1)
   7 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
   8 - filter("SYS_P12"."ORDER_KEY">:B1 AND "SYS_P12"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P12"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P12"."LOCATOR")=1)
   9 - access("SYS_P12"."PATHID"=HEXTORAW('4203') AND "SYS_P12"."RID"=:B1)
10 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
11 - filter("SYS_P15"."ORDER_KEY">:B1 AND "SYS_P15"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P15"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P15"."LOCATOR")=1)
12 - access("SYS_P15"."PATHID"=HEXTORAW('66BA') AND "SYS_P15"."RID"=:B1)
13 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
14 - filter("SYS_P18"."ORDER_KEY">:B1 AND "SYS_P18"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P18"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P18"."LOCATOR")=1)
15 - access("SYS_P18"."PATHID"=HEXTORAW('550B') AND "SYS_P18"."RID"=:B1)
16 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
17 - filter("SYS_P21"."ORDER_KEY">:B1 AND "SYS_P21"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P21"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P21"."LOCATOR")=1)
18 - access("SYS_P21"."PATHID"=HEXTORAW('652E') AND "SYS_P21"."RID"=:B1)
19 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
20 - filter("SYS_P24"."ORDER_KEY">:B1 AND "SYS_P24"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P24"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P24"."LOCATOR")=1)
21 - access("SYS_P24"."PATHID"=HEXTORAW('44EC') AND "SYS_P24"."RID"=:B1)
22 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
23 - filter("SYS_P31"."ORDER_KEY">:B1 AND "SYS_P31"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P31"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P31"."LOCATOR")=1)
24 - access("SYS_P31"."PATHID"=HEXTORAW('2C38') AND "SYS_P31"."RID"=:B1)
25 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
26 - filter("SYS_P34"."ORDER_KEY">:B1 AND "SYS_P34"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P34"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P34"."LOCATOR")=1)
27 - access("SYS_P34"."PATHID"=HEXTORAW('3026') AND "SYS_P34"."RID"=:B1)
28 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
29 - filter("SYS_P37"."ORDER_KEY">:B1 AND "SYS_P37"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P37"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+2 AND
              SYS_XMLI_LOC_ISNODE("SYS_P37"."LOCATOR")=1)
30 - access("SYS_P37"."PATHID"=HEXTORAW('4F1A') AND "SYS_P37"."RID"=:B1)
31 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
32 - filter("SYS_P40"."ORDER_KEY">:B1 AND "SYS_P40"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P40"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+2 AND
              SYS_XMLI_LOC_ISNODE("SYS_P40"."LOCATOR")=1)
33 - access("SYS_P40"."PATHID"=HEXTORAW('7E65') AND "SYS_P40"."RID"=:B1)
34 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
35 - filter("SYS_P43"."ORDER_KEY">:B1 AND "SYS_P43"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P43"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P43"."LOCATOR")=1)
36 - access("SYS_P43"."PATHID"=HEXTORAW('7497') AND "SYS_P43"."RID"=:B1)
37 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
38 - filter("SYS_P46"."ORDER_KEY">:B1 AND "SYS_P46"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P46"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P46"."LOCATOR")=1)
39 - access("SYS_P46"."PATHID"=HEXTORAW('2D8D') AND "SYS_P46"."RID"=:B1)
40 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
41 - filter("SYS_P49"."ORDER_KEY">:B1 AND "SYS_P49"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P49"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P49"."LOCATOR")=1)
42 - access("SYS_P49"."PATHID"=HEXTORAW('4486') AND "SYS_P49"."RID"=:B1)
43 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
44 - filter("SYS_P66"."ORDER_KEY">:B1 AND "SYS_P66"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P66"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P66"."LOCATOR")=1)
45 - access("SYS_P66"."PATHID"=HEXTORAW('5005') AND "SYS_P66"."RID"=:B1)
46 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
47 - filter("SYS_P69"."ORDER_KEY">:B1 AND "SYS_P69"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P69"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P69"."LOCATOR")=1)
48 - access("SYS_P69"."PATHID"=HEXTORAW('3935') AND "SYS_P69"."RID"=:B1)
49 - filter(:B1<SYS_ORDERKEY_MAXCHILD(:B2))
50 - filter("SYS_P59"."ORDER_KEY">:B1 AND "SYS_P59"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD(:B2) AND
              SYS_ORDERKEY_DEPTH("SYS_P59"."ORDER_KEY")=SYS_ORDERKEY_DEPTH(:B3)+1 AND
              SYS_XMLI_LOC_ISNODE("SYS_P59"."LOCATOR")=1)
51 - access("SYS_P59"."PATHID"=HEXTORAW('37CE') AND "SYS_P59"."RID"=:B1)
59 - filter(SYS_XMLI_LOC_ISNODE("SYS_P49"."LOCATOR")=1)
60 - access("SYS_P49"."PATHID"=HEXTORAW('4486') )
61 - filter(SYS_XMLI_LOC_ISNODE("SYS_P62"."LOCATOR")=1 AND
              "SYS_P49"."ORDER_KEY"<"SYS_P62"."ORDER_KEY" AND "SYS_P62"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD("SYS_P49".
              "ORDER_KEY") AND SYS_ORDERKEY_DEPTH("SYS_P49"."ORDER_KEY")+1=SYS_ORDERKEY_DEPTH("SYS_P62"."ORDER_KEY")
62 - access("SYS_P62"."PATHID"=HEXTORAW('780B') AND "SYS_P62"."RID"="SYS_P49"."RID")
63 - filter(SYS_XMLI_LOC_ISNODE("SYS_P27"."LOCATOR")=1 AND
              "SYS_P27"."ORDER_KEY"<"SYS_P49"."ORDER_KEY" AND "SYS_P49"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD("SYS_P27".
              "ORDER_KEY") AND SYS_ORDERKEY_DEPTH("SYS_P27"."ORDER_KEY")+1=SYS_ORDERKEY_DEPTH("SYS_P49"."ORDER_KEY")
64 - access("SYS_P27"."PATHID"=HEXTORAW('49C4') AND "SYS_P49"."RID"="SYS_P27"."RID")
65 - filter(SYS_XMLI_LOC_ISNODE("SYS_P46"."LOCATOR")=1 AND
              "SYS_P27"."ORDER_KEY"<"SYS_P46"."ORDER_KEY" AND "SYS_P46"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD("SYS_P27".
              "ORDER_KEY") AND SYS_ORDERKEY_DEPTH("SYS_P27"."ORDER_KEY")+1=SYS_ORDERKEY_DEPTH("SYS_P46"."ORDER_KEY")
66 - access("SYS_P46"."PATHID"=HEXTORAW('2D8D') AND "SYS_P46"."RID"="SYS_P27"."RID")
67 - filter(SYS_XMLI_LOC_ISNODE("SYS_P52"."LOCATOR")=1 AND
              "SYS_P46"."ORDER_KEY"<"SYS_P52"."ORDER_KEY" AND "SYS_P52"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD("SYS_P46".
              "ORDER_KEY") AND SYS_ORDERKEY_DEPTH("SYS_P46"."ORDER_KEY")+1=SYS_ORDERKEY_DEPTH("SYS_P52"."ORDER_KEY")
68 - access("SYS_P52"."PATHID"=HEXTORAW('6AFA') AND "SYS_P52"."RID"="SYS_P46"."RID")
69 - filter(SYS_XMLI_LOC_ISNODE("SYS_P24"."LOCATOR")=1 AND
              "SYS_P24"."ORDER_KEY"<"SYS_P27"."ORDER_KEY" AND "SYS_P27"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD("SYS_P24".
              "ORDER_KEY") AND SYS_ORDERKEY_DEPTH("SYS_P24"."ORDER_KEY")+1=SYS_ORDERKEY_DEPTH("SYS_P27"."ORDER_KEY")
70 - access("SYS_P24"."PATHID"=HEXTORAW('44EC') AND "SYS_P27"."RID"="SYS_P24"."RID")
71 - filter(SYS_XMLI_LOC_ISNODE("SYS_P4"."LOCATOR")=1 AND
              "SYS_P4"."ORDER_KEY"<"SYS_P24"."ORDER_KEY" AND "SYS_P24"."ORDER_KEY"<SYS_ORDERKEY_MAXCHILD("SYS_P4"."O
              RDER_KEY") AND SYS_ORDERKEY_DEPTH("SYS_P4"."ORDER_KEY")+1=SYS_ORDERKEY_DEPTH("SYS_P24"."ORDER_KEY"))
72 - access("SYS_P4"."PATHID"=HEXTORAW('5B3D') AND "SYS_P24"."RID"="SYS_P4"."RID")
Note
   - dynamic sampling used for this statement (level=2)

Constraining Values in Dashboard Prompts

Hi,
I have a question about constraining values in dashboard prompts. Do all fields need to come from the same table as I am finding constraining values is not working where I am selecting some values from different tables:
For example
Start Date - Fact Table
End Date - Fact Table
Salesperson - Org Dim
Market - Org Dim
Introducer - Org Dim
Customer - Org Dim
I am trying to constrain values beginning from Salesperson and so on but this does not work.
Is this the expected behaviour? should all values be retrieved from the same table in order for this to work?
Thanks

Hi,
Below is the filter I am applying in the report:
"Agreement Fact"."Prop Creation Date" >= Evaluate('to_date(%1,%2)','@{startdate}','YYYY-MM-DD HH24:MI:SS')
and "Agreement Fact"."Prop Creation Date2" <= Evaluate('to_date(%1,%2)','@{enddate}','YYYY-MM-DD HH24:MI:SS')
and Organisation.Market = '@{market}'
and Organisation."Sales Person Name" = '@{salesperson}'
and Organisation."Introducer Name" = '@{introducer}'
and Organisation."Customer Name" = '@{customer}'
I have selected constrain in the report from salesperson onwards but instead when I run the dashboard report the values beginning with salesperson do not show.
I definitely know that data exists for the date parameters(startdate and enddate) and market parameter. I have run a report in answers using the same parameters as in dashboard and do see data.
Can anyone help?
Thanks
Edited by: sliderrules on 14-Mar-2011 05:57

Date parameters using MDX query

Hello experts,
Not sure if this question falls under SSAS or SSRS but I'm writing it here for now and hopefully get the answer.
I'm using SSAS cube to develop a report using SSRS and this is the first time I'm doing it. I want to filter records based on date range and did some research online. My report contains two datasets:
1. dsMain dataset -> it contains all the field which I want to use in the report and added a parameter thru query designed with following settings:
Dimension : Dates
Hierachary : Date
Operator : Range (Inclusive)
Parameters : checked
it created two parameters called FromDatesDate and toDatesDate
2. I created another dataset called dsDate and wrote a custom query (found at following link) and changed FromDatesDate and ToDatesDate using this date dataset
https://jsimonbi.wordpress.com/2011/03/22/using-a-date-parameter-in-ssrs-with-mdx/
Query for dsDate
WITH
MEMBER DateValue
AS
[Dates].[Date].CurrentMember.UniqueName
MEMBER DateLabel
AS
[Dates].[Date].CurrentMember.Name
SELECT
[Measures].[DateValue],
[Measures].[DateLabel]
} ON 0,
[Dates].[Date].[Date]
} ON 1
FROM [myCube]
Here is the value returned by dsDate dataset (above query)
DateValue DateLabel
06/04/1980 [Dates].[Date].&[29375]
06/04/1980
06/05/1980 [Dates].[Date].&[29376]
06/05/1980
06/06/1980 [Dates].[Date].&[29377]
06/06/1980
06/07/1980 [Dates].[Date].&[29378]
06/07/1980
06/08/1980 [Dates].[Date].&[29379]
06/08/1980
06/09/1980 [Dates].[Date].&[29380]
06/09/1980
06/10/1980 [Dates].[Date].&[29381]
06/10/1980
06/11/1980 [Dates].[Date].&[29382]
06/11/1980
06/12/1980 [Dates].[Date].&[29383]
06/12/1980
06/13/1980 [Dates].[Date].&[29384]
06/13/1980
Here is what I changed in FromDatesDate and ToDatesDate parmeter:
Under Available Values tab:
Dataset : dsDate
Value Field : DateValue
Label Field : DateLabel
Here are my questions:
1. I want to use date/time parameter so that user doesn't have to scroll thru whole date dimension.
2. I changed the FromDatesDate and ToDatesDate to date/time parameter, removed the values from Available values tab and made the following changes on Parmaeters expression under dsMain dataset
=”[Dates].[Date].&[” + Format(CDate(Parameters!FromDatesDate.Value),”MM/dd/yyyy”)
+ “T00:00:00]”
=”[Dates].[Date].&[” + Format(CDate(Parameters!ToDatesDate.Value),”MM/dd/yyyy”)
+ “T00:00:00]”
Now when I run the report I get following error:
Query (1, 55) The restrictions imposed by the CONSTRAINED flag in the STRTOMEMBER function are violated.
I think the reason is by changing parameter to date/time, now I cannot get "DateValue" which is required for the query.
1. What is the best way to work with date parameters?
Hope it is all clear and look forward to hear from experts.
Thanks,
P
mark it as answer if it answered your question :)

Hi Parry2k,
In Analysis Services, a member can be referenced by either its member name or by its member key. The member key is used by the dimension to specifically identify a given member. The ampersand (&) character is used in MDX to differentiate
a member key from a member name. In this scenario, the datetime is member name, not the member key. So you should not add "&".
Reference:
Member Names and Keys
Simon Hou
TechNet Community Support

Pass Multiple Parameters to SQL query in Drop down or Select Boxes

Post Author: JasonW
CA Forum: Data Connectivity and SQL
Hello all- I am using CR XI and SQL server 2000.I have written a SQL statement and used that statement as a 'command' in the Database Expert, to pull data into a report. There are two issues I have that I need some help/advice on.-. The report needs 4 parameters. A, B, C, D.-. I can create Parameters in the Database Expert that will prompt me for the data when I refresh the report. However,-. I need to be able to select those parameters in drop down boxes based on data in the SQL database. The problem is that the parameter cannot pull the data without the criteria - so a drop down box seems impossible. OR is it? That is part of my question. The other part is - Even if it is possible, can Crystal do this somehow? NOTE: The query is selecting the data rather than Crystal - so Creating a Parameter field IN the report is futile. -. The other half of this problem is that users would like the ability to select multiple values from Field A and from Field B.

Post Author: JasonW
CA Forum: Data Connectivity and SQL
I ended up using a stored procedure. This queries the proper data, and allows me to use Dynamic Parameters to make multiple selections on the data. (I query out a large portion of the data in the stored procedure, then pair it down using Dynamic Parameters in Crystal.) Here is the new problem this has created:My Dynamic Parameters are not pulling all the values from the query. Ex. One field in the query is a "directory" listing. It has 227 unique values in it. (It has multiple values, it is not constrained.) When I create a Dynamic Parameter off of this field, I only get 18 of the 227 as available selections in the drop down box. However, I can type in any of the 227 values into the field manually, I pull the proper data. So the data is there, its just not showing up in the drop down box. Anyone have any ideas on this?

How to pass more number of parameters in procedure

How can we send 1000 parametrs in a procedure?
is there any other method to pass parameters without defning 1000 parametrs
Any example really helpful

I know it's a hint, but have you ever known it to be ignored? Can you provide a working example showing it being ignored?Well it is not hard to demonstrate it being ignored, but these restrictions, while not obvious, are relatively well documented.
What does not appear to be documented is the behaviour when calling from 3GLs (or does this qualify as an external procedure call?) where I believe the hint is also ignored.
http://download-uk.oracle.com/docs/cd/B19306_01/appdev.102/b14261/tuning.htm#sthref2261
"The use of NOCOPY increases the likelihood of parameter aliasing. For more information, see "Understanding Subprogram Parameter Aliasing".
Remember, NOCOPY is a hint, not a directive. In the following cases, the PL/SQL compiler ignores the NOCOPY hint and uses the by-value parameter-passing method; no error is generated:
1. The actual parameter is an element of an associative array. This restriction does not apply if the parameter is an entire associative array.
2. The actual parameter is constrained, such as by scale or NOT NULL. This restriction does not apply to size-constrained character strings. This restriction does not extend to constrained elements or attributes of composite types.
3. The actual and formal parameters are records, one or both records were declared using %ROWTYPE or %TYPE, and constraints on corresponding fields in the records differ.
4. The actual and formal parameters are records, the actual parameter was declared (implicitly) as the index of a cursor FOR loop, and constraints on corresponding fields in the records differ.
5. Passing the actual parameter requires an implicit datatype conversion.
6. The subprogram is called through a database link or as an external procedure."
For example, consider rule #2 above and compare output of first block (with unconstrained NUMBER datatype) with second (with constrained NUMBER datatype).
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
SQL> SET SERVEROUTPUT ON;
SQL> <<anonymous_block>>
2 DECLARE
3     variable_name NUMBER := 0;
4
5     PROCEDURE procedure_name (
6        parameter_name   IN OUT NOCOPY   NUMBER)
7     IS
8     BEGIN
9        dbms_output.put_line ('#2 variable_name => ' || variable_name);
10        parameter_name := parameter_name + 1;
11        dbms_output.put_line ('#3 variable_name => ' || variable_name);
12     END procedure_name;
13 BEGIN
14     dbms_output.put_line ('#1 variable_name => ' || variable_name);
15     procedure_name (variable_name);
16     dbms_output.put_line ('#4 variable_name => ' || variable_name);
17 END anonymous_block;
18 /
#1 variable_name => 0
#2 variable_name => 0
#3 variable_name => 1
#4 variable_name => 1
PL/SQL procedure successfully completed.
SQL> <<anonymous_block>>
2 DECLARE
3     variable_name NUMBER (10) := 0;
4
5     PROCEDURE procedure_name (
6        parameter_name IN OUT NOCOPY NUMBER)
7     IS
8     BEGIN
9        dbms_output.put_line ('#2 variable_name => ' || variable_name);
10        parameter_name := parameter_name + 1;
11        dbms_output.put_line ('#3 variable_name => ' || variable_name);
12     END procedure_name;
13 BEGIN
14     dbms_output.put_line ('#1 variable_name => ' || variable_name);
15     procedure_name (variable_name);
16     dbms_output.put_line ('#4 variable_name => ' || variable_name);
17 END anonymous_block;
18 /
#1 variable_name => 0
#2 variable_name => 0
#3 variable_name => 0
#4 variable_name => 1
PL/SQL procedure successfully completed.
SQL>

Possible to use parameters in MDX Studio?

Is it possible to use parameters in MDX Studio? I've tried using SSRS2008 for query design but...
SSRS2008 query designer complains that parameters do not exist when they quite obviously do ( in the report)
LaCie drives. Failing when you need them most."La" meaning "Terrible", "Cie" meaning "customer service"

You can declare parameters in XMLA format after the MDX query - see examples in this post:
Bug v2.9.1: Parametric queries parsing and debugging errors
WITH MEMBER [Measures].[Profit] AS '[Measures].[Sales Amount]-[Measures].[Standard Product Cost]' SELECT NON EMPTY { [Measures].[Internet Sales Amount], [Measures].[Internet Total Product Cost], [Measures].[Internet Order Quantity] } ON COLUMNS, NON
EMPTY { ([Sales Reason].[Sales Reason].[Sales Reason].ALLMEMBERS * [Sales Territory].[Sales Territory Group].[Sales Territory Group].ALLMEMBERS ) } DIMENSION PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME, [Sales Reason].[Sales Reason].[Sales Reason].KEY, [Sales
Territory].[Sales Territory Group].[Sales Territory Group].KEY ON ROWS FROM ( SELECT ( STRTOSET(@ProductCategory, CONSTRAINED) ) ON COLUMNS FROM [Adventure Works]) WHERE ( IIF( STRTOSET(@ProductCategory, CONSTRAINED).Count = 1, STRTOSET(@ProductCategory, CONSTRAINED),
[Product].[Category].currentmember ) ) CELL PROPERTIES VALUE, BACK_COLOR, FORE_COLOR, FORMATTED_VALUE, FORMAT_STRING, FONT_NAME, FONT_SIZE, FONT_FLAGS
<Parameters xmlns:xsi="www.w3.org/2001/XMLSchema-instance" xmlns:xsd="www.w3.org/2001/XMLSchema"
xmlns="urn:schemas-microsoft-com:xml-analysis">
<Parameter>
<Name>ProductCategory</Name>
<Value xsi:type="xsd:string">{ [Product].[Category].&[1],[Product].[Category].&[2] }</Value>
</Parameter>
</Parameters>
<PropertyList xmlns="urn:schemas-microsoft-com:xml-analysis">
<Catalog>Adventure Works DW</Catalog>
<LocaleIdentifier>1033</LocaleIdentifier>
<Format>Tabular</Format>
<Content>SchemaData</Content>
<Timeout>0</Timeout>
<ReturnCellProperties>true</ReturnCellProperties>
<DbpropMsmdFlattened2>true</DbpropMsmdFlattened2>
</PropertyList>
- Deepak

Is It Possible To define a size of the Procedure Parametere?

In Oracle Is It Possible To define a size of the Procedure Parametere?
If i have the procedure like
Test_sp(no int,name varchar2)
Is it possible to define a size
Test_sp(no int(5),name varchar2(255))
Thanks
Rangan S

As Anthony said - no, not in the parameter signature of a procedure or a function. Which could have unexpected run-time errors as one could wrongly assume that using a "derived" type will allow this.
The following example illustrates:
SQL> create table datatype(
2 varchar2_5 varchar2(5),
3 number1 number(1)
4 );
Table created.
SQL>
SQL>
SQL> create or replace procedure fooProc( s datatype.varchar2_5%TYPE, n datatype.number1%TYPE ) is
2 s1 datatype.varchar2_5%TYPE;
3 n1 datatype.number1%TYPE;
4 begin
5 begin
6 DBMS_OUTPUT.put_line( 'len='||length(s)||' value='||s );
7 DBMS_OUTPUT.put_line( 'value='||to_char(n) );
8 exception when OTHERS then
9 DBMS_OUTPUT.put_line( 'parameter display failed with error '||SQLERRM(SQLCODE) );
10 end;
11
12 begin
13 s1 := s;
14 DBMS_OUTPUT.put_line( 'string parameter assignment succeeded' );
15 exception when OTHERS then
16 DBMS_OUTPUT.put_line( 'string assignment failed with error '||SQLERRM(SQLCODE) );
17 end;
18
19 begin
20 n1 := n;
21 DBMS_OUTPUT.put_line( 'number parameter assignment succeeded' );
22 exception when OTHERS then
23 DBMS_OUTPUT.put_line( 'number assighment failed with error '||SQLERRM(SQLCODE) );
24 end;
25 end;
26 /
Procedure created.
SQL>
SQL> exec fooProc( 'test1', 1 );
len=5 value=test1
value=1
string parameter assignment succeeded
number parameter assignment succeeded
PL/SQL procedure successfully completed.
SQL>
SQL> exec fooProc( 'this should fail', 1 );
len=16 value=this should fail
value=1
string assignment failed with error ORA-06502: PL/SQL: numeric or value error: character string buffer too small
number parameter assignment succeeded
PL/SQL procedure successfully completed.
SQL>
SQL> exec fooProc( 'test', 1234 );
len=4 value=test
value=1234
string parameter assignment succeeded
number parameter assignment succeeded
PL/SQL procedure successfully completed.
SQL>
Note that only the string assignment fails. The string parameter works fine. And there is no impact at all on the number side, despite seemingly constraining it to a single digit.

Curve Fit of ODE, should I use Lev-Mar or Constrained Nonlinear Optimization?

I wanna do a curve fitting of differential equations, following is the equations:
dx/dt = u*x-a*x
ds/dt = b*u*x+c*x
dp/dt = d*u*x+e*x+f*p
and u = um*s/(km+s+s^2/ki)
I've tried "nonlinear curve fit( Lev-Mar)", but I met difficulties when writing the f(x,a) of Lev-Mar.
Then I tried "Constrained Nonlinear Optimization", I found that the example "Estimate Nonlinear Spring Constant.vi"
in the "labview\examples\math\curvefit.llb" was similar to the fitting I tried to do, but there was only one parameter
need to estimate in this example,but what I need is to estimate 3 parameters.
However,I modified the example to my equations, it failed again.
How can I achieve this? is it possible to do this fit only using Labview VIs or need Matlab Script Node?
Any help will be appreciated.

I forgot to mention that in the equations above, a,b,c,d,e,f is constant,
and the data of x,s,p corresponding with the data of time is already known,
and which parameters I wanna identify is um,km,and ki
帖子被myafu在12-22-2006 01:33 AM时编辑过了

Constrained nonlinear curve fit can properly handle the function like ln(1+b(x-xc)/a) ?

Hi all,
I met some problems about using constrained nonlinear curve fitting vi. It seems to me that this vi can't properly deal with the function like ln(1+b(x-xc)/a), a,b, and xc are the parameters, and b is in the range of 0 and -1. The reason I said that is as I used the other nonlinear fitting function in the other software, like Originlab, the fitting function can work properly.
The error message from LV occurs as 1+b(x-xc)/a is less than zero.
However, due to a,b are both adjustable parameters, how could this situation happen ?
Now I attach the vi files. The attachment includes main vi, mathmatical formula, and an input XY txt file.
I appreciate any help or suggestion from you!!
Here is the error message
Joy
Solved!
Go to Solution.
Attachments:
LN-fitting.vi ‏21 KB
LN-fittingmodel.vi ‏18 KB
Book2.txt ‏1 KB

Thanks for reply. whitenoiz
Actually I have more than 100 XY data set to test my vi. Some of the data set can be fit flawlessly. And the best fit parameters obtained from my vi are exactly the same as those from other analytical software, like OriginLab. In this case, I know my vi is valid. And in this scenario, I also found 1+b(x-xc)/a is always larger than zero with the best fit parameters (a and b). However, for certain XY data set, the error message will pop up if I use LV built-in vi, but I still can obtain the best fit parameters with OriginLab. And then I realized that error message always pops up as 1+b(x-xc)/a is less than zero, which it means to me that as LV built-in vi handles this type mathematical function, this built-in vi will encounter some difficulties.
I will step through my code, and also focus on the Matrix Left DivisionMV.vi, try yo find where the problem is.
Best regards,
Joy

Constrain on Parameters

Similar Messages

Maybe you are looking for