Error Connecting To Database Ora-10
find the cause of this error. Finally came across that APPLSYSPUP is in EXPIRED (GRACE) status . you can check this under dba_users cloumn account_status.I changed the status to open usingAlter user APPLSYSPUB identified by PUB;This resolved my issue.RegardsGuru Posted by Gurtej Singh at 4:16 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Blog Archive ► 2008 (23) ► Jan 2008 (10) ► Feb 2008 (1) ► Mar 2008 (10) ► May 2008 (2) ► 2010 (1) ► Feb 2010 (1) ▼ 2011 (8) ▼ Jan 2011 (2) Error connecting to database ORA--1 Delete Discoverer Workbook from backend ► Mar 2011 (5) ► May 2011 (1) ► 2012 (3) ► Nov 2012 (3) ► 2013 (8) ► Sep 2013 (5) ► Oct 2013 (1) ► Nov 2013 (2) ► 2014 (3) ► Jan 2014 (2) ► Aug 2014 (1) ► 2015 (2) ► Jul 2015 (2) About Me Gurtej Singh View my complete profile Followers Site Viewers Visitors Simple template. Powered by Blogger.
autoconfig Test the issue. Posted by Zahid Rahim at 00:15 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest No comments: Post a Comment Newer Post http://oracleapplicationguru.blogspot.com/2011/01/error-connecting-to-database-ora-1.html Older Post Home Subscribe to: Post Comments (Atom) About Me Zahid Rahim View my complete profile Blog Archive ► 2016 (14) ► August (1) ► April (2) http://zahidrahimocp.blogspot.in/2015/09/error-connecting-to-database-ora-10.html ► March (7) ► February (3) ► January (1) ▼ 2015 (19) ► October (1) ▼ September (4) Error connecting to database Ora-10 Error Applying hrglobal.drv AD Auto Config (adautocfg) Steps/Procedure Oracle EBS R12.2.4 Rapid Clone ► August (1) ► July (1) ► June (1) ► May (2) ► March (4) ► February (1) ► January (4) ► 2014 (29) ► December (6) ► November (7) ► September (1) ► August (2) ► July (13) Simple template. Powered by Blogger.
‘db_files';Get the count of the datafiles createdselect count(*) from v$datafile;When exceeding the db_files parameter ORA-00059 error given. Increasing the value of the http://amilasanoracle.blogspot.com/2012/02/ora-error-codes.html db_files parameter will resolve the problem. ORA-01102: cannot mount database in EXCLUSIVE mode First check smon using the command ps -eaf | grep smon Then shutdown database... shutdown immediate https://answers.splunk.com/answers/72101/splunk-db-connect-error-connecting-to-oracle-instance-ora-12514.html Then logout of SQL and again grep for smon... Kill that particular process using kill -9
and to help other users in the Splunk community with their own questions. This quick tutorial will help you get started with key features to help you find the answers you need. You will receive 10 karma points upon successful completion! Get Started Skip Tutorial Splunk.com Documentation Splunkbase Answers Wiki Blogs Developers Sign Up Sign in FAQ Refine your search: Questions Apps Users Tags Search Home Answers ask a question Badges Tags Users Welcome to Splunk Answers! Not what you were looking for? Refine your search. Search Splunk DB Connect: Error connecting to Oracle Instance ORA-12514 0 I've been trying to connect to an oracle instance but I am running into a brick wall and not sure what to try next. I know the Oracle SID, server name, port, and account are all good for read only, but this is the error I continuously get: Encountered the following error while trying to update: In handler 'dbx-databases': Error connecting to database: java.sql.SQLException: Listener refused the connection with the following error: ORA-12514, TNS:listener does not currently know of service requested in connect descriptor I'm running Splunk 5.0.1 and Splunk DB Connect 1.0.6.. db Question by mjones414 Jan 15, 2013 at 03:20 PM 247 ● 4 ● 5 ● 7 People who like this Close 0 Add comment Comment 10 |10000 characters needed characters left 4 Answers · Add your answer oldest newest most voted 0 Accepted Answer Looks like I was right about the cache.. for whatever insane reason, one of the trial attempts using a fully qualified instance name was set in ../launcher/local/database.conf. Once I blew this away and bounced splunk all was peaceful.. Thanks Ziegfried for all of your help! Answer by mjones414 Jan 18, 2013 at 10:01 PM Comment 10 |10000 characters needed characters left ziegfried ♦ · Jan 22, 2013 at 07:33 AM Just to clarify: The database stanza in launcher/local/database.conf is not a cache. It's there because it has been created in the context of the launcher app. This happens when you navigate from Launcher to manager instead of navigating there from the DB Connect app. The behavior for other configs in Splunk like inputs or props is similar. Add comment 4 If you are sure that you are using the correct SID and you are using an older version of Oracle, you might be able to connect by changing the following setting database.conf for you database connection: database.sid = true This setting is not exposed to the UI and you'll have to restart S