CREATE DBSPACE SQL Admin API Command - need help
Posted in 2009
Topics: Storage & Space Management, Server Administration, Platform-Specific Issues, Versions, Editions & End-of-Life
Hi experts,
[ IDS 11.50.UC4 on SuSE Linux ]
I am tesing IDS11.50.UC4 coming from IDS 10.00.
The CREATE DBSPACE SQL Admin API Command seems not
to have a way to specify a symbolic link for the
parameter value of pathname.
Do I miss something here?
All I want to do using the API is:
touch $SPACE/idschunks/chk001_01
chmod 660 $SPACE/idschunks/chk001_01
ln -s $SPACE/idschunks/chk001_01 $IDSSYMLINKS/L_chk001_01
onspaces -c -d dbspc001 -p $IDSSYMLINKS/L_chk001_01 -o 0 -s $SIZE
Is there a way to do the same using the new API?
dic_k
--
Richard Kofler
SOLID STATE EDV
Dienstleistungen GmbH
Vienna/Austria/Europe
On May 23, 2:26 pm, Richard Kofler <richard.kof...@chello.at> wrote:
> [ IDS 11.50.UC4 on SuSE Linux ]
>
> I am testing IDS11.50.UC4 coming from IDS 10.00.
>
> The CREATE DBSPACE SQL Admin API Command seems not
> to have a way to specify a symbolic link for the
> parameter value of pathname.
>
> Do I miss something here?
>
> All I want to do using the API is:
> touch $SPACE/idschunks/chk001_01
> chmod 660 $SPACE/idschunks/chk001_01
> ln -s $SPACE/idschunks/chk001_01 $IDSSYMLINKS/L_chk001_01
> onspaces -c -d dbspc001 -p $IDSSYMLINKS/L_chk001_01 -o 0 -s $SIZE>
> Is there a way to do the same using the new API?
I think the API assumes that the space is already 'allocated' or
'available' -- that is, the file name specified already exists. When
it does, it may be a symlink; but the name must already exist.
None of the utilities that manage dbspaces actually create the file
that is used.
It is not an unreasonable request to make - but I think it is a
feature request (and one that will need some care in implementation).
-=JL=-
Jonathan Leffler schrieb:
> On May 23, 2:26 pm, Richard Kofler <richard.kof...@chello.at> wrote:
>
>> [ IDS 11.50.UC4 on SuSE Linux ]
>>
>> I am testing IDS11.50.UC4 coming from IDS 10.00.
>>
>> The CREATE DBSPACE SQL Admin API Command seems not
>> to have a way to specify a symbolic link for the
>> parameter value of pathname.
>>
>> Do I miss something here?
>>
>> All I want to do using the API is:
>> touch $SPACE/idschunks/chk001_01
>> chmod 660 $SPACE/idschunks/chk001_01
>> ln -s $SPACE/idschunks/chk001_01 $IDSSYMLINKS/L_chk001_01
>> onspaces -c -d dbspc001 -p $IDSSYMLINKS/L_chk001_01 -o 0 -s $SIZE>>
>> Is there a way to do the same using the new API?
>
> I think the API assumes that the space is already 'allocated' or
> 'available' -- that is, the file name specified already exists. When
> it does, it may be a symlink; but the name must already exist.
>
> None of the utilities that manage dbspaces actually create the file
> that is used.
>
> It is not an unreasonable request to make - but I think it is a
> feature request (and one that will need some care in implementation).
>
> -=JL=-
Hello Jonathan,
thank you for your reply.
In fact after posting the above I gave it a second read in
the IBM Informix Guide to SQL: Syntax docs, pg 6-17 and saw
that I was mislead by all the example on slides I saw.
CREATE CHUNK SQL Admin API Command and the CREATE DBSPACE
API Command have the 'WITH_CHECK' Option.
Without 'WITH_CHECK' they are able to create the file if it is not
there, but if one uses WITH_CHECK, the file (or raw device)
has to be there already.
Today I tested, that path can be a symlink and it also
works w/o 'WITH_CHECK'. If the symlink is already there,
and is specified in the pathname parameter, then is works
as expected.
dic_k
As a sidenote: It 'd be good style, if the IDS 11.50.UC4-
Instance in the Virtual Appliance had symlinks instead of
filepaths in the reserved pages .....
Please, for the next Release 11.50.UC5 this should be changed
if possible!
--
Richard Kofler
SOLID STATE EDV
Dienstleistungen GmbH
Vienna/Austria/Europe
Richard Kofler wrote:
> Jonathan Leffler schrieb:
>> On May 23, 2:26 pm, Richard Kofler <richard.kof...@chello.at> wrote:
>>
>>> [ IDS 11.50.UC4 on SuSE Linux ]
>>>
>>> I am testing IDS11.50.UC4 coming from IDS 10.00.
>>>
>>> The CREATE DBSPACE SQL Admin API Command seems not
>>> to have a way to specify a symbolic link for the
>>> parameter value of pathname.
>>>
>>> Do I miss something here?
>>>
>>> All I want to do using the API is:
>>> touch $SPACE/idschunks/chk001_01
>>> chmod 660 $SPACE/idschunks/chk001_01
>>> ln -s $SPACE/idschunks/chk001_01 $IDSSYMLINKS/L_chk001_01
>>> onspaces -c -d dbspc001 -p $IDSSYMLINKS/L_chk001_01 -o 0 -s $SIZE>>>
>>> Is there a way to do the same using the new API?
>>
>> I think the API assumes that the space is already 'allocated' or
>> 'available' -- that is, the file name specified already exists. When
>> it does, it may be a symlink; but the name must already exist.
>>
>> None of the utilities that manage dbspaces actually create the file
>> that is used.
>>
>> It is not an unreasonable request to make - but I think it is a
>> feature request (and one that will need some care in implementation).
>>
>> -=JL=-
>
> Hello Jonathan,
>
> thank you for your reply.
> In fact after posting the above I gave it a second read in
> the IBM Informix Guide to SQL: Syntax docs, pg 6-17 and saw
> that I was mislead by all the example on slides I saw.
> CREATE CHUNK SQL Admin API Command and the CREATE DBSPACE
> API Command have the 'WITH_CHECK' Option.
> Without 'WITH_CHECK' they are able to create the file if it is not
> there, but if one uses WITH_CHECK, the file (or raw device)
> has to be there already.
> Today I tested, that path can be a symlink and it also
> works w/o 'WITH_CHECK'. If the symlink is already there,
> and is specified in the pathname parameter, then is works
> as expected.
>
> dic_k
>
> As a sidenote: It 'd be good style, if the IDS 11.50.UC4-
> Instance in the Virtual Appliance had symlinks instead of
> filepaths in the reserved pages .....
> Please, for the next Release 11.50.UC5 this should be changed
> if possible!
>
A nice feature would be to allow the API command to accept arguments to create
a symlink and a file and create both if they don't exist.
Nevertheless I don't think that using sym links is so important as it used to
be since you can easily change paths on restore. (I still use them of course)
In any case the suggestion in your sidenote should be sent to Guy Bowerman. I'm
not sure if he reads this, but I can send him a note.
Regards.
--
Fernando Nunes
Portugal
http://informix-technology.blogspot.com
My email works... but I don't check it frequently...