Neoview Messages Manual (R2.2)

Master Thread, Load Task-Specific Messages
SESSION PARAMETERS
Cause This message displays the inputs provided for the task currently executing. The
message contains:
• Task Name
• DB Object Name – is the name of the table being loaded
• Compress Data – indicates whether compression was used
• Data Format – indicates whether FIXED of DELIMINTED input data format
• Field Delimiter – is the field delimiter for DELIMITED data
• RowsToSkip – is the number of rows to skip
• Rowset Size – is rowset size for the insert
• Operation Type – type of load request (INSERT, INSERT-UPDATE, UPDATE-INSERT)
• Transaction Size – same as rowset size
• ExecutionParallelism – indicates whether the gelservers were started by partition or CPU
• LogSeverityLevel – logging level
• Character set conversion option – indicates whether character set conversion was selected
• Recovery Flag – indicates whether recover was enabled for the task
• Readers – shows the input files
• Writers – shows the IP address and port numbers for each of the writer threads
For example:
SESSION PARAMETERS
--------------------
DB Object Name : CAT.SCH.TABLE
Compress Data : false
Data Format : DELIM
Field Delimiter : ,
RowsToSkip : 0
Rowset Size : 1000
Operation Type : INSERT-UPDATE
Transaction Size : 1000
ExecutionParallelism : PARTITION
LogSeverityLevel : INFO
Character set conversion option : true
Recovery Flag : true
Readers :
---------
1. /home/testenv/data/data.dat
Writers :
---------
1. 192.168.10.1:1234
Recovery This is an informational message only. No corrective action is needed.
Failed to initialize reader metadata.
Cause The gelserver failed to initialize all the reader-related metadata. This failure can occur
if the format file supplied is corrupted or contains invalid data. Previous errors in the task
instance log file provide details about the error.
Recovery Check the task instance log for the specific error that caused the problem.
Failed to initialize writer metadata.
Cause The gelserver failed to initialize all the writer-related metadata. This failure can occur
if problems occur in receiving metadata from the gelserver process on the Neoview platform
or if metadata supplied is incorrect. Previous errors in the log provide details about the error.
378 Neoview Loader