|
   
Appendix
D . Troubleshooting
D. Troubleshooting
This appendix
describes the problems you may encounter when you create, start, or
connect to a database when using DBMaker. It also suggests the possible
solutions for you to solve these problems. The listed warning and error
messages are arranged in numerical order.
ERROR ( ): bind
address error: Address already in use
Cause
This error
occurs when you try to run dmserver, and may be caused by one
of the following situations:
1. The
port number specified for your database in dmconfig.ini is being used
by another process or another copy of dmserver.
2. The
port number specified for your database in dmconfig.ini was being used
by another process or another copy of dmserver that terminated
abnormally and did not release the port.
Solution
1. Change
the port number specified in dmconfig.ini on both the client and server
sides, and then try to start the database again.
2. Wait
for a period of time for the port number to be released by the operating
system. The amount of time depends on your operating system.
WARNING (43):
an active transaction has been aborted
Cause
This error
may occur in situations where a database is running with the AUTOCOMMIT
option set to OFF and some action occurs that forces user transactions
to be aborted, such as:
1. You
disconnect from a database before issuing the COMMIT WORK command for
your active transactions. Disconnecting from a database with the AUTOCOMMIT
option set to OFF will abort any active transactions.
2. You
terminate a database when there are other users connected who haven't
issued a COMMIT WORK command for their active transactions. Terminating
a database with the AUTOCOMMIT option set to OFF will abort any uncommitted
transactions of other users.
Solution
1. Commit
your work before you disconnect from the database.
2. Tell
other connected users to commit their work and disconnect before you
terminate the database.
WARNING (44):
could not lock temporary table
Cause
You tried
to lock a temporary table, but only permanent tables can be locked.
You should note that in the PC single user model, if you try to lock
a temporary table, no warning message will be given.
Solution
This is
by design. Only permanent tables can be locked.
WARNING (45):
previous backup mode will be restored
Cause
The backup
mode was changed during an on-line full backup, but the backup was aborted
before it completed. When a backup is aborted, DBMaker returns the database
to the state it was in before the backup started to ensure consistency.
This will restore the backup mode to the mode it was originally in before
the backup started
Solution
This is
by design. This warning is only a reminder for the user.
WARNING (47):
consistency check found errors
Cause
There are
inconsistencies in the database. This may result from hardware failures
such as disk errors.
Solution
Please
consult with CASEMaker product support personnel.
WARNING (56):
cannot open a backed up journal file to roll over:
Cause
Some of
the contents of the archived journal file are invalid or not in sequence.
Solution
Give Server
Manager another complete valid journal file.
WARNING (59):
the order of the journal file is wrong:
Cause
One of
the crashed journal files is not in the correct sequence to do a rollover.
Solution
Give the
crashed journal files to Server Manager in the correct sequence.
WARNING (60):
not enough journal files to roll over:
Cause
There are
not enough crashed journal files to do a rollover.
Solution
If your
database has N journal files, you must give N crashed journal files.
Please give the valid amount N of crashed journal files to Server Manager.
Otherwise, give zero to Server Manager.
WARNING (70):
backup server doesn't exist
Cause
When journal
is almost full and backup server is called, DBMaker finds the backup
server does not exist in the system. This error occurs when both backup
mode and backup server are on.
Solution
1. When
the journal is really full, manually perform the backup.
2. Terminate
the database, then restart it and the backup server.
WARNING (79):
invalid value in configuration file
Cause
Some values
in dmconfig.ini are invalid. For example, if you set DB_LTIMO= -5 in
the dmconfig.ini file, you will get this warning message when you connect
to the database. (Because -5 is not a legal value for DB_LTIMO.)
Solution
Make sure
the values for all keywords in dmconfig.ini are valid. The valid values
for each keyword are listed in Appendix B.
ERROR (101):
not enough space to insert object
Cause
1. You
try to insert a data record but all the data files in the tablespace
are full.
2. You
try to insert a BLOB record but all the BLOB files in the tablespace
are full.
3. You
try to insert a BLOB record but no BLOB file exists in the tablespace.
4. No disk
space remains on your system.
Solution
1. Add
a new data file to the tablespace. Refer to the DBATool User's Guide
for instructions on how to add data files to a tablespace.
2. Add
a new BLOB file to the tablespace. Refer to the DBATool User's Guide
for instructions on how to add BLOB files to a tablespace.
3. Add
a new BLOB file to the tablespace. Refer to the DBATool User's Guide
for instructions on how to add BLOB files to a tablespace.
4. Ask
your system administrator to free disk space for use by the database
or add more storage.
ERROR (316):
USER file object function off, cannot link file
Cause
You try
to link an external file to the database as a user file object, but
the user file object option has been turned off in dmconfig.ini.
Solution
Terminate
the database and turn on the user file object option by setting the
keyword DB_USRFO = 1 in dmconfig.ini. Then restart the database and
execute the command again.
ERROR (401):
unique key violation
Cause
1. You
tried to create a unique index, but the key columns contain duplicate
values.
2. You
tried to insert a duplicate value into a column that has unique index
on it.
Solution
This is
by design. You cannot create a unique index on columns that contain
duplicate values, and you cannot insert a duplicate value into a column
that has a unique index on it. This is part of the definition of a unique
index.
ERROR (605):
incompatible file version:
Cause
The database
was created with a version of DBMaker different from the one you are
using, and the file format of these two versions is not compatible.
Solution
Use the
version of DBMaker that was used to create the database, or a version
with a compatible file format. If you want to use your database with
another version of DBMaker that has an incompatible file format, you
must unload the database with the compatible version, and load it again
with the new version. For more information on the load and unload commands,
please refer to the dmSQL User's Guide. For information on which
versions of DBMaker have compatible file formats, please consult with
CASEMaker product support personnel.
ERROR (606):
incompatible byte ordering:
Cause
This error
will occur when a database is created and used on machines with CPUs
having a different low/hi byte sequence (big-endian/little-endian CPUs).
For example, if you create a database on one machine with an Intel CPU,
and then move the database to another machine with a Motorola CPU, you
will get this error message when you try to start it on the machine
with the Motorola CPU.
Solution
Unload
the database on the original machine and create a new, empty database
on the target machine. Then load the database into the newly created
database on the target machine.
ERROR (607):
database name does not match with database name recorded in file:
Cause
The name
of the database you want to start is different from the name of the
database recorded internally in the database file. This error will occur
if you tried to manually change the name of the database in the host
operating system and dmconfig.ini file. Since a database created with
DBMaker also records the database name internally, the database will
not start for consistency reasons.
Solution
Unload
the database and create a new, empty database with the name you want
to use. Then load the database into the newly created database.
ERROR (608):
system information page format in db file is invalid:
Cause
The database
was created with a version of DBMaker different from the one you are
using, and the file format of these versions is not compatible.
Solution
Use the
version of DBMaker that was used to create the database, or a version
with a compatible file format. If you want to use your database with
another version of DBMaker, you must unload the database with the compatible
version, and load it again with the new version. For more information
on the load and unload commands, please refer to the SQL Command
and Function Reference. For information on which versions of DBMaker
have compatible file formats, please consult with CASEMaker product
support personnel.
ERROR (609):
number of journal files (in configuration file) does not match with
system information
Cause
The number
or size of journal files you specified in dmconfig.ini is different
from the system information recorded in the database you want to start.
The database will not start for consistency reasons.
Solution
Use NEW
JOURNAL mode to change the number and size of the journal files. For
more information on how to use new journal mode, refer to the chapter
Advanced Database Administration.
ERROR (853):
timeout value is invalid
Cause
An invalid
lock timeout value was specified in the parameter of the ODBC function
SQLSetConnectOption().
Solution
The default
lock timeout value is 5 seconds. The valid value range for lock timeout
is from -1 to 2147483648. If you specify -1 as the value, the process
will wait until the lock is released (i.e. disable lock timeout).
ERROR (902):
database terminated or not started yet
Cause
There are
two situations in which this error message might occur:
1. A user
tries to connect to a database which has not been started yet. This
error message will also occur if the START DB command has been issued,
but the database has not yet finished starting when a user tries to
connect. For example, one user starts a database and another user tries
to connect to the database at approximately the same time. If the start
operation has not finished, the second user will get this error message.
2. In the
Unix client/server model, if the shared memory allocated to a DBMaker
server is removed without killing the server, then any client applications
that try to connect to the server will get this error message.
Solution
1. Wait
for the database to finish starting.
2. Kill
the server process and restart the database.
ERROR (1002):
cannot switch journal mode: backup mode on or backup in progress
Cause
There are
two situations in which this error message might occur:
1. You
try to turn on NO JOURNAL mode while the database is running in BACKUP
mode. You can not switch the journal mode while DBMaker is in BACKUP
mode.
2. You
try to turn on NO JOURNAL mode during a backup operation. You cannot
switch the journal mode during a backup.
Solution
1. Shut
down the database, change the backup mode in dmconfig.ini to NO BACKUP
and restart the database.
2. Wait
until the backup in progress is finished, then set the journal mode
to NO JOURNAL.
ERROR (1102):
lock timeout
Cause
Another
connection is holding a lock on some database resource that you are
trying to use.
Solution
Wait for
the connection that is holding the resource to commit its work. If you
are not sure which connection is holding the resource you need, you
can use DBATool to find out.
If you
are waiting for a connection that has been abnormally terminated but
left the connection active, you can ask your DBA to kill the connection
to free the locks.
ERROR (1103):
out of DCCA memory: initial DCCA setting is too small
Cause
The initial
size of the shared memory allocated for the database is too small. The
database is currently holding locks on too many objects or there are
too many transactions in the system, and the database has requested
more memory than was initially allocated.
Solution
Please
refer to Chapter 4 -Basic Database Administration and Chapter
11 - Performance Tuning to adjust the size of DB_SCASZ, DB_NBUFS,
DB_NJNLB, DB_NTRAN in dmconfig.ini. Otherwise, you will have to reduce
the number of users currently using the database. You may alternatively
change the table lock mode to a higher level, which decreases the amount
of resources used, but also reduces the level of concurrency.
ERROR (1104):
cannot start database : shared memory in use
Cause
This message
may occur in one of the following conditions:
1. You
try to start a database that has already been started. It is not possible
to start a database with the same name as a database that has already
been started.
2. The
database terminated abnormally the last time it was run, and the shared
memory it allocated has not been freed. You cannot start a database
that still has shared memory allocated in the system.
Solution
1. If the
database has already been started, you do not need to start it yourself.
Simply connect to the database using the CONNECT command.
2. On the
machine the database was last started before it terminated abnormally,
use the UNIX utility ipcrm to remove the allocated shared memory
from your system. For more information on how to use ipcrm, please
refer to your UNIX operating system documentation.
ERROR (1105):
cannot allocate sort memory, operating system out of memory
Cause
The database
tries to allocate memory for doing a sort operation, but the operating
system is out of memory.
Solution
Kill some
non-urgent processes to release memory.
ERROR (1110):
Requested DCCA memory exceeds system maximum
Cause
There are
two situations in which this error message can occur:
1. The
machine you are trying to run the database on does not have enough physical
memory to start the database.
2. This
error can also occur on UNIX systems if the maximum amount of shared
memory that can be allocated by the operating system is smaller than
that requested by the database.
Solution
1. Make
the size of the DCCA small enough to allow the database to start on
machines with limited amount of physical memory, or add more physical
memory to the system.
2. Please
see your UNIX operating system documentation for information on how
to change the maximum size of shared memory that can be allocated by
the operating system. On most UNIX systems, you will have to rebuild
the UNIX kernel and specify a new size for the maximum amount of shared
memory.
ERROR (1111):
not enough memory to allocate shared memory
Cause
There are
two situations in which this error message can occur:
1. The
machine you are trying to run the database on does not have enough physical
memory to start the database.
2. This
error can also occur on UNIX systems if the maximum amount of shared
memory that can be allocated by the operating system is smaller than
that requested by the database.
Solution
1. Make
the size of the DCCA small enough to allow the database to start on
machines with limited amount of physical memory, or add more physical
memory to the system.
2. Please
see your UNIX operating system documentation for information on how
to change the maximum size of shared memory that can be allocated by
the operating system. On most UNIX systems, you will have to rebuild
the UNIX kernel and specify a new size for the maximum amount of shared
memory.
ERROR (1112):
DCCA is too large to allocate from OS shared memory
Cause
There are
two situations in which this error message can occur:
1. The
machine you are trying to run the database on does not have enough physical
memory to start the database.
2. This
error can also occur on UNIX systems if the maximum amount of shared
memory that can be allocated by the operating system is smaller than
that requested by the database.
Solution
1. Make
the size of the DCCA small enough to allow the database to start on
machines with limited amount of physical memory, or add more physical
memory to the system.
2. Please
see your UNIX operating system documentation for information on how
to change the maximum size of shared memory that can be allocated by
the operating system. On most UNIX systems, you will have to rebuild
the UNIX kernel and specify a new size for the maximum amount of shared
memory.
ERROR (1113):
cannot attach shared memory or shared memory does not exist
Cause
The operating
system cannot attach shared memory or shared memory does not exist.
This is an operating system error.
Solution
Please
refer to your operating system documentation.
ERROR (1114):
available data space is not enough
Cause
Operating
system error.
Solution
Please
refer to your operating system documentation.
ERROR (1115):
shared memory permission denied
Cause
Operating
system error.
Solution
Please
refer to your operating system documentation.
ERROR (1201):
the file already exists
Cause
You tried
to create a new database with the same name as an existing database.
The database files (.DB, .BB) or journal files (.JNL) already exist.
Solution
Choose
a new name for your database that is not already being used by an existing
database, or delete the old database and journal files if they are no
longer in use.
ERROR (1204):
cannot get shared lock on the database system file, start database fails
Cause
This message
may occur in one of the following situations:
1. There
are one or more users still connected to a database which has been terminated,
and you try to restart the database.
2. Another
user starts a database but doesn't disconnect from it, and you try to
connect to the database.
Solution
1. Ask
those users who are still connected to the terminated database to disconnect.
You should try to ensure that there are no other users connected to
a database when you terminate it. You can ask other users to disconnect
themselves, or you can kill their connection before terminating the
database.
2. Ask
the user who started the database to disconnect.
ERROR (1308):
invalid backup mode: incremental backup requires database in BACKUP
mode
Cause
You tried
to perform an incremental backup, but backup mode is set to OFF in dmconfig.ini.
Solution
Turn on
backup mode in dmconfig.ini. Please refer to the chapter Database
Backup, Recovery, and Restoration for more information on how to
turn on backup mode.
ERROR (1310):
journal full: command rolled back to internal savepoint
Cause
The journal
is full and your transaction has been rolled back to the last internal
savepoint taken by DBMaker.
Solution
Commit
or abort your transaction. If your transaction is very long, you may
want to increase the size of the journal file size to avoid another
journal full error. To resize a journal file you can do the following:
Terminate the database.
Increase your journal file size by setting DB_JNLSZ in dmconfig.ini
to a higher value.
Set the start mode to NEW JOURNAL by setting DB_SMODE to 2
Reset DB_SMODE to 1
The next
time you start the database you will be using the resized journal file.
ERROR (1316):
cannot start with NEW JOURNAL mode : database crashed
Cause
The database
has crashed, and you are trying to start it in NEW JOURNAL mode.
Solution
After a
database has crashed, you must restart it in NORMAL mode. Starting the
database in NORMAL mode will allow the database to perform crash recovery.
To change the start mode of the database, change DB_SMODE to 1 in dmconfig.ini,
and restart database.
ERROR (1317):
cannot start database : database crashed in NO JOURNAL mode
Cause
Your database
crashed while running in NO JOURNAL mode and you tried to restart the
database to perform crash recovery.
Solution
You cannot
perform crash recovery on a database that crashed in NO JOURNAL mode.
Use NEW JOURNAL mode to restart database. For detailed instructions,
please refer to the chapter Database Backup, Recovery, and Restoration.
ERROR (1318):
cannot find a valid backup status in archived journal files
Cause
DBMaker
cannot find a valid backup status in the archived journal files.
Solution
Find the
valid journal files of full backup for DBMaker to do restoration.
ERROR (1501):
cannot create socket
Cause
The Unix
sockets or Windows winsock service cannot create a new socket to allow
you to connect to the server.
Solution
Restart
the client-end computer. If this does not solve the problem, note the
return code of the error message and refer to your operating system
manuals for information on the Unix socket or Windows winsock socket()
function.
ERROR (1502):
cannot translate from hostname to IP address
Cause
The hostname
of the computer you are trying to connect to is not defined in /etc/hosts.
Solution
Add the
host name with the related IP address to the /etc/hosts file.
ERROR (1503):
Cannot connect to server
Cause
You try
to connect to a client/server database, but cannot connect to the server
because it is not powered on or the IP address you specified is invalid.
Solution
Start the
database at the server end or give the correct IP address.
ERROR (1504):
Network binding port error
Cause
There was
an error while trying to bind a local address to a network socket or
port number.
Solution
Restart
the client-end computer. If this does not solve the problem, note the
return code of the error message and refer to your operating system
documentation for information on the Unix sockets or Windows winsock
bind() function.
ERROR (1505):
Network listening error
Cause
There was
an error listening for connections on a network socket.
Solution
Restart
the client-end computer. If this does not solve the problem, note the
return code of the error message and refer to your operating system
documentation for information on the Unix sockets or Windows winsock
listen() function.
ERROR (1506):
timeout when connecting to server
Cause
This message
may occur in one of the following situations:
1. The
server has not been started yet.
2. The
port number specified in dmconfig.ini on client side is different from
the port number bound by the server.
Solution
1. Start
the database at the server side.
2. Give
the same port number on the client side that the server has bound on
the server side.
ERROR (1507):
cannot load winsock.dll
Cause
A client
application tried to connect to a server, but DBMaker could not find
the file winsock.dll.
Solution
Put the
file winsock.dll in your System directory.
ERROR (1508):
cannot initialize winsock.dll
Cause
A client
application wants to connect to a server and DBMaker finds that winsock.dll
is not compatible with windows network driver when it tries to initialize
the socket status.
Solution
1. In Windows
95 or NT, replace the current winsock.dll file with the one provided
with the operating system, and restart Windows.
2. In Windows
3.1, replace the current winsock.dll file with one compatible
with your network driver. Consult you network driver product documentation
to determine which winsock.dll files are compatible.
ERROR (1601):
no available page buffer in buffer pool
Cause
All memory
buffers have been allocated.
Solution
Enlarge
the value of DB_NBUFS in dmconfig.ini and restart the database.
ERROR(2102):
number of transactions exceeds setting in configuration file:
Cause
The number
of active transactions is larger than the value set by the keyword DB_NTRAN
in dmconfig.ini.
Solution
Terminate
the database and increase the value of DB_NTRAN.
ERROR (3001):
too many errors were found
Cause
You performed
a database consistency check and too many errors were found to repair.
Solution
Please
refer to the chapter Advanced Database Administration for more
information on database consistency checking.
ERROR (3002):
cannot continue checking because a serious error was found
Cause
You performed
a database consistency check and a serious error was found that cannot
be repaired.
Solution
Please
consult with DBMaker support personnel.
ERROR (8002):
keyword entry is required in configuration file
Cause
There is
no value specified for a keyword in the dmconfig.ini file and that keyword
has no default value.
Solution
Add the
keyword and value to dmconfig.ini.
ERROR (8003):
config value too long
Cause
The value
specified for a keyword in dmconfig.ini is too long.
Solution
Modify
the value of the keyword so it is within the range of DBMaker system
limits.
ERROR (8005):
configuration file entry format error or config keyword too long
Cause
The keyword
entry that you specified in dmconfig.ini is not in the correct format
or its length exceeds the maximum limit of 80 characters.
Solution
Modify
the keyword entry so it is within the range of DBMaker system
limits.
ERROR (8006):
config value is not an integer
Cause
The value
of a keyword specified in dmconfig.ini should be an integer.
Solution
Change
the value of the keyword in dmconfig.ini to an integer value.
ERROR (8007):
cannot find the specified database section in the configuration file
Cause
There is
no database section in the dmconfig.ini file for the database you want
to start or connect. There are two possible reasons:
1. The
database has not been created yet.
2. The
database section has been removed from dmconfig.ini.
Solution
1. Check
to ensure the name of the database you want to start or connect to is
valid. You must create a database before you can use that database name.
2. If the
database has already been created, you should add the database section
into dmconfig.ini. However, if any of the keywords relating to BLOB
or journal files were changed, you must write them back correctly or
you may fail to start or connect to the database.
ERROR (8008):
cannot create database section in configuration file
Cause
You tried
to create a database, but the dmconfig.ini file is write-protected.
Solution
Turn off
write-protection on the dmconfig.ini file and try to create the database
again.
ERROR (8009):
configuration file not exist for update or insert
Cause
DBMaker
tried to update or insert data into the dmconfig.ini file, but cannot
find the file in its search path.
Solution
Make sure
that the dmconfig.ini file exists in a directory in the search path.
ERROR (8010):
configuration file close failed
Cause
The dmconfig.ini
file was opened, but could not be closed for some reason.
Solution
This is
an operating system error. Check to ensure the file was not deleted,
moved, or write-protected while it was in use. If the file is okay,
try executing the command that caused the error again.
ERROR (8013):
I/O error creating file object directory
Cause
DBMaker
tried to create a new file object directory, but the path you specified
is invalid or does not exist.
Solution
Specify
a valid path when creating a new file object directory.
ERROR (8014):
no default directory for default user DBMaker
Cause
An error
occurred when you installed DBMaker.
Solution
Reinstall
DBMaker.
ERROR (8030):
cannot open temp file to backup configuration file
Cause
DBMaker
tried to back up dmconfig.ini, but does not have the right to create
files in the backup directory.
Solution
Make sure
that you have the right to create files in the backup directory.
ERROR (8031):
cannot find back up ID in backup history file
Cause
You are
trying to restore a database from a backup with Server Manager, but
Server Manager cannot find the backup ID in the history file because
the file was backed up manually.
Solution
Make sure
that you remember the relationship between the backup ID and the backup
file when you do manual backups so you can give the correct files to
Server Manager. Otherwise Server Manager may fail to properly restore
files from a backup.
ERROR (8040):
cannot move old backup history file to bak file
Cause
You don't
have the proper privileges to read the old backup history file or to
write to a .bak file.
Solution
Make sure
that you have the proper privileges to read or write the related files.
ERROR (8330):
building multiple index scan keys requires too much memory
Cause
The size
of the condition list specified is too large to build multiple index
scan keys.
e.g. SELECT
col1 FROM table1 WHERE col1 IN (1, 3,...,99999);
The number
of multiple index scan keys (1, 3, 5, .....,99999) exceeds the system
limitation of DBMaker.
Solution
Reduce
the size of the condition list for building multiple index scan keys.
ERROR (8332):
expression or predicate needs too large memory
Cause
The expression
or predicate needs too much memory to do comparison. It has exceeded
the system limitation of DBMaker.
Solution
Reduce
the size of the expression or predicate when doing conditional evaluation.
ERROR (8336):
character/binary data truncated during internal conversion
Cause
Data was
truncated while doing a conversion between character and binary data
themselves or each other (because they were different sizes).
Solution
Avoid transferring
data between character/binary fields of different lengths.
ERROR (8341):
function argument is out of range or invalid
Cause
You gave
an invalid argument value to a built-in function.
Solution
Call the
function again with valid argument values.
ERROR (10105):
out of memory, transaction aborted
Cause
A transaction
was aborted because your operating system has run out of memory.
Solution
Kill some
unused processes or add additional memory.
ERROR (10851):
invalid value in configuration file
Cause
There is
an invalid keyword value in the dmconfig.ini file.
Solution
Refer to
Appendix A for the valid parameter range of each keyword.
ERROR (11011):
error while access shared memory
Cause
There was
an error allocating or mapping shared memory.
Solution
Shut down
the database and restart it.
ERROR (11206):
cannot create/open a file
Cause
DBMaker
cannot locate files belonging to the database you want to connect to.
Solution
Make sure
the file exists and the path is correct in dmconfig.ini.
ERROR (11215):
cannot lock the database system file, create/start/connect database
failed
Cause
In the
Unix client/server model, you tried to restart a database that still
has at least one forked process running. This may occur after a client
application connects to a server process, causing the server process
to fork another copy of itself for the client application to use. The
shared memory allocated for the server was removed and the original
server process was killed, leaving the forked process in the system.
Solution
Kill the
server process that was forked to handle the client application and
restart the database.
ERROR (11311):
journal full: transaction has been aborted
Cause
Your current
transaction has been aborted because there are too many active transactions
and the journal has run out of free space. All operations in your aborted
transaction will be lost.
Solution
1. If your
system is in NONBACKUP mode, you should try to decrease the number of
operations in your transaction. Alternatively, you can resize the journal
file (see Error 1310 for information on how to do this).
2. If your
system is in BACKUP mode, you need to perform a full backup or an incremental
backup.
ERROR (11312):
no valid journal status block during crash recovery
Cause
You are
trying to recover a crashed database, but the journal files have no
valid journal status blocks.
Solution
Give DBMaker
a valid set of journal files so it can complete crash recovery. If you
do not have any valid journal files, crash recovery will fail.
ERROR (11313):
time in journal file status block is newer than current time
Cause
This message
may occur in one of the following situations:
1. Your
system time has been changed to a time earlier than the current time.
2. Your
database was created and used with the system time set in the future
and you have now set the system time to the correct time or your database
has been moved to a different system in a locale with a different time
and time zone.
Solution
1. Check
the system time to make sure it is set to the current time. If you consistently
have problems with your clock running slow or resetting to the earliest
possible system time, you may have a problem with your CMOS or CMOS
battery.
2. Wait
for the system time to exceed the time in the database file. If the
time period is too long, you can unload and recreate the database, or
you can use NEW JOURNAL mode to start the database. If you use NEW JOURNAL
mode to start the database, you must ensure that the database terminates
normally, and if the database is in BACKUP mode, you must do a full
backup after you start in NEW JOURNAL mode. See the chapter Database
Backup, Recovery, and Restoration for more details.
ERROR (11314):
too many invalid pages to recover database
Cause
DBMaker
was attempting to recover your database after a crash, but there were
too many invalid pages in the database to complete recovery. This error
may occur if crash recovery is performed using the wrong data file.
Solution
Ensure
DBMaker is using the correct data file to perform crash recovery. If
the correct data file is being used and you still receive this error,
you can try using a backed up data file, or you can use forced startup
mode. If you use a backed up data file, you will lose the data that
was entered from the time of the backup for all transactions that have
been flushed from the journal. If you still cannot get the database
to start, please consult with CASEMaker support personnel.
ERROR (11315):
invalid pages found during recovery
Cause
DBMaker
was attempting to recover your database after a crash and found an invalid
page in the database.
Solution
Ensure
DBMaker is using the correct data file to perform crash recovery. If
the correct data file is being used and you still receive this error,
you can try using a backed up data file, or you can use forced startup
mode. If you use a backed up data file, you will lose the data that
was entered from the time of the backup for all transactions that have
been flushed from the journal. If you still cannot get the database
to start, please consult with CASEMaker support personnel.
ERROR (11421):
deadlock, transaction rollback
Cause
Your transaction
caused a deadlock, and was aborted.
Solution
Submit
your transaction again after any other transactions that were involved
in the deadlock have completed
ERROR (20901):
database terminated
Cause
The database
you are using has been started by another user.
Solution
You may
restart the database if your privilege level is high enough, or consult
your System Administrator to determine why the database was terminated.
ERROR (20904):
invalid shared memory, shared memory may be allocated by another application
Cause
DBMaker
tried to access the shared memory allocated by the DCCA, but the contents
of the DCCA memory have been modified by another application program,
or there was an internal error when the DCCA memory was last accessed
by DBMaker.
Solution
Restart
the database.
ERROR (21012):
error while unmapping database shared memory
Cause
DBMaker
encountered an error while trying to free shared memory.
Solution
Restart
the database.
|
