While Using Explain Plan option in SQL Developer, getting below error (mentioned in
screenshot).
There is no uncommitted transaction in the session.
I am getting this error even when first time opening SQL Developer.
SQL Developer Version:
It's a bug (27371100) - try upgrading your version of SQL Developer to at least version 18.1.
It's related to working with the plan table.
Latest versions shouldn't be committing/rolling back transactions based on an Explain Plan request.
Related
Whenever I compile my package, Oracle SQL developer is showing this.
Any action to be taken from my side in scripting ? How can I avoid this ? Any serious issue in scripting?
Version-21.4.3.063
For simplicity and cost, we are starting our project using local MySQL running on our GCE instances. We will want to switch to CloudSQL some months down the road.
Any advice on avoiding MySQL version conflicts/challenges would be much appreciated!
The majority of the documentation is for MySQL 5.7 so as an advice I recommend you use this version and review migrating to cloudsql concept this is a guide that will guide you through how to migrate safely which migration methods exist and how to prepare you MySQL database.
Another advice which I can give you is make the tutorial migrating mysql to cloud using automated workflow tutorial this guide also says that the any MySQL database running version 5.6 or 5.7 allows you to take advantage of the Cloud SQL automated migration workflow this tutorial is important to know how works and how deploy a source MySQL database on Compute Engine. The sql page will give you more tutorials if you want to learn more.
Finally I suggest to you check de sql pricing to be aware about the billing and also I suggest to you create a workspace with this you can have more transparency and more control over your billing charges by identifying and tuning up the services that are producing more log entries.
I hope all the information that I'm giving you are helpful.
The error message i'm getting is "current version of the following service is not supported: GitOdb".
Build pipeline is for ASP.NET CORE(v3) API project.
When i click on the error it says "Build not found"
After investigation, there is a recently event of availability degradation of Azure DevOps, which affected these services, and it has been resolved now. If you want to know more information, please click here: https://status.dev.azure.com/_event/188718946 .
The issue is now fully mitigated. To mitigate, we stopped updates and
upgraded the impacted databases. We recognize the wide impact this had
to our customers in this region and will be following up on learnings
and improvements to prevent the chance of recurrence. We apologize for
the impact this caused.
In this case, many users encountered the same problem (starting a build pipeline immediately fails with TF400860: The current version of the following service is not supported: GitOdb. Version: 1700, MinVersion: 1700), which has now been fixed.
I am trying to migrate from TFS 2013 Update 4 to Visual Studio Online. I have had real difficulties using OpsHub Migration Utility, so I have come now seeking advice on how I may go forward.
I have 65 Team Projects to migrate, some with source code, others fairly empty with just a few work items so they differ in size a fair bit. I want to maintain branches we currently have which are cross Team Projects so I initially tried selecting all 65 projects for migration. This took 11hours at the creating configuration stage of the utility, then on getting to the end the tool complained it could not communicate with the service OpsHub Visual Studio Online Migration Utility. So back to square one.
Next approach was to batch the projects into sets of 10 projects. The validation and creating configuration stage was done in 10mins for each set which was a big leap forward, and the migration actually started. This has currently been running for about 17hours. It has done 29,000 work item revisions out of 480,000 across all Team Projects, so I think this may well take a couple of weeks to clear. It hasn't started on the Version Control data yet, which I'm hopeful it does at a later stage but this says not running at the moment.
This is running on a fast i7 box, with 16GB RAM, SSDs the business. 100Mbps internet connection.
I have emailed OpsHub to find out if the commercial version will perform better. But any suggestions what I could do better welcome, including any alternatives to the migration tool.
For Configuration creation taking high time, the assumed reason seems
to be due to issue in communicating with the service OpsHub Visual
Studio Online and waiting till the TimeOut.
The Work Item migration sync time seems to be near to the expectation, migration of Version Control data will be started once the work item migration is completed.
Also as the data is in big amount, its taking time but the migration would keep on running in background, you can use your source TFS instance(if required) without stopping the migration.
For more details on Profession Services you can drop an email to support#opshub.com
There is another tool named TFS Integration Platform that developed by MS for TFS Migration. You can try with it to see if it can migrate the data faster.
I started a migration source code from TFS (not work items) to Visual Studio Online and it has been running for more than 24 hours but the status still shows "Reading and Analysis". CPU usage for the application is showing 0.
Should I keep waiting or is there a way to find out if an exception is thrown? I am not too familiar with debugging procedure for Java applications.
Which version you are using?
There is performance issue with label which is fixed in version 1.0.1.005.
Can you try current version?
Error : TF14045: The identity 19b7a3e0-b25b-4c48-90a8-813202d6d1b4 is not a recognized identity.
above error comes while connecting to tfs server that's why utility continuously displaying reading and analysis because everytime utility connects to source TFS for fetching total number of change sets and lables it encounters same error.
As per microsoft blogs, people are encountering this type of issue after upgradation/db restore for collection. After this process when user tries to connect tfs, it always throws the same error which you have encountered. Have you done any of the above process for the collection you are trying to migrate? You can refer following thread which contains resolution for same error.
http://social.msdn.microsoft.com/Forums/vstudio/en-US/b67ad1d6-d763-4602-bf14-489a3389a30d/getting-tf14045-the-identity-guid-is-not-a-recognized-identity-after-db-restored?forum=tfsadmin
Let us know in case you won't be able to resolve this with the above information and also in case you have not done any upgradation/db restore procedure. In that case we would like to know your source tfs version and older upgrade history of this instance (If any).