关于pdb插拔更多信息

amazing

772

3页

0次

2020-01-19

5墨值下载

Multitenant Unplug/Plug Best Practices (Doc ID 1935365.1)

In this Document

Goal

Solution

Preparation:

Scenarios:

Scenario 1 – No plug in violations

Scenario 2 – SQL patch present in target container but not in source container

Scenario 3 – SQL patch present in source container but not in target container

Scenario Summary and Actions

References

APPLIES TO:

Oracle Database - Enterprise Edition - Version 12.1.0.1 and later

Oracle Database Cloud Schema Service - Version N/A and later

Oracle Database Exadata Cloud Machine - Version N/A and later

Oracle Cloud Infrastructure - Database Service - Version N/A and later

Oracle Database Cloud Exadata Service - Version N/A and later

Information in this document applies to any platform.

GOAL

To provide the Multitenant Unplug/Plug Best Practices

SOLUTION

When plugging into a new container a PDB may have violations due to Database version (12.1.0.1 vs 12.1.0.2)

SQL patch mismatches

Database parameter mismatches such as character sets or block size

The dbms_pdb.describe and dbms_pdb.check_plug_compatibility APIs can be used to determine if a given PDB can be plugged in

successfully to a target container. Here are the steps to invoke dbms_pdb.describe and dbms_pdb.check_plug_compatibility to investigate

this further:

Preparation:

1) Create PDB description XML file for PDB(PDB1) in question:

exec dbms_pdb.describe (‘PDB1_Unplug.xml’, ‘PDB1’);

2) In the target container environment, check plug compatibility

begin

