installation :
Oracle There are many tutorials on the web for installation , The explanation is very detailed , we won't repeat it here . , only two links available , Maybe it's helpful . : the Oracle installation and simple configuration "," Installation Free Oracle Client and PL/SQL "
Problem:
in the Oracle experience in the process of such or such a problem, here to do a simple collation.
Question one:
Problem Description:
in the DOS window, use SQL Plus/nolog Command Login Oracle , the result reported: " Sqlplus not internal or external command ",:
Problem solving:
computer → properties → advanced → environment variables, inPathadded inOracle11G(server-side)Sqlplus.exethe file path. For example mine is: D:\app\huaying\product\11.2. 0\Dbhome\ Bin, then add the path to the above file in path, if D:\app\huaying\product\11.2. 0\Dbhomethe \ Bin directory must have sqlplus. EXE file, if not, then you can only reinstall.
Problem Analysis:
We know Path is the path meaning, it is like a global variable, after the setting is complete, as long as the computer or user executes SQL Plus command, will go under this path to find.
Question two:
Problem Description:
Installation Complete Oracle after, found himself forgotten system and the SYS user's password, so the Dos command to try a lot of their own guess of the password, may be due to the wrong password entered too many times, so reported the hint: " Oracle 11g The account is locked ".
Problem solving:
First step: Use Sqlplus Landing System
Step two: Connect SYS DBA
Step three: Unlock
Fourth step: Change the password
Problem Analysis:
Here are some of the reasons why the user name may be locked: ① Common Sense multiple landing unsuccessful (possibly incorrect password); ② This user is manually locked by an administrator, ③ the user password expires, does not change the password on time, and so on.
Question three:
this should not be a problem here, it's just talking about Script some of the feelings of the time. In the Guide script , seemingly very simple action, but in the course of the process has experienced a lot, all should originate from their own not familiar!
The first is to set up a user, set up a table space, modify the user's default table space, give the user authorization, and then the real guideScript. GuideScriptthese previous jobs were onlySQLstatements are relatively ripe and should not be a problem. But in the guidePowerDesignerBuildScriptThere are many problems in the process, one of the reasons is that we have not modifiedPowerDesignerdata syntax, so the resultingScript's AllSQL, a lot of them can't be inOracle, especially some keywords are easy to error.
Summarize:
Oracle Journey of experience, pain and happiness.