Some parts in this document seems to be showing the old IFS Windows client
There are some trace debug services within the server environment. These are all integrated in the client debug console, but may be used even as stand-alone tools in the server environment (from SQL*Plus, Server Manager or other tools).
This is a system service within the Oracle environment. The package support buffering of text messages during execution of PL/SQL. After texts have been buffered by using Put_Line, the texts can after the execution be received by using Get_Line(s). The enabling of the buffering mechanism is made by using Enable and Disable. Please refer to Oracle documentation for details.
SQL> set serveroutput on (SQL*Plus only)
or
SQL> exec Dbms_Output.Enable (NULL)
This method enables the buffering mechanism and set size of the buffer in SGA to unlimited..
SQL> exec Dbms_Output.Put_Line (info_)
This method stores a text in the buffer. The parameter is overloaded for different parameter data types (VARCHAR2, NUMBER and DATE).
SQL> exec Dbms_Output.Get_Line (info_, status_)
This method fetches a text line from the buffer.
SQL> exec Dbms_Output.Get_Lines (info_, no_of_lines_)
This method fetches a multiple number of text lines from the buffer.
SQL> exec Client_SYS.Attr_To_Dbms_Output (attr_)
This method sends the given attribute string to Dbms_Output.Put_Line by separating the attribute names and values.
SQL> exec Event_SYS.Set_Event_Trace (1)
This method activates logging for usage of Event Registry in package Event_SYS. The trace output will appear when activating Event_SYS facilities such as Event Server actions based on decisions in the business logic layer and will also include timestamp information.
SQL> exec General_SYS.Set_Method_Trace (1)
This method activates logging for method calls. The trace output will appear when executing General_SYS.Init_Method and will also include timestamp information.
SQL> exec General_SYS.Put_Line (text_)
This method has identical functionality as for Dbms_Output.Put_Line, but include timestamp information as a suffix to the text.
SQL> exec Reference_SYS.Set_Reference_Trace (1)
This method activates logging for reference handling in package Reference_SYS. The trace output will appear when activating Reference_SYS facilities such as list of values, restricted references, cascade options and will also include timestamp information.
SQL> exec Report_SYS.Set_Report_Trace (1)
This method activates logging for report handling. The trace output will appear when using IFS/InfoServices such as ordering or printing reports and will also include timestamp information.
SQL> exec Trace_SYS.Set_Trace_Output (1)
This method activates logging by using system service Trace_SYS which support trace outputs with indented method calls. The trace output will appear only when using Trace_SYS in the existing business logic and will not include any timestamp information.
SQL> exec Transaction_SYS.Set_Transaction_Trace (1)
This method activates logging for ordering of background jobs and execution of dynamic PL/SQL package calls. The trace output will appear when using facilities in Transaction_SYS such as starting background jobs or when executing dynamic calls and will also include timestamp information.
The runtime debug console can be activated in a Foundation1-based application by pressing either:
("Alt Gr" might be excluded on some keyboards but is a simply substitution key for the conbination of "Ctrl" and "Alt", which might also be used)
The console shows trace output both from client and server. To add own messages from the client, use the Console object (see Public Interfaces - Console). To add server trace messages, use the techniques described above (Trace Services in Server).
The Console Setup window that appears when the console is activated is of container type. The information to view or tools to use is spread across a range of tabs.
Used for selecting what message types should appear in the console. The Oracle SQL Trace can be activated from here as well.
The "commit" and "rollback" statements placed in server code can be disabled from here. If any such statement is encountered during the execution, it will result in an error.
The console output can be placed in a window or in a file. The output file is named IFSCons.txt and placed in the directory the application was started in.
The "commit" and "rollback" statements placed in server code can be disabled from here. If any such statement is encountered during the execution, it will result in an error.
The services provided by the console are: initialization of all the packages in the database and refresh of the performance tables.
While the console is open, an additional debug tab is added to the window properties dialog. Containing information about data source properties and object relations.
The simulate functionality gives the opportunity to, in a development phase, simulate different runtime situations. Enter simulate parameter settings on this tab and then use the RMB menu upon the console window to toggle simulation modes.
Simulate slow network, should be used to simulate the application behavior when run on a slow network. Every database interaction will be delayed with a predefined delay time. Use this mode to find application performance bottlenecks caused by slow network. The delay time is configurable.
Simulate no security, is a basic but yet powerful feature which simply lets the developer to disable user server access, forcing the system to return FALSE for the standards security questions (IsDatabaseAvailable, IsViewAvailable, IsMethodAvailable...). Use this simulation mode find method and objects in the application that does not support or use the security mechanism correctly. The simulate no security mode have no configurable parameters. Start the console and toggle the mode on and off to test your application.
The info tab is containing useful information sources for development or configuration issues.
You can debug PL/SQL server code triggered by an action in the Centura client
by specifiying the listening Host & Port (default 4000).
The Host must start a JDPA (Java Platform Debugger Architecture) listener (found
in e.g. JDeveloper and PL/SQL Developer 6.1) in order to take over the debug control
for a session.
The "Client DB call" activity can contain either plain text as input or bind variables containing values. Double clicking on a "Client DB call" will open a dialog containing the statement. If the statement contains any bind variables, the names,IN/OUT values and Data Type will be listed for each bind variable is a separate section names "Bind Variables".
Hovering with the mouse over a cell should show a tooltip with the length of the cell. Convinient when trying to count the amount of characters in e.g. bind variables of the Data Type: String. Also, this might reveal characters that are not "visible" like space characters or field separators, as the length of a cell that looks empty is not NULL but a number.
Same as "Copy" with the difference that it also adds a "Dbms_Output Section" making it possible to receive an output trace in SQL/Plus.
Note: Depending on the client being used and running the statement, enabling of the output might differ. In SQL/Plus, the output is normally enabled by writing "Set serveroutput on". Once the output is enabled, paste the clipboard content and execute it. The output should appear at the end as in the example:
