[
https://jira.jboss.org/jira/browse/TEIID-835?page=com.atlassian.jira.plug...
]
Ramesh Reddy resolved TEIID-835.
--------------------------------
Resolution: Done
The VDB name was being compared in case sensitive way, where there is no guarantee that
user logged in with same case for the VDB name
AdminApi (thru AdminShell) allows deletion of an active VDB from
under a connected user
---------------------------------------------------------------------------------------
Key: TEIID-835
URL:
https://jira.jboss.org/jira/browse/TEIID-835
Project: Teiid
Issue Type: Bug
Components: AdminApi
Affects Versions: 6.2.0
Environment: Fedora 10, Teiid 6.2 RC1
Reporter: Paul Nittel
Assignee: Ramesh Reddy
Fix For: 6.2.0
I used two AdminShell sessions to demonstrate this: one connected as an administrator and
the other connected as a user to a VDB.
Admin: addVDB("VDB name", "VDB file")
User: SELECT ...
Admin: deleteVDB("VDB name","version")
User: SELECT ...
At this point the user receives:
// Error: // Uncaught Exception: TargetError : at Line: 165 : in file: URL:
jar:file:/home/pnittel/teiid62RC1/adminshell/lib/teiid-adminshell-6.2.0-SNAPSHOT.jar!/scripts/jdbc.bsh
: throw e ;
Target exception: com.metamatrix.jdbc.MMSQLException: VDB "qt_db2v81ds" version
"1" does not exist or not in valid state.
The MetaMatrix (Console) way of doing things is to defer deletion of the VDB until there
are no active connections. Also, it was required that the VDB status be INACTIVE before
the request to delete would be honored.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira