New problem during Dbimport

abdel BIDAR wrote: > > One of my customer have encountered a problem during dbimport . > After doing a success dbexport . He tries to do a dbimport but he > encountered a problem : > He had these error message > > *** execute sqlobj > 312 - Cannot update system catalog (sysdistrib). > 131 - ISAM error: no free disk space > " > and import is ending. > What to do with it? Is it because the database is corrupted. I think not. I think it is probably "131 - ISAM error: no free disk space". Sounds crazy "'cause the database fitted in the disk space before the import" - right? This type of problem is easy to reproduce in an instance tight for disk space. A simple ALTER TABLE MODIFY NEXT SIZE <something big> should be enough to do it. What was "onstat -d" reporting before the export? Also, I'm guessing that the dbimport fell over during update statistics statements generated at the end of the script. Brett Randall > > If someone have an idea , it will be great > > abdel

One of my customer have encountered a problem during dbimport . After doing a success dbexport . He tries to do a dbimport but he encountered a problem : He had these error message *** execute sqlobj 312 - Cannot update system catalog (sysdistrib). 131 - ISAM error: no free disk space " and import is ending. What to do with it? Is it because the database is corrupted. If someone have an idea , it will be great abdel

You did not specify version or even operating system - I will assume IDS version 7.x or above and some sort of UNIX... The system is telling you that there is no free space left either in: dbspace the table/index is being imported into, or, rootdbs, or, tempdbs, or, /tmp (Unix temporary directory) Do not take the names above literally - whatever the system has these set to. I would recommend you/your customer drop the database if still there and restart the dbimport while running an onstat -d as well as a df in separate terminal sessions to observe the space usage and see what is getting filled up and take action accordingly (that is, after checking the current status of all of the above - perhaps you can see what is filling up right away and take the necessary action before the second try)... Hal Maner M Systems International, Inc. www.msystemsintl.com abdel BIDAR <abdel.bidar@marconi.com> wrote in message news:94978h$3ot$1@newsfeed.pit.comms.marconi.com... > One of my customer have encountered a problem during dbimport . > After doing a success dbexport . He tries to do a dbimport but he > encountered a problem : > He had these error message > > *** execute sqlobj > 312 - Cannot update system catalog (sysdistrib). > 131 - ISAM error: no free disk space > " > and import is ending. > What to do with it? Is it because the database is corrupted. > > If someone have an idea , it will be great > > abdel > > > >

The second error message says it all: No free disk space. Are you specifying which dbspace the dbimport is going to? If not, the import is happening in rootdbs. abdel BIDAR wrote: > One of my customer have encountered a problem during dbimport . > After doing a success dbexport . He tries to do a dbimport but he > encountered a problem : > He had these error message > > *** execute sqlobj > 312 - Cannot update system catalog (sysdistrib). > 131 - ISAM error: no free disk space > " > and import is ending. > What to do with it? Is it because the database is corrupted. > > If someone have an idea , it will be great > > abdel -- Phillip Tien Database Administrator Whole Foods Market, Inc.