Adding dbspace/chunks with onspaces
Windows 2000 Advanced Server sp3
Informix 9.21.TC5X6
You'll probably think that I'm losing it with this question, but here
goes;
for reasons too varied and too dull to go into, I'm looking at the
feasibility of adding a new dbspace and associated chunks on a remote
machine
(I know - I can think of a hundred reason not to as well - but all are
as nothing against the magic word 'costs')
basically to store archived data from our ERP system which no-one's
going to want to access any more, and is just generally cluttering up
the place.
Have set up a share giving full control to all informix admin logins -
and can add a file and open it up for edit in the online command
prompt, so permissions are obviously OK, but when I run
onspaces -c -d <dbspace> -p <file path> -o 0 -s 20480
I get the message
The file <file path> does not exist.
either using UNC or a mapped drive
I've been through the Administrator's guide, and it doesn't state
anywhere that you *can't* link to another machine in this way (at least
not that I've found).
Does anyone know if this is (in principle) possible - and if so, any
idea where I'm going wrong?
ta
Andrew
> onspaces -c -d <dbspace> -p <file path> -o 0 -s 20480>
> I get the message
>
> The file <file path> does not exist.
> either using UNC or a mapped drive
Does the file <file path> really exist?
Does informix user have all the permissions to access this remote file?
Simply try to login as local user informix and perform command like:
copy nul \\\\path_to_your_shared_resource\\your_file
and, if <your file> will be successfully created - that's all!
> Does anyone know if this is (in principle) possible - and if so, any
> idea where I'm going wrong?
It is possible. I used the same idea for TAPEDEV with total success :)
Although you have to solve your Windows security issues.
Hi - thanks for the prompt reply. Yes - the file does exist. In order
to try and convince myself that the problem wasn't a typo somewhere in
te path - one of my approaches was to use a script to create the file
on the remote machine (just as you suggested) - and then the onspaces
command with the filename just created pasted in to the appropriate
spot. The file created OK - onspaces claimed it didn't exist. I can
also open and edit in the same command line box, no problem