E_SC0206 An internal error prevents ...

[aleniaam]

I have run the following line commend:

verifydb -mrun -sdbname "icd_ept_alenia ucs_db test aln_hardwired" -opurge


but ingres gives me the following error:

Aborting because of error
E_SC0206 An internal error prevents further processing of this query.
Associated error messages which provide more detailed information about
the problem can be found in the error log, II_CONFIG:error.log

[maspa05]

{reply deleted - not what I thought it was}

[aleniaam]

Now I have run the command again and it tells me:

E_DU101A_CANT_CONNECT
Unable to connect with database icd_ept_alenia-
E_DU502A_PURGE_ERR
VERIFYDB: Fatal erro encounterd while attepting
to purge database icd_ept_alenia

[aleniaam]

Now it seems that the error comes back to the one in the first post.

The second error, I suppose, was given because there was someone loggeg in.

Sorry

[dejan]

Aleniaam, I think you are getting an error because verifydb tried to get an exclusive lock on the database, and failed because someone already had some lock(s) there, so verifydb failed.

[kschendel]

The error log is not terribly informative. It's trying to list the filenames in the data directory, so I'd suggest taking a look in the data locations for that database. (Infodb will tell you what the directories are.) Make sure the directory permission is OK, make sure that there are no bizarre filenames in the directory. Valid data location filenames look something like aaaabcde.t00 or occasionally ppppabcd.t00.

You can also try enabling the DBMS log if it's not enabled already. In a command prompt, type "ingprenv" and see if you have II_DBMS_LOG defined. If not, ingsetenv II_DBMS_LOG 'full-path' where full-path is a directory + filename where Ingres will put the DBMS log. Sometimes the DBMS log has more information than the error log.

[aleniaam]

Attached there is the ii_dbms_log file.

The second kind of error was given because there was somebody logged in.

But the first kind of error I don't really know the reason.

Give a look at the log file, please

Thanks

[seran01]

It appears that the E_SC0206 occurs, because :

if there is any work location defined, but for which the physical directory is not properly created .

An output from
ingprenv
and
infodb icd_ept_alenia
infodb ucs_db
infodb test
infodb aln_hardwired

would give more infomation about the work directories for each database.

[aleniaam]

Here there is the info ...

[padst01]

hi Aleniaam,

it seems your databases are on D disk while the rest is still stored on C drive (Work, Dump, Journals, etc.). I would suggest you make sure you are not running out of disk space on C and check all directories mentionned in infodb do exist.

Hope this helps