i added a new mysql table and did a build-schema my config/schema.yml contains my new table
now when i run the build-model i get:
Some problems occurred when executing the task:
build-propel.xml:474:20: Duplicate table found: propel.
build-propel.xml:461:22: Execution of the target buildfile failed. Aborting.
If the exception message is not clear enough, read the output of the task for
more information
how on earth must i find the duplicate table??
please help?
thank you
I've had this problem before. It is due to any schema.xml files lying around in your config folder. Try deleting these and run the command again.
a duplicate schema.yml or generated-schema.xml exists somewhere in your plugins, rename it to schema.yml.back or delete it. reference
Related
Please advise. This SQLPlus call:
SQL > #dba_files_all
...is not working.
SP2-0310: unable to open file "dba_files_all.sql"
How can I resolve the error?
You need to provide the path of the file as string.
Put the path in double quotes and it will work.
For example:
#"C:\Users\Arpan Saini\Zions R2\Reports Statements and Notices\Patch\08312017_Patch_16.2.3.17\DB Scripts\snsp.sql";
I encountered this error when attempting to execute a file in the same folder as the calling function. In my example, this process:
Was executed in SQL Developer;
Has been a long-standing part of my system (moving a setup file with some settings and variable names through various folders; those folder names include the feature IDs and a short description);
Has worked fine in the past;
Did not require any pathing in my case because the files were in the same folder;
Failed on the most recent attempt with the error above (SP2-0310).
The issue in my situation was that the folder name in which it failed included a character (#) that was valid for a Windows file name, but confusing to SQL Developer.
1.Use absolute path:
/u01/app/oaracle/test.sql
2.Check the path to see if script exists:
ls -l /u01/app/oaracle/test.sql
Note that
SQL> #some_file.sql
means that sql app you are using will look for that using "absolute path" so if you want to use "relative path" use following format [add ?]
SQL> #?some_file.sql
else, use "full path" with first command.
All the answers so far imply that absolute paths are required. That aren't. Relative paths in sql is pretty universal in sql tools. Sometimes, you have to configure a lost default configuration such as in the case of SQLDeveloper as explained in this answer:
https://stackoverflow.com/a/24003529/442968
I just run into same error when I was trying to unlock oe schema.
While reading the error, I realized that when I run the following line:
>SQL #?/demo/schema/order_entry/oe_main.sql
The error returned a completely different path
SP2-0310: unable to open file "C:/app/USER/product/18.0.0/dbhomeXE/demo/schema/order_entry/oe_main.sql"
Thus I copied my sql file to the path specified by the error and everything worked. I recommend that you do the same. Check the path in the error and adjust accordingly.
Use absolute path or run sqlplus command from a shell/dos that points to the path of the script. Also, to use a masterscript, refer to subscripts with ##.
verify that your file has an extension .sql not .sql.txt
I am using sql 2012 SSIS process task to unzip my files but I am getting the following error
[Execute Process Task] Error:
In Executing "C:\Windows\System32\compact.exe" "x F:\Imports\RenLearn\'Roseville City School District'.zip -oF:\Imports\RenLearn\Roseville City School District" at "",
The process exit code was "1" while the expected was "0".
The two paths above are created as variables along with the path to . Any suggestions and thanks ahead of time.
I had the exact same problem and I realised that I had copied the .exe file in the same folder as the .zip files because this resolved my problem in BIDS, but in Data Tools it seems like necessary to do that.. sounds little weird, but it worked for me so perhaps it will for you as well. :-)
If you have set the "Working directory" property, you need to remove it to make the task work.
Remove the space in zip file name as the Execute process fails if the file contains special characters. Instead of spaces, use "_" and try it. Even the same issue I got later was sorted out by this approach.
I am getting these errors in flat file connection manager.
Error: [SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on Flat File Source returned error code 0xC0202091. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
I am reletively new to ssis and I am finding it quite hard to figure out the issue. Please let me know your views.
On your flat file connection properties - Look for the property "AlwaysCheckForRowDelimeters" - SET it to FALSE.
Hope that helps.
"An error occurred while skipping data rows" - I had this error in a package and found the problem was reading files inside a for loop. More files matched the criteria than intended, so a file with an invalid schema was also matched.
More generally I think this is related to either the file not matching the connection definition, I have also seen people online saying it is related to the flat file using a text qualifier (i.e. " in a csv) but having no closing quote.
I had this error today, and my package was looking for more files than existed based on the conditions of the for each loop. The text qualifier wasn't the issue causing this particular error.
near the Start button press drop-down menu arrow
choose package_name Debug Properties
than under Configuration Properties open Debugging
than under Debug Options choose Run64BitRuntime and turn it to False
I am getting the followinge error while cherry-picking a gerrit...does anyone have info on what this means and why would anyone see it?
error: addinfo_cache failed for path 'ROE/NAS/src/abc.c
Looks like this has something to do with the whitespace and EOL. I also got the same issue today and just used the git-->mergetool to resolve the issue based on the following thread - http://git.661346.n2.nabble.com/error-addinfo-cache-failed-during-merge-tp6840473p6840622.html.
The only cause of concern, I now see the entire file modified instead of just the two lines which were part of my cherry-pick changeset.
Run git stash before cherry-picking. It helped at least in my case.
when i am doing ant build, every time build got failed due to Unable to delete file xxxx.jarSAVE. But this file is not there in that folder. i am attaching build trace here. Can any one help me for the same.
BUILD FAILED
D:\2.4_BV_BuildArea\aiRES-Comp\Build.xml:162: The following error occurred while executing this line:
D:\2.4_BV_BuildArea\aiRES-Comp\Java\Build.xml:225: The following error occurred while executing this line:
D:\2.4_BV_BuildArea\aiRES-Comp\Java\src\com\ibsplc\iRes\tax\build.xml:127: Unable to delete file D:\2.4_BV_BuildArea\aiRES-Comp\Java\src\com\ibsplc\iRes\tax\dist\iRes_Tax_ejb.jarSAVE
ANT thinks that the name a file it it supposed to delete is iRes_Tax_ejbSAVE. But the actual name of the file which really exists and ANT is supposed to delete is iRes_Tax_ejb.jar
This means its a space issue. In some config or property file there is a whitespace between iRes_Tax_ejb.jar and SAVE is not being picked up.
search for the <delete> tag in all your build.xmls and you'll come to know which file is it picking the name iRes_Tax_ejb.jar to delete from.
Also search for the word SAVE in all your build.xmls
Then go and fix the space. This is tricky sometimes as when you see the text file, space might be visible, but ANT is not able to pick it up due to encoding issues. So you'll have to use the correct editor.