How to create and configure a Pluggable Database(PDB) in Oracle 12c Release 12.2

1.Oracle Universal Installer(OUI)

2.Database Configuration Assistant(DBCA)

The Database Configuration Assistant (DBCA) gives similar options to the Oracle Universal Installer (OUI). The "Creation Mode" page allows you to enter the default installation configuration details directly.

Step0: run the DBCA

[oracle@ol7 bin]$ dbca
[oracle@ol7 bin]$ pwd
/u01/app/oracle/product/12.1.0.2/db_1/bin
[oracle@ol7 bin]$ 

Step1: Select the operation that you want to perform , Create a databse.

Step2: Select Database Creation Mode.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

[oracle@ol7 ~]$ 
[oracle@ol7 ~]$ 
[oracle@ol7 ~]$ sqlplus / as sysdba

SQL*Plus: Release 12.2.0.1.0 Production on Tue Feb 7 14:13:24 2023

Copyright (c) 1982, 2016, Oracle.  All rights reserved.


Connected to:
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production

SQL> show con_name;

CON_NAME
------------------------------
CDB$ROOT
SQL> 

 The following sections describe some of these options.

Create a Pluggable Database (PDB) using the DBCA

[oracle@ol7 bin]$ pwd
/u01/app/oracle/product/12.1.0.2/db_1/bin
[oracle@ol7 bin]$ 
[oracle@ol7 bin]$ dbca

On the "Manage Pluggable Databases" screen shown previously, select the "Create a Pluggable Database" option and click the "Next" button. On the resulting screen, select the container database to house the new pluggable database and click the "Next" button.

 

 Select the "Create a new Pluggable Database" option and click the "Next" button. If you were plugging in a previously unplugged database, you would select the PDB Archive or PDB File Set options to match the format of the files containing the unplugged PDB.

 

 Enter the pluggable database name, database location and admin credentials, then click the "Next" button.

 If you are happy with the summary information, click the "Finish" button.

Wait while the pluggable database is created. Once complete, click the "OK" button on the message dialog and the "Close" button on the main screen.  

 Unplug a Pluggable Database (PDB) using the DBCA

[oracle@ol7 bin]$ pwd
/u01/app/oracle/product/12.1.0.2/db_1/bin
[oracle@ol7 bin]$ 
[oracle@ol7 bin]$ dbca

On the "Manage Pluggable Databases" screen shown previously, select the "Unplug a Pluggable Database" option and click the "Next" button. On the resulting screen, select the container database that houses the pluggable database to be unplugged and click the "Next" button.

 

 

 

 Plugin a Pluggable Database (PDB) using the DBCA

[oracle@ol7 bin]$ pwd
/u01/app/oracle/product/12.1.0.2/db_1/bin
[oracle@ol7 bin]$ 
[oracle@ol7 bin]$ dbca

 

 

 

 

 Delete a Pluggable Database (PDB) using the DBCA

[oracle@ol7 bin]$ pwd
/u01/app/oracle/product/12.1.0.2/db_1/bin
[oracle@ol7 bin]$ 
[oracle@ol7 bin]$ dbca

 On the "Manage Pluggable Databases" screen shown previously, select the "Delete a Pluggable Database" option and click the "Next" button. On the resulting screen, select the container database that houses the pluggable database to be deleted and click the "Next" button.

 

 

 

 Configure a Pluggable Database (PDB) using the DBCA

On the "Manage Pluggable Databases" screen shown previously, select the "Configure a Pluggable Database" option and click the "Next" button. On the resulting screen, select the container database that houses the pluggable database to be configured and click the "Next" button.

 

 

 https://ol7.localdomain:5500/em

[oracle@ol7 ~]$ sqlplus / as sysdba

SQL*Plus: Release 12.2.0.1.0 Production on Tue Feb 7 16:00:53 2023

Copyright (c) 1982, 2016, Oracle.  All rights reserved.


Connected to:
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production

SQL> show user;
USER is "SYS"
SQL> show con_name;

CON_NAME
------------------------------
CDB$ROOT
SQL>     
SQL> alter session set container=PDB1;

Session altered.

SQL> show user;
USER is "SYS"
SQL> show con_name;

CON_NAME
------------------------------
PDB1
SQL> select DBMS_XDB_CONFIG.GETHTTPPORT() from dual;

DBMS_XDB_CONFIG.GETHTTPPORT()
-----------------------------
			    0

SQL> select DBMS_XDB_CONFIG.GETHTTPSPORT() from dual;

DBMS_XDB_CONFIG.GETHTTPSPORT()
------------------------------
			  5500

SQL> prompt execute the DBMS_XDB.setHTTPSPort procedure to set the HTTPS port 5501
execute the DBMS_XDB.setHTTPSPort procedure to set the HTTPS port 5501
SQL> 
SQL> exec DBMS_XDB_CONFIG.SETHTTPSPORT(5501);

PL/SQL procedure successfully completed.

SQL> select DBMS_XDB_CONFIG.GETHTTPSPORT() from dual;

DBMS_XDB_CONFIG.GETHTTPSPORT()
------------------------------
			  5501

SQL> prompt execute DBMS_XDB.setHTTPPort procedure to set the HTTP port 5511 for EM Express
execute DBMS_XDB.setHTTPPort procedure to set the HTTP port 5511 for EM Express
SQL> 
SQL> exec DBMS_XDB_CONFIG.SETHTTPPORT(5511);

PL/SQL procedure successfully completed.

SQL> select DBMS_XDB_CONFIG.GETHTTPPORT() from dual;

DBMS_XDB_CONFIG.GETHTTPPORT()
-----------------------------
			 5511

SQL> 

  https://ol7.localdomain:5501/em

Create a Pluggable Database (PDB) Manually

