blocks|key|1408959|text|我刚安装了oracle11g
ORA-65096:+oracle中无效的通用用户或角色名称|type|blockquote|depth|inlineStyleRanges|entityRanges|data|1408960|不，您已经安装了Oracle12c。该错误只能发生在12c上，而不能发生在11g上。|unstyled|offset|length|style|BOLD|CODE|1408961|始终检查您的数据库版本，最多4位小数点：|1408962|SELECT+banner+FROM+v$version+WHERE+ROWNUM+=+1;|code-block|syntax|javascript|1408963|Oracle+12c多租户容器数据库有：|1408964|根container(CDB)|unordered-list-item|1408965|和/或零，一个或多个可插拔databases(PDB).|1408966|您必须将数据库创建为容器数据库。但是，您试图在容器中创建用户，即CDB$ROOT，但是，您应该在可插拔数据库中创建用户。|1408967|不应该在容器中创建与应用程序相关的对象，容器保存可插拔数据库的元数据。一般数据库操作应该使用可插拔数据库。否则，不要将其创建为容器，也不要使用multi-tenancy.。但是，12+cR2仍然不能创建非容器数据库。|1408968|最有可能的是，示例模式可能已经安装好了，您只需要在可插拔数据库中解锁。|1408969|例如，如果您将可插拔数据库创建为pdborcl|1408970|sqlplus+SYS/password@PDBORCL+AS+SYSDBA

SQL>+ALTER+USER+scott+ACCOUNT+UNLOCK+IDENTIFIED+BY+tiger;

sqlplus+scott/tiger@pdborcl

SQL>+show+user;
USER+is+"SCOTT"|1408971|要显示PDB并从根容器连接到可插拔数据库：|1408972|SQL>+show+con_name

CON_NAME
------------------------------
CDB$ROOT

SQL>+show+pdbs

++++CON_ID+CON_NAME+++++++++++++++++++++++OPEN+MODE++RESTRICTED
----------+------------------------------+----------+----------
+++++++++2+PDB$SEED+++++++++++++++++++++++READ+ONLY++NO
+++++++++3+ORCLPDB++++++++++++++++++++++++READ+WRITE+NO

SQL>+alter+session+set+container+=+ORCLPDB;

Session+altered.

SQL>+show+con_name;

CON_NAME
------------------------------
ORCLPDB|1408973|我建议你读，Oracle+12c安装后强制步骤|1408974|Note：在生产系统中，建议使用_ORACLE_SCRIPT隐藏参数设置为true的答案是危险的，并且可能会使您的支持合同失效。注意，如果没有咨询Oracle支持，就不要使用隐藏参数。|1408975|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.oracle.com/database/121/CNCPT/cdbovrvw.htm#CNCPT89235|1|http://lalitkumarb.wordpress.com/2014/10/01/mandatory-steps-for-12c-installation/^0|0|8|9|Q|3|11|3|0|6|5|0|0|0|I|0|0|B|3|0|N|3|0|A|5|W|8|1C|6|0|1Z|D|0|7|4|W|2|0|G|7|0|0|0|0|6|H|1|0|0|4|29|A|G|E|0^^$0|@$1|2|3|4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1Q|8|@$E|1R|F|1S|G|H]|$E|1T|F|1U|G|I]|$E|1V|F|1W|G|I]]|9|@]|A|$]]|$1|J|3|K|5|D|7|1X|8|@$E|1Y|F|1Z|G|H]]|9|@]|A|$]]|$1|L|3|M|5|N|7|20|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|D|7|21|8|@]|9|@$E|22|F|23|1|24]]|A|$]]|$1|S|3|T|5|U|7|25|8|@$E|26|F|27|G|H]]|9|@]|A|$]]|$1|V|3|W|5|U|7|28|8|@$E|29|F|2A|G|H]]|9|@]|A|$]]|$1|X|3|Y|5|D|7|2B|8|@$E|2C|F|2D|G|H]|$E|2E|F|2F|G|H]|$E|2G|F|2H|G|H]]|9|@]|A|$]]|$1|Z|3|10|5|D|7|2I|8|@$E|2J|F|2K|G|H]]|9|@]|A|$]]|$1|11|3|12|5|D|7|2L|8|@$E|2M|F|2N|G|H]|$E|2O|F|2P|G|H]]|9|@]|A|$]]|$1|13|3|14|5|D|7|2Q|8|@$E|2R|F|2S|G|I]]|9|@]|A|$]]|$1|15|3|16|5|N|7|2T|8|@]|9|@]|A|$O|P]]|$1|17|3|18|5|D|7|2U|8|@]|9|@]|A|$]]|$1|19|3|1A|5|N|7|2V|8|@]|9|@]|A|$O|P]]|$1|1B|3|1C|5|D|7|2W|8|@]|9|@$E|2X|F|2Y|1|2Z]]|A|$]]|$1|1D|3|1E|5|D|7|30|8|@$E|31|F|32|G|H]|$E|33|F|34|G|H]|$E|35|F|36|G|I]]|9|@]|A|$]]|$1|1F|3|-4|5|D|7|37|8|@]|9|@]|A|$]]]|1G|$1H|$5|1I|1J|1K|A|$1L|1M]]|1N|$5|1I|1J|1K|A|$1L|1O]]]]

