The procedure for add and delete PDB is as follows for the database using the multitenant architecture.
Add PDB when userApplication is Online. Execute the following procedures on the node whose userApplication is Online.
There is no setting change of the Oracle instance resource. After the monitoring restart, added PDB is automatically monitored.
Maintenance mode / Monitoring disruption
# /opt/SMAW/SMAWRrms/bin/hvutil -m on <userApplication> (Maintenance mode) # /opt/FJSVclora/sbin/hvoradisable -a <userApplication> (Monitoring disruption)
Confirmation of maintenance mode and stop of monitoring
Confirm that changing into maintenance mode and stop of monitoring have been successfully done.
(Refer to note of "4.1 hvoradisable - Discontinue Monitoring Resources".)
Add PDB
Allocate the files of the PDB on the shared disk. Start the PDB and check that OPEN_MODE is “READ WRITE".
See
For details, see the Oracle Database manual
Monitoring restart / Maintenance mode stop
# /opt/FJSVclora/sbin/hvoraenable -a <userApplication> (Monitoring restart) # /opt/SMAW/SMAWRrms/bin/hvutil -m off <userApplication> (Maintenance mode stop)
Confirmation of restart of monitoring and maintenance mode
Confirm that restart of monitoring and changing out of maintenance mode has been successfully done.
(Refer to note of "4.2 hvoraenable - Restart Monitoring Resources".)
Confirmation of PDB
Check that the following messages are output to syslog.
FSP_PCLW-ORACLE_FJSVclora: INFO: 9142: OPEN_MODE of PDB <PDB name> was OPEN. (CDB=<ORACLE_SID of CDB> PDB=<PDB name> OPEN_MODE=<state of PDB>)
Confirming of switch to the standby node
Confirm the switch of userApplication to the standby node, and CDB/PDBs start correctly.
Delete PDB when userApplication is Online. Execute the following procedures on the node whose userApplication is Online.
There is no setting change of the Oracle instance resource. After the monitoring restart, deleted PDB comes off from the monitor automatically.
Maintenance mode / Monitoring disruption
# /opt/SMAW/SMAWRrms/bin/hvutil -m on <userApplication> (Maintenance mode) # /opt/FJSVclora/sbin/hvoradisable -a <userApplication> (Monitoring disruption)
Confirmation of maintenance mode and stop of monitoring
Confirm that changing into maintenance mode and stop of monitoring have been successfully done.
(Refer to note of "4.1 hvoradisable - Discontinue Monitoring Resources".)
Delete PDB
See
For details, see the Oracle Database manual
Monitoring restart / Maintenance mode stop
# /opt/FJSVclora/sbin/hvoraenable -a <userApplication> (Monitoring restart) # /opt/SMAW/SMAWRrms/bin/hvutil -m off <userApplication> (Maintenance mode stop)
Confirmation of restart of monitoring and maintenance mode
Confirm that restart of monitoring and changing out of maintenance mode has been successfully done.
(Refer to note of "4.2 hvoraenable - Restart Monitoring Resources".)
