I am using SQL Developer 4.0.0.13 to connect to Oracle 11g DB. Now I have a package that I need to update its body, I open the package body in the editor, do my change then
1) right click compile
2) right click compile for debug
3) save (ctrl+s)
For all the above the new changes are not saved... When I close the package body editor and open it again I don't find my changes. I tried closing the app and opening it again but nothing helped... Any ideas??? It seems it caches or something like that.
Update
I tried updating it from a peer's machine, which worked fine... It seems the problem is in my version... By the way it was working well before.
Update
Same happens if try to edit any database entity (function/procedure/...).
I figured out the reason, I just needed to put the schema name as a prefix to the package body ....... but the weird thing is that the SQL developer didn't complain, It just printed a message 'compiled'
Related
I tried to change the run through the folder without success.
'jupyter notebook --generate-config'
I signed up and changed the target address and still when I register in CMD jupyter notebook I ran a writing document
Suggestions for a solution please?
The problem was solved, the default file for html beats was assigned to the writer.
All that had to be done was:
My Computer> Properties> Search Bar: Set Default Apps> Search Explorer> In html extension redefine Explorer.
Hope I helped those who also encountered this stupid problem, long before they got into the core of Jupiter's code
I am trying to create a program using SQLite and have hit a dead end. I accidentally set the default program for opening .sqlite3 files as notepad and in my quest to fix it I think I broke something and now I'm getting error messages. Here's an example
sqlalchemy.exc.DatabaseError: (sqlite3.DatabaseError) file is not a database
[SQL: PRAGMA main.table_info("test")]
(Background on this error at: http://sqlalche.me/e/4xp6)
Visiting the link tells me that the error originates from the database driver and at this point I'm in over my head. I was hoping that completely uninstalling the program (maybe including removing all my computer's associations with .sqlite3 files?) might fix it. (I'm on Windows 10)
I've been at this for past 2 days and I'm getting weird errors from the store.
I'm trying to upload an update to my application "CoManga" via the store and it's not working out.
I'm working on Xamarin.Forms (UWP) and before making the appxbundle, I made sure and "associated my app with CoManga" from my developer account. All the information over there matches and should work fine without any issues.
Then I made a release of my UWP app, got the bundle and I tried to upload it to UWP.
It said that the Publisher info is different, so it couldn't upload. This is weird because I tried signing the bundle with my developer account itself.
Now, I tried building and signing the app bundle from app center. I got the appxbundle and that I tried to upload. But, since today it's giving me weird error :
The package comic_dl.UWP_2.1.15.0_ARM_x86_x64.appxbundle is taking a
long time to process. If this isn’t completed soon, try refreshing the
page, or remove the package and then upload it again. If you continue
to see this issue, contact support.
This package I tried to build from my system manually : https://drive.google.com/open?id=1VVvF6IB70R2DKNUgBJcqw-HryL1LIwgo
This is what I got from App center : https://drive.google.com/open?id=1o0sGKU2AKVgrcTelIoRFz7QCe8Do0WJ3
This is the Store ID : 9N81F8B5WW93
Can someone guide me what I might be doing wrong/missing something.
Thanks
EDIT Update : So, I followed the suggestion and contacted Microsoft's Team for help on this issue. After 3 months of multiple contacts, I was able to get someone to reply back and follow the case. Even they tried things on their end and I tried by deleting all the certificate files I had in my current project and tried to manually build the manifest file and then it worked. I'm not entirely sure what worked out in the end. But, you can try these things if you run into this issue.
1.) Clean your project.
2.) Delete .vs directory.
3.) Look for any certificate files in your project. Back them up somewhere else and then delete them from the project (Don't exclude from project, just delete them entirely). Clean and rebuild your solution.
4.) Check if the application is already installed on your system (When you debug, VS will install your UWP app on your machine to run it). If it's installed, uninstall it completely.
5.) Make a backup of your manifest file and try to create a new manifest file.
These are the links I received from Microsoft Help:
PFN and package publisher name must match values here: https://partner.microsoft.com/en-us/dashboard/products/{YourAppID}/identity
Update manually: https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/how-to-create-a-package-manifest-manually
Update in VS: https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/generate-package-manifest
If these values were pulled from test certificate, partner needs to update their test cert: https://learn.microsoft.com/en-us/windows/msix/package/create-certificate-package-signing
I think this problem is not caused by anything code related, but rather it is a problem on the Store side. I would suggest contacting the Store support, they should be able to investigate if there is something wrong with your app package or the problem is on their side.
For support go to the official website, click the Contact Us tab and fill out the form accordingly.
The team should be able to advise even for the first error with different publisher info. If your app was always associated with the same account, there is no reason it should give you such an error message.
I had this issue gazillion of times. It is so frustrating. That error message isn't useful at all.
Anyway - I think it is something in Package.appxmanifest, something in Identity tag.
Retrieving some necessary info from store helped me.
Click right on your project -> Publish -> Associate App with the Store. This will update Package Display Name,Package Name,Publisher ID,Publisher Display Name and Version with correct values (within Package.appxmanifes).
Also be careful with version number. The last from numbers must be zero. 1.1.1.0 is fine, while 1.1.1.1 is not.
I created a worksheet yesterday. I have not made any changes to the configurations but today my graph is not being displayed.
However, if I hover over the worksheet name it shows me a preview of the graph I have created.
How do I make it show in the main window?
This is what solved the problemm, after speaking to Tableau support:
ODBC drivers (what I was using to connect to my database) are possible to use but not supported by Tableau.
Changing to a Microsoft SQL Server Driver solved the problem. Drivers can be found here:
https://www.tableau.com/support/drivers
Please check if your data is still available.. The Preview is coming from a cache of the workbook..
I have just experienced this behavior. The problem, in my case, was that I had built a "Set" that required a connection to the Tableau Server, and that connection had not been made when I opened the workbook.
Check to make sure that you are signed in to your Tableau Server from your workbook.
If that is not the problem, check each of your filters. Remove them and add them back, one by one. After the problem filter is removed, the worksheet will render normally. Then it is just a matter of fixing the filter.
I've been using meteorjs for quite a while now on linux. But when I installed using the relatively new windows installer, I saw that the most basic example doesn't work on properly on my computer - win7.
The example is at: https://www.meteor.com/try/4
which runs perfectly on my ububtu, but on my windows - I see that no information is inserted into the db and all changes I make (add new "tasks") are only local to that page, and other tabs I opened were also local, and there was no "reactivity" (no information was shared between different pages).
I tried to troubleshoot it in some ways:
I made sure that MONGO_URL is not set, and then I set MONGO_URL to another db, and saw that even though that db reported "connection accepted", the oplog nor the collection updated (tasks) have any new information.
Tried different kinds of browsers (chrome, firefox). Both are latest in version.
See no errors in chrome console.
I am assuming that all writes are made to minimongo, which doesn't pass them on.
Is this somehow a known issue?
Any suggestions?
A few things you can try:
uninstall meteor & any separate instance of mongo (including cmd aliases). download a fresh copy & install. Create a new project in a new folder. If the DB had some weird bugged lock on it, this is sure to fix it.
download robomongo (or use meteor mongo) to insert a new doc & see if it sticks. If it does, you know mongo isn't the problem.
Check that autopublish and insecure are installed. If they are, when you complete step 2 you should see a new doc in the app. If you do, then the DB can communicate to the app, so the problem has to be with the client-side saving to DB. Try a meteor method instead of a direct insert. If you don't see a new doc, then the data from the DB can't reach your client, which means your firewall (yes, it can screw up localhost requests, too) is to blame. Turn it off, make sure ports 3000 & 3001 (mongo) are allowed full access & that it doesn't do anything wonky with websockets.
I would try re-installing Visual Studio 2012 and Python 2.6/2.7, then re-installing Node and then Meteor.