<blockquote>
 I just installed oracle11g
 
 ORA-65096: invalid common user or role name in oracle
</blockquote>

No, you have installed Oracle 12c. That error could only be on <code>12c</code>, and cannot be on <code>11g</code>. 

Always check your database version up to 4 decimal places:

<pre><code>SELECT banner FROM v$version WHERE ROWNUM = 1;
</code></pre>

<a href="https://docs.oracle.com/database/121/CNCPT/cdbovrvw.htm#CNCPT89235" rel="noreferrer">Oracle 12c multitenant container database</a> has:

<ul>
<li>a root container(CDB)</li>
<li>and/or zero, one or many pluggable databases(PDB). </li>
</ul>

You must have created the database as a container database. While, you are trying to create user in the container, i.e. CDB$ROOT, however, you should create the user in the PLUGGABLE database.

You are not supposed to create application-related objects in the container, the container holds the metadata for the pluggable databases. You should use the pluggable database for you general database operations. Else, do not create it as container, and not use multi-tenancy. However, 12cR2 onward you cannot create a non-container database anyway. 

And most probably, the sample schemas might have been already installed, you just need to unlock them in the pluggable database.

For example, if you created pluggable database as <code>pdborcl</code>:

<pre><code>sqlplus SYS/password@PDBORCL AS SYSDBA

SQL&gt; ALTER USER scott ACCOUNT UNLOCK IDENTIFIED BY tiger;

sqlplus scott/tiger@pdborcl

SQL&gt; show user;
USER is "SCOTT"
</code></pre>

To show the PDBs and connect to a pluggable database from root container:

<pre><code>SQL&gt; show con_name

CON_NAME
------------------------------
CDB$ROOT

SQL&gt; show pdbs

 CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
 2 PDB$SEED READ ONLY NO
 3 ORCLPDB READ WRITE NO

SQL&gt; alter session set container = ORCLPDB;

Session altered.

SQL&gt; show con_name;

CON_NAME
------------------------------
ORCLPDB
</code></pre>

I suggest read, <a href="http://lalitkumarb.wordpress.com/2014/10/01/mandatory-steps-for-12c-installation/" rel="noreferrer">Oracle 12c Post Installation Mandatory Steps</a>

<hr>

Note: Answers suggesting to use the <code>_ORACLE_SCRIPT</code> hidden parameter to set to true is dangerous in a production system and might also invalidate your support contract. Beware, without consulting Oracle support DO NOT use hidden parameters.

