Hi I am trying to load data using ODI where my source is flat files and target is Hyperion Essbase but it is getting failed and if I try to see the ODI Log and Error files they are empty.
Can anyone help me regarding this issue.
Thanks in advance.
The best way to debug an ODI job is to go in the Operator navigator in ODI Studio. There you will see the result of the execution, with more or less details depending on the log level you choose at execution time. The higher the log level is, the more information you will have.
The log files in ODI Studio only contains errors encountered by the GUI while designing your jobs, it doesn't give much information about the runtime.
Related
I'm using two laptops and stored my C# code in OneDrive.
I am aware that sharing code via OneDrive is not be the best approach, but that's what I'm dealing with now.
I noticed that on laptop 1 I have to define the following path to the data file (mdf):
C:\Users\ Diet\OneDrive\Personal\VisualStudio2019\Repos\project\project\App_Data\data.mdf
On laptop 2, the path is different because the user I'm logged in with has a different name (or at least that's what I believe is the cause)
C:\Users\ Dieter\OneDrive\Personal\VisualStudio2019\Repos\project\project\App_Data\data.mdf
Updating this in the Web.config fixed the connection to the database, BUT building the solution still returns an error, also related to a cloud operation, hence why I think it is caused by the path in OneDrive...
The error message:
CSC : error CS0041: Unexpected error writing debug information -- 'The cloud operation was unsuccessful.
I welcome your insights. Thank you for helping me out.
I have my projects stored in OneDrive and had this same issue. The fix was to set the entire Project folder contents to "Always keep on this device".
Seems that building the solution in VS was attempting to write to files that were not cached locally from OneDrive. As soon as I changed the setting, the build worked!
I was also storing my project on OneDrive, got the same error after installing a new ssd.
Rebuilding the solution was enough for me.
I want to write to whole execution process of a Job to a text file in Talend Open Studio 7.3 because in Enterprise edition it is already logged but I am not sure where to find the execution log in Talend Open Studio
so I had thought of writing the execution of the job to a Text file
Can anyone please guide me how to do it
Please follow below process to get the logs of the job in a file.
Select the job
Select Stats & Logs in the left pannel of the same window
Uncheck Use Project Settings if checked
Select the type of log you need (tStatCatcher/ tLogCatcher/tFlowMeterCatcher). You can select all three as well
Provide path of the file and file names
If you need detailed logs, you can also have tJava and customize your logs and direct it to a file
I added a build step for my project in teamcity which consists on using the plugin Parasoft Findings to publish an XML report of all the code violations. the problem is that teamcity is failing to parse XML report. It says there is an unexpected report format and to see log (which I couldn't find).
I already checked the report location pattern which is right. I don't use SOAtest but C++ test so I only put "Parasof analyzers 10.x" for the report type
I'm sorry but you did not provide any additional details regarding your question and it's hard to help you.
Please, provide:
error message
your configuration of build step and version of TeamCity and C++test
command line used to start C++test ( if you are using variables,
replace variables with real values used in your run)
By log I think, you should check your build step log, and provide us the right content.
You can find such logs on two different ways:
You can download it by clicking "Download full build log" on build
log page (Recommended).
Try to find the raw output from the build agent by looking in the
agents logs directory, for example in
c:\TeamCity_dir_agent\logs\teamcity-build.log
Following article from JetBrains' TeamCity manual might good point to start
Edit:
Parasoft updated the plugin which fixed the issue:
https://plugins.jetbrains.com/plugin/9949-parasoft-findings
I have the same issue. Error messages in build log:
Unexpected report format: <path-to>\report.xml. See log for details.
Failed to parse XML report
Failed to parse XML report
Step test results (Parasoft Findings) failed
teamcity-agent.log and teamcity-build.log are having no entries within this build step because there is no piece of code which would write that into during this error case.
Edit/Workaround:
In the report the node <ExecutedTestsDetails> must be below the node <Exec>. The node still has the right indendation but it is at the same level as <Exec>. The xsl of TeamCity Plugin works perfectly if you fix the report xml manually.
To make it work you can add the Build Feature "File Content Replacer" like that:
Regex: (?s)(<ExecutedTestsDetails.*?<\/ExecutedTestsDetails>).*?(<Exec.*?>)
Replace with: $2 $1
How do we attach a sql query such as join query to an existing gdb process in eclipse? Whenever I try to fork the given process using debug configurations in eclipse, which is a shared library , I am getting the following error:
No source available for "__kernel_vsyscall() at 0xb729c424"
Also, whenever I set break points in a specific program in eclipse, control goes to main.c and finally the process never comes back to the actual program.
Is there any way that the process be constrained only to my specific program?
how do we attach a sql query such as join query to an existing gdb process in eclipse
Um, what?
Are you attempting to debug a PostgreSQL server backend? If so, see the PostgreSQL wiki page that provides lots of details on the topic.
Whenever I try to fork the given process using debug configurations in eclipse, which is a shared library
What is a shared library? Eclipse isn't. PostgreSQL isn't. So what's the shared library here?
Are you trying to debug a PostgreSQL extension? If so, see the above link for details on attaching to a PostgreSQL server backend.
No source available for "__kernel_vsyscall() at 0xb729c424"
That's normal. It's just telling you that there's no source code on record for the __kernel_vsyscall call that's the entrypoint into syscalls in linux-gate.so via glibc when using sysenter.
The stack below it should be more informative. Get a backtrace, then look at the lower stack frames.
See:
What is __kernel_vsyscall?
Having trouble finding the method __kernel_vsyscall within the Linux kernel
http://www.trilithium.com/johan/2005/08/linux-gate/
Your "also" is really a separate question, and it's pretty hard to answer it usefully with the total lack of information provided. Try posting a new, more detailed question on just that topic. Specify how you compiled the program, set it up for debugging, how you're running it, where you're trying to set breakpoints, etc.
In Eclipse(version 3.6.2.M201102101200/Helios service release 2). I am getting a strange error when I run a large Java project called ACE toolkit. Below is a picture:
What are possible reasons it would do this?
can it be that Java runtime version is incompatible? The project was built for Java 1.5, but I have 1.6 running.
I appreciate any tips or advice.
There could be any number of reasons for eclipse crashing, from insufficient memory to a misbehaving plugin. The first place to start troubleshooting would be the C:\path\to\your\workspace\.metadata\.log file. You might find something helpful if you examine the end of this file soon after eclipse crashes.
From the documentation:
Eclipse has a log file where problems are recorded and usually this is the first thing that an Eclipse developer asks for when you report a problem. The log file can be found in a couple of places:
Workspace log - This is the most common location for the log file, It is stored in your workspace in the meta-data directory. Check out
workspace/.metadata/.log.
Configuration log - Sometimes information is recored in the configuration log file instead of the workspace log. (especially if
the workspace hasn't been created yet, there isn't one, or it cannot
be created) Check your configuration area for a configuration log
file. (configuration/.log)
Startup - Occasionally problems happen in the system really early before there is a workspace and before there is a configuration area.
This means that there is nowhere to write the log file so information
is written to the console, See the notes below on running with a
console to get these messages.