Categories
- All Categories
- Oracle Analytics Learning Hub
- 30 Oracle Analytics Sharing Center
- 20 Oracle Analytics Lounge
- 250 Oracle Analytics News
- 45 Oracle Analytics Videos
- 16.1K Oracle Analytics Forums
- 6.3K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 93 Oracle Analytics Trainings
- 16 Oracle Analytics and AI Challenge
- Find Partners
- For Partners
Dataset fails to be found, has no Access option to enable us to check the permissions.
Hiya, hopefully someone can explain this. We have just stood up the FDI environment in production but we cant access one of our spreadsheet data sets.
Errors
[nQSError: 17010] SQL statement preparation failed.
[nQSError: 17001] Oracle Error code: 942, message: ORA-00942: table or view does
not exist at OCI call OCIStmtExecute.
[nQSError: 46217] Query to the replica failed. Retrying the query without the replica.
On further inspection of the the Dataset we noticed the access option is missing so we cant inspect/change the permissions. In the Dev environment its actually the same but we can access the dataset without any issue.
Ive included the Performance Download in the hope someone might be able to explain this.
Thank you for taking the time to read this.
Best Answers
-
Can you try to re-upload or re-publish the Spreadsheet Dataset in Prod? You might need to delete the broken dataset in Prod.
1 -
Hi @Kevin Robertson,
Welcome to the Oracle Analytics Community!
There's a chance, it might be due to either a permissions issue with your user role or that the dataset owner has not granted you sufficient access.
Can you please check the following doc & the post which might be useful.
Hope this help.
Thank you.
1
Answers
-
Thank you to everyone who took time out of their own day to read and respond to my question. I'm pleased to say that we have resolved the issue and it did appear to be a permissions problem when the file was created as a .dva
We think the original file was setup with only the permissions of the person who created the import file and unfortunately that person is not available to us at the moment.
I recreated the dva file, this time without permissions being set, imported the file and then set they required permissions in our Production environment.
All would appear to be working fine.
Thank you, very much appreciated.
1 -
0