Commit 3139bdde authored by Giuseppe Lo Presti's avatar Giuseppe Lo Presti
Browse files

Fixed log messages (related to bug #101856)

parent a7ee7fd8
......@@ -248,7 +248,7 @@ AS
RECALL_FAILING CONSTANT VARCHAR2(2048) := 'Failing Recall(s)';
RECALL_FS_NOT_FOUND CONSTANT VARCHAR2(2048) := 'bestFileSystemForRecall could not find a suitable destination for this recall';
RECALL_LOOPING_ON_LOCK CONSTANT VARCHAR2(2048) := 'Giving up with recall as we are looping on locked file(s)';
RECALL_NOT_FOUND CONSTANT VARCHAR2(2048) := 'setBulkFileRecallResult: unable to identify recall, giving up';
RECALL_NOT_FOUND CONSTANT VARCHAR2(2048) := 'Unable to identify recall, giving up';
RECALL_INVALID_PATH CONSTANT VARCHAR2(2048) := 'setFileRecalled: unable to parse input path, giving up';
RECALL_COMPLETED_DB CONSTANT VARCHAR2(2048) := 'setFileRecalled: db updates after full recall completed';
RECALL_FILE_OVERWRITTEN CONSTANT VARCHAR2(2048) := 'setFileRecalled: file was overwritten during recall, restarting from scratch or skipping repack';
......
......@@ -608,7 +608,7 @@ BEGIN
-- recall, thus we pick the first one as "the" responsible. The only consequence is
-- that it's uid/gid will be used for the DiskCopy creation
EXCEPTION WHEN NO_DATA_FOUND THEN
-- log "setFileRecalled : unable to identify Recall. giving up"
-- log "Unable to identify Recall. giving up"
logToDLF(inReqId, dlf.LVL_ERROR, dlf.RECALL_NOT_FOUND, varFileId, varNsHost, 'tapegatewayd',
'mountTransactionId=' || TO_CHAR(inMountTransactionId) ||
' fseq=' || TO_CHAR(inFseq) || ' filePath=' || inFilePath || ' ' || inLogContext);
......@@ -1953,7 +1953,7 @@ BEGIN
AND nsHost = varNsHost
FOR UPDATE;
EXCEPTION WHEN NO_DATA_FOUND THEN
-- log "setBulkFileRecallResult : unable to identify Recall. giving up"
-- log "Unable to identify Recall. giving up"
logToDLF(varReqId, dlf.LVL_ERROR, dlf.RECALL_NOT_FOUND, inFileIds(i), varNsHost, 'tapegatewayd',
'mountTransactionId=' || TO_CHAR(inMountTrId) || ' TPVID=' || varVID ||
' fseq=' || TO_CHAR(inFseqs(i)) || ' filePath=' || inFilePaths(i) || ' ' || inLogContext);
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment