Gerhardpet
asked on
Delete database in Pervasive CC
I have created a database in pervasive control center and I manage to create it but did not have proper permission to the database server
So I granted myself the required permissions and I'm now able to create a database pointing to the database server
But now I want to delete the database I created before I had the proper permission. Now when I try to delete that database I get this error
Delete database in Pervasive CC
So I granted myself the required permissions and I'm now able to create a database pointing to the database server
But now I want to delete the database I created before I had the proper permission. Now when I try to delete that database I get this error
7004: Genral failure code
Delete database in Pervasive CC
ASKER
I'm on Pervasive 10
Yes I have already deleted the Engine DNS in the ODBC admisnistrator.
But I can't delete the database from the PCC. I only have remote desktop access so I will ask the admin to try from the console. It is on a VMWare server.
Yes I have already deleted the Engine DNS in the ODBC admisnistrator.
But I can't delete the database from the PCC. I only have remote desktop access so I will ask the admin to try from the console. It is on a VMWare server.
Was that machine updated from PSQLv9? If so, check for this registry key:
HKLM/Software/Pervasive Software/Utilities Interface/Settings/Restric ted Access on WTS Client.
Be sure that this value is set to 0 (unrestricted). With this change, you should be able to delete the DBName from the PCC. If there is a dialog box to ALSO delete the DSN, be sure to uncheck it, as you have already deleted it.
HKLM/Software/Pervasive Software/Utilities Interface/Settings/Restric
Be sure that this value is set to 0 (unrestricted). With this change, you should be able to delete the DBName from the PCC. If there is a dialog box to ALSO delete the DSN, be sure to uncheck it, as you have already deleted it.
ASKER
No it is a new 2012 Windows server and is clean install of psql 10
I checked the registry key and it is already set to 0
I checked the registry key and it is already set to 0
ASKER
I just has the IT manager login to the console form VMware vSphere and try to delete from there and that not work either. Same error
Could be that something is messed up in the dbnames.cfg file. Your best action is to uninstall, manually delete DBNAMES.CFG if is remains behind, then reinstall. The other option would be a manual hack of the dbnames file, which is not exactly easy.
ASKER
I will re-install. Where is the DBNAMES.CFG file located so that I can make sure it does not remain behind?
It is possible to move it after the fact, so it is best to check the current location. Open the PCC, select Configure Local Engine, then go to the Directories tab. Last item should be DBNames location. You can select this entry text, then paste it into a Windows Explorer window to make going there easier.
ASKER
Is there a way to tweak the file to fix the issue instead of reinstalling?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Did I just figure out the easy way to do this?
I renamed the DBNAMES.CFG and then went to another server copied over from that server.
Then deleted the databases from the other server and now I'm able to add new once. No problem.
All works fine
I renamed the DBNAMES.CFG and then went to another server copied over from that server.
Then deleted the databases from the other server and now I'm able to add new once. No problem.
All works fine
Well, gee -- if I had known you had a second server, I could have suggested that!
ASKER
Well I could not have done this without you explaining the DBNAMES.CFG file.
Thank you very much for you help Bill!
Thank you very much for you help Bill!
Try going to the server console (i.e. NOT via remote desktop) and do it there, with an Administrator login. This should have full rights to do what you need.
Essentially, databases are comprised of one or two pieces (depending on the version). There is a DBName (which is visible in the PCC) and an Engine DSN (which is visible in the ODBC Administrator). You can always try to delete the two pieces separately, too.