blocks|key|1962898|text|99.9%25的错误ORA-65096:+invalid+common+user+or+role+name意味着您在应该登录到PDB时登录到CDB。例如，如果使用默认的19c安装设置，则应该登录到ORCLPDB+(+PDB)，而不是ORCL+(+CDB)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1962899|危险--如果您坚持以错误的方式创建用户，请按照以下步骤操作。|BOLD|1962900|设置这种无文档化的参数(如前面的下划线所示)只应在Oracle支持的指导下进行。在没有这种指导的情况下更改这些参数可能会使您的支持合同失效。所以你要冒着自己的风险去做。|1962901|具体来说，如果设置"_ORACLE_SCRIPT"=true，将对列ORACLE_MAINTAINED进行一些数据字典更改，将其设置为'Y‘。这些用户和对象将被错误地排除在一些DBA脚本之外。它们可能被错误地包含在某些系统脚本中。|1962902|如果您对上述风险没有意见，并且不希望以正确的方式创建普通用户，请在创建用户之前运行以下命令：|1962903|alter+session+set+"_ORACLE_SCRIPT"=true;++|code-block|syntax|javascript|1962904|我在这里找到了答案|1962905|entityMap|0|LINK|mutability|MUTABLE|url|http://www.dba-oracle.com/t_ora_65096_create_user_12c_without_c_prefix.htm^0|8|17|0|0|2|0|0|9|L|0|0|0|0|9|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|16|8|@$9|17|A|18|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|19|8|@]|D|@]|E|$]]|$1|K|3|L|5|6|7|1A|8|@$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|1D|8|@]|D|@]|E|$]]|$1|O|3|P|5|Q|7|1E|8|@]|D|@]|E|$R|S]]|$1|T|3|U|5|6|7|1F|8|@]|D|@$9|1G|A|1H|1|1I]]|E|$]]|$1|V|3|-4|5|6|7|1J|8|@]|D|@]|E|$]]]|W|$X|$5|Y|Z|10|E|$11|12]]]]

99.9% of the time the error <code>ORA-65096: invalid common user or role name</code> means you are logged into the CDB when you should be logged into a PDB. For example, if you used the default 19c installation settings, you should login to ORCLPDB (the PDB) instead of ORCL (the CDB).
<hr />
DANGER - If you insist on creating users the wrong way, follow the steps below.
Setting undocumented parameters like this (as indicated by the leading underscore) should only be done under the direction of Oracle Support. Changing such parameters without such guidance may invalidate your support contract. So do this at your own risk.
Specifically, if you set <code>&quot;_ORACLE_SCRIPT&quot;=true</code>, some data dictionary changes will be made with the column ORACLE_MAINTAINED set to 'Y'. Those users and objects will be incorrectly excluded from some DBA scripts. And they may be incorrectly included in some system scripts.
If you are OK with the above risks, and don't want to create common users the correct way, run this command before creating the user:
<pre><code>alter session set &quot;_ORACLE_SCRIPT&quot;=true; 
</code></pre>
<a href="http://www.dba-oracle.com/t_ora_65096_create_user_12c_without_c_prefix.htm" rel="noreferrer">I found the answer here</a>

blocks|key|803273|text|在数据库连接工具上创建用户依赖项|type|unstyled|depth|inlineStyleRanges|entityRanges|data|803274|sql+plus
SQL>+connect+as+sysdba;
Enter+user-name:+sysdba
Enter+password:
Connected.
SQL>+ALTER+USER+hr+account+unlock+identified+by+hr;
User+altered
+then+create+user+on+sql+plus+and+sql+developer|code-block|syntax|javascript|803275|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Create user dependency upon the database connect tools

<pre><code>sql plus
SQL&gt; connect as sysdba;
Enter user-name: sysdba
Enter password:
Connected.
SQL&gt; ALTER USER hr account unlock identified by hr;
User altered
 then create user on sql plus and sql developer
</code></pre>

