11/7/24, 4:53 p.m. Document 1072014.
1
Copyright (c) 2024, Oracle. All rights reserved. Oracle Confidential.
E1: DB: JDE.LOG Error - The transaction log for database <database_name> is full - SQL
Server Database (Doc ID 1072014.1)
In this Document
Goal
Solution
References
APPLIES TO:
JD Edwards EnterpriseOne Tools - Version 8.97 and Prior and later
Generic (Platform Independent)
GOAL
Customer is trying to build a package from deployment server. The jde.log contains the following errors:
4248/7204 WRK:Starting jdeCallObject Fri Feb 26 19:10:37.508001 Jdbodbc.c8351
ODB0000164 - STMT:00 [42000][9002] [Microsoft][SQL Native Client][SQL Server]The transaction log for database
'PSPlan811' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in
sys.databases
4248/7204 WRK:Starting jdeCallObject Fri Feb 26 19:10:37.508002 Jdb_drvm.c1116
JDB9900401 - Failed to execute db request
or this error (for main database):
1020/2828 WRK:Starting jdeCallObject Wed Feb 24 20:33:53.781000 Jdbodbc.c8352
ODB0000164 - STMT:00 [42000][1101] [Microsoft][SQL Native Client][SQL Server]Could not allocate a new page for
database 'JDE_AB900' because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by
dropping objects in the filegroup, adding additional files to the file
1020/2828 WRK:Starting jdeCallObject Wed Feb 24 20:33:53.781001 Jdbodbc.c8352
ODB0000164 - STMT:01 [42000][1750] [Microsoft][SQL Native Client][SQL Server]Could not create constraint. See
previous errors.
1020/2828 WRK:Starting jdeCallObject Wed Feb 24 20:33:53.781002 Jdbodbc.c8352
ODB0000164 - STMT:02 [01000][3621] [Microsoft][SQL Native Client][SQL Server]The statement has been terminated.
SOLUTION
This is a database issue. The log or the database has reached the maximum allowed size. Turn on auto-growth and make
sure that the size is unlimited for both database and log.
The cause of the errors above is most likely to be one of the following two reasons:
A. (most common) The disk with your databases or the servers transaction logs is full
B. (less likely, but possible) The database has reached its limit for a data-file or a
transaction log (that is where it stores all the information needed to preserve data integrity
during operation failures)
Notes:
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=be3o17hxa_4&id=1072014.1 1/3
11/7/24, 4:53 p.m. Document 1072014.1
- If it says PRIMARY the problem is related to the database data file (*.mdf)
- If it says DEFAULT the problem is related to the database transaction log (*.ldf)
Step-by-step for A
If you are using MS SQL Desktop Edition (MSDE) please check that the drives where you have
installed MSDE and where your database(s) resides have sufficient space left.
If you are using a full MS SQL Server you will have to use the Enterprise Manager to determine
where your files are placed.
1. On the computer with the MS SQL server installed go to:
Start -> Programs -> Microsoft SQL Server -> Enterprise Manager
2. Navigate to the actual database, right-click it and select properties
3. Depending on your SQL server version you will have to select:
a. Files
b. or navigate to the tabs Data File and Transaction Log respectively
4. There is a list of file-locations (paths) for Data File and Transaction Log, check that the
disks to which these paths point have sufficient space left.
Sufficient space is:
* more than 50 megabyte for transaction logs
* can be several to many gigabytes for data files
Step-by-step for B
If it is a problem with the transaction log it can be solved as follows:
(Note: this step-by-step explanation assumes that you are not using MS SQL Desktop Edition)
1. On the computer with the MS SQL server installed go to:
Start -> Programs -> Microsoft SQL Server -> Enterprise Manager
2. Navigate to the actual database, right-click it and select properties
3. Depending on your SQL server version you will have to select:
a. Files
b. or navigate to the tabs Data File and Transaction Log respectively
4. Make sure that the maximum files-sizes are set to unlimited
5. Accept the changes (click ok) and close the properties dialog
6. Stop and then start the SQL Server
7. Close the Enterprise Manager
8. Restart the computer
Did you find this document helpful? If so, please provide your feedback and comments on this document in
MOS. Your feedback helps us help you.
To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or
start a discussion in the Configurable Network Computing - JDE1 Community.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=be3o17hxa_4&id=1072014.1 2/3
11/7/24, 4:53 p.m. Document 1072014.1
To look at upcoming or archived Advisor Webcasts, please see the Advisor Webcast JD Edwards EnterpriseOne
Schedule Document 1450327.1. If your topic is not currently scheduled, please suggest it.
Didn't find what you are looking for?
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=be3o17hxa_4&id=1072014.1 3/3
