How can I recreate the .atr file for a folder in OBIEE?
On the server, the catalog contains a directory, but its corresponding ATR file is missing.
As a result, the folder does not appear in the UI.
It was inadvertently deleted from the file system.
Can I reverse engineer the ATR using another ATR file, or does the Catalog Manager application have a utility to help restore it?
Instead of reverse-engineering the ATR file, let the Catalog rebuild it automatically by re-propagating folder permissions down from a higher folder level in the catalog.
After this, the missing folder (caused by the missing ATR file) will now appear in the BI Catalog.
Related
in a scheduler action i need to add files to FAL (to sys_file) which are already in the storage, uploaded via ftp. The normal way
storage->addFile(....)
which copies the file from a temporary folder to the file storage and adds it to the sys_file table does not work, because the file is already in the fileadmin directory. If i try i get this error message:
[ERROR] Cannot add a file that is already part of this storage.
How is it possible to add a file to sys_file which is already in fileadmin?
Thanks!
AFAIK addFile() is to be used for files uploaded from a local disk. If the files are already available on the remote server, you should go for addUploadedFile() instead.
This guide indicates that you need both a file directory and sql file to accomplish this, does anyone know a workaround?
https://localwp.com/help-docs/how-to-import-a-wordpress-site-into-local/
You can retrieve the backup archives from the starting-site folder. Within your WordPress folder, navigate to wp-content -> uploads -> backwpup-xxxxxx-backups. Open the archive. Inside you’ll find a .SQL file (local.sql).
I am using Oracle SQL Developer on MacOS and I am trying to save zip file into Blob field. I know how to load any other file type by clicking "Load" button and then selecting the file.
The problem is that when I select the zip file and click on Open, it does not select that file, but shows the me the content of zip file and then I can select only one file from that zip. This is not what I want, because I want to upload the whole zip.
Is there any setting in Oracle SQL Developer or any other way?
I do not have such problem on same table when using PLSQL Developer on Windows machine.
I have found out that when I have a zip file in a folder, then Oracle Sql Developer automatically shows also folders for this file, even if does not exist in reality on disk. The name of the folder and the file is the same including extension. Different is only the icon. If you select archive then loading to blob works ok. This is the behaviour on MacOS. I did not test it on other systems. On bottom picture is the example of folder containing only 2 zip files and how it looks when you try selecting file from that folder.
I have Unity 5.0.2f1. Firstly, I've successfully added GooglePlayGamesPlugin-0.9.20.unitypackage to my project. Then, I've tried to import GoogleMobileAds.unitypackage, but I got these errors:
Error importing folder (The pathName assets/plugins is already mapped to fce8a713f1e5a4cc4b9973d1ef630f31. But the meta data wants it to be mapped to cbde64d36fd994c458fffca9e931b232)
Error importing folder (The pathName assets/plugins/android is already mapped to b8f0d9a6a7f9240c981894807effddbc. But the meta data wants it to be mapped to 2f5d736f7c4cb4c1e80d0816d0e81625)
Error importing folder (The pathName assets/plugins/ios is already mapped to 6490bb8acab6f4f92b29615e7429b8df. But the meta data wants it to be mapped to da135550add3c4abca622bda5280d204)
How to resolve this?
First make a backup of your project and delete your metadata files in your asset project folder and childs.
Files with extension .meta
The easiest workaround I could come up with:
1. Within the Unity Editor, create a subfolder of the Assets folder, for instance called TEMP123.
2. Move the entire (other) content of the Assets folder to TEMP123.
3. Import your package.
4. Manually merge the content of TEMP123back to the Assets folder.
If you see these kinds of errors, reimport all the assets. This reprocesses the metadata and the error goes off.
I store all SSIS packages in Subversion repository, their configuration files as well. Configuration file almost always stored in the same folder where package is.
Problem is - SSIS seems to always store path to configuration file (the one saved in the package itself) as an absolute path.
When someone else checks out folder with the package in the location different from where I had on my development PC the configuration file is not detected (because my absolute path is stored and it doesn't exist on the other developer PC). So another developer has to remove this configuration and add it again from where it is now on his local hard drive. Then changed package is saved which will cause new version to be committed. When I get that version from SVN it will no longer match local path on my PC.
On a related note: another developer may want to change values in configuration file as well. If I later get the latest version of everything from SVN package will no longer work on my PC.
How do you work around these inconveniences?
Another solution is to save your configuration in a database with an environment variable as the first configuration to tell it what database to look in, that's what we do. We have scripts to populate ssisconfig for each server in our source control, but the package uses the actual table data for the database in the environment variable we are using.
Anyone who has heard my SQL Saturday presentations knows I don't much care for XML and this is one of the reasons. A trick to using XML configuration with varying locations is to use an environment variable (indirect configuration) to direct SSIS where it can look for that resource. The big, big downside to this approach is you'd generally need to create an environment variable for each set of configuration files or have a massive, honking .dtsconfig file which becomes painful for versioning.
The option I prefer if XML configuration is a must is that the "variableness" is removed. Developers and admins get together and everyone agrees "there will be a folder everywhere SSIS is done to hold configuration files and that location is X" and then it's just a matter of solving for X. At a previous job, we used D:\ssisdata\configs
#HLGEM's approach of a table for configurations is hands down my favorite approach to SSIS configuration (until you get to 2012 and their project deployment model where configuration is an entirely different animal)
I add a folder called "config" under my projects folder, add it to source control and mantain the config file in this folder. You can also add it to the SSIS project if you like.
I think its a good solution because everybody can have this folder and dowload the config file.
When the package is deployed it will read the config file from where you inform in the deployment manifest so this solution wont impact your development