blocks|key|1409064|text|在Oracle+12c及更高版本中，我们有两种类型的数据库：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1409065|容器DataBase+(CDB)|ordered-list-item|1409066|可插拔式DataBase。|1409067|如果您想要创建一个用户，您有两种可能：|1409068|您可以创建一个“容器用户”，也就是“公共用户”。
普通用户属于CBD以及当前和未来的PDBs。这意味着它们可以在Container中执行新的操作，也可以根据指定的权限执行可插拔的DBs。
create+user+c##username+identified+by+password;|offset|length|style|CODE|1409069|您可以创建一个“可插入用户”，也就是“本地用户”。
本地用户只属于一个PDB。这些用户可能被授予管理特权，但仅对其存在的PDB。为此，您应该连接到这样的可插拔数据：
alter+session+set+container+=+nameofyourpluggabledatabase;
在那里，您可以像通常那样创建用户：
create+user+username+identified+by+password;|1409070|不要忘记指定要使用的表空间，它在DB的导入/导出过程中可能很有用。有关it的更多信息，请参见此8003.htm#SQLRF01503|1409071|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.oracle.com/database/121/SQLRF/statements_8003.htm#SQLRF01503^0|0|0|0|0|2M|1B|0|2B|1M|4G|18|0|1B|J|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|12|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|13|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|14|8|@$K|15|L|16|M|N]]|9|@]|A|$]]|$1|O|3|P|5|D|7|17|8|@$K|18|L|19|M|N]|$K|1A|L|1B|M|N]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1C|8|@]|9|@$K|1D|L|1E|1|1F]]|A|$]]|$1|S|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

In Oracle 12c and above, we have two types of databases:

<ol>
<li>Container DataBase (CDB), and</li>
<li>Pluggable DataBase (PDB). </li>
</ol>

If you want to create an user, you have two possibilities: 

<ol>
<li>You can create a "container user" aka "common user". 
Common users belong to CBDs as well as to current and future PDBs. It means they can perform operations in Container DBs or Pluggable DBs according to assigned privileges.

<code>create user c##username identified by password;</code></li>
<li>You can create a "pluggable user" aka "local user". 
Local users belong only to a single PDB. These users may be given administrative privileges, but only for that PDB inside which they exist. For that, you should connect to pluggable datable like that:

<code>alter session set container = nameofyourpluggabledatabase;</code>

and there, you can create user like usually:

<code>create user username identified by password;</code></li>
</ol>

Don't forget to specify the tablespace(s) to use, it can be useful during import/export of your DBs. See this for more information about it <a href="https://docs.oracle.com/database/121/SQLRF/statements_8003.htm#SQLRF01503" rel="noreferrer">https://docs.oracle.com/database/121/SQLRF/statements_8003.htm#SQLRF01503</a>

blocks|key|1962970|text|也许，相对于"_ORACLE_SCRIPT"=true，更安全的替代方法是将"_common_user_prefix"从C##改为空字符串。当它为null时，任何名称都可以用于普通用户。找到了那里。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1962971|在更改该值期间，您可能会面临另一个问题--+ORA-02095+-参数无法修改，根据您的配置(来源)，可以通过几种方法来修复该参数。|1962972|所以对我来说：|1962973|alter+system+set+_common_user_prefix+=+'';+scope=spfile;|code-block|syntax|javascript|1962974|entityMap|0|LINK|mutability|MUTABLE|url|http://www.petefinnigan.com/weblog/archives/00001370.htm|1|https://itsiti.com/ora-02095-specified-initialization-parameter-cannot-be-modified/^0|6|L|12|L|1O|3|2O|2|0|0|1B|2|1|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@$9|15|A|16|1|17]]|E|$]]|$1|F|3|G|5|6|7|18|8|@]|D|@$9|19|A|1A|1|1B]]|E|$]]|$1|H|3|I|5|6|7|1C|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1D|8|@]|D|@]|E|$M|N]]|$1|O|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]|W|$5|R|S|T|E|$U|X]]]]

Might be, more safe alternative to <code>"_ORACLE_SCRIPT"=true</code> is to change <code>"_common_user_prefix"</code> from <code>C##</code> to an empty string. When it's null - any name can be used for common user. Found <a href="http://www.petefinnigan.com/weblog/archives/00001370.htm" rel="nofollow noreferrer">there</a>.

During changing that value you may face another issue - ORA-02095 - parameter cannot be modified, that can be fixed in a several ways, based on your configuration (<a href="https://itsiti.com/ora-02095-specified-initialization-parameter-cannot-be-modified/" rel="nofollow noreferrer">source</a>).

So for me worked that:

<pre><code>alter system set _common_user_prefix = ''; scope=spfile;
</code></pre>

