LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: snbkumar

Hi Team,

While executing a db node (for update) through brg manually it works. But the same, when deployed as brx is failing with below error.

This is the first time I am facing this issue. Kindly me know about this.

Error executing statement: begin
update tablename set error_msg=null where status = 'STATUS';
end;. On connection: APPS@OIC. ORA-06550: line 1, column 7:
PLS-00103: Encountered the symbol "" when expecting one of the following:

begin case declare exit for goto if loop mod null pragma
raise return select update while with <an identifier>
<a double-quoted delimited-identifier> <a bind variable> <<
close current delete fetch lock insert open rollback
savepoint set sql execute commit forall merge pipe
The symbol "" was ignored.
ORA-06550: line 2, column 79:
PLS-00103: Encountered the symbol "" when expecting one of the following:

begin case declare end exception exit for goto if loop mod
null pragma raise return select update while with
<an identifier> <a double-quoted delimited-id
.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: rboccuzzi

Can you please post a copy of the node, and any parameters you used to configure it (run time parameters used for the brx would be helpful. Any sample data you could create in a Static Data node to exhibit input data would be helpful as well. It isn't clear from the above what the issue is, there isn't enough detail; I suspect there is a problem with the run parameter you are giving when you run in BRE vs. the one you might be giving when you run as a brx.


Cheers
Rich

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: snbkumar

Thanks Rich. I will check the Run parameters.
The issue was resolved when we opened the brg in a different machine, saved as brx and executed in server. Not sure how it got resolved though!

The error logs do not provide a great deal of details. Is there a debugging/error log walkthrough methodology that we need to follow for common errors? Can you share a debugging/error log document?

Regards,
Bharath

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: rboccuzzi

We don't have a debugging/error log guide, but we do have a number of logs to check. There is the server log and controller log which are stored in the log directory, and the standard error when you start the server (not generally much there), and the standard error when you start the controller (could be useful info there). There is also the brdlog which can be requested of the controller with a command line switch, which is a log in the format that can be read by the brdViewer and also read into the LAE by a Brd File node. Additionally, if you run the controller on the command line, you can pass a "-h" to see some of the controller options. The "--debug" and "--verbose" options are probably what you are looking for, and can potentially give more useful information to standard error as well.

Cheers
Rich

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: snbkumar

Thanks Rich.
1. Server and Controller log: They show an entry like below which is not easily understandable. Is there a way for users to understand it (with some help) or is it only for Lavastorm technicians?
<logEvent timestamp="1366351928604" level="WARN">
<message xsi:type="rawMessage"><![CDATA[Error while writing to output: java.lang.RuntimeException - Unhandled node done state: class class com.lavastorm.brain.graph.Node$State

2. brdlog which can be requested of the controller: (filename: controller.log.brd)
I have attached a sample log that I got. Please check if this is what you referred to. Also would like you to show me a way to understand that.

3. Running from command line:
Please can you list the commands (like laeController) and their options possibly in a document?

<<unable to attach controller log file. throws error#2028>>

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: rboccuzzi

Bharath, we are in the process of changing over our logs to a new format and getting a new log viewer up and running. While there isn't a standard way to view the server logs right now for the user, attached here is a bat that should work, with minor tweaks possibly needed for your specific paths. This should allow you to open up those XML logs and view them in a nicer format, with some filtering (you can right click on the cell and choose the filter option to create filters based on that entry).

For the BrdLog, the basic format is:

• Id - this is generally the node handle, a unique identifier of the node. You can search for these in BRE as well, in the find dialog.
• DisplayName - A somewhat encoded qualified name of the node, full path through the graph
• Action - Graph Started, Node Started, Node Processing, Node Completed, Node Completed with Errors, Graph Completed, Graph Completed with Errors, and I might have missed one, but you get the idea
• Date - Date the action occurred
• Time - Time the action occurred
• Status - any free text that can additionally describe the event
• NumberOfInputs - number of inputs on the node - I think only populated on Node Starting/Node Completed
• NumberOfOutputs - same as above, but for node outputs
• Inputs - 1 line for each input (so newline separated) with for each input, a colon separated set of facts: <inputName>:<numberOfRecords>. This will be present on the node started and node completed line
  
• Outputs - 1 line for each output (so newline separated) with for each output, a colon separated set of facts: <outputName>:<numberOfRecords>:<numberOfBytes>. This will be present on the node started with only the output name, but be fully populated on the Node Complete line.
  

Both the Inputs and Outputs information may be missing (partially or completely) when the node is streaming.


For the server commands, those are generally enterprise server operations, and you should talk to your enterprise support contact to get the right information for your system.

Cheers
Rich


Attachments:
ViewLog.zip