Why are my resources owned by 'nobody'?
Article ID: KB0080185
Updated On:
| Products | Versions |
|---|---|
| TIBCO Data Virtualization | v7.0.x |
Description
After a .car file migration of resources, an execution of a view or procedure may return a privilege error concerning an object that is owned by 'nobody'.
Issue/Introduction
This article concerns TDV privilege related errors.
Resolution
The 'nobody' user is a default TDV userid belonging to the 'composite' domain but is not meant to be used by anyone.
This user has no assigned role or privileges for any resource, thus if one of your resources is owned by 'nobody', there will likely be a permission error thrown when being used in an execution.
Aside from an intentional manual owner change, a resource can end up being owned by 'nobody' instead of its true original owner if the resource object was migrated via a .car file import into a destination server where that user does not exist.
This could typically happen between different environments, such as from a DEV server to a PROD server where the individual TDV developer userids are not expected to exist.
This user has no assigned role or privileges for any resource, thus if one of your resources is owned by 'nobody', there will likely be a permission error thrown when being used in an execution.
Aside from an intentional manual owner change, a resource can end up being owned by 'nobody' instead of its true original owner if the resource object was migrated via a .car file import into a destination server where that user does not exist.
This could typically happen between different environments, such as from a DEV server to a PROD server where the individual TDV developer userids are not expected to exist.
Feedback
Yes
No
Powered by
