I don't use SE so I'm only guessing here:
I do know that when you unload a table and reload it using the "onunload" and "onload" statements the priviledges are revoked and have to be recreated. Is it possible that to fix the index problem Informix rebuilt the table (or...
Only guessing here:
Is this a new database instance? Did you initialize the shared memory before you tried to start it?
Are you logged on as root or informix?
Is there any error number with the message? Sometimes it's hard to tell when the message is a Unix error or an Informix error...
You have my sympathies. There is usually a file somewhere on your systems that shows you the default settings for the Unix kernel parameters. However these always need to be tuned to fit your system's usage.
For now I think your best bet is trying to find the Informix file that tells you the...
Actually this is an issue for your Unix System Admin. SHMSEG is a Unix kernel parameter that will need to be changed. Somewhere in the installation notes for your operating system it should tell you what it should be set to.
On our system it's in $INFORMIX/release/en_us/0333/ONLINE.7.2
I'd...
What does the message in your online log say? If you've reached a maximum of some parameter setting it will tell you in the log.
I can tell you something from experience: if a user kills their Informix process using a kill -9 it can cause the database to crash. They MUST use the onmode -z...
While I'm not familiar with SCO I'm pretty sure the cpio command is the same:
find / -depth -print | cpio -oavcC 32768 > /dev/your/tapedrive
or of you don't want to use an explicit path:
cd /
find . -depth -print | cpio -oavcC 32768 > /dev/your/tapedrive
This will back up everything from the...
Not sure what application you are using. In my office we put a line in the user's .profile that sends them directly into the GUI application when they log on. If they exit the application they automatically get logged off. The last few lines of their .profile looks like this:
if [...
I'm not familiar with your platform but I can imagine all kinds of reasons why stopping your system clock would cause problems. There are lots of system processes that run in the background (daemons). Many of them go to sleep and wake up at different intervals. They obviously use the system...
Jim,
Many of the tables that will show up are temporary tables created by Informix. Don't ask me what they're for. I asked Informix once and got one of those garbled responses that made me think they didn't know either. They tend to come and go depending upon system usage.
For the tables...
Wow, that seems like an awful lot of work for a backup. Of course the good part is you can restore a single table, which you couldn't do if you used Informix to do the backup. However I don't know how you would apply your logical logs if you needed to do a restore.
As I said I don't have any...
I was told by Informix that once a table has more than 8 extents then paging becomes a performance problem. I monitor extents every few weeks and if I see a table has 9 or more extents I usually rebuild it. I know at first Informix said 8 extents was best. Then they said it didn't matter...
type: onstat -d
It lists the location of all the database chunks. If it says something like:
/dev/ios/rsdisk00s4
or
/dev/vd/rvdisk5
Then it's a raw disk.
If it says something like:
/home/informix/data/file1
Then it's a regular Unix file.
If you don't know where the data is how can you...
You didn't tell me how you store your Informix tables. Are they on raw disk or are they in Unix files?
If they are regular Unix files in a file system then I don't think I can help you.
Jane
Another thing I should have asked:
When the system has problems have you looked at the Informix log? Don't know about your system but on ours it's in $INFORMIX/online.log (where 'online.log' is whatever you called it in your configuration file)
Jim,
It's not very easy to check for number of extents. This is the way I do it:
onstat -T > somefile (will list all tables in your instance)
The last column on the right is the number of extents.
To figure out which table a row refers to you have to take the value listed under...
Yes, that's what they are.
If someone is editing a file with 'vi' and they get disconnected for some reason a file is created in /usr/preserve that allows them to start again where they left off next time they log on. In my experience almost nobody ever does.
If the files are more than one...
What I'm saying below definitely pertains to you if you are using raw devices for your data. If you are using "cooked" files (or regular Unix files) then it still probably makes sense but since I don't have experience using cooked files I'm not sure:
We also do a level 0 backup...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.