blocks|key|1962982|text|SQL>+alter+session+set+"_ORACLE_SCRIPT"=true;++
SQL>+create+user+sec_admin+identified+by+"Chutinhbk123@!";|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1962983|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>SQL&gt; alter session set &quot;_ORACLE_SCRIPT&quot;=true; 
SQL&gt; create user sec_admin identified by &quot;Chutinhbk123@!&quot;;
</code></pre>

blocks|key|803390|text|如果您的目标是创建一个Oracle用户，然后使用它来处理您的DB，那么您可能需要考虑这样做：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|803391|日志作为sysdba|unordered-list-item|803392|创建pdb+(a.k.a+)。可插拔数据库)|803393|为pdb创建一个用户|803394|下面假设您在localhost中使用db，如果不是简单地用db+uri更改"localhost“的话。|803395|样本代码|803396|记录为sysdba：|803397|$+sqlplus+sys/<your_admin_pws>@localhost+as+sysdba|code-block|syntax|javascript|803398|然后执行以下操作：|803399|create+pluggable+database+MYDATABASE
admin+user+Scott+identified+by+tiger;
file_name_convert+=+('/pdbseed/',+'/mydatabase/')
;

alter+pluggable+database+MYDATABASE+open;|803400|然后，您可能需要向用户Scott授予一些权限:从@localhost登录，并以sysdba的身份登录到新的db。|803401|$+sqlplus+sys/<your_admin_pws>@localhost/MYDATABASE+as+sysdba|803402|给斯科特任何你想要的许可。|803403|grant+connect+to+Scott;
grant+create+view+to+Scott;
grant+create+table+to+Scott;
grant+create+trigger+to+Scott;|803404|现在您可以开始了:您有一个空的数据库实例和一个用户。只需通过做|803405|$+sqlplus+Scott/tiger@localhost/MYDATABASE|803406|奖金|803407|在那之后，我对表空间和配额产生了问题。用sqlplus+sys/<your_admin_pws>@localhost/MYDATABASE+as+sysdba登录|offset|length|style|CODE|803408|可以列出所有表空间|803409|SELECT+TABLESPACE_NAME,+STATUS,+CONTENTS+FROM+USER_TABLESPACES;|803410|创建一个新的表空间。|803411|CREATE+TABLESPACE+TABLESPACENAME+DATAFILE+'tablespace_datafile.dat'+SIZE+10M+REUSE+AUTOEXTEND+ON+NEXT+10M+MAXSIZE+200M;|803412|您可以使用以下方法丢弃已损坏的表空间|803413|Drop+tablespace+TABLESPACENAME+including+contents+and+datafiles;|803414|您可以向Scott授予对表空间的“访问”|803415|alter+user+Scott+quota+unlimited+on+TABLESPACENAME;|803416|注：quota+unlimited可能是一种不好的做法，检查甲骨文如何限制用户的配额|803417|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|K|1N|0|0|0|0|0|0|0|0|0|2|F|0^^$0|@$1|2|3|4|5|6|7|21|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|22|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|23|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|24|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|25|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|26|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|27|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|28|8|@]|9|@]|A|$R|S]]|$1|T|3|U|5|6|7|29|8|@]|9|@]|A|$]]|$1|V|3|W|5|Q|7|2A|8|@]|9|@]|A|$R|S]]|$1|X|3|Y|5|6|7|2B|8|@]|9|@]|A|$]]|$1|Z|3|10|5|Q|7|2C|8|@]|9|@]|A|$R|S]]|$1|11|3|12|5|6|7|2D|8|@]|9|@]|A|$]]|$1|13|3|14|5|Q|7|2E|8|@]|9|@]|A|$R|S]]|$1|15|3|16|5|6|7|2F|8|@]|9|@]|A|$]]|$1|17|3|18|5|Q|7|2G|8|@]|9|@]|A|$R|S]]|$1|19|3|1A|5|6|7|2H|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|2I|8|@$1D|2J|1E|2K|1F|1G]]|9|@]|A|$]]|$1|1H|3|1I|5|6|7|2L|8|@]|9|@]|A|$]]|$1|1J|3|1K|5|Q|7|2M|8|@]|9|@]|A|$R|S]]|$1|1L|3|1M|5|6|7|2N|8|@]|9|@]|A|$]]|$1|1N|3|1O|5|Q|7|2O|8|@]|9|@]|A|$R|S]]|$1|1P|3|1Q|5|6|7|2P|8|@]|9|@]|A|$]]|$1|1R|3|1S|5|Q|7|2Q|8|@]|9|@]|A|$R|S]]|$1|1T|3|1U|5|6|7|2R|8|@]|9|@]|A|$]]|$1|1V|3|1W|5|Q|7|2S|8|@]|9|@]|A|$R|S]]|$1|1X|3|1Y|5|6|7|2T|8|@$1D|2U|1E|2V|1F|1G]]|9|@]|A|$]]|$1|1Z|3|-4|5|6|7|2W|8|@]|9|@]|A|$]]]|20|$]]