To create a new pluggable database from the seed database, all we have to do is tell Oracle where the file should be placed.

 We can do this using one of three methods. If we are using Oracle Managed Files (OMF) we don't need to worry about the file placement. Oracle will handle it for us.

ALTER SYSTEM SET db_create_file_dest = '/u02/oradata';

From 12.1.0.2 onward there is an inline variation of this using the CREATE_FILE_DEST clause. The path set in this clause will be used as the OMF location for the new PDB.

SQL*Plus: Release 12.2.0.1.0 Production on Tue Feb 7 16:16:48 2023

Copyright (c) 1982, 2016, Oracle.  All rights reserved.


Connected to:
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production

SQL> 
SQL> 
SQL> show user;
USER is "SYS"
SQL> show con_name;

CON_NAME
------------------------------
CDB$ROOT
SQL> 
SQL> 
SQL> CREATE PLUGGABLE DATABASE pdb2 ADMIN USER pdb_adm IDENTIFIED BY pdb_adm CREATE_FILE_DEST='/u01/app/oracle/oradata';

Pluggable database created.

SQL> 

The second method uses the FILE_NAME_CONVERT clause in the CREATE PLUGGABLE DATABASE statement.

oracle@ol7 datafile]$ sqlplus / as sysdba

SQL*Plus: Release 12.2.0.1.0 Production on Tue Feb 7 16:28:03 2023

Copyright (c) 1982, 2016, Oracle.  All rights reserved.


Connected to:
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production

SQL> CREATE PLUGGABLE DATABASE pdb3 ADMIN USER pdb_adm IDENTIFIED BY pdb_adm FILE_NAME_CONVERT=('/u01/app/oracle/oradata/cdb1/pdbseed/','/u01/app/oracle/oradata/cdb1/pdb3/');

Alternatively, we can specify the PDB_FILE_NAME_CONVERT initialization parameter before calling the command without using the FILE_NAME_CONVERT clause.

CONN / AS SYSDBA

ALTER SESSION SET PDB_FILE_NAME_CONVERT='/u01/app/oracle/oradata/cdb1/pdbseed/','/u01/app/oracle/oradata/cdb1/pdb4/';

CREATE PLUGGABLE DATABASE pdb4 ADMIN USER pdb_adm IDENTIFIED BY pdb_adm;

Every time there is a need to convert file locations, either of these two methods will work. For the remainder of the article I will stick to using the FILE_NAME_CONVERT method to cut down on the variations I have to display.

We can see the PDBs are present by querying the DBA_PDBS and V$PDBS views.

SQL> show user;
USER is "SYS"
SQL> 
SQL> 
SQL> show parameter pdb_file_name_convert;

NAME				     TYPE	 VALUE
------------------------------------ ----------- ------------------------------
pdb_file_name_convert		     string
SQL> 
SQL> 
SQL> 
SQL> 
SQL> 
SQL> 
SQL> 
SQL> 
SQL> COLUMN pdb_name FORMAT A20
SQL> 
SQL> 
SQL> select pdb_name,status from dba_pdbs order by pdb_name;

PDB_NAME	     STATUS
-------------------- ----------
PDB$SEED	     NORMAL
PDB1		     NORMAL
PDB2		     NEW

SQL> column name format a20
SQL> select name,open_mode from v$pdbs order by name;

NAME		     OPEN_MODE
-------------------- ----------
PDB$SEED	     READ ONLY
PDB1		     READ WRITE
PDB2		     MOUNTED

SQL> show pdbs;

    CON_ID CON_NAME			  OPEN MODE  RESTRICTED
---------- ------------------------------ ---------- ----------
	 2 PDB$SEED			  READ ONLY  NO
	 3 PDB1 			  READ WRITE NO
	 4 PDB2 			  MOUNTED
SQL> 
SQL> ALTER PLUGGABLE DATABASE pdb2 OPEN READ WRITE;

Pluggable database altered.

SQL> select pdb_name,status from dba_pdbs order by pdb_name;

PDB_NAME	     STATUS
-------------------- ----------
PDB$SEED	     NORMAL
PDB1		     NORMAL
PDB2		     NORMAL

SQL> select name,open_mode from v$pdbs order by name;

NAME		     OPEN_MODE
-------------------- ----------
PDB$SEED	     READ ONLY
PDB1		     READ WRITE
PDB2		     READ WRITE

SQL> 
  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
To create a PAL decoder block in GNU Radio Companion (GRC), you can follow these steps: 1. Open GNU Radio Companion and create a new flow graph. 2. Drag a "QT GUI Frequency Sink" block onto the flow graph canvas and connect it to the output of your PAL decoder block. This will allow you to visualize the output of your decoder. 3. Drag a "Feedforward AGC" block onto the flow graph canvas and connect it to the output of your PAL decoder block. This block will adjust the gain of the signal to a constant level. 4. Drag a "Low Pass Filter" block onto the flow graph canvas and connect it to the output of the AGC block. This block will remove high-frequency noise from the signal. 5. Drag a "Throttle" block onto the flow graph canvas and connect it to the output of the low pass filter block. This block limits the rate at which the signal is processed to prevent overloading the CPU. 6. Drag a "QT GUI Time Sink" block onto the flow graph canvas and connect it to the output of the throttle block. This block will allow you to visualize the output of the decoder in the time domain. 7. Finally, add a "PAL Decoder" block to the flow graph. You can find this block in the "Digital" section of the block library. Connect the input of the decoder block to your PAL signal source and the output to the input of the AGC block. 8. Configure the PAL Decoder block according to your signal's characteristics, such as the frequency offset and the type of PAL signal being used. 9. Save the flow graph and run it to see the output of your PAL decoder block. Note that the specific steps may vary depending on your signal source and the requirements of your PAL decoder.

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值