We are integrating the P6 primavera thick client(EPPM)with Oracle Access Manager (OAM) we have done all the configurations on both OAM and Application side as per the oracle documentation.
The connectivity looks OK, but its giving following error.
The application and database versions do not match. Click Exit to close the application.
Primavera P6 Professional R16.1
Expected database version: PMDB,1610.0001.0001
Current database version:
Though both the expected and current database version is same. Also when I checked here I see in the screenshot it does give current database version value. but in our case its not giving any value in the error message.we are using Primavera P6 version 16R1.
Check the version of Database using following SQL query:
select database_version from prefer
if this is different from the expected one then applying patches should sort the issue.
Related
I'm trying to upgrade an old artifactory (OSS) installation from version 5.5.1 to 6.23.13 on RHEL. The DB is postgres.
Have copied the DB and filesystem from production (running 5.5.1) to a test installation (running 6.23.13).
The test implementation appears to work, except for a problem with user permissions, which don't appear to be picked up as expected in the new system.
I note that in 5.5.1, the users appear in a 'users' table in Postgres. However, in the 6.23.13 version, this table is being ignored and users are being populated into an 'access_users' table instead.
The users authenticate with LDAP (that part is working) but when logged in, do not get any of their old groups and permissions.
I'm not very familiar with artifactory, so any pointers on where to look to get to the bottom of this appreciated.
I have recently upgraded Asp.Net Identity V1.0 to V2.0. Because of this, in Identity database few more columns get added like Email, IsEmailConfirmed etc. without any data loss.
I like to know is there any way to downgrade from Asp.Net Identity V2.0 to V1.0 without any data loss.
I have tired many ways but I am not able to retrieve Identity V1.0 database without data loss. Have spend nearly 3 days in search of good tutorial/blog for downgrading activity but not able to find one.
Any help much appreciated.
No source control or backups I assume?
One thing you could possibly do is use code first migrations:
1) Open an Identity Version 1 of your solution. If you can't find one, just do a new project with Identity Version 1.
2) From the console, enable-migrations then add-migration -IgnoreChanges initialIdentity1 followed by update-database. This will create a migration with a snapshot of the current database state.
3) Upgrade to Identity 2.
4) From the console, add-migration identity2update followed by update-database. This will create a migration with the differences including a method called Down() that will contain the information needed to move backwards.
5) Generate a script that can be used to move backwards:
update-database -Script -TargetMigration initialIdentity1
6) Apply that script to your database and downgrade the Nuget Identity package.
Now make a backup and add your code to source control :)
Please suggest a easy method to take backup of P6 application configuration details(configuration and authentication tab).
I need to take backup of this configuration before importing production data into the develpment environment. Currently i am taking screenshots of each options which is very exhausting.(I'm new to Primavera). Please help.
It looks like the configuration data is held in the ADMIN_CONFIG table. If you are using SQL Server you can use the SQL Profiler to watch the queries being issued by the admin tool.
I have noticed that on one of my old asp.net applications (running on Azure now and now using SQL azure database) that I get the SQL txt for all queries run against the database contained within the SQL Dependency telemetry. This is great and has helped me target queries to optomise.
I have a newer app (running in a raskspace data centre) that is also showing SQL telemetry, but the query txt is missing.
Do I need to be running within Azure for the query txt to be included, or is there something that I can do to enable this feature?
Thanks for all your help.
I might be mistaken here, but I remember that when one uses AI Status Monitor to collect dependencies - the command text is collected, when one uses .NET 4.5.2 and no AI Status Monitor - then the embedded .NET collection does not extract the command text.
This might be your case if the old asp.net app you mention is .NET 4.0 and AI Status Monitor is installed on that box, while the new app is 4.5+ without the AI Status Monitor on the box (which might be expected for the data center).
I'm running into a strange issue when connecting to a local sqlite database on Windows Phone 8. When testing the app locally after deploying with VS, I'm able to connect to the database without any issues and run queries.
However, when I run the app after downloading it from the Store, I receive the following exception upon attempting to connect to the database:
Could not open database file: 'Version=3,uri=file:mydbname.sqlite' (CannotOpen)
at SQLite.SQLiteConnection.ctor(String databasePath, SQLiteOpenFlags openFlags, Boolean storeDateTimeAsTicks)
I should note that after receiving this exception, the query goes through and returns the expected data (seemingly without issue), which confirms that the db does indeed exist on the device after installing it from the Store.
The database path in the exception is the same as the one I've seen while debugging so I'm not sure why I'm getting an error. I'm using sqlite-net-wp8 v3.8.4.3.
I've seen this post (but it seems to not be limited to the Store): I cannot create SQLiteConnection in PCL version of Sqlite.net on WP8
Thank you!
Changing my db path from 'Version 3, uri=file:mydbname.sqlite' to use ApplicationData.Current.LocalFolder.Path + 'mydbname.sqlite' seems to have solved this problem.