ODBC Connector, ODBC Enterprise Stage, ODBC Stage

-
Use ODBC trace when a problem is encountered with a component that uses ODBC to get at data sources. This includes the following components:
  • ODBC Connector (DataStage Parallel Jobs)
  • ODBC Enterprise Stage (DataStage Parallel Jobs)
  • ODBC Stage (DataStage Server Jobs)
  • Information Analyzer
Since collection of ODBC trace can affect performance, enable ODBC trace before you re-run a job or repeat a task. Disable ODBC trace as soon as possible.

Problems with metadata import in Information Analyzer

If you are collecting ODBC trace because of problems with metadata import in Information Analyzer, restart the ASB Agent service after enabling or disabling the trace.  To do so, follow these instructions:


Windows
Command
Description
Click on Control Panel > Administrative Tools > Services.Find the ASB Agent service and click Stop.
To restart the ASB Agent, click Start.
To restart the ASB Agent, after enabling or disabling the trace
 AIX, Solarix, Linux, or HP-UX
Command
Collects
Log on as rootcd <InformationServer>/ASBNode/binTo stop the ASB Agent, type:   ./NodeAgents.sh stopTo start the ASB Agent, type:   ./NodeAgents.sh startTo restart the ASB Agent, type:   ./NodeAgents.sh restart 
Generate the ODBC Trace
Windows
Command
Description
  1. Click on  Control Panel >Administrative Tools > ODBC Data Source Administrator
  2. Select the Tracing tab
  3. Specify a file name in the Log File Path
  4. Click Start Tracing Now
  5. Execute the DataStage job or perform the task that requires tracing
  6. Click Stop Tracing Now
  7. Collect the trace file from the specified location
Generate and collect the ODBC trace
 AIX, Solarix, Linux, or HP-UX
Command
Description
  1. Log on as a DataStage administrator (for example, dsadm)
  2. cd $DSHOME
  3. Edit the .odbc.ini file
  4. Locate the [ODBC] section in .odbc.ini, which is typically at the bottom of the file.
    Modify the following properties to enable tracing:    Trace=1
    TraceFile=Trace file location and name (for example, /tmp/odbctrace.txt)
  5. Execute the DataStage job or perform the task that requires tracing
  6. Edit .odbc.ini again, and set Trace=0
  7. Collect the trace file from the specified location
Generate and collect the ODBC trace

Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more