Oracle Express Sales Analyzer version control

Oracle Express Sales Analyzer version control

Post by Tom Ricciard » Fri, 18 Jul 1997 04:00:00



Has anyone attempted to upgrade Oracle Express Sales Analyzer
applications in the last year or so?  We are now working with version
1.6 of Sales Analyzer; I found out that specific dimension objects in
the Sales Analyzer database catalog have changed after version 1.3.2.  I
haven't seen documentation of the changes from Oracle/IRI.  Any hints
for migrating custom 1.3.2 applications to 1.6?

--
-Tom

******************************************************************
Thomas N. Ricciardi

 
 
 

Oracle Express Sales Analyzer version control

Post by Dan Vlami » Wed, 23 Jul 1997 04:00:00


<< I found out that specific dimension objects in
the Sales Analyzer database catalog have changed after version 1.3.2.  I
haven't seen documentation of the changes from Oracle/IRI.  Any hints
for migrating custom 1.3.2 applications to 1.6? >>

I am aware that the objects that store dimension attribute information
changed.  Is that the change you refer to?  This change appears to be
part of an effort to make attribute information compatible with Oracle
Express Objects.  Instead of having one relation, DIMATTREL.x, they have
split each attribute into its own relation (back to the way this was
done in the DOS DataServer product).

Perhaps the following message from Oracle Support will help:

-- snip --

In 1.5 DIMATTREL.X is replaced by a series of structures, 1 for each
attribute
...these structures are names DMATRL.<prefix>.X where <prefix> is the
value of the PREFIX.XA variable for the giveen attribute.....You can
also
find the name of the DMATRL structure by going through DM.DIMATTREL and
then
to DM.DMATRL.X....

for example:

Quote:>rpr dm.dimattrel

               DM.DIMATTR
DMENTRY            EL
-------------- ----------
D1             DM.DMATRL.
               T
D2             DM.DMATRL.
               G
D3             DM.DMATRL.
               P
D4             NA
D5             NA
->rpr dm.dmatrl.g

               DM.DMATRL.
GATTR              G
-------------- ----------
SEGMENT        DMATRL.SEG
               .G
DISTRICT       DMATRL.DIS
               .G
REGION         DMATRL.REG
               .G

DMATRL.SEG.G would be identical to:
DIMATTREL.G(GATTR 'SEGMENT')

-- end snip --

 Dan Vlamis
 Vlamis Software Solutions, Inc.
 Specializing in Express OLAP applications

 Using Virtual Access
 http://www.ashmount.com/va

 
 
 

1. Overhead using Oracle Express, Sales Analyzer tools

It seems that a lot of manpower is required to maintain an Oracle Objects
application unlike Microstrategy or Information Advantage type ROLAP
tools.  The cubes themselves seem to be very rigid to even minor changes,
unlike a relational tool and relational server which is slower but more
forgiving to change.  Its not an adhoc query tool by any means and unless
you know exactly what your users want in terms of information, you can be
in big trouble if you rebuild and reaggregate these cubes retroactively.
If your organization seems to change quite frequently, this tool seems to
have a lot of overhead to retro populate cubes....

Any thoughts.are welcome....

2. Q: Concurrency problems with multi user PARADOX apps ??

3. Oracle Express and Sales Analyzer

4. Calculations slower in FMP 5.0

5. Express Sales Analyzer Blank Measures

6. newbie: autocompletes in DB B based on data in DB A

7. OLAP, Oracle, SQL, Financial Analyzer, Sales Analyzer, Contract

8. Star Transformation

9. Cleveland, OH - Oracle Developer w/Oracle Express, Oracle Sales Analyzer and/or Oracle Financial Analyzer.

10. Oracle Express functions in Oracle Financial Analyzer

11. Known Issue between Financial Analyzer and Express Analyzer

12. Oracle Express Analyzer 2.10 on German Windows 98?

13. Oracle Express Analyzer/Objects