Re: SQL files not visible in DB-ACCESS
Posted in 1996
Topics: Installation, Setup & Upgrades, Stored Procedures & SPL, Server Administration
Alexander Ponomarenko <shura@bitcom.msk.ru> wrote:
>John Prideaux <alastl@ix.netcom.com> wrote:
>> wombn@sprynet.com wrote:
>> >
>> > > John Prideaux <alastl@ix.netcom.com> wrote:
>> > >. We recently upgraded from SCO 3.2.4.2 to SCO
>> > > }5.0, and upgraded our Informix from SE 7.10 to SE 7.12.UC1. When we enter
>> > > }dbaccess and attempt to select a previously saved .sql, not all of them
>> > > }are visible. If we enter the name of a script we know is there, it will
>> > > }then find it, but it still will not show up on the list (even if we then
>> > > }re-save the script). I am guessing that this is a problem with the SCO port
>> > > }of dbaccess, because our ISQL (6.03.UC1) does not behave in this manner.
>> > >
>> > >>>>
>> > In my environment, we've had problems with long .sql file names. Have you tried
>> > shortening the names?
>>
>> Our file names are all 14 characters or less. In fact, all of the "missing"
>> files were created before our upgrade and appeared fine under our previous
>> Informix version.
>>
>This is not Informix 7.X bug. We have 6.00UD2 and have the same problem.
>We discover it when we upgraded from 3.2.4.2 to OSR5. Possible OSR5.0.2
>can help us? If you will find any solution please let me know. Thanks
>in advance.
>---
>Shura Ponomarenko <shura@bitcom.msk.ru>
>System Manager, BITCOM Ltd, Moscow.
I don't know about the long sql filename problem, but I believe that I
know what is causing the problem with not displaying all of the sql
files in the current directory.
Apparently the new default filesystem type in OS5 (HTFS) has a subtle
interaction with the readdir() system call, especially when there are
a lot of files in that directory.
If the directory where those sql files exists is not on the root
filesystem, then you could change the filesystem type from HTFS to
EAFS (AFTER backing everything up, of course). The only functionality
that you would lose from such a change is that that filesystem could
not be > 2GB in size or have > 65000 inodes. The journaling
functionality remains intact.
BTW, I haven't run the OS5-specific port of SQL4.x and SE5.x along
with I-Net, but if anyone has any feedback, I'd love to hear it.
HTH,
*************************************************************
That was Zen - this is Tao
*************************************************************