| Hi Regina,
I hadn't heard this. It's all described in chapter 9 of the Oracle Rdb7
Distributed Technology Product Family User's Guide. Page 9-7 has an example
of using a config file with labels but it is not an oracle config file.
I'm going to try this later and see if I can get it to work, or recreate
the problem. Will let you know my results.
Diane
<<< Note 1143.0 by chsr38.ch.oracle.com::ROHR "The Packers did it!" >>>
-< Labels in config file with LORA_CONFIG_FILE >-
I guess you can't use the labels in the config file if you choose to
work with LORA_CONFIG_FILE?
If yes, help where is this described?
/thanks,
Regina
|
| Hi Diane,
what I wanted to know is: I know you can use the labels in the config
file with the /CONFIG qualifier on the attach string. I just wondered
if there is a possibility to use the labels when you don't use the
/CONFIG qualifier but the LORA_CONFIG_FILE logical.
CHeers,
Regina
|
| Hi Regina,
> what I wanted to know is: I know you can use the labels in the config
> file with the /CONFIG qualifier on the attach string. I just wondered
> if there is a possibility to use the labels when you don't use the
> /CONFIG qualifier but the LORA_CONFIG_FILE logical.
I tested here and I got labels to work using a logical.
I believe what you are asking for is documented on page 9-5 of the Product
Family User's Guide:
$ DEFINE LSYB_CONFIG_FILE "(USER1:[SHARED]CONFIG1.DAT, GROUP1, USER)"
(The quotes are not in the book but they are needed or the above logical
cannot be defined.)
I did the following and it all worked:
Created a config file with 2 labels -
attach_user1:
/user=scott
/pass=tiger
#
attach_user2:
/user=bither
/pass=bither
$ define lora_config_ora "(ora_config.dat, attach_user1)"
Successfully attached to tables that only scott/tiger has access to.
$ define lora_config_ora "(ora_config.dat, attach_user2)"
Successfully attached to tables that only bither/bither has access to.
I also tried:
$ define lora_config_ora "(ora_config.dat,attach_user1)"
$ define lora_config_ora "(ora_config.dat,attach_user1)"
^no space
and these both worked too. The reason I tried these second logical
definitions is because:
During my testing I found another doc error in addition to the above
missing quotes which is much more serious. Whenever I try
to use what is documented in the attach string, it fails with a
syntax error:
SQL> attach 'f /type=oracle/config=(ora_config.dat, attach_user1)';
f /type=oracle/config=(ora_config.dat, attach_user1)
^
%SQL-F-DBSPECSYNERR, Syntax error in database specification
The ONLY way I could get labels to work when used in the attach string
was to omit the space. This is not true when using a logical name that
points to the config file. In that case both space and no space works.
I'm writing a STARS article on this since I tried a lot of things before
getting this to work, i.e.:
SQL> attach 'f /type=oracle/config=(ora_config.dat, attach_user1)';
SQL> attach 'f /type=oracle/config=(ora_config.dat attach_user1)';
SQL> attach 'f /type=oracle/config=(ora_config.dat/attach_user1)';
SQL> attach 'f /type=oracle/config=ora_config.dat, attach_user1';
SQL> attach 'f /type=oracle/config=(ora_config.dat,attach_user1)'; <--WORKS!
Thanks, Diane
|