Top
Systemwalker Desktop Keeper Troubleshooting Guide
FUJITSU Software

4.1 Troubles Relating to Assets Backup

1. After backing up data using backup command, the command log is not backed up.


Target Version/Edition

BE V12.0L10

BE V12.0L20

BE V13.0.0

BE V13.2.0

BE V13.3.0

V14.0.0/V14.0.1

SE V12.0L20

SE V13.0.0

SE V13.2.0

SE V13.2.1

SE V13.3.0

V14.1.0

V14.2.0


Cause

Command prompt operation log has not been evacuated through backup command.


[Resolution]

Perform backup operation by referring to the following manual. In version V13.0.0 or later, the command log is already the target of collection of backup command.

[Refer to Operation Manual]

4.1 Assets Backup/Restoration in Systemwalker Desktop Keeper Importing Guidance
Table of File Backup/Restoration

[Data of Backup]

All data under the folder PromptLog


2. The executed backup command is ended due to error.


Target Version/Edition

BE V12.0L10

BE V12.0L20

BE V13.0.0

BE V13.2.0

BE V13.3.0

V14.0.0/V14.0.1

SE V12.0L20

SE V13.0.0

SE V13.2.0

SE V13.2.1

SE V13.3.0

V14.1.0

V14.2.0


Error message

The following information will be displayed in the event log.

"qdg12148e: Serious error has been detected in the execution of SQL statements:'JYP5007E RDBII memory of server space is insufficient.' (System name= SWDTK)."
"qdg12102u:RDBII local memory in space is insufficient (System name=SWDTK)"

Cause

There are too many cases of logs in backup at one time, which causes insufficiency in memory.


[Resolution]

Shorten the period of backup and perform backup again.


3. The executed log deletion process has ended due to error.


Target Version/Edition

BE V12.0L10

BE V12.0L20

BE V13.0.0

BE V13.2.0

BE V13.3.0

V14.0.0/V14.0.1

SE V12.0L20

SE V13.0.0

SE V13.2.0

SE V13.2.1

SE V13.3.0

V14.1.0

V14.2.0


Error message

The following information will be displayed in the event log.

"Error: 9002, level: 17, status: 6 log files in database 'DTKDB' is already full. Back up the database transaction logs in order to release the log space."

Cause

It is likely that logs cannot be deleted due to insufficient of transaction capacity of database.


[Resolution]

Back up the transaction log space according to the following procedure.

  1. From the start menu, start [Microsoft SQL Server] - [Enterprise Manager].

  2. From the tree on the left, select [console root] - [Microsoft SQL Servers] - [SQL Server Group] - [(Local) (Windows NT)] - [Database] - [DTKDB (Database Name of Desktop Keeper)], and right-click to select "Database Backup".

  3. Perform the following settings in the [General] tab.

    • [Database]: Specify [DTKDB].

    • [Backup]: Specify [Transaction Log].

    • [End at]: Specify the file name of backup transaction log.

  4. Select [Delete Inactive Entries from Transaction Logs] in the [Options] tab.

  5. Click [OK] to backup the transaction logs.

*Refer to the Manual of the SQL Server for detailed procedure.