if dbms_pdb.check_plug_compatibility('PDB1_Unplug.xml', ‘PDB1') then

dbms_output.put_line(‘no violations found');

else

dbms_output.put_line(‘violations found');

end if;

end;

Plugin compatibility issues, if any, will be reported in

pdb_plug_in_violations view

Scenarios:

Scenario 1 – No plug in violations

SQL> BEGIN

2 IF dbms_pdb.check_plug_compatibility('/tmp/PDBORCL.xml') THEN

Document 1935365.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_ad...

第1页共3页 2020/1/13 9:22

3 dbms_output.put_line('no violations found');

4 ELSE

5 dbms_output.put_line('violations found');

6 END IF;

7 END;

8 /

no violations found

PL/SQL procedure successfully completed.

SQL> SELECT type, message, action

2 FROM pdb_plug_in_violations

3 WHERE name = 'PDBORCL';

no rows selected

Scenario 2 – SQL patch present in target container but not in source container

SQL> BEGIN

2 IF dbms_pdb.check_plug_compatibility('/tmp/PDBORCL.xml') THEN

3 dbms_output.put_line('no violations found');

4 ELSE

5 dbms_output.put_line('violations found');

6 END IF;

7 END;

8 /

violations found

SQL> SELECT type, message, action

2 FROM pdb_plug_in_violations

3 WHERE name = 'PDBORCL';

TYPE MESSAGE

--------- --------------------------------------------------------------------------------

ACTION

--------------------------------------------------------------------------------

ERROR PSU bundle patch 1 (PSU Patch 12345): Installed in the CDB but not in the PDB.

Call datapatch to install in the PDB or the CDB

NOTE** :

The violation error message "Installed in the CDB but not in the PDB. PENDING" can also occur when either the

CDB or PDB have invalid database components.

Post validating the database components in CDB and PDB, the status of the violation message in the view

pdb_plug_in_violations will change to RESOLVED, as below.

MESSAGE STATUS ACTION

------------------------------------------ ------------------- ------------------------------------

Installed in the CDB but not in the PDB. RESOLVED Call datapatch to install in the PDB or the CDB

Scenario 3 – SQL patch present in source container but not in target container

SQL> BEGIN

2 IF dbms_pdb.check_plug_compatibility('/tmp/PDBORCL.xml') THEN

3 dbms_output.put_line('no violations found');

4 ELSE

5 dbms_output.put_line('violations found');

6 END IF;

7 END;

8 /

violations found

Document 1935365.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_ad...

第2页共3页 2020/1/13 9:22

Multitenant Unplug/Plug Best Practices (Doc ID 1935365.1)

In this Document

Goal

Solution

Preparation:

Scenarios:

Scenario 1 – No plug in violations

Scenario 2 – SQL patch present in target container but not in source container

Scenario 3 – SQL patch present in source container but not in target container

Scenario Summary and Actions

References

APPLIES TO:

Oracle Database - Enterprise Edition - Version 12.1.0.1 and later

Oracle Database Cloud Schema Service - Version N/A and later

Oracle Database Exadata Cloud Machine - Version N/A and later

Oracle Cloud Infrastructure - Database Service - Version N/A and later

Oracle Database Cloud Exadata Service - Version N/A and later

Information in this document applies to any platform.

GOAL

To provide the Multitenant Unplug/Plug Best Practices

SOLUTION

When plugging into a new container a PDB may have violations due to Database version (12.1.0.1 vs 12.1.0.2)

SQL patch mismatches

Database parameter mismatches such as character sets or block size

The dbms_pdb.describe and dbms_pdb.check_plug_compatibility APIs can be used to determine if a given PDB can be plugged in

successfully to a target container. Here are the steps to invoke dbms_pdb.describe and dbms_pdb.check_plug_compatibility to investigate

this further:

Preparation:

1) Create PDB description XML file for PDB(PDB1) in question:

exec dbms_pdb.describe (‘PDB1_Unplug.xml’, ‘PDB1’);

2) In the target container environment, check plug compatibility

begin

if dbms_pdb.check_plug_compatibility('PDB1_Unplug.xml', ‘PDB1') then

dbms_output.put_line(‘no violations found');

else

dbms_output.put_line(‘violations found');

end if;

end;

Plugin compatibility issues, if any, will be reported in

pdb_plug_in_violations view

Scenarios:

Scenario 1 – No plug in violations

SQL> BEGIN

2 IF dbms_pdb.check_plug_compatibility('/tmp/PDBORCL.xml') THEN

Document 1935365.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_ad...

第1页共3页 2020/1/13 9:22

3 dbms_output.put_line('no violations found');

4 ELSE

5 dbms_output.put_line('violations found');

6 END IF;

7 END;

8 /

no violations found

PL/SQL procedure successfully completed.

SQL> SELECT type, message, action

2 FROM pdb_plug_in_violations

3 WHERE name = 'PDBORCL';

no rows selected

Scenario 2 – SQL patch present in target container but not in source container

SQL> BEGIN

2 IF dbms_pdb.check_plug_compatibility('/tmp/PDBORCL.xml') THEN

3 dbms_output.put_line('no violations found');

4 ELSE

5 dbms_output.put_line('violations found');

6 END IF;

7 END;

8 /

violations found

SQL> SELECT type, message, action

2 FROM pdb_plug_in_violations

3 WHERE name = 'PDBORCL';

TYPE MESSAGE

--------- --------------------------------------------------------------------------------

ACTION

--------------------------------------------------------------------------------

ERROR PSU bundle patch 1 (PSU Patch 12345): Installed in the CDB but not in the PDB.

Call datapatch to install in the PDB or the CDB

NOTE** :

The violation error message "Installed in the CDB but not in the PDB. PENDING" can also occur when either the

CDB or PDB have invalid database components.

Post validating the database components in CDB and PDB, the status of the violation message in the view

pdb_plug_in_violations will change to RESOLVED, as below.

MESSAGE STATUS ACTION

------------------------------------------ ------------------- ------------------------------------

Installed in the CDB but not in the PDB. RESOLVED Call datapatch to install in the PDB or the CDB

Scenario 3 – SQL patch present in source container but not in target container

SQL> BEGIN

2 IF dbms_pdb.check_plug_compatibility('/tmp/PDBORCL.xml') THEN

3 dbms_output.put_line('no violations found');

4 ELSE

5 dbms_output.put_line('violations found');

6 END IF;

7 END;

8 /

violations found

Document 1935365.1 https://support.oracle.com/epmos/faces/DocumentDisplay?_ad...

第2页共3页 2020/1/13 9:22

of 3

5墨值下载

oracle 官方文档日常运维

关注

评论