I mostly work with SQL Server, and thought I'd like to try out Oracle a bit, in case I ever need to work with a client that uses it. I downloaded and installed Enterprise Edition on my desktop. Created a listener. So far so good.
Now it's time to create The Database. I run DBCA, use the General Purpose template with a few tweaks, get to the end, and tell it to start creating.
ORA-12154: TNS:could not resolve the connect identifier specified
Sweet. Abort. I searched around a little bit, and figured I needed a tsnames.ora. I set that up, and tried connecting with sqlplus (which I expected to fail, since no database has been created, but it ought to at least find the listener and talk to it). And sure enough, that part seemed to work. Ran DBCA again. Same error.
So a little more Google work leads me to this thread:
Here's the interesting line:
but I think my original attempts were failing b/c I was specifying passwords (for the SYS, SYSTEM. SYSMAN, etc.) that contained special characters that the dbca somehow didn't handle and/or pass long properly. In my case, the special character seemed to be "@".
Wait a minute. I'm using p@ssw0rd for the passwords. Could it possibly be? I ran DBCA again, using Passw0rd instead (it's a test machine, who gives a shit). This time:
Database creation complete. For details check the logfiles at:
What the pissing fuck? You can't use @ in a password? Please tell me this is just a DBCA bug.