Skip to Main Content
Forums

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Install script

PGRWOct 9 2007 — edited Oct 9 2007
I'm packaging up an app for a client. The application installs and seeds the tables and data necessary for the app but the client uses a different set of tablespaces etc. I've created a couple of application substitution items and marked these in the install as to be prompted for which it does.
However, the install process fails to replace the item with the substituted value if I use either the &NAME. or #NAME# notation.
Does anyone know if this works and if so what syntax is needed for substitution please?

Phil

Comments

flavioc
Hi,
did you try with the v('NAME') notation?

I've seen Scott Spadafore mentioning it a few times.

Bye,
Flavio
-------------------------------------------------------------------------
http://oraclequirks.blogspot.com/search/label/Apex
PGRW
Flavio

Thanks - I didn't try this because this is a script and it would make no sense to do that - my scripts also include packaged code itself that uses this notation and so it would break that.

I suspect that it may be missing or may need a different approach? For example, in SQL*Plus I'd use &Name but obviously this won't translate to the app script example. It may be something that APEX does not do which would be a shame as it means that substitution in install scrips would not be possible. Obviously, this is one place we used them for years before APEX and so I am hoping there is a way.

Phil
flavioc
Phil,
wouldn't it be easier to relocate tables and indexes at a later time?

ALTER TABLE xyz MOVE TABLESPACE tbs;
ALTER INDEX abc REBUILD TABLESPACE tbs;

I mean, i don't see why one should become crazy making unnecessarily complex installation scripts when in the end there is an alternate and relatively easy solution.

I had a look at the substitution strings prompt, but i suppose this works only for changing the values of global substitutions that will be used by the application at run time, not during the installation process.

Bye,
Flavio

-------------------------------------------------------------------------
http://oraclequirks.blogspot.com/search/label/Apex
PGRW
Yes, that is a good suggestion. I was just after a way of reducing the complexity for the end client - never mind if it makes life harder for the developer.
SQL install scrips for objects often use substitution variables for tables and index tablspaces so I had hoped it would be simple to do the same for APEX. Looks like it is not.

Phil
1 - 4
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Nov 6 2007
Added on Oct 9 2007
#apex-discussions
4 comments
526 views