Version 6.3.8 for Windows
 —  Messages and Codes  —

Natural System Error Messages 6501-6550

NAT6501: Database :1: is not active or accessible.

Text Database ... is not active or accessible.
Expl. The specified database is currently not active, or, if you are
working with a remote database, perhaps NET-WORK is not active.
If the error occurs during automatic start via Natural, try to start
the database in the foreground from the command prompt
(use ADAMAIN DBID) to detect the original error.
If you receive the message during execution of a Natural program,
start the database you require. To determine this database
check the DBIDs of the corresponding DDMs. If the error occurs when
transaction data is being read or written, the database specified by
the parameter UDB is required.
Actn. see explanation

NAT6502: The database call is too big to fit into the communication area.

Text The database call is too big to fit into the communication area.
Expl. Either the database call is bigger than the communication area or, if
you are using either the standalone version or the file-server version
of Natural, the communication area contains an earlier database
call. This error can occur when an application (such as Natural or
an Adabas utility) ends abnormally while waiting for an answer to the
earlier database call.
If you are using either the standalone version or the file-server
version of Natural, restart the database. If this has no effect or
you are using a different version of Natural, increase the size of
the communication area and then restart the database.
Actn. see explanation

NAT6504: The database has failed to answer a call within the time allowed.

Text The database has failed to answer a call within the time allowed.
Expl. The time limit for a database call has been reached and the database has
not answered.
Actn. Increase the size of the parameter that sets the time limit. If this has
no effect, contact Software AG support because there could be an
internal error in the database.

NAT6506: There is no connection to the local routing table.

Text There is no connection to the local routing table.
Expl. The routing table contains information about open databases. The lack of
a connection to it indicates an internal error.
Actn. Contact Software AG support.

NAT6507: The application has already accessed max. number of databases.

Text The application has already accessed max. number of databases.
Expl. In the current version there is a limit of 10 different databases
which can be accessed by an application.
Actn. Try to reduce the access to so many different databases.

NAT6508: More databases available than can be returned by apcm̲dbstate.

Text More databases available than can be returned by apcm̲dbstate.
Expl. apcm̲dbstate could not return all active databases because
not enough space was allocated by the calling function.
This message is for internal use only.
Actn. Contact Software AG support.

NAT6509: Database is already active.

Text Database is already active.
Expl. The database to be started is already active.
Actn. Do not start a database which is already active.

NAT6510: Database number invalid.

Text Database number invalid.
Expl. The database number must be in the range of 1 .. 255.
Actn. Check the database number and use only numbers which are within the range
specified above.

NAT6511: Internal error :1: in interface to database server.

Text Internal error in interface to database server.
Expl. Internal error.
Actn. Contact Software AG support.

NAT6512: Internal error :1: in interface to TP monitor

Text Internal error ... in interface to TP monitor
Expl. Internal error.
Actn. Contact Software AG support.

NAT6513: The TX interface is not available.

Text The TX interface is not available.
Expl. A database has been configured to use the TX interface for
transaction control. However, the TX interface is not
available.
Actn. Make the TX interface available.

NAT6514: Error :1: from call to TX interface.

Text Error ... from call to TX interface.
Expl. Each nonzero response code from the TP monitor is reported
with this error message.
Actn. For more information see: Your TP monitor documentation.

NAT6515: ET data not available.

Text ET data not available.
Expl. ET data cannot be stored in databases, that are
coordinated by a transaction monitor.
Actn. Correct setting of ETDB or XADB parameter.

NAT6520: No database found.

Text No database found.
Expl. No database found in the DBENV directory.

NAT6521: Semaphore already exists.

Text Semaphore already exists.
Expl. A semaphore which should be created exists already. Internal error.
Actn. Contact Software AG support.

NAT6523: Mode of a semaphore is invalid.

Text Mode of a semaphore is invalid.
Expl. A semaphore is created with an invalid mode. Internal error.
Actn. Contact Software AG support.

NAT6524: There are too many semaphores open.

Text There are too many semaphores open.
Expl. All semaphores in the system are in use.
Actn. Reduce active programs which use semaphores.

NAT6525: Semaphore not found.

Text Semaphore not found.
Expl. A semaphore which should be used is not there. Internal error.
Actn. Contact Software AG support.

NAT6526: Error at semaphore setting.

Text Error at semaphore setting.
Expl. Internal error.
Actn. Contact Software AG support.

NAT6527: Invalid handle of semaphore.

Text Invalid handle of semaphore.
Expl. A semaphore was used with a wrong handle. Internal error.
Actn. Contact Software AG support.

NAT6528: Private semaphore could not be shared.

Text Private semaphore could not be shared.
Expl. Internal error.
Actn. Contact Software AG support.

NAT6529: Too many semaphore requests.

Text Too many semaphore requests.
Expl. A semaphore is requested too many times.
Actn. End the application and the database and try again.
When the error occurs again, contact Software AG support.

NAT6530: Semaphore timed out.

Text Semaphore timed out.
Expl. A semaphore timeout. Internal error.
Actn. Contact Software AG support.

NAT6531: Semaphore owner died.

Text Semaphore owner died.
Expl. A semaphore could not be accessed because the owner (i.e application
or database) has died. To use the semaphore again all processes which
use this semaphore must stop.
Actn. End the application and the database. If this is not possible, reboot
the system and try again.

NAT6533: Internal semaphore error occurred.

Text Internal semaphore error occurred.
Expl. Internal error.
Actn. Contact Software AG support.

NAT6542: shared memory segment with the specified name does not exist.

Text Shared memory segment with the specified name does not exist.
Expl. Internal error.
Actn. Contact Software AG support.

NAT6543: Invalid handle of shared memory.

Text Invalid handle of shared memory.
Expl. A handle of a shared memory is invalid. Internal error.
Actn. Contact Software AG support.

NAT6544: No more memory available.

Text No more memory available.
Expl. Either the operating system is not configured correctly or there is not
enough space on the disc for the system swap file.
Actn. Check the configuration settings of the operating system and correct
them if neccessary. Then check the available disk space for your system
swap file. Please contact your system administrator for further help.

NAT6545: Access to shared memory denied.

Text Access to shared memory denied.
Expl. A semaphore which should be created exists already. Internal error.
Actn. Contact Software AG support.

NAT6547: Shared memory already exists.

Text Shared memory already exists.
Expl. A shared memory which should be created exists already. Internal error.
Actn. Contact Software AG support.

NAT6549: There are too many shared segments open.

Text There are too many shared segments open.
Expl. All shared segments in the system are in use.
Actn. Reduce active programs which use shared segments.

NAT6550: Disc full.

Text Disc full.
Expl. The device is full.
Actn. Increase free space on the hard disc / floppy. Check the disk space
where the swap file is located.

Top of page