If your goal is to create an Oracle user and then use it to do stuff with your DB you probably want to consider doing this:
<ul>
<li>log as sysdba</li>
<li>create a pdb (a.k.a. pluggable database)</li>
<li>create a user for your pdb</li>
</ul>
What follows assume you are working with a db in localhost, if not simply change &quot;localhost&quot; with your db uri.
<h2>Sample code</h2>
Log as sysdba:
<pre><code>$ sqlplus sys/&lt;your_admin_pws&gt;@localhost as sysdba
</code></pre>
then execute this:
<pre><code>create pluggable database MYDATABASE
admin user Scott identified by tiger;
file_name_convert = ('/pdbseed/', '/mydatabase/')
;

alter pluggable database MYDATABASE open;
</code></pre>
then you may want to grant some permission to user Scott: log out from @localhost and log back in as sysdba to your new db
<pre><code>$ sqlplus sys/&lt;your_admin_pws&gt;@localhost/MYDATABASE as sysdba
</code></pre>
and grant Scott whatever permission you want, e.g.
<pre><code>grant connect to Scott;
grant create view to Scott;
grant create table to Scott;
grant create trigger to Scott;
</code></pre>
now you are good to go: you have an empty database instance and a user. Just log in by doing
<pre><code>$ sqlplus Scott/tiger@localhost/MYDATABASE
</code></pre>
<h2>Bonus</h2>
I had problem with tablespaces and quotas after that.
Log with <code>sqlplus sys/&lt;your_admin_pws&gt;@localhost/MYDATABASE as sysdba</code>
You can list all tablespaces with
<pre><code>SELECT TABLESPACE_NAME, STATUS, CONTENTS FROM USER_TABLESPACES;
</code></pre>
You can create a new tablespace with
<pre><code>CREATE TABLESPACE TABLESPACENAME DATAFILE 'tablespace_datafile.dat' SIZE 10M REUSE AUTOEXTEND ON NEXT 10M MAXSIZE 200M;
</code></pre>
You can drop your broken tablespaces with
<pre><code>Drop tablespace TABLESPACENAME including contents and datafiles;
</code></pre>
You can grant &quot;access&quot; to the tablespace to Scott with
<pre><code>alter user Scott quota unlimited on TABLESPACENAME;
</code></pre>
N.B. <code>quota unlimited</code> is probably a bad practice, check oracle docs on how to limit user's quota

blocks|key|803500|text|在我的例子中，默认安装甲骨文之后，我首先连接到导致问题的orcl。并重新连接到orclpdb+(可插拔DataBase+)解决了这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|803501|​|803502|📷|atomic|803503|803504|803505|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/ab4732f1ea4d973c189d4ee28f407b5d.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/74c4d68f788bb821c473e761bc7674bd.png^0|S|4|13|7|0|0|0|1|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|12|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|13|8|@]|D|@$9|14|A|15|1|16]]|E|$]]|$1|K|3|I|5|J|7|17|8|@]|D|@$9|18|A|19|1|1A]]|E|$]]|$1|L|3|G|5|6|7|1B|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T|U|-4]]|V|$5|P|Q|R|E|$S|W|U|-4]]]]

