Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 15 Oracle Analytics Lounge
- 214 Oracle Analytics News
- 43 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 78 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Getting error 17014,17001,12154
Hi,
Some new fields were added in the database, which i tried importing through connection pool using meta data. But i got this error 17014,17001,12154. Tried a lot but without any success.Please make me understand.
1) Checked DSN value which is already defined in Variable block and is also assigned the value of server name.
2) Checked the value of connection pool and DSN value
3) Checked tnsnames.ora is present in
i) u01/app/oracle/product/11.2.0.3/network/admin
ii) u01/app/oracle/product/11.2.0.4/network/admin
iii) u01/app/oracle/product/middleware11g/oracle_bi1/network/admin
Kindly help.
Answers
-
If it's just few columns, it's often easier to add them by hand (right click > new column, enter the name and type, done).
When you import using the wizard it use the local info, not the server, therefore your DB connection settings needs to work locally too.
And just error numbers doesn't mean much: I doubt people knows errors by number
0 -
Gianni Ceresa wrote:And just error numbers doesn't mean much: I doubt people knows errors by number
Cough cough. Really?
0 -
Thankyou Gianne and Chritian,
I thought it must be well known error. Actually the error looks like this
Error: "[nQSError: 17014] Could Not Connect to Oracle Database. [nQSError: 17001] Oracle Error Code: 12154"Connecting Via ODBC Or OCI To Oracle Database From OBIEE 11g (Doc ID 1228974.1)Troubleshooting OBIEE and ORA-12154: TNS:could not resolve the connect identifier
I think i will follow Gianne.
Regards
0 -
3984491 wrote:I thought it must be well known error. Actually the error looks like this
It's more that often a single OBIEE error has a long list of possible database errors behind: like 17001, it seems to be a single error in OBIEE to say there was an error with the database, but the real error is given in the message as it return the database error.
And if you got ORA-12154, this is not an OBIEE error (like are the nQSError messages), therefore without the full text it's just impossible to clearly know what (which component) is telling you what.
So if you had an ORA-12154 it's probably because your client has no idea of the TNS name used.
Have a look at https://support.oracle.com/epmos/faces/DocContentDisplay?id=2068474.1 too, in 12c the location for the tnsnames.ora is different (also apply to the admintool install which is quite similar in various aspects to a full install of OBIEE).
0 -
Yes, the 170* ones are well known. They are "wrapper errors" and point to actual database issues. Like the OBIEE headers to say "Something is wrong underneath".
The REAL error is ORA-12154. And all ORA-* errors are errors of the database.
0 -
This way doing is more tedious and also you cannot import data. I want to know why I am not able to import through metadata?
1) Located where my tnsnames /u01/app/oracle/product/middleware11g/oracle_bi1/network/admin/tnsnames.ora
2) Also assigned in user.cmd TNS_Admin value as /u01/app/oracle/product/11.2.0.3/network/admin
3) restarted the bi administration tool
but I am still getting the error. I want to do this using wizard as we have many connection pools. Everything is configured properly using olap_dsn
0 -
Did you configure your admintool properly? As said it's something happening on the client, therefore settings tnsnames in linux paths doesn't really help as the admintool is a windows-only program.
3984491 wrote:... you cannot import data.
Data? Which data? There is no data imported in the admin tool, only metadata information about objects of your physical DB.
0 -
Did you give up on this question in the meantime?
0 -
Yes i have given up. got fed up. I think you guys were right we cannot do that. So preferred the manual manner i.e giving full path wherever it was need and imported the columns.
0
