//
you're reading...
QAD Ent Application

SYSTEM ERROR: Can’t attach shared memory with segment_id: for

SYSTEM ERROR: Can’t attach shared memory with segment_id: <id> for <dbname>

fact: MFG/PRO All Versions

fact: Progress All Versions

fact: Database start-up

fact: Starting database server

symptom: SYSTEM ERROR: Can’t attach shared memory with segment_id: <id> for <dbname>

symptom: There is no server for database <dbname>. (1423)

symptom: Progress error 1423

symptom: Unable to start a database server

cause: The database structure (.db) file still refers to shared memory segments that do not belong to it anymore.

fix: It is necessary to clear the shared memory segments’ ids from the database structure file.

In order to do this, move to the directory where the database structure (.db) file is located:
cd /databases/production

Then run the command below in order to create a new structure description (.st) file that reflects the database’s current structure.
prostrct list <dbname>

And now run the command below to refresh the database structure (.db) file.
prostrct repair <dbname>

Remarks:
If a database lock (.lk) file exists for the database, it will be necessary to make sure that no process is using the database and remove that lock file.  If you are not sure, DO NOT remove it.
It may also be necessary to specify the full path to PROGRESS’s prostrct utility if it is not included in the session’s PATH environment variable.

fact: MFG/PRO All Versions

fact: Progress All Versions

fact: Database start-up

fact: Starting database server

symptom: SYSTEM ERROR: Can’t attach shared memory with segment_id: <id> for <dbname>

symptom: There is no server for database <dbname>. (1423)

symptom: Progress error 1423

symptom: Unable to start a database server

cause: The database structure (.db) file still refers to shared memory segments that do not belong to it anymore.

fix: It is necessary to clear the shared memory segments’ ids from the database structure file.

In order to do this, move to the directory where the database structure (.db) file is located:
cd /databases/production

Then run the command below in order to create a new structure description (.st) file that reflects the database’s current structure.
prostrct list <dbname>

And now run the command below to refresh the database structure (.db) file.
prostrct repair <dbname>

Remarks:
If a database lock (.lk) file exists for the database, it will be necessary to make sure that no process is using the database and remove that lock file.  If you are not sure, DO NOT remove it.
It may also be necessary to specify the full path to PROGRESS’s prostrct utility if it is not included in the session’s PATH environment variable.

Advertisements

About iambaprang

Bap Rang's house

Discussion

No comments yet.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s