I recently ran across this error, which led me to this article in DBForums.
Unfortunately, it's been a while and I can't figure out my login, so I'm posting this here.
In my case, it was very definitely a user error :(
This was Oracle 12c, local development database on my laptop.
Because of space constraints, I had moved the USER tablespace to an external drive, and then forgot about it!
Oracle very happily started up and gave no visible objection, but when I tried to connect, it have this message.
So, long story short, if you get this, check that you can connect to all of your Oracle data files!
Happy databasing ;-)
Subscribe to:
Post Comments (Atom)
I had previous written very breifly about creating a report on disk space using WMI A much better, and very concise instruction for qu...
-
I doubt that this comes up often, but I find myself in a bit of an argument about what isolation level will be used for transactions in our ...
-
(get-childitem -recurse -include *.java | select-string -pattern PrepareStatement | foreach {$_.line}).Count I developed this fairly quick...
-
I was a bit surprised that not all RDBMS platforms offer robust, native support for regular expressions. Oracle: Oracle introduced this ...
No comments:
Post a Comment