In my case, after default oracle installation, I first connected to <code>orcl</code> which cause the problem. And reconnected to <code>orclpdb</code> (Pluggable DataBase, PDB) resolve the issue.
<a href="https://i.stack.imgur.com/d0Lpa.png" rel="noreferrer"><img src="https://i.stack.imgur.com/d0Lpa.png" alt="enter image description here" /></a>
<a href="https://i.stack.imgur.com/cc1cIl.png" rel="noreferrer"><img src="https://i.stack.imgur.com/cc1cIl.png" alt="enter image description here" /></a>

blocks|key|1963117|text|​|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1963118|📷|atomic|offset|length|1963119|在多个oracle版本12或更高版本下，有两种类型的用户：|1963120|属于CBD容器的全局用户。若要在此容器中创建用户，必须创建用户c##username+identified+by+passwod;。|ordered-list-item|style|CODE|1963121|本地用户:属于PDBS数据库(是与父CBD容器相关的元素)。您使用的语法与本地用户的创建匹配。|1963122|如果您在可插拔数据库(PDBS)中，请这样做以解决问题：|1963123|create+user+c##Scott+identified+by+tiger;+|code-block|syntax|javascript|1963124|注意:您必须在用户名之前添加c##。|BOLD|1963125|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/8b2410ecaaefdef3b7b769e758551444.png|imageAlt^0|0|0|1|0|0|0|V|Y|0|0|0|0|E|3|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|19|8|@]|9|@$E|1A|F|1B|1|1C]]|A|$]]|$1|G|3|H|5|6|7|1D|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|1E|8|@$E|1F|F|1G|L|M]]|9|@]|A|$]]|$1|N|3|O|5|K|7|1H|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1I|8|@]|9|@]|A|$]]|$1|R|3|S|5|T|7|1J|8|@]|9|@]|A|$U|V]]|$1|W|3|X|5|6|7|1K|8|@$E|1L|F|1M|L|Y]]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]]|10|$11|$5|12|13|14|A|$15|16|17|-4]]]]

<a href="https://i.stack.imgur.com/unlTO.png" rel="noreferrer"><img src="https://i.stack.imgur.com/unlTO.png" alt="enter image description here" /></a>
under multinant oracle version 12 or higher , there are two types of users:
<ol>
<li>global users, which belong to the CBD container. to create a user in this container you must do Create user <code>c##username identified by passwod;</code></li>
<li>local users: which belong to the PDBS databases (are elements which relate to the parent CBD containers). the syntax you used matches the creation of local users.</li>
</ol>
if you are in pluggable database(PDBS) do this to solve your problem :
<pre><code>create user c##Scott identified by tiger; 
</code></pre>
note : you must add c## before the username.

blocks|key|1409341|text|这部分可能会解决你的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1409342|alter+"_oracle_script"=true；|blockquote|1409343|遵循以下原则：|1409344|>+sqlplus+/nolog
>+connect+sys+/+as+sysdba
>+alter+session+set+"_oracle_script"=true;
>+create+user+user1+identified+by+1;|code-block|syntax|javascript|1409345|用户被创建..。|1409346|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Q|8|@]|9|@]|A|$]]|$1|E|3|F|5|6|7|R|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|S|8|@]|9|@]|A|$J|K]]|$1|L|3|M|5|6|7|T|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|O|$]]

this part may fix your problem.
<blockquote>
alter session set &quot;_oracle_script&quot;=true;
</blockquote>
follow this:
<pre><code>&gt; sqlplus /nolog
&gt; connect sys / as sysdba
&gt; alter session set &quot;_oracle_script&quot;=true;
&gt; create user user1 identified by 1;
</code></pre>
and the user is created..

