Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- ==> To get here, I followed the previous URL (using XE 18c) - first I did the change in the CDB$ROOT container :
- SQL> show parameter string_size
- NAME TYPE VALUE
- ------------------------------------ ----------- ------------------------------
- max_string_size string STANDARD
- SQL> alter system set max_string_size=EXTENDED scope=spfile;
- System altered.
- SQL> shutdown immediate;
- Database closed.
- Database dismounted.
- ORACLE instance shut down.
- SQL> startup upgrade;
- ORACLE instance started.
- ... lot of messages ...
- Database mounted.
- Database opened.
- ==> Now I run the utl32k script IN this container :
- SQL> @?/rdbms/admin/utl32k.sql
- Session altered.
- DOC>#######################################################################
- DOC>#######################################################################
- DOC> The following statement will cause an "ORA-01722: invalid number"
- DOC> error if the database has not been opened for UPGRADE.
- DOC>
- DOC> Perform a "SHUTDOWN ABORT" and
- DOC> restart using UPGRADE.
- DOC>#######################################################################
- DOC>#######################################################################
- DOC>#
- ... lots of messages, the important thing is to check if NO errors ORA-xxx happens ......
- Package altered.
- Package altered.
- ==>> restart of the CDB :
- SQL> shutdown immediate;
- Database closed.
- Database dismounted.
- ORACLE instance shut down.
- SQL> startup
- ORACLE instance started.
- ==>> see the changed parameter :
- SQL> show parameter string_size
- NAME TYPE VALUE
- ------------------------------------ ----------- ------------------------------
- max_string_size string EXTENDED
- ==> We are done with CDB but not with the whole task : I have the PDBs to be changed...
- SQL> show pdbs
- CON_ID CON_NAME OPEN MODE RESTRICTED
- ------ ---------- ---------- ----------
- 2 PDB$SEED MOUNTED
- 3 XEPDB1 MOUNTED
- 4 DB_APP MOUNTED
- ==> Solution: we have to run utl32k.sql in each PDB. For PDB$SEED let's use the well known “_oracle_script”-trick:
- SQL> alter session set "_oracle_script"=true;
- Session altered.
- SQL> alter pluggable database pdb$seed open upgrade;
- Pluggable database altered.
- SQL> alter session set container=PDB$SEED;
- Session altered.
- SQL> @?/rdbms/admin/utl32k
- Session altered.
- .. again, lot of messages, no ORA-xxx erros ...
- SQL> alter session set container=cdb$root;
- Session altered.
- SQL> alter pluggable database pdb$seed close;
- Pluggable database altered.
- SQL> alter pluggable database pdb$seed open read only;
- Pluggable database altered.
- ==> The other ones will be done normally :
- SQL> alter pluggable database XEPDB1,DB_APP open upgrade;
- Pluggable database altered.
- SQL> alter session set container=XEPDB1;
- Session altered.
- SQL> @?/rdbms/admin/utl32k
- .. again, lot of messages, no ORA-xxxx errors....
- SQL> alter session set container=DB_APP;
- Session altered.
- SQL> @?/rdbms/admin/utl32k
- .. etc...
- ==> restart of the PDBs :
- SQL> alter pluggable database XEPDB1,DB_APP close;
- Pluggable database altered.
- SQL> alter pluggable database XEPDB1,DB_APP open;
- Pluggable database altered.
- SQL> show pdbs
- CON_ID CON_NAME OPEN MODE RESTRICTED
- ---------- ------------------------------ ---------- ----------
- 2 PDB$SEED READ ONLY NO
- 3 XEPDB1 READ WRITE NO
- 4 DB_APP READ WRITE NO
- ==> That's all, folks....
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement