Need Solution for the below error. I have dump file to restore in a database. But got a error during import.
IMP-00002: failed to open C:\oracle\product\10.2.0\NEFT_IFSC.dmp for read
Import file: EXPDAT.DMP >
There are lots of things it could be: file path is wrong, file is corrupt, file is too big, permissions on the directory, file name is wrong, and so on.
You may find it helpful to run your import using a parameter file. Not only will that save you some typing if you end up re-running this several times, it will give you the possibility to review what you're about to submit. Find out more.
Also you can set the SHOW=Y parameter to validate the contents of the file.
Related
i try to import images product in magento 2 with csv file. I use import options in magento admin (System > Data Transfer > Import) but i get this error.
My csv file have this columns
sku,product_type,attribute_set_code,name,price,base_image,base_image_label,small_image,small_image_label,thumbnail_image,thumbnail_image_label,additional_images
thanks
Hi, i find error in csv field but now i got permissions error
i use sudo chmod 777 -R va/import/images/ but doesnt work
Did you find something in the logs?
Also, what if you try the import without images? (Just for testing, to be sure if the data or the files are the problems)
I am trying to write a script that automates opatch, but before I get into the actual scripting I want to test the commands directly through the command prompt. My oracle home is C:\oracle\Middleware, and my patch 23094292 folder is located in the Middleware folder. Here are the commands I am using to apply the patch:
cd C:\oracle\Middleware\23094292
C:\oracle\Middleware\OPatch\opatch apply
When I run the latter command I get this:
ZOP-51: The patch location is not valid for apply, because it doesn't have correct metadata, or it points to a patch directory.
Argument(s) Error... Patch location is not valid for apply
Please check the arguments and try again.
OPatch failed with error code = 135
Shouldn't oracle home be the valid patch location? I am not too familiar with Oracle's product's, so I'm not certain. Please let me know if I can provide any further information. Any help explaining what I am doing wrong would be greatly appreciated.
You're missing a directory in the 23094292 directory. There should be two directories in there, "files" and "etc". And then there should be a "README.txt" file there as well.
Edit: I'd just suggest removing the 23094292 directory and unzipping the zip file again, or re-download it if that doesn't work.
With pylint, I'm getting an E0611 error on an import when I know the file exists and the script runs fine. Suggestions? I annotated the image below with the error.
Try this:
In VS Code Preferences > Settings, change the "python.linting.pylintPath" to the virtual env path "/bin/pylint"
https://github.com/Microsoft/vscode-docs/blob/master/docs/python/linting.md
Removing all ignored files (in the __pycache__-folder, etc.) using the command git clean -dfx fixed the issue for me. (Warning: Ensure you do not have any important git-ignored files which you want to keep before executing this command.)
I'm trying to implement one of the answers to this question. However, I haven't been successful because when I run
> sphinx-autogen -o generated *.rst
I get the errors
Failed to import 'MyMod.X': no module named MyMod.X
Failed to import 'MyMod.Y': no module named MyMod.Y
Failed to import 'MyMod.Z': no module named MyMod.Z
Within my .rst files, there is one with the line:
.. automodule:: MyMod.X
(and similarly for MyMod.Y and MyMod.Z).
I'm running this within a subdirectory docs. In the parent directory containing docs, there is also a subdirectory MyMod which contains __init__.py, X.py, Y.py, and Z.py. The conf.py file within docs has the line sys.path.insert(0, os.path.abspath('../')) immediately after import sys.
The closest related question I can find is this, but the answers there seem to suggest that it is solved by inserting '../' into the path, which I had already done. Also, sphinx-autobuild can find these modules happily, so I don't think this is the issue.
Interestingly, changing the line in my .rst file to be .. automodule:: ../MyMod.X gets rid of the error message, though nothing seems to be generated in the directory I expect, and I then get error messages in sphinx-autobuild.
How can I get sphinx-autogen to read in these modules?
if anyone else has a better answer, or an explanation for this please post it, but here is what I learned about my question
Although sphinx-autogen gives error messages, in the case that I was looking at, the files I was trying to get it to create were still created. While it could not find the modules (and indeed, they were functions, not modules, so it's not a surprise that it couldn't), it still produced the expected output.
I'm trying to use the magmi extension to import bulk categories/products, but when I try to import my .csv file I get this error:
---- TRACE : 1 -----
---- DATE : 2015-04-24 11:24:36 ------
************************************
not found
*************************************
/plugins/base/datasources/csv/magmi_csvdatasource.php:121 - Magmi_CSVReader->checkCSV
----------------------------------------
Is this a known issue? and did someone find a fix yet?
I just had this problem. Turns out that "Configurable Item processor v1.3.7a" was checked and by unchecking it, the problem went away. But I do need this option so after a bit of troubleshooting, it was a mistake in my column name. I was trying to use "drop-down" but it should have been "drop_down".
This mysterious error probably means you have a syntax error in your CSV file.
I like the MAGMI importer. It is a very versatile and powerful tool.
I think the error you are getting is due to this line of code:
file: magmi/inc/magmi_csvreader.php
class: Magmi_CSVReader
function: checkCSV
throw new Magmi_CSVException("{$this->_filename} not found");
And the error message you get suggests the filename is an empty string so you just see 'not found'.
Double check the way you are setting the CSV filename and saving the MAGMI config. For example, it is possible that the config file cannot be saved due to permission restrictions. After you save the MAGMI config you should be able to see the filename and path to your CSV file in the MAGMI configuration file:
file:magmi/conf/Magmi_CSVDataSource.conf
[Magmi_CSVDataSource]
CSV:importmode = "local"
CSV:basedir = "var/import"
CSV:filename = "...SOME_PATH.../var/import/your-upload-file.csv"
And also check that the CSV file exists and is readable.
If you can't spot the problem please give more details about how your are running MAGMI and where you are storing the CSV file.