blocks|key|1409397|text|对于码头用户获取此错误的建议：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1409398|我在试图创建Oracle19c的对接图像时也犯了同样的错误，原因正是被接受的答案。我的对接图像打算作为原始数据库的副本，以便在孤立的环境中进行测试和开发，因此我的目标是尽可能与原始数据库保持最佳的相似性。不幸的是，原始数据库被配置为nonCDB单实例数据库，这在标准甲骨文图像中不是默认设置。|offset|length|1409399|首先，我尝试了支持另类图像的地方，但是它还有另一个缺点(两倍大的硬编码卷)。|1409400|最后，我从原始图像和替代图像中提取了$ORACLE_BASE/*.sh脚本，分析了差异，并将相关差异应用于原始脚本。基本的更改是在dbca.rsp.tmpl文件中，在删除$ORACLE_PDB+env重新配置alter+system启动SQL脚本的使用时，还必须执行一些进一步的相关更改，例如在健康检查中。|style|CODE|1409401|然后甲骨文在nonCDB模式下成功启动。可以验证是否尝试create+user+foo+identified+by+foo;作为system用户(成功)或select+name,+cdb,+con_id+from+v$database;+(返回cdb=0)。|1409402|entityMap|0|LINK|mutability|MUTABLE|url|https://hub.docker.com/layers/oracle.19.3.0-ee/oracledb19c/oracle.19.3.0-ee/oracle19.3.0-ee/images/sha256-2e76fb433e5bfdcea00c08ffbe96541dc32677463e95fac40cb7bb6289bf4f7b?context=explore|1|https://hub.docker.com/r/doctorkirk/oracle-19c^0|0|3N|7|0|0|9|4|1|0|I|H|1T|D|2D|B|2W|C|0|S|Y|1S|6|25|15|3E|5|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]]|A|$]]|$1|F|3|G|5|6|7|12|8|@]|9|@$D|13|E|14|1|15]]|A|$]]|$1|H|3|I|5|6|7|16|8|@$D|17|E|18|J|K]|$D|19|E|1A|J|K]|$D|1B|E|1C|J|K]|$D|1D|E|1E|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1F|8|@$D|1G|E|1H|J|K]|$D|1I|E|1J|J|K]|$D|1K|E|1L|J|K]|$D|1M|E|1N|J|K]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]|V|$5|Q|R|S|A|$T|W]]]]

Advice for docker users getting this error:
I got same error trying to create docker image of Oracle19c and the cause was exactly what accepted answer says. My docker image was intended as copy of original database for testing and development in isolated environment so I was aimed at the best possible similarity with original. Unfortunately the original database was configured as nonCDB single-instance database which is not default setting in <a href="https://hub.docker.com/layers/oracle.19.3.0-ee/oracledb19c/oracle.19.3.0-ee/oracle19.3.0-ee/images/sha256-2e76fb433e5bfdcea00c08ffbe96541dc32677463e95fac40cb7bb6289bf4f7b?context=explore" rel="nofollow noreferrer">standard Oracle image</a>.
First I tried <a href="https://hub.docker.com/r/doctorkirk/oracle-19c" rel="nofollow noreferrer">alternative image</a> where it was supported but it has another drawbacks (twice larger, hardcoded VOLUME).
Finally I pulled out <code>$ORACLE_BASE/*.sh</code> scripts from both original and alternative image, analyzed differences and applied relevant differences onto original scripts. The essential change was in <code>dbca.rsp.tmpl</code> file and in removing usage of <code>$ORACLE_PDB</code> env reconfiguring <code>alter system</code> startup SQL scripts, also some further related changes such as in healthcheck must be performed.
Then oracle successfully started in nonCDB mode. It can be verified trying <code>create user foo identified by foo;</code> as <code>system</code> user (which succeeds) or the <code>select name, cdb, con_id from v$database;</code> (which returns <code>cdb=0</code>).

I just installed Oracle, and it was missing the Scott schema. So i am trying to generate it myself. I got the sql script of Scott schema, but when i try to run the query:
<pre><code>create user Scott identified by tiger; 
</code></pre>
it displays the following error:
<blockquote>
ORA-65096: invalid common user or role name in oracle.
</blockquote>
Basically it is not allowing me to create a user Scott.
Why is that, and how can I fix my problem?

error: ORA-65096: invalid common user or role name in oracle

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我刚刚安装了Oracle，它缺少Scott模式。所以我正试图自己产生它。我得到了Scott模式的sql脚本，但是当我尝试运行查询时：create user Scott identified by tiger; 它显示以下错误：ORA-65096: oracle中无效的通用用户或角色名称。基本上，它不允许我创建一个用户S...

问错误: ORA-65096: oracle中无效的通用用户或角色名称
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问错误: ORA-65096: oracle中无效的通用用户或角色名称EN